[Paraview] VRPN Problem detailed desciption

Christian Wohlschlager Christian.Wohlschlager at jku.at
Wed Mar 14 02:42:55 EDT 2012


** Reply Requested When Convenient **


Dear Nikihil ! 

YEESS very good  thank you for your support i tell you next ParaView
master how it s going on 

the secound thing with the cutfunvtion: 

I try to visualsize a skill made from a mr in the cave. 
With a PAD ( incuding a tracking device and some buittons ) a try to
move the skul and a secound button where i try to make a kind of hole in
the skull and i can see thru. 
therefor i need a Headtracker ok  
a wand ( not ok) 
a button ( should be ok) 
and a secound button which simulates the tracking coordinate and a hole
or cut there. 

  

thank again 

christian


Christian Wohlschlager
JKU Universität Linz
Altenbergerstr.69
4040 Linz
Austria



>>> Nikhil Shetty <nikhil.shetty at kitware.com> 3/13/2012 3:47 PM >>>
Hi Christian, 



On Tue, Mar 13, 2012 at 9:32 AM, Christian Wohlschlager
<Christian.Wohlschlager at jku.at> wrote:



Hy Nikhil ! 


Yes it worked at least for the head sensor, for the wandpos i need the
cutfunktion i didnt managed to put this in the pvsm file (if i did it
crashes sometimes or even didnt start at all) 
 



The cutfunction typically comes with a slice or clip filter. Can you
send me a few more details as to the process you followed and what
errors you see. 



HeadPos and WandPos are both set on the vtkCamera (or RenderView in
case of PV). There was a bug which didnt update the WandPos on the
server side and I pushed a fix for that and in VTK and am waiting for it
to get into ParaView master (it may come in by Friday). 





it seems to me that using the VRPlugin the system is slower than
before, is there something i can do to make it a little bit faster ( i
have enough cpus) it looks to me that even the crosshair cursor is
slower than before, so this looks like it done allways slow using this
VRPlugin . 
But anyway thanks for your help on this issue before i managed with you
help to make it run. 

 



Yes we identified this performance issue as well last week and have a
fix for it in next branch and am awaiting for it to get into ParaView
master (hopefully by Friday). You can pull pv next and compile it in the
time being. 



-Nikhil 





mfg 



christian


Christian Wohlschlager
JKU Universität Linz
Altenbergerstr.69
4040 Linz
Austria




>>> Nikhil Shetty <nikhil.shetty at kitware.com> 3/12/2012 12:03 PM >>>
Hi Christian, 



Yes this will be a little annoying till a GUI is developed to handle
this. But right now we have need to manually figure this out. 



You need to construct your pipeline and have pv Proxy Objects in place
before you can apply VR interactor styles to them. 



So things like 'RenderView1.HeadPose' implies 'Proxy.Property'. The
state file stores this information about what Proxies and properties are
available so you could infer this info from the state file. An easier
way to figure out the objects available is to use the Property Linking
Tool in the GUI 



Tools->Manage Links->Add->Mode:PropertyLinks



I am attaching a sample state file which may be useful. 



-Nikhil 



On Mon, Mar 12, 2012 at 2:42 AM, Christian Wohlschlager
<Christian.Wohlschlager at jku.at> wrote:



Dear Nikhil ! 


Sorry didnt tell you what the exact error message was: 



on the client side ( pvserver loaded ) 
after loading the *.pvsm state file  


vtkVRStyleTracking::GetOutProxyNProperty 
Proxy ( RenderView) :Not Found 
vtkVRStyleGrabNUpdateMatrix::GetOutProxyNProperty 
Proxy ( RenderView1) :Not Found 
Proxy ( CutFunction) :Not Found 
Proxy ( CutFunction) :Not Found 
Segmentation fault (core dumped) 


thank you 




christian 


Christian Wohlschlager
JKU Universität Linz
Altenbergerstr.69
4040 Linz
Austria




>>> Nikhil Shetty <nikhil.shetty at kitware.com> 3/9/2012 4:52 PM >>>
Hi Christian, 






