http://www.k-wave.org/forum/topic/3d-simulations-output-with-gpu Support for the k-Wave MATLAB toolbox en-US Wed, 13 May 2026 01:11:54 +0000 http://bbpress.org/?v=1.0.2 q http://www.k-wave.org/forum/search.php http://www.k-wave.org/forum/topic/3d-simulations-output-with-gpu#post-6200 Wed, 08 Nov 2017 14:47:55 +0000 HannaB 6200@http://www.k-wave.org/forum/ <p>Hi Brad<br /> Couldn't have been more helpful, thanks a lot !! </p> http://www.k-wave.org/forum/topic/3d-simulations-output-with-gpu#post-6198 Wed, 08 Nov 2017 13:45:13 +0000 Bradley Treeby 6198@http://www.k-wave.org/forum/ <p>Hi Hanna,</p> <p>When you use an object of the <code>kWaveTransducer</code> class as the sensor, the MATLAB implementation of <code>kspaceFirstOrder3D</code> will automatically average the signals across the grid points belonging to each transducer element using the appropriate delays. The output <code>sensor_data</code> will then contain as many time series as there are transducer elements.</p> <p>This behaviour is not implemented in the C++ code, so instead the output <code>sensor_data</code> will contain as many time series as the number of grid points that form the transducer. However, you can combine the data after the simulation using the <code>combine_sensor_data</code> of the <code>kWaveTransducer</code> class to give you the same output as when using the MATLAB code.</p> <p>Brad. </p> http://www.k-wave.org/forum/topic/3d-simulations-output-with-gpu#post-6197 Wed, 08 Nov 2017 11:58:25 +0000 HannaB 6197@http://www.k-wave.org/forum/ <p>Update: I think I understood the point but still have questions.</p> <p>The width of one element is 5 in grid units, and its length is 10 in grid units. The output signal given by kspacefirstorder3dg seems to give the RF coming from each grid point composing each element of the transducer. Is that right? </p> <p>Is there a way to ask for only 64 signals in the output? Or do I have to code the summation for each element of my transducer myself? </p> <p>Therefore, is it a summation of the RF from each grid points of the element that is done in kspacefirstorder3d? Or is it a mean? </p> <p>Thanks for your answers,</p> <p>Hanna </p> http://www.k-wave.org/forum/topic/3d-simulations-output-with-gpu#post-6196 Wed, 08 Nov 2017 11:35:45 +0000 HannaB 6196@http://www.k-wave.org/forum/ <p>Hello, </p> <p>I have a 3d simulation working fine with kspacefirstorder3D, but taking few hours to complete. I am trying to improve the code by running it on my GPU.<br /> I only change on my code the function - replaced by kspacefirstorder3DG.<br /> I don't understand how to control what happens inside this function which seems to do something different than before.</p> <p>- 'kspacefirstorder3D' code gives me sensor data of 64 (elements) by 4468 (time) </p> <p>- 'kspacefirstorder3DG' code gives me sensor data of 3200 by 4468. By plotting the RF I understood where the 3200 comes from:<br /> 3200 = 64 (elements) * 5 (size of element in kgrid) * 10 (repetitions of the simulation)</p> <p>Here are my points :<br /> 1) Why is the simulation repeated 10 times? How can I ask for only one?<br /> 2) Why do I have 5 signals per element and not only one? Can I change this in the inputs? (I guess I can fix this by summing the 5 signals for each element, but how come it is different from kspacefirstorder3d?..)</p> <p>Thank you very much for your answers and advice,<br /> All the best,</p> <p>Hanna</p> <p>PS: The transducer is defined with kWaveTransducer. </p>