Skip to content

Setting up WIEMIP Transient runs #165

@wwieder

Description

@wwieder

How do we initialize transient hillslope hydrology runs from 1850 initial conditions?

I'm trying to figure out how to set up our transient experiments for WIEMIP and need advice.

My plan was to use this compset HIST_DATM%CRUJRA2024b_CLM60%BGC_SICE_SOCN_MOSART_SGLC_SWAV with modifications for the following experiments (Note, there is no landuse change in any of these experiments, flanduse_timeseries = '').

  • control (CON), which is basically a continuation of our spinup, cycling over 20 years of ndep and climate with constant CO2
  • Biogeochemically coupled (BGC) with time evolving CO2 and Ndep, but cycling climate
  • Radiatiatively coupled (RAD) with time evolving climate, but cycling NDEP and constant CO2
  • Coupled (COU) with time evolving CO2, climate & Ndep

I have a sandbox of usermods where this is working for non-hillslope cases here /glade/u/home/wwieder/wetlands/cime_config/usermods_dirs/clm/WIEMIP

Smoke tests with with a flat case seem to work (e.g. /glade/work/wwieder/wiemip/wetlands.n03.ctsm5.4.029_f09noCrop_flat_158_testBGC), but require setting use_init_interp = .true..

Similar tests with a hillslope hydrology case fail because we can't use use_init_interp = .true. with hillslope hydrology, but it also seems like it's required for starting a historical run (even though flanduse_timeseries = '')

 Reading restart dataset:
 /glade/derecho/scratch/wwieder/archive/wetlands.n03.ctsm5.4.029_f09noCrop_HH_16
 5_AD/rest/0181-01-01-00000/wetlands.n03.ctsm5.4.029_f09noCrop_HH_165_AD.clm2.r.
 0181-01-01-00000.nc
 check_dim_size ERROR: mismatch of input dimension       176267
  with expected value       178441  for variable column
Did you mean to set use_init_interp = .true. in user_nl_clm?
(Setting use_init_interp = .true. is needed when doing a
transient run using an initial conditions file from a non-transient run,
or a non-transient run using an initial conditions file from a transient run,
or when running a resolution or configuration that differs from the initial conditions.)

Suggestions are welcome here @slevis-lmwg, @olyson, @ekluzek, @swensosc (thanks in advance).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions