[Paraview] Using VR-Style input devices

2012-10-24 Thread Johannes Zarl 
Hi,

I'm currently trying to configure ParaView for a CAVE-like environment. So far 
I was able to set up the pvservers correctly and even make headtracking over 
VRPN work.

Myself, I'm more of a newbie concerning ParaView, so I'm having some trouble 
understanding the state-file and how to define a wand-device so that ParaView 
can use it.

As far as I understand it, the VRPlugin reads the VRConnectionManager and 
VRInteractorStyles tags from the state-file and makes the connection to the 
server.

The Styles in VRInteractorStyles are supposed to reference a proxy name, that 
they are then attached to. So in this example:


   ...snip...

Re: [Paraview] Using VR-Style input devices

2012-10-24 Thread Nikhil Shetty 
Hi,

On Wed, Oct 24, 2012 at 9:40 AM, Johannes Zarl  wrote:

> Hi,
>
> I'm currently trying to configure ParaView for a CAVE-like environment. So
> far
> I was able to set up the pvservers correctly and even make headtracking
> over
> VRPN work.
>
> Awesome.


> Myself, I'm more of a newbie concerning ParaView, so I'm having some
> trouble
> understanding the state-file and how to define a wand-device so that
> ParaView
> can use it.
>
> A state file represents the state of all the objects currently in the
scene.


> As far as I understand it, the VRPlugin reads the VRConnectionManager and
> VRInteractorStyles tags from the state-file and makes the connection to the
> server.
>
> This was more of the hack way of connecting device inputs to different
actions. I think there is a GUI in the works that would make this easier.


> The Styles in VRInteractorStyles are supposed to reference a proxy name,
> that
> they are then attached to. So in this example:
>
> 
>...snip...
>origin="CutFunction.Origin">
>

Re: [Paraview] Using VR-Style input devices

2012-10-24 Thread Aashish Chaudhary 
Hi Johannes,

Very recently, we have improved the VR API and related tools and now
the VR plugin comes with a GUI to configure connection managers and
interactor styles.

The way it works now is that you create a connection manager (lines
475 - 483), which will be generated by the GUI if used, and then for
the styles,
you would link it with the ID of the proxy and its specific property
that you want to control. Now said that the GUI shows you the name of
the proxy and not the ID
for obvious reasons. Then depending upon the type of the proxy and
property you specify a particular input from a HCI device. Currently
we support analog, button, and tracker.

The wiki here is bit old:
http://www.paraview.org/Wiki/ParaView/Users_Guide/CAVE_Display
We wrote a source article as well: http://www.kitware.com/source/home/post/66

This recent work is not in master yet (hopefully this Friday) but you
can checkout this branch: vtk_vr_improvements_new_gui
if you want to from paraview stage repository. The branch contains
bunch of bug fixes, and API improvements.

475   
476 
477   
478   
479   
480   
481   
482 
483   
484   
485 
486   
487 
488 
489   
490

Re: [Paraview] Using VR-Style input devices

2012-10-24 Thread Johannes Zarl 
On Wednesday 24 October 2012 17:01:37 Aashish Chaudhary wrote:
> The way it works now is that you create a connection manager (lines
> 475 - 483), which will be generated by the GUI if used, and then for
> the styles,
> you would link it with the ID of the proxy and its specific property
> that you want to control. Now said that the GUI shows you the name of
> the proxy and not the ID
> for obvious reasons. Then depending upon the type of the proxy and
> property you specify a particular input from a HCI device. Currently
> we support analog, button, and tracker.
> 
> The wiki here is bit old:
> http://www.paraview.org/Wiki/ParaView/Users_Guide/CAVE_Display

Yes, I noticed. Together with the information in a thread on this list
(http://www.paraview.org/pipermail/paraview/2012-July/025507.html), it was 
quite valuable, though...

> We wrote a source article as well:
> http://www.kitware.com/source/home/post/66

Thanks, I didn't see that before.

> 
> This recent work is not in master yet (hopefully this Friday) but you
> can checkout this branch: vtk_vr_improvements_new_gui
> if you want to from paraview stage repository. The branch contains
> bunch of bug fixes, and API improvements.

That's great news -- I wasn't aware that the GUI work is this close to 
entering master. The screenshot looks promising. I will definitely try it out 
next week.

Thanks,
  Johannes
___
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

Re: [Paraview] Using VR-Style input devices

2012-10-30 Thread Johannes Zarl 
Hello again,

Today I tried out the new VR improvements in the master branch. I can tell 
it's a big improvement over the state-file-hacking. Connecting some tracker 
input to an object is so much easier (and less error-prone) now!

However, some issues remain for me:

1) GUI-Improvements:
 - It would be nice if one could specify the TrackerTransform via the GUI
 - The ability to load tracker-configurations from a file would be handy
 - When connecting tracker-input to objects, it would be nice if only 
