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

20050118: borked precip

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20050118: borked precip
  • Date: Tue, 18 Jan 2005 14:10:45 -0700
>From: "Patrick L. Francis" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200501182052.j0IKqNv2006785

>
>using the following script
>(also may login located /home/ldm/util/models/gfs/precip)
>
>any idea why i'm getting borked (overly high) precip values?
>i did take CINT way high simply because the values were there.
>
>


Patrick,

I don't see that you set "SCALE" anywhere in your script.
If you are setting specific contour values, you should 
set SCALE to the appropriate value (eg SCALE=0). Yur script
should set all values for the program, either within your
redirection, or from restore of a .nts file.

Otherwise, if you aren't setting it, then SCALE will be whatever is found
in the .nts file, and if its 999 (or blank), then the values will be scaled
by data range, which would not be necessarily 10**0).

I'd also explicitly set CONTUR and CURVE settings to make the contours smoother.

Steve Chiswell
Unidata User Support
--
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.