JSBACH "dynveg" in AWIESM

[ackerlar]

I just recognized, that the use_dynveg in namelist.jsbach is always set to True for AWI-ESM in configs/setups/awiesm/awiesm.yaml. As I understand, the usage of dynamic vegetation is the (main) difference between AWI-CM and AWI-ESM, I find it somewhat misleading and unintuitive that there is the dynamic_vegetations flag that controls the namelist directories for JSBACH but not the actual namelist entries.

I changed this setting in configs/setups/awiesm/awiesm.yaml (#681bcf7) but I am not sure how reasonable that is.

[mandresm]

Hi @ackerlar,

You can see that it's defined as True by default in 681bcf7#diff-12db65fd0e5c14c8c3bef16672a0137ca33026004049cf1eb5334ba81bf03860R246

The reason why it's configured in this way is in case someone wants to deactivate it can simply do in the runscript.yaml:

jsbach:
    dynamic_vegetations: False

instead of

jsbach:
        add_namelist_changes:
                namelist.jsbach:
                        jsbach_ctl:
                            use_dynveg: False

So I'd recommend to leave it as it was because by default is True already.

[ackerlar]

Thanks @mandresm for the reply!

But your suggestion does not work.

jsbach:
    dynamic_vegetations: False

still gives

&jsbach_ctl 
    ...
    use_dynveg = .true.
/

/work/ba0989/a270124/PalModII/experiments/test_dynveg02/scripts/awiesm.yaml
/work/ba0989/a270124/PalModII/experiments/test_dynveg02/run_awiesm_36010101-36011231/work/namelist.jsbach

I guess because it is hard coded in esm_tools/configs/setups/awiesm/awiesm.yaml

Or do I misunderstand something?

[christian-stepanek]

Short update based on my work with 6.43.0:

The following addition to the standard jsbach section of the simulation YAML:

jsbach:
    dynamic_vegetations: False

leads to the following expected change in namelist.jsbach in the work folder:

stepanek@albedo0$ diff namelist.jsbach ../../../PI_dynveg/run_50010101-50011231/work/namelist.jsbach 
16c16
<     use_dynveg = .false.
---
>     use_dynveg = .true.