In #4029 @ekluzek wrote:
I'm assuming that we only expect use_hillslope to be used with CRUJRA24b forcing.
The other part here is that this might come into play in how lnd_tuning_mode is handled in buildnml. At least in how it's reported. I should probably think about that and file an issue if it looks like we should make changes there. That would be an update that comes in later.
But, it basically shows that lnd_tuning_mode now is going to be different for the hillslope model than for the default flat model. And we probably aren't going to tune the hillslope model for as many configurations as the flat model. So that is likely something we'll want documented and the user to be aware of.
I forget if namelist items are default last or first. But, if you were to run coupled with LND_TUNING_MODE==clm6_0_cam7.0 and hillslope on -- I'm not sure what you will get. Nor am I sure what you'd want to get for that case either.
That could be something to decide on. To make it clear you could also add:
lnd_tuning_mode="clm6_0_crujra" to the attributes for the hillslope case to make it clear. But, it also depends on which file we think we want to have set for a hillslope case using different LND_TUNING_MODE.
And @wwieder wrote:
Thanks for all these thoughts, @ekluzek. I agree there is a lot of potential complication here. We should try to keep it simple as much as possible by narrowly defining what we'll support (e.g. CLM6_CRUJRA_HH compset)?
In #4029 @ekluzek wrote:
I'm assuming that we only expect use_hillslope to be used with CRUJRA24b forcing.
The other part here is that this might come into play in how lnd_tuning_mode is handled in buildnml. At least in how it's reported. I should probably think about that and file an issue if it looks like we should make changes there. That would be an update that comes in later.
But, it basically shows that lnd_tuning_mode now is going to be different for the hillslope model than for the default flat model. And we probably aren't going to tune the hillslope model for as many configurations as the flat model. So that is likely something we'll want documented and the user to be aware of.
I forget if namelist items are default last or first. But, if you were to run coupled with LND_TUNING_MODE==clm6_0_cam7.0 and hillslope on -- I'm not sure what you will get. Nor am I sure what you'd want to get for that case either.
That could be something to decide on. To make it clear you could also add:
lnd_tuning_mode="clm6_0_crujra" to the attributes for the hillslope case to make it clear. But, it also depends on which file we think we want to have set for a hillslope case using different LND_TUNING_MODE.
And @wwieder wrote:
Thanks for all these thoughts, @ekluzek. I agree there is a lot of potential complication here. We should try to keep it simple as much as possible by narrowly defining what we'll support (e.g. CLM6_CRUJRA_HH compset)?