| Re: IDL memory limitation? [message #45609 is a reply to message #45488] |
Mon, 19 September 2005 10:46   |
Karl Schultz
Messages: 341
Registered: October 1999
|
Senior Member |
|
|
On Fri, 16 Sep 2005 17:18:09 -0400, IDLmastertobe wrote:
> Thank you everyone, here is my test result from memtest:
>
> Memory block # 1: 569 Mb (total: 569 Mb)
> Memory block # 2: 382 Mb (total: 951 Mb)
> Memory block # 3: 196 Mb (total: 1147 Mb)
> Memory block # 4: 183 Mb (total: 1330 Mb)
> Memory block # 5: 128 Mb (total: 1458 Mb)
> Memory block # 6: 88 Mb (total: 1546 Mb)
> Memory block # 7: 63 Mb (total: 1609 Mb)
> Memory block # 8: 59 Mb (total: 1668 Mb)
> Memory block # 9: 40 Mb (total: 1708 Mb)
> Memory block #10: 37 Mb (total: 1745 Mb)
>
> before I was visualing 3-D data on the size of say
> 50x50x10, now im visualizing data on the size of 250x250x1 and it is
> giving me error saying it can't allocate memory to create array. I check
Posting some more details or part of the actual code would really help
here.
You say that you have 3D data that is 50x50x10 and then you say 250x250x1,
which isn't clear to me. Did you mean 250x250x10? What is the type of
the data in the array? Byte? Float?
> the memory by using "help, /memory" and found the heap memory is used
> up. I am taking in 3D data and visualizing it by using IDLgrContainer.
> I created IDLgrModel and IDLgrAxis etc and put them together to
> visualize them. I can rotate it or flip it any way I want. It is a
> real time visualization. Does anyone know how I can overcome this
> memory problem? I currently have 1GB of RAM installed and 2GB of Virtual
> Memory allocated.
> Thanks.
IDLgrContainer is a container object and isn't capable of visualizing
anything on its own. There needs to be some sort of graphic
primitive like IDLgrSurface, IDLgrContour, IDLgrVolume, etc. Which one
are you using?
You mentioned the IDLgrAxis, but that's not the object that is handling
your actual data.
The amount of RAM and Virtual Memory that you have doesn't matter here if
you are asking for a block of contiguous memory that is larger than the
largest available free block. In your case, the largest free block WAS
569MB at the time you ran memtest. The size of the largest free block may
have been different at the time your application needed it. We won't know
until you tell us how you are visualizing your data.
Karl
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
