Hi Sean,<div><br><div class="gmail_quote">On Tue, Jul 10, 2012 at 6:28 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">
<div>Hi Nikhil,</div><div><br></div><div>My config and state files are attached.</div><div><br></div><div>While running Paraview, I used netstat to look for a connection to the tracking server, but found no connection. If I use "vrpn_print_devices <a href="mailto:iotracker@192.168.20.9" target="_blank">iotracker@192.168.20.9</a>" then netstat can find the connection. </div>
<div><br></div></blockquote><div>This means that you are not creating a connection. You may have to check your configuration file. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div></div><div>By the way, the vrpn_print_devices command returns information on 2 different "sensors". Should I be selecting one of them in the state file? Or is this standard for a single tracking device?</div>
<div><br></div></blockquote><div><br></div><div>VRPN can return a number of tracking sensors but you need to pick one. For example if you want to use Kinect with FAAST then you get around 23 tracked sensors. Paraview is capable of only handling two tracked sensors one for head and one for hand/wand. If you have two tracking devices then use one for head and another for wand(hand) tracking. If you need to simply test tracking then you can set wand pose instead of head because the wand is not disabled on client so you can see stuff move on the screen.</div>
<div><br></div><div>I'll take a look at the files and let you know if I find something wrong with it.</div><div><br></div><div>-Nikhil </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div></div><div>Thanks,</div><div><br></div><div>Seán</div><div class="HOEnZb"><div class="h5">
<div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><br><br><div class="gmail_quote">On Tue, Jul 10, 2012 at 3:04 AM, Nikhil Shetty <span dir="ltr"><<a href="mailto:nikhil.shetty@kitware.com" target="_blank">nikhil.shetty@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Sean,<div><br></div><div>Can you send me your config and state files. I'll take a look.</div><span><font color="#888888"><div>
<br></div></font></span><div><span><font color="#888888">-Nikhil</font></span><div><div><br><br><div class="gmail_quote">On Mon, Jul 9, 2012 at 11:19 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"><div>Thanks Nikhil. </div><div><br></div><div>I should have mentioned that I have set the VRplugin to load automatically both for the server and client (and checked that it is marked as "loaded" in the manager). My apologies for not mentioning that in the last message. </div>
<div><br></div><div>The figures I used in the pvx file describing the corners of the screen (in the coordinates / units of the tracking system) are not correct, I just used them for testing. I was still expecting to see some change on the display when I move the tracking target (even if it's not the "correct" change). I can recalibrate the system to rule this out, but I suspect that this will not solve the problem.</div>
<div><br></div><div>Perhaps I can use a network monitoring tool to see if Paraview is actually connecting to the tracking server.</div><div><br></div><div>Seán</div><div><br></div><div><br></div><br><br><div class="gmail_quote">
<div><div>
On Mon, Jul 9, 2012 at 3:14 PM, Nikhil Shetty <span dir="ltr"><<a href="mailto:nikhil.shetty@kitware.com" target="_blank">nikhil.shetty@kitware.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>
Sean,<div><br><div class="gmail_quote"><div>On Mon, Jul 9, 2012 at 9:04 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">
Hi Nikhil and Stephan,<div><br></div><div>Outstanding response time, thanks! As you say, my first mistake is not using a CAVE client-server setup. </div><div><br></div><div>I have set up a CAVE display with the short pvx file below, (borrowed from the CAVE example). I run the server with</div>
<div>pvserver /path/to/config.pvx</div><div>I don't use MPI because I only have 1 screen and hence 1 process. I launch the client (by ssh from another machine) with</div><div>paraview --stereo --stereo-type="Crystal Eyes" --server="hubble1" --state=/path/to/1.pvsm</div>
<div>where "hubble1" is the local hostname, and also the PVserver name.</div><div><br></div><div>Result: A "cave" type window is launched in fullscreen mode on the main display showing a stereo image. The standard Paraview client is available on the remote machine (via X forwarding). I can manipulate the session with the mouse on the remote machine. Moving the tracking targets has no effect on the main display.</div>
<div><br></div><div>Perhaps I should save the state from the CAVE session and append the VRPN settings to that one instead?</div><div><br></div></blockquote></div><div>Make sure that the VRPlugin is loaded at startup. The appended VRPN setting in *.pvsm are read by the plugin. When the plugin is not loaded then the configuration is simply ignored.</div>
<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,</div><div><br></div><div>Seán</div><div><br></div><div><br></div>
<div>------------------------------ config.pvx ------------------------</div><div><div><?xml version="1.0" ?></div><div><pvx></div><div> <Process Type="client" /></div><div> <Process Type="server"></div>
<div> <EyeSeparation Value="0.065"/></div><div> <Machine name="hubble1"</div><div> Environment="DISPLAY=:0"</div><div> LowerLeft="-1.0 -1.0 -1.0"</div>
<div> LowerRight="1.0 -1.0 -1.0"</div><div> UpperRight="1.0 1.0 -1.0"></div><div> </Machine></div><div> </Process></div><div></pvx></div></div>
</blockquote></div></div><br></div>
<br></div></div><div>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
<br></div></blockquote></div><br>
</blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
<br></blockquote></div><br>
</div></div></blockquote></div><br></div>