# Metadata error

**URL:** <https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436>\
**Category:** Unified Model\
**Created:** [6 June 2024 12:33 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436 "2024-06-06T12:33:12Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![emxin](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@emxin](https://cms-helpdesk.ncas.ac.uk/u/emxin)\
**Post date:** [6 June 2024 12:33 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/1 "2024-06-06T12:33:12Z")

</div>

Hi CMS,

I found errors in my suite (u-de518) Metadata when I did “check fail-in, warm-in”. They are related to (i) namelist:clmchfcg with errors on clima\_fcg\_levls\_che4 and clim\_fcg\_levls\_n2o, and (ii) nameless:run\_radiation with errors on ch4mmr and n2ommr, see attached screenshot for details. My question is do they cause model crash? and how to correct them? Note that the job I copied is a nudged version.

Cheers,  
Xin

 ![Screenshot 2024-06-06 at 12.58.33](https://europe1.discourse-cdn.com/flex013/uploads/cms_support/original/1X/b884068235caa17670a20e39b60e555e064007eb.png)

---

<div class="post-metadata">

**Author:** ![mdalvi](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mdalvi](https://cms-helpdesk.ncas.ac.uk/u/mdalvi)\
**Post date:** [6 June 2024 15:53 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/2 "2024-06-06T15:53:35Z")

</div>

Hi Xin,

The CH4 and N2O values will not be used **if the Radiative feedback from UKCA is selected** (l\*\_ukca\_radch4=.true. ; l\_ukca\_radn2o=.true.\*).  
I believe the ch4mmr and n2ommr have been deliberately set to unrealistic values that will cause the model to crash and thus ensure that only UKCA fields are used. (The warning/ error here is because they are set to \> 0.0 when the above logicals are True).  
It is not clear what the warning for the clim\_fcg\_levels is but they also should not be read in case of UKCA feedback.

---

<div class="post-metadata">

**Author:** ![emxin](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@emxin](https://cms-helpdesk.ncas.ac.uk/u/emxin)\
**Post date:** [7 June 2024 09:47 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/3 "2024-06-07T09:47:37Z")

</div>

Hi Mohit,

Thanks. It seems I do not need to worry about these warnings (even they are marked error). I have just submitted a small job to see it runs smoothly.

Another thing is, I am planning to run a nudged UKCA for the period of Nov/2019-May/2020 to make a campaign comparison. The the current nudged suite version (a copy of u-de170) is only available for years before the end of 2015. I am wondering if there is a suite-id that I can take for that period?

Best,  
Xin

---

<div class="post-metadata">

**Author:** ![mdalvi](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mdalvi](https://cms-helpdesk.ncas.ac.uk/u/mdalvi)\
**Post date:** [7 June 2024 10:11 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/4 "2024-06-07T10:11:46Z")

</div>

Hi Xin,

u-de170 seems to be already set up to run for 2015+ using the CMIP6 ssp3-7.0 scenario emissions and forcings.  
You will have to only replace the SST and Seaice files (currently ending in 2019-09) with those in /projects/ukca-admin/inputs/ancil/gregorian/n96e/reynolds/v2.1/reynolds\_\*\_201401-202312.anc

(In app/um/rose-app.conf, search for ‘reynolds’ in the [namelist:items] entries and replace the reynolds\_sst and reynolds\_seaice files with those mentioned above).

–  
Mohit

---

<div class="post-metadata">

**Author:** ![emxin](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@emxin](https://cms-helpdesk.ncas.ac.uk/u/emxin)\
**Post date:** [7 June 2024 11:05 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/5 "2024-06-07T11:05:08Z")

</div>

Hi Mohit,

Great, thanks! I have replaced both forcing files to see if they work.

Cheers,  
Xin

---

<div class="post-metadata">

**Author:** ![emxin](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@emxin](https://cms-helpdesk.ncas.ac.uk/u/emxin)\
**Post date:** [10 June 2024 08:03 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/6 "2024-06-10T08:03:12Z")

</div>

Hi Mohit,

After I changed the for forcing file the submitted suite job (u-de523) for 2019 failed with error message shown below.  
? 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 = 2019 9 1 0 0 0  
? fixhd validity time = 2015 9 1 0 0 0

It seems the date in “fixhd validity time” is taken from the initial file (but I am not sure on this), but I have changed it to the new year 2019 in the suite. BTW, I could not find where the term “fixed validity time” was defined. Please help, thanks!

Best,  
Xin

---

<div class="post-metadata">

**Author:** ![mdalvi](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mdalvi](https://cms-helpdesk.ncas.ac.uk/u/mdalvi)\
**Post date:** [10 June 2024 09:38 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/7 "2024-06-10T09:38:34Z")

</div>

Hi Xin,

The fihxd\_validity\_time is read from the initialisation file (AINITIAL\_FILE at the top-level).  
This is currently set to use ‘de087a.da20150901\_00’ from /work/n02/n02/anran.

From ‘moo ls’ it looks like neither u-de087 or u-de170 were actually run much beyond 2015, so there does not seem to be a 2019 initialisation file available from a related configuration.

If there is no suitable initialisation file for 2019, the reconfiguration step can be asked to overwrite the Year in the 2015 dump directly to 2019. Alternatively, you could start the run as ‘2018’ and run the first year as spin-up, given that you are nudging with ERA5 meteorology anyway.

---

<div class="post-metadata">

**Author:** ![emxin](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@emxin](https://cms-helpdesk.ncas.ac.uk/u/emxin)\
**Post date:** [10 June 2024 11:20 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/8 "2024-06-10T11:20:35Z")

</div>

Hi Mohit,

Could you please tell me a bit more in detail regarding how to overwrite the Year in reconfiguration? I could not find a proper webpage talking about this issue.  
I am also trying to re-run the job from 2018 to get a 2019 re-start file, but this may take a long time.

Best,  
Xin

---

<div class="post-metadata">

**Author:** ![mdalvi](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mdalvi](https://cms-helpdesk.ncas.ac.uk/u/mdalvi)\
**Post date:** [10 June 2024 11:29 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/9 "2024-06-10T11:29:36Z")

</div>

![image](https://europe1.discourse-cdn.com/flex013/uploads/cms_support/original/1X/e22305fa13d0993ceb54576edf02034f701b61a5.png)  
Example from another configuration

---

<div class="post-metadata">

**Author:** ![emxin](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@emxin](https://cms-helpdesk.ncas.ac.uk/u/emxin)\
**Post date:** [10 June 2024 13:28 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/10 "2024-06-10T13:28:40Z")

</div>

Thanks Mohit. That is very helpful.  
Xin

---

<div class="post-metadata">

**Author:** ![emxin](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@emxin](https://cms-helpdesk.ncas.ac.uk/u/emxin)\
**Post date:** [11 June 2024 08:35 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/11 "2024-06-11T08:35:55Z")

</div>

Hi Mohit,

The suite after changing the reconfiguration failed at "recent’ stage with error message:  
? Error from routine: RCF\_ANCIL\_ATMOS  
? Error message: replanca\_rcf\_replanca: Current time precedes start time of data

Not sure what caused the failure. Please help, thanks.

Xin

---

<div class="post-metadata">

**Author:** ![mdalvi](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mdalvi](https://cms-helpdesk.ncas.ac.uk/u/mdalvi)\
**Post date:** [11 June 2024 10:08 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/12 "2024-06-11T10:08:54Z")

</div>

Hi Xin,

From the Reconfiguration log file

```auto
/home/n02/n02/emxin/cylc-run/u-dg901/work/20190901T0000Z/recon/pe_out901.fort6.pe00
=================================
IO: Open: /work/n02/n02/luke/inputs/ocean_bgc/CHL_ssp370_timeseries_bc292_be690_2014_2100_n96_greg.anc on unit 13
replanca_rcf_replanca: UPDATE REQUIRED FOR FIELD 96 : OCEAN NR. SURFACE CHLOROPHYLL(KGM-3)

????????????????????????????????????????????????????????????????????????????????
?????????????????????????????? WARNING ??????????????????????????????
? Warning code: -100
? Warning from routine: REPLANCA_RCF_REPLANCA
? Warning message: Ancillary time mean lookup items 1-12 are not compliant UMDP F03. Field no: 96
? Warning from processor: 0
? Warning number: 3
????????????????????????????????????????????????????????????????????????????????

Error in replanca_rcf_replanca
CMESSAGE replanca_rcf_replanca: Current time precedes start time of data
ErrorStatus 496
============================

```

So it looks like the recon is incorrectly interpreting dates associated with the ancillary file due to mismatch in header format.  
The files seem to have been converted for Gregorian format by Luke.

@Luke have you seen this error before for other ‘future’ runs using the ancillaries?

For info, the checking and modified processing of ancillary headers was implemented at vn12.2 under [um:#6438](https://code.metoffice.gov.uk/trac/um/ticket/6438) so it would be interesting to know if the files worked fine in suites upto vn12.2, although there may have been a 15-day deviation while interpolating the data.

```auto

```

---

<div class="post-metadata">

**Author:** ![Luke](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/luke/32/45_2.png) [@Luke](https://cms-helpdesk.ncas.ac.uk/u/Luke)\
**Post date:** [11 June 2024 15:26 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/13 "2024-06-11T15:26:55Z")

</div>

Hi Mohit, Xin,

It looks like I made these up using Xancil in July 2023. I was making up a nudged UM13.x job and needed Gregorian ancillaries.

My suite is `u-dd451` and this should work on ARCHER2. It’s a UM13.0 UKESM1.1 AMIP suite nudged to ERA-5.

Best wishes,  
Luke

---

<div class="post-metadata">

**Author:** ![emxin](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@emxin](https://cms-helpdesk.ncas.ac.uk/u/emxin)\
**Post date:** [11 June 2024 16:09 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/14 "2024-06-11T16:09:35Z")

</div>

Hi Luke and Mohit,

Many thanks on this. I will try suite u-dd451 and see if it works.

Cheers  
Xin

---

<div class="post-metadata">

**Author:** ![mdalvi](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mdalvi](https://cms-helpdesk.ncas.ac.uk/u/mdalvi)\
**Post date:** [11 June 2024 19:29 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/15 "2024-06-11T19:29:56Z")

</div>

@Xin,

I am not sure if this is the right suite I am looking at (u-dg901) which showed the earlier error, but it looks like while the option to ‘override the year in the dump file’ has been selected, the desired year has not been set (activated as 1979 from base UKESM1 configuration).  
This is why the RCF/Ancil processing is complaining since all the ancillary data starts in 2015 while the model is trying to initialise for 1979.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/cms_support/original/1X/6221d7a144314612a00630b2003ffc38104d82ca.png)

---

<div class="post-metadata">

**Author:** ![emxin](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@emxin](https://cms-helpdesk.ncas.ac.uk/u/emxin)\
**Post date:** [13 June 2024 08:56 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/16 "2024-06-13T08:56:33Z")

</div>

Hi Mohit and Luke

I used the new sea ice and set ancillary files in a new suite (u-dh012), however the suite failed to open the seance file, see error message below. not sure what happened.

? Error from routine: io:file\_open  
? Error message: Failed to open file /projects/ukca-admin/inputs/ancil/gregorian/n96e/reynolds/v2.1/reynolds\_seaice\_201401-202312.anc

cheers,  
Xin

---

<div class="post-metadata">

**Author:** ![mdalvi](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mdalvi](https://cms-helpdesk.ncas.ac.uk/u/mdalvi)\
**Post date:** [13 June 2024 09:17 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/17 "2024-06-13T09:17:06Z")

</div>

Hi Xin,

I realised later that you are running on ARCHER2 - the files are on Monsoon !  
@Luke are you able to copy the files over to ARCHER2 to the UKCA / central area?

Thanks

---

<div class="post-metadata">

**Author:** ![emxin](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@emxin](https://cms-helpdesk.ncas.ac.uk/u/emxin)\
**Post date:** [26 June 2024 15:19 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/18 "2024-06-26T15:19:43Z")

</div>

Hi Luke,

Could you please copy the 2014-2031 ancillary files over to ARCHER2? Thanks!

Best,  
Xin

---

<div class="post-metadata">

**Author:** ![Luke](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/luke/32/45_2.png) [@Luke](https://cms-helpdesk.ncas.ac.uk/u/Luke)\
**Post date:** [26 June 2024 15:37 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/19 "2024-06-26T15:37:29Z")

</div>

Hi Xin,

I can’t at the moment - I can’t log-in. There are issues accessing the Monsoon lander currently.

I have files up to March 2020 at

```auto
/work/n02/n02/luke/inputs/reynolds

```

but I can look to copy the 2023 files when Monsoon is accessible again.

Best wishes,  
Luke

---

<div class="post-metadata">

**Author:** ![emxin](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@emxin](https://cms-helpdesk.ncas.ac.uk/u/emxin)\
**Post date:** [26 June 2024 15:55 UTC](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436/20 "2024-06-26T15:55:12Z")

</div>

Hi Luke,

No worries, I do not need them urgently. My current focus is the period: Nov/2019 to May/2020. The file upto March 2020 is helpful to text the model.

Best,  
Xin

[Next page](https://cms-helpdesk.ncas.ac.uk/t/metadata-error/1436.md?page=2)
