Internal variable "lev" undefined

[Henrique Barbosa]

Dear Ron,

You will have to give more information on your problem.

How's your data packed? Is it grib? hdf? netcdf? binary?
Could you send the ctl and place the binary somewhere
so that we could try it?

Are you sure to be using the same dataset within the
script and in the comand line? How does your script
define the level to be displayed? I mean what "set lev" or
"set z" do you have before your "display lev" command
in your script?

What's the result of 'query dims' just before 'd lev', both
at the command line and within the script?

[]'s
Henrique

On Dec 13, 2007 4:43 PM, Goodson,Ron [Edm] <Ron.Goodson at ec.gc.ca> wrote:
>
>
>
> Hi
>
> Sorry if the answer to this already exists .. but I couldn't find it.
>
> I have a grib data file using pressure levels in a fairly standard way.
>
> When I do a "d lev", sometimes I get it reported as a constant value (at
> whatever level I'm at through "set lev 500", for example) - which is what I
> would expect ... and then .. sometimes I get "Cannot Contour grid - all
> undefined values".  Everything else is fine .. I can change levels and
> properly display data on those levels.  It is just the internal GrADS
> variable "lev" that seems to get lost for display
>
> Even stranger
>
> Even if  -d lev- does work using grads interactively ... using the same
> command in a script (a single line script that contains just 'd lev') does
> not work.  Eg .. suppose I have a script called junk.gs containing the
> single line 'd lev'.
>
> Enter from keyboard     d lev           may get back constant value (or may
> not)
> Enter from keyboard     junk.gs         will get back all undefined values,
> even if 'd lev' from keyboard worked.
>
> I'm stumped - and this is causing grief as it means I can't use "lev" in my
> script calculations.
>
> Anybody got any guesses
>
> Tks
>
> Ron Goodson     (grads 1.94b on RedHat Workstation)