| change in histogram [message #12423] |
Tue, 28 July 1998 00:00 |
Vap User
Messages: 31
Registered: April 1998
|
Member |
|
|
Has there been a change to histogram in IDl 5.1? The documentation
says that the array is searched for the min/max values if min=/max=
keyword are missing. However, consider the following...
IDL> help,histogram( bindgen(100) )
<Expression> LONG = Array[256]
which suggests it sets max to the top value possible for a byte array.
IDL> help,histogram( indgen(100) )
<Expression> LONG = Array[100]
As desired.
IDL> help,histogram( bindgen(100) + 2 )
<Expression> LONG = Array[100]
Also as desired. But stranger still, since this is effectively the case above.
Am I missing something here?
Also...
Here's another oddity.
IDL> help,histogram( lindgen(100),binsize=0.5 )
% HISTOGRAM: Illegal binsize or max/min.
% Execution halted at: $MAIN$
IDL> help,histogram( lindgen(100),binsize=1.5 )
<Expression> LONG = Array[100]
IDL> help,histogram( findgen(100),binsize=0.5 )
<Expression> LONG = Array[199]
Why can't I specify a binsize of 1/2 with a interger type array? I can
specify one of 1.5. And I can specify one of 0.5 for a floating point
array having the same values as the integer type array.
I don't recall these restriction in IDl 4.x.
--
I don't speak for JPL, it doesn't speak for me.
Well, not all the time, at least.
William Daffer <vapuser@haifung.jpl.nasa.gov>
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
