NetCDF: Name contains illegal characters

[dhic27]

To report a non-security related issue, please provide:

• the version of the software with which you are encountering an issue
• environmental information (i.e. Operating System, compiler info, java version, python version, etc.)
• a description of the issue with the steps needed to reproduce it

If you have a general question about the software, please view our Suggested Support Process.

(base) [panbf@earth noahmpcn]$ cd Run/
(base) [panbf@earth Run]$ ls
BGCPARM.TBL Makefile Noah_hrldas_beta USGS_Biomass.nc
DISTR_HYDRO_CAL_PARMS.TBL MPTABLE.TBL Soil_CONUS-regrid.nc VEGPARM.TBL
GENPARM.TBL namelist.hrldas SOILPARM.TBL
geo_em.d01.nc NANI_US_1980-2016_input-ESMF_conserve.nc URBPARM.TBL
(base) [panbf@earth Run]$ ./Noah_hrldas_beta
wrfinput_flnm: '/work/panbf/try/wrfinput_d01'
wrfinput_flnm: '/work/panbf/try/wrfinput_d01'
SWC CHECK: IGBP reading: serial
Soil_CONUS-regrid.nc
Soil_CONUS-regrid.nc
Soil_CONUS-regrid.nc
Soil_CONUS-regrid.nc
Soil_CONUS-regrid.nc
Soil_CONUS-regrid.nc
Soil_CONUS-regrid.nc
SWC: CAUTIONS: YOU ARE READING NANI DATA*********
SWC CHECK: NANI reading: serial
NANI_US_1980-2016_input-ESMF_conserve.nc
NANI_US_1980-2016_input-ESMF_conserve.nc
NANI_US_1980-2016_input-ESMF_conserve.nc
NANI_US_1980-2016_input-ESMF_conserve.nc
NANI_US_1980-2016_input-ESMF_conserve.nc
-----------------------NANI_US_1980-2016_input-ESMF_conserve.nc
netcdf_flnm: '/work/panbf/try/data_input/INDIR/2000010103.LDASIN_DOMAIN1'
LDASIN TITLE attribute: OUTPUT FROM CONSOLIDATE_GRIB v20150518
ldasin_version = 20150518
LDASIN MMNINLU attribute: MODIFIED_IGBP_MODIS_NOAH
layer_bottom(1:4) = 0.1000 0.4000 1.0000 2.0000
layer_top(1:4) = 0.0000 0.1000 0.4000 1.0000
Soil depth = 0.100000 0.300000 0.600000 1.000000
k, dst_centerpoint(k) = 1 5.00000007E-02
k, dst_centerpoint(k) = 2 0.250000000
k, dst_centerpoint(k) = 3 0.700000048
k, dst_centerpoint(k) = 4 1.50000000

k, src_centerpoint(k) = 1 4.99999970E-02
k, src_centerpoint(k) = 2 0.249999985
k, src_centerpoint(k) = 3 0.699999988
k, src_centerpoint(k) = 4 1.50000000
(Near) match for destination layer: Taking destination layer at 0.0500 from source layer at 0.0500
(Near) match for destination layer: Taking destination layer at 0.2500 from source layer at 0.2500
(Near) match for destination layer: Taking destination layer at 0.7000 from source layer at 0.7000
(Near) match for destination layer: Taking destination layer at 1.5000 from source layer at 1.5000
k, dst_centerpoint(k) = 1 5.00000007E-02
k, dst_centerpoint(k) = 2 0.250000000
k, dst_centerpoint(k) = 3 0.700000048
k, dst_centerpoint(k) = 4 1.50000000

k, src_centerpoint(k) = 1 4.99999970E-02
k, src_centerpoint(k) = 2 0.249999985
k, src_centerpoint(k) = 3 0.699999988
k, src_centerpoint(k) = 4 1.50000000
(Near) match for destination layer: Taking destination layer at 0.0500 from source layer at 0.0500
(Near) match for destination layer: Taking destination layer at 0.2500 from source layer at 0.2500
(Near) match for destination layer: Taking destination layer at 0.7000 from source layer at 0.7000
(Near) match for destination layer: Taking destination layer at 1.5000 from source layer at 1.5000
INITIALIZE THREE Noah LSM RELATED TABLES
Skipping over LUTYPE = USGS
LANDUSE TYPE = MODIFIED_IGBP_MODIS_NOAH FOUND 20 CATEGORIES
INPUT SOIL TEXTURE CLASSIFICATION = STAS
SOIL TEXTURE CLASSIFICATION = STAS FOUND 19 CATEGORIES
SNOW HEIGHT NOT FOUND - VALUE DEFINED IN LSMINIT
SWC CHECK: USGS reading: serial
usgs: no using _PARALLEL
USGS_Biomass.nc
NTIME = 480002 KHOUR= 240000 dtbl = 1800.00000

**NetCDF: Name contains illegal characters

***** Problem nf90_def_var for /data/panbf/try/output/2000010103.LDASOUT_DOMAIN1

Note: The following floating-point exceptions are signalling: IEEE_INVALID_FLAG IEEE_OVERFLOW_FLAG IEEE_UNDERFLOW_FLAG IEEE_DENORMAL**

When I run ./Noah_hrldas_beta, the above error message appears. I checked the path in user_build_option and found no problem. The netcdf library is also installed correctly. I have tried various methods but still get the same error message.

From the error message, it is related to netcdf I/O issue, but I did not notice anything weird in my netcdf filename.