[Thread Prev][Thread Next][Index]

Re: [ferret_users] 30-FEB with 360_day calendar

Hi Patrick,

In addition, Ferret doesn't understand the French term Février. The following works in Ferret v6.2 on linux:
def axis/t="01-JAN-1860":"30-FEB-1890":1/edges/units="Months"/cal=360_day simutaxis2


David Wang wrote:
Hi Patrick,

I'm not convinced that you can define a 360_day calendar time axis without specifying /cal=360_day in your axis definition. The Ferret default calendar is Gregorian.


On Fri, Sep 11, 2009 at 9:45 AM, Brockmann Patrick <Patrick.Brockmann@xxxxxx <mailto:Patrick.Brockmann@xxxxxx>> wrote:

    Hi all,

    Why the use of 30-FEB in a 360_day calendar causes an error ?
    it should be allowed because there is no mistake doing so with
    this type of calendar (month of 30 days).

    yes? def axis/t="01-JAN-1860":"30-FEV-1890":1/edges/units="Months"
    **ERROR: command syntax: 30-FEV-1890

    Tested with ferret v6.20


    Data Analysis and Visualization Engineer
    IPSL Global Climate Modelling Group

turn and live.

Fabian Lienert                  |  Canadian Centre for Climate Modelling and Analysis
PhD Candidate                   |  Environment Canada
phone: +1(250)721-7211          |  University of Victoria
cccma-student-003@xxxxxxxx      |  P.O. Box 1700
http://www.cccma.bc.ec.gc.ca    |  Victoria, BC,  V8W 2Y2, Canada

[Thread Prev][Thread Next][Index]

Contact Us
Dept of Commerce / NOAA / OAR / PMEL / TMAP

Privacy Policy | Disclaimer | Accessibility Statement