http://www.k-wave.org/forum/topic/voxel-type-for-defining-medium-properties-in-3d Support for the k-Wave MATLAB toolbox en-US Tue, 12 May 2026 23:35:40 +0000 http://bbpress.org/?v=1.0.2 q http://www.k-wave.org/forum/search.php http://www.k-wave.org/forum/topic/voxel-type-for-defining-medium-properties-in-3d#post-6544 Mon, 06 Aug 2018 15:25:01 +0000 Jiri Jaros 6544@http://www.k-wave.org/forum/ <p>Hi umitarabul,</p> <p>that's a very good point! We've been working on this possibility for segmented data and called it "Labeled Materials". The implementation is being tested. It seems the runtime overhead is negligible, however, the structure of the input file has to be changed. Since we are also about to introduce a more general way of sensor and sources definition, I'd like to merge these two issues together.</p> <p>Best,<br /> Jiri </p> http://www.k-wave.org/forum/topic/voxel-type-for-defining-medium-properties-in-3d#post-6541 Tue, 31 Jul 2018 13:21:51 +0000 umitarabul 6541@http://www.k-wave.org/forum/ <p>Hi,</p> <p>I am using a large 3D grid 1024x1024x1024 and medium stores the same size matrix for each property. Instead, you could only store one matrix that stores the type of each voxel with an integer and a small property matrix that maps each voxel type to different property values.</p> <p>I have created an input.h5 with such medium that became over 30GB. I think if you make it as I suggested, it reduces the size significantly.</p> <p>Best, </p>