The fix will removing the offending function altogether and instead use a more deterministic source for the forcing which as been setup by @aidanheerdegen. The atmosphere/forcing.json file will then include the names of the forcing files in a format like:
@aekiss and @marshallward have both reported an error like this:
forrtl: severe (124): Invalid command supplied to EXECUTE_COMMAND_LINE Image PC Routine Line Source yatm_1044c48e.exe 00000000006326D1 Unknown Unknown Unknown yatm_1044c48e.exe 00000000004E07F6 util_mod_mp_first 53 util.F90 yatm_1044c48e.exe 000000000040E54B forcing_mod_mp_fo 131 forcing.F90 yatm_1044c48e.exe 000000000040D864 MAIN__ 98 atm.F90 yatm_1044c48e.exe 000000000040C31E Unknown Unknown Unknown libc-2.12.so 00002AF70A83AD1D __libc_start_main Unknown Unknown yatm_1044c48e.exe 000000000040C229 Unknown Unknown Unknown forrtl: error (78): process killed (SIGTERM)
The fix will removing the offending function altogether and instead use a more deterministic source for the forcing which as been setup by @aidanheerdegen. The atmosphere/forcing.json file will then include the names of the forcing files in a format like:
/g/data1/ua8/JRA55-do/latest/rain.{{year}}.nc
Previously this was:
/g/data1/ua8/JRA55-do/v1-3/rain.{{year}}.*.nc