[Thread Prev][Thread Next][Index]

Re: [ferret_users] @max and @min functions



Dear Russell,
        The original files (e.g. ocn_temp_0.nc) are ok and can be read. I am using nco-3.9.5 and netcdf-3.6.2 versions. What is exactly meant by version of NCO is broken? how to overcome this broken version?

Thanks & Regards,
Sandip.


On Tue, Mar 23, 2010 at 6:08 AM, Russell Fiedler <russell.fiedler@xxxxxxxx> wrote:
Hi,

Sandip's attachment indicates that he is getting ludicrous high and low values for temperature.
If the original files (e.g. ocn_temp_0.nc ) are ok and can be read then I would suspect that your version
of NCO is broken. Otherwise it looks like whatever is generating the original files is producing rubbish
(possibly not masking values correctly or using the wrong precision). Linking to an incorrect version of
the netCDF library can also cause this sort of problem especially if using autopromotion to double precision.

Russ

On Tuesday 23 March 2010 02:58, Ansley Manke wrote:
> Hi Sandip,
> What Ferret does  when it reads a data field that is stored as NC_DOUBLE is to convert it to FLOAT.  It does the conversion using a call to netCDF library, and so the error message comes from that library. The error message indicates that apparently there are values that can't be represented as FLOAT.  The missing-value flag listed here is typical for  data that we see. It should be representable in single-precision floating point. I can only assume that there are other values in the data field that are causing the problem
>
> temp: # dim. = 4, NC_DOUBLE, # att. = 3, ID = 3
> temp dimension 0: TIME, size = 12 NC_DOUBLE, dim. ID = 0 (CRD)(REC)
> temp dimension 1: zt, size = 1 NC_FLOAT, dim. ID = 3 (CRD)
> temp dimension 2: grid_y_T, size = 6 NC_FLOAT, dim. ID = 2 (CRD)
> temp dimension 3: grid_x_T, size = 6 NC_FLOAT, dim. ID = 1 (CRD)
> temp memory size is 12*1*6*6*nco_typ_lng(NC_DOUBLE) = 432*8 = 3456 bytes
> temp attribute 0: long_name, size = 52 NC_CHAR, value = THETA_FO(SALT_EXTRAP,TEMP_EXTRAP,Z[G=TEMP_EXTRAP],0)
> temp attribute 1: units, size = 7 NC_CHAR, value = nounits
> temp attribute 2: missing_value, size = 1 NC_DOUBLE, value = -9.99999979021e+33
>
>
> What version of Ferret are you running?
>
> Ansley
>
> sandip tikar wrote:
>
> Hi ,
>    I am trying @max transformation by using
>              list TEMP[I=@max,J=@max,K=@max,L=@max]
>    but I am getting error as
>              **netCDF error
>              NetCDF: Numeric conversion not representable (OPeNDAP/netCDF Error code -60)
>              Data set: ./VL_58.nc
>
>             After analyzing in detail, I think it can be problem because of double with an exponent too large to be represented in a float. The part of data, metadata is attached for reference. This file is generated by using ncks command.
>             How should I resolve this Numeric conversion issue ?
>
> Thanks & Regards,
> Sandip
>
>
>
>
>
> On Tue, Mar 9, 2010 at 3:39 AM, Ansley Manke <Ansley.B.Manke@xxxxxxxx<mailto:Ansley.B.Manke@xxxxxxxx>> wrote:
> Sandip,
> In Users' Guide Index under "Transformations" there are links to the general information about transformations and some examples.
>
> The syntax is to list the transformations you want for each axis.  Here are a few more examples.  Try them out on your data-
> var[x=@max,y=@max,z=@max,t=@max] ! @MAX transformation over the whole range of all axes
> var[x=@max,y=@max,z=@max]  ! The maximum over X, Y, and Z for each time
> var[x=300:330@max,y=0:40@max,Z=@max,T=@max]  ! Just a sub-range on some axes.
> var[x=300:330@max,y=0:40@max,Z=@max,T=@AVE] ! The time average of the max over XYZ.
>
> sandip tikar wrote:
> Dear all,
>         I am not familiar with ferret. I want to find maximum and minimum values in 4D variable ( with I=1:4320, J=1:2160, K=1:70, L=1:12 ) . How should I use @min and @max functions for this? I will  also like to use @ngd and @nbd functions to get good and bad points.
>        It will be really useful for me if someone can point to good references.
>
>
> Thanks & Regards,
> Sandip.
>
>
>


[Thread Prev][Thread Next][Index]

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

Privacy Policy | Disclaimer | Accessibility Statement