HadGEM2-ES run with ExtTC - Climate Meaning Error

[mhollaway]

Hi,

I am trying to get a version of HadGEM2-ES running with extended tropospheric chemistry switched on. The model performs the reconfiguration step with no reported errors and runs without problem for ten days however when I try to run it for longer I get the following error.

MEANCTL: ***** Called in ATMOSPHERIC mode *****
  MEAN_OFFSET( 1 )= 3
 MEANCTL: Period_ 4  mean not activated because of staggered start in means production
 Period_1 data read from unit number  24
 Period_1 data written to unit number  23

OPEN:  File /scratch/mhollo/xfsai/xfsai.apstmp1 to be Opened on Unit 24 Exists

OPEN:  File /scratch/mhollo/xfsai/xfsai.apsum1 to be Opened on Unit 23 does not Exist
OPEN:  File /scratch/mhollo/xfsai/xfsai.apsum1 Created on Unit 23
 ERROR: checksum failure in climate mean
 Section  19  item  36
 This can be due to invalid values in field, or corruption of partial sum file
 Remove or fix diagnostic, and rerun
 MEANCTL: RESTART AT PERIOD_ 0
 U_MODEL: interim history file deleted due to failu     re writing partial sum files
 *********************************************************************************
 UM ERROR (Model aborting) :
 Routine generating error: U_MODEL
 Error code:  4
 Error message:
ACUMPS: Diagnostic error. See output for item no.
 *********************************************************************************

I have noticed that the variable mentioned (section 19 item 36 in STASH) is related to TRIFFID. Could this error be linked to a difference between the TRIFFID time period and the UM time period as I am running with interactive vegetation?

Many Thanks in advance.

Michael Hollaway.

[jeff]

Hi Michael

This error usually means that the stash field contains NaNs?, i.e. invalid values. Check your output field to make sure it looks okay. If its wrong then you have to either fix it somehow or delete it from your stash output, but beware of any underlying problems.

Jeff.

[mhollaway]

Hi Jeff,

Many thanks for your reply. I have checked the output field in the restart dump for the job and it appears that that field is not present at all. I will check the setup of the diagnostics and see if I can remove or fix the field causing the error.

Thanks again.

Michael.