USE_MERRA_CLIMO option #1002
-
Hi, UFS/SRW experts - I'm runing SRW v2.2 over NE US for 2023 June period. LBCs and ICs are taken from GFS. In FV3.merra.input.yml, I set iaer to 1011 for the GFS_v16 suite. The results are quite reasonable. While my approach works, I'm just wondering whether there is a better/smarter way to change namelist variable? Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Hi @SarahLu-NOAA , The USE_MERRA_CLIMO parameter generally should only be set to true with physics suites that support MERRA2 climatology and Thompson microphysics (i.e., FV3_GFS_v15_thompson_mynn_lam3km or FV3_GFS_v17_p8 physics suites). I don't believe the FV3_GFS_v16 physics suite was updated to support MERRA2 climatology and Thompson microphysics, either, so it is concerning that you were able to achieve reasonable results using a physics suite that doesn't support MERRA2 but encountered issues with a physics suite that should support it (although FV3_GFS_v17_p8 is not supported/tested with the SRW App, which could partially explain the issue). Regardless, these are interesting results, and I've reached out to some of our SMEs to investigate. Since FV3_GFS_v16 is not configured to use MERRA2 climatology, I believe you do need to make any desired changes manually in the YAML file, but the CCPP team generally cautions against using untested and unverified combinations of physics (this is part of why it is not easily configurable). That said, informed experimentation can lead to innovation! I'm hoping @mkavulich can weigh in with thoughts/suggestions, but regardless, it would be good to touch base with the CCPP physics team, too. I will see if I can get an SME to follow up with you after the weekend with more information. Best, |
Beta Was this translation helpful? Give feedback.
-
Hi @SarahLu-NOAA ! I know we have some developers taking a look at the related issue you posted (Issue #1004 ), so I will close this discussion and let @ulmononian and others continue to troubleshoot the issue there. :) |
Beta Was this translation helpful? Give feedback.
A bugfix addressing the contents of this discussion was added via PR #1055 .