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

New CTSM setup for CO/WY (ERROR: no valid urban data)

Status
Not open for further replies.

yifanc

Yifan Cheng
New Member
What version of the code are you using?
The master branch in the CTSM github page (retrieval date: Jan 7, 2026)


Have you made any changes to files in the source tree?
I made no changes to the source code


Describe every step you took leading up to the problem:
I created a new CTSM case study using compset I2000Clm60Sp. I also generated the domain file and surface dataset file at a 5-km (0.05 degree) rectangular grid spacing for Colorado and Wyoming. My run case is located
/glade/work/yifanc/proj/DISES/ctsm/cases/DISES.default


If this is a port to a new machine: Please attach any files you added or changed for the machine port (e.g., config_compilers.xml, config_machines.xml, and config_batch.xml) and tell us the compiler version you are using on this machine.
Please attach any log files showing error messages or other useful information.

I ran this model in Derecho.


Describe your problem or question:
In the new CTSM configuration, I only provided the new domain file and surface dataset at a customized grid, and I used the default data streams for all other inputs. The model crashed with the following error message (ERROR: no valid urban data for g= 13, Line 1338 in lnd.log.4571380.desched1.260108-110452.txt)
The changes I made to the run directory are summarized in update_field.yifan.sh.txt
When generating the surface dataset, I followed the steps on (CTSM/tools/mksurfdata_esmf at master · ESCOMP/CTSM). I did not change any input source files.
 

Attachments

  • debug.YC.zip
    10.2 KB · Views: 0

slevis

Moderator
Staff member
I looked at your /run directory:
Have you run successfully now? If so, please share how you corrected the issue.
 

yifanc

Yifan Cheng
New Member
Thanks for the response, Sam!
Indeed! I got the model running. It was embarrassing. The error results from not specifying MASK_MESH. I only specified LND_DOMAIN_MESH for my targeted domain, and the MASK_MESH was still pointed to the default global one, which caused the inconsistency in the domain file. After I specified MASK_MESH, it ran smoothly.
 
Status
Not open for further replies.
Top