wsimson Support for the k-Wave MATLAB toolbox en-US Tue, 12 May 2026 23:37:02 +0000 http://bbpress.org/?v=1.0.2 q http://www.k-wave.org/forum/search.php http://www.k-wave.org/forum/topic/python-implementation-of-k-wave#post-9111 Thu, 11 Jul 2024 17:42:33 +0000 wsimson 9111@http://www.k-wave.org/forum/ <p>Hi All,</p> <p>as a follow-up, k-wave-python now supports MacOS out of the box in the latest release.</p> <p>Hope you find this helpful!</p> <p>Best,<br /> Walter </p> http://www.k-wave.org/forum/topic/python-implementation-of-k-wave#post-8563 Sat, 09 Jul 2022 18:25:30 +0000 wsimson 8563@http://www.k-wave.org/forum/ <p>As a follow up, the project is still being actively developed. Here is the link to our GitHub repo!</p> <p><a href="https://github.com/waltsims/k-wave-python" rel="nofollow">https://github.com/waltsims/k-wave-python</a> </p> http://www.k-wave.org/forum/topic/python-implementation-of-k-wave#post-8525 Wed, 04 May 2022 20:26:34 +0000 wsimson 8525@http://www.k-wave.org/forum/ <p>Hi all,</p> <p>the k-Wave python package is now available on PYPI. Here is the link to the package. If you have any questions or issues, please open an issue on Github or ask in the dedicated telegram channel.</p> <p><a href="https://pypi.org/project/k-Wave-python/" rel="nofollow">https://pypi.org/project/k-Wave-python/</a></p> <p>Looking forward to your feedback,<br /> Walter </p> http://www.k-wave.org/forum/topic/python-implementation-of-k-wave#post-8247 Wed, 21 Jul 2021 14:08:37 +0000 Bradley Treeby 8247@http://www.k-wave.org/forum/ <p>Thanks for your efforts with this Walter - looking forward to having a play! </p> http://www.k-wave.org/forum/topic/migrate-forum-and-development-to-github#post-8246 Wed, 21 Jul 2021 14:07:47 +0000 Bradley Treeby 8246@http://www.k-wave.org/forum/ <p>Hi Walter,</p> <p>We periodically discuss this, but for various reasons have stuck with a private repository. I'll add it back onto the list of things to discuss. </p> <p>Brad. </p> http://www.k-wave.org/forum/topic/bug-k-wave-cuda-binaries-do-not-throw-errors-when-run-with-recordmovie-flag#post-8182 Tue, 08 Jun 2021 15:25:59 +0000 Bradley Treeby 8182@http://www.k-wave.org/forum/ <p>Agreed. We will try and resolve this for the next release. </p> http://www.k-wave.org/forum/topic/python-implementation-of-k-wave#post-8154 Tue, 18 May 2021 15:57:03 +0000 wsimson 8154@http://www.k-wave.org/forum/ <p>Also @Jiri, I believe GPU acceleration in native python could be achieved with something like [numba](http://numba.pydata.org/), but We have omitted this for now for the sake of simplicity. </p> http://www.k-wave.org/forum/topic/python-implementation-of-k-wave#post-8153 Tue, 18 May 2021 15:54:23 +0000 wsimson 8153@http://www.k-wave.org/forum/ <p>Hi all, </p> <p>I will be releasing a ported version of kWave in Python shortly on GitHub. I would be happy to receive feedback on the draft. This version goes beyond the prototype to generate files and takes an object oriented approach in python to generating the h5 files. We tried to remain true to the architecture, but modified it in some places to reduce complexity. To ensure compatibility, we test the python implementation on all of the examples listed on the website by comparing the generated h5 files in both cases.</p> <p>Currently, the elastic simulation, and temperature simulations have been omitted, from the python version.</p> <p>Looking forward to your feedback.<br /> Best,<br /> Walter </p> http://www.k-wave.org/forum/topic/migrate-forum-and-development-to-github#post-8152 Tue, 18 May 2021 15:49:03 +0000 wsimson 8152@http://www.k-wave.org/forum/ <p>Would it be possible to migrate the issue tracking and development to GitHub? Since the project is already open source, I think it would increase the accessibility of the project, make it easier to report and track bugs, and make it much easier to contribute to the project.</p> <p>Best,<br /> Walter </p> http://www.k-wave.org/forum/topic/bug-k-wave-cuda-binaries-do-not-throw-errors-when-run-with-recordmovie-flag#post-8151 Tue, 18 May 2021 15:46:57 +0000 wsimson 8151@http://www.k-wave.org/forum/ <p>I haven't tested all the flags, but there is no information passed to the user when flags that are supported in the <code>kspaceFirstOrder3DG</code> that are documented to work for <code>kspaceFirstOrder3D</code>.</p> <p>Some examples that do not throw errors are:</p> <p> - "RecordMovie"<br /> - "PlotLayout"</p> <p>Warning the user at a minimum would be useful for this. </p> http://www.k-wave.org/forum/topic/python-implementation-of-k-wave#post-7717 Fri, 31 Jul 2020 16:34:58 +0000 SamPichardo 7717@http://www.k-wave.org/forum/ <p>As an alternative, embedding Matlab in Python is officially supported since some time. So your Python code can just prepare parameters and input data, and then call a Matlab function/script directly in Python and the recover the data. If saving in Matlab 7.0 file format, scipy can read it with out too much trouble. Even reading from the new 7.3 format is quite easy do using h5py as 7.3 is based on HDF5. </p> http://www.k-wave.org/forum/topic/simulating-a-plane-wave-with-a-linear-array-tranducer#post-7294 Mon, 16 Mar 2020 12:45:36 +0000 Bradley Treeby 7294@http://www.k-wave.org/forum/ <p>Hi bramth,</p> <p>Some of the wave energy will propagate through the PML. However, with appropriate settings this should be -80 dB less than the incoming wave (see the user manual if you want more details). This means your simulation is only accurate to a few decimal places, but that should be enough for most practical purposes. </p> <p>Brd. </p> http://www.k-wave.org/forum/topic/simulating-a-plane-wave-with-a-linear-array-tranducer#post-7290 Thu, 12 Mar 2020 14:46:25 +0000 bramth 7290@http://www.k-wave.org/forum/ <p>It seems setting the 'PlotScale' to either the max source intensity or to 'auto' solves the problem. Still, I wonder what happens in those low intensity regions. </p> http://www.k-wave.org/forum/topic/simulating-a-plane-wave-with-a-linear-array-tranducer#post-7289 Thu, 12 Mar 2020 14:03:16 +0000 bramth 7289@http://www.k-wave.org/forum/ <p>That is true, thanks. Is it by the way a plotting artefact that the B-mode scan example using linear array, when plotting the simulation, shows black intensities and something that seems PML penetration in the beginning? The "black" wave progression continues afterwards. See for the result after a few time steps <a href="https://imgur.com/a/4ME4RBZ" rel="nofollow">https://imgur.com/a/4ME4RBZ</a> and <a href="https://imgur.com/a/gNVeMEs" rel="nofollow">https://imgur.com/a/gNVeMEs</a>. </p> http://www.k-wave.org/forum/topic/simulating-a-plane-wave-with-a-linear-array-tranducer#post-7288 Wed, 11 Mar 2020 18:53:48 +0000 Bradley Treeby 7288@http://www.k-wave.org/forum/ <p>The particle velocity is typically several orders of magnitude smaller than the pressure. In 1D, they are related by the acoustic impedance (sound speed times density), so to get the same relative amplitude you will need to divide by the amplitude of the velocity source by the impedance. </p> http://www.k-wave.org/forum/topic/simulating-a-plane-wave-with-a-linear-array-tranducer#post-7287 Wed, 11 Mar 2020 18:42:08 +0000 bramth 7287@http://www.k-wave.org/forum/ <p>Dear Bradley,<br /> When using such a dipole transducerin a velocity-source setting (by setting source.p_mask to source.u_mask and source.p to source.ux), why can we not scale the input the same way as with a pressure source? (E.g. the transducer.source_strength, when scaling the tone_burst input with this value (and the impedance).) If I do scale the input, I get 'black' wavefronts (when not using C++ or CUDA implementations). Kind regards, Bram </p> http://www.k-wave.org/forum/topic/simulating-a-plane-wave-with-a-linear-array-tranducer#post-7237 Thu, 20 Feb 2020 15:07:04 +0000 jbishop 7237@http://www.k-wave.org/forum/ <p>Simulation of heating in an air-backed transducer and its substrate was of interest to me, and I too wondered just how well k-Wave could do with it not having access to any FEM solver. Without yet knowing how well the result matches experimental data, I can say so far it is certainly plausible looking. It required a lower CFL number of &lt; 0.1 before the air gap would stabilize. As a result of the low CFL number and fine resolution needed, compute times in 2D matlab were getting too long. I saw the other post on the c++/gpu release for 2D: that will be of immediate use to me. </p> http://www.k-wave.org/forum/topic/python-implementation-of-k-wave#post-6621 Tue, 30 Oct 2018 16:21:55 +0000 Bradley Treeby 6621@http://www.k-wave.org/forum/ <p>Hi Umit,</p> <p>We now have a prototype version of code to save the input file from Python. See <a href="http://www.k-wave.org/forum/topic/creating-the-hdf5-file-in-c">this topic</a> for the download link.</p> <p>Brad. </p> http://www.k-wave.org/forum/topic/python-implementation-of-k-wave#post-6598 Tue, 09 Oct 2018 12:04:44 +0000 umitarabul 6598@http://www.k-wave.org/forum/ <p>Hi,</p> <p>I agree with G. I think a script to generate input.h5 and call C++ binary and read output.h5 back into Python would be sufficient. Should not be that difficult if once HDF5 structure is known. Can be a contribution of a user as well.</p> <p>Umit, </p> http://www.k-wave.org/forum/topic/simulating-a-plane-wave-with-a-linear-array-tranducer#post-6460 Sun, 13 May 2018 20:10:37 +0000 Bradley Treeby 6460@http://www.k-wave.org/forum/ <p>Hi laughingrice,</p> <p>You could try using a velocity source instead of a pressure source. This will produce a dipole field, which will make the wave-field more directional. If the source is aligned with the grid, there will also be no response detected at the adjacent elements.</p> <p>Alternatively, you could model the source conditions using another model (e.g., FEM) that accounts for the actual source construction, record the acoustic field just in front of the source, and then input this into k-Wave.</p> <p>Accurately modelling the layered structure of the piezo, backing, and air in k-Wave will be pretty difficult due to the small scale structures and the large impedance mismatches.</p> <p>Brad. </p>