comp.lang.idl-pvwave archive: archive » Re: problems with VELOVECT

Home » Public Forums » archive » Re: problems with VELOVECT

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: problems with VELOVECT [message #26362 is a reply to message #26359]

Tue, 21 August 2001 08:31

Lasse Clausen
Messages: 22
Registered: August 2001

Junior Member

Again me.

i've looked at the source code of VELOVECT.PRO and there are some things
I find suprising.

1)
PRO VELOVECT,U,V,X,Y, Missing = Missing, Length = length, Dots = dots,
$
Color=color, _EXTRA = extra

that's the 'header'. 'Missing' is written with capital M.
further down it says

if n_elements(missing) le 0 then missing = 1.0e30

isn't IDL type-sensitive?

2) then it says

if n_elements(missing) gt 0 then begin
good = where(mag lt missing)
if keyword_set(dots) then bad = where(mag ge missing, nbad)
endif else begin
good = lindgen(n_elements(mag))
endelse

Strange! this if-block is totally unessesary, i believe how can
'missing' not be greater than 0? if it's not set (or set to a negative
number) in the procedure call, its value is set to 1.0e30 (which is
obviously greater than 0). and if it's set, it's set to a positive
number. so how can it *not* be greater than 0?

any remarks?

Lasse Clausen

Report message to a moderator

[Message index]

		Re: problems with VELOVECT By: James Kuyper on Tue, 21 August 2001 09:34
		Re: problems with VELOVECT By: Lasse Clausen on Tue, 21 August 2001 09:02
		Re: problems with VELOVECT By: Lasse Clausen on Tue, 21 August 2001 08:31
		Re: problems with VELOVECT By: btt on Tue, 21 August 2001 08:26
		Re: problems with VELOVECT By: Lasse Clausen on Tue, 21 August 2001 08:04

Previous Topic:	STRMID question
Next Topic:	Local max filter

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu Oct 09 20:27:09 PDT 2025

Total time taken to generate the page: 1.91783 seconds