|
Hi David, Thanks for writing. First, we should add PROLEPTIC_GREGORIAN as one of the calendars Ferret recognizes, as the default calendar Ferret uses IS a Proleptic Gregorian calendar! Unfortunately, the way Ferret currently treats this calendar, we can't fix up the axis quite as simply as you suggest, but we can do it. When Ferret reads in the header of the file, it saves the attributes of the coordinate variable TIME, and we can use these to redefine the axis correctly. yes? use "http://esgcet.llnl.gov/cgi-bin/dap-cgi.py/ipcc4/20c3m/giss_aom/pcmdi.ipcc4.giss_aom.20c3m.run1.atm.mo.xml" yes? sh att/all (time) attributes for dataset: http://esgcet.llnl.gov/cgi-bin/dap-cgi.py/ipcc4/20c3m/giss_aom/pcmdi.ipcc4.giss_aom.20c3m.run1.atm.mo.xml (time).units = DAYS since 1-JAN-1850:00:00 (time).bounds = time_bnds (time).orig_file_axname = time (time).time_origin = 1-JAN-1850:00:00 yes? define axis/t/units=days/t0="1-jan-1850:00:00" `tauu,return=taxis` = t[gt=time] yes? sh grid tauu GRID GJJ3 name axis # pts start end LON LONGITUDE 90mr 2E 2W LAT LATITUDE 60 r 88.5S 88.5N normal Z TIME TIME 1812 r 02-JAN-1850 00:00 18-DEC-1854 00:00 Now, notice that when we say the time origin is 'days since 1-jan-1850', then the first time step of 1 represents 2-jan-1850. If you think that the intent was for the first step to be on 1-jan-1850, then you could use (t[gt=time]-1) in the right hand side of the definition above. David Wang wrote: Hi Ferreters, |