ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-06-15T15:53:48-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/17267Auto Apply with readers2023-06-15T15:53:48-04:00W. Alan ScottAuto Apply with readersMake the readers work properly with Auto Apply on. One idea is to have Readers ignore Auto Apply, thus you always manually select variables then hit the Apply button. Another idea (from Ken) is to have a floating panel pop up, that you...Make the readers work properly with Auto Apply on. One idea is to have Readers ignore Auto Apply, thus you always manually select variables then hit the Apply button. Another idea (from Ken) is to have a floating panel pop up, that you then set up, and click OK.
This is needed for PV 6.0https://gitlab.kitware.com/paraview/paraview/-/issues/17872path tracer point aligned values not always colored correctly2023-06-15T15:51:47-04:00David E. DeMarlepath tracer point aligned values not always colored correctlyneed interpolate colors, which suggests that 1d textures are not enabled in pathtracer::objmaterial
also, out of range colors are clamped incorrectly to lowneed interpolate colors, which suggests that 1d textures are not enabled in pathtracer::objmaterial
also, out of range colors are clamped incorrectly to lowDavid E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/20456Python Editor open file issue2023-06-15T15:42:41-04:00Mathieu Westphal (Kitware)Python Editor open file issue- Tools -> Python Editor
- File -> Open
- **The window is called Save File and actually behave like a save file window**, this is a bug
- Open a file.py
@thomas.caissard- Tools -> Python Editor
- File -> Open
- **The window is called Save File and actually behave like a save file window**, this is a bug
- Open a file.py
@thomas.caissardhttps://gitlab.kitware.com/paraview/paraview/-/issues/22127More Issues with Copy Pipeline / Paste Pipeline2023-06-15T15:27:14-04:00Mathieu Westphal (Kitware)More Issues with Copy Pipeline / Paste PipelineBug:
* Wavelet, Apply
* Right Click on wavelet -> Copy Pipeline
* Right Click on wavelet -> Paste Pipeline is greyed out, this is a bug
Bug:
* Wavelet, Apply
* Wavelet, Apply
* Select both wavelet
* Right Click on wavelet -> Copy Pipe...Bug:
* Wavelet, Apply
* Right Click on wavelet -> Copy Pipeline
* Right Click on wavelet -> Paste Pipeline is greyed out, this is a bug
Bug:
* Wavelet, Apply
* Wavelet, Apply
* Select both wavelet
* Right Click on wavelet -> Copy Pipeline is greyed out, this is a bug
Bug:
* Wavelet, Apply
* Right Click on wavelet -> Copy Pipeline
* Delete Wavelet
* Right Click anywhere -> Paste Pipeline is greyed out, this is a bugYohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/8560Select zoom to a node2023-06-15T15:19:40-04:00Kitware RobotSelect zoom to a node**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=8560). Further discussion may take place here.**
---
From a user, asking if EnSight will do what blot will, the following reques...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=8560). Further discussion may take place here.**
---
From a user, asking if EnSight will do what blot will, the following request:
In blot there is a way to zoom to a node. Is there a similar capability in ensight. For example, in blot you can say zoom node 57 radius 1
and it will zoom to that node and include everything in a radius of 1.https://gitlab.kitware.com/paraview/paraview/-/issues/12479AMR Dual Clip produces incorrect results on some datasets.2023-06-15T15:08:19-04:00Kitware RobotAMR Dual Clip produces incorrect results on some datasets.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12479). Further discussion may take place here.**
---
Bug happens when clipping both materials at 0.1.
See attached image**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12479). Further discussion may take place here.**
---
Bug happens when clipping both materials at 0.1.
See attached imagehttps://gitlab.kitware.com/paraview/paraview/-/issues/16035Save data, clipped, CTH crashes2023-06-15T14:16:59-04:00Kitware RobotSave data, clipped, CTH crashes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16035). Further discussion may take place here.**
---
We have a bad crash, that is impacting a user, when trying to write out cl...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16035). Further discussion may take place here.**
---
We have a bad crash, that is impacting a user, when trying to write out clipped CTH AMR data. Here is how to replicate.
* PV 5.0.1 RC2, Linux. Remote server (I had 16 pvservers, but I bet it replicates with 2).
* Load Dave's large CTH dataset. All vars on.
* Turn off Merge XYZ Components and Down Convert Volume Fraction. (I bet this bug replicates without this step).
* Apply.
* Clip. By Scalar. Material Volume Fraction 1. Value == 0.5. Apply.
(Just so you can see, turn visibility off for the CTH reader.)
* File/ Save Data. Exodus writer. Don't save all timesteps. Apply.
<<Server side dies>>
Looking in the output, there are a bazillion warnings somewhat like this:
Warning: In /projects/viz/paraview/src/ParaView/5.0.1-RC2/ParaView5/VTK/IO/ParallelExodus/vtkPExodusIIWriter.cxx, line 74
vtkPExodusIIWriter (0x8cebe30): ExodusIIWriter ignores ghost level request
Warning: In /projects/viz/paraview/src/ParaView/5.0.1-RC2/ParaView5/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 3236
vtkPExodusIIWriter (0x8cebe30): Attempting to proceed without metadata
And then MPI dies.https://gitlab.kitware.com/paraview/paraview/-/issues/15832vtkExodusIIWriter: vtk int array converted to double2023-06-15T14:14:21-04:00Kitware RobotvtkExodusIIWriter: vtk int array converted to double**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15832). Further discussion may take place here.**
---
Writing an Int array to an exodus file, the data is incorrectly stored as ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15832). Further discussion may take place here.**
---
Writing an Int array to an exodus file, the data is incorrectly stored as double in the file. An MWE
```
import numpy
import vtk
from vtk.util import numpy_support
points = [
[0.0, 0.0, 0.0],
[1.0, 0.0, 0.0],
[1.0, 1.0, 0.0],
[0.0, 1.0, 0.0]
]
mesh = vtk.vtkUnstructuredGrid()
# set points
vtk_points = vtk.vtkPoints()
# Not using a deep copy here results in a segfault.
vtk_array = vtk.util.numpy_support.numpy_to_vtk(points)
vtk_points.SetData(vtk_array)
mesh.SetPoints(vtk_points)
# TODO use numpy_support here, avoid the copying
c = numpy.array([
3,
0, 1, 2,
3,
0, 2, 3
], dtype=int)
a = vtk.util.numpy_support.numpy_to_vtkIdTypeArray(c)
cell_array = vtk.vtkCellArray()
cell_array.SetCells(2, a)
mesh.SetCells(vtk.VTK_TRIANGLE, cell_array)
# add int point data
X = numpy.array([7, 8, 3, -2], dtype=int)
array = vtk.util.numpy_support.numpy_to_vtk(X)
array.SetName('X')
pd = mesh.GetPointData()
pd.AddArray(array)
writer = vtk.vtkExodusIIWriter()
writer.SetFileName('test.e')
writer.SetInput(mesh)
writer.Write()
```
The array `X` is stored as `double` in `test.e`.https://gitlab.kitware.com/paraview/paraview/-/issues/18927Global data writer is bad for exodus2023-06-15T14:09:08-04:00W. Alan ScottGlobal data writer is bad for exodusI am pretty sure that the Exodus writer is broken for global data, especially for strange timesteps. Here is how to replicate using can.exo.
* Linux, master, builtin server. ( v5.6.0-1290-gb61f946 )
* Load can.exo. All vars on. Appl...I am pretty sure that the Exodus writer is broken for global data, especially for strange timesteps. Here is how to replicate using can.exo.
* Linux, master, builtin server. ( v5.6.0-1290-gb61f946 )
* Load can.exo. All vars on. Apply.
* Extract Timesteps filter. Select Time Range. Timestep 0 to 19. Apply.
* File/ Save Data/ save as Exodus. Save as canA. (It will write out a canA.e file). Save all timesteps.
* CHANGE Extract Timesteps filter. Select Time Range. Timestep 20 to 43. Apply.
* File/ Save Data/ save as Exodus. Save as canB. (It will write out a canB.e file). Save all timesteps.
* Edit/ Reset Session.
* Load canA.e, load all variables, apply.
* Plot global variable over time. Apply. Turn off everything other than NSTEPS. Notice this is a straight line.
* Load canB.e, load all variables, apply.
* Plot global variable over time. Apply. Turn off everything other than NSTEPS. Notice this is a straight line.
* Change visibility of the canB plot global variables over time to also be in the canA.e plot global variables over time.
This should be a straight line, rather than two slanted, parallel lines.
You can see this occurring if you output canA.e and canB.e into two spreadsheets. canB.e restarts NSTEPS at 0, where in the original data it is fairly large.5.12 (Winter 2023)W. Alan ScottW. Alan Scotthttps://gitlab.kitware.com/paraview/paraview/-/issues/14265Exodus writer fails with polyhedral data2023-06-15T14:07:22-04:00Kitware RobotExodus writer fails with polyhedral data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14265). Further discussion may take place here.**
---
Local server, master, Linux.
Open dataset fmaego.mesh.case, found in bug r...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14265). Further discussion may take place here.**
---
Local server, master, Linux.
Open dataset fmaego.mesh.case, found in bug report http://paraview.org/Bug/view.php?id=13338. Apply.
File/ Save Data, and write this out as an exodus dataset. ParaView/VTK will output lots of error verbiage, and then write out an empty file.
```
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 42
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 110
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 178
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 382
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 450
```W. Alan ScottW. Alan Scotthttps://gitlab.kitware.com/paraview/paraview/-/issues/15950Exodus writer - edge sets not written correctly,2023-06-15T13:58:54-04:00Kitware RobotExodus writer - edge sets not written correctly,**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15950). Further discussion may take place here.**
---
A customer is having issues writing edge sets, coming from the Resample wi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15950). Further discussion may take place here.**
---
A customer is having issues writing edge sets, coming from the Resample with Dataset filter. Here is how to replicate:
* Open donor-DoNotRelease.g. All variables on. Apply.
* Note - Two important vars - PRES_PA and TEMP_K
* Open recipient-DoNotRelease.g. Select Has Mode Shapes. Advanced Properties tab. Select all Sets. Select all Variables. Apply.
* Note - PRES_PA and TEMP_K do not exist in this dataset.
* Resample with Dataset.
** Input > donor-DoNotRelease.g
** Source > recipient-DoNotRelease.g OK.
* (Advanced properties need to be on.)
* select Pass Cell Array, select Pass Point Array.
* unselect Compute Tolerance. Set manual tolerance to 1e-3.
* Apply
* Note - ResampleToDataset should already be selected. If not, select it.
* Save Data. Exodus file. Save as some known file, such as combined-DoNotRelease.e. Don't save all timesteps - it will take forever.
* Now, open combined-DoNotRelease.e. All variables on, all sets on, all blocks off. There's nothing here! This is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/14429State file doesn't load remote server from recent files.2023-06-15T13:46:10-04:00Kitware RobotState file doesn't load remote server from recent files.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14429). Further discussion may take place here.**
---
ParaView master, Linux, remote server (I have 8 pvservers).
Source/ Wavele...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14429). Further discussion may take place here.**
---
ParaView master, Linux, remote server (I have 8 pvservers).
Source/ Wavelet. Apply.
Save State.
Delete Wavelet.
Now, try loading this state file from Recent Files. All that happens is an error is printed out, saying "File does not exist:"https://gitlab.kitware.com/paraview/paraview/-/issues/18765Plane tool is totally wacked when moving from 2d to 3d.2023-06-15T13:42:27-04:00W. Alan ScottPlane tool is totally wacked when moving from 2d to 3d.* Linux, 5.6.0, builtin server.
* Sources/ Mandlebrot. Apply.
* 3D. Note that the Mandelbrot will disappear (shrink). This probably a bug.
* Clip. Apply.
* Reset. We now see a thing that looks like a short water tower. This is a bu...* Linux, 5.6.0, builtin server.
* Sources/ Mandlebrot. Apply.
* 3D. Note that the Mandelbrot will disappear (shrink). This probably a bug.
* Clip. Apply.
* Reset. We now see a thing that looks like a short water tower. This is a bug.
![Capture](/uploads/c7b52dbf88008249ec641b5b687b1392/Capture.JPG)Thomas GallandThomas Gallandhttps://gitlab.kitware.com/paraview/paraview/-/issues/16104Allow save state/ load state to load data automatically2023-06-15T13:40:27-04:00Kitware RobotAllow save state/ load state to load data automatically**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16104). Further discussion may take place here.**
---
Please add the ability to tell a .pvsm file to auto load it's data from th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16104). Further discussion may take place here.**
---
Please add the ability to tell a .pvsm file to auto load it's data from the same directory as the .pvsm. This can be either a check box that adds this information in the .pvsm file or an external environment variable. Best answer would be both.https://gitlab.kitware.com/paraview/paraview/-/issues/16762Multiple selections don't work correctly in parallel2023-06-15T13:38:46-04:00Kitware RobotMultiple selections don't work correctly in parallel**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16762). Further discussion may take place here.**
---
Multiple selections don't work correctly in parallel. I suspect that this...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16762). Further discussion may take place here.**
---
Multiple selections don't work correctly in parallel. I suspect that this is the tip of an iceberg. I have seen single point selections also be weird - but this finally allows us to replicate it.
Utkarsh took a few tries, but was able to replicate this.
* 8 remote pvservers, Linux, 5.0.1. (I don't know if it replicates the same with fewer pvservers.)
* Open g1s1. Ask Utkarsh or me for this dataset.
* Run ProcessIdScalars, Apply. Not necessary, but helps me describe where to select.
* Go to last timestep. Back one timestep.
* -Z
* Select points on.
* Not necessary, but you may want surface with edges.
* Now, you want to rubber band select the lower tip of the medium blue material (white in vtkBlockColors). You want to rubber band select about 1/2" by 1/2", including a bit of the orange, the beige, and the medium blue. (You may need to cycle through this a few times.)
* Outline.
<<Bug>> Notice that many points are selected that are inside the dataset. I think they are on processor boundaries, but cannot tell. This is a bug.Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/18081(master): Selections infrastructure refactor2023-06-15T13:34:55-04:00Utkarsh Ayachit(master): Selections infrastructure refactor* [x] `vtkSelectionNode::FieldType` doesn't match vtkDataObject::FieldAssociations. Let's fix that. Create a new variable (maybe FieldAssociation or AttributeType and deprecate the old).
* [x] `vtkSelection` doesn't support boolean expre...* [x] `vtkSelectionNode::FieldType` doesn't match vtkDataObject::FieldAssociations. Let's fix that. Create a new variable (maybe FieldAssociation or AttributeType and deprecate the old).
* [x] `vtkSelection` doesn't support boolean expressions to combine `vtkSelectionNode`. Currently it support a collection of selection nodes, but doesn't define how they are combined. The idea is to add support for an expression string to vtkSelection that combines the selection-nodes into a boolean expression with ands,ors,nots etc. BC issues are addressed by keeping the default expression consistent with current.
* [x] Selection extraction filter uses several vtkObject subclasses to evaluate each of the selection nodes to get a mask array and then combine them together.
* [x] Selection Source Proxy -- we potentially need to use a custom proxy that doesn't use the Property mechanism to define the values for selection nodes.Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/17605Plot Over Line fails to plot2023-06-15T13:23:03-04:00Jarno van der KolkPlot Over Line fails to plotI was trying to use the "Plot Over Line" filter on a 2D dataset, but no line is drawn. The legend and axes do appear though. I tried making a minimal example of just an Xdmf3 file with hand-written values as XML data, but then it works f...I was trying to use the "Plot Over Line" filter on a 2D dataset, but no line is drawn. The legend and axes do appear though. I tried making a minimal example of just an Xdmf3 file with hand-written values as XML data, but then it works fine. So I have attached a sample data file where Plot Over Line fails.
[chi_0072.dat.xmf](/uploads/f52cbc1422c845b1de225a05de12d2d2/chi_0072.dat.xmf)
[chi_0072.dat](/uploads/975401eeba4760dddc07e247548be5ca/chi_0072.dat)
Steps to reproduce:
1. Open the file "chi_0072.dat.xmf".
2. Double-click on "Xdmf3 Reader S"
3. Click Apply
4. Click on the Plot Over Line button
5. Click Apply
Then an empty plot appears.
![image](/uploads/7e8cb07488cf2b4eac5c298720957ff1/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/16822Slice crinkle cut option with multiple offsets2023-06-15T13:11:23-04:00Utkarsh AyachitSlice crinkle cut option with multiple offsetsIt only shows one of the slices if the crinkle cut is enabled but all of the slice offsets if they are not.It only shows one of the slices if the crinkle cut is enabled but all of the slice offsets if they are not.W. Alan ScottW. Alan Scotthttps://gitlab.kitware.com/paraview/paraview/-/issues/175372d plots Axis Range Min/Max is inverted2023-06-15T13:08:36-04:00W. Alan Scott2d plots Axis Range Min/Max is invertedThe locations of the Max and Min for the Use Custom Range/ Axis Range Minimum and Maximum are inverted. Generally you see the maximum item above the minimum. Please invert and correct their location in the properties tab.
* ParaView 5...The locations of the Max and Min for the Use Custom Range/ Axis Range Minimum and Maximum are inverted. Generally you see the maximum item above the minimum. Please invert and correct their location in the properties tab.
* ParaView 5.4.0, Linux, local server.
* Open can.exo, all vars on, apply.
* Plot over line. Apply.
* Now, slide down on the properties tab. Select Left Axis Use Custom Range.
* Left Axis Range Minimum is above Left Axis Range Maximum. Please invert them for Left, Right, Top and Bottom.https://gitlab.kitware.com/paraview/paraview/-/issues/17590Slice view crashes with Box source2023-06-15T12:32:27-04:00Cory Quammencory.quammen@kitware.comSlice view crashes with Box source**Version**
ParaView 5.4.0 Kitware binaries on macOS
**Steps to reproduce:**
* Launch paraview
* Add Box source
* Create Slice View
* Turn visibility of Box source on in the Slice view
* Adjust the sliders. It may take a few adjustmen...**Version**
ParaView 5.4.0 Kitware binaries on macOS
**Steps to reproduce:**
* Launch paraview
* Add Box source
* Create Slice View
* Turn visibility of Box source on in the Slice view
* Adjust the sliders. It may take a few adjustments of all three sliders, some to the extremes of the sliders, for the crash to happen.
**Stack trace**
0 libsystem_platform.dylib 0x00007fff9fa99c49 _platform_bzero$VARIANT$Haswell + 41
1 libvtkCommonDataModel-pv5.4.1.dylib 0x000000010499b252 vtkPointLocator::InitPointInsertion(vtkPoints*, double const*, long long) + 866
2 libvtkFiltersCore-pv5.4.1.dylib 0x0000000104392486 vtkCutter::DataSetCutter(vtkDataSet*, vtkPolyData*) + 790
3 libvtkFiltersCore-pv5.4.1.dylib 0x000000010439121a vtkCutter::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 954
4 libvtkCommonExecutionModel-pv5.4.1.dylib 0x00000001047382a5 vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 69
5 libvtkCommonExecutionModel-pv5.4.1.dylib 0x0000000104732a9d vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 61
6 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010472e12b vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 107
7 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010473222c vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1228
8 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010475f99f vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 895
9 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010475fd5e vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 254
10 libvtkPVClientServerCoreRendering-pv5.4.1.dylib 0x00000001066829d0 tbb::interface7::internal::start_for<tbb::blocked_range<long long>, vtk::detail::smp::FuncCall<vtk::detail::smp::vtkSMPTools_FunctorInternal<(anonymous namespace)::CutWorker, false> >, tbb::auto_partitioner const>::execute() + 1568
11 libtbb.dylib 0x000000010625c4ad tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) + 493
12 libtbb.dylib 0x000000010625ab1d tbb::internal::generic_scheduler::spawn_root_and_wait(tbb::task&, tbb::task*&) + 301
13 libvtkPVClientServerCoreRendering-pv5.4.1.dylib 0x0000000106681e3a vtkThreeSliceFilter::Process(vtkDataSet*, vtkPolyData**, unsigned int) + 778
14 libvtkPVClientServerCoreRendering-pv5.4.1.dylib 0x0000000106681a9a vtkThreeSliceFilter::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 410
15 libvtkCommonExecutionModel-pv5.4.1.dylib 0x00000001047382a5 vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 69
16 libvtkCommonExecutionModel-pv5.4.1.dylib 0x0000000104732a9d vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 61
17 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010472e12b vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 107
18 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010473222c vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1228
19 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010475f99f vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 895
20 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010475fd5e vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 254
21 libvtkPVClientServerCoreRendering-pv5.4.1.dylib 0x0000000106626e18 (anonymous namespace)::vtkGSRGeometryFilter::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1320
22 libvtkCommonExecutionModel-pv5.4.1.dylib 0x00000001047382a5 vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 69
23 libvtkCommonExecutionModel-pv5.4.1.dylib 0x0000000104732a9d vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 61
24 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010472e12b vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 107
25 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010473222c vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1228
26 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010475f99f vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 895
27 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010472f092 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 290
28 libvtkCommonExecutionModel-pv5.4.1.dylib 0x0000000104732070 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 784
29 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010475f99f vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 895
30 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010472f092 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 290
31 libvtkCommonExecutionModel-pv5.4.1.dylib 0x0000000104732070 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 784
32 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010475f99f vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 895
33 libvtkCommonExecutionModel-pv5.4.1.dylib 0x000000010475fd5e vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 254
34 libvtkPVClientServerCoreRendering-pv5.4.1.dylib 0x0000000106622b4d vtkGeometryRepresentation::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 381