http://www.k-wave.org/forum/topic/incorrect-units-in-grid-size-logging-when-running-kspacefirstorder-cuda Support for the k-Wave MATLAB toolbox en-US Tue, 12 May 2026 23:08:33 +0000 http://bbpress.org/?v=1.0.2 q http://www.k-wave.org/forum/search.php http://www.k-wave.org/forum/topic/incorrect-units-in-grid-size-logging-when-running-kspacefirstorder-cuda#post-8957 Fri, 24 Nov 2023 17:36:59 +0000 Bradley Treeby 8957@http://www.k-wave.org/forum/ <p>Any chance you can reproduce this with a minimum working example? The output is printed by <code>kspaceFirstOrder_displaySimulationParameters</code> which should automatically display the correct units. </p> http://www.k-wave.org/forum/topic/incorrect-units-in-grid-size-logging-when-running-kspacefirstorder-cuda#post-8932 Mon, 23 Oct 2023 12:02:19 +0000 BIlly 8932@http://www.k-wave.org/forum/ <p>Hi there, </p> <p>This is just to do with the console output, rather than the output data of kspaceFirstOrder-CUDA itself so isn't an urgent issue. I've noticed the console output gives the domain size in m when the measures given are in mm, for example:</p> <p>Running k-Wave simulation...<br /> start time: 19-Oct-2023-22-43-10<br /> reference sound speed: 1500.0 m/s<br /> reference sound speed: 1500.0 m/s<br /> dt: 25ns, t_end: 25ns, time steps: 2<br /> input grid size: 364 by 108 by 364 grid points (82.0 by 24.3297 by 82.0 m)<br /> maximum supported frequency: 3.329268MHz<br /> smoothing p0 distribution...<br /> expanding computational grid...<br /> computational grid size: 384 by 128 by 384 grid points<br /> precomputation completed in 2.619699553s<br /> saving input files to disk...<br /> completed in 5.87853329s</p> <p>line 5 should state either, "(82.0 by 24.3297 by 82.0 mm)" or "(0.082 by 0.0243297 by 0.082 m)" for this simulation.</p> <p>Regards,<br /> Billy. </p>