[Paraview] Error when trying to turn on Volume Rendering for large tetrahedral data in ParaView 5.4.1

2018-01-24 Thread Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
Hello, I am experiencing an error with volume rendering very large tetrahedral data with ParaView version 5.4.1. The data is loaded properly and the surface representation works, but when I change the representation to Volume, I get the standard dialog below to which I respond "Yes" 'This

Re: [Paraview] How to insert annotate time info into catalyst?

2018-01-24 Thread Andy Bauer
Hi Seongmo, Please keep the conversations on the mailing list so that anyone can follow along or participate. Also, these types of things often get lost in my inbox when they don't make it back to the ParaView mailing list. What version of ParaView Catalyst are you using? I think the annotate

Re: [Paraview] [Non-DoD Source] Re: Error when trying to turn on Volume Rendering for large tetrahedral data in ParaView 5.4.1

2018-01-24 Thread Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
Utkarsh, Thanks, turning on "Use Data Partitions" helped quite a bit. The rendering is working for me now. I still suspect there is a bug somewhere, but with "Use Data Partitions" on I do not seem to be hitting it, and it is renders faster as well. Thanks, Joe

Re: [Paraview] Error when trying to turn on Volume Rendering for large tetrahedral data in ParaView 5.4.1

2018-01-24 Thread Utkarsh Ayachit
Joe, Sorry, doesn't ring a bell. One thing to try is to turn of "Use Data Partitions" (see [1]) if your data is already partitioned between ranks such that we can build a sorting order. Utkarsh [1] https://blog.kitware.com/improved-parallel-rendering-in-paraview/ On Wed, Jan 24, 2018 at 3:16

Re: [Paraview] python mismatch with superbuild on os x

2018-01-24 Thread Cory Quammen
On Wed, Jan 24, 2018 at 12:57 PM, Sgouros, Thomas wrote: > Hello: > > I unpacked a version of the Paraview-v5.4.1 tarball, and then did git clone > of the superbuild right next to it. So I have this: > > $ ls > ParaView-v5.4.1 > paraview-superbuild > $ mkdir

Re: [Paraview] Reading group of pvti files: vtkImageData is static over time

2018-01-24 Thread Ahmad .
Hello again, Could someone please confirm this to be a bug, or otherwise tell me how it could be resolved? The problem is that my vtkImageData object changes in size over time, but visually it stays the same when I import it in ParaView as a group and play it as an animation. Please see

Re: [Paraview] Reading group of pvti files: vtkImageData is static over time

2018-01-24 Thread Cory Quammen
Hi Ahmad, Please see Mathieu Westphal's comment on the issue you created. Thanks, Cory On Wed, Jan 24, 2018 at 9:02 AM, Ahmad . wrote: > Hello again, > > > Could someone please confirm this to be a bug, or otherwise tell me how it > could be resolved? > > > The problem

Re: [Paraview] Extracting data on the surface of a block?

2018-01-24 Thread Utkarsh Ayachit
> How is "Chart View" selected again? I didn't find it in the "View" drop down > menu at the top, but I was able to open a new layout and select > "SpreadSheetView". By selecting the "Chart View", I meant simply click on the view that's showing the plots after you applied the

Re: [Paraview] Extracting data on the surface of a block?

2018-01-24 Thread Utkarsh Ayachit
Louis, Can you also attach a state file for the vis you're generating currently, so I get a starting point? I am not sure which block is the oil drop. Thanks, Utkarsh On Tue, Jan 23, 2018 at 8:12 PM, Steytler, Louis Louw wrote: > Hi Utkarsh, > > My data file is rather

[Paraview] python mismatch with superbuild on os x

2018-01-24 Thread Sgouros, Thomas
Hello: I unpacked a version of the Paraview-v5.4.1 tarball, and then did git clone of the superbuild right next to it. So I have this: $ ls ParaView-v5.4.1 paraview-superbuild $ mkdir paraview-superbuild-build $ cd paraview-superbuild-build $ ccmake ../paraview-superbuild There is a mismatch

Re: [Paraview] XDMF file with multiple temporal collections

2018-01-24 Thread Nicolas Cedilnik
Hello It's been a while but I'm back to trying to solve this issue. Unfortunately this doesn't solve the issue. Using paraview 5.4.1 from latest Fedora… Anything else I should try ? -- Nicolas On 11/20/2017 10:46 PM, David E DeMarle wrote: Try dropping your standalone external geometry