Hi there.
Are these runs done on Archer2 or Monsoon3?
I’m doing the runs on Monsoon3 (under ~jonny.williams.ext). I only used ARCHER2 to create some perturbed restarts.
Mohit advised me to add this line :
mule.stashmaster.STASHMASTER_PATH_PATTERN = ‘/projects/metoff/umdir/vn13.9/ctldata/STASHmaster/STASHmaster_A’
Thank you, that’s worked for me.
The different ainitial (eb430a.da19800101_00_1979) is from today because I am now trying to perturb the runs by using dump file from a year after the start, rather than perturb_theta.
I think this is a good idea; certainly worth a try.
I’m trying a version with the reconfiguration turned off to see if this makes any difference. The results I get when running with my newly perturbed restart files do differ according to mule-cumf but they are extremely small (in agreement with your previous message). According to the ‘docstring’ in perturb_theta.py, the script is designed to fix ‘grid point storms’ which occur mid-run, not at the start. So it’s possible that the reconfiguration is somehow ironing out the differences intruduced by perturb_theta.py.
Another way of doing a qualitatively similar thing to perturbing theta (ostensibly to fix those ‘grid point storms’ I mentioned) is to change the number of calls to convection for 1 month to tweak the integration of the model, e.g. see here.
Yet another possibility is to just use some start dumps other years in the same workflow as the standard one from u-by791. These are available on MASS…
$ moo ls moose:/crum/u-by791/ada.file|grep -C 1 1979
moose:/crum/u-by791/ada.file/by791a.da19780101_00
moose:/crum/u-by791/ada.file/by791a.da19790101_00
moose:/crum/u-by791/ada.file/by791a.da19800101_00
To use these you’d need to overwrite the start year in the dump but that’s straightforward using the rose GUI.
All the best.
Jonny