EMPIRE DA
v1.9.1
Data assimilation codes using EMPIRE communication
|
module pf_control holds all the information to control the the main program More...
Data Types | |
type | pf_control_type |
Public Member Functions | |
subroutine | set_pf_controls |
subroutine to ensure pf_control data is ok More... | |
subroutine | parse_pf_parameters |
subroutine to read the namelist file and save it to pf datatype Here we read pf_parameters.dat or empire.nml More... | |
subroutine | deallocate_pf |
subroutine to deallocate space for the filtering code More... | |
Public Attributes | |
type(pf_control_type), save | pf |
the derived data type holding all controlling data More... | |
module pf_control holds all the information to control the the main program
Definition at line 29 of file pf_control.f90.
subroutine pf_control::deallocate_pf | ( | ) |
subroutine to deallocate space for the filtering code
Definition at line 519 of file pf_control.f90.
subroutine pf_control::parse_pf_parameters | ( | ) |
subroutine to read the namelist file and save it to pf datatype Here we read pf_parameters.dat or empire.nml
pf_parameters.dat or empire.nml is a fortran namelist file. As such, within it there must be a line beginning
&pf_params
To make it (probably) work, ensure there is a forward slash on the penultimate line and a blank line to end the file
This is just the fortran standard for namelists though.
On to the content...in any order, the pf_parameters.dat (or empire.nml) file may contain the following things:
Integers:
Reals, double precision:
2 Characters:
1 Character:
Logicals:
250 Character string:
Definition at line 216 of file pf_control.f90.
subroutine pf_control::set_pf_controls | ( | ) |
subroutine to ensure pf_control data is ok
Definition at line 146 of file pf_control.f90.
type(pf_control_type), save pf_control::pf |
the derived data type holding all controlling data
Definition at line 141 of file pf_control.f90.