Re: [Paraview] Unexpected lines in Surface with Edges mode with PV 3.14

2012-03-13 Thread Richard GRENON

Hello.

In addition to my previous mail, I discovered that this problem of 
unexpected lines in Surface with Edges mode with PV 3.14 concerns only 
the Linux version ! I am using the 64 bits version on Linux CentOS 5.7.


The Surface with Edges view is correct with PV 3.14 Windows 32 bits on 
Vista Home Premium SP2 !


If it may help you, the problem on the Linux version does not come from 
the Tecplot file format: I have also problems with surfaces given in VTM 
format.


I add the gzip of my Tecplot test file that contains the surface 
representation of a wake behind a wing.


Best regards.

Richard.

Richard GRENON a écrit :

Hello, all.

I have found a strange behavior of PV 3.14 in Surface with Edges 
mode for some surfaces: when reading some Tecplot files that contained 
a structured mesh, I get some unexpected lines that don't exist in the 
file and that don't appear when I select the Wireframe mode. The 
Wireframe view is correct, the Surface with Edges view is not.



--
Richard GRENON
ONERA
Departement d'Aerodynamique Appliquee - DAAP/ACI
8 rue des Vertugadins
92190 MEUDON - FRANCE
phone : +33 1 46 73 42 17
fax   : +33 1 46 73 41 46
mailto:richard.gre...@onera.fr
http://www.onera.fr



wake.tp.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] VRPN Problem

2012-03-13 Thread Christian Wohlschlager
** Reply Requested When Convenient **


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)  
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. 

mfg 

christian


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



 Nikhil Shetty nikhil.she...@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.wohlschla...@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.she...@kitware.com 3/9/2012 4:52 PM 
Hi Christian, 





On Fri, Mar 9, 2012 at 2:01 AM, Christian Wohlschlager
christian.wohlschla...@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@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.she...@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

Re: [Paraview] VRPN Problem

2012-03-13 Thread Nikhil Shetty
Hi Christian,

On Tue, Mar 13, 2012 at 9:32 AM, Christian Wohlschlager 
christian.wohlschla...@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.she...@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.wohlschla...@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.she...@kitware.com 3/9/2012 4:52 PM 
 Hi Christian,



   On Fri, Mar 9, 2012 at 2:01 AM, Christian Wohlschlager 
 christian.wohlschla...@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*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@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 

Re: [Paraview] [EXTERNAL] Paraview can't show grads origin data

2012-03-13 Thread Moreland, Kenneth
OK.  I see now.  Clearly I'm not familiar with the GrADS software or its
data formats.  If someone else on the ParaView mailing list is familiar
with GrADS it would be great if they speak up, but according to the mail
archives GrADS has not yet been discussed.


I suspect the problem is that ParaView simply does not know how to read
the type of netCDF files written by GrADS.  NetCDF is not a completely
specified file format.  Rather, it is a collection of arrays that are
self describing.  That is, the arrays and dimensions are named and can
have properties, but to read them properly you really have to understand
what these metadata mean.

There are actually several readers in ParaView that use netCDF as the
underlying technology, but only one that makes an attempt to generally
read unknown conventions.  It will assume that arrays are regular grids
with up to three physical dimensions (x/y/z or lat/lon/z) and optionally a
time dimension.  Based on about 5 minutes looking at the GrADS web pages,
I'm guessing that the netCDF file GrADS is outputting contains 5
dimensional arrays.  In this case, the ParaView reader won't know what to
do with 5 dimensions and will therefore issue an error if you try to read
one.  (You never actually said what went wrong, but perhaps that is it.)

I'm sorry that probably none of this is helping.  Ultimately, it sounds
like a new reader would have to be created for ParaView.

-Ken

On 3/13/12 2:28 AM, wang w...@knmi.nl wrote:

Thanks for your reply.

Grads is a software package that widely used by meteorological societies
  worldwide. http://www.iges.org/grads/.
The nc file I get can  be shown by ferret (which is also a software
package
used by earth science communities) and Grads (Grads can read binary and
data).

The problem may occurred by conversion...

Xueli

