http://www.k-wave.org/forum/topic/defining-overlaping-detectors-to-reduce-computation-time Support for the k-Wave MATLAB toolbox en-US Tue, 12 May 2026 23:35:30 +0000 http://bbpress.org/?v=1.0.2 q http://www.k-wave.org/forum/search.php http://www.k-wave.org/forum/topic/defining-overlaping-detectors-to-reduce-computation-time#post-1126 Thu, 20 Dec 2012 05:33:28 +0000 Bradley Treeby 1126@http://www.k-wave.org/forum/ <p>Hi Pavel,</p> <p>If you are storing the complete domain, the output sensor data will be stored in column major order, indexed as x, then y, then z. You could reorder the output data using <code>reshape</code>, for example:</p> <p><code>sensordata4D = reshape(sensordata2D, [Nx, Ny, Nz, Nt]);</code></p> <p>I hope that helps,</p> <p>Brad. </p> http://www.k-wave.org/forum/topic/defining-overlaping-detectors-to-reduce-computation-time#post-1118 Mon, 17 Dec 2012 16:21:26 +0000 Pavel 1118@http://www.k-wave.org/forum/ <p>Hi Brad,</p> <p>Thank you very much, it really makes sence for the line sensor in your example. However, we would like to define more complicated sensors in 3D. In order to compute all possible sensor points it seems reasonable to define sensor mask as "sensor.mask(:,:,:)=ones(1:Nx, 1:Ny, 1:Nz)", so that we can have 4D array "sensordata4D(1:Nx, 1:Ny, 1:Nz, 1:Nt)" that would contain A-scans in all possible sensor points. Then we can combine them as we need.</p> <p>Unfortunately, K-Wave output saves everything in 2D array which combines A-scans from all the sensors as sensordata2D(1:Nx*Ny*Nz,1:Nt).</p> <p>Could you please advise if there is sure way to extract the data from 2D array "sensordata2D(1:Nx*Ny*Nz,1:Nt)" into 4D array "sensordata4D(1:Nx, 1:Ny, 1:Nz, 1:Nt)". Is there any mixing up between different elements and their numbers in sensordata2D?</p> <p>Would it correctly work as the following:<br /> for i=1:Nx; for j=1:Ny; for k=1:Nz;<br /> sensordata4D(i, j, k, 1:Nt)=sensordata2D(i*j*k,1:Nt);<br /> end; end; end;</p> <p>We can use "ijk cycle" and combine sensordata4D from point-like (xi,yj,zk) detectors, but it ruins initial idea to shorten the computational time. Using just "ij cycle" to combine sensordata4D from line detectors still requires too much time. This is all we tried yet.</p> <p>Thank you and Regards,<br /> Pavel Subochev </p> http://www.k-wave.org/forum/topic/defining-overlaping-detectors-to-reduce-computation-time#post-1112 Wed, 12 Dec 2012 00:28:39 +0000 Bradley Treeby 1112@http://www.k-wave.org/forum/ <p>Hi Pavel,</p> <p>The sensor mask that you define in k-Wave is just a collection of grid points where the data is recorded during the simulation. One possibility would be to define a sensor mask that includes all the possible detector positions, then process the data afterwards into individual A-scans using overlapping points. For example, if your sensor mask is a line, you could use something like <code>data = sensor_data(start_index:start_index + width, :)</code> and then increment start_index as you wish.</p> <p>Brad. </p> http://www.k-wave.org/forum/topic/defining-overlaping-detectors-to-reduce-computation-time#post-1109 Tue, 11 Dec 2012 10:05:19 +0000 Pavel 1109@http://www.k-wave.org/forum/ <p>Dear Dr. Treeby and Dr. Cox,</p> <p>Could you please advise if K-Wave allows to define detectors that overlap with each other in space? For example, after laser shot #1 you measure A-scan by finite-size detector with aperture D. After laser shot #2 you slightly move your detector at distance DX over the tissue,but DX does not exceed the size D of detector (DX&lt;&lt;D). In real world you can not use two detectors and one laser shot to obtain two A-scans simultaneously, since such detectors will physically overlap.</p> <p>Does your K-Wave allow to use "single laser shot" for big number of overlaping detectors? If it could allow that, that would drastically reduce computation time in problem that we try to solve now using K-Wave.</p> <p>Thank you and Regards,<br /> Pavel Subochev,PhD </p>