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 +.
@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:
These inXXX variables are read in from gridinfo file in spatialSoil() (filename%type is the namelist entry for the gridinfo file):
This seems to make sense since it seems soilparmnew is the option that introduced spatially varying soil parameters):
If soilparmnew is False, the soil% variables are initialised from soilin%:
soilin% are set from the soil parameter namelist. See the cable_soil_params() subroutine:
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.