> By default a series is loaded into memory all at once so you could be
> definitely outstripping available resources once you enlarge your
> series.
>
I am aware of that, but this is a time series of 6 time steps where each
time step is a scalar field on 64x32 points. The positions are the same
for all fields and connected through the same quad connection
throughout. This is a total of ~200k of data in the raw netCDF file.
Even though it blows up inside the visualizer due to the extra
information you need to keep available it still seems odd that it does
not work on a system with 6GB of RAM.
In fact, I now repeated the test using a 6x6 mesh instead and the import
module crashes if I have 6 time steps, but works ok when I have 5 time
steps. Admittedly, this was on a 128 MB linux system and using the
command line:
dx -memory 32 -local -host localhost &
But this same system and command line happily displays an 8x8x8 3D mesh
and the 64x32 mesh provided the time series is no longer than 5 time
steps.
I am by no means ruling out that I am doing something wrong. Possibly in
the structure of my netCDF file. But I don't believe it is a system
resource issue.
Anyway, thanks for the input. I'd be more than thankful if anyone could
find out where the problem lies.
Cheers,
/Nils
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Nils Smeds
HPCSU / Sci & Techn. e-mail: [EMAIL PROTECTED]
UNSW, NSW 2052 Voice: +61-2-9385 6915
Sydney Fax: +61-2-9385 ----
AUSTRALIA Office: Red Centre, West, Rm 2075
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Nils Smeds http://www.pdc.kth.se/
Center for Parallel Computers e-mail: [EMAIL PROTECTED]
Royal Institute of Technology Voice: +46-8-7909115
KTH Fax: +46-8-247784
S-100 44 Stockholm, Sweden Office: OB2, room 1546
-----------------------------------------------------------------------
