http://www.k-wave.org/forum/topic/modifying-beamforming_delays Support for the k-Wave MATLAB toolbox en-US Wed, 13 May 2026 00:22:43 +0000 http://bbpress.org/?v=1.0.2 q http://www.k-wave.org/forum/search.php http://www.k-wave.org/forum/topic/modifying-beamforming_delays#post-1224 Wed, 06 Feb 2013 09:30:13 +0000 hhamtaii 1224@http://www.k-wave.org/forum/ <p>Hi there,<br /> thanks for your response. that's a very good idea to add a property that allows the center element to be selected. however I think as long as one concerns phased array imaging methods based on multiple sets of active elements, every single scan-line of the final enhanced image would be the sum of corresponding scan-lines of many poor images (each according to a proper sub set of elements). to do so, delays for every set of active elements must have been calculated according to the center of the complete array. otherwise, summing poor images up to form an enhanced image would be meaningless.</p> <p>imaging using linear or convex probes, on the other hand, may be achieved without that summing up process because there we can form the final image by attaching partial images together. so no need to keep a constant coordinate i.e. the center of complete elements.</p> <p>To the best of my knowledge, beside linear imaging, the only delay values, that are calculated according to the center of active elements (instead of complete elements), are those who concern "defocusing", which is not a matter of k-wave toolbox.</p> <p>hope to be useful<br /> hhamtaii </p> http://www.k-wave.org/forum/topic/modifying-beamforming_delays#post-1212 Mon, 04 Feb 2013 18:56:29 +0000 Bradley Treeby 1212@http://www.k-wave.org/forum/ <p>You make a good point, although I believe this is how the delays are normally calculated for linear arrays. Perhaps the most general way would be to add an additional property to the kWaveTransducer class that allows the centre element to be selected. This way, the beamforming delays could be computed using either the centre of the active elements (as currently), or the centre of the complete array as you suggest, or anywhere else. We will take a look before the next release.</p> <p>Apologies for the delay in replying!</p> <p>Brad. </p> http://www.k-wave.org/forum/topic/modifying-beamforming_delays#post-1181 Tue, 29 Jan 2013 11:59:53 +0000 hhamtaii 1181@http://www.k-wave.org/forum/ <p>hi Brad,<br /> the "beamforming_delays" method of "kWaveTransducer" class, is expected to calculate the appropriate delay values, but it does not count for sub_array windows other than centered window. suppose that you have an array of total 16 elements with a sliding active sub-array of 8 elements. delay values for all of these sub-arrays, are mistakenly calculated the same as the centered (middle) 8 elemnts.<br /> I propose the following solution:<br /> instead of the present line:</p> <p>% create indexing variable<br /> element_index = -(obj.number_active_elements - 1)/2:(obj.number_active_elements - 1)/2; </p> <p>one can replace the following two lines:</p> <p>% form a vector of active element indices<br /> ActiveIdc = find(obj.active_elements == 1);</p> <p>% create indexing variable<br /> element_index = -(obj.number_elements + 1)/2 + ActiveIdc;</p> <p>and it works fine.<br /> and ... I should thank you for your useful toolbox. </p>