[Paraview] Rendering problem with the Streamline Representation plugin

2017-09-12 Thread Wilhelm Lionel
Dear Paraviewers, I found sevral rendering issues in the Streamline Representation plugin. In order the issue to be reproducible, I followed the "How to test ?" section on this page https://blog.kitware.com/new-animated-stream-lines-representation-for-paraview-5-3/. In order to see what I'm

Re: [Paraview] SelectInputVector attribute in the SurfaceLIC plugin

2017-09-12 Thread Wilhelm Lionel
Works like a charm, thanks a lot ! Lionel De : Utkarsh Ayachit <utkarsh.ayac...@kitware.com> Envoyé : lundi 11 septembre 2017 18:23 À : Wilhelm Lionel Cc : Paraview@paraview.org Objet : Re: [Paraview] SelectInputVector attribute in the SurfaceLIC

Re: [Paraview] SelectInputVector attribute in the SurfaceLIC plugin

2017-09-11 Thread Wilhelm Lionel
.SMProxy.GetProperty('SelectInputVectors').SetElement(0,['POINTS', 'vitesse']) but it still does not work... Thanks in advance, Lionel De : Utkarsh Ayachit <utkarsh.ayac...@kitware.com> Envoyé : lundi 11 septembre 2017 16:43 À : Wilhelm Lionel Cc : Pa

[Paraview] SelectInputVector attribute in the SurfaceLIC plugin

2017-09-11 Thread Wilhelm Lionel
Dear Paraviewers, I'm trying to use the SurfaceLIC plugin in a script intended to be executed by pvbatch. Naturally, I used the trace tool in the GUI to design my python script. When save the state in python and try to run it with pvbatch it raises the following error :

Re: [Paraview] Screenshot resolution and 2D actors size

2017-08-09 Thread Wilhelm Lionel
De : Cory Quammen <cory.quam...@kitware.com> Envoyé : mardi 8 août 2017 20:44 À : Wilhelm Lionel Cc : Paraview@paraview.org Objet : Re: [Paraview] Screenshot resolution and 2D actors size > Regarding the pvbatch issue, do you have any hint? That is odd. I'm not

Re: [Paraview] Screenshot resolution and 2D actors size

2017-08-08 Thread Wilhelm Lionel
: Wilhelm Lionel Cc : paraview@paraview.org Objet : Re: [Paraview] Screenshot resolution and 2D actors size Hi Lionel, This is a bug [1] that will be fixed in ParaView 5.4.1, coming out in the next week or so. In fact, it is fixed in the latest 5.4.1 release candidate, which you can get from