Skip to content

Example, user_nl_datm_streams file for anomaly forcing for NUOPC coupler #1730

Description

@ekluzek

We need an example user_nl_datm_streams file for anomaly forcing for the NUOPC coupler. @wwieder has a test case to base this off of here:

/glade/work/wwieder/ctsm/ctsm5.1.dev054/cime/scripts/NEON_NIWO54_mm_zbed1.3_LowGDD_anom

There he edited the datm.stream.xml, we need an example that just changes user_nl_datm and user_nl_datm_streams.

Definition of Done:

Activity

  1. self-assigned this
    on Apr 29, 2022
  2. moved this from Needs Prioritization to Todo ~ weeks in CESM: infrastructure / cross-component SE prioritieson May 1, 2022
  3. ekluzek commented on Jun 3, 2022

    @ekluzek
    ContributorAuthor

    OK I think I've reproduced the above case with the following changes:

    user_nl_datm:
    anomaly_forcing = 'Anomaly.Forcing.Precip','Anomaly.Forcing.Temperature','Anomaly.Forcing.Pressure','Anomaly.Forcing.Humidity','Anomaly.Forcing.Uwind','Anomaly.Forcing.Vwind','Anomaly.Forcing.Shortwave','Anomaly.Forcing.Longwave'
    user_nl_datm_streams:
    Anomaly.Forcing.Temperature:year_first=2020
    Anomaly.Forcing.Temperature:year_last=2100
    Anomaly.Forcing.Temperature:year_align=2020
    Anomaly.Forcing.Temperature:tintalgo = linear
    Anomaly.Forcing.Temperature:meshfile=$DIN_LOC_ROOT/share/meshes/fv0.9x1.25_141008_polemod_ESMFmesh.nc
    Anomaly.Forcing.Temperature:datafiles = /glade/p/cgd/tss/people/oleson/anomaly_forcing/af.tas.CESM.SSP370.2015-2100.nc
    
    Anomaly.Forcing.Precip:year_first=2020
    Anomaly.Forcing.Precip:year_last=2100
    Anomaly.Forcing.Precip:year_align=2020
    Anomaly.Forcing.Precip:tintalgo = nearest
    Anomaly.Forcing.Precip:meshfile=$DIN_LOC_ROOT/share/meshes/fv0.9x1.25_141008_polemod_ESMFmesh.nc
    Anomaly.Forcing.Precip:datafiles = /glade/p/cgd/tss/people/oleson/anomaly_forcing/af.pr.CESM.SSP370.2015-2100.nc
    
    Anomaly.Forcing.Humidity:year_first=2020
    Anomaly.Forcing.Humidity:year_last=2100
    Anomaly.Forcing.Humidity:year_align=2020
    Anomaly.Forcing.Humidity:tintalgo = linear
    Anomaly.Forcing.Humidity:meshfile=$DIN_LOC_ROOT/share/meshes/fv0.9x1.25_141008_polemod_ESMFmesh.nc
    Anomaly.Forcing.Humidity:datafiles = /glade/p/cgd/tss/people/oleson/anomaly_forcing/af.huss.CESM.SSP370.2015-2100.nc
    
    Anomaly.Forcing.Pressure:year_first=2020
    Anomaly.Forcing.Pressure:year_last=2100
    Anomaly.Forcing.Pressure:year_align=2020
    Anomaly.Forcing.Pressure:tintalgo = linear
    Anomaly.Forcing.Pressure:meshfile=$DIN_LOC_ROOT/share/meshes/fv0.9x1.25_141008_polemod_ESMFmesh.nc
    Anomaly.Forcing.Pressure:datafiles = /glade/p/cgd/tss/people/oleson/anomaly_forcing/af.ps.CESM.SSP370.2015-2100.nc
    
    Anomaly.Forcing.Longwave:year_first=2020
    Anomaly.Forcing.Longwave:year_last=2100
    Anomaly.Forcing.Longwave:year_align=2020
    Anomaly.Forcing.Longwave:tintalgo = linear
    Anomaly.Forcing.Longwave:meshfile=$DIN_LOC_ROOT/share/meshes/fv0.9x1.25_141008_polemod_ESMFmesh.nc
    Anomaly.Forcing.Longwave:datafiles = /glade/p/cgd/tss/people/oleson/anomaly_forcing/af.rlds.CESM.SSP370.2015-2100.nc
    
    Anomaly.Forcing.Shortwave:year_first=2020
    Anomaly.Forcing.Shortwave:year_last=2100
    Anomaly.Forcing.Shortwave:year_align=2020
    Anomaly.Forcing.Shortwave:tintalgo = linear
    Anomaly.Forcing.Shortwave:meshfile=$DIN_LOC_ROOT/share/meshes/fv0.9x1.25_141008_polemod_ESMFmesh.nc
    Anomaly.Forcing.Shortwave:datafiles = /glade/p/cgd/tss/people/oleson/anomaly_forcing/af.rsds.CESM.SSP370.2015-2100.nc
    
    Anomaly.Forcing.Uwind:year_first=2020
    Anomaly.Forcing.Uwind:year_last=2100
    Anomaly.Forcing.Uwind:year_align=2020
    Anomaly.Forcing.Uwind:tintalgo = linear
    Anomaly.Forcing.Uwind:meshfile=$DIN_LOC_ROOT/share/meshes/fv0.9x1.25_141008_polemod_ESMFmesh.nc
    Anomaly.Forcing.Uwind:datafiles = /glade/p/cgd/tss/people/oleson/anomaly_forcing/af.uas.CESM.SSP370.2015-2100.nc
    
    Anomaly.Forcing.Vwind:year_first=2020
    Anomaly.Forcing.Vwind:year_last=2100
    Anomaly.Forcing.Vwind:year_align=2020
    Anomaly.Forcing.Vwind:tintalgo = linear
    Anomaly.Forcing.Vwind:meshfile=$DIN_LOC_ROOT/share/meshes/fv0.9x1.25_141008_polemod_ESMFmesh.nc
    Anomaly.Forcing.Vwind:datafiles = /glade/p/cgd/tss/people/oleson/anomaly_forcing/af.vas.CESM.SSP370.2015-2100.nc
    
  4. ekluzek commented on Jun 3, 2022

    @ekluzek
    ContributorAuthor

    Since the Anomaly Forcing (AF) data are all monthly and normally you want the different variables to be coordinated together, this could be changed so that all variables were on one file and you only use two streams to manage the data. That would cut down on the number of changes you have to add to the user_nl_datm_streams file.

  5. slevis-lmwg commented on Jun 6, 2022

    @slevis-lmwg
    Contributor

    Thank you @ekluzek
    I will try your changes in #1654

  6. wwieder commented on Jun 6, 2022

    @wwieder
    Contributor

    @ekluzek if we're running with GSWP3 should year_first and year_align=2015?

  7. slevis-lmwg commented on Jun 6, 2022

    @slevis-lmwg
    Contributor

    @wwieder the gswp3 data ranges 1901-2014, so I think that year_first=2015 won't work and that you just pick the range of years that you want to cycle for the rest of the run (eg 1991-2010).

  8. wwieder commented on Jun 6, 2022

    @wwieder
    Contributor

    The SSP370 compset defaults to DATM_YR_START=2001 (in env_run.xml), and cycles over data from 2001-2014 (in CaseDocs/datm_streams)

    But I think we want the year_first and year_align in user_nl_datm_streams (above) to be 2015? e.g.

    user_nl_datm_streams:
    Anomaly.Forcing.Temperature:year_first=2015
    Anomaly.Forcing.Temperature:year_last=2100
    Anomaly.Forcing.Temperature:year_align=2015
    Anomaly.Forcing.Temperature:tintalgo = linear
    ...
    

    Again, this would be specific for GSWP3 runs.

  9. wwieder commented on Jun 6, 2022

    @wwieder
    Contributor

    Now that I"m looking more carefully at datm_streams...

    Does this for the year first and year align look right for presaero in a simulation starting in 2015 that's using anomaly forcing @ekluzek?

      <stream_info name="presaero.SSP3-7.0">
       <taxmode>cycle</taxmode>
       <tintalgo>linear</tintalgo>
       <readmode>single</readmode>
       <mapalgo>bilinear</mapalgo>
       <dtlimit>1.5</dtlimit>
       <year_first>2014</year_first>
       <year_last>2101</year_last>
       <year_align>2014</year_align>
    

    my case is here
    /glade/work/wwieder/ctsm/flexLeafCN/cime/scripts/ctsm51d074_2deg_GSWP3V1_ssp370_cnSlope0

  10. slevis-lmwg commented on Jun 6, 2022

    @slevis-lmwg
    Contributor

    The SSP370 compset defaults to DATM_YR_START=2001 (in env_run.xml), and cycles over data from 2001-2014 (in CaseDocs/datm_streams)

    But I think we want the year_first and year_align in user_nl_datm_streams (above) to be 2015? e.g.

    user_nl_datm_streams:
    Anomaly.Forcing.Temperature:year_first=2015
    Anomaly.Forcing.Temperature:year_last=2100
    Anomaly.Forcing.Temperature:year_align=2015
    Anomaly.Forcing.Temperature:tintalgo = linear
    ...
    

    Again, this would be specific for GSWP3 runs.

    I see what you mean, and I think you're right.

  11. ekluzek commented on Jun 23, 2022

    @ekluzek
    ContributorAuthor

    We have this example working, so I'm closing.

  12. 21 remaining items

  13. wwieder commented on Aug 26, 2022

    @wwieder
    Contributor

    Thanks for clearing this up!

  14. wwieder commented on Sep 1, 2022

    @wwieder
    Contributor

    Once the cdeps issue is resolved I suggest we close this issue and move the 'correct' answer to discussion.

  15. added
    docs:newNew documentation needed (e.g., for a new feature)
    docs-loc:users-guideRelates to User's Guide (using CTSM/tools)
    on May 29, 2025
  16. moved this to In Progress in CLM documentationon May 30, 2025
  17. moved this from In Progress to Done in CLM documentationon May 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

docs-loc:users-guideRelates to User's Guide (using CTSM/tools)docs:newNew documentation needed (e.g., for a new feature)documentationadditions or edits to user-facing documentation or its infrastructure

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions