Re: [Paraview] Changing colormap parameters in a Catalyst script

Thanks Cory! Matthieu From: Cory Quammen [cory.quam...@kitware.com] Sent: Friday, October 30, 2015 2:19 PM To: Dorier, Matthieu Cc: Paraview (paraview@paraview.org) Subject: Re: [Paraview] Changing colormap parameters in a Catalyst script Mattheiu, For rescaling

[Paraview] SOLVED Re: Paraview 4.4.0 build error with osmesa on RHEL cluster at LLNL

I ended up fixing the problem by appending " -lGLU" to my LINKER_FLAGS, which I add to all my CMAKE__FLAGS as follows: -DCMAKE_EXE_LINKER_FLAGS:STRING="$LINKER_FLAGS" \ -DCMAKE_SHARED_LINKER_FLAGS:STRING="$LINKER_FLAGS" \ -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING="$LINKER_FLAGS"

[Paraview] Making timesteps

All, I would like to take a ring of elements, lets say a ring of 180 elements, each 2degrees of arc. After loading this ring, each of the 180 elements in the ring will have a specific strain state. I would like to then take a separate input which would be a single element and give it 180

Re: [Paraview] Some questions about Catalyst Live Visualization

Hi Adam, To rename the objects in the pipeline, you should be able to do: simSteps = coprocessor.CreateProducer(datadescription, 'simSteps') RenameSource('simSteps', simSteps) simCalHits = coprocessor.CreateProducer(datadescription, 'simCalHits') RenameSource('simCalHits', simCalHits) Please let

Re: [Paraview] segmentation fault with netCDF when loading state file

On Wed, Oct 28, 2015 at 9:47 PM, Ryan Abernathey wrote: > Yes, I can confirm that this state loads without crashing in 4.4. > The fields are not actually accessible at the current timestep (appear > with a "?"), but can be rewound to the beginning and restarted without

Re: [Paraview] Some questions about Catalyst Live Visualization

Hi Andy - thanks for the answers!! You misunderstood my question #2. I'm not reporting a bug -- the adapter works fine and feeds data appropriately. Right now my code to translate my data objects to VTK objects runs no matter what. I'd like this code to only run if a ParaView client is actually

Re: [Paraview] Changing colormap parameters in a Catalyst script

Mattheiu, For rescaling when your data range is known, use: a1_dbz_PiecewiseFunction.RescaleTransferFunction(min, max) a1_dbz_PVLookupTable.RescaleTransferFunction(min, max) When it is unknown, you can use pipelineObject = GetActiveSource() display = GetDisplayProperties(pipelineObject)

Re: [Paraview] Some questions about Catalyst Live Visualization

Hi Adam, On Fri, Oct 30, 2015 at 10:20 AM, Adam Lyon wrote: > I'd like this code to only run if a ParaView client is actually connected > (because if there's no client connected then it's making VTK objects that > no human is looking at, so it's wasting time). So I'd like to know

Re: [Paraview] Paraview 4.4.0 build error with osmesa on RHEL cluster at LLNL

On Fri, Oct 30, 2015 at 18:22:01 +, Cook, Rich wrote: > I'm seeing an error when trying to build the latest Paraview using > osmesa: > > The configuration step goes OK. In particular note that I set > -DOPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so I think with OSMesa, this should be

[Paraview] Changing colormap parameters in a Catalyst script

Hi, I have generated a Catalyst python script that produces a colormap on a slice of a 3D rectilinear grid. I would like to use the same script for another variable of the simulation, but the range of data is not the same. How can I adapt the script, both in case where I know the new data

[Paraview] Paraview 4.4.0 build error with osmesa on RHEL cluster at LLNL

I'm seeing an error when trying to build the latest Paraview using osmesa: == The configuration step goes OK. In particular note that I set