# CABLE site runs with ACCESS forcing

**URL:** <https://forum.access-hive.org.au/t/cable-site-runs-with-access-forcing/2108>\
**Category:** CABLE\
**Tags:** cable4-planning\
**Created:** [17 May 2024 04:06 UTC](https://forum.access-hive.org.au/t/cable-site-runs-with-access-forcing/2108 "2024-05-17T04:06:03Z")\
**Posts on this page:** 3\
**Page:** 3

<div class="post-metadata">

**Author:** ![RachelLaw](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@RachelLaw](https://forum.access-hive.org.au/u/RachelLaw)\
**Post date:** [16 January 2025 22:05 UTC](https://forum.access-hive.org.au/t/cable-site-runs-with-access-forcing/2108/41 "2025-01-16T22:05:25Z")

</div>

At some point, do we also want to look at how different any of the soil properties are between the ESM1.5 era ancillary (which I’m pretty sure is what the offline gridinfo1x1 is based on) and the current AM3 era ancillary? Presumably datasets have improved over the last decade +.

---

<div class="post-metadata">

**Author:** ![clairecarouge](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/clairecarouge/32/380_2.png) [@clairecarouge](https://forum.access-hive.org.au/u/clairecarouge)\
**Post date:** [16 January 2025 22:32 UTC](https://forum.access-hive.org.au/t/cable-site-runs-with-access-forcing/2108/42 "2025-01-16T22:32:14Z")

</div>

@Jhan You are seeing the opposite of what I see. Here is the detail of what I see in `cable_parameters.F90`.

**If `soilparmnew` is True** , the `soil%` variables are set in `write_default_params()` from the `inXXX` variables:

> <https://github.com/CABLE-LSM/CABLE/blob/6d74bdf2fa2876ed5d54056e80eaa74377f46e63/src/offline/cable_parameters.F90#L1360-L1366>

These `inXXX` variables are read in from gridinfo file in `spatialSoil()` (`filename%type` is the namelist entry for the gridinfo file):

> <https://github.com/CABLE-LSM/CABLE/blob/6d74bdf2fa2876ed5d54056e80eaa74377f46e63/src/offline/cable_parameters.F90#L483>

> <https://github.com/CABLE-LSM/CABLE/blob/6d74bdf2fa2876ed5d54056e80eaa74377f46e63/src/offline/cable_parameters.F90#L512-L515>

This seems to make sense since it seems `soilparmnew` is the option that introduced spatially varying soil parameters):

> <https://github.com/CABLE-LSM/CABLE/blob/6d74bdf2fa2876ed5d54056e80eaa74377f46e63/src/offline/cable_parameters.F90#L175-L179>

**If `soilparmnew` is False** , the `soil%` variables are initialised from `soilin%`:

> <https://github.com/CABLE-LSM/CABLE/blob/6d74bdf2fa2876ed5d54056e80eaa74377f46e63/src/offline/cable_parameters.F90#L1512-L1514>

`soilin%` are set from the soil parameter namelist. See the `cable_soil_params()` subroutine:

> <https://github.com/CABLE-LSM/CABLE/blob/6d74bdf2fa2876ed5d54056e80eaa74377f46e63/src/offline/cable_soil_params.F90#L46>

---

<div class="post-metadata">

**Author:** ![Jhan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/jhan/32/721_2.png) [@Jhan](https://forum.access-hive.org.au/u/Jhan)\
**Post date:** [16 January 2025 23:44 UTC](https://forum.access-hive.org.au/t/cable-site-runs-with-access-forcing/2108/43 "2025-01-16T23:44:44Z")

</div>

Yeah you’re right. I was looking at the order of calls in get\_default\_params() The CALL to cable\_soil\_params that reads them from the namelist is “after” the others. I went straight from there to searching where soil%xxx were set and being from inxxx, from a netcdffile I just assumed it was cable\_soilparm.nml. I didnt even check it was filename%type. Odd the order of CALLing get\_default\_params() last though. No desire to follow it. The proof was in the pudding that it was assuming values from grid info.

[Previous page](https://forum.access-hive.org.au/t/cable-site-runs-with-access-forcing/2108.md?page=2)