http://www.k-wave.org/forum/topic/non-staggered-velocities Support for the k-Wave MATLAB toolbox en-US Tue, 12 May 2026 23:29:53 +0000 http://bbpress.org/?v=1.0.2 q http://www.k-wave.org/forum/search.php http://www.k-wave.org/forum/topic/non-staggered-velocities#post-7039 Mon, 09 Sep 2019 18:43:43 +0000 vich 7039@http://www.k-wave.org/forum/ <p>Thank you so much Professor! </p> http://www.k-wave.org/forum/topic/non-staggered-velocities#post-7038 Mon, 09 Sep 2019 15:47:08 +0000 Jiri Jaros 7038@http://www.k-wave.org/forum/ <p>Hi vich,<br /> You are right.<br /> It is not possible to perform the temporal unstaggering due to memory capacity, we have to flush the data to disk after every time step sampled. </p> <p>Best<br /> Jiri </p> http://www.k-wave.org/forum/topic/non-staggered-velocities#post-7036 Sun, 08 Sep 2019 07:32:36 +0000 vich 7036@http://www.k-wave.org/forum/ <p>Hi,</p> <p>When running kspaceFirstOrder3DC() (or 3DG) with a sensor.record that includes 'I' or 'I_avg', the computation of acoustic intensities seems to be performed in private/kspaceFirstOrder_saveIntensity.m by commands of the form:</p> <p><code><br /> ux_sgt = fourierShift(sensor_data(sensor_mask_index).ux_non_staggered, 1/2);<br /> sensor_data(sensor_mask_index).Ix = sensor_data(sensor_mask_index).p .* ux_sgt;<br /> </code></p> <p>Does this mean that the <code>--u_non_staggered_raw</code> option passed to kspaceFirstOrder3D-OMP (or -CUDA) only affects spatial but not temporal staggering (which then needs to be fixed with fourierShift())?</p> <p>Thank you very much! </p>