# Time compatibility error with start dumps

**URL:** <https://cms-helpdesk.ncas.ac.uk/t/time-compatibility-error-with-start-dumps/204>\
**Category:** Unified Model\
**Tags:** Monsoon2\
**Created:** [27 August 2021 09:01 UTC](https://cms-helpdesk.ncas.ac.uk/t/time-compatibility-error-with-start-dumps/204 "2021-08-27T09:01:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![zosiast](https://avatars.discourse-cdn.com/v4/letter/z/258eb7/32.png) [@zosiast](https://cms-helpdesk.ncas.ac.uk/u/zosiast)\
**Post date:** [27 August 2021 09:01 UTC](https://cms-helpdesk.ncas.ac.uk/t/time-compatibility-error-with-start-dumps/204/1 "2021-08-27T09:01:12Z")

</div>

Hi there,

I’m running a 2014 timeslice experiment (u-ch405). I’ve done a spin up run for 10 years (u-ch090) and would like to use the dumps from the end of the run (2023) to start this timeslice. The mismatch in date seems to be causing the error.

Error files here on monsoon: /home/d04/zstanias/cylc-run/u-ch405/log/job/20140101T0000Z/coupled/NN

Error 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 = 2014 1 1 0 0 0  
? fixhd validity time = 2023 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

I’ve tried setting i\_override\_date\_time to 1 and setting the new\_date\_time to 2014 (shown [here](https://code.metoffice.gov.uk/trac/roses-u/changeset?reponame=&new=204505%40c%2Fh%2F4%2F0%2F5&old=204496%40c%2Fh%2F4%2F0%2F5)) as suggested but am still getting the same error.  
Note I have re-labelled the start dump filenames to 2014.

Thanks in advance,  
Zosia

---

<div class="post-metadata">

**Author:** ![grenville](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/grenville/32/29_2.png) [@grenville](https://cms-helpdesk.ncas.ac.uk/u/grenville)\
**Post date:** [31 August 2021 07:57 UTC](https://cms-helpdesk.ncas.ac.uk/t/time-compatibility-error-with-start-dumps/204/2 "2021-08-31T07:57:35Z")

</div>

Zosia

I’m not entirely sure what you are trying to do, but I suggest changing the model basis time to 2023. Note, it is usually possible to extend a run simply by changing the run length and restarting the suite (but, I can’t tell if that is what you wish to do).

Grenville

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/cms_support/original/1X/1fd2411499ffcbc299fe756cd5cdf26e44956558.png) [@system](https://cms-helpdesk.ncas.ac.uk/u/system)\
**Post date:** [20 October 2021 14:57 UTC](https://cms-helpdesk.ncas.ac.uk/t/time-compatibility-error-with-start-dumps/204/3 "2021-10-20T14:57:48Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.