Skip to content

ctsm5.4.000: Update to CMIP7 LULCC forcings #2851

Closed
2 of 2 issues completed
Closed

Description

@wwieder

It looks like a preliminary dataset for LULCC is available for CMIP7 (scroll down the table with links)

Specifically, is the v3.0 dataset any different that what we're already using from TRENDY?
This github page could be helpful for tracking changes / updates to the dataset.

If this dataset is different from TRENDY, we should migrate to the latest v3 data so we're testing the model with LULCC data that's hopefully consistent with the final CMIP7 data.

@lawrencepj1 can you have a look at this dataset to see if it's different that what we've already integrated into the 5.3 tag?

Definition of Done:

Activity

  1. added
    enhancementnew capability or improved behavior of existing capability
    investigationNeeds to be verified and more investigation into what's going on.
    on Oct 29, 2024
  2. added this to the ctsm5.4.0 milestone on Oct 29, 2024
  3. samsrabin commented on Oct 29, 2024

    @samsrabin
    Member

    See also: This brief slide deck with some info from Louise Chini; there's also a recording of her talk here.

  4. wwieder commented on Oct 29, 2024

    @wwieder
    ContributorAuthor

    And this note from @ckoven on the FATES side

  5. lawrencepj1 commented on Oct 29, 2024

    @lawrencepj1

    Hi Everyone
    Just for reference this is actually "CMIP6Plus" based on the CMIP Forcings meeting this morning. It is a test version that will be updated if needed to CMIP7 in 2025.

    https://wcrp-cmip.org/wp-content/uploads/2024/10/2024-10-29_Forcings-drop-in_session.pdf

    That said I am very happy to start going through the LUH3 data and getting CTSM53 raw PFT data generated from the new data.
    Thanks
    Peter

  6. olyson commented on Oct 29, 2024

    @olyson
    Contributor

    Since we now have dynamic urban capability, I wonder if we should include urban in this version. I'm not sure what was done with urban previously in CMIP6, maybe it was assigned to some other landunit?

  7. lawrencepj1 commented on Oct 29, 2024

    @lawrencepj1

    Hi @olyson

    Urban is transient in the LUH data and the values from LUH are explicitly put into the raw CLM5 and CTSM53 PFT data. Mksurfdata however does not use the raw PCT_URBAN data. There is a lot more information required for CTSM than provided by LUH so it would not be useful as a source for final surface or landuse timeseries data.

    Cheers
    Peter

  8. olyson commented on Oct 29, 2024

    @olyson
    Contributor

    Thanks @lawrencepj1 . I was thinking that a simple and reasonable thing to do would be to use the PCT_URBAN supplied by LUH and assign it to a single density type (medium density, as that is by far the most common) and then simply splice in the static-in-time urban properties, which don't depend on PCT_URBAN and just depend on density type and region, into those files. We would end up with raw files that have the same information in them as we do now.
    If you have a sample raw CLM5/CTSM53 file, I could experiment with that.

  9. lawrencepj1 commented on Oct 29, 2024

    @lawrencepj1

    Hi @olyson

    Yes not a problem at all. You can find the latest TRENDY and LUH derived CTSM53 raw data at:

    /glade/campaign/cesm/development/lmwg/landuse_source_data/CTSM53RawData

    SSP5-8.5 has the largest urban expansion of the future scenarios. Here is 2015 vs 2100 values from these two raw files:

    globalctsm53TRSSP585Deg025_240728/mksrf_landuse_ctsm53_TRSSP585_2015.c240728.nc
    globalctsm53TRSSP585Deg025_240728/mksrf_landuse_ctsm53_TRSSP585_2100.c240728.nc

    image

    Peter

  10. olyson commented on Oct 29, 2024

    @olyson
    Contributor

    Thanks @lawrencepj1 !

  11. 46 remaining items

  12. moved this from Stalled to In Progress in LMWG: Sprint Planning Boardon Oct 22, 2025
  13. changed the title [-]Update to CMIP7 LULCC forcings[/-] [+]ctsm5.4.000: Update to CMIP7 LULCC forcings[/+] on Oct 30, 2025
  14. moved this to Ready to start (or start again) in CTSM: Upcoming tagson Oct 30, 2025
  15. moved this from Ready to start (or start again) to Stalled (needs review, blocked etc.) in CTSM: Upcoming tagson Oct 30, 2025
  16. moved this from Stalled (needs review, blocked etc.) to In progress - master in CTSM: Upcoming tagson Oct 30, 2025
  17. slevis-lmwg commented on Dec 4, 2025

    @slevis-lmwg
    Contributor

    For Sprint accounting purposes I am marking this done, while I work on final steps in PR #3638

    This issue will close when we merge #3638

  18. moved this from In Progress to Done in LMWG: Sprint Planning Boardon Dec 4, 2025
  19. added
    doneIssues whose closing PR is done but not yet merged (pending test re-run ok)
    on Dec 4, 2025
  20. moved this from In progress - master to Done (non release/external) in CTSM: Upcoming tagson Dec 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

blocked: dependencyWait to work on this until dependency is resolveddoneIssues whose closing PR is done but not yet merged (pending test re-run ok)enhancementnew capability or improved behavior of existing capabilityinvestigationNeeds to be verified and more investigation into what's going on.priority: highHigh priority to fix/merge soon, e.g., because it is a problem in important configurations

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions