ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-01-24T05:18:49-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/22462MaskPoints hangs on non-distributed composite dataset collection in distribut...2024-01-24T05:18:49-05:00Mathieu Westphal (Kitware)MaskPoints hangs on non-distributed composite dataset collection in distributed contextMaskPoints hangs on non-distributed partitioned dataset collection in distributed context.
Unable to reproduce when merging the blocks or in non-distributed context.
The issue is not with the MaskPoint filter but with the composite pip...MaskPoints hangs on non-distributed partitioned dataset collection in distributed context.
Unable to reproduce when merging the blocks or in non-distributed context.
The issue is not with the MaskPoint filter but with the composite pipeline logic.
Steps to reproduce:
- run distributed pvserver
- run ParaView
- open [helmet.vtpc](/uploads/79f91a495d8c16cc64c0a7cb9205fbbd/helmet.tgz), Apply
- MaskPoints, Apply
- Hangshttps://gitlab.kitware.com/paraview/paraview/-/issues/22460Add support to control Catalyst 2 Live from the GUI2024-01-24T05:20:38-05:00Juan Jose CasafrancaAdd support to control Catalyst 2 Live from the GUIRight now the only way to control a running simulation with Catalyst from the ParaView GUI is through the Pause/Breakpoints functionality, and the breakpoints are actually broken (https://gitlab.kitware.com/paraview/paraview/-/issues/217...Right now the only way to control a running simulation with Catalyst from the ParaView GUI is through the Pause/Breakpoints functionality, and the breakpoints are actually broken (https://gitlab.kitware.com/paraview/paraview/-/issues/21735).
However, in some cases, its desireable to run simulations steps by step, for example, if you are analyzing the simulations results and debugging the simulation code side by side.
For such cases, it would be nice to have buttons to Pause, Step and Run the simulation, similar to how a code debugger work. Of course this would complement the breakpoint functionality.
Probably this buttons should also be visible directly on the GUI toolbars when Catalyst is connected, not hidden inside a menu.https://gitlab.kitware.com/paraview/paraview/-/issues/22459Catalyst 2 Live Visualization can't handle fast simulations2024-01-23T05:44:00-05:00Juan Jose CasafrancaCatalyst 2 Live Visualization can't handle fast simulationsI am trying to use Catalyst for my simulation engine. The simulations I am running are fast, each timestep tooks just around 20ms, and I want to visualize the simulation in realtime using Catalyst Live in ParaView GUI.
However, ParaVie...I am trying to use Catalyst for my simulation engine. The simulations I am running are fast, each timestep tooks just around 20ms, and I want to visualize the simulation in realtime using Catalyst Live in ParaView GUI.
However, ParaView GUI freezes when Catalyst sends data faster than it can be processed by the GUI. Simulation continues just fine, and the Catalyst script still runs its pipeline, but in the GUI I can't see any updated until the simulation finishes and Catalyst stops sending new data to the GUI.
This is easily reproducible with the Catalyst examples in Paraview repo, as already commented here: https://discourse.paraview.org/t/problems-with-catalyst2-and-paraview-live-visualization/11401/3
https://discourse.paraview.org/t/catalyst-super-slow-with-live-visualization/13694/8
If I add a sleep(0.5) in the Catalyst script in the catalyst_execute function, then the GUI has enough time to process all the data it has received before it receives new data, and the GUI doesn't freezehttps://gitlab.kitware.com/paraview/paraview/-/issues/22458add support for ProgrammableConduitSource2024-01-23T09:48:29-05:00Utkarsh Ayachitadd support for ProgrammableConduitSourcerefer to the discussion here for details: https://discourse.paraview.org/t/supporting-arbitrary-schemas-with-programmable-conduit-based-producer/13759refer to the discussion here for details: https://discourse.paraview.org/t/supporting-arbitrary-schemas-with-programmable-conduit-based-producer/13759https://gitlab.kitware.com/paraview/paraview/-/issues/22456Loading a state with a bp file [ADIOS2VTXReader] is broken2024-01-19T03:27:57-05:00Massimiliano LeoniLoading a state with a bp file [ADIOS2VTXReader] is brokenHello! I noticed that loading a state that involves an ADIOS2VTXReader fails to load the Data arrays of the file.
UPDATE: this only happens for a VTX file with multiple time steps for which the mesh was saved only once [as opposed to at...Hello! I noticed that loading a state that involves an ADIOS2VTXReader fails to load the Data arrays of the file.
UPDATE: this only happens for a VTX file with multiple time steps for which the mesh was saved only once [as opposed to at every time step] AND if the saved state does not load the initial time step.
Furthermore, if you do load a file with only one mesh for multiple time steps at a time step for which there is no mesh but then go to a time step at which there is a mesh, Paraview finds the Data arrays and everything starts working fine.
Step to reproduce:
1. Open Paraview and load bp file with an ADIOS2VTXReader that has multiple time steps and that reuses the mesh
2. Save state at a time for which there is no mesh
3. Reset session
4. Load saved state
You should get an error that a certain data array has no fields. In the "Information" tab you can verify that no Data arrays are present in the bp file.
Using Paraview latest compiled from source.https://gitlab.kitware.com/paraview/paraview/-/issues/22454Rescale to Visible Data Range doesn't work with multiple sources2024-01-17T07:00:13-05:00Andrew BauerRescale to Visible Data Range doesn't work with multiple sourcesHi,
`Rescale to Visible Data Range` doesn't seem to work properly when there are multiple sources with different data ranges of the same field. To reproduce do the following:
1. Load [multi_wavelet.pvsm](/uploads/d2545c9b87743c6a6ead9d1...Hi,
`Rescale to Visible Data Range` doesn't seem to work properly when there are multiple sources with different data ranges of the same field. To reproduce do the following:
1. Load [multi_wavelet.pvsm](/uploads/d2545c9b87743c6a6ead9d1abbec3519/multi_wavelet.pvsm)
2. Click on `Wavelet1` in the pipeline browser and then click on `Rescale to Visible Data Range`
3. Click on `Wavelet2` in the pipeline browser
This changes the LUT range. This was found using ParaView 5.12.0-RC1 downloaded from the ParaView download site on a Linux machine.https://gitlab.kitware.com/paraview/paraview/-/issues/22450ParaView 5.12.0-RC2: "Cache Geometry for Animation" is incorrect if enabled i...2024-01-16T06:02:06-05:00Cory Quammencory.quammen@kitware.comParaView 5.12.0-RC2: "Cache Geometry for Animation" is incorrect if enabled in the middle of a time seriesI see that the cached time steps with geometry caching enabled and animation playback running can show incorrect data at certain times.
How to reproduce:
* Run ParaView, builtin server
* Load `can.ex2`
* Change the timestep to 20
* Ope...I see that the cached time steps with geometry caching enabled and animation playback running can show incorrect data at certain times.
How to reproduce:
* Run ParaView, builtin server
* Load `can.ex2`
* Change the timestep to 20
* Open Settings, General, enable advanced button.
* Click to enable **Cache Geometry for Animation**.
* Turn on animation looping.
* Now play through the animation.
Notice that when you play the animation, cache data at one or more timesteps is incorrect.https://gitlab.kitware.com/paraview/paraview/-/issues/22446GLTF file support in ParaView is incomplete2024-01-15T09:23:44-05:00Jaswant Panchumarti (Kitware)GLTF file support in ParaView is incomplete**vtkGLTFReader**
- Available in ParaView with File -> Open (*.gltf, *.glb)
- Loads each part of the mesh into a block of a composite dataset.
- Loads materials and textures, but cannot apply those on actor because this is a reader.
- Th...**vtkGLTFReader**
- Available in ParaView with File -> Open (*.gltf, *.glb)
- Loads each part of the mesh into a block of a composite dataset.
- Loads materials and textures, but cannot apply those on actor because this is a reader.
- The composite polydata mapper needs to be aware of the material and texture description found in the field data of reader output. vtk/vtk!5735 does this in a new vtkGLTFMapper.
**vtkGLTFImporter**
- Not available in ParaView.
- Loads each part of the mesh into a vtkPolyData connected to a vtkActor through a vtkPolyDataMapper.
- Loads materials and textures, applies them on actors.
- PBR information is directly applied on actors.
- Bringing this to ParaView would imply constructing fake proxies to represent each actor. Composite actors (NOT composite datasets) are non trivial in ParaView pipeline browser because each element can have atmost one representation. A solution to this problem would allow us to import external scenes in ParaView.
- If this is being brought into ParaView, it would be nice to have a UI dialog that can choose which actors will be imported.
**vtkGLTFWriter**
- Not available in ParaView.
- Saves material and textures. It looks for specific arrays on the field data of the input dataset. From looking around in unit tests, it expects developers to populate the field data with material and texture file names.
- Meant as a lower level approach to writing GLTF files.
- Not bringing this to ParaView.
**vtkGLTFExporter**
- Available in ParaView with File -> Export Scene...
- Saves simple material numbers like strength, metallic factor, roughness factor and base color texture only. Does not save any other texture like normal map, occlusion map, etc.
- Saves all actors from the render window's renderers.
- There is a UI dialog that's shown when using this exporter. It's very basic and has 3 checkboxes. Add more capabilities to allow selective export of actors or textures.Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/22443Undefined symbol at runtime when compiling static python32024-01-11T09:46:05-05:00Loic TetrelUndefined symbol at runtime when compiling static python3HI,
I am having an error at runtime after compiling paraview with python:
```
./bin/paraview
./bin/paraview: symbol lookup error: [REDACTED]/paraview-test/build/bin/../lib/libvtkRenderingMatplotlib-pv5.11.so.1: undefined symbol: PyTupl...HI,
I am having an error at runtime after compiling paraview with python:
```
./bin/paraview
./bin/paraview: symbol lookup error: [REDACTED]/paraview-test/build/bin/../lib/libvtkRenderingMatplotlib-pv5.11.so.1: undefined symbol: PyTuple_Type
```
OS: ubuntu 20.04
On `master` at 53257ab20c6ec6bc42b7ad2dc9e4c28ec05a123a using:
```sh
cmake -DPARAVIEW_USE_PYTHON=ON -DPARAVIEW_USE_MPI=ON -DVTK_SMP_IMPLEMENTATION_TYPE=TBB -DCMAKE_BUILD_TYPE=Release ..
```
By default CMake find my locally compiled python in `usr/local` (which is static by default following [python doc](https://docs.python.org/3/using/unix.html#building-python)).
Working with python dynamic lib in `/usr` (shipped with ubuntu in `/usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0`). Dynamic lib is automatically used by CMake in that case.
```sh
-DPython3_EXECUTABLE=/usr/bin/python3
```
additional files:
[pv-python-dynamic.log](/uploads/95b2b291f56d66c5d59143cb3d7be9f8/pv-python-dynamic.log)
[pv-python-static.log](/uploads/a14555b36e4cd2a25ac973d3950a09c2/pv-python-static.log)
Thanks,https://gitlab.kitware.com/paraview/paraview/-/issues/22441Dash (-) ignored in selector'name2024-01-15T17:05:40-05:00Edoardo alinoviDash (-) ignored in selector'nameHello,
I just would like to flag a bug or at least I believe so. In vtkMultiblockDataSet, the dash inside names is ignored while using selectors.
For example:
my_filter.Selectors = ['test-1']
does the same selection as:
my_filter.Se...Hello,
I just would like to flag a bug or at least I believe so. In vtkMultiblockDataSet, the dash inside names is ignored while using selectors.
For example:
my_filter.Selectors = ['test-1']
does the same selection as:
my_filter.Selectors = [‘test1’]
The annoying thing is that if you have a data set with some coordinate in the name (e.g. x_-1, x_0, x_1), selecting only x_-1 would trigger the selection of the x_1 at the same time.
You can find this behaviour in the latest nightly version of Paraview.
Let me know if you know a workaroud to this for the time being :slight_smile:
Thank you very muchhttps://gitlab.kitware.com/paraview/paraview/-/issues/22440Record Test, Error message when cicking on plugin toolbar button2024-01-09T11:28:41-05:00Loïc GaillardRecord Test, Error message when cicking on plugin toolbar buttonWhen using the `Record Test` feature from paraview, if you click on a toolbar button from a loaded plugin, it will log an error message in the console : `
critical: Unable to to determine name for Object QAction(0x1fbf473f0b0) because ...When using the `Record Test` feature from paraview, if you click on a toolbar button from a loaded plugin, it will log an error message in the console : `
critical: Unable to to determine name for Object QAction(0x1fbf473f0b0) because a parent GUIMyToolBarPlugin(0x7ffeb04b2a80) is not a top-level widget. Name so far = "GUIMyToolBarPlugin0/MyToolBarActions/MyToolBarActions0/QAction0"`
Steps to reproduce :
- Choose a plugin from the paraview example folder, i tried with `GUIMyToolBar` & `SourceToolbar` (both logs the error).
- Load the plugin.
- Start recording a test
- Click on the plugin toolbar button
The issue seems related to QTesting.Loïc GaillardLoïc Gaillardhttps://gitlab.kitware.com/paraview/paraview/-/issues/22439Duplicate context-menu action in the edit menu of ParaView2024-01-08T04:50:35-05:00Mathieu Westphal (Kitware)Duplicate context-menu action in the edit menu of ParaViewThere are a few context menu actions that are not available in any actual menu of ParaView.
They should be added to the edit menu.
pipeline browser:
- Reload
- Change fileThere are a few context menu actions that are not available in any actual menu of ParaView.
They should be added to the edit menu.
pipeline browser:
- Reload
- Change filehttps://gitlab.kitware.com/paraview/paraview/-/issues/22438XRInterface plugin: Native interactions (scale, move, rotate) are not working...2024-01-09T13:23:28-05:00Mathieu Westphal (Kitware)XRInterface plugin: Native interactions (scale, move, rotate) are not working reliably with OpenVRNative grip interactions (https://www.kitware.com/navigation-basics-in-virtual-reality-with-paraview/) are not working reliably.
Sometimes they do, sometimes they dont.
Steps to reproduce:
- run ParaView, load XRInterface plugin
- Wav...Native grip interactions (https://www.kitware.com/navigation-basics-in-virtual-reality-with-paraview/) are not working reliably.
Sometimes they do, sometimes they dont.
Steps to reproduce:
- run ParaView, load XRInterface plugin
- Wavelet, Apply
- OpenVR, SendToXR
- Press A on both controllers and move hands (Valve Index Grip interactions)
- Not working
- If working, repeat until it does not work
- In my tests, it worked 3/10 times roughly
Notes:
- Works perfectly with OpenXR
- **This is a reggresion!** broken between def2b450a8 and 19627031fehttps://gitlab.kitware.com/paraview/paraview/-/issues/22437XRInterface: Navigation panel misplaced with OpenXR, regression2024-01-03T05:59:36-05:00Mathieu Westphal (Kitware)XRInterface: Navigation panel misplaced with OpenXR, regressionNavigation panel is not placed on the left controller as expected, but instead seems to be placed on the ground.
The navigation info are correct though.
Steps to reproduce:
- run ParaView, load XRInterface plugin
- OpenXR, SendToXR
...Navigation panel is not placed on the left controller as expected, but instead seems to be placed on the ground.
The navigation info are correct though.
Steps to reproduce:
- run ParaView, load XRInterface plugin
- OpenXR, SendToXR
- Press B, Widgets, Show navigation panel
- Navigation panel is misplaced
Notes:
- Works with OpenVR
- **this is a regression**! broken between 5.11.1 and 19627031fehttps://gitlab.kitware.com/paraview/paraview/-/issues/22434OBJ Loader does not open time series correctly2024-01-03T03:44:50-05:00Micha PfeifferOBJ Loader does not open time series correctlyLoading a time series of .obj files does not work for me.
The .obj files are correctly collapsed as a group in the file dialogue, but after loading only the first file seems to really be opened.
The files are named correctly (surface_f1...Loading a time series of .obj files does not work for me.
The .obj files are correctly collapsed as a group in the file dialogue, but after loading only the first file seems to really be opened.
The files are named correctly (surface_f1.obj, surface_f2.obj ...) and the same process works fine with .vtu files and .stl files.
Similar bug report (where the only workaround was to convert to .vtk):
https://discourse.paraview.org/t/how-to-open-a-group-of-obj-files/8672/8
Paraview version: 5.12.0-RC1
Ubuntu version: 20.04https://gitlab.kitware.com/paraview/paraview/-/issues/22433ExtractBlock is not able to extract block with identical names2024-01-03T03:49:18-05:00farensheepExtractBlock is not able to extract block with identical namesExtractBlock let user select block to extract but if the block of the same name, all blocks will be extracted.
Steps to reproduce:
- Open [samename.vtm](/uploads/01846bd1dbca718df398eb463e1053ed/samename.tgz), Apply
- Filters -> Extr...ExtractBlock let user select block to extract but if the block of the same name, all blocks will be extracted.
Steps to reproduce:
- Open [samename.vtm](/uploads/01846bd1dbca718df398eb463e1053ed/samename.tgz), Apply
- Filters -> ExtractBlock
- Select a single block, apply
- All blocks are extracted
================= Original issue below:
Hi,
I am trying to use paraview to process the results of the Fire Dynamics Simulator (FDS). Recently, a new reader has been implemented in paraview and I am trying to use it.
I set a simple case of a convective heat transfer with slides defined by FDS. When I try to process the results the reader can see the different temperature slices but I can’t select only one, they are all selected, even though I click on only one “STRUCTURE_TEMPERATURE” (see image).
It seems that the name of the blocks from the smv are all the same.
See the discussion : https://discourse.paraview.org/t/fdsreader-vtkpartitioneddatasetcollection/13599
Could it be possible to change the name, maybe including the coordinate of the slide ?https://gitlab.kitware.com/paraview/paraview/-/issues/22427CI: Flaky tests on fedora runner2024-01-04T07:41:47-05:00Nicolas VuailleCI: Flaky tests on fedora runnerOn `[fedora35_shared_mpi_python_qt_vtkmoverride]` and `[fedora35_shared_mpi_python_qt]`, the following tests fails with different output, but since the exact same build on master. (12/08/2023: https://open.cdash.org/viewTest.php?buildid=...On `[fedora35_shared_mpi_python_qt_vtkmoverride]` and `[fedora35_shared_mpi_python_qt]`, the following tests fails with different output, but since the exact same build on master. (12/08/2023: https://open.cdash.org/viewTest.php?buildid=9212439)
* [ ] pqCoreKeySequences
* `FAIL! : KeySequencesTester::basic() 'QTest::qWaitForWindowActive(window)' returned FALSE. ()`
* [ ] pqWidgetspqTextEditTest
* Timeout
* [ ] pv.ComputeArrayMagnitudeSetting
* `critical: Components property value is: X. Expecting: Magnitude.`
* [ ] (pv|pvcs|pvcrs)TestPythonView
* baseline: black screen
* [ ] pv.TooltipCopy
* `critical: property value is: . Expecting: MeshQuality1`
* [ ] (pvcs|pvcrs)ShaderReplacements
* baseline: scalars instead of solid color
Needs investigations.
CI exclusion: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6630https://gitlab.kitware.com/paraview/paraview/-/issues/22423Link to python error when compiling ParaView with -DPARAVIEW_BUILD_TESTING=ON...2024-01-02T04:43:04-05:00guillaume PeillexLink to python error when compiling ParaView with -DPARAVIEW_BUILD_TESTING=ON -DPARAVIEW_BUILD_WITH_KITS=ONHi all,
I’m facing a link problem when i try to build `ParaView` when the option `PARAVIEW_BUILD_TESTING` and `PARAVIEW_BUILD_WITH_KITS` to on.
When it is `OFF`, `ParaView` build successfully.
The errors arise when compiling some of the...Hi all,
I’m facing a link problem when i try to build `ParaView` when the option `PARAVIEW_BUILD_TESTING` and `PARAVIEW_BUILD_WITH_KITS` to on.
When it is `OFF`, `ParaView` build successfully.
The errors arise when compiling some of the test modules of the `VTKExtensions` such as `IOCGNS`.
The error message is the following:
```
FAILED: bin/vtkPVVTKExtensionsIOCGNSWriterCxxTests
: && /usr/bin/c++ -O2 -g -DNDEBUG -Wl,-lc -Wl,-lc VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/vtkPVVTKExtensionsIOCGNSWriterCxxTests.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestPartitionedDataSetCollection2.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestStructuredGrid.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestUnstructuredGrid.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestPartitionedDataSet.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestPartitionedDataSetCollection.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestPolydata.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestPolyhedral.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestCellAndPointData.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestMultiBlockDataSet.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestMappedUnstructuredGrid.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestTimeWriting.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestRectilinearGrid.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestImageData.cxx.o -o bin/vtkPVVTKExtensionsIOCGNSWriterCxxTests -Wl,-rpath,/opt/paraview_build/lib:/usr/lib/x86_64-linux-gnu/openmpi/lib:/usr/lib/x86_64-linux-gnu/hdf5/serial lib/libvtkTestingDataModel-pv5.12.so.5.12 lib/libvtkIOIOSS-pv5.12.so.5.12 lib/libvtkPVCoreKit-pv5.12.so.5.12 /usr/lib/x86_64-linux-gnu/libexpat.so lib/libvtkParallel-pv5.12.so.5.12 lib/libvtkIO-pv5.12.so.5.12 lib/libvtkFilters-pv5.12.so.5.12 lib/libvtkverdict-pv5.12.so.5.12 /usr/lib/x86_64-linux-gnu/libpugixml.so.1.13 lib/libvtkCommon-pv5.12.so.5.12 lib/libvtksys-pv5.12.so.5.12 lib/libvtktoken-pv5.12.so.5.12 lib/libvtkloguru-pv5.12.so.5.12 lib/libvtkkissfft-pv5.12.so.5.12 /usr/lib/x86_64-linux-gnu/libdouble-conversion.so /usr/lib/x86_64-linux-gnu/liblz4.so /usr/lib/x86_64-linux-gnu/liblzma.so /usr/lib/x86_64-linux-gnu/libz.so lib/libvtkcgns-pv5.12.so.5.12 lib/libvtkfmt-pv5.12.so.5.12 /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.so /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5_hl.so -ldl -Wl,-rpath-link,/opt/paraview_build/lib:/usr/lib/x86_64-linux-gnu/hdf5/serial && :
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyUnicode_InternFromString'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyDict_DelItemString'
/usr/bin/ld: /opt/paraview_build/lib/libvtkPythonInterpreter-pv5.12.so.1: undefined reference to `_Py_Dealloc'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyByteArray_AsString'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyLong_FromLong'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyExc_KeyError'
/usr/bin/ld: /opt/paraview_build/lib/libvtkPythonInterpreter-pv5.12.so.1: undefined reference to `PyStatus_Exception'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyExc_NotImplementedError'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyByteArray_Type'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyNumber_Absolute'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyDescr_NewClassMethod'
/usr/bin/ld: /opt/paraview_build/lib/libvtkPythonInterpreter-pv5.12.so.1: undefined reference to `PyType_IsSubtype'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyErr_Fetch'
/usr/bin/ld: /opt/paraview_build/lib/libvtkPythonInterpreter-pv5.12.so.1: undefined reference to `Py_PreInitialize'
...
collect2: error: ld returned 1 exit status
```
I have made a reproducer through the following Dockerfile
[Dockerfile](/uploads/cd4ef7bc6793b20df0da3406460cfe9e/Dockerfile)
When built, run the container and in the `/opt/paraview_build` just run `cmake --build ..`
I found a hack to workaround. It is to add a dependency to `ParaView::RemotingApplication` in the `TEST_DEPENDS` section of the vtk.module files involved.
See https://discourse.paraview.org/t/link-to-python-error-when-compiling-paraview-with-dparaview-build-testing-on/13524https://gitlab.kitware.com/paraview/paraview/-/issues/22418Cannot color VTU cells as glyphs by scalar2023-12-11T10:42:58-05:00Randy HeilandCannot color VTU cells as glyphs by scalarUsing PV 5.11.2, I’m unable to color cells as glyphs with a scalar array. In the attached .vtu file, I want to display the cells as 3D glyphs, colored by the “cell_id” array. It seems to only do what I want if I add a "CellDataToPointDat...Using PV 5.11.2, I’m unable to color cells as glyphs with a scalar array. In the attached .vtu file, I want to display the cells as 3D glyphs, colored by the “cell_id” array. It seems to only do what I want if I add a "CellDataToPointData" filter
[vtu_2cells.vtu](/uploads/c336c67f40d973c8d6eeaa0e389cb8a0/vtu_2cells.vtu)
[Screenshot_2023-12-11_at_10.20.18_AM](/uploads/e3d2bced384587f5f969a165af98947e/Screenshot_2023-12-11_at_10.20.18_AM.png)[Screenshot_2023-12-11_at_10.24.31_AM](/uploads/f168c3a2642ff6306ac8e1195008b7da/Screenshot_2023-12-11_at_10.24.31_AM.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22414paraview without python using external VTK with python results in errors2023-12-12T13:07:44-05:00Dan Lipsaparaview without python using external VTK with python results in errors```
Using 'QtHelp' without 'QtWebEngine' will ignore embedded javascript and *.js files for documentation
Enabled modules: VTK(172), ParaView(42 + 5)
Configuring done (4.0s)
CMake Error at /home/local/KHQ/dan.lipsa/projects/vtk/external_...```
Using 'QtHelp' without 'QtWebEngine' will ignore embedded javascript and *.js files for documentation
Enabled modules: VTK(172), ParaView(42 + 5)
Configuring done (4.0s)
CMake Error at /home/local/KHQ/dan.lipsa/projects/vtk/external_vtk/build/install/lib/cmake/vtk-9.3/VTK-targets.cmake:1308 (set_target_properties):
The link interface of target "VTK::Python" contains:
Python3::Module
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
Call Stack (most recent call first):
/home/local/KHQ/dan.lipsa/projects/vtk/external_vtk/build/install/lib/cmake/vtk-9.3/vtk-config.cmake:149 (include)
CMakeLists.txt:65 (find_package)
CMake Error at /home/local/KHQ/dan.lipsa/projects/vtk/external_vtk/build/install/lib/cmake/vtk-9.3/VTK-targets.cmake:1342 (set_target_properties):
The link interface of target "VTK::PythonUsed" contains:
Python3::Python
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
Call Stack (most recent call first):
/home/local/KHQ/dan.lipsa/projects/vtk/external_vtk/build/install/lib/cmake/vtk-9.3/vtk-config.cmake:149 (include)
CMakeLists.txt:65 (find_package)
Generating done (1.7s)
```