ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-11T22:21:03-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/22375Add Cinema Export Plugin2024-03-11T22:21:03-04:00John PatchettAdd Cinema Export PluginCurrent plugin state can be found here.
https://github.com/cinemascience/cinema-paraview-plugin
This needs to be added to the standard set of ParaView Plugins that ultimately get built and released with ParaView.
@dhr @cory.quammen @jonesCurrent plugin state can be found here.
https://github.com/cinemascience/cinema-paraview-plugin
This needs to be added to the standard set of ParaView Plugins that ultimately get built and released with ParaView.
@dhr @cory.quammen @jones5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22374undefined symbol: Silo_version_4_11_1 on RHEL 82023-11-14T12:24:09-05:00lucasbantingundefined symbol: Silo_version_4_11_1 on RHEL 8Testing RC1 for 5.12:
```
~/software/ParaView-5.12.0-RC1-osmesa-MPI-Linux-Python3.10-x86_64/bin/pvserver-real: symbol lookup error: ~/software/ParaView-5.12.0-RC1-osmesa-MPI-Linux-Python3.10-x86_64/bin/../lib/../lib/libvtkIOVisItBridge-...Testing RC1 for 5.12:
```
~/software/ParaView-5.12.0-RC1-osmesa-MPI-Linux-Python3.10-x86_64/bin/pvserver-real: symbol lookup error: ~/software/ParaView-5.12.0-RC1-osmesa-MPI-Linux-Python3.10-x86_64/bin/../lib/../lib/libvtkIOVisItBridge-pv5.12.so.1: undefined symbol: Silo_version_4_11_1
```
Also tested on RHEL 9 and did not encounter the same issue.https://gitlab.kitware.com/paraview/paraview/-/issues/22366Ensight Reader fails due to quotation marks around file names2023-11-08T10:05:52-05:00njwallaEnsight Reader fails due to quotation marks around file namesThe Ensight case reader fails to identify file names of referenced files (e.g. the *.geo and scalar files) when those filenames are within quotes in the *.case file. This can occur for files exported from ANSYS Fluent at least since 202...The Ensight case reader fails to identify file names of referenced files (e.g. the *.geo and scalar files) when those filenames are within quotes in the *.case file. This can occur for files exported from ANSYS Fluent at least since 2022, when ANSYS decided to put the internally-referenced filenames in quotes. Manually editing the .case file to remove the quotes (e.g. `"simulation-case.geo"` becomes `simulation-case.geo`) allows the file to be loaded without issue. A suggested fix would be to simply remove outer quotes when reading in a filename.https://gitlab.kitware.com/paraview/paraview/-/issues/22365Default Compression Level Should be 5 not 62024-02-03T00:11:19-05:00John PatchettDefault Compression Level Should be 5 not 6When saving data in vtk xml file formats with compression in the ParaView GUI, the default compression level defaults to 6. Compression level 5 is labeled as the best cost/performance. Make Compression level 5 the default.When saving data in vtk xml file formats with compression in the ParaView GUI, the default compression level defaults to 6. Compression level 5 is labeled as the best cost/performance. Make Compression level 5 the default.Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/22359Hover Cells On bug2023-11-28T12:32:24-05:00Boonthanome NouanesengsyHover Cells On bugWhen using the `Hover Cells On` feature, if the geometry changes over time, such as in an AMR grid, then the hover information becomes incorrect. An example is shown in the below screenshots.
![grid0](/uploads/55fc496906249ffb7838edec...When using the `Hover Cells On` feature, if the geometry changes over time, such as in an AMR grid, then the hover information becomes incorrect. An example is shown in the below screenshots.
![grid0](/uploads/55fc496906249ffb7838edec5be50b61/grid0.png)
The first image shows the first timestep of a grid, with the `Hover Cells On` being used, and the mouse pointer is over a cell, with the cell's information being shown. Note that the cell is highlighted in blue.
![grid1](/uploads/080f1b65c808f0261b165818d2d364cc/grid1.png)
In the second screenshot above, the timestep has been moved forward, and the geometry has changed. As the mouse pointer is being moved, the wrong cell is highlighted. Note that in the image the mouse pointer is somewhere in the middle of the grid, but a cell on the bottom row is highlighted blue. Also the information in the pop up is incorrect.
To reproduce:
- download test dataset:[grid.tar.gz](/uploads/eea0a197e40282d0ef55e9bf65a283fa/grid.tar.gz)
- open `grid0.vtu` and `grid1.vtu` together as a time series
- turn on `Hover Cells On`
- go forward a time step
- move the mouse, the highlighted cell is incorrect, and the pop-up information is incorrect
There is a workaround, in that if you turn off `Hover Cells On` and turn it back on, then `Hover Cells On` works correctly.It would be good to fix this issue, though.
There seems to be a similar issue here: https://gitlab.kitware.com/paraview/paraview/-/issues/19574. Perhaps this is a duplicate.
@patchett2002 @cory.quammen @yohann.bearzi5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22357Test syntax2023-11-04T01:19:02-04:00W. Alan ScottTest syntax//as
\\ blar//as
\\ blarhttps://gitlab.kitware.com/paraview/paraview/-/issues/22355Release ParaView 5.12.0-RC12024-01-03T16:02:35-05:00Ryan Krattigerryan.krattiger@kitware.comRelease ParaView 5.12.0-RC1<!--
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
- `-RC1` - for release candidates, replace with "-RC?". 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
- `-RC1` - 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
- `master`: The branch to create the release on (for `x.y.0-RC1`,
`master`, otherwise `release`)
- `8f255709a4cd60cdfea59ec5889434a3fe3535c9`: The ParaView commit where the release should be started
Please remove this comment.
-->
# Preparatory steps
- Update ParaView guides
- Catalyst Guide
- [ ] Rename to ParaViewCatalystGuide-5.12.0.pdf
- [ ] Upload to www.paraview.org/files/v5.12
- Getting Started Guide
- [ ] Rename to ParaViewGettingStarted-5.12.0.pdf
- [ ] Upload to www.paraview.org/files/v5.12
- macOS signing machine
- [ ] Check that the macOS signing machine is reachable. If not, request it to be switched on.
# Update ParaView
- Update the local copy of `master`.
- If `0-RC1` is `0-RC1`, update `master`
- Otherwise, update `release`
```
git fetch origin
git checkout master
git merge --ff-only origin/master # if this fails, there are local commits that need to be removed
git submodule update --recursive --init
```
- If `master` 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`-only changes on a single topic
(suggested branch name: `update-to-v5.12.0`):
- 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-RC1 8f255709a4cd60cdfea59ec5889434a3fe3535c9
echo 5.12.0-RC1 > version.txt
git commit -m 'Update version number to 5.12.0-RC1' version.txt
```
- [x] Update VTK's `paraview/release` branch. The
[`release-mr`][release-mr] script should be used to do this. Pass
`-c .kitware-release-paraview.json` to use the appropriate
configuration file.
- [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`
- [ ] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [ ] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [ ] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- [ ] Pull the script for each release; it may have been updated since it
was last used
- [ ] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m 8f255709a4cd60cdfea59ec5889434a3fe3535c9`
- [ ] 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).
- [ ] Get positive review
- [ ] `Do: merge`
- [x] Create tag: `git tag -a -m '5.12.0-RC1' v5.12.0-RC1 commit-that-updated-version.txt`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.12.0-RC1`)
- Upload tarballs to `paraview.org`
- [ ] 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)
- [x] 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 `master` 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 master branch for **paraview-superbuild**
```
git fetch origin
git checkout master
git merge --ff-only origin/master
git submodule update --recursive --init
```
- [x] Create new branch `git checkout -b update-to-v5.12.0-RC1 master`
- Integrate changes.
- Update versions
- [ ] Guide selections in `versions.cmake` and ensure that the paraview
http URL source is the _DEFAULT_ source.
- [ ] `paraview_SOURCE_SELECTION` version in `README.md`
- [ ] `PARAVIEW_VERSION_DEFAULT` in CMakeLists.txt
- [ ] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [ ] ARG PARAVIEW_TAG=v5.12.0-RC1
- [ ] ARG SUPERBUILD_TAG=v5.12.0-RC1
- [ ] ARG PARAVIEW_VERSION_STRING=paraview-5.12
- [ ] Commit changes
- [ ] `git add README.md versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile`
- [ ] `git commit -m "Update the default version to 5.12.0-RC1"`
- Make a commit for each of these `release`-only changes
- [ ] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups (if `master` is `master`)
- Create a commit which will be tagged:
- [ ] `git commit --allow-empty -m "paraview: add release 5.12.0"`
- [ ] Create tag: `git tag -a -m 'ParaView superbuild 5.12.0-RC1' v5.12.0-RC1 HEAD`
<!-- if not RC and patch == 0 -->
- [ ] Create a commit that changes the paraview _DEFAULT_ source to the git
url source in the `versions.cmake` file.
<!-- endif -->
- Force `5.12.0-RC1` in CMakeLists.txt
- [ ] Append to the top of CMakeLists.txt (After project...) The following
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.12.0-RC1" CACHE STRING "Force version to 5.12.0-RC1" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- [ ] Create fixup commit with the above changes `git commit -a --fixup=@`. The fixup commit will prevent merging of the temporary code above; it will be removed in a future step.
- [ ] Create a merge request targeting `release`
- [ ] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [ ] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [ ] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- [ ] Pull the script for each release; it may have been updated since it
was last used
- [ ] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m 8f255709a4cd60cdfea59ec5889434a3fe3535c9`
<!-- if not RC and patch == 0-->
- [ ] Make sure that the backporting directive in the merge-request
description skips the last commit such as: `Backport: master:HEAD~`
<!-- endif -->
- [x] Build binaries
- [ ] Build binaries (start all pipelines)
- [ ] Download the binaries that have been generated from the Pipeline
build products. They will be deleted within 24 hours.
- [x] Remove fixup commit: `git reset --hard @^`
- [ ] Get positive review
- [x] Force push `git push -f gitlab`
- [ ] `Do: merge`
- Software process updates (these can all be done independently)
- [x] 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 `master` 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-RC1.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.12.0-RC1.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)
- 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 @jonthan.volks (Kitware comm team) 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
```
- [ ] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.12.0-RC1`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.12.0-RC1`.
# Spack
- [ ] 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
- [ ] 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`
- [ ] Upload versioned documentation to `https://github.com/kitware/paraview-docs` (see `https://github.com/Kitware/paraview-docs/blob/master/README.md`)
- [ ] Tag the HEAD of release in [ParaView docs](https://gitlab.kitware.com/paraview/paraview-docs/-/tags) with v5.12.0.
- [ ] Activate the tag on [readthedocs](https://readthedocs.org/projects/paraview/versions/) and build it [here](https://readthedocs.org/projects/paraview/)
- [ ] Go to readthedocs.org and activate
- [ ] Write and publish blog post with release notes.
- [ ] 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
- [x] 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:
- [ ] Request from comm@kitware.com an update of version number in "Download Latest Release" text on www.paraview.org
- [ ] 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/12`Ryan Krattigerryan.krattiger@kitware.comRyan Krattigerryan.krattiger@kitware.com2023-11-07https://gitlab.kitware.com/paraview/paraview/-/issues/22348vtkPVDataSetAlgorithmSelectorFilter does not fully support composite input2023-12-11T08:31:15-05:00Charly BollingervtkPVDataSetAlgorithmSelectorFilter does not fully support composite inputThe `vtkPVDataSetAlgorithmSelectorFilter` used to be able to switch active filter on the fly takes `vtkDataSet` and `vtkHyperTreeGrid` in input (see `FillInputPortInformation`). This means the pipeline will execute the selected filter on...The `vtkPVDataSetAlgorithmSelectorFilter` used to be able to switch active filter on the fly takes `vtkDataSet` and `vtkHyperTreeGrid` in input (see `FillInputPortInformation`). This means the pipeline will execute the selected filter on each dataset of the composite. This is what happens with `vtkPVMetaClipDataSet` (ie. `Clip`) or `vtkPVMetaSliceDataSet` (ie. `Slice`).
However, if a filter can explicitely execute on composite datasets, like the `vtkGhostCellsGenerator`, it will not execute correctly.
This is the issue described in #22343.
On the other hand, setting input port information to `vtkDataObject`, although fixing above issue, will make the composite pipeline to stop working. This means `Slice`, for example, will not work anymore on a composite dataset.5.12 (Winter 2023)Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/22347Name exceeds 32 characters limit2023-10-25T16:21:45-04:00Xujiang LiuName exceeds 32 characters limitOS: Windows 10 Version 2022
ParaView Version: 5.11.2
Description
When using Paraview to export variables after time-averaging processing, the variable name exceeds the 32-character limit![微信截图_20231025215503](/uploads/f9b7a2d17ccebc8c3e...OS: Windows 10 Version 2022
ParaView Version: 5.11.2
Description
When using Paraview to export variables after time-averaging processing, the variable name exceeds the 32-character limit![微信截图_20231025215503](/uploads/f9b7a2d17ccebc8c3e37ebd5eddf965a/微信截图_20231025215503.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22343Ghost cells generator fails to produce ghosts on a wavelet2024-03-26T13:50:48-04:00Yohann Bearzi (Kitware)Ghost cells generator fails to produce ghosts on a waveletThe following state file works with 5.11.0, but not with master. There should be a non-empty output in `Extract Ghost Cells`
[ghost_image_data.pvsm](/uploads/f6b953701340abfe6d14413522fb9650/ghost_image_data.pvsm)The following state file works with 5.11.0, but not with master. There should be a non-empty output in `Extract Ghost Cells`
[ghost_image_data.pvsm](/uploads/f6b953701340abfe6d14413522fb9650/ghost_image_data.pvsm)Charly BollingerCharly Bollingerhttps://gitlab.kitware.com/paraview/paraview/-/issues/22337OpenFOAM Parallel Reader - MPI issue with Reconstructed Case when changing pr...2023-11-07T03:29:15-05:00Francois MazenOpenFOAM Parallel Reader - MPI issue with Reconstructed Case when changing propertiesThere is a MPI blockage when changing patch selection with reconstructed case mode of the OpenFOAM Reader.
To reproduce:
- Launch `pvserver` with 4 MPI ranks, usually `mpirun -np 4 pvserver`
- Launch ParaView and connect to the server
-...There is a MPI blockage when changing patch selection with reconstructed case mode of the OpenFOAM Reader.
To reproduce:
- Launch `pvserver` with 4 MPI ranks, usually `mpirun -np 4 pvserver`
- Launch ParaView and connect to the server
- Open cavity test case, available [here](https://data.kitware.com/#folder/5afd932e8d777f15ebe1b183)
- Check that the case type is reconstructed case.
- Click Apply, the default internal mesh patch is displayed in the render view
- Check `patch/fixedWall` in the Mesh Regions list
- Click Apply
- ParaView hangs forever
The rank 0 is in `vtkPOpenFOAMReader::GatherMetaData()` method calling `MPI_Allgather`, whereas the other ranks are in `vtkPVGeometryFilter::RequestDataObjectTree` calling `MPI_Allreduce`. Hence the inter-blocking calls.
Call stacks here:
[cavity_rank0.txt](/uploads/e15fa1c6a92ed1d595192dafbd7b5a18/cavity_rank0.txt)
[cavity_rank1.txt](/uploads/d6c94afad3739a09b937a7694650b938/cavity_rank1.txt)
[cavity_rank2.txt](/uploads/86d87105b5e7a863ba44943f2776cee6/cavity_rank2.txt)
[cavity_rank3.txt](/uploads/2b3c6f90c029187bd7a26f3c4dc55b3a/cavity_rank3.txt)https://gitlab.kitware.com/paraview/paraview/-/issues/22330Crystal Eyes2023-10-02T18:53:05-04:00Nathan WoodsCrystal Eyeshttps://gitlab.kitware.com/paraview/paraview/-/issues/22329ParaView binary release Fluent CFF reader is unable to open ANY file2023-10-09T03:29:19-04:00Mathieu Westphal (Kitware)ParaView binary release Fluent CFF reader is unable to open ANY fileThe following hdf5 file generated with fluent cannot be open with ParaView nightly binary and makes ParaView crash.
https://drive.google.com/file/d/1qzIf_HQpGE0tFrOgRSMhGKVS_pW3goK9/view?usp=sharing
The one in the testing data shows th...The following hdf5 file generated with fluent cannot be open with ParaView nightly binary and makes ParaView crash.
https://drive.google.com/file/d/1qzIf_HQpGE0tFrOgRSMhGKVS_pW3goK9/view?usp=sharing
The one in the testing data shows the same behavior.
It CAN be opened with a build ParaView master of the same commitMathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/22324HTG contour filter do not work with 1-cell grid2023-10-23T05:06:52-04:00Thomas GallandHTG contour filter do not work with 1-cell grid**Steps to reproduce:**
- Generate random HTG:
- Choose 1 as seed
- Choose [2, 2, 2] for dimension
- Apply
- Contour with default value (2.5)
**Result:** no contour is generated.**Steps to reproduce:**
- Generate random HTG:
- Choose 1 as seed
- Choose [2, 2, 2] for dimension
- Apply
- Contour with default value (2.5)
**Result:** no contour is generated.Thomas GallandThomas Gallandhttps://gitlab.kitware.com/paraview/paraview/-/issues/22323Time Manager: warning qt about QPainter2023-09-29T03:09:20-04:00Lucas GivordTime Manager: warning qt about QPainterI have some error with qt when openning the `Time Manager` panel
![image](/uploads/18b43aa7802caf52493694a70c9c3d43/image.png)
Note that I try it on Windows.
<details>
<summary>Paraview information</summary>
```
Client Information:
V...I have some error with qt when openning the `Time Manager` panel
![image](/uploads/18b43aa7802caf52493694a70c9c3d43/image.png)
Note that I try it on Windows.
<details>
<summary>Paraview information</summary>
```
Client Information:
Version: 5.11.1-1734-ge38f0734cc
VTK Version: 9.3.0.rc0-500-g3b50717c75
Qt Version: 5.15.2
vtkIdType size: 64bits
Embedded Python: Off
Python Testing: Off
MPI Enabled: Off
Disable Registry: Off
Test Directory:
Data Directory:
SMP Backend: Sequential
SMP Max Number of Threads: 1
OpenGL Vendor: NVIDIA Corporation
OpenGL Version: 3.2.0 NVIDIA 531.79
OpenGL Renderer: NVIDIA GeForce RTX 3050 Ti Laptop GPU/PCIe/SSE2
Accelerated filters overrides available: No
Connection Information:
Remote Connection: No
```
</details>https://gitlab.kitware.com/paraview/paraview/-/issues/22312Python Calculator fails if numpy is not available2023-09-29T11:29:50-04:00Louis GombertPython Calculator fails if numpy is not availableIn Paraview, the Python calculator [cannot work without numpy](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Wrapping/Python/paraview/detail/calculator.py#L7). Yet, when numpy is not found for the selected Python installatio...In Paraview, the Python calculator [cannot work without numpy](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Wrapping/Python/paraview/detail/calculator.py#L7). Yet, when numpy is not found for the selected Python installation, the Python Calculator is still exposed as a Python filter, but will systematically fail when applied.https://gitlab.kitware.com/paraview/paraview/-/issues/22307Build Dependencies for Ubuntu 22.04 LTS2023-09-25T10:10:08-04:00Jonathan HodgesBuild Dependencies for Ubuntu 22.04 LTSBuild instructions for Paraview are based on Ubuntu 18.04 LTS. qt5-default is no longer available in newer Ubuntus. In Ubuntu 22.04 LTS I needed to replace it with the following (new packages at the end):
sudo apt-get install git cmake ...Build instructions for Paraview are based on Ubuntu 18.04 LTS. qt5-default is no longer available in newer Ubuntus. In Ubuntu 22.04 LTS I needed to replace it with the following (new packages at the end):
sudo apt-get install git cmake build-essential libgl1-mesa-dev libxt-dev libqt5x11extras5-dev libqt5help5 qttools5-dev qtxmlpatterns5-dev-tools libqt5svg5-dev python3-dev python3-numpy libopenmpi-dev libtbb-dev ninja-build qtbase5-dev qtchooser qt5-qmake qtbase5-dev-toolshttps://gitlab.kitware.com/paraview/paraview/-/issues/22304Release ParaView 5.11.22023-10-19T01:13:07-04:00Ryan Krattigerryan.krattiger@kitware.comRelease ParaView 5.11.2<!--
This template is for tracking a release of ParaView. Please replace the
following strings with the associated values:
- `5.11.2` - 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.11.2` - 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
- `11` - replace with minor version number
- `2` - replace with patch version number
- `release`: The branch to create the release on (for `x.y.0-RC1`,
`master`, otherwise `release`)
- `8442ccd42b50effff97375d176f89e317856a588`: The ParaView commit where the release should be started
Please remove this comment.
-->
# Preparatory steps
- Update ParaView guides
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.11.2.pdf
- [x] Upload to www.paraview.org/files/v5.11
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.11.2.pdf
- [x] Upload to www.paraview.org/files/v5.11
- macOS signing machine
- [ ] 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 `2` 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`-only changes on a single topic
(suggested branch name: `update-to-v5.11.2`):
- [x] Assemble release notes into `Documentation/release/ParaView-5.11.2.md`.
- [x] Update `version.txt` and tag the commit (tag this commit below)
```
git checkout -b update-to-v5.11.2 8442ccd42b50effff97375d176f89e317856a588
echo 5.11.2 > version.txt
git commit -m 'Update version number to 5.11.2' version.txt
```
- [x] Update VTK's `paraview/release` branch. The
[`release-mr`][release-mr] script should be used to do this. Pass
`-c .kitware-release-paraview.json` to use the appropriate
configuration file.
- [ ] Merge the VTK `paraview/release` update MR
- [ ] 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] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m 8442ccd42b50effff97375d176f89e317856a588`
- [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] Get positive review
- [x] `Do: merge`
- [x] Create tag: `git tag -a -m '5.11.2' v5.11.2 commit-that-updated-version.txt`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.11.2`)
- Upload tarballs to `paraview.org`
- [x] Setup your `~/.ssh/config` and add the web host (@vbolea).
- [x] `rsync -rptv $tarballs web:ParaView_Release/v5.11/`
- 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.11.2 release`
- Integrate changes.
- Update versions
- [x] Guide selections in `versions.cmake` and ensure that the paraview
http URL source is the _DEFAULT_ source.
- [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.11.2
- [x] ARG SUPERBUILD_TAG=v5.11.2
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.11
- [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.11.2"`
- 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`)
- Create a commit which will be tagged:
- [x] `git commit --allow-empty -m "paraview: add release 5.11.2"`
- [x] Create tag: `git tag -a -m 'ParaView superbuild 5.11.2' v5.11.2 HEAD`
<!-- if not RC and patch == 0 -->
- [ ] Create a commit that changes the paraview _DEFAULT_ source to the git
url source in the `versions.cmake` file.
<!-- endif -->
- Force `5.11.2` in CMakeLists.txt
- [ ] Append to the top of CMakeLists.txt (After project...) The following
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.11.2" CACHE STRING "Force version to 5.11.2" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- [ ] Create fixup commit with the above changes `git commit -a --fixup=@`. The fixup commit will prevent merging of the temporary code above; it will be removed in a future step.
- [ ] Create a merge request targeting `release`
- [ ] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [ ] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [ ] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- [ ] Pull the script for each release; it may have been updated since it
was last used
- [ ] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m 8442ccd42b50effff97375d176f89e317856a588`
<!-- if not RC and patch == 0-->
- [ ] Make sure that the backporting directive in the merge-request
description skips the last commit such as: `Backport: master:HEAD~`
<!-- endif -->
- [x] 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.
- [x] Remove fixup commit: `git reset --hard @^`
- [x] Get positive review
- [x] Force push `git push -f gitlab`
- [x] `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.11.2.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.11.2.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
- Python. Open the Python shell and run
- Plugins are present and load properly
- OSPRay raycasting and pathtracing runs ("Enable Ray Tracing" property in View panel)
- OptiX pathtracing runs (not macOS)
- 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.11/`)
- [x] Ask @jonthan.volks (Kitware comm team) 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.11
```
- [ ] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.11.2`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.11.2`.
# 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
- [ ] Submit a Merge Request for release that updates the version to 5.11.2 in https://gitlab.kitware.com/paraview/paraview-docs/-/blob/master/doc/source/conf.py` for `paraview-docs`
- [ ] Upload versioned documentation to `https://github.com/kitware/paraview-docs` (see `https://github.com/Kitware/paraview-docs/blob/master/README.md`)
- [ ] Tag the HEAD of release in [ParaView docs](https://gitlab.kitware.com/paraview/paraview-docs/-/tags) with v5.11.2.
- [ ] Activate the tag on [readthedocs](https://readthedocs.org/projects/paraview/versions/) and build it [here](https://readthedocs.org/projects/paraview/)
- [ ] Go to readthedocs.org and activate
- [ ] Write and publish blog post with release notes.
- [ ] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
-->
# Post-release
- [ ] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [ ] Request DoD vulnerability scan
- [x] Request an XRInterface plugin validation using [TESTING.md](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Plugins/XRInterface/TESTING.md) protocol from KEU
- [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
/cc @vbolea
[win-sign-example]: https://kwgitlab.kitware.com/software-process/package-signing/-/issues/12Ryan Krattigerryan.krattiger@kitware.comRyan Krattigerryan.krattiger@kitware.com2023-09-23https://gitlab.kitware.com/paraview/paraview/-/issues/22302XRInterface pipeline interface corruption (Monado OpenXR)2023-09-19T01:33:21-04:00Tyson WhiteheadXRInterface pipeline interface corruption (Monado OpenXR)### Issue
The XCInterface plugin works okay until I click on any of the pipeline objects. Then the interface window gets shrunk down to part of the panel with the extra space filled with garbage.
It doesn't freeze or anything, and if y...### Issue
The XCInterface plugin works okay until I click on any of the pipeline objects. Then the interface window gets shrunk down to part of the panel with the extra space filled with garbage.
It doesn't freeze or anything, and if you inteface with the areas on the wider window where the buttons and such would be if they hadn't been shrunk down, it still works and updates the shrunk down bit.
Here is a screenshot of the shrunk interface
![paraview](/uploads/2d77dd0ad7889dd7285e6375ad27c8ac/paraview.png)
### Client Information
```
Version: 5.11.0
VTK Version: 9.2.20220823
Qt Version: 5.15.10
vtkIdType size: 64bits
Embedded Python: On
Python Library Path: /nix/store/xs0nw11xzxm875vma7cn31haiqvhrbg7-python3-3.10.12-env/lib/python3.10
Python Library Version: 3.10.12 (main, Jun 6 2023, 22:43:10) [GCC 12.2.0]
Python Numpy Support: On
Python Numpy Path: /nix/store/xs0nw11xzxm875vma7cn31haiqvhrbg7-python3-3.10.12-env/lib/python3.10/site-packages/numpy
Python Numpy Version: 1.24.2
Python Matplotlib Support: On
Python Matplotlib Path: /nix/store/xs0nw11xzxm875vma7cn31haiqvhrbg7-python3-3.10.12-env/lib/python3.10/site-packages/matplotlib
Python Matplotlib Version: 3.7.0
Python Testing: Off
MPI Enabled: On
Disable Registry: Off
Test Directory:
Data Directory:
SMP Backend: TBB
SMP Max Number of Threads: 4
OpenGL Vendor: AMD
OpenGL Version: 4.6 (Core Profile) Mesa 23.0.3
OpenGL Renderer: AMD Radeon RX 6600 XT (navi23, LLVM 15.0.7, DRM 3.52, 6.4.12)
Accelerated filters overrides available: No
```
### Connection Information
```
Remote Connection: No
```
### OpenXR Information
I don't really see how to query my OpenXR setup (there doesn't seem to be any tool like `openxr-info`). But here is the output from the `openxr_runtime_list` program that is included with the openxr loader package
```
LOG in xrCreateInstance: Instance created
createInfo->applicationInfo.applicationName: List
createInfo->applicationInfo.applicationVersion: 1
createInfo->applicationInfo.engineName: List Engine
createInfo->applicationInfo.engineVersion: 1
appinfo.detected.engine.name: (null)
appinfo.detected.engine.version: 0.0.0
quirks.disable_vulkan_format_depth_stencil: false
LOG in xrCreateInstance: Selected devices
Head: 'Valve Index (libsurvive)'
Left: 'Valve Index Left Controller (libsurvive)'
Right: 'Valve Index Right Controller (libsurvive)'
Hand-Tracking Left: 'Valve Index Left Controller (libsurvive)'
Hand-Tracking Right: 'Valve Index Right Controller (libsurvive)'
Evaluating system
name: 'Monado: Valve Index (libsurvive)'
vendorId: 0x2a
systemId: 0x1
systemName: Monado: Valve Index (libsurvive)
List instance extensions
XR_KHR_binding_modification 1
XR_KHR_composition_layer_cube 8
XR_KHR_composition_layer_cylinder 4
XR_KHR_composition_layer_depth 6
XR_KHR_composition_layer_equirect 3
XR_KHR_composition_layer_equirect2 1
XR_KHR_convert_timespec_time 1
XR_KHR_opengl_enable 10
XR_KHR_opengl_es_enable 8
XR_KHR_swapchain_usage_input_attachment_bit 3
XR_KHR_vulkan_enable 8
XR_KHR_vulkan_enable2 2
XR_EXT_dpad_binding 1
XR_EXT_hand_tracking 4
XR_FB_display_refresh_rate 1
XR_MND_headless 2
XR_MND_swapchain_usage_input_attachment_bit 2
XR_EXTX_overlay 5
XR_MNDX_egl_enable 1
XR_MNDX_force_feedback_curl 1
XR_EXT_debug_utils 4
List API layer properties
```
Here are the various version numbers for OpenXR related components
```
openxr-loader: 1.0.27
vulkan-loader: 1.3.249
amdvlk: 2023.Q2.1
libsurvive: 1.01
openhmd: 0.3.0
monado: unstable-2023-01-14
```https://gitlab.kitware.com/paraview/paraview/-/issues/22301Colormaps: consider adding color deficient-friendly colormaps from Fabio Crameri2023-10-03T20:24:42-04:00Cory Quammencory.quammen@kitware.comColormaps: consider adding color deficient-friendly colormaps from Fabio CrameriThese colormaps are available here: https://www.fabiocrameri.ch/colourmaps/
They include ParaView colormap files.These colormaps are available here: https://www.fabiocrameri.ch/colourmaps/
They include ParaView colormap files.