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

Error in atm forcing (GSWP3) - CLM5

Status
Not open for further replies.
Hello, I have successfully ported CLM to a local cluster and am trying out some out-of-the-box test cases. I'm running the case only changing a few things per the CaseStatus file. The cesm.log* reports the following error. Additional info in attached files. I'm guessing it's an issue with NaN in my atmospheric forcing files (GSWP3 forcing), but I'm wondering how I fix the problem? What forcing files include zonal wind (Sa_u)? Or is it calculated? Do I need to change NaN's to 1e+36 (which is the -FillValue and missing_value in the forcing files? It seems all input files have NaN, so is there a quick way to do it? Thanks for any insight on this issue!

./create_newcase --case CLM5-Test6 --mach bell --res f19_g17 --compset I1850Clm50Sp --compiler gnu --run-unsupported

2021-02-11 15:18:19: case.setup starting
---------------------------------------------------
2021-02-11 15:18:21: case.setup success
---------------------------------------------------
2021-02-11 15:19:42: xmlchange success <command> ./xmlchange STOP_OPTION=nyears </command>
---------------------------------------------------
2021-02-11 15:20:11: xmlchange success <command> ./xmlchange STOP_N=10 </command>
---------------------------------------------------
2021-02-11 15:21:31: xmlchange success <command> ./xmlchange JOB_WALLCLOCK_TIME=40:00:00 </command>
---------------------------------------------------
2021-02-11 15:22:10: case.build starting
---------------------------------------------------
CESM version is release-clm5.0.34-24-gdc5ea974
Processing externals description file : Externals.cfg
Processing externals description file : Externals_CLM.cfg
Processing externals description file : Externals_CISM.cfg
Checking status of externals: clm, fates, ptclm, cism, source_cism, rtm, mosart, cime, doc-builder,
M ./cime
modified sandbox, on cime5.6.33
./components/cism
clean sandbox, on cism-release-cesm2.1.2_02
./components/cism/source_cism
clean sandbox, on release-cism2.1.03
./components/mosart
clean sandbox, on release-cesm2.0.04
./components/rtm
clean sandbox, on release-cesm2.0.04
e-o ./doc/doc-builder
-, not checked out --> v1.0.4
./src/fates
clean sandbox, on sci.1.30.0_api.8.0.0
./tools/PTCLM
clean sandbox, on PTCLM2_20200121
2021-02-11 15:24:31: case.build success
---------------------------------------------------
2021-02-11 15:24:42: case.submit starting
---------------------------------------------------
2021-02-11 15:25:05: case.submit success case.run:1331269, case.st_archive:1331270

From cesm.log:

ERROR: component_mod:check_fields NaN found in ATM instance: 1 field Sa_u 1d global index: 13717
 

Attachments

  • config_compilers.xml.txt
    1.9 KB · Views: 0
  • config_batch.xml.txt
    1.5 KB · Views: 1
  • config_machines.xml.txt
    3.8 KB · Views: 0
  • version_info.txt
    826 bytes · Views: 1
  • README.case.txt
    2.6 KB · Views: 2
  • glc.log.1331269.210211-152536.txt
    390.9 KB · Views: 0
  • cpl.log.1331269.210211-152536.txt
    457.5 KB · Views: 0
  • cesm.log.1331269.210211-152536.txt
    196.2 KB · Views: 6
  • clm5-error.zip
    941.1 KB · Views: 2

oleson

Keith Oleson
CSEG and Liaisons
Staff member
The wind components (u and v) are derived from the forcing wind magnitude which comes from the GSWP3 files (specifically, WIND in the TPQWL files).
From the atm log file, it looked like the model was running fine starting in 1901 and then crashed in Feb 1905? So it seems like your forcing files wouldn't have any NaNs from 1901 up to the point at which it crashed. Do they?
There shouldn't be any NaNs in any of the GSWP3 forcing files (I don't see any in our version of the forcing files we have here on cheyenne).

Maybe your file(s) were not downloaded completely/correctly? You could try downloading them again.
 
Status
Not open for further replies.
Top