compatible properties were displayed.
 - It would be nice if the grab tool would work globally, more like the mouse, 
and not have to be connected to a specific object.

2) Display issues:
 - In a curved screen setup powered by 3 overlapping projectors, the 
perspective seems to be incorrect:
This can be most easily observed when you move your head past the coordinate 
system origin. What I would expect to see is that the z-axis (pointing out of 
the screen) points somewhat to the right when my x-position is negative, and 
to the left when my x-position is positive. What I actually see is that the 
perspective of the axis-cross does not change.
What could I have messed up in the configuration that would cause this?

 - When moving a Slice-plane using the tracker (SliceOrigin,SliceOrientation), 
the displayed slice plane is not updated. I can see that the plane was moved 
on the client window, but the actual slice is not affected. I have to move the 
plane a little with the mouse to trigger an update of the slice.

 - Grabbing an object only affects the object in the client window, not the 
server view. 
When the Grab tool is connected to an object, I can move that object around, 
but I only see this in the client window. On the server side, things are 
totally unaffected by the changes. (I didn't test this one again with the new 
git master, so excuse me if it has been fixed since 3.14.1)

3) Loose ends
I didn't find anything I can do with an analog input. Do I have to enable some 
special build option to enable those?

Cheers,
  Johannes


Am 24.10.2012, 17:01:37 schrieb Aashish Chaudhary:
> Hi Johannes,
> 
> Very recently, we have improved the VR API and related tools and now
> the VR plugin comes with a GUI to configure connection managers and
> interactor styles.
> 
> The way it works now is that you create a connection manager (lines
> 475 - 483), which will be generated by the GUI if used, and then for
> the styles,
> you would link it with the ID of the proxy and its specific property
> that you want to control. Now said that the GUI shows you the name of
> the proxy and not the ID
> for obvious reasons. Then depending upon the type of the proxy and
> property you specify a particular input from a HCI device. Currently
> we support analog, button, and tracker.
> 
> The wiki here is bit old:
> http://www.paraview.org/Wiki/ParaView/Users_Guide/CAVE_Display
> We wrote a source article as well:
> http://www.kitware.com/source/home/post/66
> 
> This recent work is not in master yet (hopefully this Friday) but you
> can checkout this branch: vtk_vr_improvements_new_gui
> if you want to from paraview stage repository. The branch contains
> bunch of bug fixes, and API improvements.
> 
> 475   
> 476 
> 477   
> 478   
> 479   
> 480   
> 481   
> 482 
> 483   
> 484   
> 485  property="EyeTransformMatrix">
> 486   
> 487 
> 488  property="ModelTransformMatrix">
> 489   
> 490

Re: [Paraview] Using VR-Style input devices

2012-11-05 Thread Aashish Chaudhary 
Hi Johannes,

However, some issues remain for me:
>
> 1) GUI-Improvements:
>  - It would be nice if one could specify the TrackerTransform via the GUI
>  - The ability to load tracker-configurations from a file would be handy
>  - When connecting tracker-input to objects, it would be nice if only
> compatible properties were displayed.
>

Sure, this is a good suggestion and we wanted to do this but ran out of
time.


>  - It would be nice if the grab tool would work globally, more like the
> mouse,
> and not have to be connected to a specific object.
>

I am not so sure what you are saying here, because currently the grab style
just works on the scene and not on a particular object. Current we don't
perform intersection but you could extend the style to do so.

>
> 2) Display issues:
>  - In a curved screen setup powered by 3 overlapping projectors, the
> perspective seems to be incorrect:
> This can be most easily observed when you move your head past the
> coordinate
> system origin. What I would expect to see is that the z-axis (pointing out
> of
> the screen) points somewhat to the right when my x-position is negative,
> and
> to the left when my x-position is positive. What I actually see is that the
> perspective of the axis-cross does not change.
> What could I have messed up in the configuration that would cause this?
>

is it possible for you to share a movie?

>
>  - When moving a Slice-plane using the tracker
> (SliceOrigin,SliceOrientation),
> the displayed slice plane is not updated. I can see that the plane was
> moved
> on the client window, but the actual slice is not affected. I have to move
> the
> plane a little with the mouse to trigger an update of the slice.
>

