You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently fire-emissions from CTSM into CAM can only work for CN or BGC modes and NOT with FATES. As a longer term goal we need FATES to be able to send fire-emissions from CTSM to the coupler and into CAM-Chem.
@adrifoster noticed that the namelist build doesn't ensure these two can't be turned on together, and as a result cases fail in a hard to understand way. So she is going to remedy this.
thanks @ekluzek this is the error I got for a test that erroneously had -fire_emis and use_fates
cat /scratch/cluster/afoster/tests_0126-104846iz/SMS_D_Mmpi-serial.CLM_USRDAT.I1PtClm51Fates.izumi_nag.clm-default--clm-NEON-FATES-NIWO.GC.0126-104846iz_nag/run/cesm.log.589551.izumi.cgd.ucar.edu.230126-115716
Runtime Error: /home/afoster/CTSM/src/biogeochem/FireEmisFactorsMod.F90, line 76: Subscript 1 of FACTORS (value 16) is out of range (1:14)
Program terminated by fatal error
So I added this check but now thisfates test is failing on build because -fire_emis is used (from one of the default clm includes user mods).
One solution would be to grab what is needed from the mimics/clm includes chain and put in this testmod dir. Otherwise I'm not sure how to get around using the necessary mimics, clm, and fates options. @ekluzek can you advise?
Hoping to finish #1932 soon and don't want to keep adding too much to it that is outside the scope of FATES-NEON stuff.
Change the include order so that FATES is last and overrides the other settings (and explicitly set CLM_BLDNML_OPTS)
Have a mimics base test-mod that doesn't include the default that can be used by both CTSM-BGC and FATES
Duplicate the mimics test-mod for FATES
Since, right now all that the mimics test mode does is include: default and Cold-Start and sets one namelist variable. I think we should do "3". So the FATES test mod wouldn't reference the other one, but just set
Activity
glemieux commentedon May 19, 2022
Reviewing issues I believe this is related to NGEET/fates#163
ekluzek commentedon Jan 26, 2023
@adrifoster noticed that the namelist build doesn't ensure these two can't be turned on together, and as a result cases fail in a hard to understand way. So she is going to remedy this.
adrifoster commentedon Jan 26, 2023
thanks @ekluzek this is the error I got for a test that erroneously had
-fire_emis
anduse_fates
adrifoster commentedon Jan 30, 2023
So I added this check but now this
fates
test is failing on build because-fire_emis
is used (from one of the default clm includes user mods).One solution would be to grab what is needed from the mimics/clm includes chain and put in this testmod dir. Otherwise I'm not sure how to get around using the necessary
mimics
,clm
, andfates
options. @ekluzek can you advise?Hoping to finish #1932 soon and don't want to keep adding too much to it that is outside the scope of FATES-NEON stuff.
ekluzek commentedon Feb 1, 2023
I see a couple ways to handle this:
Since, right now all that the mimics test mode does is include: default and Cold-Start and sets one namelist variable. I think we should do "3". So the FATES test mod wouldn't reference the other one, but just set
soil_decomp_method = 'MIMICSWieder2015'
explicitly in it.
10 remaining items