<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Object Tracking, coordinate system and units in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Object-Tracking-coordinate-system-and-units/m-p/1003450#M31092</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm using the sample code for object tracking (2D and feature-based 3D) and would like more clarification on the units and coordinate system of the translation (obtained using PXCTracker::TrackingValues arrData-&amp;gt;translation, display function from main is copied below with the translation values in bold and italicized). Documentation seem to indicate that&amp;nbsp;the coordinate system is at the object origin and I assumed units are 'mm'. However, this does not seem to correlated when moving the camera around with the object static (z values range well above 1000 when in a 200-500mm workspace). Can someone also explain the depthnum value below. Is this code modified much from metaio? Are there references for noise and accuracy using these implementations for object tracking?&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;

&lt;P&gt;Wen&lt;/P&gt;

&lt;P&gt;void DrawTrackingValues(HWND hwndDlg, PXCTracker::TrackingValues *arrData)&lt;BR /&gt;
	{&lt;BR /&gt;
	&amp;nbsp;...&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;const double pi = 3.1415926535897;&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;const double depthnum = -630; // for the middleware being a left hand coordinate system.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&amp;nbsp;//correction values for translation and movement dependent on z values&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;float depthcorrectionfactor = (arrData-&amp;gt;translation.z/depthnum);&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;arrData-&amp;gt;translation.x = arrData-&amp;gt;translation.x/depthcorrectionfactor;&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;arrData-&amp;gt;translation.y = arrData-&amp;gt;translation.y/depthcorrectionfactor;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&amp;nbsp;PXCPoint3DF32 translation = arrData-&amp;gt;translation;&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;float xp = translation.x;&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;float yp = translation.y;&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;float zp = translation.z;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;...&lt;/P&gt;

&lt;P&gt;}&lt;/P&gt;</description>
    <pubDate>Wed, 01 Apr 2015 04:42:08 GMT</pubDate>
    <dc:creator>Wen_L_</dc:creator>
    <dc:date>2015-04-01T04:42:08Z</dc:date>
    <item>
      <title>Object Tracking, coordinate system and units</title>
      <link>https://community.intel.com/t5/Software-Archive/Object-Tracking-coordinate-system-and-units/m-p/1003450#M31092</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm using the sample code for object tracking (2D and feature-based 3D) and would like more clarification on the units and coordinate system of the translation (obtained using PXCTracker::TrackingValues arrData-&amp;gt;translation, display function from main is copied below with the translation values in bold and italicized). Documentation seem to indicate that&amp;nbsp;the coordinate system is at the object origin and I assumed units are 'mm'. However, this does not seem to correlated when moving the camera around with the object static (z values range well above 1000 when in a 200-500mm workspace). Can someone also explain the depthnum value below. Is this code modified much from metaio? Are there references for noise and accuracy using these implementations for object tracking?&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;

&lt;P&gt;Wen&lt;/P&gt;

&lt;P&gt;void DrawTrackingValues(HWND hwndDlg, PXCTracker::TrackingValues *arrData)&lt;BR /&gt;
	{&lt;BR /&gt;
	&amp;nbsp;...&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;const double pi = 3.1415926535897;&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;const double depthnum = -630; // for the middleware being a left hand coordinate system.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&amp;nbsp;//correction values for translation and movement dependent on z values&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;float depthcorrectionfactor = (arrData-&amp;gt;translation.z/depthnum);&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;arrData-&amp;gt;translation.x = arrData-&amp;gt;translation.x/depthcorrectionfactor;&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;arrData-&amp;gt;translation.y = arrData-&amp;gt;translation.y/depthcorrectionfactor;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&amp;nbsp;PXCPoint3DF32 translation = arrData-&amp;gt;translation;&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;float xp = translation.x;&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;float yp = translation.y;&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;float zp = translation.z;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;...&lt;/P&gt;

&lt;P&gt;}&lt;/P&gt;</description>
      <pubDate>Wed, 01 Apr 2015 04:42:08 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Object-Tracking-coordinate-system-and-units/m-p/1003450#M31092</guid>
      <dc:creator>Wen_L_</dc:creator>
      <dc:date>2015-04-01T04:42:08Z</dc:date>
    </item>
    <item>
      <title>Sorry to necro this question</title>
      <link>https://community.intel.com/t5/Software-Archive/Object-Tracking-coordinate-system-and-units/m-p/1003451#M31093</link>
      <description>&lt;P&gt;Sorry to necro this question but did you ever find a conversion logic? I'm facing the same issue with the latest SDK 2D Tracking sample and an F200.&lt;/P&gt;

&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 10:10:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Object-Tracking-coordinate-system-and-units/m-p/1003451#M31093</guid>
      <dc:creator>Sebastian_A_1</dc:creator>
      <dc:date>2016-03-09T10:10:40Z</dc:date>
    </item>
  </channel>
</rss>

