<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
<link rel="self" type="application/atom+xml" href="http://theeyetribe.com/forum/feed.php?f=9&amp;t=355" />

<title>The Eye Tribe</title>
<subtitle>Developer Forum</subtitle>
<link href="http://theeyetribe.com/forum/index.php" />
<updated>2014-10-29T22:52:07+02:00</updated>

<author><name><![CDATA[The Eye Tribe]]></name></author>
<id>http://theeyetribe.com/forum/feed.php?f=9&amp;t=355</id>
<entry>
<author><name><![CDATA[Martin]]></name></author>
<updated>2014-10-29T22:52:07+02:00</updated>
<published>2014-10-29T22:52:07+02:00</published>
<id>http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1475#p1475</id>
<link href="http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1475#p1475"/>
<title type="html"><![CDATA[Re: Device accuracy issue (bottom center points)]]></title>

<content type="html" xml:base="http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1475#p1475"><![CDATA[
Hey V,<br /><br />Thanks for the info. <br /><br />The setup looks very suitable, we have many similar arrangements here, but cannot reproduce (other than occasional poor calibration points). <br /><br />Are you using the calibration UI from the Eye Tribe software package or are you rolling your own?<br />Does it improve if you do a nine point instead of twelve?<br /><br />Good you sent the report to Javier, he will look into the data.<p>Statistics: Posted by <a href="http://theeyetribe.com/forum/memberlist.php?mode=viewprofile&amp;u=117">skataMartin</a> — 29 Oct 2014, 22:52</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[vstroy]]></name></author>
<updated>2014-10-21T14:20:58+02:00</updated>
<published>2014-10-21T14:20:58+02:00</published>
<id>http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1462#p1462</id>
<link href="http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1462#p1462"/>
<title type="html"><![CDATA[Re: Device accuracy issue (bottom center points)]]></title>

<content type="html" xml:base="http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1462#p1462"><![CDATA[
Hi Martin,<br /><br />Some details about our test setup:<br /><ul><li>- monitor size: 22&quot;</li><li>- eyes distance: ~50cm</li><li>- sampling rate: 30Hz</li><li>- calibration: 12 points</li></ul><br />We've tried various desktops and laptops with smaller screens. We've also made some experiments with device positioning relative to the screen. Problem remains.<br />Our clients are expierencing the same problem (deviations near bottom center point).<br /><br />And few photos:<br /><br /><img src="http://i.imgur.com/4xOMwPe.jpg" alt="Image" /><br /><img src="http://i.imgur.com/fMdJgNA.jpg" alt="Image" /><p>Statistics: Posted by <a href="http://theeyetribe.com/forum/memberlist.php?mode=viewprofile&amp;u=4171">skatavstroy</a> — 21 Oct 2014, 14:20</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[Martin]]></name></author>
<updated>2014-10-21T13:27:25+02:00</updated>
<published>2014-10-21T13:27:25+02:00</published>
<id>http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1460#p1460</id>
<link href="http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1460#p1460"/>
<title type="html"><![CDATA[Re: Device accuracy issue (bottom center points)]]></title>

<content type="html" xml:base="http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1460#p1460"><![CDATA[
Hi Vyacheslav,<br /><br />We looking into this to see if we can replicate the behavior on our end. <br /><br />Meanwhile, could you please tell me a little more about your setup, specifically the physical screen size and placement of device relative to screen. A photo would be great.<p>Statistics: Posted by <a href="http://theeyetribe.com/forum/memberlist.php?mode=viewprofile&amp;u=117">skataMartin</a> — 21 Oct 2014, 13:27</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[vstroy]]></name></author>
<updated>2014-10-20T12:48:50+02:00</updated>
<published>2014-10-20T12:48:50+02:00</published>
<id>http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1456#p1456</id>
<link href="http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1456#p1456"/>
<title type="html"><![CDATA[Re: Device accuracy issue (bottom center points)]]></title>

<content type="html" xml:base="http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1456#p1456"><![CDATA[
I think that the problem is related to the internal points interpolation inside the EyeTribe software. We can predict errors and make some corrections. But if this issue will be fixed in future TET software releases it will break our results (our math corrections will give us errors in opposite direction).<p>Statistics: Posted by <a href="http://theeyetribe.com/forum/memberlist.php?mode=viewprofile&amp;u=4171">skatavstroy</a> — 20 Oct 2014, 12:48</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[JeffKang]]></name></author>
<updated>2014-10-15T02:51:40+02:00</updated>
<published>2014-10-15T02:51:40+02:00</published>
<id>http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1453#p1453</id>
<link href="http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1453#p1453"/>
<title type="html"><![CDATA[Re: Device accuracy issue (bottom center points)]]></title>

<content type="html" xml:base="http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1453#p1453"><![CDATA[
Check out this comment:<br /><br /><blockquote class="uncited"><div><br />With a 5 stars calibration, I have very high precision, the mouse cursor is constrained to an area maybe 2-3 mm across and (when smoothed) low travel in that area, but extremely low accuracy. The cursor might be an inch or more away from where I am looking. Not drifting, just sitting there.<br /><br />Ultimarly, that's a good sign. Low accuracy can be fixed by math, low precision can't.<br /><br />They have a mythical 1.0 build in QA that should improve accuracy, but in the meantime there isn't much you can do, other than roll your own calibration technique and cursor control.<br /></div></blockquote><br /><br /><!-- l --><a class="postlink-local" href="http://theeyetribe.com/forum/viewtopic.php?f=9&amp;t=342">viewtopic.php?f=9&amp;t=342</a><!-- l --><p>Statistics: Posted by <a href="http://theeyetribe.com/forum/memberlist.php?mode=viewprofile&amp;u=2379">skataJeffKang</a> — 15 Oct 2014, 02:51</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[vstroy]]></name></author>
<updated>2014-10-14T14:06:36+02:00</updated>
<published>2014-10-14T14:06:36+02:00</published>
<id>http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1450#p1450</id>
<link href="http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1450#p1450"/>
<title type="html"><![CDATA[Device accuracy issue (bottom center points)]]></title>

<content type="html" xml:base="http://theeyetribe.com/forum/viewtopic.php?t=355&amp;p=1450#p1450"><![CDATA[
We have tested your device intensively and followed all best practices from TET, but still have some questions and need your assistance.<br /><br />Screenshot with our results: <img src="http://i.imgur.com/lykXyyf.png" alt="Image" /><br />In all cases people saw 9-point grid and focused on all of them or followed some pattern. In all cases 9-point calibration was made and calibration results were never lower then 3 stars. Nevertheless, we saw stable incorrect results for lower and sometimes upper point in the middle column (see the image attached).<br /><br />We tried to position device on your tripod or using other DIY mounts, but we constantly see these shifts to the center (looks like the &quot;pillow effect&quot; in old CRT monitors). Points on the right or left side look much more accurate. We've got the same results with another ET device.<br /><br />Please let us know, what is the possible reason of such behavior.<p>Statistics: Posted by <a href="http://theeyetribe.com/forum/memberlist.php?mode=viewprofile&amp;u=4171">skatavstroy</a> — 14 Oct 2014, 14:06</p><hr />
]]></content>
</entry>
</feed>