[Thread Prev][Thread Next][Index]

[ferret_users] Re: regarding no_calendar error



hi,

Please see the documentation for a discussion of calendar time axes,
http://ferret.pmel.noaa.gov/Ferret/documentation/users-guide/index-1/index#alph_c

You will need to regrid the data to a common time axis with one calendar definition.

-Ansley


On 4/3/2017 6:20 PM, saurabh rathore wrote:
Dear Ferreters,
I am getting an unexpected error of no_calendar axis while analysis of regression on time axis for two different variables. This the detail for the file and errors. I tried by inserting the same calendar axis but ohc is taking the calendar axis and nino34 is not taking the defined calendar axis.

use "/media/srathore/original_en.nc"
use "/media/srathore/nino_reg.nc"

define axis/edges/t/units=months/t0=15-dec-2004/t=15-jan-2005:15-jan-2016:1/calendar=360_days tmonthly

let ohc=ohcg_en[d=1,gt=tmonthly@asn]
let nino34=noi34[d=2,gt=tmonthly@asn]

let/quiet p=nino34
let/quiet q=ohc

go regresst

plot/ov/nolab/nokey q,qhat

**ERROR: inconsistent data grids: Differing calendar axes:
          first variable is on NO_CALENDAR axis
          subsequent variable is on 360_DAY axis
plot/ov/nolab/nokey q,qhat
Command file, command group, or REPEAT execution aborted

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! variable detail !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
currently SET data sets:
    1> /media/srathore/original_en.nc
 name     title                                                                             I         J         K         L         M         N
 OHCG_EN  (OHCG_GA+OHCG_GB+OHCG_GC+OHCG_G  ...       ...       ...       1:132     ...       ...
       (X=20E:20E(380))
 
    2> /media/srathore/nino_reg.nc  (default)
 name     title                                                      I         J         K         L         M         N
 NOI34    NINO34[D=1,GT=HIP@NRST]          ...       ...       ...       1:132     ...       ...
 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! details of file !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
​ncdump -h "/media/srathore/binny/phd1/phd/argo/ensemble/nino/ohc1/nino_reg.nc"
netcdf nino_reg {
dimensions:
    TIME = UNLIMITED ; // (132 currently)
    bnds = 2 ;
variables:
    double TIME(TIME) ;
        TIME:units = "days since 0001-01-01 00:00:00" ;
        TIME:long_name = "time" ;
        TIME:time_origin = "01-JAN-0001 00:00:00" ;
        TIME:axis = "T" ;
        TIME:bounds = "TIME_bnds" ;
        TIME:standard_name = "time" ;
    double TIME_bnds(TIME, bnds) ;
    double NOI34(TIME) ;
        NOI34:missing_value = -1.e+34 ;
        NOI34:_FillValue = -1.e+34 ;
        NOI34:long_name = "NINO34[D=1,GT=HIP@NRST]"
// global attributes:
        :history = "PyFERRET V7 (opt) 30-Mar-17" ;
        :Conventions = "CF-1.6" ;​

​In one of the previous ferret mail archived it is supposed to be a bug. So how to get rid of this problem.​

​Any help will be highly appreciated

regards, saurabh ​

--


REGARDS

Saurabh Rathore
Research Scholar (PhD.)
Centre For Oceans, Rivers, Atmosphere & Land Science Technology
Indian Institute Of Technology, Kharagpur
contact :- 91- 8345984434


[Thread Prev][Thread Next][Index]
Contact Us
Dept of Commerce / NOAA / OAR / PMEL / Ferret

Privacy Policy | Disclaimer | Accessibility Statement