[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #LCA-261543]: GrADS .ctl files

Hi Stefan-

I'm not reading the IDV support regularly now, but happened to notice this.  
Could you send the .ctl file for the WRFPost output?

Don Murray

> Full Name: Stefan Cecelski
> Email Address: address@hidden
> Organization: University of Maryland
> Package Version:
> Operating System:
> Hardware:
> Description of problem:
> Hi all,
> I know you aren't fully supporting GrADS files in your nightly build,
> but I'd thought I'd give you some feedback on my experiences thus far. I
> create .dat/.ctl pairs of my WRF output using ARWpost processing. When
> opening the .ctl file, I see all the variables created by ARWpost and
> the derived variables that can be calculated by IDV in the field selector
> window. However, plotting derived variables by IDV results in an error,
> and variables processed through ARWpost have values that range between
> -2E39 and 2E39 and look like just 'noise' when plotted. The error
> for the IDV derived variables comes from IDV not being able to find
> variables needed for calculation. I think this is because ARWpost(or
> other post processing software) changes the variable name to some other
> convention. I have tried plotting many ARWpost generated variables,
> and all just look like noise with extremely large(or small) values on
> the order of E39 to E42(or E-39 ect).
> I would attach my .dat/.ctl pairs, but my files are all well over
> 1GB. I can try to create a small subset of data if you all would be
> interested. Attached is a text file showing the error from trying to
> create Theta-E using IDV from the data.
> Thanks!
> V/R,
> Stefan

Ticket Details
Ticket ID: LCA-261543
Department: Support IDV
Priority: Normal
Status: Open

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.