-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Geos cycling tasks #184
Geos cycling tasks #184
Conversation
…ure/forecast_geos sky update
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments after looking through the code. I haven't tried to run anything yet.
src/swell/utilities/bin/generate_task_question_default_dicts.py
Outdated
Show resolved
Hide resolved
Thanks for putting together this great and extensive piece of work. I haven't tested things yet but started adding a few minor comments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Swell cycles!
Description
Major refactoring of GEOSgcm
gcm_run.j
within Swell and the addition of relevant tasks and utilities. Includes recent updates regarding configurations and task questions.New suite
forecast_geos
allows running coupled GEOSgcm with 5 deg ocean horizontal resolution andPE12x72-CF
atm. resolution. 0.66 and 0.25 degree tests were also simulated but they will require a few more modifications to run.New suite
3dvar_cycle
is capable of running coupled GEOSgcm with 5 deg ocean horizontal resolution and PE12x72-CF atm. resolution with 24 hour DA window. 2/3- and 1/4-degrees runs are also possible. Appropriate IC files need to be provided and the rest is handled by3dvar_cycle
These changes allow hot starting 3DVar cycling GEOS from a previous run using configuration files created with gcm_setup. Swell assumes
$HOMDIR
and$EXPDIR
are collocated (if not, only theRC
folder needs to be moved from$EXPDIR
to the$HOMDIR
).User needs to point to the
$HOMDIR
of the previous run (for hotstarting) as well as the*_rst
files,MOM.res.nc
(can be multiple), andtile.bin
created by a previous GEOS simulation. Rest is handled by Swell tasks internally.Capabilities
AGCM.rc
,CAP.rc
, andgcm_run.j
into dictionaries to obtain grid, BC, and physics information. This allows modifications of BCs according to cycle time step similar to what's done ingcm_run.j
.NUM_SGMT
andJOB_SGMT
entries inCAP.rc
and'n'
to'r'
change ininput.nml
.cap_restart
automatically.*_checkpoint
to*_rst
.AGCM.rc
calledRECORD_FREQUENCY
which will be useful for DA outputs.*_rst
files. This could pose an issue between yaml setup and restart files so probably requires some time difference check in Swell. GEOSgcm handles this internally and quits if mismatch is too high.MOM.res.nc
with theocn.analysis
file from SOCA withPrepareAnalysis
task. This task could easily be updated to handleice
,sfc
, andbgc
files using SOCAnomenclature
.geosdir
.Some current issues
AGCM.rc
andMOM_override
which is obtained by gcm_setup.RunGeosExecutable
does not allow repeating runs in the same folder if the model progressed some time steps during the first try and outputted history files. GEOS fails and exits if it sees those history files during next try.gcm_run.j
were not included. mpirun automatically assumes MOM6 (LD_PRELOAD=$GEOSDIR/lib/libmom6.so
was not necessary). These did not cause issues on my end but something to keep in mind.-P1D
inflow.cylc
requires manual change for geos suites,-P1
does not work in UTC mode.cycle_times
need to be added toflow.cylc
for3dvar_cycle
suite.