comp.lang.idl-pvwave archive: archive » Re: weird behaviour with cgdemodata

Home » Public Forums » archive » Re: weird behaviour with cgdemodata

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

Re: weird behaviour with cgdemodata [message #76620 is a reply to message #76619]

Tue, 21 June 2011 08:19

wlandsman
Messages: 743
Registered: June 2000

Senior Member

The problem is that the "input" parameter to cgdemodata is really an input-output parameter -- it is modified by cgdemodata(). For example,

IDL> i = 1 & print,N_elements(cgdemodata(i)) & print,i
101
0

The offending code in cgdemodata() is below. It should probably be rewritten so that the "number" parameter is left unmodified

FUNCTION cgDemoData_ReadData, number

IF N_Params() EQ 1 THEN BEGIN
type = Size(number)
type = type( type(0) + 1 )
IF type EQ 0 THEN Message, 'Supplied argument is undefined.'
IF type GT 5 THEN Message, 'Supplied argument must be a number.'
number = number - 1
number = 0 > number < 24
data = cgDemoData_ReadData(number)
RETURN, data
ENDIF

Report message to a moderator

[Message index]

		Re: weird behaviour with cgdemodata By: David Fanning on Tue, 21 June 2011 10:53
		Re: weird behaviour with cgdemodata By: Jeremy Bailin on Tue, 21 June 2011 09:28
		Re: weird behaviour with cgdemodata By: Foldy Lajos on Tue, 21 June 2011 09:10
		Re: weird behaviour with cgdemodata By: Jeremy Bailin on Tue, 21 June 2011 08:49
		Re: weird behaviour with cgdemodata By: Jeremy Bailin on Tue, 21 June 2011 08:28
		Re: weird behaviour with cgdemodata By: ben.bighair on Tue, 21 June 2011 08:27
		Re: weird behaviour with cgdemodata By: wlandsman on Tue, 21 June 2011 08:19

Previous Topic:	Composite images
Next Topic:	IDL IMAGE NAVIGATION

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 15:57:34 PDT 2025

Total time taken to generate the page: 0.00425 seconds