Moreland, Kenneth wrote:
 I don't know what you mean by a grad or what problem it is causing, so
 I'm going to make a total guess.  I am guessing that you mean gradian (a
 unit equal to 9/10 of a degree).  Furthermore, because I can't think of
 any other way such units would mess you up, I am guessing that you are
 trying to write spherical coordinates in terms of gradians, but ParaView
 is interpreting them either as degrees or as Cartesian coordinates.


 Assuming that this is the problem, it is caused by the fact that the
 default netCDF reader for ParaView honors the CF convention
 (http://cf-pcmdi.llnl.gov), and the CF convention specifies spherical
 coordinates in terms of degrees.  To specify angles in any other units
is
 to break the convention.

 Your best solution is to convert your gradians to degrees (it's OK to
have
 floating-point degrees) and write a netCDF file that properly follows
the
 CF convention.

 If I have completely missed the point of your question, you'll have to
 better explain what are grads and what problem you are having with them.

 -Ken

 On 3/12/12 10:13 AM, wangw...@knmi.nl  wrote:


 Dear Paraview users,

 I have problem with data that origin of grads. We have a program to
 convert grads data into NetCDF format. But this data can not be shown
in
 Paraview. I don't have any problem to show normal nc data.

 Have you ever experience the same problem?

 Thanks!
 Xueli
 ___
 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

  






___
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


[Paraview] vtkReconstructionSurfaceFilter

2012-03-13 Thread Aurélien Marsan
Dear Paraview users and developers,

I would like to use the *vtkReconstructionFilter* inside of the python
shell in order to generate a surface from a vtkPointsSet.
But I do not find this class.

Is it not available within the vtk version embeeded with the paraview 3.14
binary release ?

Thanks,

A.Marsan
___
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] vtkReconstructionSurfaceFilter

2012-03-13 Thread Pat Marion
If you mean the vtkSurfaceReconstructionFilter, you have to import the
imaging module:

from paraview.vtk.imaging import vtkSurfaceReconstructionFilter


Pat

2012/3/13 Aurélien Marsan aur.mar...@gmail.com

 Dear Paraview users and developers,

 I would like to use the *vtkReconstructionFilter* inside of the python
 shell in order to generate a surface from a vtkPointsSet.
 But I do not find this class.

 Is it not available within the vtk version embeeded with the paraview 3.14
 binary release ?

 Thanks,

 A.Marsan

 ___
 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


___
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] vtkReconstructionSurfaceFilter

2012-03-13 Thread Aurélien Marsan
Yes that is what I was looking for !
Thanks for your quick answer.

Aurélien

Le 13 mars 2012 22:11, Pat Marion pat.mar...@kitware.com a écrit :

 If you mean the vtkSurfaceReconstructionFilter, you have to import the
 imaging module:

 from paraview.vtk.imaging import vtkSurfaceReconstructionFilter


 Pat

 2012/3/13 Aurélien Marsan aur.mar...@gmail.com

 Dear Paraview users and developers,

 I would like to use the *vtkReconstructionFilter* inside of the python
 shell in order to generate a surface from a vtkPointsSet.
 But I do not find this class.

 Is it not available within the vtk version embeeded with the paraview
 3.14 binary release ?

 Thanks,

 A.Marsan

 ___
 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



___
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


[Paraview] 2d selections

2012-03-13 Thread Scott, W Alan
I have selected some of the points in a 2d view (plot over line), and have no 
idea how to unselect these points.  How can I unselect points in a 2d plot?

Thanks,

Alan


W. Alan Scott
ParaView Support Manager

GAITS
Sandia National Laboratories, MS 0822
Org 9326 - Building 880 A1-C
(505) 284-0932   FAX (505) 284-5619
-



___
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] [EXTERNAL] 2d selections

2012-03-13 Thread Moreland, Kenneth
I see that if you make a second selection in the same 2d plot, the old points 
are unselected and the new points are selected.  But if you try to select 
nothing, nothing changes.  I would think that the current selection would be 
cleared out, so this sounds like a bug.

I also notice that if I go to a different view and select a different object, 
the old selection in the 2d plot remains.  I believe all the selections are 
supposed to be linked together, so this sounds like a different bug.

-Ken

From: Scott, W Alan wasc...@sandia.govmailto:wasc...@sandia.gov
Date: Tue, 13 Mar 2012 23:50:02 +
To: paraview@paraview.orgmailto:paraview@paraview.org 
paraview@paraview.orgmailto:paraview@paraview.org
Subject: [EXTERNAL] [Paraview] 2d selections

I have selected some of the points in a 2d view (plot over line), and have no 
idea how to unselect these points.  How can I unselect points in a 2d plot?

Thanks,

Alan


W. Alan Scott
ParaView Support Manager

GAITS
Sandia National Laboratories, MS 0822
Org 9326 - Building 880 A1-C
(505) 284-0932   FAX (505) 284-5619
-



___ 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
___
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


[Paraview] Mac OS X 10.7.3 install failures

2012-03-13 Thread Chris Kees
Hi,

The stuff (paraview.app etc.)  in my build tree works but 'make
install' fails in part because it's trying to install the vtk python
module in

$PREFIX/bin/Python

which is a link to
$PREFIX/Library/Frameworks/Python.framework/Versions/2.7/bin/python
(mac OS is partially blind to case)

If I manually change the install location to something else like
$PREFIX/paraview-vtk-stuff, then things get further but verify_app
still fails. Does this look familiar to anybody?

Chris
___
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