You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by @AndrewWittenberg on 24 Jun 2011 22:48 UTC
CANCEL ATTRIBUTE/OUTPUT seems to have no effect on the NetCDF output for pseudovariables that refer to an explicit dataset number (which is often the case for pseudovariables).
In the following example, the output dataset b.nc still has the (ZAXLEVITR).point_spacing attribute, despite our telling Ferret to suppress it. And where did the extra (ZAXLEVITR).axis attribute come from?
NOAA/PMEL TMAP
FERRET v6.7
Linux rh5 (gfortran) 2.6.18-238.1.1.el5P - 05/06/11
24-Jun-11 18:36
yes? use levitus_climatology
yes? let a = temp[x=`@ave`,y=`@ave`]
yes? let b = temp[x=`@ave`,y=`@ave`,d=1]
yes? can att/output (`a,r=zaxis`).point_spacing
!-> can att/output (ZAXLEVITR).point_spacing
yes? save/q/clob/file="a.nc"/bounds a
yes? sp ncdump -h a.nc | grep "ZAXLEVITR:"
ZAXLEVITR:units = "METERS" ;
ZAXLEVITR:positive = "down" ;
ZAXLEVITR:bounds = "ZAXLEVITR_bnds" ;
yes? save/q/clob/file="b.nc"/bounds b
yes? sp ncdump -h b.nc | grep "ZAXLEVITR:"
ZAXLEVITR:units = "METERS" ;
ZAXLEVITR:positive = "down" ;
ZAXLEVITR:point_spacing = "uneven" ;
ZAXLEVITR:axis = "Z" ;
ZAXLEVITR:bounds = "ZAXLEVITR_bnds" ;
Reported by @AndrewWittenberg on 24 Jun 2011 22:48 UTC
CANCEL ATTRIBUTE/OUTPUT seems to have no effect on the NetCDF output for pseudovariables that refer to an explicit dataset number (which is often the case for pseudovariables).
In the following example, the output dataset b.nc still has the (ZAXLEVITR).point_spacing attribute, despite our telling Ferret to suppress it. And where did the extra (ZAXLEVITR).axis attribute come from?
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1863
The text was updated successfully, but these errors were encountered: