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
Description:
Year-1700 spin-up and 1701-2023 historical simulations for the TRENDY2024 intercomparison:
1700 ADspinup DONE
1700 SASU DONE
1700 pSASU DONE
1701-2023 HIST: TRENDY identifies this as S3 (S3_irrig because we forgot irrigation in the first iteration); @adrifoster will complete several other simulations, such as Control, S1, and S2.
Case directory:
Locally:
/glade/work/afoster/TRENDY_2024/simulations/TRENDY2024_f09_clm60_ADspinup_20240807-162013
/glade/work/afoster/TRENDY_2024/simulations/TRENDY2024_f09_clm60_ADspinup_matCN_20240809-094159
/glade/work/afoster/TRENDY_2024/simulations/TRENDY2024_f09_clm60_postSASUspinup_20240811-104349
slevis-lmwg
changed the title
TRENDY2024 yr-1700 and historical cases (TRENDY2024_f09_clm60_ADspinup_20240726-144515 followed by SASU, pSASU, HIST)
TRENDY2024 yr-1700 + historical cases with ctsm5.3 fsurdat (TRENDY2024_f09_clm60_ADspinup_20240726-144515 followed by SASU, pSASU, HIST)
Jul 26, 2024
slevis-lmwg
changed the title
TRENDY2024 yr-1700 + historical cases with ctsm5.3 fsurdat (TRENDY2024_f09_clm60_ADspinup_20240726-144515 followed by SASU, pSASU, HIST)
TRENDY2024 yr-1700 + historical cases with ctsm5.3 fsurdat (TRENDY2024_f09_clm60_ADspinup_<date_stamp> followed by SASU, pSASU, HIST)
Jul 31, 2024
@adrifoster when it's time to start SASU, please look at my user_nl_clm here: /glade/u/home/slevis/cases_ctsm5.2/TRENDY2024_f09_ctsm52_SASU_20240729
I don't want to jinx it, but the simulation got past the error and is in progress now. The fix:
I upped the tolerance nnegcrit = -7.d0 from -6, which is what @ekluzek had recommended from the beginning, but I resisted...
In the same user_nl_clm, I changed reseed_dead_plants to false, as I did for SASU in #58
And remember the isotope stuff :-)
I did not include the latter since my simulations are for comparing ctsm5.3 to 5.2 but will not be used beyond that since we're moving to 5.3.
Result from reseed_dead_plants test: I see tiny diffs between my SASU runs with reseed_dead_plants = .true. and .false. so they are NOT bit-for-bit. @adrifoster and I decided to keep it set to .true. in SASU.
From discussion this morning: Let's coordinate what AD year we start SASU from. I've been using yr 300. Let me know if you decide on a different year. @adrifoster decided to extend AD to 400 yrs.
Description:
Year-1700 spin-up and 1701-2023 historical simulations for the TRENDY2024 intercomparison:
Case directory:
Locally:
/glade/work/afoster/TRENDY_2024/simulations/TRENDY2024_f09_clm60_ADspinup_20240807-162013
/glade/work/afoster/TRENDY_2024/simulations/TRENDY2024_f09_clm60_ADspinup_matCN_20240809-094159
/glade/work/afoster/TRENDY_2024/simulations/TRENDY2024_f09_clm60_postSASUspinup_20240811-104349
Sandbox:
Locally:
/glade/work/afoster/TRENDY_2024/CTSM_TRENDY
user_nl_clm
user_nl_datm_streams
SourceMods:
None.
Diagnostics:
https://webext.cgd.ucar.edu/I20TR/TRENDY2024_f09_clm60_S3.2004_2023-TRENDY2024_f09_ctsm52_1700-2023_20240813.2004_2023/setsIndex.html
Output:
Output (if still available):
Initially: /glade/derecho/scratch/afoster/archive/TRENDY2024_f09_clm60_ADspinup_20240804-094339
later: /glade/campaign/cgd/tss/people/afoster/...
Contacts:
@adrifoster @slevis-lmwg
Extra details:
Planned sequence of simulations UPDATE AS NEEDED:
1700AD 320 yrs --> 1700SASU 240 yrs --> 1700pSASU 220 yrs --> hist 1701-2023
The text was updated successfully, but these errors were encountered: