Re: [Paraview] Use of Python declared variables inside new scripts from ProgrammableSource and/or ProgrammableFilter.

Hello everyone, Thanks Utkarsh for this answer. It works with pvpython. Unfortunately, this does not work with paraview I have tested manually from a desktop version of Paraview, with Paraview 4.4 and 5.0 on Windows. I have this error: NameError: global name 'meta_data' is not defined In fact, I

Re: [Paraview] Incorrect shading results in ParaViewWeb Local(VGL) mode

Did you try the other WebGL option that is marked 'deprecated' ? On Mon, Jan 18, 2016 at 1:12 AM, Xue Junjie wrote: > It seems the Local(VGL) rendering mode in ParaViewWeb has issues with some > model files. > > How to reproduce the issue: > open the visualiser, selecte the

[Paraview] Incorrect shading results in ParaViewWeb Local(VGL) mode

It seems the Local(VGL) rendering mode in ParaViewWeb has issues with some model files. How to reproduce the issue: open the visualiser, selecte the data file: 'can.ext2'. Under 'Remote mode': all is ok, no issue Under 'Local(VGL) mode': if the model is zoomed out to a certain distance, some

[Paraview] superbuild fails on OS X

I have the latest OS X and qt4 and qt5 installed by brew. I use the current superbuild, which covers PV 4.4 (why not 5.0?) but build fails. I use the default setting in my build and just set CMAKE_INSTALL_PREFIX and ENABLE_paraview make … -- Installing:

Re: [Paraview] superbuild fails on OS X [solved]

I found it: Qt needs to be enabled! ENABLE_qt4 results in the error below, with USE_SYSTEM_qt4 (installed with brew) it works! While I understand that there is no gui without qt and that it makes sense to build paraview without gui, I suggest to make it a little clearer: The help for

[Paraview] A Question on opening Python Shell.

Hi there, I have installed the Paraview 5.0 version released from the official site. Everything seems good until I opened the Start Trace from the Tools option. Then, I clicked OK and the whole Paraview crashed to desktop. It also happened when I opened Python Shell. I think maybe something

Re: [Paraview] Incorrect shading results in ParaViewWeb Local(VGL) mode

>From the source tree it will be in {VTK-src}/Web/JavaScript/Lib/vtkweb.viewport.webgl.js Which will be gathered inside {www}/lib/core/vtk-web-all.js On Mon, Jan 18, 2016 at 9:01 AM, Junjie Xue wrote: > Hi, Sebastien, > > Thanks for your quick reply! > > I need to modify

Re: [Paraview] Incorrect shading results in ParaViewWeb Local(VGL) mode

Hi, Sebastien, Thanks for your quick reply! I need to modify the frustum parameter(modify the 'far' value from 1e4 t 1e5) to test the model in 'deprecated' mode. The code of 'local(cgl)' mode is located in '/.../ext/core/vgl.min.js'. Do you know where is the WebGL code of 'deprecated' mode?

Re: [Paraview] Incorrect shading results in ParaViewWeb Local(VGL) mode

Managed to display the data file in 'deprecated' mode. the black area now display as transparency, looks like holes on the model. 在 2016/1/19 0:11, Sebastien Jourdain 写道: From the source tree it will be in {VTK-src}/Web/JavaScript/Lib/vtkweb.viewport.webgl.js Which will be gathered inside

Re: [Paraview] superbuild fails on OS X [solved]

> While I understand that there is no gui without qt and that it makes sense to > build paraview without gui, I suggest to make it > a little clearer: > > The help for ENABLE_qt* is just „Request to build project qt*“. Maybe an „Qt > is necessary for the gui“ could be added. Also the error