Opened 6 months ago

Closed 5 months ago

#3123 closed help (answered)

Error: Mismatch between model_basis_time read from namelist and validity time read

Reported by: luciad Owned by: ros
Component: UM Model Keywords: time mismatch
Cc: Platform: ARCHER
UM Version: 11.1

Description

Hello,

I wanted to start the run of my suite (u-bo228) in 20170801 (instead
of 20170101), and I only modified the model_basis_time, but I get the following error (same as in ticket #2357):

???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!!
? Error code: 10
? Error from routine: INITTIME
? Error message:
? Mismatch between model_basis_time read from namelist and validity time read
? from dump fixed header.
?
? model_basis_time = 2017 8 1 0 0 0
? fixhd validity time = 2017 1 1 0 0 0
?
? If this is intentional disable this check by setting all elements of
? namelist:nlstcall=model_basis_time to zero. Otherwise make adjustments to
? either the namelist or dump to ensure that these two values match.
?
? Please note, that if it is valid to do so for your job setup, you may change
? the validity time of the dump using the reconfiguration namelist variables:
? * namelist:headers=i_override_date_time
? * namelist:headers=new_date_time
?
? Please see the metadata help text associated with these two variables for
? more information.
? Error from processor: 168
? Error number: 23
????????????????????????????????????????????????????????????????????????????????

Is it correct to modify the Output dump fixed header overrides
→ new_date_time which is set to $BASIS_YR,01,01,0,0,0 to $BASIS_YR,08,01,0,0,0 or there is a more efficient way?

I also checked Dumping and Meaning → astart which is set to
$ROSE_DATA/${RUNID}a.astart. Should I set this to:
'$DATAM/${RUNID}a.da${DATEC_DUMP}' ?

Thank you for the help,
Lucia

Change History (4)

comment:1 Changed 6 months ago by luciad

  • Type changed from defect to help

comment:2 Changed 6 months ago by ros

  • Owner changed from um_support to ros
  • Status changed from new to accepted

Hi Lucia,

Yes you are overriding the full date so you need to set the new_date_time to be $BASIS_YR,08,01,0,0,0

No need to change astart setting.

Cheers,
Ros.

comment:3 Changed 6 months ago by luciad

Hi Ros,

I modified the new_date_time as suggested. However, I get the same error.

Any thoughts?
Lucia

comment:4 Changed 5 months ago by ros

  • Resolution set to answered
  • Status changed from accepted to closed

Closed due to lack of activity and continued in other tickets. (#3127)

Note: See TracTickets for help on using tickets.