Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

Guidance on Running with LME datasets with CESM2.1.3 (CLM5)

O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I have a tar file of the anomaly forcing files here:

ftp://ftp.cgd.ucar.edu/pub/oleson/anomaly_forcing_mct_for_ftp.tar

I would use it. The files at, e.g., /glade/campaign/cesm/cesmdata/cseg/inputdata/atm/datm7/anomaly_forcing/CMIP6-SSP3-7.0 were created from CMIP6 simulations that had an emissions error. The files I'm providing are from the corrected simulations.
Alternatively, you could try the file that has all of the variables in one file, e.g.,

/glade/campaign/cesm/cesmdata/cseg/inputdata/atm/datm7/anomaly_forcing/CMIP6-SSP3-7.0/af.allvars.CESM.SSP3-7.0.2015-2100_c20220628.nc

That file was also created from the corrected simulations.
 
wvsi3w

wvsi3w

wvsi3w
Member
oleson said:
I have a tar file of the anomaly forcing files here:

ftp://ftp.cgd.ucar.edu/pub/oleson/anomaly_forcing_mct_for_ftp.tar

I would use it. The files at, e.g., /glade/campaign/cesm/cesmdata/cseg/inputdata/atm/datm7/anomaly_forcing/CMIP6-SSP3-7.0 were created from CMIP6 simulations that had an emissions error. The files I'm providing are from the corrected simulations.
Alternatively, you could try the file that has all of the variables in one file, e.g.,

/glade/campaign/cesm/cesmdata/cseg/inputdata/atm/datm7/anomaly_forcing/CMIP6-SSP3-7.0/af.allvars.CESM.SSP3-7.0.2015-2100_c20220628.nc

That file was also created from the corrected simulations.
Click to expand...

So if I understood your message clearly, I could either download the .tar file you mentioned,

or

I could use the files (e.g., http://af.allvars.cesm.ssp2-4.5.2015-2100_c20220628.nc) which are in this link: - Revision 70792: /trunk/inputdata/atm/datm7/anomaly_forcing

I don't have access to glade (which I guess is an internal server for NCAR).
 
Z

Zh Chen

chen
Member
oleson said:
Correct.
Click to expand...
Hi, Oleson. Thanks for providing the anomaly forcing files (e.g., af.allvars.cesm.ssp2-4.5.2015-2100_c20220628.nc). I am currently running SSP5-8.5 using CTSM5.3.026 with the NUOPC. I noticed that the repository currently seems to only contain the land use file (flanduse_timeseries) that is necessary for CTSM for SSP2-4.5 (link:- Revision 70792: /trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0) compatible with CTSM5.3.
Could you please advise on how to obtain the flanduse_timeseries files for other SSP scenarios (e.g., SSP3-7.0, SSP5-8.5)? Should I generate them using the CTSM surface dataset tools, or are files from previous CLM/CTSM versions compatible with CTSM5.3.026? Thanks for your help.
 
Z

Zh Chen

chen
Member
Zh Chen said:
Hi, Oleson. Thanks for providing the anomaly forcing files (e.g., af.allvars.cesm.ssp2-4.5.2015-2100_c20220628.nc). I am currently running SSP5-8.5 using CTSM5.3.026 with the NUOPC. I noticed that the repository currently seems to only contain the land use file (flanduse_timeseries) that is necessary for CTSM for SSP2-4.5 (link:- Revision 70792: /trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0) compatible with CTSM5.3.
Could you please advise on how to obtain the flanduse_timeseries files for other SSP scenarios (e.g., SSP3-7.0, SSP5-8.5)? Should I generate them using the CTSM surface dataset tools, or are files from previous CLM/CTSM versions compatible with CTSM5.3.026? Thanks for your help.
Click to expand...
or the SSP landuse of CTSM5.2 (- Revision 70792: /trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.2.0). Thanks
 
Z

Zh Chen

chen
Member
Additionally, I noticed that the presets for various SSP scenarios (such as SSP3-7.0 and SSP5-8.5) with path of repository in namelist_defaults_ctsm.xml

e.g.,
<flanduse_timeseries hgrid="0.9x1.25" sim_year_range="1850-2100" ssp_rcp="SSP5-8.5"
>lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_0.9x1.25_SSP5-8.5_1850-2100_78pfts_c240908.nc</flanduse_timeseries>
Click to expand...
yet these files appear to be missing from the repository link. Thanks for your help.
 
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I am not sure about compatibility between different versions, @slevis may be able to provide some information. The ctsm5.2 and ctsm5.3 are not official releases so that is likely why we are not providing a full set of SSP landuse timeseries files in the public repository. However, if they are available on our internal server (i.e., they've been created using the mksurfdata_esmf tool) then I could put them on our ftp site, or, it might be easier for you to create them using the mksurfdata_esmf tool.
What specific SSP(s) and resolution(s) are you looking for?
 
Z

Zh Chen

chen
Member
oleson said:
I am not sure about compatibility between different versions, @slevis may be able to provide some information. The ctsm5.2 and ctsm5.3 are not official releases so that is likely why we are not providing a full set of SSP landuse timeseries files in the public repository. However, if they are available on our internal server (i.e., they've been created using the mksurfdata_esmf tool) then I could put them on our ftp site, or, it might be easier for you to create them using the mksurfdata_esmf tool.
What specific SSP(s) and resolution(s) are you looking for?
Click to expand...
Thank you for your reply. I am looking for three files for SSP3-7.0, SSP4-6.0, and SSP5-8.5 at 0.9x1.25.These are as follows, and they are from namelist_defaults_ctsm.xml of CTSM5.3.026:
<!-- SSP3-RCP7.0 - relative to {csmdata}) -->
<flanduse_timeseries hgrid="0.9x1.25" sim_year_range="1850-2100" ssp_rcp="SSP3-7.0"
>lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_0.9x1.25_SSP3-7.0_1850-2100_78pfts_c240908.nc</flanduse_timeseries>
Click to expand...
<!-- SSP4-RCP6.0 - relative to {csmdata}) -->
<flanduse_timeseries hgrid="0.9x1.25" sim_year_range="1850-2100" ssp_rcp="SSP4-6.0"
>lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_0.9x1.25_SSP4-6.0_1850-2100_78pfts_c240908.nc</flanduse_timeseries>
Click to expand...
<!-- SSP5-RCP8.5 - relative to {csmdata}) -->
<flanduse_timeseries hgrid="0.9x1.25" sim_year_range="1850-2100" ssp_rcp="SSP5-8.5"
>lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_0.9x1.25_SSP5-8.5_1850-2100_78pfts_c240908.nc</flanduse_timeseries>
Click to expand...
If these files are available on your internal server, would it be possible to upload them to the FTP site? It would be greatly appreciated, as running the mksurfdata_esmf tool myself seems challenging due to the large amount of raw SSP dependency files required. Thanks for your help.
 
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
The first two files are there:

ftp://ftp.cgd.ucar.edu/pub/oleson/ctsm5.3_landusetimeseries/landuse.timeseries_0.9x1.25_SSP3-7.0_1850-2100_78pfts_c240908.nc
ftp://ftp.cgd.ucar.edu/pub/oleson/ctsm5.3_landusetimeseries/landuse.timeseries_0.9x1.25_SSP4-6.0_1850-2100_78pfts_c240908.nc

The disc space is limited, so if you grab those files I can start putting the last one on.
 
Last edited:
Z

Zh Chen

chen
Member
oleson said:
The first two files are there:

ftp://ftp.cgd.ucar.edu/pub/oleson/ctsm5.3_landusetimeseries/landuse.timeseries_0.9x1.25_SSP3-7.0_1850-2100_78pfts_c240908.nc
ftp://ftp.cgd.ucar.edu/pub/oleson/ctsm5.3_landusetimeseries/landuse.timeseries_0.9x1.25_SSP4-6.0_1850-2100_78pfts_c240908.nc

