FVCOM suite

External files required

The aim is to have the rose suite as self contained as possible however there is a necessity for it to pick up some setup files from outside.

General run files (grid etc, in a common dir

If in hindcast mode the path to the WRF archive directory is required, if in forecast the path to both the WRF forecast and archive (to allow the river model to update) are required.

For the river mode when using the NEURAL_NET option . When using CLIMATOLOGY

When using the COLD_START and CMEMS then a warm start file interpolated from CMEMS data will be used for the first run. This requires a dummy restart file with one timestep (though the time value can be anything) for the structure to be used. The path to the file is defined in rose-suite.conf with the variable.

Dependencies on other suites

If FORECAST is on and any of WIND_ON, HEATING_ON, PRECIPITATION_ON, or AIR_PRESSURE_ON are true then it expects a suite with the name 'wrf' to be running and triggers on sucess of its task 'transfer_for_fvcom'

If BOUNDARY_FORCING is CMEMS then it expects a suite with the name 'download' to be running and triggers on finish of its task 'get_CMEMS_data'.

If BOUNDARY_FORCING is NEST_FILE then it expects a suite with the name specified by NEST_RUN_SUITE to be running and triggers on sucess of its task 'transfer_data'.

Variables for the FVCOM namelist

The aim is to have for the FVCOM rose suite to be as portable as possible, therefore any run specific fvcom options should be abstracted to the rose-app.conf file.

The process for doing this is:

• Add as a variable in rose-suite.conf (and try and commit a 'default' value)
• In suite.rc add to environment variables sections (following the template of the rest of the variables i.e. $var={{var}}
• In app/write_run_namelist/rose-app.conf replace the variable with the bash variable