Getting the UFS Weather Model to output physics tendencies #862
Replies: 3 comments 2 replies
-
|
Hi Gerard, Not sure if you've seen WM Discussions #1862 and #1867, but it looks like there are changes that need to be made to the Best, |
Beta Was this translation helpful? Give feedback.
-
|
It looks like the physics tendencies will be output in |
Beta Was this translation helpful? Give feedback.
-
|
@gspetro-NOAA Oh ok. Even if they're 3-D fields and/or not related to the surface? @swomantree and I ended up turning off quilting and looking at the tendencies on the native grid (i.e. in the |
Beta Was this translation helpful? Give feedback.
-
|
@gsketefian Yeah, everyone I've talked to agrees that it doesn't make sense, but that is where the 3-D fields seem to show up! I believe they'll be in there even if not related to the surface, but if any variables seem to be missing, make sure to check other 2-D files (even though they're 3-D fields) before throwing up your hands in confusion. ;) |
Beta Was this translation helpful? Give feedback.
-
|
@gsketefian <https://github.com/gsketefian> I wonder if your bug fix for
outputting the physics tendencies would be helpful for this discussion
<ufs-community/ufs-weather-model#1867>. I
know you helped me fix 4 lines of code so I was able to output those
fv3_history files, and I thought you had made a separate bug/issue report
detailing what you did. I think it's
<#869>this
<#869>fix that did
the trick.
The last post on that discussion said that he tried to turn off quilting
to output those tendencies, but the model crashed. That happened to us as
well, before we turned the ldiag3d and qdiag3d namelist options in the
weather model's namelist on and set quilting to false.
…On Mon, Aug 21, 2023 at 11:21 AM gsketefian ***@***.***> wrote:
@gspetro-NOAA <https://github.com/gspetro-NOAA> Oh ok. Even if they're
3-D fields and/or not related to the surface? @swomantree
<https://github.com/swomantree> and I ended up turning off quilting and
looking at the tendencies on the native grid (i.e. in the fv3_history.nc
file). I'm actually not familiar with the sfc*.nc files (I should read
the other discussions but haven't gotten around to it yet).
—
Reply to this email directly, view it on GitHub
<#862 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZLMKXZOEZ3UZWG5NREY6YDXWOKKNANCNFSM6AAAAAA2O4UZXU>
.
You are receiving this because you were mentioned.Message ID:
<ufs-community/ufs-srweather-app/repo-discussions/862/comments/6783704@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
Hi,
I am trying to get the UFS Weather Model (running through the UFS SRW App) to output physics tendencies. From this page, it seems the way to do this is to change the
ldiag3dandqdiag3dnamelist options to.true.. This should cause the model to output thefv3_history2d.ncand/orfv3_history.ncfiles that will contain the physics tendencies. So I changedldiag3dandqdiag3dto.true.inparm/input.nml.FV3and reran my cases (which are just 4 of the workflow end-to-end tests), but there was no change in the model output, i.e. thefv3_history2d.ncandfv3_history.ncfiles were not generated. I checked theinput.nmlfiles for my experiments, and those do indeed containldiag3dandqdiag3dset to.true.(so that part is working right). Is there something else (maybe indiag_table) that I need to change to get the model to output those history files? Thanks.Beta Was this translation helpful? Give feedback.
All reactions