The disc space is limited, so if you grab those files I can start putting the last one on.
Click to expand...
Thanks a lot! I've grabbed the two files, so you can delete them now. I'm ready for the last one whenever you are.
 
wvsi3w

wvsi3w

wvsi3w
Member
Hello Keith @oleson and Sam @slevis

Following my case (which I mentioned here), my simulations started running, and all of a sudden failed in the middle of the second resubmit. I did try to redo the whole thing from the beginning and they all failed at the same year (2033).

I have four cases, and all of them crashed with the same error:

ERROR: ERROR in BalanceCheckMod.F90

I have attached the cesm log file (had to reduce its size by turning it into gz file).

Please let me know what you think the root cause of this issue is. Thanks.

P.S. a reminder to specify my cases: I had two verson of the depth (shallow and deep), and two members of solar variability (mem1, mem2), hence I had 4 conditions to start my SSP simulations which are SSP45_Mem1_Deep, SSP45_Mem1_Shallow, SSP45_Mem2_Deep, SSP45_Mem2_Shallow (started the SSP from 2021 and all failed in year 2033, twice!).

P.P.S. If you want, I can share my user_datm.streams.txt.Anomaly* files and the rest of the setup.
 

Attachments

  • cesm log SSP245.txt.gz
    140 KB · Views: 2
Z

Zh Chen

chen
Member
oleson said:
Ok, the last one is there now.
Click to expand...
Thanks! Download complete, so please feel free to remove it. I realized I still need the SSP1-2.6 file listed below. If you could upload that one, I'll grab it instantly. Thanks for your patience!
<!-- SSP1-RCP2.6 - relative to {csmdata}) -->
<flanduse_timeseries hgrid="0.9x1.25" sim_year_range="1850-2100" ssp_rcp="SSP1-2.6"
>lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_0.9x1.25_SSP1-2.6_1850-2100_78pfts_c240908.nc</flanduse_timeseries>
Click to expand...
 
wvsi3w

wvsi3w

wvsi3w
Member
wvsi3w said:
Hello Keith @oleson and Sam @slevis

Following my case (which I mentioned here), my simulations started running, and all of a sudden failed in the middle of the second resubmit. I did try to redo the whole thing from the beginning and they all failed at the same year (2033).

I have four cases, and all of them crashed with the same error:

ERROR: ERROR in BalanceCheckMod.F90

I have attached the cesm log file (had to reduce its size by turning it into gz file).

Please let me know what you think the root cause of this issue is. Thanks.

P.S. a reminder to specify my cases: I had two verson of the depth (shallow and deep), and two members of solar variability (mem1, mem2), hence I had 4 conditions to start my SSP simulations which are SSP45_Mem1_Deep, SSP45_Mem1_Shallow, SSP45_Mem2_Deep, SSP45_Mem2_Shallow (started the SSP from 2021 and all failed in year 2033, twice!).

P.P.S. If you want, I can share my user_datm.streams.txt.Anomaly* files and the rest of the setup.
Click to expand...
Hello again,
Would this part of my previous run which is being used as finidat in my current SSP2-4.5 run impact the results and create that BalanceCheckMod Error?
In that I used SSP1-2.6 for 2015-2020, and here from 2021 I am using SSP2-4.5, do you think that is the cause?
 
wvsi3w

wvsi3w

wvsi3w
Member
wvsi3w said:
Hello again,
Would this part of my previous run which is being used as finidat in my current SSP2-4.5 run impact the results and create that BalanceCheckMod Error?
In that I used SSP1-2.6 for 2015-2020, and here from 2021 I am using SSP2-4.5, do you think that is the cause?
Click to expand...
Hello again,
I have tried with SSP1-2.6 too, and it failed with the same error.

So this was not causing that error.

what do you think is causing this error that everytime it is failing at the exact same date (2033 with BalanceCheckMod Error) for every case?
Is there anything wrong with my setup?
 
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
The size of the error in the log file:

errh2o = 68719476736.0000

and the fact that forc_rain is very large:

forc_rain = 4.546426176309987E+026

