Skip to content
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

Land use time series for extensions to 2300 #944

Closed
wwieder opened this issue Mar 18, 2020 · 9 comments
Closed

Land use time series for extensions to 2300 #944

wwieder opened this issue Mar 18, 2020 · 9 comments
Assignees
Labels
enhancement new capability or improved behavior of existing capability priority: high High priority to fix/merge soon, e.g., because it is a problem in important configurations science Enhancement to or bug impacting science
Milestone

Comments

@wwieder
Copy link
Contributor

wwieder commented Mar 18, 2020

It looks like we're going to be able to run SSP5-3.4 overshoot and SSP5-8.5 extensions out to 2300 with CESM2. To do this we'll need

  • Land use time series for each scenario that will go into a

  • Compset for each scenario (Jim Edwards may be creating this)

@lawrencepj1 how did you do this for the CESM1 RCP8.5 extension? How do we handle wood harvest and LULCC out to 2300? Let's discuss at the TSS meeting tomorrow.

@lawrencepj1
Copy link

lawrencepj1 commented Mar 18, 2020 via email

@wwieder
Copy link
Contributor Author

wwieder commented Mar 19, 2020

Great, Peter. Can we go ahead a start moving on generating the land use time series for SSP5-34 and SSP5-85? It seems like we'd like to get these simulations running pretty soon.

@wwieder wwieder added priority: high High priority to fix/merge soon, e.g., because it is a problem in important configurations tag: enh - new science labels Mar 19, 2020
@lawrencepj1
Copy link

lawrencepj1 commented Mar 19, 2020 via email

@ekluzek ekluzek self-assigned this Mar 20, 2020
@ekluzek ekluzek added this to the cesm2.1.4 milestone Mar 20, 2020
@ekluzek
Copy link
Collaborator

ekluzek commented Mar 20, 2020

This will go on the release-clm5.0 branch and into the next CESM2.1 release. We'll need to have a compset and test in CTSM for this. And CESM will also need a compset for each.

@lawrencepj1
Copy link

lawrencepj1 commented Mar 20, 2020 via email

@ekluzek
Copy link
Collaborator

ekluzek commented Mar 24, 2020

taxmode in both pop-dens and urbantv are setup to "extend". So we'll run over 2100 for popdens and 2100-2106 for urbantv and they'll both use the last value in the file after they get to the end of the data. ndep is monthly and set to cycle (so for I cases it will loop over the last year of data since it has a seasonal cycle). For cases with WACCM, ndep comes from CAM so it doesn't matter what ndep file is being used.

@ekluzek ekluzek added the branch tag: release Changes go on release branch as well as master label Mar 26, 2020
@wwieder
Copy link
Contributor Author

wwieder commented Mar 31, 2020

@ekluzek is this close to being ready? It looks the the CAM tag is ready to go, so once the land is done @jedwards4b can make the final CESM tag.

@billsacks billsacks added the enhancement new capability or improved behavior of existing capability label Apr 2, 2020
@ekluzek ekluzek removed the branch tag: release Changes go on release branch as well as master label Apr 2, 2020
@ekluzek
Copy link
Collaborator

ekluzek commented Apr 2, 2020

This is on the release branch (release-clm5.0.32). We do NOT plan to bring it to master at least for now.

@ekluzek ekluzek closed this as completed Apr 2, 2020
@lawrencepj1
Copy link

lawrencepj1 commented Apr 2, 2020 via email

@samsrabin samsrabin added the science Enhancement to or bug impacting science label Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new capability or improved behavior of existing capability priority: high High priority to fix/merge soon, e.g., because it is a problem in important configurations science Enhancement to or bug impacting science
Projects
None yet
Development

No branches or pull requests

5 participants