Turn off deep convection?

[benjamin-cash]

We are running a test of the model at C3072 and would like to turn off the deep convection scheme. Our first attempt was:
do_deep = .false.
imfdeepcnv = -1 (was =2)
ras = .false.

However, that left the results entirely unchanged. What do we need to do to turn off deep convection?

[pjpegion]

I suspect you will need to modify the suite definition file you compile with:
try removing these lines...

  <scheme>GFS_DCNV_generic_pre</scheme>
  <scheme>samfdeepcnv</scheme>
  <scheme>GFS_DCNV_generic_post</scheme>

[benjamin-cash]

Thanks @pjpegion. Are those changes in addition to the namelist changes?

[pjpegion]

To be safe, yes. I don't understand the interplay between the suite definition files and the namelist options.

[ShawnCebulaNOAA]

@benjamin-cash Did this fix the issue? Please let me know!

Shawn Cebula - EPIC End User Support

[benjamin-cash]

Hi @ShawnCebulaNOAA - We ended up abandoning this approach for other reasons so it ended up not being relevant.

[junwang-noaa]

The suite_FV3_GFS_v15_thompson_mynn_lam3km.xml used by regional high resolution runs has the connection turned off, maybe you can use it as a reference. You do need the namelist changes too.

…

On Fri, Nov 12, 2021 at 10:47 AM Phil Pegion ***@***.***> wrote: To be safe, yes. I don't understand the interplay between the suite definition files and the namelist options. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#912 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI7D6TLFRLRWTBNZSK7MFI3ULUZJZANCNFSM5H5DSPQA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[benjamin-cash]

Doing cleanup on my old questions - going to mark this as answered. Although we never did figure out how to do it we've moved on to other efforts.