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

Home » Public Forums » archive » Re: Large Arrays 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: Large Arrays in IDL [message #5546 is a reply to message #5539] Fri, 12 January 1996 00:00 Go to previous message
kspencer is currently offline  kspencer
Messages: 21
Registered: December 1993
Junior Member
szoonem@astro.sunysb.edu (Saeid Zoonematkermani) writes:

> Hi;

> This is a question that concerns astronomers once in a while. I have
> wondered what the limit is to the size of the arrays that IDL can create.
> Some times IDL fails to read a FITS image complaining:

> % Unable to allocate memory: to make array.
> not enough core

> This is not so uncommon if one has to deal with even moderate size cubes.
> I have tried to use .SIZE to increase the default value for data area but
> it doesn't seem to work. So the question is if there is a way to open a
> very large image by IDL. IRAF seems to have no problem with this. Does
> this problem arise from lack of RAM on the computer?

I don't do astronomy and don't know about the FITS format, but the only
memory limitation for IDL is the total amount of RAM (physical and virtual)
on your system. Of course, if that memory space becomes fragmented, it will
seem like you have a lot less.

Kevin
-----------------------------------------------------------
Kevin Spencer
Cognitive Psychophysiology Laboratory and Beckman Institute
University of Illinois at Urbana-Champaign
kspencer@p300.cpl.uiuc.edu / kspencer@psych.uiuc.edu
-----------------------------------------------------------
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: IDL and PV-WAVE?
Next Topic: Re: Using GNU gcc to compile for CALL_EXTERNAL

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

Current Time: Sat Oct 11 14:38:13 PDT 2025

Total time taken to generate the page: 0.71876 seconds