<div dir="ltr">On Sat, Aug 17, 2013 at 3:39 PM, Francesco Callari <span dir="ltr"><<a href="mailto:fgcallari@gmail.com" target="_blank" onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=fgcallari@gmail.com&cc=&bcc=&su=&body=','_blank');return false;">fgcallari@gmail.com</a>></span> wrote:<br>
<div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="im"><span style="color:rgb(34,34,34)">It is conceptually quite easy, and in fact the easiest implementation is the most general one: a scene graph solver. </span></div>
</div></blockquote><div><br></div><div>Thanks for the detailed writeup. Reading that, I think expressing the solver constraints which are most useful may be easier to work with using a hybrid approach. For example, it seems much easier (from a user-UI perspective) to bundle a bunch of trackers and say they are on a plane, or express a constraint about which is closer to the camera -- without involving the 3d scene graph. </div>
</div>
</div></div>