You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The steps to reproduce the error are listed in the first message of the post:
Hello everyone!
I’ve been trying to restart a historical run with no success. I want to restart it from year 1960 and apply some perturbations.
What I’ve done so far:
git cloned the esm-historical configuration directory
changed start year at config.yaml to 1960
changed ‘inidate’ and ‘init_date’ to 19600101 in ice/input.nml
changed ‘model_basis_time’ to 1960
changed the following in warm_start.sh: project=p66; user=cm2704; expname=HI-14; source_year=1960 and run the warm start scripts
when running the warm start script I’ve got the following warnings:
/g/data/hh5/public/apps/miniconda3/envs/analysis3-23.04/lib/python3.9/site-packages/mule/stashmaster.py:259: UserWarning:
Unable to load STASHmaster from version string, path does not exist
Path: $UMDIR/vn7.3/ctldata/STASHmaster/STASHmaster_A
Please check that the value of mule.stashmaster.STASHMASTER_PATH_PATTERN is correct for your site/configuration
warnings.warn(msg)
/g/data/hh5/public/apps/miniconda3/envs/analysis3-23.04/lib/python3.9/site-packages/mule/validators.py:198: UserWarning:
File: work/atmosphere/restart_dump.astart
Field validation failures:
Fields (1114,1115,1116)
Field grid longitudes inconsistent
File grid : 0.0 to 358.125, spacing 1.875
Field grid: 0.5 to 359.5, spacing 1.0
Extents should be within 1 field grid-spacing
Field validation failures:
Fields (4935,4937,6676,6715)
Skipping Field validation due to irregular lbcode:
Field lbcode: 31320
warnings.warn(msg)
If I try to put the model to run it crashes at the very begging with payu error code 134. This seems to be related to forcing/restart files and the same warning as above appears in the payu error log file.
Any ideas on how to make this restart work are welcome.
Thanks,
Gabriel
The text was updated successfully, but these errors were encountered:
This issue is created as a follow-up of the discussion happened in this ACCESS-Hive forum post.
The steps to reproduce the error are listed in the first message of the post:
The text was updated successfully, but these errors were encountered: