deblina Support for the k-Wave MATLAB toolbox en-US Tue, 12 May 2026 23:10:15 +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-spherical-sensors-and-memory-consuming-issues#post-4539 Thu, 22 May 2014 15:53:49 +0000 Bradley Treeby 4539@http://www.k-wave.org/forum/ <p>Hi Sebastian,</p> <p>The <code>makeSphericalSection</code> function simply calls <code>makeSphere</code>, and then truncates the output. The radius is the radius of curvature, i.e., the radius used to create the corresponding sphere. The height is the total "thickness" of the transducer along the beam axis. I will take a look at the documentation and perhaps add a figure illustrating the different inputs. In any case, thanks for posting your alternate code!</p> <p>Regarding out of memory issues, we are aware this is a problem. As part of the upcoming release, we have added several new functions and examples to save HDF5 files for the C++ code in parts, so that only a small number of matrices are stored in memory at the same time. This seems to solve most of the issues.</p> <p>Brad. </p> http://www.k-wave.org/forum/topic/defining-spherical-sensors-and-memory-consuming-issues#post-4526 Wed, 21 May 2014 16:55:47 +0000 bastlwastl 4526@http://www.k-wave.org/forum/ <p>Well, after all, it turned out the problem is not that hard. I'm posting my code for the inspiration of the reader. Here a function for creating the Cartesian coordinates of a spherical formed sensor (like in my case, an Olympus V311). Use cart2grid to convert this to an binary mask in your KWave simulation. You can shift the focal point of your sensor. Keep in mind, that the kgrid to which these coordinates are applied is centered around 0 in all directions, i.e. for 10(!) grid points from -5 to 4</p> <p><code><br /> %%Script creating spherical sensors via cartessian coordinates<br /> function[final_cart_sphere] = createCartSphericalSection(focal_length, focal_shift, sensor_diameter, sample_points)<br /> %focal_length is the radius of the original sphere in meter.<br /> %focal_shift might be a needed final shift of the focal point in meter in all directions in this form: [x_shift, y_shift, z_shift]</p> <p>%sensor_diameter defines the maximal opening angle of the spherical section<br /> sensor_half = sensor_diameter/2;<br /> %sample_points defines, how many point in the orignial sphere are sampled, in my case 20000 is a good starting value;</p> <p>%create sphere in cartesian coordinates around zero<br /> cart_sphere = makeCartSphere(focal_length,sample_points, [0,0,0]);</p> <p>%convert to spherical coordinates for better modeling<br /> [phi, theta, r] = cart2sph(cart_sphere(1,:),cart_sphere(2,:), cart_sphere(3,:));</p> <p>%get opening angle of sensor<br /> alpha = asin(sensor_diameter/(2*focal_length));</p> <p>%select possible phi values<br /> possible_phi = find(abs(phi)&lt;=alpha);<br /> %select possible values for theta<br /> possible_theta = find(abs(theta)&lt;=alpha);<br /> %intersect<br /> possible_values = intersect(possible_phi, possible_theta);<br /> final_sphere = [];<br /> for counter=possible_values<br /> theta_max = sqrt(sensor_half^2-(phi(counter)*focal_length)^2)/focal_length;<br /> if abs(theta(counter))&lt;=theta_max<br /> final_sphere = [final_sphere; [phi(counter),theta(counter),r(counter)]];<br /> end<br /> end</p> <p>[final_x, final_y, final_z] = sph2cart(final_sphere(:,1),final_sphere(:,2), final_sphere(:,3));</p> <p>%shift x coordinate by focus point on axial direction<br /> %now it should focus to the bragg peak</p> <p>final_x = final_x+focal_shift(1);<br /> final_y = final_y+focal_shift(2);<br /> final_z = final_z+focal_shift(3);</p> <p>%convert to structure for K-Wave function</p> <p>final_cart_sphere = [final_x,final_y,final_z].';<br /> end<br /> </code><code></code> </p> http://www.k-wave.org/forum/topic/defining-spherical-sensors-and-memory-consuming-issues#post-4525 Wed, 21 May 2014 11:09:32 +0000 bastlwastl 4525@http://www.k-wave.org/forum/ <p>Hi Anthony,<br /> i found this topic before and actually it's not that helpful for my specific problem. I considered modeling the sensor with Cartesian coordinates and converting it, since on top, my grid spacing is not uniform, i.e. dx!=dy. This is also not covered in the function makeSphericalSection.</p> <p>I wanted to point out, that the help text on this specific function is misleading, which is sad because it seems to be a fast-to-use function. Therefore is was looking for enlightenment but it seems that i have to write the function for the "Cartesian" approach.</p> <p>Anyway, thanks for your answer.<br /> Cheers,<br /> Sebastian </p> http://www.k-wave.org/forum/topic/defining-spherical-sensors-and-memory-consuming-issues#post-4522 Fri, 16 May 2014 08:43:58 +0000 Anthony 4522@http://www.k-wave.org/forum/ <p>Hi Sebastian</p> <p>About your first point, you may find this topic helpful :<br /> <a href="http://www.k-wave.org/forum/topic/sensor-mask-of-3d-time-reversal-reconstruction-for-a-spherical-sensor#post-4393" rel="nofollow">http://www.k-wave.org/forum/topic/sensor-mask-of-3d-time-reversal-reconstruction-for-a-spherical-sensor#post-4393</a> </p> <p>Best regards,<br /> Anthony </p> http://www.k-wave.org/forum/topic/defining-spherical-sensors-and-memory-consuming-issues#post-4519 Tue, 13 May 2014 14:44:17 +0000 bastlwastl 4519@http://www.k-wave.org/forum/ <p>Hi,</p> <p>i'm working on a simulation of our latest experiments and facing two major problems:</p> <p>1. I try the simulate the spherical sensor we used to match and compare the experimental results. For that, i use makeSphericalSection and provide the calculated number of grid point. Unfortunately, the resulting spherical section is tending to be larger then the provided grid points and thereby, i find it impossible to get the correct size for the sensor I'll like to simulate. Additionally, the help text is confusing. It says, that i have to provide the radius of curvature and the height in grid point, but from the resulting Plots, its seem these values are the radius of the corresponding disc of the sensor and the depth. Can you clarify this for me?</p> <p>2. At the moment, i simulate a 2000*430*430 grid, and although the memory consumption in the simulation itself is 'only' about 15gb, I'm facing Matlabs Out-Of-Memory Error during the pre-simulations (grid expansion, smoothing etc.) Since I'm already working on the best cluster the university can offer for this purpose with 64GB per working node, I'm looking for possibilities to minimize the memory consumption during this pre-simulation phase. Is there a way?</p> <p>Thanks for your time and help,</p> <p>Sebastian </p>