We just added HDF5 support in our application. We are using the C API. Our
datasets are 1D and 2D arrays of integers, a pretty simple structure on
disk. Today we have about 5GB of data and we load the whole thing into RAM,
do somewhat random reads, make changes, then overwrite the old .h5 file.
I
Hi, this is my first post to hdf-forum so apologies in advance for anything
that is redundant that I've missed in previous posts. I have a process that
is running for several hours opening and reading from many hdf files. The
heap memory is constantly growing, and because all memory is returned u
Finally developed things to a point that I can get useful performance
numbers for my application. So far, things look good. But, when I look
at the performance numbers I see behavior I don't expect -- namely,
that my write throughput is almost 2x greater than my read throughput.
My system
Thanks for replying... this is the path I thought would let me create a test
HDF5 file with 4 datasets and importing
data from a file...
HDFView:
1) New -> HDF5 (Test.h5)
2) Right click on Test.h5, New -> Dataset
Dataset Name: Sensor1
Datatype class: Float, Size: native, Byte ordering: nati
Hi Jonathan,
Could you be more specific how you did it?
Thanks
--pc
On 12/3/2010 11:22 AM, Hillman, Jonathan E wrote:
I am trying to create a trivial HDF5 formatted file with HDFView. I created 4
datasets of single diminsion with 1 item and unlimited max size each for
testing.
I assumed I co
I am trying to create a trivial HDF5 formatted file with HDFView. I created 4
datasets of single diminsion with 1 item and unlimited max size each for
testing.
I assumed I could load the data using import data from file, but that doesn't
seem to work.
Am I attempting to do something not intend
Hi,
Using hdf1.8.5 and 1.8.6 pre2; openmpi 1.4.3 on linux rhel4 and rhel5
In a case where the hdf5 operations aren't using MPI but build an h5
file exclusive to individual MPI jobs/processes:
The create:
currentFileID = H5Fcreate(filePath.c_str(), H5F_ACC_TRUNC, H5P_DEFAULT,
H5P_DEFAULT);