Re: [Paraview] pvpython script fails on Paraview 5.0.1

[Utkarsh Ayachit]

Bishwajit,

Just remove the "SetScaleArray" invocation from your script to over
this issue. I suspect you're building the GUI with
VTK_RENDERING_BACKEND cmake variable set to OpenGL2, while with 5.0.1,
it may be defaulting to OpenGL, as a result your Mesa build is using
legacy OpenGL backend. This is causing mismatch in available
parameters of the representations.

Utkarsh

On Mon, Apr 3, 2017 at 9:37 PM, Bishwajit Dutta  wrote:
>
> Dear
> All,
>
> I have compiled Paraview 5.0.1 on ubuntu with mesa libs to run it on CPU.
> Also I generated a simple pvpython script from Paraview 5.0.1 GUI on my
> windows machine (attached) and the script runs fine there.
> However this script fails with my mesa compiled pvpython.
>
> =error logs===
> Traceback (most recent call last):
>   File "cone_clip.py", line 19, in 
> cone1Display.SetScaleArray = [None, '']
>   File
> "/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/lib/site-packages/paraview/servermanager.py",
> line 307, in __setattr__
> "to add this attribute.")
> AttributeError: Attribute SetScaleArray does not exist.  This class does not
> allow addition of new attributes to avoid mistakes due to typos. Use
> add_attribute() if you really want to add this attribute.
> =
>
> I have built the Paraview with the following options (CMakeCache.txt
> attached):
> cmake ../ -DBUILD_TESTING=OFF -DCMAKE_BUILD_TYPE=Release
> -DPARAVIEW_ENABLE_CATALYST=ON -DPARAVIEW_ENABLE_PYTHON=ON
> -DPYTHON_LIBRARY=$PYTHON_LIBRARY -DPYTHON_INCLUDE_DIR=$PYTHON_INCLUDE_DIR
> -DPARAVIEW_USE_MPI=ON -DMPI_HEADER_PATH=$MPI_HEADER_PATH
> -DCMAKE_INSTALL_PREFIX=$BD_INSTALL_PATH -DPARAVIEW_BUILD_QT_GUI=OFF
> -DVTK_USE_X=OFF -DOPENGL_INCLUDE_DIR=$BD_INSTALL_PATH/include
> -DOPENGL_gl_LIBRARY=$BD_INSTALL_PATH/lib/libOSMesa.so
> -DOPENGL_glu_LIBRARY=$BD_INSTALL_PATH/lib/libGLU.so
> -DVTK_OPENGL_HAS_OSMESA=ON -DOSMESA_INCLUDE_DIR=$BD_INSTALL_PATH/include
> -DOSMESA_LIBRARY=$BD_INSTALL_PATH/lib/libOSMesa.so
>
> Do I need to pass some extra parameters while building and if so what are
> they? All my GUI generated scripts seem to fail with similar errors.
>
> Thanks in advance for guidance.
>
> BR,
> Bishwajit (Bish) Dutta
> CpE - Grad Student
> Virginia Tech
>
>
> ___
> 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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Problems with writing VTK in MPI

[Joachim Pouderoux]

Jose,

It looks like the file for time step 50 is incomplete: there is less values
than expected.
See, the files correspond to same mesh, only the "roh" point array is
different but file t50
is more than 6MB smaller than t0 which is not correct as data is written in
binary but not
compressed. So I guess there is a bug in your writing procedure but it is
not possible
to tell more without analysing its source code.

Best regards,


*Joachim Pouderoux*, PhD

*Technical Expert - Scientific Computing Team*
*Kitware SAS *


2017-03-29 16:31 GMT-04:00 José Luis López López <
jlopezfis...@ciencias.unam.mx>:

> Hi! Paraviewers,
>
> We are having problems with the output VTK files when running a Lattice
> Boltzmann simulation in parallel with MPI. I am not sure what could be the
> problem. The thing is that when executing the program in the front end
> there is no problem, however when sending sbatch with 64 processors the
> files most of the time do not write correctly. I am attaching a file and
> maybe you can guide me to solve the issue,
>
> warmly,
> Jose
>
>
> The files have square part that should not be there,
> ​
>  rho1_t.50.vtk
> 
> ​​
>  rho1_t.0.vtk
> 
> ​
>
> ___
> 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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] ParaView 5 Crashes on macOS (Sierra)

[Christopher Neal]

Not sure if it is a general Gmsh reader, but there is a merge request
pending that claims to introduce a reader.

https://gitlab.kitware.com/paraview/paraview/merge_requests/1453



On Mon, Apr 3, 2017 at 3:39 PM, Cory Quammen 
wrote:

> Zach,
>
> Thanks for trying it out! I'm glad to hear it is fixed.
>
> To my knowledge, ParaView does not read Gmsh files directly. Apparently,
> you can save out VTK files from Gmsh that can be read into ParaView:
>
> https://www.cfd-online.com/Forums/openfoam-meshing-open/
> 139538-rendering-gmsh-files-paraview.html
>
> Cory
>
> On Mon, Apr 3, 2017 at 3:27 PM, Zach Davis  wrote:
>
>> Hi Cory,
>>
>> This build works for me.  I don’t have the crashing issue as before.  On
>> a completely unrelated note since I’m replying to the entire mailing list,
>> is there a way to view mesh files in the Gmsh format using ParaView?
>>
>> Best Regards,
>>
>> [image: Pointwise, Inc.]
>> Zach Davis
>> Pointwise®, Inc.
>> Sr. Engineer, Sales & Marketing
>> 213 South Jennings Avenue
>> Fort Worth, TX 76104-1107
>>
>> *E*: zach.da...@pointwise.com
>> *P*: (817) 377-2807 x1202 <(817)%20377-2807>
>> *F*: (817) 377-2799
>>  
>>  
>>
>> On Apr 3, 2017, at 2:07 PM, Cory Quammen 
>> wrote:
>>
>> Zach,
>>
>> Would you mind trying this nightly build of ParaView?
>>
>> http://www.paraview.org/paraview-downloads/download.php?
>> submit=Download=nightly=all=all
>> =ParaView-5.3.0-219-g24f5a44-Qt5-OpenGL2-MPI-OSX10.8-64bit.dmg
>>
>> I recently merged a change that should hopefully fix this crash.
>>
>> Thanks,
>> Cory
>>
>> On Tue, Mar 21, 2017 at 2:09 PM, Cory Quammen 
>> wrote:
>>
>>> Zach,
>>>
>>> Thanks for the information.
>>>
>>> I mounted an SMB volume on my machine and did not get a crash when
>>> opening a file in ParaView 5.3.0. That leaves NFS as causing some unhandled
>>> condition in the code pointed out by your error report.
>>>
>>> I'll file a bug report and investigate for 5.4.0.
>>>
>>> https://gitlab.kitware.com/paraview/paraview/issues/17310
>>>
>>> Thanks,
>>> Cory
>>>
>>> On Tue, Mar 21, 2017 at 1:36 PM, Zach Davis 
>>> wrote:
>>>
 Hi Cory,

 I have three SMB volumes and one NFS volume mounted at
 /Users/zdavis/Shares using Autofs.  As an aside, I have been able to revert
 to using ParaView 4.4.0, but obviously don’t want to be stuck on this
 version forever if it can be avoided.

 Best Regards,


 [image: Pointwise, Inc.]
 Zach Davis
 Pointwise®, Inc.
 Sr. Engineer, Sales & Marketing
 213 South Jennings Avenue
 Fort Worth, TX 76104-1107

 *E*: zach.da...@pointwise.com
 *P*: (817) 377-2807 x1202 <(817)%20377-2807>
 *F*: (817) 377-2799
 
 
  

 On Mar 21, 2017, at 12:30 PM, Cory Quammen 
 wrote:

 Hi Zach,

 Someone else on this mailing list recently reported a similar crash. Do
 you have any unusual file systems mounted on the Mac in question? That will
 help debug the problem.

 Thanks,
 Cory

 On Tue, Mar 21, 2017 at 1:22 PM, Zach Davis  w
 rote:

> Tuesday, 21 March 2017
>
>
>
> All,
>
> I’ve been having issues with ParaView version 5 builds since their
> release.  I’ve tried each new release as its announced, but run into the
> same issue.  The application can be opened, but anytime I attempt to open 
> a
> file the application crashes before even displaying the Open/Save dialog
> window.  The termination signal is a Segmentation fault of type 11.  I’ve
> attached the crash report for anyone more knowledgeable about what the
> issue is.  Has anyone else experienced this issue?  Is there a workaround?
>
> Best Regards,
>
>
>
> [image: Pointwise, Inc.]
> Zach Davis
> Pointwise®, Inc.
> Sr. Engineer, Sales & Marketing
> 213 South Jennings Avenue
> Fort Worth, TX 76104-1107
>
> *E*: zach.da...@pointwise.com
> *P*: (817) 377-2807 x1202 <(817)%20377-2807>
> *F*: (817) 377-2799
> 
> 
> 
> 
>
> enc
>
>
>
>
> ___
> 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:
> 

[Paraview] Camera offset in Cave (ParaView 5.2.0)

[Dreer, Jutta]

Dear ParaView experts,

I managed to get ParaView 5.2.0 running in our Cave. I connect a cluster of 
servers, load the VR plugin, connect VRPN and start tracking. Then I load one 
of the geometric primitives like a cube and I am glad to say that I see the 
object moving when moving the glasses, so head tracking is working in 
principle. I can move or rotate the object with a wand, and it's even moving 
and turning in the correct direction (Yippee !!).

Now here's the problem: it seems to me that I have an offset of the viewer's 
position of several meters in the positive z direction (backward). The left and 
right movements of the object on the projection wall somehow correspond to the 
movement of the head position, but they seem to belong to a much longer 
distance between viewer and object. The VR module's window is showing values 
for a camera position which is several meters from the origin of the Cave (VRPN 
will give measurements in meters), although the viewer is in fact near to the 
origin (in the middle of the Cave).

How can I avoid to add an offset to the Camera and just take plain VRPN values 
for head position?

I am not very experienced with ParaView, sorry if this should be trivial. Any 
help is welcome. Thanks in advance.

Best Regards

Jutta Dreer
Leibniz Supercomputing Centre, Munich, Germany
jutta.dr...@lrz.de

___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Point Gaussian Radius

[Cory Quammen]

Bruce,

Thanks for the report, and sorry for the inconvenience. Cleaning up
the Point Gaussian representation is being tracked in an issue here:

https://gitlab.kitware.com/paraview/paraview/issues/17000

Best,
Cory

On Tue, Apr 4, 2017 at 8:32 AM, Bruce Jones  wrote:
> When using Point Gaussian for a large number of points, with an unsuitably
> large Gaussian radius, ParaView becomes unresponsive for a long time before
> it finally renders. In ParaView <=5.2, this was a fairly minor annoyance,
> the default Gaussian radius was always too high, but you could set the
> Gaussian radius to a suitable value before changing to point Gaussian.
> However, in ParaView 5.3 it is not possible to change the Gaussian radius
> before switching modes. With the default so high we are left waiting a long
> time before we are able to do anything again.
>
> My suggestion here is to either revert the behaviour back to 5.2, where the
> Gaussian radius could be specified before changing modes. Or (better), set
> the default to 0, which still renders the points, but without the massive
> lag time.
>
> Regards,
> Bruce
>
> ___
> 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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
Staff R Engineer
Kitware, Inc.
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] 2D Plot Log Warning Toggle Inquiry

[Joel Kulesza]

Colleagues,

Is there any ETA for incorporating this, or similar, functionality to
disable the log warning when zero/negative values are encountered?

https://gitlab.kitware.com/paraview/paraview/merge_requests/827

Please contact me with any comments, questions, or concerns.

Thank you,
Joel

Joel A. Kulesza, P.E.Ph.D. Candidate / Graduate Student Researcher
 University of Michigan, College of EngineeringNuclear Engineering &
Radiological Sciences Dept.2355 Bonisteel Boulevard
Ann Arbor, MI 48109-2104, USAMobile:  +1 (734) 223-7312
<(734)%20223-7312>Email:
 jkulesza@umich.eduHome Page:  http://www.engin.umich.edu/ners/
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Point Gaussian Radius

[Bruce Jones]

When using Point Gaussian for a large number of points, with an unsuitably
large Gaussian radius, ParaView becomes unresponsive for a long time before
it finally renders. In ParaView <=5.2, this was a fairly minor annoyance,
the default Gaussian radius was always too high, but you could set the
Gaussian radius to a suitable value before changing to point Gaussian.
However, in ParaView 5.3 it is not possible to change the Gaussian radius
before switching modes. With the default so high we are left waiting a long
time before we are able to do anything again.

My suggestion here is to either revert the behaviour back to 5.2, where the
Gaussian radius could be specified before changing modes. Or (better), set
the default to 0, which still renders the points, but without the massive
lag time.

Regards,
Bruce
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] ParaView v5.2 problems with PLY files with point clouds

[Nenad Vujicic]

Cory,

Thank you for response. Bil has already solved it (crashing problem, on
January 25th, 2017) and pushed it to repository, so it became part of
ParaView v5.3.0 release.

Thanks,
Nenad.

On Tue, Apr 4, 2017 at 2:44 AM, Cory Quammen 
wrote:

> Nenad,
>
> Sorry, this has been sitting in my inbox for a while now.
>
> I tried reading the PLY file you cited [1] with ParaView 5.3. It seems
> to read the points just fine.
>
> What might be confusing is that since there is no cell data, the
> points are not rendered in the default "Surface" representation. In
> the Properties panel, set the "Representation" type to 3D Glyphs, the
> Glyph Type to Sphere, and the Radius to 0.05. You'll see the points as
> pictured in the attached image.
>
> HTH,
> Cory
>
> [1] https://courses.cs.washington.edu/courses/cse558/01sp/
> software/scanalyze/points.html
>
> On Mon, Jan 16, 2017 at 9:20 AM, Nenad Vujicic  wrote:
> > Hello everyone,
> >
> > I found several PLY files which crashed my ParaView based application. I
> > inspected vtkPLYReader.cxx and found (Ln 128-140) that it doesn't even
> > support loading PLY files with points.
> >
> > Example of such PLY file:
> > https://courses.cs.washington.edu/courses/cse558/01sp/
> software/scanalyze/points.html
> > Example of software which successfully opens such PLY file: CloudCompare
> -
> > http://www.danielgm.net/cc/
> >
> > Do you maybe have in plan adding support for such PLY files? Has someone
> > perhaps already implemented such feature and is willing to share it?
> >
> > Thanks in advance,
> > Nenad.
> >
> > ___
> > 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
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
>
>
> --
> Cory Quammen
> Staff R Engineer
> Kitware, Inc.
>
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview