global ensemble workflow debugging - restart fails with "Error from routine: EXPPXI - Invalid item number 0"

[Björn Fock (BHFock)]

I am helping a partner to debug a global model workflow which fails to restart the forecast task (CRUN and using CONTINUE=true) with the error:

[0] um_readdump:UM_READDUMP : Dump field 464 switching from ppx_atm_ozone to ppx_atm_tzonal
[0] ereport_mod:
[0] ereport_mod:????????????????????????????????????????????????????????????????????????????????
[0] ereport_mod:???!!!???!!!???!!!???!!!???!!!       ERROR        ???!!!???!!!???!!!???!!!???!!!
[0] ereport_mod:?  Error code: 100
[0] ereport_mod:?  Error from routine: EXPPXI
[0] ereport_mod:?  Error message: Invalid item number     0
[0] ereport_mod:?  Error from processor: 0
[0] ereport_mod:?  Error number: 21
[0] ereport_mod:????????????????????????????????????????????????????????????????????????????????

Can you comment on where this error may come from and what a solution could be?

I have the log files and app but cannot run the case myself and do not have the full workflow or input data available. An initial advice here and a follow up via email or private message for further investigation would be helpful. I will point our partner to this post so that they can see it as well.

[Deleted user (ghost)]

Thank you Bjoern,

Although I'm currently utilizing an ensemble suite, this workflow can also undergo testing with deterministic forecasting. The objective is to restart the global forecast after 5 days but at a coarse resolution. Based on my understanding, I am trying the following way:

1. Execute the global long forecast for a duration of 6 days (allowing for extra hours to amalgamate lagged forecasts).
2. Following has been used to obtain a restart dump:

[namelist:nlstcgen]
dumptimesim=120,39*0

3. This will generate the restart dump "englaa_da120" (at 12km resolution in our scenario).
4. Reconfigure "englaa_da120" to get a coarser resolution file (20km in our scenario).
5. Restart the forecast utilizing this coarser resolution dump by setting CRUN with CONTINUE=true.

I hope it could make some sense