http://www.k-wave.org/forum/topic/need-help-with-cascaded-simulations-on-large-grid-treeby-2020 Support for the k-Wave MATLAB toolbox en-US Tue, 12 May 2026 23:30:44 +0000 http://bbpress.org/?v=1.0.2 q http://www.k-wave.org/forum/search.php http://www.k-wave.org/forum/topic/need-help-with-cascaded-simulations-on-large-grid-treeby-2020#post-8294 Fri, 13 Aug 2021 11:38:50 +0000 Elly Martin 8294@http://www.k-wave.org/forum/ <p>Hi Hammerben, </p> <p>In reply to your first post - the simulations for this paper were run using a multi-GPU version of k-Wave which splits the simulation domain across a number of GPUs, rather than as sequential simulations. The simulations run simultaneously and for all time steps with data exchanged between the subdomains. You can read more about how this works in J. Jaros, F. Vaverka, and B. E. Treeby, Supercomput. Frontiers Innov., vol. 3, no. 3, pp. 40–55, 2016. Unfortunately this version is not available yet but we aim to include it in a future release. </p> <p>Re the sensor data: setting the p_max_all flag records p_max over the whole domain. sensor_data.p is only recorded at the positions defined by the sensor mask. In the paper, this was a much smaller volume, for example, for the water simulations, the pressure time signals were recorded over a volume of 11x11x1701 grid points.</p> <p>In reply to you 2nd post: in the paper the source was defined using a back projected hydrophone measurement, resulting in non-uniform source waveform amplitudes across the source. It is likely that the shape of the measured waveform will also be different to the shape of the waveform generated by setting e.g a windowed sinusoidal burst. You can find more information on the differences which arise from uniform vs measured sources in E. Martin, Y. T. Ling, B. E. Treeby IEEE Trans. Ultrason. Ferroelectr. Freq. Control, 63 (10), pp. 1535–1542, 2016. </p> <p>If you wish to compare using the measured data (including the source characterization), it is available here:<br /> <a href="https://rdr.ucl.ac.uk/articles/dataset/Experimental_Validation_of_k-Wave_Nonlinear_Wave_Propagation_in_Layered_Absorbing_Fluid_Media/14216717" rel="nofollow">https://rdr.ucl.ac.uk/articles/dataset/Experimental_Validation_of_k-Wave_Nonlinear_Wave_Propagation_in_Layered_Absorbing_Fluid_Media/14216717</a></p> <p>Elly </p> http://www.k-wave.org/forum/topic/need-help-with-cascaded-simulations-on-large-grid-treeby-2020#post-8292 Thu, 12 Aug 2021 06:34:25 +0000 Hammerben1 8292@http://www.k-wave.org/forum/ <p>An update on this thread:</p> <p>I successfully ran the simulation at a lower spatial resolution.<br /> I used a uniform 4-cycle burst for all source element.<br /> The results don't seem to match with the paper even for the free-field case, which uses a hydrophone measured back-projected plane as source plane. </p> <p>Does it mean we shouldn't define the source waveform as a single waveform in all of our simulations?</p> <p>Thanks </p> http://www.k-wave.org/forum/topic/need-help-with-cascaded-simulations-on-large-grid-treeby-2020#post-8289 Wed, 11 Aug 2021 03:56:18 +0000 Hammerben1 8289@http://www.k-wave.org/forum/ <p>Hi k-wave team:<br /> I am trying to repeat what you did in Treeby 2020, Experimental validation of k-Wave: Nonlinear wave propagation in layered, absorbing fluid media.</p> <p>How did you define the sensor_mask to run it sequentially for 8 subdomains? </p> <p>When I tried to define it as [1,1,Nz-8, Nx,Ny,Nz] and ask to record sensor_data.p, to be used as the source for the next subdomain, the data size was about 220GB, which is much higher than the RAM available to me. </p> <p>Also it seems that I can't record p_max with a separate sensor_mask. How did you record the sensor_data.p_max along with sensor_data.p with that large window (40x40x70mm)? The data size for sensor_data.p with that window is easily &gt; 10TB</p> <p>These led me to think I am doing this wrong. </p> <p>Help greatly appreciated<br /> Thanks</p> <p>P.S. I have the NVIDIA V100 with 32GB and about 128GB RAM available. I have no issue running the first segment but it can't handle it when the data starts to transfer to disk </p>