-
Notifications
You must be signed in to change notification settings - Fork 374
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
Fixing a bug causing floating-point error in RtmMod.F90 #6146
Fixing a bug causing floating-point error in RtmMod.F90 #6146
Conversation
…wo way coupling is on
@liho745 is this BFB or non-BFB ? |
I'd say it is BFB, but did not run a full developer test since it is only a
bug fix.
…On Thu, Jan 18, 2024 at 11:28 PM Robert Jacob ***@***.***> wrote:
@liho745 <https://github.com/liho745> is this BFB or non-BFB ?
—
Reply to this email directly, view it on GitHub
<#6146 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC5QWBRM5MG4M7IL3IYLIJ3YPH767AVCNFSM6AAAAABBVWMVZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJZG44TINBTHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@liho745 you should see if its BFB. You could just run one test. |
@rljacob Three MOSART related tests all passed BFB on Compy: ERS.MOS_USRDAT.RMOSGPCC.compy_intel.mosart-mos_usrdat; ERS.r05_r05.RMOSGPCC.compy_intel.mosart-gpcc_1972; SMS.MOS_USRDAT.RMOSGPCC.compy_intel.mosart-unstructure. So, the bug fix should be BFB. |
great! @bishtgautam you can start merging this. |
I re-merged another MOSART PR (#6092) today. I will merge this PR tomorrow, provided nightly tests look good tomorrow. |
A bug in RtmMod.F90 has been causing a floating-point error, related to Tunit%rlen, when the land-river two-way coupling is invoked. This PR fixes that bug based on a branch off the commit, 417920b, where the bug was introduced into the master. [BFB] Fixes #5540
A bug in RtmMod.F90 has been causing a floating-point error, related to Tunit%rlen,
when the land-river two-way coupling is invoked. This PR fixes that bug based on
a branch off the commit, 417920b, where the bug was introduced into the master.
[BFB]
Fixes #5540