Re: [Paraview] xdmf latest sources?

2016-07-25 Thread Chuck Atkins
Hi Nabil, It's likely that you are behind some sort of firewall, either local on your machine or on the networks your trying use, that is blocking access to unknown protocols, in this case, the git protocol. HTTP and HTTPS are usually always allowed but probably not git://. You can also access

Re: [Paraview] Convert structured exodus to voxel data

2016-07-25 Thread Scott, W Alan
Makes sense. Will pass this to my user. Alan From: Moreland, Kenneth Sent: Monday, July 25, 2016 2:30 PM To: Scott, W Alan ; paraview@paraview.org Subject: RE: [Paraview] Convert structured exodus to voxel data Alan, For reasons I am sure you are aware of, you cannot in

Re: [Paraview] [EXTERNAL] Re: Convert structured exodus to voxel data

2016-07-25 Thread Scott, W Alan
Thanks Sujin – I will pass this to my user. Alan From: Sujin Philip [mailto:sujin.phi...@kitware.com] Sent: Monday, July 25, 2016 1:41 PM To: Scott, W Alan Cc: paraview@paraview.org Subject: [EXTERNAL] Re: [Paraview] Convert structured exodus to voxel data Hi Alan, Have you

Re: [Paraview] Procedure for compiling Catalyst

2016-07-25 Thread Shawn Waldon
He doesn't need to delete and re-clone. The recursive flag just does a normal clone followed by a git submodule update --init. So run that command in your paraview source tree and you should be fine. HTH, Shawn On Mon, Jul 25, 2016 at 4:00 PM, Adam Lyon wrote: > Well, reading

Re: [Paraview] Convert structured exodus to voxel data

2016-07-25 Thread Moreland, Kenneth
Alan, For reasons I am sure you are aware of, you cannot in general directly convert the points and cells of an unstructured grid like an Exodus mesh to a regular grid of voxels, and there is no such filter. The easiest way to make this conversion is to run the Resample To Image filter. This

Re: [Paraview] Procedure for compiling Catalyst

2016-07-25 Thread Adam Lyon
Well, reading that page again, it doesn't mention VTK, but adding "--recursive" to git clone will get the submodule. You should probably delete your repository and clone it again following the instructions at https://gitlab.kitware.com/paraview/paraview/blob/master/CONTRIBUTING.md. -- A *--*

Re: [Paraview] Procedure for compiling Catalyst

2016-07-25 Thread Adam Lyon
You need to follow the instructions at https://gitlab.kitware.com/paraview/paraview/blob/master/CONTRIBUTING.md . That will tell you how to checkout the VTK submodule. -- Adam *--* *Adam L. Lyon* *Scientist; Associate Division Head for Systems for Scientific Applications* Scientific

Re: [Paraview] Procedure for compiling Catalyst

2016-07-25 Thread T.J. Corona
Hi Chris, VTK is a submodule under VTK, so try the following: > git clone https://github.com/Kitware/ParaView.git > git submodule init git submodule update …the rest of the build process. Hope this helps! Sincerely, T.J. Thomas J. Corona, Ph.D.

Re: [Paraview] Procedure for compiling Catalyst

2016-07-25 Thread Christopher Neal
Hey guys, Have you ever had an issue with cmake concerning some missing VTK files? I typed Adam’s command exactly after cloning the Paraview repo(git clone https://github.com/Kitware/ParaView.git). I made a ParaView_build directory and executed Adam’s command in the build directory. I’m

Re: [Paraview] Convert structured exodus to voxel data

2016-07-25 Thread Sujin Philip
Hi Alan, Have you tried the "Resample To Image" filter? It will resample an input dataset to a vtkImageData. You can also specify the bounds and the dimension of the image data. By default the bounds is the same as the input dataset bounds. Thanks Sujin On Mon, Jul 25, 2016 at 3:31 PM, Scott,

[Paraview] Convert structured exodus to voxel data

2016-07-25 Thread Scott, W Alan
>From a user - is this even possible? How do you use paraview to convert an exodus mesh (with hex8 elements) into voxels and export as a VTK file? Can I control the number of voxels in each dimension? The mesh is of uniform size in each direction and I need the number of voxels to be a

Re: [Paraview] Procedure for compiling Catalyst

2016-07-25 Thread Christopher Neal
Thank you for sharing your cmake command Adam! I will try out your command. Best regards, Chris Neal From: Adam Lyon Date: Monday, July 25, 2016 at 1:50 PM To: Andy Bauer Cc: Christopher Neal , jeff wright

Re: [Paraview] Procedure for compiling Catalyst

2016-07-25 Thread Adam Lyon
Hi - I build the ParaView package with Catalyst turned on (but the ParaView GUI turned off). My cmake command is (sorry for the poor formatting, some of these options may not be useful for you)... cmake -DCMAKE_BUILD_TYPE:STRING=Release -DCMAKE_SKIP_INSTALL_RPATH:BOOL=YES -DBUILD_TESTING:BOOL=OFF

Re: [Paraview] Procedure for compiling Catalyst

2016-07-25 Thread Christopher Neal
Thank you Andy, My understanding is that the Catalyst editions can be compiled separately from Paraview i.e. I do not need to have a version of Paraview compiled in order to compile a Catalyst edition. Is this correct? Thank you, Chris From: Andy Bauer Date:

Re: [Paraview] Procedure for compiling Catalyst

2016-07-25 Thread Andy Bauer
Hi Chris, Catalyst is not a separate entity from ParaView. It is a subset of ParaView that is used for *in situ *processing. The concept of the editions is that the subset of interest differs based on the desired *in situ *processing and linking your simulation code to all of ParaView Catalyst