Seems like a bug. We recently updated the slice style. Hopefully soon we
will be pushing this branch to master.

>
>  - Grabbing an object only affects the object in the client window, not the
> server view.
> When the Grab tool is connected to an object, I can move that object
> around,
> but I only see this in the client window. On the server side, things are
> totally unaffected by the changes. (I didn't test this one again with the
> new
> git master, so excuse me if it has been fixed since 3.14.1)
>

I see. This particular style is not tested well and was intended for the
testing purposes.

>
> 3) Loose ends
> I didn't find anything I can do with an analog input. Do I have to enable
> some
> special build option to enable those?
>

It depends on the style. If a style needs an analog input, it will use it
if configured correctly. Currently we don't have any interactor style that
uses any analog input. if you do have such requirement, we could help you
write one.

Thanks for your valuable feedback.

Best,



>
> Cheers,
>   Johannes
>
>
> Am 24.10.2012, 17:01:37 schrieb Aashish Chaudhary:
> > Hi Johannes,
> >
> > Very recently, we have improved the VR API and related tools and now
> > the VR plugin comes with a GUI to configure connection managers and
> > interactor styles.
> >
> > The way it works now is that you create a connection manager (lines
> > 475 - 483), which will be generated by the GUI if used, and then for
> > the styles,
> > you would link it with the ID of the proxy and its specific property
> > that you want to control. Now said that the GUI shows you the name of
> > the proxy and not the ID
> > for obvious reasons. Then depending upon the type of the proxy and
> > property you specify a particular input from a HCI device. Currently
> > we support analog, button, and tracker.
> >
> > The wiki here is bit old:
> > http://www.paraview.org/Wiki/ParaView/Users_Guide/CAVE_Display
> > We wrote a source article as well:
> > http://www.kitware.com/source/home/post/66
> >
> > This recent work is not in master yet (hopefully this Friday) but you
> > can checkout this branch: vtk_vr_improvements_new_gui
> > if you want to from paraview stage repository. The branch contains
> > bunch of bug fixes, and API improvements.
> >
> > 475   
> > 476 
> > 477   
> > 478   
> > 479   
> > 480   
> > 481   
> > 482 
> > 483   
> > 484   
> > 485  > property="EyeTransformMatrix">
> > 486   
> > 487 
> > 488  > property="ModelTransformMatrix">
> > 489   
> > 490

Re: [Paraview] Using VR-Style input devices

2012-11-07 Thread Johannes Zarl 
Am 05.11.2012, 23:55:58 schrieb Aashish Chaudhary:
> >  - It would be nice if the grab tool would work globally, more like the
> > 
> > mouse,
> > and not have to be connected to a specific object.
> 
> I am not so sure what you are saying here, because currently the grab style
> just works on the scene and not on a particular object. Current we don't
> perform intersection but you could extend the style to do so.

Maybe I just used it wrongly. you mean that the grab style should be attached 
to a renderview property? What I did is to attach the Grab style to a source 
(e.g. Box0.Center). Therefore I assumed  that it would only affect that object.


> > 2) Display issues:
> >  - In a curved screen setup powered by 3 overlapping projectors, the
> > 
> > perspective seems to be incorrect:
> > This can be most easily observed when you move your head past the
> > coordinate
> > system origin. What I would expect to see is that the z-axis (pointing
> > out of
> > the screen) points somewhat to the right when my x-position is negative,
> > and
> > to the left when my x-position is positive. What I actually see is that
> > the perspective of the axis-cross does not change.
> > What could I have messed up in the configuration that would cause this?
> 
> is it possible for you to share a movie?

I'll do that.

> >  - When moving a Slice-plane using the tracker
> > 
> > (SliceOrigin,SliceOrientation),
> > the displayed slice plane is not updated. I can see that the plane was
> > moved
> > on the client window, but the actual slice is not affected. I have to
> > move the
> > plane a little with the mouse to trigger an update of the slice.
> 
> Seems like a bug. We recently updated the slice style. Hopefully soon we
> will be pushing this branch to master.

Ok. So I'll stick with the master branch...

> >  - Grabbing an object only affects the object in the client window, not
> >  the server view.
> > When the Grab tool is connected to an object, I can move that object
> > around,
> > but I only see this in the client window. On the server side, things are
> > totally unaffected by the changes. (I didn't test this one again with the
> > new
> > git master, so excuse me if it has been fixed since 3.14.1)
> 
> I see. This particular style is not tested well and was intended for the
> testing purposes.

