ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-02-13T01:29:29-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/22471pvtu with polyhedra segfault2024-02-13T01:29:29-05:00Kirill Terekhovpvtu with polyhedra segfaultDear developers,
Opening an issue as suggested in discussion: https://discourse.paraview.org/t/pvtu-with-polyhedra-issue/13858
The display of polyhedra in Paraview depends on the order of pieces in the pvtu file.
In the attached exam...Dear developers,
Opening an issue as suggested in discussion: https://discourse.paraview.org/t/pvtu-with-polyhedra-issue/13858
The display of polyhedra in Paraview depends on the order of pieces in the pvtu file.
In the attached example [parallel_polyhedron.pvtu](/uploads/5af0951c12da380600d2974cd61bb6eb/parallel_polyhedron.pvtu), there are 3 hexahedra. In the first piece [parallel_polyhedron_0.vtu](/uploads/928ac87aa4bbc23661908dd2a2198e9c/parallel_polyhedron_0.vtu), there is the usual hexahedron of type 12. In the following two [parallel_polyhedron_1.vtu](/uploads/d25858bf3f8820d67147a32c3e272fff/parallel_polyhedron_1.vtu) and [parallel_polyhedron_2.vtu](/uploads/65e4a6fb24487e4d87c51e1b3b6fc9f1/parallel_polyhedron_2.vtu), there are two hexes stored as polyhedra of type 42 with additional “faces” and “faceoffsets” arrays.
In the original order of pieces in the example, Paraview displays a gap in the middle of the mesh, whereas there should be three tight hexahedra. If the order of the pieces in the pvtu file is changed with parallel_polyhedron_0.vtu going last, the mesh is displayed correctly.
It appears that Paraview renders the mesh correctly if the pieces with polyhedra are followed by the pieces without polyhedra. It skips rendering the polyhedra if the piece without polyhedra is followed by the piece with polyhedra. This is verified in a large mesh example with numerous pieces.
Encountered with Paraview 5.11.1 on windows and tested with the latest ParaView-5.12.0-RC2-Windows-Python3.10-msvc2017-AMD64.msi.
The next issue with the attached example is encountered when applying a “Clip” filter. It will give a warning “A cell with a non-manifold triangulation has been encountered. This cell cannot be contoured.”. Only the top cell is rendered in this case. However, if you check “Crinkle clip”, it will show the cell in the middle (this was a gap) and wouldn’t render the cell at the bottom.
This works as described with Paraview 5.11.1 on windows. ParaView-5.12.0-RC2-Windows-Python3.10-msvc2017-AMD64.msi crashes at “Clip” filter.
Regards,
Kirillhttps://gitlab.kitware.com/paraview/paraview/-/issues/22468Skybox: expose transform property2024-01-31T10:59:33-05:00Lucas GivordSkybox: expose transform propertyIn VTK, we can modify the transform of a skybox which is handy to rotate the skybox for example.
Currently, such property isn't exposed in ParaView.
cc @mwestphal @francois.mazen @louis.gombertIn VTK, we can modify the transform of a skybox which is handy to rotate the skybox for example.
Currently, such property isn't exposed in ParaView.
cc @mwestphal @francois.mazen @louis.gomberthttps://gitlab.kitware.com/paraview/paraview/-/issues/22467Significant performance difference caused by the number of timesteps2024-01-29T14:06:43-05:00SchnFloSignificant performance difference caused by the number of timestepsIssue created w.r.t this [topic](https://discourse.paraview.org/t/poor-performance-for-high-number-of-timesteps/13815/) on the forum.
Initial issue:
```plaintext
Hello! I am new to ParaView/Vtk and am looking for some guidance. Current...Issue created w.r.t this [topic](https://discourse.paraview.org/t/poor-performance-for-high-number-of-timesteps/13815/) on the forum.
Initial issue:
```plaintext
Hello! I am new to ParaView/Vtk and am looking for some guidance. Currently I am testing vtk-xmlUnstructuredGrids as a possible output format for a project. I tested the following sets in the paraview Render-View:
* 7000 cells / 100 Time steps —> 25 Fps
* 6 cells / 32 000 Time steps —> 2Fps
```
Events:
* Confirmation of issue by mwestphal
* Reproducable from paraview application, but not from pvpython by nicolas.vuaillehttps://gitlab.kitware.com/paraview/paraview/-/issues/22463Catalyst2 CxxSteeringExample doesn't work2024-01-24T06:20:56-05:00Juan Jose CasafrancaCatalyst2 CxxSteeringExample doesn't workI am testing the steering capabilities of Catalyst 2. however, I am having a hard time making the example work. When I run it, I just get the following error:
```
./bin/CxxSteeringExample ../catalyst_steering_proxies.xml ../catalyst_pip...I am testing the steering capabilities of Catalyst 2. however, I am having a hard time making the example work. When I run it, I just get the following error:
```
./bin/CxxSteeringExample ../catalyst_steering_proxies.xml ../catalyst_pipeline.py
( 0.114s) [pvbatch ] ParaViewCatalyst.cxx:291 INFO| Catalyst plugin loaded: ../catalyst_steering_proxies.xml
executing catalyst_pipeline
( 0.598s) [pvbatch ]vtkSIProxyDefinitionMan:517 ERR| vtkSIProxyDefinitionManager (0x562f7b1a1660): No proxy that matches: group=extract_writers an
d proxy=steering were found.
Traceback (most recent call last):
File "/workspace/ParaView/lib/python3.10/site-packages/paraview/catalyst/v2_internals.py", line 82, in import_and_validate
m = importlib.import_module(modulename)
File "/workspace/ParaView/lib/python3.10/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 883, in exec_module
File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
File "/home/seddi/paraview/Examples/Catalyst2/CxxSteeringExample/build/../catalyst_pipeline.py", line 13, in <module>
steering_extractor = CreateExtractor('steering', filterArray, registrationName='steerchannel')
File "/workspace/ParaView/lib/python3.10/site-packages/paraview/simple.py", line 486, in CreateExtractor
RegisterExtractor(extractor)
File "/workspace/ParaView/lib/python3.10/site-packages/paraview/catalyst/detail.py", line 80, in RegisterExtractor
_get_active_helper().RegisterExtractor(extractor.SMProxy)
AttributeError: 'NoneType' object has no attribute 'SMProxy'
```
If I remove the `steering_extractor = CreateExtractor('steering', filterArray, registrationName='steerchannel')` then it works, but of course, I can't get any information back from ParaView.https://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/22455ParaView date based versioning is incomplete2024-01-18T03:12:38-05:00Mathieu Westphal (Kitware)ParaView date based versioning is incompleteParaView recently switched to date based versionning, however it seems incomplete.
The date appears in `version.txt` as well as in the package names generated by ParaView-superbuild.
But it seems to be incorrect in many other places.
...ParaView recently switched to date based versionning, however it seems incomplete.
The date appears in `version.txt` as well as in the package names generated by ParaView-superbuild.
But it seems to be incorrect in many other places.
- `paraview --version` reports `paraview version 5.12.0-RC2-330-g0cf0dc5a12`
- About dialog reports `5.12.0-RC2-330-g0cf0dc5a12`
- ParaView dialog is `5.12.0-RC2-330-g0cf0dc5a12`
- find_package(ParaView) report a ParaView_VERSION `5.12.0-RC2-330-g0cf0dc5a12`
It would be nice if the versionning was coherent. Using VTK has an example would be fine imo.5.13 (Summer 2024)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/22452Screenshots are incorrect size on Mac2024-01-17T10:31:31-05:00W. Alan ScottScreenshots are incorrect size on MacScreenshots are incorrect size on Mac. Here is how to replicate. Note that I am on a monitor that is 2560X1440
* 5.12.0-RC1, builtin server, Mac M1
* Sources/ Wavelet. Apply. Surface.
* File/ Save Screenshot. deleteMe (take default ...Screenshots are incorrect size on Mac. Here is how to replicate. Note that I am on a monitor that is 2560X1440
* 5.12.0-RC1, builtin server, Mac M1
* Sources/ Wavelet. Apply. Surface.
* File/ Save Screenshot. deleteMe (take default of .png). OK.
Notice that the chosen resolution is 3514X1956. This is totally, totally bogus and is a bug.
@phismith25 - Be sure to check on all three platforms.5.12.1 (Spring 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22451Manual release testing2024-02-13T12:56:22-05:00W. Alan ScottManual release testingPlease modify the release template to include manual release testing. Over time the intent is to automate this process.
On all platforms do the following:
* open can.exo. Apply. Split screen. Volume rendering. Ray tracing. Save sc...Please modify the release template to include manual release testing. Over time the intent is to automate this process.
On all platforms do the following:
* open can.exo. Apply. Split screen. Volume rendering. Ray tracing. Save screenshot (.png). Save Animation (.avi).
On one platform, maybe Linux, do the following:
* Remote server with at least 4 ranks.
* Run through the Classroom Tutorials. Not everything needs to be done (i.e., try a few sources and filters), but every section (including Python) needs to be run.
* As it isn't listed in the classroom tutorials, be sure to run ghost cell generator and view/memory inspector.5.12.1 (Spring 2024)Caitlin RossCaitlin Rosshttps://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/22447ParaView 5.12.0-RC2 build failure on Fedora Rawhide2024-03-07T20:23:59-05:00Orion PoplawskiParaView 5.12.0-RC2 build failure on Fedora RawhideTest building the Fedora ParaView package with 5.12.0-RC2 tarball I'm getting:
```
[100%] Building CXX object Clients/ParaView/CMakeFiles/paraview.dir/ParaViewMainWindow.cxx.o
cd /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-bu...Test building the Fedora ParaView package with 5.12.0-RC2 tarball I'm getting:
```
[100%] Building CXX object Clients/ParaView/CMakeFiles/paraview.dir/ParaViewMainWindow.cxx.o
cd /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Clients/ParaView && /usr/bin/g++ -DFMT_SHARED -DPARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION=1 -DPARAVIEW_USE_MATERIALEDITOR=0 -DPARAVIEW_USE_PYTHON=1 -DQT_CORE5COMPAT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGLWIDGETS_LIB -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -Dkiss_fft_scalar=double -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Clients/ParaView/paraview_autogen/include -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Clients/ParaView -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Clients/ParaView -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Qt/ApplicationComponents -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Qt/ApplicationComponents -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Qt/Components -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Qt/Components -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Qt/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Qt/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Qt/Widgets -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Qt/Widgets -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/ThirdParty/QtTesting/vtkqttesting -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/ThirdParty/QtTesting/vtkqttesting -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Utilities/Versioning -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Utilities/Versioning -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/GUISupport/Qt -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/GUISupport/Qt -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Common/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Common/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/token/vtktoken/token -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/token/vtktoken/token -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/token/vtktoken -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/token/vtktoken -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Rendering/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Rendering/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Common/DataModel -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Common/DataModel -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Common/Math -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Common/Math -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/kissfft/vtkkissfft -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/kissfft/vtkkissfft -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Common/Transforms -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Common/Transforms -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Common/ExecutionModel -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Common/ExecutionModel -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Filters/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Filters/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Common/Misc -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Common/Misc -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Rendering/OpenGL2 -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Rendering/OpenGL2 -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Filters/General -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Filters/General -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/IO/Image -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/IO/Image -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Imaging/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Imaging/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Rendering/HyperTreeGrid -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Rendering/HyperTreeGrid -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Rendering/UI -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Rendering/UI -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Interaction/Widgets -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Interaction/Widgets -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Filters/Sources -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Filters/Sources -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Rendering/Context2D -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Rendering/Context2D -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Remoting/ServerManager -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Remoting/ServerManager -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Remoting/ClientServerStream -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Remoting/ClientServerStream -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Remoting/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Remoting/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTKExtensions/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTKExtensions/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/IO/XML -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/IO/XML -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/IO/XMLParser -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/IO/XMLParser -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/fmt/vtkfmt -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/fmt/vtkfmt -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Parallel/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Parallel/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/CMakeFiles/ParaView_paraview_plugins -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Remoting/Settings -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Remoting/Settings -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/include/paraview/pvpythonmodules -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/include/paraview/vtkpythonmodules -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/include/paraview/pvincubatorpythonmodules -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Qt/Python -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Qt/Python -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Utilities/PythonInterpreter -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Utilities/PythonInterpreter -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Utilities/Python -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Utilities/Python -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Wrapping/PythonCore -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Wrapping/PythonCore -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Utilities/PythonInitializer -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Utilities/PythonInitializer -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Utilities/KWSys -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Utilities/KWSys -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Utilities/KWIML -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Utilities/KWIML -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/token -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/token -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/nlohmannjson -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/nlohmannjson -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/kissfft -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/kissfft -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/glew -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/glew -isystem /usr/include/qt6/QtOpenGL -isystem /usr/include/qt6 -isystem /usr/include/qt6/QtCore -isystem /usr/lib64/qt6/mkspecs/linux-g++ -isystem /usr/include/qt6/QtGui -isystem /usr/include/qt6/QtWidgets -isystem /usr/include/qt6/QtOpenGLWidgets -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/ThirdParty/protobuf -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/ThirdParty/protobuf -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/cli11 -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/cli11 -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/fmt -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/fmt -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/jsoncpp -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/jsoncpp -isystem /usr/include/qt6/QtCore5Compat -isystem /usr/include/python3.12 -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fcommon -m64 -march=z13 -mtune=z14 -fasynchronous-unwind-tables -fstack-clash-protection -DNDEBUG -DOMPI_SKIP_MPICXX -std=c++17 -fPIE -fvisibility=hidden -fvisibility-inlines-hidden -MD -MT Clients/ParaView/CMakeFiles/paraview.dir/ParaViewMainWindow.cxx.o -MF CMakeFiles/paraview.dir/ParaViewMainWindow.cxx.o.d -o CMakeFiles/paraview.dir/ParaViewMainWindow.cxx.o -c /builddir/build/BUILD/ParaView-v5.12.0-RC2/Clients/ParaView/ParaViewMainWindow.cxx/builddir/build/BUILD/ParaView-v5.12.0-RC2/Clients/ParaView/ParaViewMainWindow.cxx:41:10: fatal error: ParaViewDocumentationInitializer.h: No such file or directory
41 | #include "ParaViewDocumentationInitializer.h"
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
```
RC1 I think built fine.5.13 (Summer 2024)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/22442Automate Tutorial tests as part of CI2024-01-11T20:07:50-05:00Spiros TsalikisAutomate Tutorial tests as part of CICreate automated tests out of the Self-Directed and Classroom tutorials on docs.paraview.org, and add them as part of CI.
- https://docs.paraview.org/en/latest/Tutorials/SelfDirectedTutorial/index.html
- https://docs.paraview.org/en/l...Create automated tests out of the Self-Directed and Classroom tutorials on docs.paraview.org, and add them as part of CI.
- https://docs.paraview.org/en/latest/Tutorials/SelfDirectedTutorial/index.html
- https://docs.paraview.org/en/latest/Tutorials/ClassroomTutorials/index.html#
@cory.quammen @ben.boeckel @wascott5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://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 Gaillard