Re: [Paraview] SurfaceLIC issues with Paraview 5.2.0

Yeah, I think so too, but the admins who have installed Qt on the HPC clusters here didn't build the xmlpatterns binary. Hence, I don't have it on my system. It is a bit weird though that this should mess with SurfaceLIC plugin unless I misread the Qt docs. I think for now I'll skip this plugin

Re: [Paraview] Installing paraviewweb on a raspberry pi

Hi Faraz, I can look into your system if you can provide me ssh access. I don't promise to fix your issue but have experience with Raspberry Pis and Paraview builds. And I don't need money, I'll do it out of curiosity and in free time :) On Tue, Feb 14, 2017 at 4:55 PM, Faraz Hussain

Re: [Paraview] SurfaceLIC issues with Paraview 5.2.0

Set the xmlpatterns executable, if you have it. I am sure that's what's messing the build up. On Tue, Feb 14, 2017 at 6:01 PM, Faiz Abidi wrote: > Utkarsh - I think I am missing /usr/lib64/qt4/bin/xmlpatterns but that's > just a warning. Attached is the CMakeCache file. > >

[Paraview] volume vs volume

Hi all, I was trying to find volume for a user, and started wondering if the user wanted volume of the dataset, or volume of each cell. Turns out that there is incorrect information on the list. I believe the following is true: Volume of the dataset: Python Calculator. Expression:

Re: [Paraview] PV5.2 Scalarbar range error

Hi Bob, This issue has been identified and a fix will be in ParaView 5.3.0. Please see https://gitlab.kitware.com/paraview/paraview/issues/17152 for more information. Thanks, Cory On Thu, Jan 12, 2017 at 11:17 AM, Bob Flandard wrote: > Hi, > > I'm using PV5.2 on Windows 7

Re: [Paraview] Installing paraviewweb on a raspberry pi

Unfortunately, I am not having much luck getting Paraview to build. I keep trying to configure (c), but the generate (g) option does not come. I am wondering if someone would be willing to poke around in my system . I can pay some nominal amount for your time. However , since this is

Re: [Paraview] Automating contour isosurface values in parallel Catalyst Python script

Hi Yvan, Another option is just to compute it yourself. The reason that the global min and max aren't know in Catalyst is that it requires communication but many times the value isn't needed so in order to make Catalyst more efficient it doesn't compute that value for you automatically. In the

Re: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download

Hi, I don't have access to the server right now and I could not check the cake version but probably it is 3.7.x. So, I'll try to test the newer version and i'll get back to you then (probably on Thursday). Thanks for your help. Regards, --ufuk > On Tue, Feb 14, 2017 at 10:04:50 -0500, Utkarsh

Re: [Paraview] ParaView 5.3.0 and VTK-m

Hi, As Joachim pointed out currently ParaView requires a specific version of VTK-m to resolve the exception name problem. Yesterday we merged in a fix for this problem to VTK ( https://gitlab.kitware.com/vtk/vtk/merge_requests/2469 ) so soon you will not require a specific version of VTK-m. On

Re: [Paraview] Automating contour isosurface values in parallel Catalyst Python script

Hi Yvan, Regarding MinMax: this filter is indeed not exposed by any standard Catalyst edition but it is easy to add. See for instance in ParaView/Catalyst/Editions/Extras/manifest.json how the PVExtractSelection filter is exposed (line 50 and 247). Just do the same with the MinMax filter (see

Re: [Paraview] ParaView 5.3.0 and VTK-m

Hello Claire, Checking at paraview-superbuild project is generally a good idea to answer this kind of questions. In versions.cmake one can see that it downloads this version:

Re: [Paraview] SurfaceLIC issues with Paraview 5.2.0

I had a similar problem on debian export QT_SELECT=qt5 or qt4 before running cmake fix the problem Christophe TROPHIME Research Engineer CNRS - LNCMI 25, rue des Martyrs BP 166 38042 GRENOBLE Cedex 9 FRANCE Tel : +33 (0)4 76 88 90 02 Fax : +33 (0) 4 76 88 10 01 Office U 19 M@il :

Re: [Paraview] STL files: normal and vertex

Hello Tiago, Using Fetch you should end up with a vtkPolyData object which have accessors to triangle point ids (using GetPolys() then a traversal on the vtkCellArray or directly using GetCellPoints(). Point coordinates can be retrieved using GetPoint() function. So could you be more specific on

Re: [Paraview] SurfaceLIC issues with Paraview 5.2.0

Can you post your CMakeCache.txt? I suspect one of the Qt help generation tools was not found/set correctly. Utkarsh On Tue, Feb 14, 2017 at 12:46 PM, Faiz Abidi wrote: > Hello community, > > Anyone faced issues with Paraview 5.2.0 and the SurfaceLIC plugin? When I > install

Re: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download

On Tue, Feb 14, 2017 at 10:04:50 -0500, Utkarsh Ayachit wrote: > Chuck, is this a CMake version related issue? Ufuk, which cmake > version are you using? It likely is. VTK is now using CMake's C++11 support detection and older versions of CMake do not have the required bits for Intel 16. These

[Paraview] SurfaceLIC issues with Paraview 5.2.0

Hello community, Anyone faced issues with Paraview 5.2.0 and the SurfaceLIC plugin? When I install Paraview from source, I get the below error. "/bin/sh: line 0: cd: /home/fabidi89/git/ParaView/build_usingCCMake/Plugins/SurfaceLIC/doc: No such file or directory make[2]: ***

Re: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download

Could you be more explicit regarding the error you encounter as those output are expected on Windows. Did you provide the path to ParaView as the argument of the Visualizer executable? Thanks, Seb On Tue, Feb 14, 2017 at 4:07 AM, Daniel Zuidinga wrote: > paraview web

Re: [Paraview] Cataylst pipeline not updating

Hi Tim, I'm glad this fixed the issue. You'll want to always pass in the time to UpdatePipeline() for Catalyst. The issue was that the pipeline thought that everything it had was current since the time didn't change and none if the filters' parameters changed and therefore it skipped recomputing

Re: [Paraview] Cataylst pipeline not updating

Hi Andy, Looks like passing the current time step into the UpdatePipeline calls made it work as expected. Sorry for the delay in reporting, it took a long time for the job to move through the queue! Anyway, looks like it's working properly and I am getting the data as expected. For future

[Paraview] ParaView 5.3.0 and VTK-m

Hi all, I'm trying to build ParaView 5.3.0 with the last version of VTK-m (sources download today using git clone https://gitlab.kitware.com/vtk/vtk-m.git). I compile VTK-m with TBB backend (version 4.2), gcc 4.9 and -std=c++11 option. I have the following issues a lot of times when

Re: [Paraview] vtkPythonProgrammableFilter Multiple output port?

AFIAK, this is not currently supported. Utkarsh On Fri, Feb 10, 2017 at 1:34 PM, michal wozniak wrote: > Hi, > > > Since ParaView 5.2, vtkPythonProgrammableFilter can now accept multiple > input ports. Is it possible to also have multiple output port? > > > Thanks, > >

Re: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download

Chuck, is this a CMake version related issue? Ufuk, which cmake version are you using? Utkarsh On Tue, Feb 14, 2017 at 5:27 AM, Ufuk Utku Turuncoglu (BE) wrote: > Hi Cory, > > I was trying to install new release candidate from source to test Catalyst > module

Re: [Paraview] [Non-DoD Source] XDMF and nested Grid Collections (UNCLASSIFIED)

CLASSIFICATION: UNCLASSIFIED Alessandro, This looks like a useful feature to add to the reader, and we will put in our list of things to work on. But, I can not immediately implement this as we have a number of high priority updates such as c++11 support, and an updated base Xdmf library

Re: [Paraview] [vtkusers] Open big *.VTK files with ParaView

Christopher, I'm moving this to the ParaView mailing list. As I recall, Microsoft's runtime requires the use of special file-handling functions for reading files larger than 4 GB, even when running on a 64-bit version of Windows. I do not believe the VTK legacy library does not use these

[Paraview] XDMF and nested Grid Collections

Hi, I'm trying to export from a parallel MPI CFD code a set of results using xdmf/hdf5 format in order to be read in Paraview. The computational domain is divided into several parts (unstructured polyhedral grid) and the idea is to write a xdmf with a further subdivision to be read in parallel

[Paraview] STL files: normal and vertex

Dear all, I have a contour in Paraview that I would like to export to Matlab. In the past I’ve been doing this by generating a STL file which could be read in Matlab without any problems. However, now my STL files are quite large and reading in Matlab is really inefficient because of the STL

Re: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download

paraview web visualizer does not work in windows: ls: no such file or directory: /Applications ls: no such file or directory: /opt ls: no such file or directory: /usr/local/opt/ Am 13.02.2017 um 17:49 schrieb Cory Quammen: Folks, Binaries and source code zip files and tar balls for ParaView

Re: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download

Hi Cory, I was trying to install new release candidate to test Catalyst module but i am getting following error messages under Linux (CentOS) and with Intel compiler (2016), CMake Error at VTK/CMake/vtkModuleMacros.cmake:549 (target_compile_features): target_compile_features no known

Re: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download

Hi Cory, I was trying to install new release candidate from source to test Catalyst module but i am getting following error messages under Linux (CentOS) and with Intel compiler (2016), CMake Error at VTK/CMake/vtkModuleMacros.cmake:549 (target_compile_features):

Re: [Paraview] Copying representation properties

Works perfectly on ParaView 5.2.0 on Windows 10. you may want to try and reproduce this behavior on other computers/OSes. And let us know how you use this feature. Regards, Mathieu Westphal On Sun, Feb 12, 2017 at 1:31 PM, Dimitrova, Maria < maria.dimitr...@helsinki.fi> wrote: > Thank you,