# Glm recon failing looking for dust clay soil fraction

**URL:** <https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300>\
**Category:** Unified Model\
**Tags:** ARCHER2, Nesting-Suite\
**Created:** [12 January 2024 09:35 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300 "2024-01-12T09:35:01Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![shakka](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/shakka/32/111_2.png) [@shakka](https://cms-helpdesk.ncas.ac.uk/u/shakka)\
**Post date:** [12 January 2024 09:35 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/1 "2024-01-12T09:35:01Z")

</div>

Hi CMS,

I’ve started another run using suite u-dc576, which is a copy of u-cy223 (I’ve got ten of these suite running perfectly at the moment). It’ failing in the recon, looking for STASH 418 (soil dust clay fraction).

???  
???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!!  
? Error code: 30  
? Error from routine: RCF\_RESET\_DATA\_SOURCE  
? Error message: Section 0 Item 418 : Required field is not in input dump!  
? Error from processor: 0

The only thing about this suite that is different to u-cy223 is the dates (2020).

It’s pretty confusing because the task does produce as astart file and the field _is_ in it (albeit all zeroes). So it’s not that the field isn’t in the input dump, it’s more that it’s not got any values.

I figured that I might be using cycle dates after the end of the global ancil file, but it’s a climatology so it shouldn’t be causing a time-related issue.

Can you help?

Cheers,  
Ella

---

<div class="post-metadata">

**Author:** ![shakka](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/shakka/32/111_2.png) [@shakka](https://cms-helpdesk.ncas.ac.uk/u/shakka)\
**Post date:** [13 January 2024 13:56 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/2 "2024-01-13T13:56:09Z")

</div>

Update: I also tried adding these stash in under glm\_um\>recon\>configure ancils and: 1) referring to the um ancil directory on archer, 2) setting to zero. I figured there must be a reference to stash 418 in the optional config for ga7 but I can’t see it (seems like the only references are in the confusingly named opt/rose-app-nosoildust.conf

I also tried running with GA6.1 in case that eliminates the need for the soil dust ancil.

Turning on extra diags doesn’t really help either. Any thoughts? I’m really stuck here.

Ella

---

<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:** [15 January 2024 10:24 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/3 "2024-01-15T10:24:27Z")

</div>

Ella,  
Is it the case that u-dc576 is identical to u-da701 apart from dates (if not u-da701, which successfully running suite is it identical to?)

Grenville

---

<div class="post-metadata">

**Author:** ![shakka](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/shakka/32/111_2.png) [@shakka](https://cms-helpdesk.ncas.ac.uk/u/shakka)\
**Post date:** [15 January 2024 12:17 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/4 "2024-01-15T12:17:08Z")

</div>

Hi Grenville,

Yep, all the suites starting u-da, plus u-dc576, are copies of u-cy223 and so should be identical aside from dates.

(Btw I got past the soil dust clay error by adding it in under the glm recon panel, but I’m now getting the same error relating to stash 221, snow soot content.)

---

<div class="post-metadata">

**Author:** ![shakka](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/shakka/32/111_2.png) [@shakka](https://cms-helpdesk.ncas.ac.uk/u/shakka)\
**Post date:** [16 January 2024 16:15 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/5 "2024-01-16T16:15:35Z")

</div>

Update: I tested running the suite as-is and changing the dates to 2000, and it runs with no problem. So it’s definitely something about the year being 2020.

Any insight would be much appreciated with this as I also need to run years 2021, 2022 and 2023, which I assume will have the same problem…

---

<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:** [17 January 2024 09:36 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/6 "2024-01-17T09:36:24Z")

</div>

This is bizarre - looking

---

<div class="post-metadata">

**Author:** ![shakka](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/shakka/32/111_2.png) [@shakka](https://cms-helpdesk.ncas.ac.uk/u/shakka)\
**Post date:** [18 January 2024 10:20 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/7 "2024-01-18T10:20:43Z")

</div>

Did you manage to find any reasons for this, Grenville?

---

<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:** [18 January 2024 10:39 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/8 "2024-01-18T10:39:04Z")

</div>

We’re still looking - this is undesirable behaviour!! It appears that there is some logic in the masses of nesting suite jinja that users aren’t aware of or it’s a bug.

---

<div class="post-metadata">

**Author:** ![shakka](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/shakka/32/111_2.png) [@shakka](https://cms-helpdesk.ncas.ac.uk/u/shakka)\
**Post date:** [18 January 2024 10:40 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/9 "2024-01-18T10:40:53Z")

</div>

okay, that sounds like a deeper issue than I had anticipated! Thanks for digging into this for me…

---

<div class="post-metadata">

**Author:** ![shakka](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/shakka/32/111_2.png) [@shakka](https://cms-helpdesk.ncas.ac.uk/u/shakka)\
**Post date:** [18 January 2024 13:25 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/10 "2024-01-18T13:25:42Z")

</div>

fyi, I also tried a month in 2022 and got the same error using this same suite.

---

<div class="post-metadata">

**Author:** ![AnnetteOsprey](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/annetteosprey/32/27_2.png) [@AnnetteOsprey](https://cms-helpdesk.ncas.ac.uk/u/AnnetteOsprey)\
**Post date:** [18 January 2024 15:20 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/11 "2024-01-18T15:20:08Z")

</div>

Hi Ella,

There is a bit of logic in the job script which sets the `nodust` optional configuration based on the date:

```auto
cylc __job__ inst__env_script() {
# ENV-SCRIPT:
eval $(rose task-env)
DUST_OPT=
EC_OPT=
DATE=$(rose date -c -f %Y%m%d%H%M)
  if [[$DATE -lt 201107201200]]; then
    DUST_OPT=nodust
  fi
}

```

This is pulled in from the file `suite-runtime/dm.rc` in the suite.

The logic seems to be that there is no dust in UM start dumps before this date (I found a reference to this in the suite repo: [https://code.metoffice.gov.uk/trac/roses-u/changeset/7458](https://code.metoffice.gov.uk/trac/roses-u/changeset/7458))

However looks like you are starting from an ERA file anyway, so that logic isn’t relevant.

Hopefully that explains what is going on with the different behaviour based on the start dates.

Annette

---

<div class="post-metadata">

**Author:** ![shakka](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/shakka/32/111_2.png) [@shakka](https://cms-helpdesk.ncas.ac.uk/u/shakka)\
**Post date:** [18 January 2024 15:32 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/12 "2024-01-18T15:32:48Z")

</div>

Thanks Annette. So I can just change that date?

Edit for anyone also having this problem: I did just change the date (to 01/01/24) and it runs fine.

---

<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:** [5 February 2024 09:56 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/13 "2024-02-05T09:56:48Z")

</div>



---

<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:** [6 March 2024 09:56 UTC](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300/14 "2024-03-06T09:56:58Z")

</div>

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