nellens1 Support for the k-Wave MATLAB toolbox en-US Tue, 12 May 2026 22:59:52 +0000 http://bbpress.org/?v=1.0.2 q http://www.k-wave.org/forum/search.php http://www.k-wave.org/forum/topic/sensorrecord_interval#post-5785 Fri, 09 Dec 2016 17:07:02 +0000 nellens1 5785@http://www.k-wave.org/forum/ <p>Thanks!</p> <p>Best,<br /> Nick </p> http://www.k-wave.org/forum/topic/sensorrecord_interval#post-5783 Thu, 08 Dec 2016 16:59:22 +0000 Bradley Treeby 5783@http://www.k-wave.org/forum/ <p>Hi nellens1,</p> <p>It's not possible with the current version of k-Wave, but it would be a useful feature. I've added it to the list, although I can't promise when it will make it to release!</p> <p>If you're using the MATLAB code and looking for a quick hack, you could check <a href="http://www.k-wave.org/forum/topic/time-between-saving-steps#post-3819">this post</a>.</p> <p>Kind regards,</p> <p>Brad. </p> http://www.k-wave.org/forum/topic/sensorrecord_interval#post-5778 Tue, 06 Dec 2016 22:20:52 +0000 nellens1 5778@http://www.k-wave.org/forum/ <p>Is it possible to sample the p or u field at a fixed timestep interval instead of saving everything after sensor.record_start_index, or only the final step (p_final, u_final)? </p> http://www.k-wave.org/forum/topic/problems-with-kspacefirstorder3dc-for-heterogeneous-alpha_power#post-5773 Wed, 30 Nov 2016 17:26:50 +0000 nellens1 5773@http://www.k-wave.org/forum/ <p>Thanks very much! That explains the difference.</p> <p>Best,<br /> Nick </p> http://www.k-wave.org/forum/topic/problems-with-kspacefirstorder3dc-for-heterogeneous-alpha_power#post-5772 Wed, 30 Nov 2016 16:56:47 +0000 Bradley Treeby 5772@http://www.k-wave.org/forum/ <p>Hi Nick,</p> <p>The reason is that the optional input <code>medium.alpha_mode = &#39;no_dispersion&#39;</code> is not supported by the C++ code. If you remove this, the MATLAB simulation will also be unstable. This is because the absorption values are very high, so the sound speed dispersion is also significant. You can alleviate this by using a smaller time step (CFL number).</p> <p>Hope that helps,</p> <p>Brad. </p> http://www.k-wave.org/forum/topic/problems-with-kspacefirstorder3dc-for-heterogeneous-alpha_power#post-5771 Wed, 30 Nov 2016 15:49:02 +0000 nellens1 5771@http://www.k-wave.org/forum/ <p>Hi Brad,</p> <p>Thanks for the quick reply. I made a mistake in my previous post. My problem arises for a matrix medium.alpha_coeff. Admittedly, some of my medium.alpha_coeff get quite high, but the matlab code seems to handle it without difficulty while the C code produces some sort of numerical instability which spreads away from the voxels with high alpha.</p> <p>I uploaded an example to my dropbox:<br /> <a href="https://dl.dropboxusercontent.com/u/12851069/kwaveExample.zip" rel="nofollow">https://dl.dropboxusercontent.com/u/12851069/kwaveExample.zip</a> has code and an example of my array inputs (6.5 MB)<br /> <a href="https://dl.dropboxusercontent.com/u/12851069/exampleoutput.mat" rel="nofollow">https://dl.dropboxusercontent.com/u/12851069/exampleoutput.mat</a> has my output from the script in the previous (126 MB)</p> <p>Please let me know if you see the same problem!</p> <p>Thanks,<br /> Nick </p> http://www.k-wave.org/forum/topic/problems-with-kspacefirstorder3dc-for-heterogeneous-alpha_power#post-5770 Wed, 30 Nov 2016 11:28:42 +0000 Bradley Treeby 5770@http://www.k-wave.org/forum/ <p>Hi Nick,</p> <p>The input for <code>medium.alpha_coeff</code> can be a matrix, but the input for <code>medium.alpha_power</code> must be a single value (for both the matlab and C++ codes). </p> <p>Brad. </p> http://www.k-wave.org/forum/topic/problems-with-kspacefirstorder3dc-for-heterogeneous-alpha_power#post-5769 Tue, 29 Nov 2016 23:24:22 +0000 nellens1 5769@http://www.k-wave.org/forum/ <p>Hi-</p> <p>I would like to do a fairly large 3D simulation with a heterogeneous medium with 3D arrays representing c, rho, and alpha_power. This works fine with the kspaceFirstOrder3D function, but gives me garbage output for kspaceFirstOrder3DC. If I change medium.alpha_power to, say, 0.75 (per the example), it works just fine. medium.sound_speed and medium.density are heterogeneous for both. Is there something obvious that I'm doing wrong? I can share an example, if that's helpful.</p> <p>Thanks,<br /> Nick </p>