k-Wave

1. jwjs
   

   Member
   Joined: Jun '11
   Posts: 14

   Hi Brad/Jiri,

   I started digging through the code a little bit today and was hoping to find something that would allow me to read data back in from the output file (much like the input settings are read in). Unfortunately I didn't find anything, but maybe I'm missing something obvious?

   What I was wanting is to read sensor data back in based on time steps of the simulation (i.e. for each time step read in its corresponding sensor data). I'm producing extremely large amounts of data in my simulations (constant out of memory issues with Matlab) and was wanting to read in sensor data, per time step, in order to get around this issue and hopefully leave behind Matlab all together. It seems like there is still a lot of work going on with this and wanted to see if this was planned or already underway before I started implementing this.

   I'm guessing it would just be something along the lines of reading in HyperSlabs much like they're written out?

   Posted 11 years ago #

2. Jiri Jaros
   

   Developer
   Joined: Feb '12
   Posts: 115

   Hi jwjs
   It’s quite easy. What you need to do is to select a Hyperslab and then read data from it.

   The 'p', 'ux', 'uy', 'uz' variables are stored as 3D arrays in the output file with dimension sizes of (1, Nt, sensor_size ). Please note that the dimension sizes are written in (Z, Y, X) order in the C++ code.

   If you want for example the sensor data from the 10th timestep you’d write:
   

   int offset[] = {1, 10, sensor_size};  // !dims in Z, Y, X order!
   int count [] = {1,  1, sensor_size};  // !dims in Z, Y, X order!
   H5Sselect_hyperslab (dataspace, H5S_SELECT_SET, offset, NULL, count, NULL);

   This returns a single slab containing data recorded in the 10th timestep, which you can read then.
   You can find more details on how to select a hyperslab at http://www.hdfgroup.org/HDF5/Tutor/select.html

   You can use the function THDF5_File::WriteHyperSlab to write the function you need (just replace H5Dwrite with H5Dread).

   Posted 11 years ago #

3. jwjs
   

   Member
   Joined: Jun '11
   Posts: 14

   Hi Jiri,

   Thanks for the detailed response, it clears up some confusion I had with the layout of the data. Seems pretty straightforward, so I'm gonna go ahead and code it.

   Posted 11 years ago #

4. huangchao
   

   Member
   Joined: Nov '10
   Posts: 57

   Hi Jiri,

   You mentioned that the dimension sizes of the matrices are written in (Z, Y, X) order. However, I find that the size of 'pml_x' is defined by using 'TDimensionSizes(FullDim.X, 1, 1)', so I wonder why the order is not '(1, 1, FullDim.X)' here.

   And if I want to define a matrix with size 'sensor_size x Nt', and I want the 'sensor_size' being the first dimension, should I use 'TDimensionSizes(1, Nt, sensor_size)' or 'TDimensionSizes(sensor_szie, Nt, 1)'?

   Also, I want to set some matrices to be zero matrices, do you have any recommendation, like 'bzero' or 'memset'?

   Thanks,
   Chao

   Posted 11 years ago #

5. Jiri Jaros
   

   Developer
   Joined: Feb '12
   Posts: 115

   Hi Chao,

   1) All matrices are physically stored as Z, Y, X, and also, HDF5 library takes the dimension in Z, Y, X order.

   2) However, the class TDimensionSizes has a constructor that takes dimension sizes in the order of X, Y, Z. It’s just to help me keep the dimension sizes under control and in the same order as in MATLAB when registering the matrices in C++ code. So, in your case you should use TDimensionSizes(sensor_size, Nt, 1).
   You can alternatively create a variable of TDimensionSezes and set properties it's properties manually e.g.
   
TDimensionSizes Dims;
Dims.X = sensor_size;
Dims.Y = Nt;
Dims.Z = 1;


   3) To zero a matrix, you can call method ZeroMatrix(). This method also compiles with NUMA page placement.

   Jiri

   Posted 11 years ago #

RSS feed for this topic

Reply

You must log in to post.