ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T07:56:19-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/22511Comparative View Constantly Updating Causing High CPU Usage2024-03-07T07:56:19-05:00Ethan StamComparative View Constantly Updating Causing High CPU Usage@cory.quammen
I am using ParaView 5.11.2 on a Mac x86_64 laptop.
I am getting a problem with the comparative viz view where (in at least one case) it is constantly updating the views.
Steps to reproduce:
1. Launch paraview from comma...@cory.quammen
I am using ParaView 5.11.2 on a Mac x86_64 laptop.
I am getting a problem with the comparative viz view where (in at least one case) it is constantly updating the views.
Steps to reproduce:
1. Launch paraview from command line with `/Applications/ParaView-5.11.2.app/Contents/MacOS/paraview -v=9` to get verbose output
2. Close renderview and open renderview (comparative)
3. View -> Comparative View Inspector
4. File Open disk_out_ref example dataset
5. Apply contour filter with default options
6. In Comparative View Inspector, choose Contour1 and Isosurfaces as the parameter, click the plus icon to add it
After step 6 is where I hit the issue. I didn't spend much time, but I couldn't find another way to reproduce it. I tried other datasets, but didn't get the same result.
![comparative_view](/uploads/e29329840ed69e83da6707b87adb680a/comparative_view.gif)https://gitlab.kitware.com/paraview/paraview/-/issues/22510ParaView v5.12.0 requires an old version of FastFloat, why?2024-03-08T12:48:23-05:00Thierry ThomasParaView v5.12.0 requires an old version of FastFloat, why?Trying to build ParaView 5.12.0 on my workstation, where FastFloat v6.0.0 is installed: it is rejected by CMake:
```
CMake Warning at VTK/CMake/vtkModule.cmake:4958 (find_package):
Could not find a configuration file for package "FastF...Trying to build ParaView 5.12.0 on my workstation, where FastFloat v6.0.0 is installed: it is rejected by CMake:
```
CMake Warning at VTK/CMake/vtkModule.cmake:4958 (find_package):
Could not find a configuration file for package "FastFloat" that is
compatible with requested version "3.9.0".
The following configuration files were considered but not accepted:
/usr/local/share/cmake/FastFloat/FastFloatConfig.cmake, version: 6.0.0
Call Stack (most recent call first):
VTK/CMake/vtkModule.cmake:5594 (vtk_module_find_package)
VTK/CMake/vtkModule.cmake:5462 (vtk_module_third_party_external)
VTK/ThirdParty/fast_float/CMakeLists.txt:1 (vtk_module_third_party)
CMake Error at VTK/CMake/vtkModule.cmake:4964 (message):
Could not find the FastFloat external dependency.
Call Stack (most recent call first):
VTK/CMake/vtkModule.cmake:5594 (vtk_module_find_package)
VTK/CMake/vtkModule.cmake:5462 (vtk_module_third_party_external)
VTK/ThirdParty/fast_float/CMakeLists.txt:1 (vtk_module_third_party)
```
Note: upstream released [FastFloat v6.1.0](https://github.com/fastfloat/fast_float/releases/tag/v6.1.0) some days ago.
Does ParaView really need such an old version?https://gitlab.kitware.com/paraview/paraview/-/issues/22509Python wrapping needs to pull in all wrapped targets in static builds2024-03-07T07:57:53-05:00Alexander NeumannPython wrapping needs to pull in all wrapped targets in static buildsSo I am trying to build PV 5.12 with external VTK (https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6375?full_index=1) statically and ran into (after removing a cycle in the target deps):
```
CMake Error at E:/vcpkg_folders...So I am trying to build PV 5.12 with external VTK (https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6375?full_index=1) statically and ran into (after removing a cycle in the target deps):
```
CMake Error at E:/vcpkg_folders/paraview/installed/x64-windows-static-md-release/share/vtk/VTK-targets.cmake:967 (set_target_properties):
The link interface of target "VTK::RenderingOpenVR" contains:
OpenVR::OpenVR
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):
E:/vcpkg_folders/paraview/installed/x64-windows-static-md-release/share/vtk/vtk-config.cmake:143 (include)
E:/vcpkg_folders/paraview/scripts/buildsystems/vcpkg.cmake:859 (_find_package)
CMakeLists.txt:65 (find_package)
CMake Error at E:/vcpkg_folders/paraview/installed/x64-windows-static-md-release/share/vtk/VTK-targets.cmake:1265 (set_target_properties):
The link interface of target "VTK::pegtl" contains:
PEGTL::PEGTL
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):
E:/vcpkg_folders/paraview/installed/x64-windows-static-md-release/share/vtk/vtk-config.cmake:143 (include)
E:/vcpkg_folders/paraview/scripts/buildsystems/vcpkg.cmake:859 (_find_package)
CMakeLists.txt:65 (find_package)
CMake Error at E:/vcpkg_folders/paraview/installed/x64-windows-static-md-release/share/vtk/VTK-targets.cmake:1584 (set_target_properties):
The link interface of target "VTK::IOGDAL" contains:
GDAL::GDAL
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):
E:/vcpkg_folders/paraview/installed/x64-windows-static-md-release/share/vtk/vtk-config.cmake:143 (include)
E:/vcpkg_folders/paraview/scripts/buildsystems/vcpkg.cmake:859 (_find_package)
CMakeLists.txt:65 (find_package)
```
The target chain is:
```
OpenVR::OpenVR
-> VTK::RenderingOpenVR
-> VTK::vtkRenderingOpenVRPython
-> VTK::vtkpythonmodules
-> ParaView::PythonInitializer or pvincubatorpythonmodules or pvpythonmodules
```
(similar for GDAL)
The problem is that the `find_package` call added for external VTK is not pulling in the required VTK COMPONENTS which have been wrapped.
The calculated find_package call is:
`find_package(VTK CONFIG REQUIRED COMPONENTS CommonCore;CommonDataModel;IOImage;IOParallelXML;ParallelMPI;RenderingCore;RenderingOpenGL2;CommonExecutionModel;PythonInterpreter;ParallelCore;WrappingPythonCore;FiltersGeneral;FiltersHybrid;vtksys;mpi;RenderingParallelLIC;Python;RenderingMatplotlib;AcceleratorsVTKmFilters;IOXdmf2;IOCGNSReader;DomainsChemistry;FiltersAMR;FiltersCore;FiltersExtraction;FiltersFlowPaths;FiltersGeneric;FiltersGeometry;FiltersHyperTree;FiltersModeling;FiltersOpenTURNS;FiltersParallel;FiltersParallelDIY2;FiltersParallelVerdict;FiltersSources;FiltersStatistics;FiltersTensor;FiltersTexture;FiltersVerdict;ImagingCore;ImagingFourier;ImagingGeneral;ImagingHybrid;ImagingSources;IOAsynchronous;IOChemistry;IOGeometry;IOInfovis;IOLegacy;IOParallel;IOPLY;IOVPIC;IOXML;IOAMR;IOCityGML;IOCONVERGECFD;IOFDS;IOIOSS;IOH5part;IOH5Rage;IONetCDF;IOOggTheora;IOOMF;IOParallelExodus;IOParallelLSDyna;IOPIO;IOHDF;IOSegY;IOTRUCHAS;IOVeraOut;IOTecplotTable;IOFLUENTCFF;RenderingFreeType;ParallelMPI4Py;FiltersParallelFlowPaths;FiltersParallelGeometry;FiltersParallelMPI;IOMPIImage;IOParallelNetCDF;WrappingTools;CommonMisc;CommonSystem;CommonTransforms;hdf5;netcdf;zlib;CommonMath;opengl;FiltersPython;FiltersPoints;IOCore;cgns;IOEnSight;FiltersParallelStatistics;FiltersProgrammable;GUISupportQt;IOExportGL2PS;jsoncpp;nlohmannjson;ChartsCore;pugixml;cli11;TestingRendering;IOImport;FiltersGeometryPreview;IOMovie;CommonComputationalGeometry;IOExport;fmt;RenderingAnnotation;RenderingContext2D;RenderingCellGrid;RenderingParallel;ViewsContext2D;ViewsCore;CommonColor;DomainsChemistryOpenGL2;FiltersCellGrid;InteractionStyle;RenderingContextOpenGL2;RenderingLICOpenGL2;RenderingLabel;RenderingVolumeAMR;lz4;RenderingVolume;FiltersImaging;doubleconversion;loguru )`
And does not contain the required COMPONENTS to activate the lookup of the additional dependencies.
CC @ben.boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22506Add polyhedra source in ParaView2024-03-04T12:28:50-05:00Alexandre MinotAdd polyhedra source in ParaViewWe should add a polyhedra source in the data sources of ParaView. See discourse here: https://discourse.paraview.org/t/adding-a-polyhedra-source/14084We should add a polyhedra source in the data sources of ParaView. See discourse here: https://discourse.paraview.org/t/adding-a-polyhedra-source/14084https://gitlab.kitware.com/paraview/paraview/-/issues/22504Colorbar titles should accept multiline and support \n as classic annotations do2024-03-03T00:55:42-05:00GregVernonColorbar titles should accept multiline and support \n as classic annotations doSee Discourse discussion here ([specifically, @mwestphal's response](https://discourse.paraview.org/t/vertical-color-legends-with-horizontal-title-clash-with-the-use-above-range-color/14059/2)).
The title below is: `$Very\ long\ text\ ...See Discourse discussion here ([specifically, @mwestphal's response](https://discourse.paraview.org/t/vertical-color-legends-with-horizontal-title-clash-with-the-use-above-range-color/14059/2)).
The title below is: `$Very\ long\ text\ but\ this\ is\ still\ a\ bug\ to\ fix$`
![image](/uploads/9f27ba992488c4deb9488f0a843832a1/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22503Vertical color legends with horizontal title clash with the Use Above Range C...2024-03-01T23:24:41-05:00GregVernonVertical color legends with horizontal title clash with the Use Above Range ColorSee [Discourse discussion here](https://discourse.paraview.org/t/vertical-color-legends-with-horizontal-title-clash-with-the-use-above-range-color/14059).
As shown in the image below, when using a vertical colorbar with a horizontal tit...See [Discourse discussion here](https://discourse.paraview.org/t/vertical-color-legends-with-horizontal-title-clash-with-the-use-above-range-color/14059).
As shown in the image below, when using a vertical colorbar with a horizontal title, if the `Use Above Color Range` option results in the title overlapping the colorbar:
![image](/uploads/1876982796e4865fea44a46e3b5600d2/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22502Add Method to Legacy Ghost Cells Generator to match Ghost Cells Generator for...2024-03-13T15:09:35-04:00John PatchettAdd Method to Legacy Ghost Cells Generator to match Ghost Cells Generator for setting ghost levelThe legacy ghost cells generator needs to have the same method for setting ghost levels so that if the two are swapped, the methods don't also have to be swapped.
So LegacyGCG::MinimumNumberOfGhosts(int) should wrap LegacyGCG::.Minimum...The legacy ghost cells generator needs to have the same method for setting ghost levels so that if the two are swapped, the methods don't also have to be swapped.
So LegacyGCG::MinimumNumberOfGhosts(int) should wrap LegacyGCG::.MinimumNumberOfGhostLevels(int)
This will alleviate a ton of headache for users needing to swap between the two GCGs.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22499Expose Grow and Shrink selection operations in paraview.selection2024-02-28T15:19:32-05:00Cory Quammencory.quammen@kitware.comExpose Grow and Shrink selection operations in paraview.selection5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22498XML tests CMakeLists improvements2024-02-28T07:15:35-05:00Nicolas VuailleXML tests CMakeLists improvementsThe XML client tests are added in the CMakeLists of this [directory](https://gitlab.kitware.com/paraview/paraview/-/tree/master/Clients/ParaView/Testing/XML?ref_type=heads).
I see different issue with this CMakeLists:
1. it is really b...The XML client tests are added in the CMakeLists of this [directory](https://gitlab.kitware.com/paraview/paraview/-/tree/master/Clients/ParaView/Testing/XML?ref_type=heads).
I see different issue with this CMakeLists:
1. it is really big
* harder to find something or the correct place for new entry
* code duplication (like `if` branches and `append` statements)
2. tests without baseline are not added to client-server test suite.
3. tests are added at some place, options defined elsewhere later (like _DISABLE_CS, THRESHOLD or so)https://gitlab.kitware.com/paraview/paraview/-/issues/22497Log Viewer - Export Log broken2024-02-28T03:53:09-05:00Scott WittenburgLog Viewer - Export Log brokenThis bug prevents the export of log data to a file using the Log Viewer. To reproduce, open the the Log Viewer, and update some categories or verbosity level. Then interact with paraview (e.g. create a Cone), and hit the "Refresh" butt...This bug prevents the export of log data to a file using the Log Viewer. To reproduce, open the the Log Viewer, and update some categories or verbosity level. Then interact with paraview (e.g. create a Cone), and hit the "Refresh" button in the Log Viewer. If there are log entries, then click the "Export Log" button, provide a filename in the resulting dialog, and click Ok. Instead of a log file, some errors appear in the Output Messages window.
![client_log_file](/uploads/8b56f975475ad15d776ca69fbc218dc0/client_log_file.png)
![pv_export_log_error](/uploads/78e523feff6e40b94095723e5531b986/pv_export_log_error.png)
As indicated in the screenshot above, this error happened with the 5.12 RC3 release candidate downloaded from the website. The machine is an x86_64 running Ubuntu 20.04.https://gitlab.kitware.com/paraview/paraview/-/issues/22496Mesh geometry corrupted by Temporal Interpolator with Xdmf3 readers2024-03-01T05:26:48-05:00Maxime RenaultMesh geometry corrupted by Temporal Interpolator with Xdmf3 readersHere is what my geometry becomes after a few timesteps when reading HDF5/XDMF3 files and applying Temporal Interpolation:
![Capture_d_écran_du_2024-02-27_08-00-29](/uploads/a5f0a57c39f1d2cffbbda9ce403c3b62/Capture_d_écran_du_2024-02-27_0...Here is what my geometry becomes after a few timesteps when reading HDF5/XDMF3 files and applying Temporal Interpolation:
![Capture_d_écran_du_2024-02-27_08-00-29](/uploads/a5f0a57c39f1d2cffbbda9ce403c3b62/Capture_d_écran_du_2024-02-27_08-00-29.png)
[Here](https://drive.google.com/drive/folders/1nBibQJRCW-EyKmJGWXFLc7noqpwECgNx?usp=sharing) are the data to reproduce.
I’m using ParaView 5.11.2 on Ubuntu 22.04.4. Here are the steps to follow :
1. Open xdmf file with Xdmf3Reader (S or T) and Apply.
2. Apply TemporalInterpolator to it, and choose any resample factor >1 (tried 2, 5, 10 and 100).
3. Click play. It will go through a few timesteps with no problem then the geometry will disappear, or change position, or completely collapse.
The issue only occurs on interpolated timesteps.
XDMF Reader doesn't show this behavior, but the fields are all wrong. An example of pressure fields: left is correct, read by Xdmf3ReaderS, and right is wrong, read by Xdmf Reader.
![Capture_d_écran_du_2024-02-27_15-48-46](/uploads/2ab8c7f6c118a6db68bcbfa1bd8075b6/Capture_d_écran_du_2024-02-27_15-48-46.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22494ParaView 5.12.0-RC3 macOS: context menu option for removing a Favorite in Ope...2024-02-26T10:53:08-05:00Cory Quammencory.quammen@kitware.comParaView 5.12.0-RC3 macOS: context menu option for removing a Favorite in Open File dialog does not work* Start ParaView
* File -> Open...
* Add a Favorite by clicking the + button
* Ctrl-click on the newly created Favorite and choose "Remove from favorites". Nothing happens.
Expected: the favorite should be removed.* Start ParaView
* File -> Open...
* Add a Favorite by clicking the + button
* Ctrl-click on the newly created Favorite and choose "Remove from favorites". Nothing happens.
Expected: the favorite should be removed.https://gitlab.kitware.com/paraview/paraview/-/issues/22493ParaView 5.12.0-RC3: Open File dialog on Windows minimum horizontal size is t...2024-02-26T11:24:27-05:00Cory Quammencory.quammen@kitware.comParaView 5.12.0-RC3: Open File dialog on Windows minimum horizontal size is too large* Launch ParaView 5.12.0-RC3
* File -> Open File
This is as narrow as I can make the dialog.
![image](/uploads/951531f0d4363ebfa8682c980514ed15/image.png)* Launch ParaView 5.12.0-RC3
* File -> Open File
This is as narrow as I can make the dialog.
![image](/uploads/951531f0d4363ebfa8682c980514ed15/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22491Missing time step in animation of OpenFOAM datasets due to precision in reader2024-02-26T04:46:14-05:00AaronMissing time step in animation of OpenFOAM datasets due to precision in readerHello,
When reading in and animating openfoam time-varying datasets, timesteps go missing and the FrameWindow input of the SaveAnimation function ceases to function correctly.
It has been described in more detail, with a sample dataset...Hello,
When reading in and animating openfoam time-varying datasets, timesteps go missing and the FrameWindow input of the SaveAnimation function ceases to function correctly.
It has been described in more detail, with a sample dataset and the diagnosis from kitware staff here:
https://discourse.paraview.org/t/missing-time-steps/13744/11https://gitlab.kitware.com/paraview/paraview/-/issues/22488Wrong outline representation for ImageData2024-02-28T07:29:34-05:00Arnaud BotellaWrong outline representation for ImageDataI have an ImageData saved as a vti file. In this file, one of the directions is negative. This leads to an accurate Surface representation but a wrong Outline representation. I am unsure if this is Paraview or VTK related and if this dat...I have an ImageData saved as a vti file. In this file, one of the directions is negative. This leads to an accurate Surface representation but a wrong Outline representation. I am unsure if this is Paraview or VTK related and if this data is supported but I guess the result should be consistent between different representations.
Here is the file
```
<VTKFile type="ImageData" version="1.0" byte_order="LittleEndian" header_type="UInt64" compressor="vtkZLibDataCompressor">
<ImageData WholeExtent="0 1 0 1 0 1" Origin="0 0 0" Spacing="1 1 1" Direction="-1 0 0 0 1 0 0 0 1">
<Piece Extent="0 1 0 1 0 1">
</Piece>
</ImageData>
</VTKFile>
```
[file.vti](/uploads/f866f6b662bd008a7e107b3f5616d250/file.vti)
And here are the results
Outline result
![image](/uploads/76d7b737cbe1d541e6c9f5bafc4e3416/image.png)
Surface result
![image](/uploads/2145eec56d9236e61663006f6549e74e/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22487PHTG Reader segfault with Ghost Cell data2024-02-20T11:06:34-05:00Louis GombertPHTG Reader segfault with Ghost Cell dataSteps to reproduce:
- Run pvserver with 2 MPI ranks
- Launch client and connect
- Create HTG Random source
- Generate Ghost Cells
- Save to .phtg
- (Reset)
- Load .phtg file
- :boom:
Individual .htg files load fine, but not the...Steps to reproduce:
- Run pvserver with 2 MPI ranks
- Launch client and connect
- Create HTG Random source
- Generate Ghost Cells
- Save to .phtg
- (Reset)
- Load .phtg file
- :boom:
Individual .htg files load fine, but not the .phtg, which is likely to be an issue with the PHTG Readerhttps://gitlab.kitware.com/paraview/paraview/-/issues/224865.12.0-RC3 failure to configure with -DPARAVIEW_USE_CUDA:BOOL=ON on Hopper GPU2024-02-19T13:02:55-05:00Jean M. Favre5.12.0-RC3 failure to configure with -DPARAVIEW_USE_CUDA:BOOL=ON on Hopper GPUcmake v3.27.7
nvcc release 12.3, V12.3.52
The default -DVTKm_CUDA_Architecture:STRING=native fails with error:
CMake Error at VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/CMake/VTKmDeviceAdapters.cmake:216 (message):
Error detecting architecture...cmake v3.27.7
nvcc release 12.3, V12.3.52
The default -DVTKm_CUDA_Architecture:STRING=native fails with error:
CMake Error at VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/CMake/VTKmDeviceAdapters.cmake:216 (message):
Error detecting architecture flags for CUDA. Please set
VTKm_CUDA_Architecture manually.
Call Stack (most recent call first):
VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/CMake/VTKmWrappers.cmake:14 (include)
VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/CMakeLists.txt:233 (include)
and there is no "hopper" (compute capability 9.0) choice in the possible choices:
VTKm_CUDA_Architecture-STRINGS:INTERNAL=native;fermi;kepler;maxwell;pascal;volta;turing;ampere;all;none5.12.1 (Spring 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22484Make the LANL X3D Reader Plugin a reader2024-02-29T12:10:19-05:00Boonthanome NouanesengsyMake the LANL X3D Reader Plugin a readerThe LANL X3D Reader is used to load in LANL X3D, which is a LANL specific format. It is currently a plugin, and we would like to make it a first class reader available in Paraview.
The first task is to create a reader in VTK based on t...The LANL X3D Reader is used to load in LANL X3D, which is a LANL specific format. It is currently a plugin, and we would like to make it a first class reader available in Paraview.
The first task is to create a reader in VTK based on the plugin, and then after that, to expose the reader in Paraview.
Below is a white paper with the specifications for the X3D format:
[X3D.pdf](/uploads/bef7735167fd72db1371f905ee9ceca1/X3D.pdf)
@patchett2002 @cory.quammen5.13 (Summer 2024)Boonthanome NouanesengsyBoonthanome Nouanesengsyhttps://gitlab.kitware.com/paraview/paraview/-/issues/22481Test: pv.TimeManagerPanel has a potential memory issue2024-02-12T04:44:29-05:00Mathieu Westphal (Kitware)Test: pv.TimeManagerPanel has a potential memory issueThe pv.TimeManagerTest can sometimes segfault has showed by cdash:
https://open.cdash.org/queryTests.php?project=ParaView&begin=2023-11-01&end=2024-02-09&filtercount=2&showfilters=1&filtercombine=and&field1=status&compare1=62&value1=Pas...The pv.TimeManagerTest can sometimes segfault has showed by cdash:
https://open.cdash.org/queryTests.php?project=ParaView&begin=2023-11-01&end=2024-02-09&filtercount=2&showfilters=1&filtercombine=and&field1=status&compare1=62&value1=Passed&field2=testname&compare2=63&value2=TimeManagerPanel
![a](/uploads/4fe020af753e5e6da5f33379eaa73ed7/a.png)
Assertion failed:
```
vtkSMTestDriver: client command is:
"/builds/gitlab-kitware-sciviz-ci/build/bin/paraview" "--enable-bt" "--test-script=/builds/gitlab-kitware-sciviz-ci/Clients/ParaView/Testing/XML/TimeManagerPanel.xml" "--test-directory=/builds/gitlab-kitware-sciviz-ci/build/Testing/Temporary" "--data-directory=/builds/gitlab-kitware-sciviz-ci/build/ExternalData" "--dr" "--exit"
vtkSMTestDriver: starting process client
-------------- client output --------------
hwloc/linux: Ignoring PCI device with non-16bit domain.
Pass --enable-32bits-pci-domain to configure to support such devices
(warning: it would break the library ABI, don't enable unless really needed).
Process started
vtkSMTestDriver: client successfully started.
Process started
Playing: /builds/gitlab-kitware-sciviz-ci/Clients/ParaView/Testing/XML/TimeManagerPanel.xml
paraview: /builds/gitlab-kitware-sciviz-ci/VTK/Common/DataModel/vtkDataObjectTreeRange.h:208: vtk::detail::DataObjectTreeRange::DataObjectTreeRange(vtkDataObjectTree*, vtk::DataObjectTreeOptions): Assertion `this->DataObjectTree' failed.
vtkSMTestDriver: ***** Test will fail, because the string: "failed"
vtkSMTestDriver: ***** was found in the following output from the client:
"paraview: /builds/gitlab-kitware-sciviz-ci/VTK/Common/DataModel/vtkDataObjectTreeRange.h:208: vtk::detail::DataObjectTreeRange::DataObjectTreeRange(vtkDataObjectTree*, vtk::DataObjectTreeOptions): Assertion `this->DataObjectTree' failed."
vtkSMTestDriver: client0 process exited with an exception: Unknown
vtkSMTestDriver: Error string found in output, vtkSMTestDriver returning 1
```
Or segfault:
```
15:16:25 : 2: Test (1): Event: /FileOpenDialog: filesSelected : C:/glr/builds/paraview/paraview-ci/build/ExternalData/Testing/Data/can.ex2
15:16:25 : 2: Done
15:16:26 : 1: Done
15:16:26 : 3: Test (0): Event: /Accept: activate :
15:16:28 : 3: Done
15:16:28 : 4: Test (0): Event: /actionIsometricView: activate :
15:16:28 : 4: Done
15:16:28 : 5: Test (0): Event: /menubar: activate : menu_View
15:16:28 : 5: Done
15:16:28 : 6: Test (0): Event: /menu_View: activate : Time Manager
15:16:29 : 6: Done
15:16:29 : 7: Test (0): Event: /1pqTimelineView0: expand : 0.0
15:16:29 : 7: Done
15:16:29 : 8: Test (0): Check Event: /1pqTimelineView0: modelRowCount : 2
15:16:29 : 8: Done
15:16:29 : 9: Test (0): Check Event: /1pqTimelineView0: modelItemData : 0.0.,Time Sources
15:16:29 : 9: Done
15:16:29 : 10: Test (0): Check Event: /1pqTimelineView0: modelItemData : 1.0,Animations
15:16:29 : 10: Done
15:16:29 : 11: Test (0): Check Event: /1pqTimelineView0: modelItemData : 0.0.0.0,can.ex2
15:16:29 : 11: Done
15:16:29 : 12: Test (0): Check Event: /proxiesBox: currentText : can.ex2
15:16:29 : 12: Done
15:16:29 : 13: Test (0): Check Event: /1pqTimelineView0: modelItemData : 1.0.0.0,TimeKeeper1 - Time
15:16:29 : 13: Done
15:16:29 : 14: Test (0): Event: /menubar: activate : menuFilters
15:16:29 : 14: Done
15:16:29 : 15: Test (0): Event: /menuFilters: activate : &Temporal
vtkSMTestDriver: client0 process exited with an exception: Segmentation fault
```
Unable to reproduce locally but valgrind reports this:
```
==238843== Conditional jump or move depends on uninitialised value(s)
==238843== at 0x4FBDA500: ???
==238843== by 0x6931E067: ???
==238843==
==238843== Conditional jump or move depends on uninitialised value(s)
==238843== at 0x4FBDA500: ???
==238843== by 0x6A0C8AE7: ???
==238843==
```
Which is quite unhelpful.
Excluding from CI could be considered.https://gitlab.kitware.com/paraview/paraview/-/issues/22480ResampleWithDataset is unreliable with quadratic elements2024-02-12T07:37:16-05:00Loïc BertheResampleWithDataset is unreliable with quadratic elementsI tried to interpolate fields from an UnstructuredGrid model to a node set with the ResampleWithDataset filter:
![image](/uploads/ee7714c107d944a6ac4ce01adcf4b1c9/image.png)
Interpolation fails at certain points:
![image](/uploads/b24...I tried to interpolate fields from an UnstructuredGrid model to a node set with the ResampleWithDataset filter:
![image](/uploads/ee7714c107d944a6ac4ce01adcf4b1c9/image.png)
Interpolation fails at certain points:
![image](/uploads/b2427f97104e267a02702c6b08182259/image.png)
Increasing the tolerance or changing the cell locator mode does not improve the result.
This problem seems linked to the type of cells used in the source mesh: if we use an "Extract Surface" filter to linearize the mesh, the problem seems to disappear.
It therefore seems that there is a problem with the robustness of the "Resample With Dataset" filter in the presence of quadratic elements.
Please find below the data to reproduce this issue:
[dest_mesh.vtk](/uploads/c0ab0fa4bedb61082e6910d225a202a0/dest_mesh.vtk) [source_mesh.vtu](/uploads/626b4482c811064616265e41358133a9/source_mesh.vtu)