<?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; Topic: Performance drop using different directivity angles</title>
		<link>http://www.k-wave.org/forum/topic/performance-drop-using-different-directivity-angles</link>
		<description>Support for the k-Wave MATLAB toolbox</description>
		<language>en-US</language>
		<pubDate>Tue, 12 May 2026 22:32:16 +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/topic/performance-drop-using-different-directivity-angles" rel="self" type="application/rss+xml" />

		<item>
			<title>bencox on "Performance drop using different directivity angles"</title>
			<link>http://www.k-wave.org/forum/topic/performance-drop-using-different-directivity-angles#post-7242</link>
			<pubDate>Thu, 27 Feb 2020 12:31:02 +0000</pubDate>
			<dc:creator>bencox</dc:creator>
			<guid isPermaLink="false">7242@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi kdreher,&#60;/p&#62;
&#60;p&#62;Yes, that is a limitation of the approach we've used. The directivity of the sensing element is applied in k-space, which makes it very general - any directionality could in principle be modelled that way. However, it means that a separate fft is required for each different directivity used, which is why it slows down so much. A faster way to incorporate directionality - although with less flexibility - is simply to use several pixels added together as one sensing 'element'. &#60;/p&#62;
&#60;p&#62;Best wishes,&#60;br /&#62;
Ben
&#60;/p&#62;</description>
		</item>
		<item>
			<title>jackYANG on "Performance drop using different directivity angles"</title>
			<link>http://www.k-wave.org/forum/topic/performance-drop-using-different-directivity-angles#post-7145</link>
			<pubDate>Fri, 06 Dec 2019 02:26:53 +0000</pubDate>
			<dc:creator>jackYANG</dc:creator>
			<guid isPermaLink="false">7145@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Generally speaking, two-dimensional simulation is relatively fast,please show me your code for further communication.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>kdreher on "Performance drop using different directivity angles"</title>
			<link>http://www.k-wave.org/forum/topic/performance-drop-using-different-directivity-angles#post-7143</link>
			<pubDate>Tue, 03 Dec 2019 11:37:52 +0000</pubDate>
			<dc:creator>kdreher</dc:creator>
			<guid isPermaLink="false">7143@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;I'm doing a 2D simulation in which I defined 256 detector elements using the &#60;code&#62;sensor.mask&#60;/code&#62; property. I arranged them in an arc shape and by using the &#60;code&#62;sensor.directivity_angle&#60;/code&#62; property, I focussed them to the center of the circle.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>jackYANG on "Performance drop using different directivity angles"</title>
			<link>http://www.k-wave.org/forum/topic/performance-drop-using-different-directivity-angles#post-7140</link>
			<pubDate>Sat, 30 Nov 2019 13:36:53 +0000</pubDate>
			<dc:creator>jackYANG</dc:creator>
			<guid isPermaLink="false">7140@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Do you mean the defined 256 concave transducers?which are divided by angle? I have also recently worked on the circular concave phased array focusing, but I have 128 elements. Are you two-dimensional simulation or 3D simulation. If you can,share your code and communicate together will be better
&#60;/p&#62;</description>
		</item>
		<item>
			<title>kdreher on "Performance drop using different directivity angles"</title>
			<link>http://www.k-wave.org/forum/topic/performance-drop-using-different-directivity-angles#post-7138</link>
			<pubDate>Fri, 29 Nov 2019 14:35:35 +0000</pubDate>
			<dc:creator>kdreher</dc:creator>
			<guid isPermaLink="false">7138@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hello,&#60;/p&#62;
&#60;p&#62;I wanted to do a simulation, for which I defined an arc-shaped detector geometry in a sensor mask with 256 elements. Using a sensor directivity angle mask, I encountered a drop in calculation speed using different angles for every single one of 256 detector elements (focus on the center of the circle). It turns out, that this simulation took about 25 times longer than a simulation which had only one directivity angle for all the detector elements or compared not settings angles at all so that the elements were omnidirectional. &#60;/p&#62;
&#60;p&#62;Do you use some techniques in your code that enable a faster calculation if all the angles are the same?&#60;br /&#62;
If yes, what do you propose I should do if I want to keep the focus on the center of the circle?&#60;/p&#62;
&#60;p&#62;Sincerely,&#60;br /&#62;
Kris
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
