Hi Sean,<div><br><div class="gmail_quote">On Mon, Jul 23, 2012 at 11:29 AM, Sean Delaney <span dir="ltr"><<a href="mailto:sdelaney@cp.dias.ie" target="_blank">sdelaney@cp.dias.ie</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear Nikhil,<div><br></div><div>Success! I believe I have the configuration right. Now I just need to add a wand. </div><div></div></blockquote><div><br></div><div>Awesome. Let me know if you run into trouble.</div><div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div> </div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div></div><div>By the way, I may have found a bug / feature. It seems like I have to specify the eye separation value in mm, even though I have transformed my tracker units to metres in the state file. Perhaps this is another mistake in my configuration though. Please let me know if that's the case.</div>
<div><br></div></blockquote><div><br></div><div>Yes you have indeed found an issue. The eye separation is usually a constant in whatever coordinate system you have at the end. However I am not sure if we should explicitly state this is the documentation of apply the transformation before saving it. The eye separation value does not use the transformation but from a users perspective would a user expect the transformation to be applied or not. I'd like to know your thoughts on this.</div>
<div><br></div><div>-Nikhil</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div></div><div>Thanks very much for all your help</div><div><br></div><div>Seán</div>
</blockquote></div><br></div>