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

netcdf error from NCD_IOLOCAL_REAL_1D

Hi all,

Has anyone else encountered this error:

HTAPES_WRAPUP: Creating history file ./B.jgr.dgvm.dfc1br.clm2.h0.0401-01.nc
at nstep = 10514232
Opening netcdf htape ./B.jgr.dgvm.dfc1br.clm2.h0.0401-01.nc
HTAPE_CREATE: Successfully defined netcdf history file 1

HTAPES_WRAPUP: Writing current time sample to local history file
./B.jgr.dgvm.dfc1br.clm2.h0.0401-01.nc at nstep = 10514232
for history time interval beginning at 146000.0000000000
and ending at 146031.0000000000

netcdf error from NCD_IOLOCAL_REAL_1D
ENDRUN: called without a message string

The resulting history file has all the field definitions but the fields themselves are all zeroes(including the lats and lons). This simulation has run 300 years and it consistently fails at that time year and month. I've looked at the subroutine ncd_iolocal_real_1D but so far have been unable to trace what's causing the error. I will try setting up the case again as a branch with the same name or startup run but just thought I'd ask in case anyone has any insight into probable causes.
 

slevis

Moderator
Staff member
Hi, Kendra. I haven't seen this particular error before, but given that the error appears at the same timestep every time, I wonder whether there are NaNs in some variable.

Sam
 
Thanks, Sam. That did occur to me although I thought that if NaNs were the case, it would at least have written out the other variables like the lats/lons and stopped at the erroneous one so I'd know which it is. This is one of my older deforestation runs without a preservation target and by this time, the trees have disappeared completely from several grid cells which could be causing an error somewhere...
 
Top