Skip to content

WIE-MIP surface data needs #3912

Open
Open

Description

@wwieder
No description provided.

Activity

  1. wwieder commented on Apr 7, 2026

    @wwieder
    ContributorAuthor

    We need an f09 surface dataset that uses land use from from the TRENDY2025 runs that @adrifoster's already done. I think we may have to remake these with 5.4 datasets, (but maybe that's functionally the same as to 5.3)?

    All WIE-MIP runs will be with constant 1850 land use, but while we're at it, maybe we should also generate land-use timeseries that can be paired with the surface data?

    @slevis-lmwg can you help with this?

  2. added
    enhancementnew capability or improved behavior of existing capability
    nextthis should get some attention in the next week or two. Normally each Thursday SE meeting.
    scienceEnhancement to or bug impacting science
    on Apr 7, 2026
  3. added theissue type on Apr 7, 2026
  4. self-assigned this
    on Apr 7, 2026
  5. changed the title [-]**Surface dataset:** I think we should be able to use data from TRENDY2025 runs that Adrianna's already done (although maybe we need to update for 5.4 datasets)? All runs will be with constant 1850 land use.[/-] [+]**Surface dataset:** f09 1850 using data from TRENDY2025 (though update for 5.4 datasets?) + landuse[/+] on Apr 7, 2026
  6. slevis-lmwg commented on Apr 7, 2026

    @slevis-lmwg
    Contributor

    I can start mksurfdata_esmf right away using the 5.4 raw datasets for f09 1850 plus landuse. No problem if we decide we need to modify this in some way.

    Derecho process for reference (git describe returns ctsm5.4.030):

    cd /glade/work/slevis/git/b4b-dev/tools/mksurfdata_esmf
    ./gen_mksurfdata_build
    conda activate ctsm_pylib
    ./gen_mksurfdata_namelist --start-year 1850 --end-year 2023 --res 0.9x1.25
    ./gen_mksurfdata_jobscript_single --namelist-file surfdata_0.9x1.25_hist_1850_78pfts_c260407.namelist --jobscript-file surfdata_0.9x1.25_hist_1850_78pfts_c260407.jobscript --number-of-nodes 2 --tasks-per-node 128
    qsub surfdata_0.9x1.25_hist_1850_78pfts_c260407.jobscript
    

    UPDATES as a result of the conversation below

    1. Before generating the namelist (line 4 above), I updated gen_mksurfdata_namelist.xml with:
    @@ -10,7 +10,7 @@
    
       <mksrf_flai>
         <entry>
    -      <data_filename>lnd/clm2/rawdata/CTSM54RawData/CLM6_LUH3_HIST_CMIP7/mksrf_pftlai_clm6_histLUH3_2005_c251012.nc</data_filename>
    +      <data_filename>/glade/campaign/cesm/development/lmwg/landuse_source_data/CTSM53RawData/globalctsm53histMKSRFDeg025_240709/mksrf_landuse_ctsm53_pftlai_CLIM.c240709.nc</data_filename>
           <mesh_filename>lnd/clm2/mappingdata/grids/UNSTRUCTgrid_0.25x0.25_nomask_cdf5_c200129.nc</mesh_filename>
         </entry>
       </mksrf_flai>
    @@ -21,7 +21,7 @@
    
       <mksrf_fsoicol>
         <entry>
    -      <data_filename>lnd/clm2/rawdata/CTSM54RawData/CLM6_LUH3_HIST_CMIP7/mksrf_soilcolor_clm6_histLUH3_2005_c251012.nc</data_filename>
    +      <data_filename>/glade/campaign/cesm/development/lmwg/landuse_source_data/CTSM53RawData/globalctsm53histMKSRFDeg025_240709/mksrf_landuse_ctsm53_soilcolor_CLIM.c240709.nc</data_filename>
           <mesh_filename>lnd/clm2/mappingdata/grids/UNSTRUCTgrid_0.25x0.25_nomask_cdf5_c200129.nc</mesh_filename>
         </entry>
       </mksrf_fsoicol>
    @@ -220,7 +220,7 @@ version of the raw dataset will probably go away.
         </entry>
    
         <entry pft_years="1850">
    -      <data_filename>lnd/clm2/rawdata/CTSM54RawData/CLM6_LUH3_HIST_CMIP7/mksrf_landuse_clm6_histLUH3_1850.c251012.nc</data_filename>
    +      <data_filename>/glade/campaign/cesm/development/lmwg/landuse_source_data/CTSM53RawData/globalctsm53histTRENDY2025Deg025_250713/mksrf_landuse_ctsm53_histTRENDY2025_1850.c250713.nc</data_filename>
           <mesh_filename>lnd/clm2/mappingdata/grids/UNSTRUCTgrid_0.25x0.25_nomask_cdf5_c200129.nc</mesh_filename>
           <lake_filename>lnd/clm2/rawdata/lake_area/mksurf_lake_0.05x0.05_hist_clm5_hydrolakes_1850.cdf5.c20220325.nc</lake_filename>
           <urban_filename>lnd/clm2/rawdata/CTSM54RawData/urban_properties/urban_properties_CMIP7_ThreeClass_1850_c250423.nc</urban_filename>
    @@ -252,7 +252,7 @@ version of the raw dataset will probably go away.
         <!-- Lake and urban data from 1700 to 1849 is copied from 1850 -->
         <!-- Lake data from 2018 to 2023 is copied from 2017 -->
         <entry pft_years="1700-2023" >
    -      <data_filename>lnd/clm2/rawdata/CTSM54RawData/CLM6_LUH3_HIST_CMIP7/mksrf_landuse_clm6_histLUH3_%y.c251012.nc</data_filename>
    +      <data_filename>/glade/campaign/cesm/development/lmwg/landuse_source_data/CTSM53RawData/globalctsm53histTRENDY2025Deg025_250713/mksrf_landuse_ctsm53_histTRENDY2025_%y.c250713.nc</data_filename>
           <mesh_filename>lnd/clm2/mappingdata/grids/UNSTRUCTgrid_0.25x0.25_nomask_cdf5_c200129.nc</mesh_filename>
    1. Before submitting the jobscript, I renamed the landuse...txt file to landuse_timeseries_hist_1850-2024_78pfts_WIEMIP.txt, added lines for 2024 to it, and updated the namelist to point to that file.
    2. Will requested that I also generate "16pft" files for the NORESM group, so repeat these steps with slight variations:
    ./gen_mksurfdata_namelist --start-year 1850 --end-year 2023 --res 0.9x1.25 --nocrop
    ./gen_mksurfdata_jobscript_single --namelist-file surfdata_0.9x1.25_hist_1850_16pfts_c260408.namelist --jobscript-file surfdata_0.9x1.25_hist_1850_16pfts_c260408.jobscript --number-of-nodes 2 --tasks-per-node 128
    qsub surfdata_0.9x1.25_hist_1850_16pfts_c260408.jobscript
    

    Before submitting this jobscript, I updated the namelist to point to the same landuse...txt file as in (2).

  7. 22 remaining items

  8. added
    nextthis should get some attention in the next week or two. Normally each Thursday SE meeting.
    on Apr 30, 2026
  9. added
    nextthis should get some attention in the next week or two. Normally each Thursday SE meeting.
    and removed
    nextthis should get some attention in the next week or two. Normally each Thursday SE meeting.
    on Apr 30, 2026
  10. slevis-lmwg commented on Apr 30, 2026

    @slevis-lmwg
    Contributor

    This time I need to work in /glade/work/slevis/git/mksurfdata_toolchain
    git branch: mk_trendy2025_datasets
    because this branch includes my updates to automatically accommodate the extension to 2024.
    git describe: ctsm5.3.063-22-g8d18668ea
    git merge escomp/master and resolve conflicts...
    git describe: ctsm5.4.036-6-gb43c7fd5e
    ./gen_mksurfdata_build
    ./gen_mksurfdata_namelist --res 0.9x1.25 --start-year 2024 --end-year 2024 (added --nocrop for the 16pft case)
    BUT got WARNING: input mksrf_furban file /glade/campaign/cesm/cesmdata/inputdata/lnd/clm2/rawdata/CTSM54RawData/urban_properties/urban_properties_CMIP7_ThreeClass_2024_c250423.nc does not exist that I can address by
    Changing the namelists to point to the 2023 urban props file
    Then:

    ./gen_mksurfdata_jobscript_single --namelist-file surfdata_0.9x1.25_hist_2024_78pfts_c260430.namelist --jobscript-file surfdata_0.9x1.25_hist_2024_78pfts_c260430.jobscript --number-of-nodes 2 --tasks-per-node 128
    ./gen_mksurfdata_jobscript_single --namelist-file surfdata_0.9x1.25_hist_2024_16pfts_c260430.namelist --jobscript-file surfdata_0.9x1.25_hist_2024_16pfts_c260430.jobscript --number-of-nodes 2 --tasks-per-node 128
    qsub surfdata_0.9x1.25_hist_2024_78pfts_c260430.jobscript
    qsub surfdata_0.9x1.25_hist_2024_16pfts_c260430.jobscript
    
  11. moved this from Todo to In Progress in LMWG: Sprint Planning Boardon Apr 30, 2026
  12. slevis-lmwg commented on May 1, 2026

    @slevis-lmwg
    Contributor

    @wwieder I generated the new files in /glade/work/slevis/git/mksurfdata_toolchain/tools/mksurfdata_esmf:

    surfdata_0.9x1.25_hist_2024_78pfts_WIEMIP_c260430.nc
    surfdata_0.9x1.25_hist_2024_16pfts_WIEMIP_c260430.nc
    

    I copied to /glade/campaign/cesm/cesmdata/inputdata/lnd/clm2/surfdata_esmf/ctsm5.4.0.
    I can ./rimport when we're sure.

  13. wwieder commented on May 2, 2026

    @wwieder
    ContributorAuthor

    Marking this as done for sprint purposes, I'll test these datasets in the next few weeks.

  14. moved this from In Progress to Done in LMWG: Sprint Planning Boardon May 2, 2026
  15. slevis-lmwg commented on May 21, 2026

    @slevis-lmwg
    Contributor

    This may answer my questions about closing WIEMIP co2, ndep, and datm issues:
    Final testing is probably pending.

  16. wwieder commented on Jun 3, 2026

    @wwieder
    ContributorAuthor

    Can you remake this dataset (using TRENDY2025 input data) to create a 2023 surface dataset for WIEMIP scenario runs? Sorry the protocol changed...

  17. slevis-lmwg commented on Jun 3, 2026

    @slevis-lmwg
    Contributor

    Generating 2023 fsurdat files.

  18. slevis-lmwg commented on Jun 3, 2026

    @slevis-lmwg
    Contributor

    New datasets

    surfdata_0.9x1.25_hist_2023_16pfts_WIEMIP_c260603.nc
    surfdata_0.9x1.25_hist_2023_78pfts_WIEMIP_c260603.nc
    

    copied to /glade/campaign/cesm/cesmdata/cseg/inputdata/lnd/clm2/surfdata_esmf/ctsm5.4.0

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 capabilityscienceEnhancement to or bug impacting science

Type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions