-
Notifications
You must be signed in to change notification settings - Fork 251
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
A MERRA2 aerosol interpolation bug was found by RRFS #2082
Conversation
Here is the log file for the regression tests. All test with use_Merra2=T and iaer=1011 passed. A few tests related conus13k failed with use_Merra2=F and iaer=1011 options, which does not make sense, because iaer asks for reading MERRA2 data, but use_Merra2 turn off the data access. |
use_merra2 is overwritten by the regional*.IN and rrfs*IN files in directory fv3_conf. use_merra2=T was dded in conus13km_control to avoid confusion. The issue of the failed tests is related to the bug fixed. A simple tests is done by adding the following line in /scratch1/NCEPDEV/global/Anning.Cheng/ufs-weather-model_wk/FV3/ccpp/physics/physics/MP/Morrison_Gettelman/aerinterp.F90 On the whole, The regression tests in Hera are successful and the code is in good shape to be merged into the trunk . New baselines are needed in all conus_13km related RT tests. |
@AnningCheng-NOAA can you sync up the branch? we will start working on this pr once the branches are synced up. |
Jong, done
…On Thu, Jan 11, 2024 at 5:32 PM JONG KIM ***@***.***> wrote:
@AnningCheng-NOAA <https://github.com/AnningCheng-NOAA> can you sync up
the branch? we will start working on this pr once the branches are synced
up.
—
Reply to this email directly, view it on GitHub
<#2082 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALQPMINEOYYKOX7ZW7ADGS3YOBR6NAVCNFSM6AAAAABBSJBOJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBYGA3TGNZRGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@AnningCheng-NOAA I synced up CICE/MOM6/Stochastic-physics hashes. Files changed look ok now. Can you confirm? |
Looks good now.
…On Thu, Jan 11, 2024 at 8:51 PM JONG KIM ***@***.***> wrote:
@AnningCheng-NOAA <https://github.com/AnningCheng-NOAA> I synced up
CICE/MOM6/Stochastic-physics hashes. Files changed look ok now. Can you
confirm?
—
Reply to this email directly, view it on GitHub
<#2082 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALQPMIMG62MTLOQYSKH2S6DYOCJJRAVCNFSM6AAAAABBSJBOJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBYGI4DQNRUHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@BrianCurtis-NOAA @zach1221 @FernandoAndrade-NOAA This pr is ready. conus 13km cases change. |
@AnningCheng-NOAA I updated commit messages above. Please, feel free to add or change the commit messages. |
@AnningCheng-NOAA You should update the FV3 hash in your UWM PR branch now that you merged the CI change. |
Denise: Could you give me some instructions on how to update the hash?
…On Fri, Jan 12, 2024 at 3:09 PM Denise Worthen ***@***.***> wrote:
@AnningCheng-NOAA <https://github.com/AnningCheng-NOAA> You should update
the FV3 hash in your UWM PR branch now that you merged the CI change.
—
Reply to this email directly, view it on GitHub
<#2082 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALQPMIMS7BL4ABQBAIT27ELYOGKABAVCNFSM6AAAAABBSJBOJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBZHA4DSMRZGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
In your UWM branch, you just need to pull in the update to FV3 and then add it. You should see (git status) something like this
so git add then git commit. Make sure the FV3 hash in your UWM branch is 1042921 |
done. Thank you! Denise
…On Fri, Jan 12, 2024 at 3:41 PM Denise Worthen ***@***.***> wrote:
In your UWM branch, you just need to pull in the update to FV3 and then
add it.
You should see (git status) something like this
modified: FV3 (new commits, untracked content)
so git add then git commit.
Make sure the FV3 hash in your UWM branch is 1042921
—
Reply to this email directly, view it on GitHub
<#2082 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALQPMIN2YAMGPMWM2RBGUO3YOGNVXAVCNFSM6AAAAABBSJBOJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBZHEZDENJTHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
All tests are done. We can start merging process. |
@AnningCheng-NOAA can you update fv3 hash? correct one is NOAA-EMC/fv3atm@095a1d5 |
done, Jong
…On Tue, Jan 16, 2024 at 12:19 PM JONG KIM ***@***.***> wrote:
@AnningCheng-NOAA <https://github.com/AnningCheng-NOAA> can you update
fv3 hash? correct one is ***@***.***
<NOAA-EMC/fv3atm@095a1d5>
—
Reply to this email directly, view it on GitHub
<#2082 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALQPMIIYFS22ATBETL3Y3YTYO2ZANAVCNFSM6AAAAABBSJBOJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJUGE3TQNRXGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@DusanJovic-NOAA we have one thing to clear on fv3 develop commit. @AlexanderRichert-NOAA committed NOAA-EMC/fv3atm@138aab1 and @AnningCheng-NOAA synced against that hash. But My question is if it's ok to bring in the change. @BrianCurtis-NOAA @zach1221 @FernandoAndrade-NOAA FYI |
Sorry, what exactly is the issue with NOAA-EMC/fv3atm@138aab1, what do we need to clear? |
No issue but to make sure we are synching with the hash. |
Commit Queue Requirements:
PR Information
Description
Commit Message
Priority
Blocking Dependencies
Git Issues Fixed By This PR
Changes
Subcomponent (with links)
Input data
Regression Tests:
New baselines are needed for all conus_13km related tests. Namely:
conus13km_2threads conus13km_debug conus13km_debug_decomp conus13km_decomp conus13km_restart
conus13km_control conus13km_debug_2threads conus13km_debug_qr conus13km_radar_tten_debug conus13km_restart_mismatch
FAILED REGRESSION TESTS
Libraries
Testing Log: