<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>k-Wave User Forum &#187; Forum: GPU Binaries - Recent Posts</title>
		<link>http://www.k-wave.org/forum/forum/gpu-binaries</link>
		<description>Support for the k-Wave MATLAB toolbox</description>
		<language>en-US</language>
		<pubDate>Fri, 06 Mar 2026 02:03:14 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.2</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://www.k-wave.org/forum/search.php</link>
		</textInput>
		<atom:link href="http://www.k-wave.org/forum/rss/forum/gpu-binaries" rel="self" type="application/rss+xml" />

		<item>
			<title>GioF on "Axysimmetric simulations with kspaceFirstOrder-CUDA"</title>
			<link>http://www.k-wave.org/forum/topic/axysimmetric-simulations-with-kspacefirstorder-cuda#post-9246</link>
			<pubDate>Mon, 09 Feb 2026 12:31:57 +0000</pubDate>
			<dc:creator>GioF</dc:creator>
			<guid isPermaLink="false">9246@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;I'm trying to move my simulations from MATLAB to C++ exploiting the kspaceFirstOrder executable. I managed to obtain comparable results with my axysimmetric simulation in MATLAB and the one from kspaceFirstOrder-OMP. I would like now to exploit the CUDA executable to speed up the computations, but I noticed that the axysimmetric simulation is not available for this executable. As moving to 3D will increase the computational burden, I was wondering if you are planning to maka the axysimmetric simulation available soon.&#60;br /&#62;
Thank you for your feedback!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>nmin on "Issue with Accessing k-Wave GPU Code on Ubuntu 24"</title>
			<link>http://www.k-wave.org/forum/topic/issue-with-accessing-k-wave-gpu-code-on-ubuntu-24#post-9229</link>
			<pubDate>Mon, 01 Sep 2025 08:41:34 +0000</pubDate>
			<dc:creator>nmin</dc:creator>
			<guid isPermaLink="false">9229@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi ujjal, I am experiencing the same issue. Could you kindly share how you resolved it? Thanks a lot!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>gpr on "Issue with Accessing k-Wave GPU Code on Ubuntu 24"</title>
			<link>http://www.k-wave.org/forum/topic/issue-with-accessing-k-wave-gpu-code-on-ubuntu-24#post-9207</link>
			<pubDate>Thu, 10 Apr 2025 11:54:55 +0000</pubDate>
			<dc:creator>gpr</dc:creator>
			<guid isPermaLink="false">9207@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi Uijal,&#60;br /&#62;
This makes a couple of times I hear about this issue. How did you resolve it?&#60;br /&#62;
Bests
&#60;/p&#62;</description>
		</item>
		<item>
			<title>ujjal on "Issue with Accessing k-Wave GPU Code on Ubuntu 24"</title>
			<link>http://www.k-wave.org/forum/topic/issue-with-accessing-k-wave-gpu-code-on-ubuntu-24#post-9205</link>
			<pubDate>Thu, 10 Apr 2025 03:32:11 +0000</pubDate>
			<dc:creator>ujjal</dc:creator>
			<guid isPermaLink="false">9205@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi, @everyone!&#60;br /&#62;
Resolved, Thanks
&#60;/p&#62;</description>
		</item>
		<item>
			<title>ujjal on "Issue with Accessing k-Wave GPU Code on Ubuntu 24"</title>
			<link>http://www.k-wave.org/forum/topic/issue-with-accessing-k-wave-gpu-code-on-ubuntu-24#post-9204</link>
			<pubDate>Sat, 05 Apr 2025 05:40:53 +0000</pubDate>
			<dc:creator>ujjal</dc:creator>
			<guid isPermaLink="false">9204@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi everyone,&#60;/p&#62;
&#60;p&#62;We are trying to access MATLAB (k-Wave) GPU code on Ubuntu 24. Our system configuration is as follows: CUDA Device: NVIDIA RTX A4000&#60;/p&#62;
&#60;p&#62;CUDA Toolkit Version: 12.2.0&#60;/p&#62;
&#60;p&#62;NVIDIA-SMI: 535.230.02&#60;/p&#62;
&#60;p&#62;Driver Version: 535.230.02&#60;/p&#62;
&#60;p&#62;CUDA Version: 12.2&#60;/p&#62;
&#60;p&#62;MATLAB Version: R2024b&#60;/p&#62;
&#60;p&#62;k-Wave Toolbox Version: 1.4&#60;/p&#62;
&#60;p&#62;k-Wave Toolbox Version (CUDA): 1.3 (CPP Linux Binaries)&#60;/p&#62;
&#60;p&#62;When we run the following command in MATLAB: sensor_data = kspaceFirstOrder2DG(kgrid, medium, source, sensor, input_args{:}, 'RecordMovie', false, 'DataCast', 'single');&#60;/p&#62;
&#60;p&#62;We encounter the following error message:&#60;br /&#62;
┌───────────────────────────────────────────────────────────────┐&#60;br /&#62;
│                  kspaceFirstOrder-CUDA v1.3                   │&#60;br /&#62;
├───────────────────────────────────────────────────────────────┤&#60;br /&#62;
│ Reading simulation configuration:                        Done │&#60;br /&#62;
│ Selected GPU device id:                                Failed │&#60;br /&#62;
└───────────────────────────────────────────────────────────────┘&#60;br /&#62;
┌───────────────────────────────────────────────────────────────┐&#60;br /&#62;
│            !!! K-Wave experienced a fatal error !!!           │&#60;br /&#62;
├───────────────────────────────────────────────────────────────┤&#60;br /&#62;
│ Error: All CUDA-capable devices are busy or unavailable.      │&#60;br /&#62;
├───────────────────────────────────────────────────────────────┤&#60;br /&#62;
│                      Execution terminated                     │&#60;br /&#62;
└───────────────────────────────────────────────────────────────┘&#60;br /&#62;
Error using h5readc&#60;br /&#62;
Unable to open '/tmp/kwave_output_data05-Apr-2025-16-29-44.h5'. File or folder not found.&#60;/p&#62;
&#60;p&#62;Error in h5read (line 95)&#60;br /&#62;
    [data,var_class] = h5readc(Filename,Dataset,start,count,stride);&#60;br /&#62;
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^&#60;br /&#62;
Error in kspaceFirstOrder3DC (line 569)&#60;br /&#62;
Nx = h5read(output_filename, '/Nx');&#60;br /&#62;
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^&#60;br /&#62;
Error in kspaceFirstOrder2DG (line 76)&#60;br /&#62;
sensor_data = kspaceFirstOrder3DC(varargin{:});&#60;br /&#62;
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^&#60;br /&#62;
Error in untitled (line 51)&#60;br /&#62;
sensor_data = kspaceFirstOrder2DG(kgrid, medium, source, sensor, input_args{:}, 'RecordMovie', false, 'DataCast', 'single');&#60;br /&#62;
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^&#60;br /&#62;
 Is it not possible to run the k-Wave binaries (related to the Linux version) with CUDA support? If so, how can we resolve this issue?&#60;/p&#62;
&#60;p&#62;Thank you for your help!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Jiri Jaros on "Discrepancy between kspaceFirstOrder3DG and kspaceFirstOrder3D"</title>
			<link>http://www.k-wave.org/forum/topic/discrepancy-between-kspacefirstorder3dg-and-kspacefirstorder3d#post-9173</link>
			<pubDate>Wed, 15 Jan 2025 12:07:12 +0000</pubDate>
			<dc:creator>Jiri Jaros</dc:creator>
			<guid isPermaLink="false">9173@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi Rehman,&#60;br /&#62;
Would it be possible to share your simulation setup (input file) with me to investigate the problem?&#60;/p&#62;
&#60;p&#62;Jiri
&#60;/p&#62;</description>
		</item>
		<item>
			<title>gcr on "CUDA simulation on Ada architecture - All CUDA-capable devices are busy"</title>
			<link>http://www.k-wave.org/forum/topic/cuda-simulation-on-ada-architecture-all-cuda-capable-devices-are-busy#post-9169</link>
			<pubDate>Wed, 08 Jan 2025 15:04:32 +0000</pubDate>
			<dc:creator>gcr</dc:creator>
			<guid isPermaLink="false">9169@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;I hope this message finds you well. I am currently attempting to run simulations in CUDA on my RTX 4090, but I keep encountering the error: “All CUDA-capable devices are busy or unavailable.” Would it be possible for you to provide the re-compiled binaries to help resolve this issue?&#60;/p&#62;
&#60;p&#62;Thank you very much for your time and assistance.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>rali2 on "Discrepancy between kspaceFirstOrder3DG and kspaceFirstOrder3D"</title>
			<link>http://www.k-wave.org/forum/topic/discrepancy-between-kspacefirstorder3dg-and-kspacefirstorder3d#post-9147</link>
			<pubDate>Thu, 03 Oct 2024 19:43:11 +0000</pubDate>
			<dc:creator>rali2</dc:creator>
			<guid isPermaLink="false">9147@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hello All,&#60;/p&#62;
&#60;p&#62;Long time k-Wave user here. In the past, I've mostly used the 2D simulator, but I recently started using the 3D codes to simulate data for 3D ultrasound tomography.&#60;/p&#62;
&#60;p&#62;I noticed that when I ran the same simulation in kspaceFirstOrder3D vs kspaceFirstOrder3DG, I would get different results. The difference between the results is not simply roundoff error. There are significant delays between the signals simulated by kspaceFirstOrder3D vs kspaceFirstOrder3DG. I suspect the discrepancy might have to do with dispersion. Are there any known (or unknown?) dispersion-related issues with kspaceFirstOrder3DG? &#60;/p&#62;
&#60;p&#62;Please let me know if you would like me to share some sample code with the example that produces the discrepancy.&#60;/p&#62;
&#60;p&#62;Thank you,&#60;br /&#62;
Rehman Ali
&#60;/p&#62;</description>
		</item>
		<item>
			<title>chatillon on "Error kWave cuda  3DG p_source_input has wrong dimension size. iostream error"</title>
			<link>http://www.k-wave.org/forum/topic/error-kwave-cuda-3dg-p_source_input-has-wrong-dimension-size-iostream-error#post-9104</link>
			<pubDate>Fri, 21 Jun 2024 15:01:26 +0000</pubDate>
			<dc:creator>chatillon</dc:creator>
			<guid isPermaLink="false">9104@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hello everyone,&#60;br /&#62;
I encounter a problem that seems similar: I define a non-symmetrical 3D source and I do the same calculation in CPU (kspaceFirstOrder3D) and GPU (kspaceFirstOrder3DC) mode. The first gives satisfactory results while for the second I have the impression that there is an inversion of the X and Y axes of the source grid and/or of the sensor grid. Could you confirm the problem for me?&#60;br /&#62;
thanks in advance
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Drainville1 on "Error kWave cuda  3DG p_source_input has wrong dimension size. iostream error"</title>
			<link>http://www.k-wave.org/forum/topic/error-kwave-cuda-3dg-p_source_input-has-wrong-dimension-size-iostream-error#post-9103</link>
			<pubDate>Fri, 14 Jun 2024 18:33:56 +0000</pubDate>
			<dc:creator>Drainville1</dc:creator>
			<guid isPermaLink="false">9103@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Any update on the labelled source mask? Is there any way to reduce the size/dimension of source.p when using a large number of source points, that could otherwise be represented by a single signal for each unique element?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>zak morgan on "C++ FFT plans creation really slow"</title>
			<link>http://www.k-wave.org/forum/topic/c-fft-plans-creation-really-slow#post-9092</link>
			<pubDate>Thu, 09 May 2024 15:08:22 +0000</pubDate>
			<dc:creator>zak morgan</dc:creator>
			<guid isPermaLink="false">9092@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Never mind, I was ecperimeting with PML and had it set to be outside the grid, thus growing the grid to a non-power of 2 size thus explaining the slow-down!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>zak morgan on "C++ FFT plans creation really slow"</title>
			<link>http://www.k-wave.org/forum/topic/c-fft-plans-creation-really-slow#post-9091</link>
			<pubDate>Wed, 08 May 2024 23:09:21 +0000</pubDate>
			<dc:creator>zak morgan</dc:creator>
			<guid isPermaLink="false">9091@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;I'm also seeing similar, when running on the CPU c++ code pre-pocessing is instant and then my simulation takes about 47 seconds, however when running the CUDA code, the simulation takes about 10 seconds, but 80 seconds is spent on pre-processing the FFT. It seems odd that preprocessing should be this much slower on the GPU than on the CPU?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>pamparana on "kspaceFirstOrder-CUDA v1.3 claims it needs CUDA 12.0"</title>
			<link>http://www.k-wave.org/forum/topic/kspacefirstorder-cuda-v13-claims-it-needs-cuda-120#post-9039</link>
			<pubDate>Sat, 17 Feb 2024 19:27:55 +0000</pubDate>
			<dc:creator>pamparana</dc:creator>
			<guid isPermaLink="false">9039@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Did you find a solution to this?&#60;/p&#62;
&#60;p&#62;For me, the situation is reversed. it runs fine on my local linux machine with cuda 11.7 but the docker container using the cuda 11.6 image does not work and gives an error where it says cuda 0.0 is installed.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>daga_pankaj on "memory requirements for GPU version"</title>
			<link>http://www.k-wave.org/forum/topic/memory-requirements-for-gpu-version#post-9028</link>
			<pubDate>Tue, 30 Jan 2024 17:59:48 +0000</pubDate>
			<dc:creator>daga_pankaj</dc:creator>
			<guid isPermaLink="false">9028@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Never mind. Should read the documentation more.&#60;br /&#62;
For anyone else, interested, it is at the end of the user manual.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>daga_pankaj on "memory requirements for GPU version"</title>
			<link>http://www.k-wave.org/forum/topic/memory-requirements-for-gpu-version#post-9026</link>
			<pubDate>Tue, 30 Jan 2024 13:55:19 +0000</pubDate>
			<dc:creator>daga_pankaj</dc:creator>
			<guid isPermaLink="false">9026@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;I am going to run simulations on a 256 x 256 x 128 grid. Could someone suggest what memory requirements I could expect for the GPU version?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>BIlly on "kspaceFirstOrder-CUDA v1.3 claims it needs CUDA 12.0"</title>
			<link>http://www.k-wave.org/forum/topic/kspacefirstorder-cuda-v13-claims-it-needs-cuda-120#post-8947</link>
			<pubDate>Mon, 20 Nov 2023 10:46:00 +0000</pubDate>
			<dc:creator>BIlly</dc:creator>
			<guid isPermaLink="false">8947@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;The CUDA binary kspaceFirstOrder-CUDA v1.3 claims to require CUDA 12.0&#60;/p&#62;
&#60;p&#62;&#60;code&#62;&#60;/code&#62;`&#60;br /&#62;
┌───────────────────────────────────────────────────────────────┐&#60;br /&#62;
│            !!! K-Wave experienced a fatal error !!!           │&#60;br /&#62;
├───────────────────────────────────────────────────────────────┤&#60;br /&#62;
│ Error: Insufficient CUDA driver version. The code needs CUDA  │&#60;br /&#62;
│        version 12.0 but 11.7 is installed.                    │&#60;br /&#62;
├───────────────────────────────────────────────────────────────┤&#60;br /&#62;
│                      Execution terminated                     │&#60;br /&#62;
└───────────────────────────────────────────────────────────────┘&#60;br /&#62;
&#60;code&#62;&#60;/code&#62;`&#60;br /&#62;
Although I see nothing to suggest that CUDA 12.0 or above is needed in the documentation or on this site and my department's HPC only runs up to CUDA 11.7.&#60;br /&#62;
Stranger still the binary runs completely fine in a CUDA 11.7 Docker container on my workstation.&#60;br /&#62;
Is this a bug with k-wave and the HPC?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Pavel on "Large-scale-simulation On 8 A100 GPUS"</title>
			<link>http://www.k-wave.org/forum/topic/large-scale-simulation-on-8-a100-gpus#post-8928</link>
			<pubDate>Fri, 06 Oct 2023 10:51:32 +0000</pubDate>
			<dc:creator>Pavel</dc:creator>
			<guid isPermaLink="false">8928@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;I am not a computer guy, but it looks like GPU apps use GPU memory plus half of CPU RAM memory, and it looks like default configuration of my system. For example, having threadripper architecture of motherboard I sum up half of my 256 GB RAM with 40 GB of my 4090 by rather fast (ddr5) and cost effective way (cheaper than buying four 3090 units in parallel). Maybe 3DG version of kWave allows for such CPUtoGPU memory sharing as well?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>so_dence on "Large-scale-simulation On 8 A100 GPUS"</title>
			<link>http://www.k-wave.org/forum/topic/large-scale-simulation-on-8-a100-gpus#post-8916</link>
			<pubDate>Sat, 23 Sep 2023 13:09:52 +0000</pubDate>
			<dc:creator>so_dence</dc:creator>
			<guid isPermaLink="false">8916@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;@Jiri Jaros&#60;br /&#62;
Hi Jiri Jaros&#60;/p&#62;
&#60;p&#62;    First of all,Thanks for your reply!And I am deeply interested in the multi-GPU version,could you please send me one beta version!I am deeply grateful with that!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>jamesjc on "Large-scale-simulation On 8 A100 GPUS"</title>
			<link>http://www.k-wave.org/forum/topic/large-scale-simulation-on-8-a100-gpus#post-8910</link>
			<pubDate>Thu, 14 Sep 2023 16:03:30 +0000</pubDate>
			<dc:creator>jamesjc</dc:creator>
			<guid isPermaLink="false">8910@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;@Jiri Jaros,&#60;/p&#62;
&#60;p&#62;Are you and your team still on track to release a multi-GPU version this month? Do you have an updated timeline?&#60;/p&#62;
&#60;p&#62;We're very keen to use it :)
&#60;/p&#62;</description>
		</item>
		<item>
			<title>f841r on "CUDA simulation on Ada architecture - All CUDA-capable devices are busy"</title>
			<link>http://www.k-wave.org/forum/topic/cuda-simulation-on-ada-architecture-all-cuda-capable-devices-are-busy#post-8888</link>
			<pubDate>Wed, 02 Aug 2023 15:06:38 +0000</pubDate>
			<dc:creator>f841r</dc:creator>
			<guid isPermaLink="false">8888@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;It was a problem with my cuda installation. I now installed the recommended drivers over apt and cuda 11.8 using the run file with the --toolkit option. Now everything works with the self-compiled binaries.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
