-
Notifications
You must be signed in to change notification settings - Fork 324
branch with 5.3.042: Make sure FORTRAN code properly aborts when fire-emission is asked for and it can't be provided #2844
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
base: cesm3_0_beta04_changes
Are you sure you want to change the base?
Conversation
…y fail as expected
…FATES, and also off when coupled to CAM
… initialization of the CNFireNorFire class
… initialization of the CNFireNorFire class
…lude tests that test that fire emission on with nofire or SP fail, which right now they don't as expected
…endrun calls for unit testing
…hat checks that fire-emission is off for fire_method==nofire
…d FireReadNML is called seperate from FireInit
…s done as a loop. Also add a li2024crujra test, this is in response to code review
…it tests fail this way
Get the FATESFireFactory tests working again now that it aborts with fire-emission on.
Correct the build-namelist option for --no-fire_emis. And also add more comments around this.
@erik seems to have addressed review comments, dissmising this as resolved
Fire initialization needed some tweaks due to the refactoring worked out in the unit testing.
These tests fail on setup because they are using fire-emis with SP cases. So I'll reconfigure these tests to make sure the testmods used include nofireemis. ERP_D_Ld3_PS.f09_g17.I2000Clm50Sp.derecho_intel.clm-prescribed (SETUP) |
Error caught on Izumi for initialization with: SMS_Ld10_D_Mmpi-serial.CLM_USRDAT.I1PtClm60Fates.izumi_nag.clm-FatesPRISM--clm-NEON-FATES-YELL.GC.ctsm5341acl_nag This is partially due to what I point out in #3078
|
The izumi tests that have the problem above are: ERI_D_Ld20.f10_f10_mg37.I2000Clm50Fates.izumi_nag.clm-FatesCold (RUN) There were some build fails, that I've been successful with just resending the build with: ERP_D_Ld5_P48x1.f10_f10_mg37.I1850Clm50Bgc.izumi_nag.clm-ciso (SHAREDLIB_BUILD) |
Description of changes
Changes in the FORTRAN code to properly abort when fire-emission is asked for it can't be provided.
To develop this a PF unit test for CNFireFactoryMod is added in.
Specific notes
Contributors other than yourself, if any:
CTSM Issues Fixed (include github issue #):
Fixes #2762
Fixes #3073
CTSM namelist checking for: NGEET/fates#1356
Some work on #2643
Are answers expected to change (and if so in what way)? No
Any User Interface Changes (namelist or namelist defaults changes)? No
Does this create a need to change or add documentation? Did you do so? No
Testing performed, if any: Currently just the PF unit tests will run regular testing when done.