Opened 2 years ago

Closed 2 years ago

#2734 closed help (answered)

Mismatch between model_basis_time and validity time when starting run

Reported by: aschurer Owned by: um_support
Component: UM Model Keywords:
Cc: Platform: Monsoon2
UM Version: 11.0


Hi, I have run a job u-bd077 for 5 years of a 50 year run.

I checked the output and realised there was a small error in my branch. Which I have subsequently corrected.

Given that the change is small I have decided that I want to continue the run from the end of the 5 years rather than re-start everything.

The run started in 1850-Jan and is now at 1855-Jan

Consequently I have changed:
1 my branch
2 the basis time to 1855-Jan
3 the name of the dump files to point to those generated at the end of the 5-year run.


The model run generates the following message:

? 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 = 1855 1 1 0 0 0
? fixhd validity time = 1850 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: 997
? Error number: 142

[997] exceptions: An non-exception application exit occured.
[997] exceptions: whilst in a serial region
[997] exceptions: Task had pid=20423 on host nid04964
[997] exceptions: Program is "./atmos.exe"
Warning in umPrintMgr: umPrintExceptionHandler : Handler Invoked


Which I think looks like the time in my atmospheric dump might still be incorrectly set to 1850. Could you please advise. Am I pointing to an incorrect dump? Or is there a problem somewhere else? Maybe the recon is overwriting the start date?

Many thanks,

Change History (4)

comment:1 Changed 2 years ago by willie

Hi Andrew,

If the 5 year run terminated normally, then all you have to do is set the end date to 50 years hence and then

rose suite-run --restart

It will then carry on from where it left off. You will need to revert your changes first.

If the 5 year run failed with an error or was terminated in mid-processing, the procedure is much more complex.


comment:2 Changed 2 years ago by aschurer

Hi Willie,

Would that have worked given that I needed to change a branch?

I thought that such a processes would require re-compiling and therefore more than a rose suite-run —restart

This was why I went down the route of trying to start a new simulations from the end point of the old run.
Given I've already attempted this can I now go down the restart route?

If the process is very complex would you recommend just starting again from the beginning i.e. in 1850?


comment:3 Changed 2 years ago by grenville


Changing a branch will require a rebuild - probably easiest to start afresh.

Sorry for the delay


comment:4 Changed 2 years ago by willie

  • Resolution set to answered
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.