Skip to content

ctsm5.3.032: Add CRU-JRA as option for datm inputs for CTSM development #1895

Closed
1 of 1 issue completed
Closed

Description

@wwieder

Should we consider updating to CRUJRA as our default forcing for CTSM development?

Brief +/- here:

  • Positive here are that these are the input data used for TRENDY simulations and updated annually (and currently available through 2021, vs. GSWP3, which ends in 2014).
  • Negatives are that each year it seems like the dataset is slightly modified. We may not what to update our input data this often.

Considerations:

  • We need some assessment of what results look like with these simulations, but @djk2120 has CLM50 runs for TRENDY;
  • We should update to CTSM5.1 / 5.2 branch and spin up new initial conditions, which would be helpful to discuss with @olyson and the rest of the LMWG/CLM team.
  • This also will require developing some infrastructure / storage to support a new input dataset that @ekluzek can inform.
  • @swensosc also noted CRU-JRA is 6 hourly data, whereas GSWP3 is 3 hr resolution.
  • @olyson noted there's not data for Antarctica with CRU-JRA, complicating evaluation.

There have been a number of conversations on this related to:

We can have discussion on this thread, but I also suggest we discuss at an upcoming Thursday science meeting (maybe next week)?


Updated Nov 20, 2024

In the absence of other options of datm data to bring us through present day, we're calibrating CLM6 with CRU-JRA forcing. A few notes related to outstanding tasks

Definition of done

Activity

  1. added
    nextthis should get some attention in the next week or two. Normally each Thursday SE meeting.
    enhancementnew capability or improved behavior of existing capability
    on Nov 10, 2022
  2. wwieder commented on Nov 14, 2022

    @wwieder
    ContributorAuthor

    @djk2120 noted that the forcing is available here:
    /glade/campaign/asp/djk2120/TRENDY2022/forcing

  3. djk2120 commented on Nov 14, 2022

    @djk2120
    Contributor

    latest TRENDY from GCB-2021:
    /glade/campaign/asp/djk2120/TRENDY2022/S3/lnd

    based on:
    branch_tags/TRENDY-2019.n05_ctsm1.0.dev056

  4. wwieder commented on Nov 14, 2022

    @wwieder
    ContributorAuthor

    @olyson can you run diagnostics (and ILAMB) on these results? Does it make the most sense to compare them with results from the CLM5.0-GWSP3 runs that were done for the CLM5 release?

  5. olyson commented on Nov 14, 2022

    @olyson
    Contributor

    Either that or the more recent CLM5 simulation I did with the PPE tag: cesm2_3_alpha02c_PPE.n08_ctsm5.1.dev030

    for our comparison with "CTSM5.1":

    https://github.com/ESCOMP/CTSM/wiki/CLM5-CTSM5.1-Simulations

  6. olyson commented on Nov 14, 2022

    @olyson
    Contributor

    Either way, I'll need permissions set on Daniel's directory to at least be able to read/copy the files on campaign store. Currently they are set to "asp" group which I don't have permissions for.

    drwxr-s---+ 11 djk2120 asp 4096 Oct 12 11:33 TRENDY2022

  7. wwieder commented on Nov 15, 2022

    @wwieder
    ContributorAuthor

    Yep the CTSM5.1.dev030 tag is also a good candidate, Keith. Dealers choice. Again, our main goal here will be to start learning big difference in the forcing data and what differences we may expect at initialization and in historical trajectories. Down the road we'll do a clean run with a modern tag and both forcing datasets assuming there's no obvious flaws in CRU-JRA

  8. olyson commented on Nov 16, 2022

    @olyson
    Contributor

    There are standard diagnostics here.
    And ILAMB results here.
    Having run those and looking at some plots I realize now that this comparison isn't going to be very useful. Mainly because CRUJRA doesn't have data over Antarctica (consequently the datm interpolates data from more northern latitudes), so CRUJRA has much poorer scores than GSWP3V1 in ILAMB, and the contour plots in the standard diagnostics have color bar scalings that wash out differences that are not over Antarctica.
    Maybe some of the northern hemisphere trend plots are useful.

  9. added
    priority: lowBackground task that doesn't need to be done right away.
    and removed
    nextthis should get some attention in the next week or two. Normally each Thursday SE meeting.
    on Jan 26, 2023
  10. wwieder commented on Jan 26, 2023

    @wwieder
    ContributorAuthor

    I've learned that JRA is no longer going to be continue / supported, which makes me think that CRU-JRA, as used in TRENDY will be of limited utility moving forward. The need for updated datm data is going to be a need for multiple CESM communities (ocean and atm use JRA for initialization in the ESPWG). At this point I suggest we wait to see what the TRENDY migrates to or consider a larger effort to generate these input data. @billsacks mentioned that Kevin R in DART suggested they may be a data product that could serve this need.

  11. klindsay28 commented on Jan 26, 2023

    @klindsay28

    FYI, with the upcoming stoppage in JRA support, the ocean community is also faced with deciding how to move forward. My understanding, based on conversations w/ Gokhan Danabasoglu, is that the ocean community is leaning towards using ERA5 from ECMWF. The forcing spans 1940 to present day, and ECMWF seems committed to updating it. I don't know if this forcing meets the needs for CTSM/CLM. It seems prudent for conversations within CESM on moving forward to include folks from both the LMWG and OMWG, to ensure coordination, where it is possible.

  12. dlawrenncar commented on Jan 26, 2023

    @dlawrenncar
    Contributor
  13. 31 remaining items

  14. moved this from Ready to start (or start again) to In progress - master/b4b-dev in CTSM: Upcoming tagson Feb 10, 2025
  15. changed the title [-]Update to CRU-JRA as default datm inputs for CTSM development[/-] [+]Add CRU-JRA as option for datm inputs for CTSM development[/+] on Feb 11, 2025
  16. wwieder commented on Feb 20, 2025

    @wwieder
    ContributorAuthor

    This PR is waiting on cdeps tag from @jedwards4b and another review from @ekluzek

  17. changed the title [-]Add CRU-JRA as option for datm inputs for CTSM development[/-] [+]ctsm5.3.031: Add CRU-JRA as option for datm inputs for CTSM development[/+] on Mar 6, 2025
  18. changed the title [-]ctsm5.3.031: Add CRU-JRA as option for datm inputs for CTSM development[/-] [+]ctsm5.3.032: Add CRU-JRA as option for datm inputs for CTSM development[/+] on Mar 13, 2025
  19. moved this from In progress - master/b4b-dev to Done (non release/external) in CTSM: Upcoming tagson Mar 17, 2025
  20. moved this from On the grill (work in progress) to Ready to eat (Done!) in CTSM-CLM6 development highlightson Mar 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementnew capability or improved behavior of existing capabilitytest: aux_clmPass aux_clm suite before merging

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions