| A related question... [message #21173] |
Wed, 09 August 2000 00:00 |
Med Bennett
Messages: 109
Registered: April 1997
|
Senior Member |
|
|
OK, I have tried rewriting my procedure to reduce the number of main level
variables created by passing all of the variables it needs, rather than
running it as a main level program. However, I now get the message
'% Procedure/function called with too many parameters: XSPLOT.'
I'm trying to give it 14 variables as parameters. What's a lousy programmer
to do?
Med Bennett wrote:
> Greetings,
>
> I am having a rather severe problem with IDL 5.0.2. I have a IDL data
> file with a lot of variables, currently about 250. When I ran a program
> that created som new variables, I found to my horror that IDL was
> replacing variable contents with the contents of other variables, i.e. a
> variable called 'AREAID', intead of being a string array of size 16, was
> now a float[193], etc. This was occuring without any warnings or error
> messages being given; only when some of my routines begin failing due
> to data having been overwitten did I realize what was going on. It
> appears that when I attempted to create variables in excess of 255 (a
> guess) , IDL began to randomly reassign existing variables with new
> contents. This is very disturbing, as the integrity of a lot of my data
> is now in question. Some questions: Is there an absolute limit on the
> number of variables in a .sav file? Do later versions of IDL have this
> limit? Why is there no warning of a limit being reached? I realize now
> that I need to compartmentalize my data and reduce the number of
> variables in a single session, but I'm curious if others have had this
> problem or have any suggestions. Thanks in advance-
>
> A slightly panicked
> Med Bennett
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
