ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-11T09:37:49-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/22500GLTF format validation issue when using export scene2024-03-11T09:37:49-04:00Loïc GaillardGLTF format validation issue when using export sceneWhen generating a simple data using the wavelet source from paraview and then exporting the scene to the gltf format, the exported file isn't compliant with the [gltf validator](https://github.khronos.org/glTF-Validator/).
Here is the p...When generating a simple data using the wavelet source from paraview and then exporting the scene to the gltf format, the exported file isn't compliant with the [gltf validator](https://github.khronos.org/glTF-Validator/).
Here is the paraview scene right before exporting it :
![image](/uploads/4f61c05361fdcafa4867d866b39c4090/image.png)
Here is the corresponding [gltf file](/uploads/7c9105c1f1f386a5102a8f355c825277/dummy.gltf).
It seems to be a texture mapping issue, the generated texture seems incorrect since it has the color map in a single 256px line and another line full of yellow :
![texture_image](/uploads/f7fe923465402d2439ae843a6b9e5a9e/export_img0.png)
This incorrect texture leads to some texture clipping in other device using gltf data generated from paraview :
![image](/uploads/7129ab6256add4c2d2738c36913ef3c4/image.png)
Here is a an example on PowerPoint but it also appears on other softwares such as MeshLab.Loïc GaillardLoïc Gaillardhttps://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/22490ParaView v5.12.0-RC3 Time Manager then Save animation defaults to frames 0,02024-03-21T08:33:22-04:00Phil SmithParaView v5.12.0-RC3 Time Manager then Save animation defaults to frames 0,0ParaView 5.12.0-RC3 time manager then save animation defaults to frames 0, 0 when we don't have time steps in the dataset.
Linux, 5.12.0-RC3, builtin server.
To reproduce:
Open sources/ sphere, Apply
View/ Time Manager and create sph...ParaView 5.12.0-RC3 time manager then save animation defaults to frames 0, 0 when we don't have time steps in the dataset.
Linux, 5.12.0-RC3, builtin server.
To reproduce:
Open sources/ sphere, Apply
View/ Time Manager and create sphere1 Opacity time track.
File/ Save Animation using defaults
The problem is that it will only save the first frame of the animation.
Before saving the animation, in the Save Animations Options Dialog, if advanced is selected then you can see the default for the Frame Window is set to 0,0
This should be set to 0,\<Max Frames\>.
@wascott @cory.quammen5.14 (Fall 2024)Spiros TsalikisSpiros Tsalikishttps://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)https://gitlab.kitware.com/paraview/paraview/-/issues/22478BivariateTextureRepresentation is flaky2024-02-08T08:10:10-05:00Thomas GallandBivariateTextureRepresentation is flakyIssue appeared so far on fedora and windows.
**CI history**
![image](/uploads/bc1580827cf90315d789629b4543ca31/image.png)
**Encountered errors so far (independent of the platform)**
![image](/uploads/8d0c9e81215a0c8d9a3ae5725abe370a...Issue appeared so far on fedora and windows.
**CI history**
![image](/uploads/bc1580827cf90315d789629b4543ca31/image.png)
**Encountered errors so far (independent of the platform)**
![image](/uploads/8d0c9e81215a0c8d9a3ae5725abe370a/image.png)
![image](/uploads/ac40db166054a84f4a1e40b3fd52f855/image.png)
**Related MR**
https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6704https://gitlab.kitware.com/paraview/paraview/-/issues/22477animations parameters have wrong context2024-03-08T03:13:03-05:00Dan Lipsaanimations parameters have wrong contextI tried this on ParaView master and in 5.12.2.
If you want to animate the Origin of a Clip filter, the Origin, X coordinate is presented as "Clip1 - Clip Type - Origin(0)".
It should be "Clip1 - Plane Parameters - Origin(0)".I tried this on ParaView master and in 5.12.2.
If you want to animate the Origin of a Clip filter, the Origin, X coordinate is presented as "Clip1 - Clip Type - Origin(0)".
It should be "Clip1 - Plane Parameters - Origin(0)".https://gitlab.kitware.com/paraview/paraview/-/issues/22475slice widget needs click to start highlight behavior2024-02-28T20:19:35-05:00Dan Lipsaslice widget needs click to start highlight behaviorI tried this on ParaView 5.11.2 on Windows, but it was true in older slice widgets on ParaView 5.8.
The interior of the slice widget (the interior of the circle) is highlighted with you move the mouse over it, to show the user that it c...I tried this on ParaView 5.11.2 on Windows, but it was true in older slice widgets on ParaView 5.8.
The interior of the slice widget (the interior of the circle) is highlighted with you move the mouse over it, to show the user that it can drag on it to move the slice along its normal. However this does not happen the first time you add the slice. You have to click on the circle for the highlight behavior to start happening.
Same happens on ParaView master on Linux.https://gitlab.kitware.com/paraview/paraview/-/issues/22474Paraview crashing when selecting cells2024-02-08T03:47:41-05:00Luke HirlParaview crashing when selecting cellsI converted output files from SPARTA with the tool grid2paraview.py provided by it. This creates the file structure that can be seen in the attached zip. everything works fine until I try to select cells with the (interactive) select Ce...I converted output files from SPARTA with the tool grid2paraview.py provided by it. This creates the file structure that can be seen in the attached zip. everything works fine until I try to select cells with the (interactive) select Cells On functionality (the green triangle with the arrow pointing to it, wether its the one with dottet line around or without makes no difference).
Zip: https://www.dropbox.com/scl/fi/iqfjnlvoud5lv4tr805oy/result0_1_2_20.rar?rlkey=q7ubmnju4ec6a1i0y1mkmiu6i&dl=0
I’ve also tried using a Linux version (5.10.0-RC1) under WSL. This leads to crashes as well however.
Issue seems to be restricted to the Windows version according to Mathieu Westphal (see following Topic in Paraview Support Forum: https://discourse.paraview.org/t/paraview-crashing-when-selecting-cells/13844)
Under WSL it puts out the following error (can be seen in Forum, as gitlab declares this ticket as Spam when i trty to include it)https://gitlab.kitware.com/paraview/paraview/-/issues/22472Assertion failed with HTG random source + threshold + clip2024-02-06T09:56:46-05:00Timothée Coubletimothee.couble@kitware.comAssertion failed with HTG random source + threshold + clipHow to reproduce the bug in ParaView:
- Create a hyper tree grid random source
- Apply a Threshold filter with an upper threshold inferior of the max
- Apply a clip filter on it
I get this error:
```
vtkHyperTreeGridGeometryEntry.cxx:13...How to reproduce the bug in ParaView:
- Create a hyper tree grid random source
- Apply a Threshold filter with an upper threshold inferior of the max
- Apply a clip filter on it
I get this error:
```
vtkHyperTreeGridGeometryEntry.cxx:139: void vtkHyperTreeGridGeometryEntry::ToChild(const vtkHyperTreeGrid*, const vtkHyperTree*, unsigned int, const double*, unsigned char): Assertion `"pre: is_masked" && !IsMasked(grid, tree)' failed.
```