As requested by paogorman the way we currently trigger the YOG parameterisation as an option to deep_scheme is not ideal, as longer-term YOG may become its own scheme covering more aspects.
There is also a danger that we incur some double counting with certain aspects of convect_deep being run under the hood.
The ideal situation would be to have a separate switch for YOG, and run with deep_scheme='off'.
To do this we need to advust the current changes to xml namelist variables:
Remove YOG as an option for deep_scheme
Add a separate switch for the YOG scheme to the xml and namelist
create a YOG namelist for the yog-specific parameters (sounding and weights filepaths)
change the in-code conditionals to use this new switch
As requested by paogorman the way we currently trigger the YOG parameterisation as an option to
deep_scheme
is not ideal, as longer-term YOG may become its own scheme covering more aspects.There is also a danger that we incur some double counting with certain aspects of
convect_deep
being run under the hood.The ideal situation would be to have a separate switch for YOG, and run with
deep_scheme='off'
.To do this we need to advust the current changes to xml namelist variables:
deep_scheme
deep_scheme='off'