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

Problem running with own atmospheric forcing

Status
Not open for further replies.
K

kabirtam@msu_edu

New Member
I am trying to do a regional simulation with CLM5.0 at 0.05 degrees spatial resolution with my own precipitation forcing which is 0.1 degrees in resolution. I replaced GSWP3 precipitation with my own customed precipitation forcing (3 hourly). I created a 0.1-degree domain file and replaced the precipitation stream domain file. I have a monthly precipitation file, the time index started from 1-Jan-1979 01:30:00 and ends at 31-Jan-1979 22:30:00 for the 1st precipitation stream file(January 1979). I submitted the model to run for a month with a maximum wall clock time of 12 hr. I am using Cheyenne. I wonder its shows running until 12 hr. and after that job aborted leaving a message that maximum wall clock time exceded. I don't have any clue what's wrong with the simulation. What's wrong with my customed precipitation forcing that it's running for such a long time and simulation cant even complete for a month??
My 0.05-degree regional situation with the deafult forcing worked perfectly. Total computation grid in my domain is 216000.
Any suggestions to diagnose the problem will be really helpful.

Thank you.
Tamanna
 
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
If this is the right case with the problem, MSWEP_WFDEI_TEST1, then it looks like it is taking a long time to do the datm fill and remap for each of the datm streams, e.g.,

(shr_strdata_init) calling shr_dmodel_mapSet for fill
(shr_strdata_init) calling shr_dmodel_mapSet for remap

It looks like you are running a regional simulation at 0.05 degree, with global atmospheric forcing at 0.1 degrees for precipitation, and WFDEI forcing for solar and TPQW at 0.5 degrees.
Does the simulation run using the WRFDEI 0.5 degree precipitation forcing?
If so, maybe the datm is having trouble mapping the global 0.1 degree precipitation data to the 0.05 regional grid. Maybe you could try subsetting the precipitation forcing to a domain that is just a bit larger than the regional grid....
 
K

kabirtam@msu_edu

New Member
Yes. You found the right case. This is MSWEP_WFDEI_TEST1. The simulation runs using global WFDEI 0.5 degrees precipitation forcing for my regional grid. If I understood properly , you suggested to subset precipitation data for my regional domain or slightly larger domain. I will try doing that. Thank your for your time and cooperation. I really appreciate your help.
Thank you.
 
Status
Not open for further replies.
Top