-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
part of cam6_4_075: Implement parcel_hscale as a namelist parameter in ZM deep convection scheme #1266
Conversation
@@ -2821,6 +2821,7 @@ | |||
<zmconv_tau > 3600.0 </zmconv_tau> | |||
|
|||
<zmconv_parcel_pbl > .false. </zmconv_parcel_pbl> | |||
<zmconv_parcel_hscale phys="cam7" > 0.5 </zmconv_parcel_hscale> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if phys is not cam7? The old logic had this being assigned for every run, so I would suggest removing the phys="cam7"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If phys /= cam7 then zmconv_parcel_pbl = false and zmconv_parcel_hscale is never used. We could simply take out the phys="cam7" right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, removing the phys="cam7"
I believe is the proper fix. (What happens we go to cam8, this variable would have no value?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cacraigucar I just removed the phys="cam7"
option. Please let me know if you want anything else changed!
… scheme (#214) Originator(s): swrneale Description (include issue title and the keyword ['closes', 'fixes', 'resolves'] and issue number): From issue [#203](#203) "Change the 'parcel_hscale' parameter in the ZM convection (zm_conv_intr.F90) to a namelist parameter" This PR is needed in parallel with ESCOMP/cam PR# [1266](ESCOMP/CAM#1266) List all namelist files that were added or changed: M schemes/zhang_mcfarlane/zm_conv_options_namelist.xml - Added new 'zmconv_parcel_hscale' namelist parameter for ZM scheme List all files eliminated and why: N/A List all files added and what they do: N/A List all existing files that have been modified, and describe the changes: (Helpful git command: `git diff --name-status development...<your_branch_name>`) M schemes/zhang_mcfarlane/zm_conv_options.F90 M schemes/zhang_mcfarlane/zm_conv_options.meta - Added new 'zmconv_parcel_hscale' namelist parameter for ZM scheme M schemes/zhang_mcfarlane/zm_convr.F90 M schemes/zhang_mcfarlane/zm_convr.meta - Replace hardcoded 'parcel_hscale' parameter with 'zmconv_parcel_hscale' namelist variable in core ZM scheme (zm_convr). List all automated tests that failed, as well as an explanation for why they weren't fixed: Is this an answer-changing PR? If so, is it a new physics package, algorithm change, tuning change, etc? No If yes to the above question, describe how this code was validated with the new/modified features: --------- Co-authored-by: Jesse Nusbaumer <[email protected]>
…amelist defaults check.
Implement parcel_hscale parameter that is hard coded in the ZM scheme as the namelist parameter zmconv_parcel_hscale. Provide the default value same as that which is currently hard coded (=0.5) so that changes should be bfb.