Welcome to the new DiscussCESM forum!
We are still working on the website migration, so you may experience downtime during this process.

Existing users, please reset your password before logging in here: https://xenforo.cgd.ucar.edu/cesm/index.php?lost-password/

Regional run failed: ERROR in UrbanParamsType.F90

adrienD

Adrien Damseaux
New Member
Hi everyone, I am trying to run a regional case (I've created my own SCRIP and mapping files) with CTSM on the new supercomputer mistral (I've been able to make a default run without problems). I know it's a very specific case, but I hope someone can help me.

I've successfully created the surfdata and domain files, and the model building is working fine. However, I have an error when I try to run the model. You can find the main problem from the lnd.log file below and the different log files are attached.
Reading in urban input data from fsurdat file ...
(GETFIL): attempting to find local file
surfdata_218x200_hist_78pfts_CMIP6_simyr2000_c210309.nc
(GETFIL): using
/work/aa0049/a271098/CTSM/inputdata/lnd/clm2/surfdata_map/surfdata_218x200_hist
_78pfts_CMIP6_simyr2000_c210309.nc
Opened existing file
/work/aa0049/a271098/CTSM/inputdata/lnd/clm2/surfdata_map/surfdata_218x200_hist
_78pfts_CMIP6_simyr2000_c210309.nc 458752
UrbanInput
/work/aa0049/a271098/CTSM/inputdata/lnd/clm2/surfdata_map/surfdata_218x200_hist
_78pfts_CMIP6_simyr2000_c210309.nc
UrbanInput: parameter nlevurb= 5
does not equal input dataset nlevurb= 10
ENDRUN:
ERROR: ERROR in UrbanParamsType.F90 at line 477
Thanks in advance,
Adrien
 

Attachments

  • config_batch_machines.zip
    4.8 KB · Views: 0
  • git describe.txt
    1.7 KB · Views: 0
  • lnd.log.28251028.210309-101242.txt
    18.4 KB · Views: 0
  • cesm.log.28251028.210309-101242.txt
    11.1 KB · Views: 0
  • run.arctic218x200_002.txt
    4.2 KB · Views: 0

jedwards

CSEG and Liaisons
Staff member
The data set in
surfdata_218x200_hist_78pfts_CMIP6_simyr2000_c210309.nc
has 10 urban types but somewhere you are specifying only 5. These need to match.
 

erik

Erik Kluzek
CSEG and Liaisons
Staff member
Yes, jedwards is correct. I think the problem you are running into is this one...


You can update to a newer version of CTSM where we fixed that issue (ctsm5.1.dev023).
 

adrienD

Adrien Damseaux
New Member
Yes, jedwards is correct. I think the problem you are running into is this one...


You can update to a newer version of CTSM where we fixed that issue (ctsm5.1.dev023).
Thanks for your help, once again! I have updated to the ctsm5.1dev029 version and the regional run is working.

However, I have huge issues with the real-time length of simulations. With ctsm5.1.dev023, I was able to run default 5-years simulations (--res f19_g17 --compset I1850Clm50Sp) in less than 3 hours and now I am not able to finish before 8 hours. With the exact same set-up. I try to increase the numbers of cpu/nodes without success.

After 8 hours, the slurm job stops due to time limit, even if I set walltimemax="24:00:00". But I suppose it's due to our supercomputer slurm installation.

Any help on that?
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I tried a short simulation with that tag and compset/res and the performance was about what I would expect.
I'm not sure what to suggest, maybe one of our software engineers has a suggestion....
 

adrienD

Adrien Damseaux
New Member
Sorry I meant "With ctsm5.1.dev013, I was able to run default 5-years simulations (--res f19_g17 --compset I1850Clm50Sp) in less than 3 hours..."
 
Top