Dear All,
i am getting following error,
CHECK_FILE - unable to find time variable in input NetCDF file:
/2000-2008/era_airtemp_2000_2008.nc
variable name does not contains the "time" string.
my NetCDF file details are below,
netcdf era_airtemp_2000_2008 {
dimensions:
XI_RHO = 361 ;
ETA_RHO = 253 ;
TAXIS = UNLIMITED ; // (26241 currently)
variables:
double XI_RHO(XI_RHO) ;
XI_RHO:standard_name = "grid_longitude" ;
XI_RHO:units = "degrees" ;
XI_RHO:axis = "X" ;
double ETA_RHO(ETA_RHO) ;
ETA_RHO:standard_name = "grid_latitude" ;
ETA_RHO:units = "degrees" ;
ETA_RHO:axis = "Y" ;
double TAXIS(TAXIS) ;
TAXIS:standard_name = "time" ;
TAXIS:units = "days since 1988-12-31 00:00:00" ;
TAXIS:calendar = "standard" ;
double AIR_TEMP(TAXIS, ETA_RHO, XI_RHO) ;
AIR_TEMP:long_name = "TAIR[GT=TAXIS@ASN]" ;
AIR_TEMP:_FillValue = -1.e+34 ;
AIR_TEMP:missing_value = -1.e+34 ;
AIR_TEMP:history = "From roms_blk_at_2000" ;
// global attributes:
:CDI = "Climate Data Interface version 1.6.2 (http://code.zmaw.de/projects/cdi)" ;
:Conventions = "CF-1.0" ;
:history = "Mon Aug 22 11:17:05 2016: cdo mergetime era_airtemp_2000.nc era_airtemp_2001.nc era_airtemp_2002.nc era_airtemp_2003.nc era_airtemp_2004.nc era_airtemp_2005.nc era_airtemp_2006.nc era_airtemp_2007.nc era_airtemp_2008.nc era_airtemp_2000_2008.nc\n",
"FERRET V6.842 21-Aug-16" ;
:CDO = "Climate Data Operators version 1.6.2 (http://code.zmaw.de/projects/cdo)" ;
}
please help me to how to change "check_multifile.F" progreme according to my data...
CHECK_FILE - unable to find time variable in input NetCDF
Re: CHECK_FILE - unable to find time variable in input NetCD
You need to change the netcdf file instead. Just add the "time" attribute pointing to "TAXIS" to the AIR_TEMP variable and ROMS should be able to find it:
ncatted comes as part of the nco package from unidata.
Code: Select all
ncatted -O -a time,AIR_TEMP,a,c,TAXIS era_airtemp_2000_2008.nc
Re: CHECK_FILE - unable to find time variable in input NetCD
Dear Kate.
i followed, according your suggestions. but till it shows same error.
Thanks in advance.
i followed, according your suggestions. but till it shows same error.
Thanks in advance.
Re: CHECK_FILE - unable to find time variable in input NetCD
netcdf rainfall2000 {
dimensions:
XI_RHO = 361 ;
ETA_RHO = 253 ;
TAXIS = UNLIMITED ; // (366 currently)
variables:
double TAXIS(TAXIS) ;
TAXIS:units = "days since 1988-12-31 00:00:00" ;
TAXIS:axis = "T" ;
TAXIS:calendar = "GREGORIAN" ;
TAXIS:time_origin = "31-DEC-1988" ;
TAXIS:standard_name = "time" ;
double RAINFALL(TAXIS, ETA_RHO, XI_RHO) ;
RAINFALL:missing_value = -1.e+34 ;
RAINFALL:_FillValue = -1.e+34 ;
RAINFALL:long_name = "PRATE[GT=TAXIS@ASN]" ;
RAINFALL:history = "From roms_blk_prec_2000" ;
RAINFALL:time = "TAXIS" ;
// global attributes:
:history = "Thu Dec 28 14:58:22 2017: ncatted -O -a time,RAINFALL,a,c,TAXIS rainfall2000.nc\n",
"FERRET V7.2 (optimized) 27-Dec-17" ;
:Conventions = "CF-1.6" ;
I done like that, till i am getting error.
dimensions:
XI_RHO = 361 ;
ETA_RHO = 253 ;
TAXIS = UNLIMITED ; // (366 currently)
variables:
double TAXIS(TAXIS) ;
TAXIS:units = "days since 1988-12-31 00:00:00" ;
TAXIS:axis = "T" ;
TAXIS:calendar = "GREGORIAN" ;
TAXIS:time_origin = "31-DEC-1988" ;
TAXIS:standard_name = "time" ;
double RAINFALL(TAXIS, ETA_RHO, XI_RHO) ;
RAINFALL:missing_value = -1.e+34 ;
RAINFALL:_FillValue = -1.e+34 ;
RAINFALL:long_name = "PRATE[GT=TAXIS@ASN]" ;
RAINFALL:history = "From roms_blk_prec_2000" ;
RAINFALL:time = "TAXIS" ;
// global attributes:
:history = "Thu Dec 28 14:58:22 2017: ncatted -O -a time,RAINFALL,a,c,TAXIS rainfall2000.nc\n",
"FERRET V7.2 (optimized) 27-Dec-17" ;
:Conventions = "CF-1.6" ;
I done like that, till i am getting error.
Re: CHECK_FILE - unable to find time variable in input NetCD
Dear Kate.
I am waiting for your reply. i followed your suggestion, till i am getting error
I am waiting for your reply. i followed your suggestion, till i am getting error
Re: CHECK_FILE - unable to find time variable in input NetCD
Well, I don't know why this is happening either. I would compile in debug mode and watch what happens in a debugger. Failing a debugger, I would add print statements in the appropriate place, which is probably get_cycle.F.