Regrid suite

This suite produces a . Currently only the CETO version works. Also take care with the number of nodes used, with Python MPI it seems to throw an error if they are over catered (i.e. more processes than operations). Conversely there is a 2gb limit on the gather function so using regrid on too large a file can also cause an issue...

There should be one instance running for each regridding required

The trigger for starting the suite is specified using TRIGGER_SUITE and TRIGGER_TASK. Whilst this should normally be the fvcom suite that is being regridded (e.g. TRIGGER_SUITE='fvcom_tamar', TRIGGER_TASK='transfer_data') if there are multiple regrids occuring on the same output it would be better to serially chain them making later regrids trigger off the completion of earlier ones such that you're not trying to run a large number of processes on phorcys at once.

NODES=1

TRIGGER_SUITE='fvcom_tamar'

TRIGGER_TASK='transfer_data'

FVCOM_GRID_NAME='tamar_v2' FVCOM_OUTPUT_DIR='data/sthenno1/scratch/modop/Model/FVCOM_tamar/output' GRID_LOWER_LEFT - comma delimited lon lat coordinates of the lower left of the regrid e.g. '-4.3,50.24'

GRID_UPPER_RIGHT - comma delimited lon lat coordinates of the top right of the regrid e.g.'-4.05,50.55'

HORIZ_RES - resolution (in degrees) of the regrid e.g. 0.001

DEPTH_LAYERS - comma delimited string of depth layers on which to regrid e.g. '0,3,5,10,15,20,25,30,40'

VARS - comma seperated list of variables to regrid'temp,salinity,u,v,zeta'

OUTPUT_DIR - 'data/sthenno1/scratch/modop/Model/FVCOM_tamar/estuary_output'

OUTPUT_FILENAME='tamar_estuary_001'

PORTAL_BASEDIR - Directory into which to softlink the regridded output in order to have it in the portal. Path should be specified without leading slash e.g. 'data/sthenno1/scratch/modop/Portal/Model/TAMAR_ESTUARY_FORECAST_PHY_001/tamar_estuary_forecast_phy_001_hourly_t_s_u_v_ssh'