ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-01T05:26:48-05:00https://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/22489Release ParaView 5.12.02024-03-08T20:38:39-05:00Ryan Krattigerryan.krattiger@kitware.comRelease ParaView 5.12.0<!--
This template is for tracking a release of ParaView. Please replace the
following strings with the associated values:
- `5.12.0` - replace with base version, e.g., 5.7.0
- `` - for release candidates, replace with "-RC?". For f...<!--
This template is for tracking a release of ParaView. Please replace the
following strings with the associated values:
- `5.12.0` - replace with base version, e.g., 5.7.0
- `` - for release candidates, replace with "-RC?". For final, replace with "".
- `5` - replace with major version number
- `12` - replace with minor version number
- `0` - replace with patch version number
- `release`: The branch to create the release on (for `x.y.0-RC1`,
`master`, otherwise `release`)
- `release`: The ParaView commit where the release should be started
Please remove this comment.
-->
# Preparatory steps
- macOS signing machine
- [x] Check that the macOS signing machine is reachable. If not, request it to be switched on.
# Update ParaView
- Update the local copy of `release`.
- If `0` is `0-RC1`, update `master`
- Otherwise, update `release`
```
git fetch origin
git checkout release
git merge --ff-only origin/release # if this fails, there are local commits that need to be removed
git submodule update --recursive --init
```
- If `release` is not `master`, ensure merge requests which should be
in the release have been merged. The [`backport-mrs.py`][backport-mrs]
script can be used to find and ensure that merge requests assigned to the
associated milestone are available on the `release` branch.
- Integrate changes.
- Make a commit for each of these `release` changes on a single topic
(suggested branch name: `update-to-v5.12.0`):
- [x] Assemble release notes into `Documentation/release/ParaView-5.12.0.md`.
- [x] Update `version.txt` and tag the commit (tag this commit below)
```
git checkout -b update-to-v5.12.0 release
echo 5.12.0 > version.txt
git commit -m 'Update version number to 5.12.0' version.txt
```
- Make a commit for each of these `release`-only changes
- [x] Merge the VTK `paraview/release` update MR
- [x] Update kwrobot with the new `paraview/release` branch rules (@ben.boeckel)
- [x] `.gitmodules` to track the `paraview/release` branch of VTK
- [x] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups
- Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- [x] Pull the script for each release; it may have been updated since it
was last used
- [x] Add your development fork as a remote named `gitlab`
- [x] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m release`
- [x] The script outputs the information it will be using to create the
merge request. Please verify that it is all correct before creating
the merge request. See usage at the top of the script to provide
information that is either missing or incorrect (e.g., if its data
extraction heuristics fail).
- [x] Run the test with `Do: test` and get a green dashboard.
- [x] Get positive review
- [x] `Do: merge`
- [ ] Create tag: `git tag -a -m '5.12.0' v5.12.0 commit-that-updated-version.txt`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.12.0`)
- Upload tarballs to `paraview.org`
- [x] Setup your `~/.ssh/config` and add the web host (@vbolea).
- [x] `rsync -rptv $tarballs web:ParaView_Release/v5.12/`
- Software process updates (these can all be done independently)
- [ ] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [ ] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [ ] Add (or update if `release` is `release`) version selection entry
in paraview-superbuild
[backport-mrs]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/backport-mrs.py
[release-mr]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/release-mr.py
[cdash-update-groups]: https://gitlab.kitware.com/utils/cdash-utils/-/blob/master/cdash-update-groups.py
# Update ParaView-Superbuild
- [x] Update release branch for **paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Create new branch `git checkout -b update-to-v5.12.0 release`
- Integrate changes.
- Update versions
- [x] Guide selections in `versions.cmake`.
- [x] `paraview_SOURCE_SELECTION` version in `README.md`
- [x] `PARAVIEW_VERSION_DEFAULT` in CMakeLists.txt
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.12.0
- [x] ARG SUPERBUILD_TAG=v5.12.0
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.12
- [x] Commit changes
- [x] `git add README.md versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile`
- [x] `git commit -m "Update the default version to 5.12.0"`
- Make a commit for each of these `release`-only changes
- [x] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups (if `release` is `master`)
- [x] Create a commit which will be tagged:
- [x] `git commit --allow-empty -m "paraview: add release 5.12.0"`
- [x] Create tag: `git tag -a -m 'ParaView superbuild 5.12.0' v5.12.0 HEAD`
- [x] Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- [x] Pull the script for each release; it may have been updated since it
was last used
- [x] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m release`
- [x] Make sure that the backporting directive in the merge-request
description skips the last commit such as: `Backport: master:HEAD~`
- Build binaries
- [x] Build binaries (start all pipelines)
- [x] Download the binaries that have been generated from the Pipeline
build products. They will be deleted within 24 hours.
- [ ] Remove fixup commit: `git reset --hard @^`
- [ ] Get positive review
- [ ] Force push `git push -f gitlab`
- [ ] `Do: merge`
- Software process updates (these can all be done independently)
- [ ] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [ ] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [ ] Add (or update if `release` is `release`) version selection entry
in paraview-superbuild
# Sign Windows binaries
- [x] Request Windows binary signings (only .exe archives) on the Package
Signing repo. Example request [here][win-sign-example].
# Sign macOS binaries
- [x] Upload to signing server, run script, download resulting .pkg and .dmg files
- [x] Install from .pkg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.12.0.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.12.0.app/`
# Validating binaries
For each binary, open the Python shell and run the following:
```python
import numpy
s = Show(Sphere())
ColorBy(s, ('POINTS', 'Normals', 'X'))
Show(Text(Text="$A^2$"))
```
Check that
- Getting started guide opens
- Help lists Readers, Writers, Filters, and Sources properly
- Examples load and match thumbnails in dialog
- Plugins are present and load properly
- OSPRay raycasting and pathtracing runs ("Enable Ray Tracing" property in View panel)
- OptiX pathtracing runs (not macOS)
- ref. !22372 for current expected results
- IndeX runs (load pvNVIDIAIndeX plugin, add a Wavelet dataset, change representaiton to NVIDIA IndeX)
Binary checklist
- [x] macOS arm64
- [x] macOS x86\_64
- [x] Linux
- [x] Linux osmesa
- [x] Windows MPI (.exe)
- [x] Windows MPI (.zip)
- [x] Windows no-MPI (.exe)
- [x] Windows no-MPI (.zip)
# Upload binaries
- [x] Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.12/`)
- [x] Ask @cory.quammen to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website from within the directory corresponding to www.paraview.org/files/
```
buildListing.sh
updateMD5sum.sh v5.12
```
- [x] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.12.0`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.12.0`.
# Spack
- [x] Update Spack package: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py
If making a non-RC release:
# Update documentation
- [x] Submit a Merge Request for release that updates the version to 5.12.0 in https://gitlab.kitware.com/paraview/paraview-docs/-/blob/master/doc/source/conf.py` for `paraview-docs`
- [x] Upload versioned documentation to `https://github.com/kitware/paraview-docs` (see `https://github.com/Kitware/paraview-docs/blob/master/README.md`)
- [x] Tag the HEAD of release in [ParaView docs](https://gitlab.kitware.com/paraview/paraview-docs/-/tags) with v5.12.0.
- [x] Activate the tag on [readthedocs](https://readthedocs.org/projects/paraview/versions/) and build it [here](https://readthedocs.org/projects/paraview/)
- [x] Go to readthedocs.org and activate
- [x] Write and publish blog post with release notes.
- [x] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [ ] Request DoD vulnerability scan
- [ ] Request an XRInterface plugin validation using [TESTING.md](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Plugins/XRInterface/TESTING.md) protocol from KEU
If making a non-RC release:
- [x] Request from comm@kitware.com an update of version number in "Download Latest Release" text on www.paraview.org
- [x] Move unclosed issues in GitLab to the next release milestone in GitLab
/cc @ben.boeckel
/cc @cory.quammen
/cc @charles.gueunet
/cc @mwestphal
[win-sign-example]: https://kwgitlab.kitware.com/software-process/package-signing/-/issues/125.12 (Winter 2023)Ryan Krattigerryan.krattiger@kitware.comRyan Krattigerryan.krattiger@kitware.com2024-03-01https://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.
```https://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.vuaille