comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » strange results using max_value in a contour plot
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
strange results using max_value in a contour plot [message #32381] Fri, 04 October 2002 13:04 Go to next message
ddye is currently offline  ddye
Messages: 5
Registered: October 2002
Junior Member
IDL version 5.4 (IRIX mipseb)

I'm encountering strange results using max_value in a contour plot.
I'm attempting to set unwanted data to a # outside of the range
(larger than max_value). The funny thing is the contour works fine
_unless_ the unwanted values are _over_ the max_value. If I set it to
zero: it plots as zero, 1/2 of the range: the appropriate color, a
little over the max_value and the whole contour plots white (which is
appropriate for zero values:.0000001). I read in previous posts that
this was a legitimate use for max_value, what the heck is going on?

Here is the code in question:
;********** snip ******************

;the following can be used to set the bathymetry to any #
;// v-- (changed this to lots of values)
for in=0,58 do begin
tmparr4[60-in,bathy[in]:*]=9.99E29
endfor

;************************************** row 2 col 3
contour,tmparr4,distance,depth $
,xrange=[1,60],yrange=[40,0] $
,titl=titl4 $
,levels=scale4zed $
,c_labels=clab $
,C_COLORS=[addC,cvec1] $
,/fill, /closed $
,max_value=ignore $
,FONT=0
resolved strange results: /fill -> /cell_fill [message #32462 is a reply to message #32381] Mon, 07 October 2002 11:56 Go to previous message
ddye is currently offline  ddye
Messages: 5
Registered: October 2002
Junior Member
I've tracked the strange results to my use of /fill, rather than
/cell_fill

"Use this keyword (/cell_fill) instead of FILL when you are drawing
filled contours over a map, when you have missing data, or when
contours that extend off the edges of the contour plot."

Note: Due to the same error I also encountered strange results when
attempting to set the data to:
!Values.F_NaN

-d

ddye@flenvironmental.org (Dan Dye) wrote in message news:<dfc65bba.0210041204.50d23a53@posting.google.com>...
> IDL version 5.4 (IRIX mipseb)
>
> I'm encountering strange results using max_value in a contour plot.
> I'm attempting to set unwanted data to a # outside of the range
> (larger than max_value). The funny thing is the contour works fine
> _unless_ the unwanted values are _over_ the max_value. If I set it to
> zero: it plots as zero, 1/2 of the range: the appropriate color, a
> little over the max_value and the whole contour plots white (which is
> appropriate for zero values:.0000001). I read in previous posts that
> this was a legitimate use for max_value, what the heck is going on?
>
> Here is the code in question:
> ;********** snip ******************
>
> ;the following can be used to set the bathymetry to any #
> ;// v-- (changed this to lots of values)
> for in=0,58 do begin
> tmparr4[60-in,bathy[in]:*]=9.99E29
> endfor
>
> ;************************************** row 2 col 3
> contour,tmparr4,distance,depth $
> ,xrange=[1,60],yrange=[40,0] $
> ,titl=titl4 $
> ,levels=scale4zed $
> ,c_labels=clab $
> ,C_COLORS=[addC,cvec1] $
> ,/fill, /closed $
> ,max_value=ignore $
> ,FONT=0
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Calling IDL from a remote shell
Next Topic: Form building in IDL.

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 19:58:53 PDT 2025

Total time taken to generate the page: 0.00732 seconds