# 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:** 1\
**Showing post:** 11

<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

---

_[View the full topic](https://cms-helpdesk.ncas.ac.uk/t/glm-recon-failing-looking-for-dust-clay-soil-fraction/1300)._