-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
year 0000, 0001 not listed for time steps, non-modulo axes #362
Comments
Comment by @AnsleyManke on 4 Mar 2008 18:33 UTC
In the future it would be better to also test for whether the axis is of length Here is the current behavior: yes? define axis/t=15-jan-0000:15-dec-0000:2/modulo/units=month tax yes? define axis/t=15-jan-0000:15-dec-0004:6/units=month tax |
Comment by @AnsleyManke on 4 Mar 2008 18:42 UTC
|
Comment by @AndrewWittenberg on 16 Nov 2009 22:37 UTC |
Reported by @AnsleyManke on 15 Jan 2004 17:07 UTC
! Say I have a variable with a time axis that starts
! either in year 0000 or year 0001, e.g.
yes? def ax/t=1-jan-0000:1-jan-0003:1/unit=month tax1
yes? def ax/t=1-jan-0001:1-jan-0003:1/unit=month tax2
! Now in a script, how can one reliably extract the start
! year? In immediate mode, both of these axes return a string
! without a year:
yes? say
t[gt=tax1],r=tstart
01-JAN 00:00
yes? say
t[gt=tax2],r=tstart
01-JAN 00:00
yes? show grid/t t[gt=tax1]
GRID (G002)
name axis # pts start end
normal X
normal Y
normal Z
TAX1 TIME 38 r 01-JAN 00:00 31-JAN-0003 03:56
translate_to_world, calls secs_to_date. This ALWAYS replaces
year 0000 or 0001 in the date string with blanks.
Possible fix:
translate_to_world knows if the time axis in question is modulo.
If it's non-modulo, then keep the year string?
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/762
The text was updated successfully, but these errors were encountered: