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

Single Point Simulations Error

S

syang

Shawn Yang
Member
Hi all,
Can anyone help with this. I am stuck to this step and feel so upset. THANKS!!!
I am trying to test clm with 1x1_brazil dataset. The case was setup; build successfully. But once I did case.submit, the error showed up like below (atm.log):

dep_WACCM.ensmean_monthly_hist_1849-2015_0.9x1.25_CMIP6_c180926.nc
(shr_strdata_init_streams) timeName = 4 time
(shr_strdata_init_streams) lonName = 4 lon
(shr_strdata_init_streams) latName = 4 lat
(shr_strdata_init_streams) hgtName = 4 unknownname
(shr_strdata_init_streams) maskName = 4 mask
(shr_strdata_init_streams) areaName = 4 area
(shr_strdata_init_streams) stream 5
(shr_strdata_init_streams) filePath = 5
/work/ese-yangs/clm5_cases/inputdata/atm/datm7/topo_forcing/
(shr_strdata_init_streams) fileName = 5
/work/ese-yangs/clm5_cases/inputdata/atm/datm7/topo_forcing/topodata_0.9x1.25_U
SGS_070110_stream_c151201.nc
(shr_strdata_init_streams) timeName = 5 time
(shr_strdata_init_streams) lonName = 5 LONGXY
(shr_strdata_init_streams) latName = 5 LATIXY
(shr_strdata_init_streams) hgtName = 5 unknownname
(shr_strdata_init_streams) maskName = 5 mask
(shr_strdata_init_streams) areaName = 5 area
(shr_strdata_init_mapping) calling shr_dmodel_mapSet for fill
(shr_strdata_init_mapping) calling shr_dmodel_mapSet for remap
(shr_strdata_init_mapping) calling shr_dmodel_mapSet for fill
(shr_strdata_init_mapping) calling shr_dmodel_mapSet for remap
(shr_strdata_init_mapping) calling shr_dmodel_mapSet for fill
(shr_strdata_init_mapping) calling shr_dmodel_mapSet for remap
(shr_strdata_init_mapping) calling shr_dmodel_mapSet for fill
(shr_strdata_init_mapping) calling shr_dmodel_mapSet for remap
('shr_map_getWts') ERROR: yd outside bounds -90.0000000000000
('shr_map_getWts') cpole = 1.57079632679490
ERROR: ('shr_map_getWts') ERROR yd outside 90 degree bounds
 
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
Can you provide the information as described here:

bb.cgd.ucar.edu

Information to include in help requests

When you are posting to the forums because you want help with an issue, please include as much of the following information as possible. Before submitting a help request, please check to see if your question is already answered: Search the forums for similar issues Check the CIME...
bb.cgd.ucar.edu bb.cgd.ucar.edu

Once I have more information I can take a look at this.
 
S

syang

Shawn Yang
Member
oleson said:
Can you provide the information as described here:

bb.cgd.ucar.edu

Information to include in help requests

When you are posting to the forums because you want help with an issue, please include as much of the following information as possible. Before submitting a help request, please check to see if your question is already answered: Search the forums for similar issues Check the CIME...
bb.cgd.ucar.edu bb.cgd.ucar.edu

Once I have more information I can take a look at this.
Click to expand...
Hi there,

Thank you for reply. I attched my config_machines, config_compliers and the cesm.log below. I tested compset X and it worked. But the Brazail single-test was failed. I noticed that "https://www.cesm.ucar.edu/models/cesm1.0/clm/models/lnd/clm/doc/UsersGuide/x10455.html",
"https://bb.cgd.ucar.edu/cesm/threads/single-point-simulations.1794/#post-7915" decribed the same problem I met, but there is no clear solution. Thus, I could like to ask for help to fix up this problem. Thanks!!!
 

Attachments

  • cesmlog.png
    cesmlog.png
    120.9 KB · Views: 20
  • config_compilers.png
    config_compilers.png
    44.5 KB · Views: 14
  • config_machines2.png
    config_machines2.png
    122.6 KB · Views: 11
  • config_machines.png
    config_machines.png
    159.9 KB · Views: 12
  • atmlog.png
    atmlog.png
    95.8 KB · Views: 12
  • cpllog.png
    cpllog.png
    141.1 KB · Views: 18
S

syang

Shawn Yang
Member
oleson said:
Can you provide the information as described here:

bb.cgd.ucar.edu

Information to include in help requests

When you are posting to the forums because you want help with an issue, please include as much of the following information as possible. Before submitting a help request, please check to see if your question is already answered: Search the forums for similar issues Check the CIME...
bb.cgd.ucar.edu bb.cgd.ucar.edu

Once I have more information I can take a look at this.
Click to expand...
The website "https://www.cesm.ucar.edu/models/cesm1.0/clm/models/lnd/clm/doc/UsersGuide/x10455.html" says it is because the wrong prescribed aerosol file is given to a pt1_pt1 simulation. But how to fix it?
 

Attachments

  • submit.png
    submit.png
    155.5 KB · Views: 18
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
What version of CESM/CLM are you using?

Document the version of the code are you using:
  • In CESM2.1.2 and later, run the script ./describe_version from the top level of your CESM clone (that is, from the directory containing cime, components, etc.). Either:
    • Copy and paste the full output into your post
    • Redirect the output to a file (./describe_version > version_info.txt) then attach the file to your post.
  • From older model versions that do not have the describe_version script, give the output from running the following commands from the top level of your CESM clone (that is, run these from the directory containing cime, components, etc.):
    • git describe
    • ./manage_externals/checkout_externals --status --verbose
 
S

syang

Shawn Yang
Member
oleson said:
What version of CESM/CLM are you using?

Document the version of the code are you using:
  • In CESM2.1.2 and later, run the script ./describe_version from the top level of your CESM clone (that is, from the directory containing cime, components, etc.). Either:
    • Copy and paste the full output into your post
    • Redirect the output to a file (./describe_version > version_info.txt) then attach the file to your post.
  • From older model versions that do not have the describe_version script, give the output from running the following commands from the top level of your CESM clone (that is, run these from the directory containing cime, components, etc.):
    • git describe
    • ./manage_externals/checkout_externals --status --verbose
Click to expand...
2.2.0 please see below.
 

Attachments

  • version_info.txt
    6 KB · Views: 9
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
Thanks for providing the information.
I'm not sure what compset you are using, but I tried this with cesm2.2.0 and it worked fine:

./create_newcase --case testBrazil --res 1x1_brazil --compset IHistClm50BgcQianGs --project P93300041 --run-unsupported

I'm not sure if your error is related to the topo file or the co2 file.
The topo file should be:

topodata_0.9x1.25_USGS_070110_stream_c151201.nc

and the co2 file should be:

fco2_datm_global_simyr_1750-2014_CMIP6_c180929.nc

The default settings for the datm files (in datm_in) should be:

&datm_nml
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 = "/glade/p/cesmdata/cseg/inputdata/share/domains/domain.clm/domain.lnd.1x1pt-brazil_navy.090715.nc"
dtlimit = 1.5, 1.5, 1.5, 1.5, 1.5, 1.5
fillalgo = "nn", "nn", "nn", "nn", "nn", "nn"
fillmask = "nomask", "nomask", "nomask", "nomask", "nomask", "nomask"
fillread = "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"
mapalgo = "bilinear", "bilinear", "bilinear", "bilinear", "bilinear", "nn"
mapmask = "nomask", "nomask", "nomask", "nomask", "nomask", "nomask"
mapread = "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"
readmode = "single", "single", "single", "single", "single", "single"
streams = "datm.streams.txt.CLM_QIAN.Solar 1895 1948 1972",
"datm.streams.txt.CLM_QIAN.Precip 1895 1948 1972",
"datm.streams.txt.CLM_QIAN.TPQW 1895 1948 1972",
"datm.streams.txt.presaero.trans_1850-2000 1849 1849 2014",
"datm.streams.txt.topo.observed 1 1 1",
"datm.streams.txt.co2tseries.20tr 1850 1850 2014"
taxmode = "cycle", "cycle", "cycle", "cycle", "cycle", "extend"
tintalgo = "coszen", "nearest", "linear", "linear", "lower", "linear"
vectors = "null"
/

You could also check to make sure the topo and co2 files aren't corrupted.
 
S

syang

Shawn Yang
Member
oleson said:
Thanks for providing the information.
I'm not sure what compset you are using, but I tried this with cesm2.2.0 and it worked fine:

./create_newcase --case testBrazil --res 1x1_brazil --compset IHistClm50BgcQianGs --project P93300041 --run-unsupported

I'm not sure if your error is related to the topo file or the co2 file.
The topo file should be:

topodata_0.9x1.25_USGS_070110_stream_c151201.nc

and the co2 file should be:

fco2_datm_global_simyr_1750-2014_CMIP6_c180929.nc

The default settings for the datm files (in datm_in) should be:

&datm_nml
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 = "/glade/p/cesmdata/cseg/inputdata/share/domains/domain.clm/domain.lnd.1x1pt-brazil_navy.090715.nc"
dtlimit = 1.5, 1.5, 1.5, 1.5, 1.5, 1.5
fillalgo = "nn", "nn", "nn", "nn", "nn", "nn"
fillmask = "nomask", "nomask", "nomask", "nomask", "nomask", "nomask"
fillread = "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"
mapalgo = "bilinear", "bilinear", "bilinear", "bilinear", "bilinear", "nn"
mapmask = "nomask", "nomask", "nomask", "nomask", "nomask", "nomask"
mapread = "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"
readmode = "single", "single", "single", "single", "single", "single"
streams = "datm.streams.txt.CLM_QIAN.Solar 1895 1948 1972",
"datm.streams.txt.CLM_QIAN.Precip 1895 1948 1972",
"datm.streams.txt.CLM_QIAN.TPQW 1895 1948 1972",
"datm.streams.txt.presaero.trans_1850-2000 1849 1849 2014",
"datm.streams.txt.topo.observed 1 1 1",
"datm.streams.txt.co2tseries.20tr 1850 1850 2014"
taxmode = "cycle", "cycle", "cycle", "cycle", "cycle", "extend"
tintalgo = "coszen", "nearest", "linear", "linear", "lower", "linear"
vectors = "null"
/

You could also check to make sure the topo and co2 files aren't corrupted.
Click to expand...
Thank you for your reply. I created the case with ./create_newcase --case ~/cime/testSPDATASET --res 1x1_brazil --compset I2000Clm50SpGs --mach yangs –run-unsupported. And the datm_in and datm_inputdata_list are attached below. I just changed the user_nl_datm with the command
"&shr_strdata_nml
mapalgo = 'nn','nn','nn','nn','nn','nn' ", and then the "yd outside 90 degree" problem was gone. But the new "error: elapsed seconds must be increasing" showed up (please see the pictures below). I set up the RUN_STARTDATE= 1991-01-01, run for 60 days for test, with DATM_CLMNCEP_YR_START ="1991", DATM_CLMNCEP_YR_END=1991". Thus, I am wondering is that error coming from the wrong inputdata? or there are some problems of my CESM installation. Since the compset X worked fine, I think it should be some problems with the inputdata. I have no idea how to fix it. Thank you!
 

Attachments

  • datm_in.png
    datm_in.png
    74.7 KB · Views: 18
  • datm_input_data_list.png
    datm_input_data_list.png
    267.2 KB · Views: 13
  • error_seconds must be increasing.png
    error_seconds must be increasing.png
    132.8 KB · Views: 14
  • user_nl_datm.png
    user_nl_datm.png
    42.5 KB · Views: 19
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I tried your case (testSPDATASET) on our machine and it ran fine without making any changes.
I also tried it with RUN_STARTDATE= 1991-01-01, run for 60 days for test, with DATM_CLMNCEP_YR_START ="1991", DATM_CLMNCEP_YR_END=1991", and that ran fine as well.
So I can only assume there must be an issue with your installation or with the input datasets you are using.
 
S

syang

Shawn Yang
Member
oleson said:
I tried your case (testSPDATASET) on our machine and it ran fine without making any changes.
I also tried it with RUN_STARTDATE= 1991-01-01, run for 60 days for test, with DATM_CLMNCEP_YR_START ="1991", DATM_CLMNCEP_YR_END=1991", and that ran fine as well.
So I can only assume there must be an issue with your installation or with the input datasets you are using.
Click to expand...
OK. THANKS. I will test more cases to figure out the problem. What I feel confuesd is that the case was setup and build successfuly, but the run did not worked.
 
Q

qian yang

qian yang
Member
dear oleson
I have met the same error . I tried modify mapalgo from "bilinear", "bilinear", "bilinear", "bilinear", "bilinear", to 'nn','nn','nn','nn','nn','nn' , The problem has gone. But I have some confusion，what does the parameter mean? What does it mean to make this change？
 
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
bilinear means bilinear interpolation, while nn is nearest neighbor. These refer to the method of mapping from datm forcing data to the model grid.
Generally, you need nn for single-point forcing because there is only one datm gridcell and one land gridcell.
 
You must log in or register to reply here.
Top