Ah ok. Then I'll focus on the other styles for now, Manipulating a slice is 
more important for the moment, anyways.

> > 3) Loose ends
> > I didn't find anything I can do with an analog input. Do I have to enable
> > some
> > special build option to enable those?
> 
> It depends on the style. If a style needs an analog input, it will use it
> if configured correctly. Currently we don't have any interactor style that
> uses any analog input. if you do have such requirement, we could help you
> write one.

Changing some analog value (like the opacity of an object) or rotating an 
object using a joystick would be great, but I'll come back to you if we really 
need it.

Cheers,
  Johannes
___
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

Re: [Paraview] Using VR-Style input devices

2012-11-12 Thread Johannes Zarl 
Am 07.11.2012, 14:06:59 schrieb Johannes Zarl:
> Am 05.11.2012, 23:55:58 schrieb Aashish Chaudhary:
> > > 2) Display issues:
> > >  - In a curved screen setup powered by 3 overlapping projectors, the
> > > 
> > > perspective seems to be incorrect:
> > > This can be most easily observed when you move your head past the
> > > coordinate
> > > system origin. What I would expect to see is that the z-axis (pointing
> > > out of
> > > the screen) points somewhat to the right when my x-position is
> > > negative, and
> > > to the left when my x-position is positive. What I actually see is that
> > > the perspective of the axis-cross does not change.
> > > What could I have messed up in the configuration that would cause this?
> > 
> > is it possible for you to share a movie?
> 
> I'll do that.

Ok, the problem with the wrong perspective was on my side. I simply got my 
rotation matrix wrong...

Cheers,
  Johannes
___
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

Re: [Paraview] Using VR-Style input devices

2012-11-12 Thread Aashish Chaudhary 
>
> Ok, the problem with the wrong perspective was on my side. I simply got my
> rotation matrix wrong...
>

Great.. good to know. Also, we have branch that has some fixes which make
the grab style work nicely for most of the scenarios. Hopefully this week
or next week we will have that merged into master. There is another branch
from Cory (thanks!) that fixes a crash at initialization that I just
approved.

Thanks





>
> Cheers,
>   Johannes
> ___
> 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
>



-- 
| Aashish Chaudhary
| R&D Engineer
| Kitware Inc.
| www.kitware.com
___
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

Re: [Paraview] Using VR-Style input devices

2012-11-13 Thread Christian Richter 

Hi Aashish,

I'm very interested in getting this to work, please point me to the 
right place in the code.


Do you know why the Paraview-own VTK does not support Tdx and does not 
use it ? (the option is there in the cmake but than something is 
missing, because it does not ask for VTK_TDX_INCLUDE_PATH and that's why 
I think compilation breaks)

http://www.vtk.org/Wiki/VTK/3DConnexion_Devices_Support

I was able to get the TDx TestApp to work with an extern build of VTK 
and hoped it would be straightforward to use ist in Paraview -- but i 
gave up at this point.


Thank you,
Christian

Am 12.11.2012 18:25, schrieb Aashish Chaudhary:

Hi Christian,

I've found out that the device acts as an analog-input (seen with
vrpn_print_devices).

Could you please tell me how to write a style to use the
analog-input (6DOF) to manipulate the camera view ?


Sorry for the late reply. We have been busy with the SuperComputing 
demo. Its really simple, you get the input from the analog devices (it 
may not be normalized), and then you calculate the delta from the last 
time you got any event and use this delta however you would like. 
Basically the math to rotate the camera is dependent on what camera 
type you would like to have. As far as getting access to camera and 
setting up the camera positions, I can point you to the code for that.


Please let me know.



___
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

Re: [Paraview] Using VR-Style input devices, analog input from 3Dconnexion device

2012-12-20 Thread Christian Richter 

Hi Aashish,

this week I've written a new Interactor style to use a 3dconnexion 
SpaceNavigator in Paraview with vrpn server. Translational motion works 
fine in parallel and orthogonal projection but rotation is not finished yet.


Two things I did not solve:
- the first time a new Interaction is created, PV crashes when the point 
vtkVRQueue:Enqueue, this->Mutex->Lock() is reached (called by 
newAnalogValue), if I use "Restore State" it works -> I think anything 
has to be initialized but did not find it.
- rotation of the scene is confusing to me. I have as input 3 analog 
values (roll/pitch/yaw) between -1 and +1. I tried to map this to 
CameraViewUp with euler-zyx-Transformation. But it does not work as 
expected.


Question at all: what would be the best way to map a scalar value to the 
rotation of a scene/view ? What does the buttons roll/pitch/yaw in the 
camera-property-menue ? I think I would need exact the same functions 
behind theses 3 buttons.


Here is the code-snippet I tried for that:

vtkSMPropertyHelper( proxy, "CameraViewUp" ).Get( rot, 3 ); //rotation
phi= data.data.analog.channel[3]*M_PI/180;
theta= data.data.analog.channel[4]*M_PI/180;
psi= data.data.analog.channel[5]*M_PI/180;

 double x=rot[0];
 double y=rot[1];
 double z=rot[2];

 double tt[3][3];
 tt[0][0]=cos(theta)*cos(psi);
 tt[0][1]=-cos(phi)*sin(psi)+sin(phi)*sin(theta)*cos(psi);
 tt[0][2]=sin(phi)*sin(psi)+cos(phi)*sin(theta)*cos(psi);

 tt[1][0]=cos(theta)*sin(psi);
 tt[1][1]=cos(phi)*cos(psi)+sin(phi)*sin(theta)*cos(psi);
 tt[1][2]=-sin(phi)*cos(psi)+cos(phi)*sin(theta)*sin(psi);

 tt[2][0]=-sin(theta);
 tt[2][1]=sin(phi)*cos(theta);
 tt[2][2]=cos(phi)*cos(theta);

 rot[0] = x*tt[0][0]+y*tt[0][1]+z*tt[0][2];
 rot[1] = x*tt[1][0]+y*tt[1][1]+z*tt[1][2];
 rot[2] = x*tt[2][0]+y*tt[2][1]+z*tt[2][2];

 vtkSMPropertyHelper( proxy, "CameraViewUp" ).Set( rot, 3 );

I attached the sourcecode, maybe someone has time over christmas to have 
a look.


Have a nice Christmas time & happy new year,
Christian

Am 30.11.2012 03:42, schrieb Aashish Chaudhary:

Hi Christian,

Are you still interested? if yes, let me know and I can provide you 
more help.


Thanks,


On Tue, Nov 6, 2012 at 11:34 AM, Christian Richter 
mailto:christian.rich...@ovgu.de>> wrote:


ell me how to write a styl




--
| Aashish Chaudhary
| R&D Engineer
| Kitware Inc.
| www.kitware.com 




vtkVRControlChangeCameraPositionStyle.tar.gz
Description: GNU Zip compressed data
___
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

Re: [Paraview] Using VR-Style input devices, analog input from 3Dconnexion device

2012-12-20 Thread Cory Quammen 
Christian,

It seems we have a common interest in adding support for the
SpaceNavigator to ParaView. I wrote a style for just this purpose and
posted it on gerrit:

http://review.source.kitware.com/#/t/1646/

This style rotates and translates the world and not individual objects.

I think my topic addresses both of your unresolved issues. Would you
care to checkout out this topic and try it out?

Thank you,
Cory

On Thu, Dec 20, 2012 at 11:32 AM, Christian Richter
 wrote:
> Hi Aashish,
>
> this week I've written a new Interactor style to use a 3dconnexion
> SpaceNavigator in Paraview with vrpn server. Translational motion works fine
> in parallel and orthogonal projection but rotation is not finished yet.
>
> Two things I did not solve:
> - the first time a new Interaction is created, PV crashes when the point
> vtkVRQueue:Enqueue, this->Mutex->Lock() is reached (called by
> newAnalogValue), if I use "Restore State" it works -> I think anything has
> to be initialized but did not find it.
> - rotation of the scene is confusing to me. I have as input 3 analog values
> (roll/pitch/yaw) between -1 and +1. I tried to map this to CameraViewUp with
> euler-zyx-Transformation. But it does not work as expected.
>
> Question at all: what would be the best way to map a scalar value to the
> rotation of a scene/view ? What does the buttons roll/pitch/yaw in the
> camera-property-menue ? I think I would need exact the same functions behind
> theses 3 buttons.
>
> Here is the code-snippet I tried for that:
>
> vtkSMPropertyHelper( proxy, "CameraViewUp" ).Get( rot, 3 ); //rotation
> phi= data.data.analog.channel[3]*M_PI/180;
> theta= data.data.analog.channel[4]*M_PI/180;
> psi= data.data.analog.channel[5]*M_PI/180;
>
>  double x=rot[0];
>  double y=rot[1];
>  double z=rot[2];
>
>  double tt[3][3];
>  tt[0][0]=cos(theta)*cos(psi);
>  tt[0][1]=-cos(phi)*sin(psi)+sin(phi)*sin(theta)*cos(psi);
>  tt[0][2]=sin(phi)*sin(psi)+cos(phi)*sin(theta)*cos(psi);
>
>  tt[1][0]=cos(theta)*sin(psi);
>  tt[1][1]=cos(phi)*cos(psi)+sin(phi)*sin(theta)*cos(psi);
>  tt[1][2]=-sin(phi)*cos(psi)+cos(phi)*sin(theta)*sin(psi);
>
>  tt[2][0]=-sin(theta);
>  tt[2][1]=sin(phi)*cos(theta);
>  tt[2][2]=cos(phi)*cos(theta);
>
>  rot[0] = x*tt[0][0]+y*tt[0][1]+z*tt[0][2];
>  rot[1] = x*tt[1][0]+y*tt[1][1]+z*tt[1][2];
>  rot[2] = x*tt[2][0]+y*tt[2][1]+z*tt[2][2];
>
>  vtkSMPropertyHelper( proxy, "CameraViewUp" ).Set( rot, 3 );
>
> I attached the sourcecode, maybe someone has time over christmas to have a
> look.
>
> Have a nice Christmas time & happy new year,
> Christian
>
> Am 30.11.2012 03:42, schrieb Aashish Chaudhary:
>
> Hi Christian,
>
> Are you still interested? if yes, let me know and I can provide you more
> help.
>
> Thanks,
>
>
> On Tue, Nov 6, 2012 at 11:34 AM, Christian Richter
>  wrote:
>>
>> ell me how to write a styl
>
>
>
>
> --
> | Aashish Chaudhary
> | R&D Engineer
> | Kitware Inc.
> | www.kitware.com
>
>
>
> ___
> 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
>



-- 
Cory Quammen
Research Associate
Department of Computer Science
The University of North Carolina at Chapel Hill
___
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

Re: [Paraview] Using VR-Style input devices, analog input from 3Dconnexion device

2012-12-20 Thread Christian Richter 

Hi Cory,

thats awesome, thank you so much for sharing this.

I would suggest the following change in HandleAnalog to support  
parallel-projection deph-scaling because moving in Z-Direction has no  
effect:


int mode = camera->GetParallelProjection();
if (mode) {
	//in case of parallel projection: moving in deph-direction has no  
effect, so needs scaling

pscale = camera->GetParallelScale();
pscale += 0.05*channel[1];
camera->SetParallelScale( pscale );
}

However, the segfault remains at Enqueue for the first time a Style is  
arranged via the GUI Panel:
(if you load a state file it works and becaue I only want to set up  
the Interactor Pipeline once and start with a state file it is not a  
big problem)


Core was generated by  
`/home/dem/playground/ParaView/build/bin/paraview --use-old-panels'.

Program terminated with signal 11, Segmentation fault.
#0  0x7f404cbeac56 in vtkVRQueue::Enqueue(vtkVREventData const&)  
() from /home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so

(gdb) bt
#0  0x7f404cbeac56 in vtkVRQueue::Enqueue(vtkVREventData const&)  
() from /home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so
#1  0x7f404cbe165a in  
pqVRPNConnection::newAnalogValue(_vrpn_ANALOGCB) () from  
/home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so
#2  0x7f404cbf1347 in  
vrpn_Callback_List<_vrpn_ANALOGCB>::call_handlers(_vrpn_ANALOGCB  
const&) () from  
/home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so
#3  0x7f404cbf0c7d in  
vrpn_Analog_Remote::handle_change_message(void*, vrpn_HANDLERPARAM) ()  
from /home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so
#4  0x7f404cbf7fbc in vrpn_TypeDispatcher::doCallbacksFor(int,  
int, timeval, unsigned int, char const*) () from  
/home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so
#5  0x7f404cbfe1cf in vrpn_Endpoint::dispatch(int, int, timeval,  
unsigned int, char*) () from  
/home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so
#6  0x7f404cbfe110 in vrpn_Endpoint_IP::getOneUDPMessage(char*,  
int) () from  
/home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so
#7  0x7f404cbfca8e in  
vrpn_Endpoint_IP::handle_udp_messages(timeval const*) () from  
/home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so
#8  0x7f404cbfb663 in vrpn_Endpoint_IP::mainloop(timeval*) () from  
/home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so
#9  0x7f404cc019a7 in vrpn_Connection_IP::mainloop(timeval const*)  
() from /home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so
#10 0x7f404cbf5aeb in vrpn_Button_Remote::mainloop() () from  
/home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so
#11 0x7f404cbdb38a in pqVRPNConnection::run() () from  
/home/dem/playground/ParaView/build/bin/../lib//libVRPlugin.so


Thank you,
best wishes,
Christian


___
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

Re: [Paraview] Using VR-Style input devices, analog input from 3Dconnexion device

2012-12-21 Thread Aashish Chaudhary 
Hi Christian,

Sorry for the late reply. Not directly answering your question, but would
like to inform you that we (Mostly Dave and some me) recently made
improvements to the VR Plugin and now its merged back into master.

(13598-VRGrabWorldFix in master now)

I am wondering if you would like to update / test your code against today's
master. If you have some specific questions, we should be able to help.

Thanks,


On Fri, Dec 21, 2012 at 2:38 AM, Christian Richter <
christian.rich...@ovgu.de> wrote:

> Hi Cory,
>
> thats awesome, thank you so much for sharing this.
>
> I would suggest the following change in HandleAnalog to support
> parallel-projection deph-scaling because moving in Z-Direction has no
> effect:
>
> int mode = camera->GetParallelProjection(**);
> if (mode) {
> //in case of parallel projection: moving in deph-direction has no
> effect, so needs scaling
> pscale = camera->GetParallelScale();
> pscale += 0.05*channel[1];
> camera->SetParallelScale( pscale );
> }
>
> However, the segfault remains at Enqueue for the first time a Style is
> arranged via the GUI Panel:
> (if you load a state file it works and becaue I only want to set up the
> Interactor Pipeline once and start with a state file it is not a big
> problem)
>
> Core was generated by `/home/dem/playground/**ParaView/build/bin/paraview
> --use-old-panels'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x7f404cbeac56 in vtkVRQueue::Enqueue(**vtkVREventData const&) ()
> from /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
> (gdb) bt
> #0  0x7f404cbeac56 in vtkVRQueue::Enqueue(**vtkVREventData const&) ()
> from /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
> #1  0x7f404cbe165a in pqVRPNConnection::**newAnalogValue(_vrpn_ANALOGCB)
> () from /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
> #2  0x7f404cbf1347 in vrpn_Callback_List<_vrpn_**
> ANALOGCB>::call_handlers(_**vrpn_ANALOGCB const&) () from
> /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
> #3  0x7f404cbf0c7d in vrpn_Analog_Remote::handle_**change_message(void*,
> vrpn_HANDLERPARAM) () from /home/dem/playground/ParaView/**
> build/bin/../lib//libVRPlugin.**so
> #4  0x7f404cbf7fbc in vrpn_TypeDispatcher::**doCallbacksFor(int, int,
> timeval, unsigned int, char const*) () from /home/dem/playground/ParaView/
> **build/bin/../lib//libVRPlugin.**so
> #5  0x7f404cbfe1cf in vrpn_Endpoint::dispatch(int, int, timeval,
> unsigned int, char*) () from /home/dem/playground/ParaView/**
> build/bin/../lib//libVRPlugin.**so
> #6  0x7f404cbfe110 in vrpn_Endpoint_IP::**getOneUDPMessage(char*,
> int) () from /home/dem/playground/ParaView/**
> build/bin/../lib//libVRPlugin.**so
> #7  0x7f404cbfca8e in vrpn_Endpoint_IP::handle_udp_**messages(timeval
> const*) () from /home/dem/playground/ParaView/**
> build/bin/../lib//libVRPlugin.**so
> #8  0x7f404cbfb663 in vrpn_Endpoint_IP::mainloop(**timeval*) () from
> /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
> #9  0x7f404cc019a7 in vrpn_Connection_IP::mainloop(**timeval const*)
> () from /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
> #10 0x7f404cbf5aeb in vrpn_Button_Remote::mainloop() () from
> /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
> #11 0x7f404cbdb38a in pqVRPNConnection::run() () from
> /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
>
> Thank you,
> best wishes,
> Christian
>
>
>
> __**_
> 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
>



-- 
| Aashish Chaudhary
| R&D Engineer
| Kitware Inc.
| www.kitware.com
___
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

Re: [Paraview] Using VR-Style input devices, analog input from 3Dconnexion device

2012-12-21 Thread Pat Marion 
Hi,

I'm not sure if this is relevant to your discussion, but I just wanted to
make sure you guys are aware of this class in VTK:

http://www.vtk.org/doc/nightly/html/classvtkTDxInteractorStyle.html


Pat

On Sat, Dec 22, 2012 at 4:38 AM, Aashish Chaudhary <
aashish.chaudh...@kitware.com> wrote:

> Hi Christian,
>
> Sorry for the late reply. Not directly answering your question, but would
> like to inform you that we (Mostly Dave and some me) recently made
> improvements to the VR Plugin and now its merged back into master.
>
> (13598-VRGrabWorldFix in master now)
>
> I am wondering if you would like to update / test your code against
> today's master. If you have some specific questions, we should be able to
> help.
>
> Thanks,
>
>
> On Fri, Dec 21, 2012 at 2:38 AM, Christian Richter <
> christian.rich...@ovgu.de> wrote:
>
>> Hi Cory,
>>
>> thats awesome, thank you so much for sharing this.
>>
>> I would suggest the following change in HandleAnalog to support
>> parallel-projection deph-scaling because moving in Z-Direction has no
>> effect:
>>
>> int mode = camera->GetParallelProjection(**);
>> if (mode) {
>> //in case of parallel projection: moving in deph-direction has no
>> effect, so needs scaling
>> pscale = camera->GetParallelScale();
>> pscale += 0.05*channel[1];
>> camera->SetParallelScale( pscale );
>> }
>>
>> However, the segfault remains at Enqueue for the first time a Style is
>> arranged via the GUI Panel:
>> (if you load a state file it works and becaue I only want to set up the
>> Interactor Pipeline once and start with a state file it is not a big
>> problem)
>>
>> Core was generated by `/home/dem/playground/**ParaView/build/bin/paraview
>> --use-old-panels'.
>> Program terminated with signal 11, Segmentation fault.
>> #0  0x7f404cbeac56 in vtkVRQueue::Enqueue(**vtkVREventData const&)
>> () from /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**
>> so
>> (gdb) bt
>> #0  0x7f404cbeac56 in vtkVRQueue::Enqueue(**vtkVREventData const&)
>> () from /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**
>> so
>> #1  0x7f404cbe165a in pqVRPNConnection::**newAnalogValue(_vrpn_ANALOGCB)
>> () from /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**
>> so
>> #2  0x7f404cbf1347 in vrpn_Callback_List<_vrpn_**
>> ANALOGCB>::call_handlers(_**vrpn_ANALOGCB const&) () from
>> /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
>> #3  0x7f404cbf0c7d in vrpn_Analog_Remote::handle_**change_message(void*,
>> vrpn_HANDLERPARAM) () from /home/dem/playground/ParaView/**
>> build/bin/../lib//libVRPlugin.**so
>> #4  0x7f404cbf7fbc in vrpn_TypeDispatcher::**doCallbacksFor(int,
>> int, timeval, unsigned int, char const*) () from
>> /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
>> #5  0x7f404cbfe1cf in vrpn_Endpoint::dispatch(int, int, timeval,
>> unsigned int, char*) () from /home/dem/playground/ParaView/**
>> build/bin/../lib//libVRPlugin.**so
>> #6  0x7f404cbfe110 in vrpn_Endpoint_IP::**getOneUDPMessage(char*,
>> int) () from /home/dem/playground/ParaView/**
>> build/bin/../lib//libVRPlugin.**so
>> #7  0x7f404cbfca8e in vrpn_Endpoint_IP::handle_udp_**messages(timeval
>> const*) () from /home/dem/playground/ParaView/**
>> build/bin/../lib//libVRPlugin.**so
>> #8  0x7f404cbfb663 in vrpn_Endpoint_IP::mainloop(**timeval*) () from
>> /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
>> #9  0x7f404cc019a7 in vrpn_Connection_IP::mainloop(**timeval const*)
>> () from /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**
>> so
>> #10 0x7f404cbf5aeb in vrpn_Button_Remote::mainloop() () from
>> /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
>> #11 0x7f404cbdb38a in pqVRPNConnection::run() () from
>> /home/dem/playground/ParaView/**build/bin/../lib//libVRPlugin.**so
>>
>> Thank you,
>> best wishes,
>> Christian
>>
>>
>>
>> __**_
>> 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
>>
>
>
>
> --
> | Aashish Chaudhary
> | R&D Engineer
> | Kitware Inc.
> | www.kitware.com
>
> ___
> 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
>
>
__