comp.lang.idl-pvwave archive: archive » memory allocation for structure arrays

Home » Public Forums » archive » memory allocation for structure arrays

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

Re: memory allocation [message #16447 is a reply to message #11586]

Tue, 27 July 1999 00:00

Craig Markwardt
Messages: 1869
Registered: November 1996

Senior Member

davidf@dfanning.com (David Fanning) writes:
>
> Essa Yacoub (yacoub@cmrr.umn.edu) writes:
>
>> I am assigning an array using the complex function
>>
>> rd=
>> complex(mag_regress*cos(phase_regress),mag_regress*sin(phase _regress))
>>
>>>> 99% of the time this turns out to be a programming error >>>
>>
>> the code works, because I have successfully used it on several data
>> sets of
>> different sizes. In this particular case, the data size is much
>> larger. I am running
>> this on an sgi onyx 2 system with 2 gig of ram, so that should not
>> be
>> a problem. In fact I can open another session in another window and
>> create bigger arrays with no problem. It actually crashed before
>> this above statement
>> and I zeroed an array I was no longer using and it continued a while
>> longer.
>> (using .con) before crashing again at a different line.
>
> I'm going to guess that there are more of these large arrays
> hanging around that you are also not cleaning up. When you
> ...

David makes some good suggestions for being memory efficient in your
IDL programs. However, if you are running on a Unix system you may be
running into the memory limit for a single process. Memory footprints
for processes are typically limited to prevent a single task from
hogging all of the resources, but often this is what you want!

You can try either limit (csh or tcsh) or ulimit (sh). By itself,
"limit" produces this output for me on an alpha machine:

[33]> limit
...
datasize 131072 kbytes
...

If you get a small number like I did, then you can try increasing it,
like so,

limit datasize 2048M # 2048 megabytes = 2 gigabytes

Usage may vary, depending on your shell and Unix version. If you
can't increase it yourself, it's time to abase yourself to your
sysadmin.

Good luck,
Craig

--
------------------------------------------------------------ --------------
Craig B. Markwardt, Ph.D. EMAIL: craigmnet@cow.physics.wisc.edu
Astrophysics, IDL, Finance, Derivatives | Remove "net" for better response
------------------------------------------------------------ --------------

Report message to a moderator

[Message index]

		memory allocation for structure arrays By: Ian Sprod on Wed, 29 April 1998 00:00
		Re: memory allocation for structure arrays By: mallors on Sat, 02 May 1998 00:00
		Re: memory allocation for structure arrays By: Ian Sprod on Fri, 01 May 1998 00:00
		Re: memory allocation for structure arrays By: korpela on Thu, 30 April 1998 00:00
		Re: memory allocation By: Essa Yacoub on Tue, 27 July 1999 00:00
		Re: memory allocation By: Liam Gumley on Tue, 27 July 1999 00:00
		Re: memory allocation By: Craig Markwardt on Tue, 27 July 1999 00:00
		Re: memory allocation By: davidf on Mon, 26 July 1999 00:00
		Re: memory allocation By: Essa Yacoub on Mon, 26 July 1999 00:00
		Re: memory allocation By: davidf on Mon, 26 July 1999 00:00

Previous Topic:	password-entry widget
Next Topic:	Re: idlwave mode for emacs/xemacs?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 08:05:19 PDT 2025

Total time taken to generate the page: 0.95971 seconds