-
Notifications
You must be signed in to change notification settings - Fork 312
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
Add a transient FATES compset alias and make sure do_transient settings are correct by default for FATES #1617
Comments
I've been uinsg 2000_DATM%GSWP3v1_CLM50%FATES_SICE_SOCN_SROF_SGLC_SWAV and recently switched to 2000_DATM%GSWP3v1_CLM50%FATES_SICE_SOCN_RTM_SGLC_SWAV because it is more similar to what can be done with anomaly forcing. I'd be interested to know what might be wrong with this. I've never been able figure out if I should be using 1850_DATM for historical transients. Frankly I don't fully understand with that specifically changes. The example case uses a compset that hasn't worked in some time (I2000Clm50FatesGs). |
@JoshuaRady I edited the example to use I2000Clm50FatesRs, which is one that exists now. The difference between the two compsets you give above is just adding the RTM river model rather than the stub-river. This would only be helpful if you are actually going to look at your RTM output and compare to streamflow for example. So I suspect you would be better off with the stub-river. If you aren't looking at the output, you might as well save a little bit of CPU time. The "2000" at the beginning is the "period" to simulate for. So 2000 means year 2000, and 1850 means pre-industrial for year 1850. A transient case is HIST for Historical. And there's also options for the future scenarios SSP-RCP which are transient simulations also that go up to year 2100. What this part changes is some of the DATM_* and CLM_* XML case settings, which then get reflected in the namelists. Does that help? |
Thanks for updating the example case. I don't need the RTM data currently but had problems getting the SROF to work with anomaly forcing. @jkshuman turned me on to using RTM. An example anomaly compset that works for me is SSP585_DATM%GSWP3v1_CLM50%FATES_SICE_SOCN_RTM_SGLC_SWAV. I understood what the descriptors mean but not all the settings that make them different. |
Here's how I think this should work: |
Transient simulations are started to be done for FATES. We should add an alias for this and also make sure the namelist is setup to work by default so that do_transient_pfts is FALSE.
The text was updated successfully, but these errors were encountered: