-
Notifications
You must be signed in to change notification settings - Fork 252
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
Allow instantaneous SW and LW fluxes to be used when cpllnd=.true. #1943
Allow instantaneous SW and LW fluxes to be used when cpllnd=.true. #1943
Conversation
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.
@DeniseWorthen At this point I am not using inst_down_lw_flx
and inst_down_sw_flx
in NoahMP cap but using Faxa_swdn
and Faxa_lwdn
which are pointing mean values. Since, all the components under UFS Weather Model are switching to instantaneous fields, maybe NoahMP needs to switch those. Let me know what you think?
@DeniseWorthen Do you also plan to do changes in |
@uturuncoglu Yes, there is a follow-on #1942 to this one which will switch the remaining field aliases to be |
@DeniseWorthen Okay. Thanks for the clarification. I think this PR good to go. In any case, I don't think but if I had issue in the land PR, I could fixed in there. |
@uturuncoglu I think it would be good to clean up the un-used fields in the |
@DeniseWorthen I could not see the place that land uses the banded SW down. Could you point me the code? Maybe this is already fixed in my PR but not sure. It would be nice to double check. |
@uturuncoglu I was looking at In your original commit to add the land component, these got moved from just a cpflx block into the cplflx or cpllnd block. These are actually the net SWs---I called them the down SWs by mistake. |
@DeniseWorthen Okay. Those are not used by land and it is not required by NoahMP. In the sbs (and also fully coupled - in the outstanding PR) configuration FV3 is not coupled with ocean and only coupled by land (so, in this case cplflx = false but cpllnd = true) and maybe those parts are only required to satisfy some internal logic in the FV3 side since it was assuming that cplflx is always true if it is coupled. Does it makes sense? |
I'm a little confused, myself. Originally (prior to your first land PR), those fields were only in the cplflx block. But, they're actually not needed when coupling to ocean either (swnet is only needed by HAFS). I can try moving them back to the cplflx block and see if I can get a failure. |
39b029e
to
fb788ba
Compare
This PR should not have been closed. This happens when you mistakenly 'sync' to develop on github and it discards the commits that are actually present in the PR. |
Re-opening |
I guess I can't re-open. I will need to re-create. |
PR Author Checklist:
Description
Allows SW and LW instantaneous export fields for when coupled to external land component.
Linked Issues and Pull Requests
Associated UFSWM Issue to close
Subcomponent Pull Requests
Blocking Dependencies
Subcomponents involved:
Anticipated Changes
Input data
Regression Tests:
Tests effected by changes in this PR:
Libraries
Code Managers Log
Testing Log: