<?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: Ultrasound Volume</title>
		<link>http://www.k-wave.org/forum/topic/ultrasound-volume</link>
		<description>Support for the k-Wave MATLAB toolbox</description>
		<language>en-US</language>
		<pubDate>Tue, 12 May 2026 23:41:34 +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/ultrasound-volume" rel="self" type="application/rss+xml" />

		<item>
			<title>Bradley Treeby on "Ultrasound Volume"</title>
			<link>http://www.k-wave.org/forum/topic/ultrasound-volume#post-632</link>
			<pubDate>Tue, 24 Jul 2012 02:15:35 +0000</pubDate>
			<dc:creator>Bradley Treeby</dc:creator>
			<guid isPermaLink="false">632@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi Ricard,&#60;/p&#62;
&#60;p&#62;To form a 3D ultrasound image requires some information from the elevation plane. Just changing the elevation focus distance won't be enough (this will just give you the same 2D image with slightly different contributions from out-of-plane scatterers). One possibility without changing the code too much would be to simulate multiple 2D images (for example, by translating the medium or the position of your transducer). Clinical images are often formed in this manner by using a conventional diagnostic ultrasound probe along with a tracking device. The 2D images are then stitched together to form a single 3D volume.&#60;/p&#62;
&#60;p&#62;I am currently on the road, but when I'm back at my desk I'll take a look at creating an example using a 2D array probe.&#60;/p&#62;
&#60;p&#62;Brad.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>rdelgado on "Ultrasound Volume"</title>
			<link>http://www.k-wave.org/forum/topic/ultrasound-volume#post-616</link>
			<pubDate>Mon, 16 Jul 2012 12:30:46 +0000</pubDate>
			<dc:creator>rdelgado</dc:creator>
			<guid isPermaLink="false">616@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi again,&#60;br /&#62;
I tried to run the script &#34;example example_us_bmode_linear_transducer.m&#34; for different values of the transducer.elevation_focus_distance. The output does not reflect the structure of the three spheres. Is my approach valid?&#60;br /&#62;
Thanks&#60;/p&#62;
&#60;p&#62;Ricard
&#60;/p&#62;</description>
		</item>
		<item>
			<title>rdelgado on "Ultrasound Volume"</title>
			<link>http://www.k-wave.org/forum/topic/ultrasound-volume#post-603</link>
			<pubDate>Tue, 10 Jul 2012 07:53:58 +0000</pubDate>
			<dc:creator>rdelgado</dc:creator>
			<guid isPermaLink="false">603@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi Bradley,&#60;br /&#62;
I am working on the example example_us_bmode_linear_transducer.m. I've seen that there is a property of the transducer (transducer.elevation_focus_distance) that is supposed to provide information about the focus distance in the elevator plane. Can I simply call this script (example example_us_bmode_linear_transducer.m) with different values of this parameter to build the z-stack? I am not so much concerned about the computational complexity, but rather in an easy way to obtain the stack.&#60;br /&#62;
Thanks&#60;/p&#62;
&#60;p&#62;Ricard
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Bradley Treeby on "Ultrasound Volume"</title>
			<link>http://www.k-wave.org/forum/topic/ultrasound-volume#post-601</link>
			<pubDate>Mon, 09 Jul 2012 06:53:32 +0000</pubDate>
			<dc:creator>Bradley Treeby</dc:creator>
			<guid isPermaLink="false">601@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi Ricard,&#60;/p&#62;
&#60;p&#62;This sort of simulation would certainly be possible with k-Wave, but I'm not aware of any examples that anyone has written yet. You would need to define the source as a 2D array instead of a 1D array, and process the input and output signals accordingly. It will probably be a little fiddly the first time around. It's on our list of examples to include, but unfortunately the turn around is not likely to be fast.&#60;/p&#62;
&#60;p&#62;Brad.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>rdelgado on "Ultrasound Volume"</title>
			<link>http://www.k-wave.org/forum/topic/ultrasound-volume#post-593</link>
			<pubDate>Fri, 06 Jul 2012 09:44:43 +0000</pubDate>
			<dc:creator>rdelgado</dc:creator>
			<guid isPermaLink="false">593@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Just to provide a bit more of context. What I'm trying to do is to generate a 3D phantom with k-Wave to evaluate the performance of a segmentation algorithm I'm working on. That's why I'd like to have the 3D ultrasound images.&#60;br /&#62;
Thanks&#60;/p&#62;
&#60;p&#62;Ricard
&#60;/p&#62;</description>
		</item>
		<item>
			<title>rdelgado on "Ultrasound Volume"</title>
			<link>http://www.k-wave.org/forum/topic/ultrasound-volume#post-592</link>
			<pubDate>Fri, 06 Jul 2012 08:51:41 +0000</pubDate>
			<dc:creator>rdelgado</dc:creator>
			<guid isPermaLink="false">592@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi,&#60;/p&#62;
&#60;p&#62;I'm new to k-Wave so forgive my naive questions. Perhaps this has been answered many times, but I was wondering if there is any code available to show how you simulate a 3D ultrasound images. I am trying to extract the data from the phantom described in &#60;a href=&#34;http://www.k-wave.org/documentation/example_us_bmode_linear_transducer.php&#34; rel=&#34;nofollow&#34;&#62;http://www.k-wave.org/documentation/example_us_bmode_linear_transducer.php&#60;/a&#62; but I only get 2D images. Is it possible?&#60;br /&#62;
Thanks&#60;/p&#62;
&#60;p&#62;Ricard
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
