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

Home » Public Forums » archive » Re: running out of memory! can all memory be restored in idl?
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: running out of memory! can all memory be restored in idl? [message #34123 is a reply to message #34121] Wed, 26 February 2003 13:22 Go to previous messageGo to previous message
heald is currently offline  heald
Messages: 2
Registered: February 2003
Junior Member
wmc@bas.ac.uk wrote in message news:<3e551adc@news.nwl.ac.uk>...
> Colette <heald@fas.harvard.edu> wrote:
>> I'm running some fairly complex idl code on large satellite data sets
>> and I've encountered some memory barriers. I'd like to loop over a
>
> It may be operating system dependent. On our alphas, I need to say
>
> limit datasize unlimited
>
> to remove artificial memory limits. Try typing
>
> limit
>
> or
>
> ulimit and see if it says anything. What is you o/s?
>
> -W.

I've been told that our system does have all the artificial memory
limits removed.
Our sysadmin tells me that we're running Origin 200 with irex 6.5.3.
I'm using idl 5.3 in a multi-user configuration...at any time 6-8
people can be running idl off the same server system. Do you know if
idl shares memory from a common pool? I wonder if that may be
contributing to my problem. I'm finding it really frustrating to deal
with though since there seems to be no easy way to track memory within
idl (I'm finding the help, /memory command to be quite cryptic).
If you (or anyone else!) have any suggestions I'd love to hear them!

...Colette
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Matrix op speaks. Computer programmers needed to build matrix.
Next Topic: Re: The continuing saga of WHERE and 2D

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

Current Time: Fri Oct 10 06:14:17 PDT 2025

Total time taken to generate the page: 0.72227 seconds