<?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: Data Ordering of 3D sensor output</title>
		<link>http://www.k-wave.org/forum/topic/data-ordering-of-3d-sensor-output</link>
		<description>Support for the k-Wave MATLAB toolbox</description>
		<language>en-US</language>
		<pubDate>Wed, 13 May 2026 00:22:41 +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/data-ordering-of-3d-sensor-output" rel="self" type="application/rss+xml" />

		<item>
			<title>KHO on "Data Ordering of 3D sensor output"</title>
			<link>http://www.k-wave.org/forum/topic/data-ordering-of-3d-sensor-output#post-1039</link>
			<pubDate>Tue, 20 Nov 2012 11:12:28 +0000</pubDate>
			<dc:creator>KHO</dc:creator>
			<guid isPermaLink="false">1039@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Ah yes, that makes perfect sense. &#60;/p&#62;
&#60;p&#62;Thank you very much!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Bradley Treeby on "Data Ordering of 3D sensor output"</title>
			<link>http://www.k-wave.org/forum/topic/data-ordering-of-3d-sensor-output#post-1018</link>
			<pubDate>Fri, 16 Nov 2012 23:30:56 +0000</pubDate>
			<dc:creator>Bradley Treeby</dc:creator>
			<guid isPermaLink="false">1018@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi KHO,&#60;/p&#62;
&#60;p&#62;The ordering follows the MATLAB column-wise linear indexing (i.e., the order the matrix elements are physically stored in memory and on disk). In 3D, this means the matrices are indexed first in the x-direction (dimension 1), then the y-direction (dimension 2), and then the z-direction (dimension 3). Thus for your example, (a plane x = a), the order would be grid(a, 1, 1), grid(a, 2, 1), etc.&#60;/p&#62;
&#60;p&#62;One way to visualise the matrix ordering is to use reshape:&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;&#38;gt;&#38;gt; Nx = 4; Ny = 3; Nz = 2;
&#38;gt;&#38;gt; reshape((1:Nx*Ny*Nz), Nx, Ny, Nz)

ans(:,:,1) =

     1     5     9
     2     6    10
     3     7    11
     4     8    12

ans(:,:,2) =

    13    17    21
    14    18    22
    15    19    23
    16    20    24&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;Hope that helps,&#60;/p&#62;
&#60;p&#62;Brad.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>KHO on "Data Ordering of 3D sensor output"</title>
			<link>http://www.k-wave.org/forum/topic/data-ordering-of-3d-sensor-output#post-1014</link>
			<pubDate>Fri, 16 Nov 2012 12:15:29 +0000</pubDate>
			<dc:creator>KHO</dc:creator>
			<guid isPermaLink="false">1014@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi all,&#60;/p&#62;
&#60;p&#62;I was wondering, in what order the recorded data is actually stored. For a sensor that is built up from a list of cartesian coordinates, this is pretty clear (the data is stored in the same order as the sensor locations are defined), but for a sensor that is defined as a binary mask there is multiple options for the order of the sensor data.&#60;/p&#62;
&#60;p&#62;For example, if the plane x = a serves as a sensor, will the sensor data be stored in order of increasing y and then increasing z (i.e. grid(a,1,1), grid(a,2,1), grid(a,3,1), ..., grid(a,1,2), grid(a,2,2), ...) or vice versa (i.e. grid(a,1,1), grid(a,1,2), ..., grid(a,2,1), grid(a,2,2), ...), or maybe a totally different order?
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
