comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: IDL memory limits
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
RE: IDL memory limits [message #1383 is a reply to message #1381] Mon, 11 October 1993 22:55 Go to previous message
nowicki is currently offline  nowicki
Messages: 11
Registered: May 1993
Junior Member
In Article <293ieq$dtn@honey.st-and.ac.uk>
so1@st-andrews.ac.uk (Sean Oughton) writes:
> Hi,
>
> I'm processing some large 3 index arrays using IDL (98 x 96 x 96).
> ALtogether I need 9 of them active at once, but the msg I get when I
> run the .pro's is
>
> Unable to allocate memory: to make array
> not enough core.
>
> Is this an intrinisc IDL limitation or a h/w limit on my host machine
> (a VAXstation with 56 MB)?
>
> Has anyone else run into problems like this? ANy solutions/workarounds
> to suggest ?
>
> Thanks
>
> sean@tartan.dcs.st-and.ac.uk

Sean,

This error is causing by not allocating enough resources to handle all of
the arrays at one time. You need to look at several SYSUAF parameters as
they pertain to the username running IDL. These are: WSextent, WSquo,
and Pgflquo. There are some SYSGEN parameters that also may need tweeking.
Mail me for more info.

NOTE: By optimizing our IDL code, we have been able to put larger and
larger arrays without changing the accounts. This includes the use of
temporary arrays.

-Greg

/* Greg Nowicki | Mail Stop 401A | LIDAR Applications Group */
/* NASA Langley Research Center | Hampton, Virginia 23681-0001 */
/* Voice: (804) 864-2713 | FAX: (804) 864-7790 */
/* nowicki@tardis.larc.nasa.gov | My opinions and mine alone . . . */
[Message index]
 
Read Message
Read Message
Previous Topic: Compressed data
Next Topic: Bezier curves

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Oct 10 10:16:50 PDT 2025

Total time taken to generate the page: 1.28069 seconds