dkhutch
commented
3 months ago Hi Pearse,
I think this issue relates to the UM date stamp not matching the date from config.yaml. You can try updating the date stamp using this script:
https://github.com/dkhutch/gadi_tools/blob/master/um_change_time.py
In order to make it work, you'll need to add the following directory to your PYTHONPATH:
/g/data/access/projects/access/apps/pythonlib/umfile_utils/
Regards, Dave
I am getting this error when following the instructions herein for setting up the historical run.
1 gc_abort (Processor 2): INITTIME: Atmosphere basis time mismatch
2 gc_abort (Processor 26): INITTIME: Atmosphere basis time mismatch
3 gc_abort (Processor 34): INITTIME: Atmosphere basis time mismatch
4 gc_abort (Processor 37): INITTIME: Atmosphere basis time mismatch
5 6 UM ERROR (Model aborting) : 7 Routine generating error: INITIAL 8 Error code: 1 9 Error message: 10 INITTIME: Atmosphere basis time mismatch 11 12 gc_abort (Processor 0): INITTIME: Atmosphere basis time mismatch
13 gc_abort (Processor 8): INITTIME: Atmosphere basis time mismatch
14 gc_abort (Processor 12): INITTIME: Atmosphere basis time mismatch
15 gc_abort (Processor 19): INITTIME: Atmosphere basis time mismatch
16 gc_abort (Processor 32): INITTIME: Atmosphere basis time mismatch
17 gc_abort (Processor 7): INITTIME: Atmosphere basis time mismatch
18 gc_abort (Processor 40): INITTIME: Atmosphere basis time mismatch
19 gc_abort (Processor 1): INITTIME: Atmosphere basis time mismatch
20 gc_abort (Processor 10): INITTIME: Atmosphere basis time mismatch
21 gc_abort (Processor 11): INITTIME: Atmosphere basis time mismatch
22 gc_abort (Processor 14): INITTIME: Atmosphere basis time mismatch
23 gc_abort (Processor 16): INITTIME: Atmosphere basis time mismatch
24 gc_abort (Processor 20): INITTIME: Atmosphere basis time mismatch
25 gc_abort (Processor 22): INITTIME: Atmosphere basis time mismatch
26 gc_abort (Processor 27): INITTIME: Atmosphere basis time mismatch
27 gc_abort (Processor 47): INITTIME: Atmosphere basis time mismatch
28 gc_abort (Processor 33): INITTIME: Atmosphere basis time mismatch
29 gc_abort (Processor 36): INITTIME: Atmosphere basis time mismatch
...
The error continues for 20260 lines so I won't provide it all here.
But, if I try the following:
payu setup
I get this response:
[pjb581@gadi-login-01 access-esm]$ payu setup laboratory path: /scratch/p93/pjb581/access-esm binary path: /scratch/p93/pjb581/access-esm/bin input path: /scratch/p93/pjb581/access-esm/input work path: /scratch/p93/pjb581/access-esm/work archive path: /scratch/p93/pjb581/access-esm/archive Loading input manifest: manifests/input.yaml Loading restart manifest: manifests/restart.yaml Loading exe manifest: manifests/exe.yaml Setting up atmosphere Setting up ocean Setting up ice Setting up coupler Checking exe and input manifests Updating full hashes for 3 files in manifests/exe.yaml Creating restart manifest Updating full hashes for 30 files in manifests/restart.yaml Writing manifests/restart.yaml Writing manifests/exe.yaml /g/data/hh5/public/apps/miniconda3/envs/analysis3-23.10/lib/python3.10/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.10/lib/python3.10/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) cdo(1) chname: Process started cdo(1) chname: Processed 78564480 values from 1 variable over 166 timesteps cdo selyear (Warning): Year 101 not found! cdo selyear (Abort): No timesteps selected!
Something is happening here with the config files setting the timesteps and year?
Thanks, pearse