ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2022-11-25T17:56:35-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/21673Add option to write time steps to EnSight case writer2022-11-25T17:56:35-05:00Tomáš KarabelaAdd option to write time steps to EnSight case writerSaving to EnSight Gold from Paraview currently only saves the current timestep. It would be useful to add a "Write Time Steps" option to save all timesteps (and possibly another option to only write the geometry once, if it is constant)....Saving to EnSight Gold from Paraview currently only saves the current timestep. It would be useful to add a "Write Time Steps" option to save all timesteps (and possibly another option to only write the geometry once, if it is constant).
The underlying `vtkEnSightWriter` class is capable of writing multiple timesteps with constant or transient geometry. It can be achieved like this:
```
writer->SetInputData(...);
writer->SetTimeStep(0);
writer->Write();
writer->SetInputData(...);
writer->SetTimeStep(1);
writer->Write();
writer->SetInputData(...);
writer->SetTimeStep(2);
writer->Write();
writer->WriteCaseFile(3); // number of steps
```
It does not support doing this via `vtkStreamingDemandDrivenPipeline`.https://gitlab.kitware.com/paraview/paraview/-/issues/21672EnSight case writer writes full data for all processes2022-11-25T18:27:35-05:00Tomáš KarabelaEnSight case writer writes full data for all processesWhen running in parallel, saving to EnSight Gold writes full geometry from each process, instead of just writing the piece that belongs to that process.
**Steps to reproduce**
- start a parallel `pvserver`, eg:
```
cd ParaView-5.11.0-...When running in parallel, saving to EnSight Gold writes full geometry from each process, instead of just writing the piece that belongs to that process.
**Steps to reproduce**
- start a parallel `pvserver`, eg:
```
cd ParaView-5.11.0-MPI-Linux-Python3.9-x86_64
./mpiexec -np 4 ./pvserver
```
- connect to the server
- create Unstructured Cell Types source
- File > Save Data... > EnSight File, save as `test.case`
This creates four identical sets of EnSight Gold geometry and variable files (with .case files currently missing, see #18242):
```
57K test.0.00000.geo
5,5K test.0.00000_n.DistanceToCenter
5,5K test.0.00000_n.Polynomial
57K test.1.00000.geo
5,5K test.1.00000_n.DistanceToCenter
5,5K test.1.00000_n.Polynomial
57K test.2.00000.geo
5,5K test.2.00000_n.DistanceToCenter
5,5K test.2.00000_n.Polynomial
57K test.3.00000.geo
5,5K test.3.00000_n.DistanceToCenter
5,5K test.3.00000_n.Polynomial
```
Each of these contains the full mesh, which can at the moment be checked by creating the .case file manually and loading it into Paraview:
```
cat <<EOF >test.0.case
FORMAT
type: ensight gold
GEOMETRY
model: test.0.00000.geo
# variable files omitted
EOF
```
When saving the same Unstructured Cell Types source but choosing to save it as Parallel VTK XML Unstructured Grid (.pvtu), the individual .vtu pieces only contain part of the original dataset:
```
567 test.pvtu
28K test/test_0.vtu
28K test/test_1.vtu
28K test/test_2.vtu
28K test/test_3.vtu
```
This can be checked by reading the indiviudal .vtu file into Paraview. It's also apparent when comparing the filesize with a .vtu file written from serial Paraview for the same dataset:
```
105K test-serial.vtu
```
![Screenshot_from_2022-11-25_23-32-58](/uploads/b778292f5fb49e0b5f7d965e50925706/Screenshot_from_2022-11-25_23-32-58.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21669Make `--venv` a pvpython/pvbatch/paraview CLI argument2023-03-06T10:36:25-05:00Utkarsh AyachitMake `--venv` a pvpython/pvbatch/paraview CLI argumentCurrently, python scripts can import [`paraview.web.venv`](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Web/Python/paraview/web/venv.py) to setup module paths etc. to load packages from a virualenv. The current approach req...Currently, python scripts can import [`paraview.web.venv`](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Web/Python/paraview/web/venv.py) to setup module paths etc. to load packages from a virualenv. The current approach requires that `import paraview.web.venv` is done in the Python script that pvpython/pvbatch executes, which makes it impossible for the Python script itself to be a part of the virtual env. For example, I have a nice Python package with Viz pipelines that I pip install in a venv. I simply want to run that package with pvpython as follows:
```sh
pvpython -m my_nice_package
```
It's not possible currently. Hence, I propose we move the venv handling to pvpython/pvbatch itself. Thus, make the following work:
```sh
pvpython --venv /.../venv -m my_nice_package
```
It makes sense to add this cmd-line arg to all executables that support Python including the server executables.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21668building Paraview 5.11 on Fedora 372022-12-06T15:57:00-05:00Nabil G.building Paraview 5.11 on Fedora 37dear experts,
while trying to build Paraview 5.11 on Fedora 37, I hit one issue related to mpi4py.
Before trying to patch what needs to be patched, do you know whether there is already some branch which supports Python 3.11 ?
```
Singul...dear experts,
while trying to build Paraview 5.11 on Fedora 37, I hit one issue related to mpi4py.
Before trying to patch what needs to be patched, do you know whether there is already some branch which supports Python 3.11 ?
```
Singularity> lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: Fedora
Description: Fedora release 37 (Thirty Seven)
Release: 37
Codename: ThirtySeven
Singularity> python --version
Python 3.11.0
```
Regardshttps://gitlab.kitware.com/paraview/paraview/-/issues/21665OpenVDB reader on multiple mpi ranks crash2022-11-21T03:14:38-05:00Timothee ChabatOpenVDB reader on multiple mpi ranks crashstep to reproduce :
- `mpiexec -n X pvserver` , X > 1
- connect to the server
- load a `.vdb` file, apply : crash
initially reported here https://discourse.paraview.org/t/egl-pvserver-5-11-0-mpi-and-openvdb/10817
reproduced on master...step to reproduce :
- `mpiexec -n X pvserver` , X > 1
- connect to the server
- load a `.vdb` file, apply : crash
initially reported here https://discourse.paraview.org/t/egl-pvserver-5-11-0-mpi-and-openvdb/10817
reproduced on master (6011921f5be11c68c79d492cc276488d006f259f) and 5.11.0 binaryhttps://gitlab.kitware.com/paraview/paraview/-/issues/21663OpenVKL initialization error with ospray on master2023-02-06T09:58:38-05:00Lucas GivordOpenVKL initialization error with ospray on masterWhen launching paraview with `VTK_ENABLE_OSPRAY` set to `ON`, we have this error :
```
[openvkl] INITIALIZATION ERROR: could not open module lib openvkl_module_cpu_device: libopenvkl_module_cpu_device_4.so.1: cannot open shared object f...When launching paraview with `VTK_ENABLE_OSPRAY` set to `ON`, we have this error :
```
[openvkl] INITIALIZATION ERROR: could not open module lib openvkl_module_cpu_device: libopenvkl_module_cpu_device_4.so.1: cannot open shared object file: No such file or directory
[openvkl] WARNING: unrecognized device type 'cpu_16'.
[openvkl] INITIALIZATION ERROR: Could not find device of type: cpu_16. Make sure you have the correct VKL libraries linked.
```
@timothee.chabat @charles.gueunethttps://gitlab.kitware.com/paraview/paraview/-/issues/21662mesa warning while running paraview for openfoam2022-12-14T09:12:59-05:00shir levimesa warning while running paraview for openfoamhey, i get this messseng in ubuntu after writing ParaView how can i fix it?
**QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shir'
Mesa warning: Window 2097160 has no colormap!
Mesa warning: Window 2097163 has no...hey, i get this messseng in ubuntu after writing ParaView how can i fix it?
**QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shir'
Mesa warning: Window 2097160 has no colormap!
Mesa warning: Window 2097163 has no colormap!
Mesa warning: Window 2097170 has no colormap!**
the paraview opens and seem to work fine but reacts really slow.
i have windows 11 (i don't familiar with using ubuntu workspace so I will appreciate any help and simple explanation.https://gitlab.kitware.com/paraview/paraview/-/issues/21661Incorrect search path in the Plugin manager2022-11-21T02:52:53-05:00NicolasBIncorrect search path in the Plugin managerFor some reason, the search path for the plugin indicates `bin/plugins` instead of `Plugins` (relatitvely to the ParaView path)
![PluginManager](/uploads/afdafd097b8f00d9d76c20e7824bbe22/PluginManager.png)For some reason, the search path for the plugin indicates `bin/plugins` instead of `Plugins` (relatitvely to the ParaView path)
![PluginManager](/uploads/afdafd097b8f00d9d76c20e7824bbe22/PluginManager.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21660Unsupported topology sphere2024-03-07T20:23:54-05:00W. Alan ScottUnsupported topology sphereMy user has a dataset that is failing. He wrote this up with the following comments:
The SIERRA/SM code represents “rigid body” blocks using a point/element of type “sphere.” Opening a file with such element types produces this messag...My user has a dataset that is failing. He wrote this up with the following comments:
The SIERRA/SM code represents “rigid body” blocks using a point/element of type “sphere.” Opening a file with such element types produces this message in Paraview 5.11.0-RC1:
```
( 14.973s) [paraview ] vtkIOSSUtilities.cxx:393 ERR| Element of topology 'sphere' with 1 nodes is not supported.
( 14.974s) [paraview ] vtkIOSSReader.cxx:2686 ERR| Error reading entity block (or set) named 'rigidbodyoutputpart' from '/snip/global.e'; skipping. Details: Unsupported topology sphere
```
As a result, the location and fields defined on this part can’t be visualized.
* Linux, master (and 5.11.0-RC2), builtin server.
* Open gears-DoNotRelease.e. Only turn on block ridigbodyoutputpart. Apply
An error is seen in the terminal window. Further, as stated, information tab shows no cells or points.
To see what it should look like, turn on and use the LegacyExodusReader in Tools/ Manage Plugins. You should see 5 points. (If needed, do a Reset and rubber band select of the screen. You will see them. Further, you can see them in the information tab.
I will send data to Cory. Data is gears-DoNotRelease.e. OK to share with anyone at Kitware.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21658Labels containing LaTeX rendered with the wrong font2022-11-16T04:38:36-05:00Massimiliano LeoniLabels containing LaTeX rendered with the wrong fontWhen adding LaTeX content to a label [with dollar signs] Paraview will correctly render the LaTeX portion of the label. However, the whole label is then rendered with a font of Paraview's choice, not with the one the user wants.
I attach...When adding LaTeX content to a label [with dollar signs] Paraview will correctly render the LaTeX portion of the label. However, the whole label is then rendered with a font of Paraview's choice, not with the one the user wants.
I attach a video that demonstrates the issue.
[labelBug.mkv](/uploads/fd4a530d358c43e64772d7e8415f97a9/vokoscreen-2022-11-15_18-13-16.mkv)https://gitlab.kitware.com/paraview/paraview/-/issues/21657CI: pv.StreamLinesRepresentationColor test is flaky2022-11-15T10:20:55-05:00Mathieu Westphal (Kitware)CI: pv.StreamLinesRepresentationColor test is flakyVery occasionnaly, the pv.StreamLinesRepresentationColor fails on fedora with:
![a](/uploads/c4b326cd6f75cfcbce5e8d00c6d71a77/a.png)
Is has been excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6016Very occasionnaly, the pv.StreamLinesRepresentationColor fails on fedora with:
![a](/uploads/c4b326cd6f75cfcbce5e8d00c6d71a77/a.png)
Is has been excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6016https://gitlab.kitware.com/paraview/paraview/-/issues/21656CI: pv.ShaderReplacements test is flaky2022-11-15T10:20:59-05:00Mathieu Westphal (Kitware)CI: pv.ShaderReplacements test is flakyVery occasionnaly, the pv.ShaderReplacements fails on fedora with:
![a](/uploads/e5c8cef777c4a4ca415ab8a422a1745f/a.png)
It has been excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6016
Note: the pvcs vers...Very occasionnaly, the pv.ShaderReplacements fails on fedora with:
![a](/uploads/e5c8cef777c4a4ca415ab8a422a1745f/a.png)
It has been excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6016
Note: the pvcs version does not seems to failhttps://gitlab.kitware.com/paraview/paraview/-/issues/21650Multiple line widget shows strange behavior2022-11-10T04:55:32-05:00Mathieu Westphal (Kitware)Multiple line widget shows strange behaviorMultiple line widget shows strange behavior
- run ParaView
- Wavelet, Apply
- PlotOverLine, Apply
- Select Wavelet
- PlotOverLine, Apply
- close chart view
- select PlotOverLine1
- press P multiples times
- plot over lines filters are s...Multiple line widget shows strange behavior
- run ParaView
- Wavelet, Apply
- PlotOverLine, Apply
- Select Wavelet
- PlotOverLine, Apply
- close chart view
- select PlotOverLine1
- press P multiples times
- plot over lines filters are selected one after another, looks unexepected
@dcthomp @timothee.chabathttps://gitlab.kitware.com/paraview/paraview/-/issues/21648Save Screenshot fails in Catalyst trace.2024-03-07T20:23:54-05:00W. Alan ScottSave Screenshot fails in Catalyst trace.My user created a Catalyst State file. It created three renderviews. He did an extract image for each of the renderviews, which worked correctly. Next, he used a trace to get the commands to save screenshot for all three renderviews a...My user created a Catalyst State file. It created three renderviews. He did an extract image for each of the renderviews, which worked correctly. Next, he used a trace to get the commands to save screenshot for all three renderviews at one time, cut and pasted that into the Catalyst State file, and ran that. Catalyst said the .png could not be written.
Error was:
```
[pvbatch.0 ] vtkPNGWriter.cxx:254 ERR| vtkPNGWriter (0x2a144d20): Unable to open file ./catalyst_output/panel_
{timestep:06d} {camera}
.png
[pvbatch.0 ] vtkImageWriter.cxx:481 ERR| vtkPNGWriter (0x2a144d20): Ran out of disk space; deleting file(s) already written
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21647Catalyst 2 scripts need to account for data operations internal to readers2024-03-07T20:23:54-05:00Cory Quammencory.quammen@kitware.comCatalyst 2 scripts need to account for data operations internal to readersWhen creating Catalyst scripts from readers that perform certain data operations such as selecting only some blocks to read and applying a displacement field to points, we are missing those data operations in the recorded script. When it...When creating Catalyst scripts from readers that perform certain data operations such as selecting only some blocks to read and applying a displacement field to points, we are missing those data operations in the recorded script. When it is used in a Catalyst run, the data comes in untransformed, leading to incorrect data. We need to capture the data transformations inside the reader in the Catalyst pipeline somehow.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21645Reset Session will not Reset your session when in interactive mode with pvpython2022-11-04T16:21:22-04:00Phil SmithReset Session will not Reset your session when in interactive mode with pvpythonResetSession() command will not do anything when performed in interactive mode via pypython. To duplicate:
Using ParaView 5.11.0-RC2, Linux
Launch pvpython via the cmd line
Enter the following within pvpython:
- from paraview.simple impo...ResetSession() command will not do anything when performed in interactive mode via pypython. To duplicate:
Using ParaView 5.11.0-RC2, Linux
Launch pvpython via the cmd line
Enter the following within pvpython:
- from paraview.simple import *
- sphere = Sphere()
- Show()
- Render()
- ResetSession() -- At this point the "Render Window" should be blank or disappear, but the Sphere is still showing.
- box=Box()
- Render() --It shows the box
- Hide(box) -- Sphere is showing again
- Hide(sphere) -- "Render Window" is blank. Good
- Show(sphere) -- "Render Window" shows the Sphere?? It should not even know about the Sphere, because of the ResetSession command
I did try a using both pvbatch and pvpython while using a file as the argument and ResetSession worked fine that way, so this will be a nice to have feature.https://gitlab.kitware.com/paraview/paraview/-/issues/21643On Windows pvpython window freezes when moved2022-11-03T09:07:12-04:00Phil SmithOn Windows pvpython window freezes when movedThis was tested with windows paraview v5.11.0-RC2
If a window is created by pvpython interactively, then the window is moved, pvpython can no longer control the widow. Here is the test case:
- Launch pvpython on Windows( I used Windows10...This was tested with windows paraview v5.11.0-RC2
If a window is created by pvpython interactively, then the window is moved, pvpython can no longer control the widow. Here is the test case:
- Launch pvpython on Windows( I used Windows10 cmd line)
- from paraview.simple import *
- sphere = Sphere()
- Show()
- Render()
- Move the window
- shrink = Shrink()
- Hide(sphere)
- Show()
- Render()....It will not hide the sphere
If the mouse is placed within the window the spinning disk appears, You can move the window again by grabbing the top, but it still will not respond. You can exit the window by clicking on the X in the top right corner, or typing exit() in pvpython. It will also exit pvpython if exit() it typedhttps://gitlab.kitware.com/paraview/paraview/-/issues/216413DGlyphs Cylinder Orientation Direction Vector Bug2022-11-15T09:58:36-05:00František Prinz3DGlyphs Cylinder Orientation Direction Vector BugThe orientation vector in Orientation Mode Direction for Glyph Type Cylinder is not ident with the symmetrical axis of revolution but perpendicular to it. I suppose there is a bug because another types (Cone, Arrow) are defined correctly...The orientation vector in Orientation Mode Direction for Glyph Type Cylinder is not ident with the symmetrical axis of revolution but perpendicular to it. I suppose there is a bug because another types (Cone, Arrow) are defined correctly paralel axis of revolution.
Could you please fix it?
Thankshttps://gitlab.kitware.com/paraview/paraview/-/issues/21640[5.11.0-RC2] Load State is different than File > Recent Files > Load *.pvsm file2022-11-02T22:18:09-04:00Menno Deij - van Rijswijk[5.11.0-RC2] Load State is different than File > Recent Files > Load *.pvsm fileIf I choose File > Load State ... and select a state *.pvsm file, a second question pops up asking me how to select the files (from file, select from directory, select files).
If I choose File > Recent Files > and select the same state ...If I choose File > Load State ... and select a state *.pvsm file, a second question pops up asking me how to select the files (from file, select from directory, select files).
If I choose File > Recent Files > and select the same state *.pvsm file, the second question does not pop up, and the state immediately loads with the "files from file".
It would be nice if loading a state file from the MRU list has the same behavior, i.e. asking me where I would like to get my files from.https://gitlab.kitware.com/paraview/paraview/-/issues/21639GenerateTimeSteps + ParticleTracer segfaults2022-11-11T04:52:44-05:00Mathieu Westphal (Kitware)GenerateTimeSteps + ParticleTracer segfaultsUsing a ParticleTracer after GenerateTimeSteps can segfaults.
Steps to reproduce:
- run ParaView
- Open [foam.vtu](https://send.kitware.io/download.php?id=1392&token=5D9r4QbLDjLhEejt81wDd5vc7r6mjTw3), Apply
- Generate timesteps, generat...Using a ParticleTracer after GenerateTimeSteps can segfaults.
Steps to reproduce:
- run ParaView
- Open [foam.vtu](https://send.kitware.io/download.php?id=1392&token=5D9r4QbLDjLhEejt81wDd5vc7r6mjTw3), Apply
- Generate timesteps, generate 10 ts, Apply
- Create a point source, -19, 100, 80, Apply
- ParticleTracer on foam.vtu, point source as seed, Apply
- Play animation back and forth until segfault
```
Thread 1 "paraview" received signal SIGSEGV, Segmentation fault.
0x00007fffd9670675 in vtkParticleTracerBase::CalculateVorticity (this=0x55556680b340, cell=0x0, pcoords=0x7fffffffa250, cellVectors=0x5555660fd1f0, vorticity=0x7fffffffa270) at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1537
1537 cell->Derivatives(0, pcoords, cellVel, 3, derivs);
(gdb) bt
#0 0x00007fffd9670675 in vtkParticleTracerBase::CalculateVorticity (this=0x55556680b340, cell=0x0, pcoords=0x7fffffffa250,
cellVectors=0x5555660fd1f0, vorticity=0x7fffffffa270)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1537
#1 0x00007fffd967167c in vtkParticleTracerBase::SetParticle (this=0x55556680b340, info=..., velocity=0x7fffffffaab0,
interpolator=0x555568605da0, particleId=0, cellVectors=0x5555660fd1f0)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1777
#2 0x00007fffd966f9e5 in vtkParticleTracerBase::IntegrateParticle (this=0x55556680b340,
it={CurrentPosition = {x = {-16.698808670043945, 93.088241577148438, 83.561920166015625, 0}}, CachedDataSetId = {0, 0}, CachedCellId = {-1, -1}, LocationState = 0, SourceID = 0, TimeStepAge = 1, InjectedPointId = 4, InjectedStepId = 0, UniqueParticleId = 0, SimulationTime = 0, ErrorCode = 0, age = 0, rotation = 0, angularVel = -8.21364447e-05, time = 0, speed = 10.0119152, PointId = 0, TailPointId = -1}, currentTime=0, targetTime=0, integrator=0x555566839d50, interpolator=0x555568605da0,
cellVectors=0x5555660fd1f0, particleCount=std::atomic<long long> = { 1 }, eraseMutex=..., sequential=true)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1407
#3 0x00007fffd9672dbd in vtkParticleTracerBaseNamespace::ParticleTracerFunctor::operator() (this=0x7fffffffadd0, begin=0,
end=4) at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:844
#4 0x00007fffd966db67 in vtkParticleTracerBase::Execute (this=0x55556680b340, inputVector=0x5555665da620)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1047
#5 0x00007fffd9ec6f86 in vtkPParticleTracerBase::Execute (this=0x55556680b340, inputVector=0x5555665da620)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/ParallelFlowPaths/vtkPParticleTracerBase.cxx:75
#6 0x00007fffd966ebca in vtkParticleTracerBase::RequestData (this=0x55556680b340, request=0x555566857050,
inputVector=0x5555665da620, outputVector=0x55556684fa80)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1192
#7 0x00007fffd966710e in vtkParticleTracerBase::ProcessRequest (this=0x55556680b340, request=0x555566857050,
inputVector=0x5555665da620, outputVector=0x55556684fa80)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:230
#8 0x00007ffff068a64d in vtkExecutive::CallAlgorithm (this=0x55556684f970, request=0x555566857050, direction=1,
inInfo=0x5555665da620, outInfo=0x55556684fa80)
at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkExecutive.cxx:735
#9 0x00007ffff06809da in vtkDemandDrivenPipeline::ExecuteData (this=0x55556684f970, request=0x555566857050,
inInfo=0x5555665da620, outInfo=0x55556684fa80)
at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:462
#10 0x00007ffff0673bd9 in vtkCompositeDataPipeline::ExecuteData (this=0x55556684f970, request=0x555566857050,
inInfoVec=0x5555665da620, outInfoVec=0x55556684fa80)
at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx:163
```