On Fri, Mar 9, 2012 at 2:01 AM, Christian Wohlschlager
<Christian.Wohlschlager at jku.at> wrote:



Thank you Nikhil ! 


Sorry this --vrpn thing was not in your homepage it comes on  



http://wiki.iq-station.com/index.php?title=ImmersiveParaView 


I shouldnt trust eh even it has a WIKI in its name. 


In the new vrpn thing there are some new issues i dont know: 


this is part of a .pvsm file which should be loaded before usage: 


<!--> 
VRPN Connections  
</!-->  
<VRConnectionManager> 
<VRPNConnection name="cspad" address="curvedscreen at virtu"> 
<Button id="1" name="1"/> 
<Button id="2" name="2"/> 
<Button id="3" name="3"/> 
<Tracker id="1" name="head"/> 
<Tracker id="2" name="wand"/> 
</VRPNConnection> 
</VRConnectionManager> 
<!--> 
Interactor Style 
</!-->  
<VRInteractorStyles> 
<Style class="vtkVRStyleTracking" set_property="RenderView1.HeadPose">

<Tracker name="cspad.head"/> 
</Style> 
<Style class="vtkVRStyleGrabNUpdateMatrix"
set_property="RenderView1.WandPose"> 
<Tracker name="cspad.wand"/> 
<Button name="cspad.1"/> 
<MatrixProperty name="RenderView1.WandPose"/> 
</Style> 
<Style class="vtkVRStyleGrabNTranslateSliceOrigin"
origin="CutFunction.Origin"> 
<Button name="cspad.2"/> 
<Tracker name="cspad.wand"/> 
</Style> 
<Style class="vtkVRStyleGrabNRotateSliceNormal"
normal="CutFunction.Normal"> 
<Button name="cspad.3"/> 
<Tracker name="cspad.wand"/> 
</Style> 
</VRInteractorStyles> 
</!-->  

the thing is i dont know what i should fill in for 


<Style class="vtkVRStyleTracking" set_property="RenderView1.HeadPose">



RenderView1.HeadPose 
or 
<Style class="vtkVRStyleGrabNTranslateSliceOrigin"
origin="CutFunction.Origin"> 
CutFunktion.Origin 


 

I understand your concern. The wiki page does document this very well.
But typically the interactor styles help you choose what type of
interaction you want to do. If you want head tracking use the
vtkVRStyleTracking which uses tracking data 'cspad.head' and changes the
property RenderView1.HeadPose (in the state file) 



If your scene has a slice and you want to manipulate the slice then you
can use vtkVRStyleGrabNTranslateSliceOrigin style. It basically takes
tracker inputs and a button to change the slice origin
(CutFunction.Origin). So you can press button and move the wand to move
the slice plane. 



I will be updating the document with more info about the interactor
styles. 





thank you for your help 


christian 


Christian Wohlschlager
JKU Universität Linz
Altenbergerstr.69
4040 Linz
Austria




>>> Nikhil Shetty <nikhil.shetty at kitware.com> 3/8/2012 2:24 PM >>>
Hi Christian, 




Here is the latest documentation for Paraview in CAVE

http://www.itk.org/Wiki/ParaView/Users_Guide/CAVE_Display 



The --vrpn option was replaced with a different mechanism (see
document). Can you send me a reference to the page where you found the
info so that can be updated. 



-Nikhil 



On Thu, Mar 8, 2012 at 3:10 AM, Christian Wohlschlager
<Christian.Wohlschlager at jku.at> wrote:



Hy ! 


Hy I'm using ParaView 3.14 in a Cave environment using VRPN when i try
to start ./pvserver --vrpn . It says cannot open file --vrpn) ( which
should mean the swtich --vrpn is not know) but on the Homepage of
ParaView is mentioned. ANY IDEA ?? 



mfg 


Christian  

Christian Wohlschlager
JKU Universität Linz
Altenbergerstr.69
4040 Linz
Austria



 


_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

 


 


 


 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20120314/590e6747/attachment-0001.htm>


More information about the ParaView mailing list