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

What does "wt_nat_patch" point to?

LiwenWu

LiwenWu
New Member
Dear Scientists,
I was running a I2000Clm50SpGs case for spinning up, but after submitting the case, an error occured:

run command is mpirun -np 26 /home/xunbin/cesm/scratch/shanxispinup4/bld/cesm.exe >> cesm.log.$LID 2>&1
Exception from case_run: ERROR: RUN FAIL: Command 'mpirun -np 26 /home/xunbin/cesm/scratch/shanxispinup4/bld/cesm.exe >> cesm.log.$LID 2>&1 ' failed
See log file for details: /home/xunbin/cesm/scratch/shanxispinup4/run/cesm.log.240416-170736
Submit job case.st_archive
Starting job script case.st_archive
st_archive starting
moving /home/xunbin/cesm/scratch/shanxispinup4/run/lnd.log.240416-170736 to /home/xunbin/cesm/archive/shanxispinup4/logs/lnd.log.240416-170736
moving /home/xunbin/cesm/scratch/shanxispinup4/run/cpl.log.240416-170736 to /home/xunbin/cesm/archive/shanxispinup4/logs/cpl.log.240416-170736
moving /home/xunbin/cesm/scratch/shanxispinup4/run/atm.log.240416-170736 to /home/xunbin/cesm/archive/shanxispinup4/logs/atm.log.240416-170736
moving /home/xunbin/cesm/scratch/shanxispinup4/run/cesm.log.240416-170736 to /home/xunbin/cesm/archive/shanxispinup4/logs/cesm.log.240416-170736
Cannot find a shanxispinup4.cpl*.r.*.nc file in directory /home/xunbin/cesm/scratch/shanxispinup4/run
Archiving history files for datm (atm)
Archiving history files for clm (lnd)
Archiving history files for mosart (rof)
Archiving history files for drv (cpl)
Archiving history files for dart (esp)
st_archive completed
Submitted job case.run with id None
Submitted job case.st_archive with id None

I opened the cesm.logfile and it showed:

surfrd_veg_all ERROR: sum of wt_nat_patch not 1.00000000000000 at nl=
118468
sum is: 1.43000000000000
ENDRUN:
ERROR: ERROR in surfrdUtilsMod.F90 at line 80
surfrd_veg_all ERROR: sum of wt_nat_patch not 1.00000000000000 at nl=
156295
sum is: 1.51000000000000
ENDRUN:
ERROR: ERROR in surfrdUtilsMod.F90 at line 80
surfrd_veg_all ERROR: sum of wt_nat_patch not 1.00000000000000 at nl=
175196
sum is: 1.59000000000000
ENDRUN:
ERROR: ERROR in surfrdUtilsMod.F90 at line 80
surfrd_veg_all ERROR: sum of wt_nat_patch not 1.00000000000000 at nl=
194097
sum is: 1.36000000000000
ENDRUN:
ERROR: ERROR in surfrdUtilsMod.F90 at line 80
surfrd_veg_all ERROR: sum of wt_nat_patch not 1.00000000000000 at nl=
137367
sum is: 1.10000000000000
surfrd_veg_all ERROR: sum of wt_nat_patch not 1.00000000000000 at nl=
212998
sum is: 1.35000000000000
ENDRUN:
ERROR: ERROR in surfrdUtilsMod.F90 at line 80
ENDRUN:
ERROR: ERROR in surfrdUtilsMod.F90 at line 80
surfrd_veg_all ERROR: sum of wt_nat_patch not 1.00000000000000 at nl=
231901
sum is: 1.20000000000000
ENDRUN:
ERROR: ERROR in surfrdUtilsMod.F90 at line 80

I attached the cesm.log file behind. I wonder what is the meaning of wt_nat_patch? Does it point to the third subgrid level -- patch level mentioned in the CLM Technical Note? Could you please give me some advice about this error? Noted that I have changed the land use, PFT, LAI and soil texture data in the surfdata file.
Any advice would be greatly appreciated. Thank you.
 

Attachments

  • cesm.log.240416-170736.txt
    10.8 KB · Views: 0

oleson

Keith Oleson
CSEG and Liaisons
Staff member
Yes, it is the third subgrid level - patch level. Since you are using a custom surface dataset, it probably means that the sum of your plant functional types are not adding up to 100% in each gridcell, rather the sum seems to be greater than 100%.
 
Top