Skip to content

FVCOM suite

Jump to bottom
Ricardo Torres edited this page Dec 12, 2022 · 5 revisions

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 DONOR_RESTART_FILE_PATH variable.

It only applies to the first day of forecast after which it runs from hot start from the previous FVCOM run.

If its fallen over and you want to keep running from yesterdays forecast then it depends if you have had to clear the ~/cylc-run directories as part of the solution or not (e.g. by doing rose suite- clean).

If you have COLD_START=False and ARCHIVE_RESTART=False then it will attempt to retrieve the restart from the previous day from the relevant folder in '~/cylc-run/fvcom_xxx/share/cycle/DDDD/' on ceto. It will fail if that has been deleted.

If you have COLD_START=False and ARCHIVE_RESTART=True then it will attempt to retrieve an already made restart file for the previous day from the location defined by RESTART_ARCHIVE_DIR . At the moment this should be setup to automatically dump the ongoing restart files in the correct restart folder so should always be able to restart in this way if the model has run to completion (but not e.g. if the model failed to transfer output because destination disk is full).

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
Clone this wiki locally