may indicate that the domain file associated with the forcing may not be lining up in terms of data/nodata. In other words, the model may be trying to use a missing value for forc_rain (and possibly other fields).
 
wvsi3w

wvsi3w

wvsi3w
Member
oleson said:
The size of the error in the log file:

errh2o = 68719476736.0000

and the fact that forc_rain is very large:

forc_rain = 4.546426176309987E+026

may indicate that the domain file associated with the forcing may not be lining up in terms of data/nodata. In other words, the model may be trying to use a missing value for forc_rain (and possibly other fields).
Click to expand...
Thank you Keith for your response.
So, what do you think I should do because I followed the steps that was provided and I assume the setup is correct.

This is the datm_in file (inside CaseDocs directory) of this current case that failed and it is using the "domain.lnd.fv0.9x1.25_gx1v7.151020.nc" domain file:
Code: 
&datm_nml
  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"
  decomp = "1d"
  factorfn = "null"
  force_prognostic_true = .false.
  iradsw = 1
  presaero = .true.
  restfilm = "undefined"
  restfils = "undefined"
  wiso_datm = .false.
/
&shr_strdata_nml
  datamode = "CLMNCEP"
  domainfile = "/scratch/USER/cesm/inputdata/share/domains/domain.lnd.fv0.9x1.25_gx1v7.151020.nc"
  dtlimit = 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5,
      1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5
  fillalgo = "nn", "nn", "nn", "nn", "nn", "nn", "nn", "nn", "nn", "nn", "nn",
      "nn", "nn", "nn", "nn", "nn", "nn", "nn", "nn", "nn", "nn", "nn"
  fillmask = "nomask", "nomask", "nomask", "nomask", "nomask", "nomask",
      "nomask", "nomask", "nomask", "nomask", "nomask", "nomask", "nomask",
      "nomask", "nomask", "nomask", "nomask", "nomask", "nomask", "nomask",
      "nomask", "nomask"
  fillread = "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET",
      "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET",
      "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET",
      "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET"
  fillwrite = "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET",
      "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET",
      "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET",
      "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET"
  mapalgo = "bilinear", "bilinear", "bilinear", "bilinear", "bilinear", "nn",
      "bilinear", "bilinear", "bilinear", "bilinear", "bilinear", "bilinear",
      "bilinear", "bilinear", "bilinear", "bilinear", "bilinear", "bilinear",
      "bilinear", "bilinear", "bilinear", "bilinear"
  mapmask = "nomask", "nomask", "nomask", "nomask", "nomask", "nomask",
      "nomask", "nomask", "nomask", "nomask", "nomask", "nomask", "nomask",
      "nomask", "nomask", "nomask", "nomask", "nomask", "nomask", "nomask",
      "nomask", "nomask"
  mapread = "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET",
      "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET",
      "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET",
      "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET"
  mapwrite = "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET",
      "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET",
      "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET",
      "NOT_SET", "NOT_SET", "NOT_SET", "NOT_SET"
  readmode = "single", "single", "single", "single", "single", "single",
      "single", "single", "single", "single", "single", "single", "single",
      "single", "single", "single", "single", "single", "single", "single",
      "single", "single"
  streams = "datm.streams.txt.CLMGSWP3v1.Solar 2000 2000 2014",
      "datm.streams.txt.CLMGSWP3v1.Precip 2000 2000 2014",
      "datm.streams.txt.CLMGSWP3v1.TPQW 2000 2000 2014",
      "datm.streams.txt.presaero.SSP1-2.6 2015 2015 2101",
      "datm.streams.txt.topo.observed 1 1 1",
      "datm.streams.txt.co2tseries.SSP1-2.6 2015 2015 2500",
      "datm.streams.txt.Anomaly.Forcing.Precip 2015 2015 2100",
      "datm.streams.txt.Anomaly.Forcing.Temperature 2015 2015 2100",
      "datm.streams.txt.Anomaly.Forcing.Pressure 2015 2015 2100",
      "datm.streams.txt.Anomaly.Forcing.Humidity 2015 2015 2100",
      "datm.streams.txt.Anomaly.Forcing.Uwind 2015 2015 2100",
      "datm.streams.txt.Anomaly.Forcing.Vwind 2015 2015 2100",
      "datm.streams.txt.Anomaly.Forcing.Shortwave 2015 2015 2100",
      "datm.streams.txt.Anomaly.Forcing.Longwave 2015 2015 2100",
      "datm.streams.txt.Anomaly.Forcing.Precip 2006 2006 2300",
      "datm.streams.txt.Anomaly.Forcing.Temperature 2006 2006 2300",
      "datm.streams.txt.Anomaly.Forcing.Pressure 2006 2006 2300",
      "datm.streams.txt.Anomaly.Forcing.Humidity 2006 2006 2300",
      "datm.streams.txt.Anomaly.Forcing.Uwind 2006 2006 2300",
      "datm.streams.txt.Anomaly.Forcing.Vwind 2006 2006 2300",
      "datm.streams.txt.Anomaly.Forcing.Shortwave 2006 2006 2300",
      "datm.streams.txt.Anomaly.Forcing.Longwave 2006 2006 2300"
  taxmode = "cycle", "cycle", "cycle", "cycle", "cycle", "extend", "cycle",
      "cycle", "cycle", "cycle", "cycle", "cycle", "cycle", "cycle", "cycle",
      "cycle", "cycle", "cycle", "cycle", "cycle", "cycle", "cycle"
  tintalgo = "coszen", "nearest", "linear", "linear", "lower", "linear",
      "nearest", "nearest", "nearest", "nearest", "nearest", "nearest",
      "nearest", "nearest", "nearest", "nearest", "nearest", "nearest",
      "nearest", "nearest", "nearest", "nearest"
  vectors = "null"
