|
|
| Re: Strange behaviour ? of Subscript range values of the form low:high [message #76528 is a reply to message #76526] |
Fri, 17 June 2011 04:17   |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
David Fanning writes:
> P.S. And WShow continues to work intermittently, and
> in no consistent way that I can understand.
This appears to be related, now that I think about it,
to another behavior I just noticed again a moment ago.
Graphics windows sometimes appear in front of the
Workbench when they are created, but nearly as
often appear (well, "appear" is the wrong word!)
*behind* the Workbench!
There doesn't appear to be any predicable pattern to
this. Sometimes the very same program will appear in
front of the Workbench this time and behind the next
time the program is run, and visa versa. Something
seems to be screwed up in the way these windows are
ordered on the display.
This certainly makes working on a laptop challenging. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thue. ("Perhaps thos speakest truth.")
|
|
|
|
| Re: Strange behaviour ? of Subscript range values of the form low:high [message #76529 is a reply to message #76528] |
Fri, 17 June 2011 02:52 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
LNpellen writes:
> Well - I checked the variables were scalars with the expected values.
> Hard coding the same values worked...
> The code worked for other datasets.
>
> Today is another day - and suddenly the same code works also for the
> dataset with the problem.
> I have no idea why but I'm crossing fingers it will keep working.
Let me guess, IDL 8.1. I've been seeing strange things
like this all week long in a class I've been teaching!
Totally inexplicable behavior on my machine and others.
Yesterday, all of a sudden, it appeared as if IDL
couldn't remember my IDL path! I couldn't get anything
to compile automatically. I exited IDL, restarted, and
all was well. Very strange...
Cheers,
David
P.S. And WShow continues to work intermittently, and
in no consistent way that I can understand.
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thue. ("Perhaps thos speakest truth.")
|
|
|
|
|
|
|
|
|
|
| Re: Strange behaviour ? of Subscript range values of the form low:high [message #76628 is a reply to message #76526] |
Tue, 21 June 2011 00:33 |
LNpellen
Messages: 37
Registered: November 2009
|
Member |
|
|
The story goes on - and the problem occurs again and this time even
stranger (to me).
I stop my code just before the error occurs and do some printouts:
IDL> help, doseTemp
DOSETEMP FLOAT = Array[502, 494]
IDL> help, doseTempFull
DOSETEMPFULL FLOAT = Array[512, 512]
IDL> print, x1,x2,y1,y2
5 506 3 496
IDL> doseTempFull[5:506,3:496]=doseTemp
IDL> doseTempFull[x1:x2,y1:y2]=doseTemp
Everything works fine to this point. The latter line above is the next
line in the code and it appears to run with no errors so lets continue
the code:
IDL> .cont
% XMANAGER: Caught unexpected error from client application. Message
follows...
% Subscript range values of the form low:high must be >= 0, < size,
with low <= high: DOSETEMPFULL.
% Execution halted at: GENERATEDOSEDISPLAY 106 P:\RTPlanViewer
\RTPlanViewer\generateDoseDisplay.pro
% RTPLANVIEWER_EVENT 291 P:\RTPlanViewer
\RTPlanViewer\RTPlanViewer_event.pro
% XMANAGER_EVLOOP_STANDARD 478 C:\Programfiler
\ITT\IDL71\lib\xmanager.pro
% XMANAGER 708 C:\Programfiler\ITT
\IDL71\lib\xmanager.pro
% RTPLANVIEWER 109 P:\RTPlanViewer
\RTPlanViewer\RTPlanviewer.pro
% $MAIN$
So the "doseTempFull[x1:x2,y1:y2]=doseTemp" works in command line, but
not in the code..... I understand nothing.
Ellen
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