/

Do you think this issue that you mentioned is because my initial file (finidat) is from the previous run that was using different forcing and a different domain?
(for your reference, this is where we discussed my previous domain modification that did suit my own boundary conditions: Guidance on Running with LME datasets with CESM2.1.3 (CLM5)
&

Guidance on Running with LME datasets with CESM2.1.3 (CLM5) )
 
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I doubt there is a problem with the finidat file since that file would be interpolated to your new grid/domain at the beginning of the simulation and your simulation runs fine for a number of years.
One question I have is why do you have the anomaly forcing repeated in the file above, i.e.,

"datm.streams.txt.Anomaly.Forcing.Precip 2015 2015 2100",
"datm.streams.txt.Anomaly.Forcing.Temperature 2015 2015 2100",
"datm.streams.txt.Anomaly.Forcing.Pressure 2015 2015 2100",
"datm.streams.txt.Anomaly.Forcing.Humidity 2015 2015 2100",
"datm.streams.txt.Anomaly.Forcing.Uwind 2015 2015 2100",
"datm.streams.txt.Anomaly.Forcing.Vwind 2015 2015 2100",
"datm.streams.txt.Anomaly.Forcing.Shortwave 2015 2015 2100",
"datm.streams.txt.Anomaly.Forcing.Longwave 2015 2015 2100",
"datm.streams.txt.Anomaly.Forcing.Precip 2006 2006 2300",
"datm.streams.txt.Anomaly.Forcing.Temperature 2006 2006 2300",
"datm.streams.txt.Anomaly.Forcing.Pressure 2006 2006 2300",
"datm.streams.txt.Anomaly.Forcing.Humidity 2006 2006 2300",
"datm.streams.txt.Anomaly.Forcing.Uwind 2006 2006 2300",
"datm.streams.txt.Anomaly.Forcing.Vwind 2006 2006 2300",
"datm.streams.txt.Anomaly.Forcing.Shortwave 2006 2006 2300",
"datm.streams.txt.Anomaly.Forcing.Longwave 2006 2006 2300"

Also, I'd check the precipitation anomaly forcing file to make sure it has valid data throughout time, could it be corrupted from a bad download?
 
You must log in or register to reply here.
Top