ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-01-18T10:36:47-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/8897Help documentation missing2024-01-18T10:36:47-05:00Kitware RobotHelp documentation missing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=8897). Further discussion may take place here.**
---
There is documentation missing in the following filters:
* Temporal snap to...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=8897). Further discussion may take place here.**
---
There is documentation missing in the following filters:
* Temporal snap to timestep
* Table to structured grid
* Table to points
* Plot selection over time
* Plot global variables over time
* Normal Glyphs
* FFT of selection over time.
To see this, run ParaView XP, help, filters. This table has missing filter descriptions.5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22536Programmable filter failing to write row output to spreadsheet in parallel2024-03-19T01:05:37-04:00W. Alan ScottProgrammable filter failing to write row output to spreadsheet in parallelHere is a writeup from a user. Berk is working this one.
I’m going to do a full writeup here for Alan to write up the bug report. I’m doing this in two side-by-side instances of ParaView 5.12.0. (Linux client both sides.) One instance...Here is a writeup from a user. Berk is working this one.
I’m going to do a full writeup here for Alan to write up the bug report. I’m doing this in two side-by-side instances of ParaView 5.12.0. (Linux client both sides.) One instance, which I will refer to as Remote, is connected to 2 nodes on the HPC (specifically Ghost) (Note Alan, this will be 56*2, or 112 ranks.). The other instance, which I will refer to as Local, is just running directly on the remote machine I’m using.
* For both Local and Remote, I open up the simulation at the location /snip/(dave karelitz's small dataset) cth-small/spcta_a in the Open File dialog box
* Turn on all Cell Arrays and hit accept.
* Add a Programmable Filter to the pipeline, change output type to vtkTable, paste in the below code block, and hit accept
```
a = vtk.vtkDoubleArray()
a.SetNumberOfTuples(1)
a.SetValue(0, mean(inputs[0].CellData['Pressure (dynes/cm^2^)']))
a.SetName('max')
output.RowData.AddArray(a)
```
* For both, the Spreadsheet view opens up:
* For Local, the Spreadsheet opens up to Row Data and displays the single value, with the name “max”. There is just one row, and only one other column (Row ID).
* For Remote, the Spreadsheet opens up to Field Data, displaying all the Field Data stuff. When I manually switch to Row Data, it shows nothing in the Spreedsheet View.
Bonus Points: Error Messages – For each instance, I add the following line to the Programmable filter in the second-to-last position (right above output.RowData.AddArray(a)) ->
```
raise ValueError(a.GetValue(0))
```
* For Local, the Output Messages dialog window opens up and displays the expected Value Error with the calculated max value. The SpreadSheet view goes blank as expected due to a Value Error.
* For Remote, nothing changes. No dialog window pops up. Note: I recall that in 5.11.<whichever>, the dialog window would open up and display the value, so this is new behavior.
* I don’t actually know how else to check the output logs using the ParaView GUI, but if you let me know I’ll check them. Note that the Value Error does write to the terminal running the Local instance, but does not for the Remote instance.
To reiterate a previous point, I used a similar workflow with pvbatch with 2 nodes (on Ghost, which was running 5.12.0), and it seems to have worked, as it exported the values over time. I double checked by trying to Export Data on the Remote Instance, even though the Row Data showed as empty, but it just wrote a .csv with TimeStep and Time column titles but no data.https://gitlab.kitware.com/paraview/paraview/-/issues/22526update example visualizations to incude new palette and fast color map2024-03-12T22:33:46-04:00W. Alan Scottupdate example visualizations to incude new palette and fast color mapupdate example visualizations to include new palette and fast color map. Test on all 3 OSs.update example visualizations to include new palette and fast color map. Test on all 3 OSs.5.13 (Summer 2024)W. Alan ScottW. Alan Scotthttps://gitlab.kitware.com/paraview/paraview/-/issues/22525New example visualizations2024-03-12T22:31:58-04:00W. Alan ScottNew example visualizationsAdd 3 new examples to the Example Visualizations. Have them be: 1) One or more of the examples found in the Examples/ vtk folder. 2) a vtkhdf example. 3) A data analysis example, possibly with a python calculator, histogram, plot and ...Add 3 new examples to the Example Visualizations. Have them be: 1) One or more of the examples found in the Examples/ vtk folder. 2) a vtkhdf example. 3) A data analysis example, possibly with a python calculator, histogram, plot and spreadsheet.5.14 (Fall 2024)W. Alan ScottW. Alan Scotthttps://gitlab.kitware.com/paraview/paraview/-/issues/22524Add VTKHDF examples to ParaView Examples directory2024-03-13T08:41:22-04:00W. Alan ScottAdd VTKHDF examples to ParaView Examples directoryPlease add some VTKHDF examples to the ParaView Examples directory. A good idea would be to add all of the examples at the bottom of the document here: https://www.paraview.org/Wiki/ParaView/Data_formats. Make sure they can be loaded a...Please add some VTKHDF examples to the ParaView Examples directory. A good idea would be to add all of the examples at the bottom of the document here: https://www.paraview.org/Wiki/ParaView/Data_formats. Make sure they can be loaded and run.5.14 (Fall 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22523Help menu - Moving data into and out of ParaView2024-03-12T22:24:32-04:00W. Alan ScottHelp menu - Moving data into and out of ParaViewPlease add a new Help menu line. Please bounce this name by Cory Q (who is better at names than I am). Possibly name the help menu "Moving data into and out of ParaView". Have this menu point at a paraview.org webpage, much as the Onl...Please add a new Help menu line. Please bounce this name by Cory Q (who is better at names than I am). Possibly name the help menu "Moving data into and out of ParaView". Have this menu point at a paraview.org webpage, much as the Online Tutorials line does (i.e., https://www.paraview.org/tutorials/).
In this new webpage, include at least the following links:
* VTK File formats: https://docs.vtk.org/en/latest/design_documents/VTKFileFormats.html
* PVD file format: This needs a new page. The best I can find is something I created maybe 10 years ago. https://www.paraview.org/Wiki/ParaView/Data_formats.
* ParaView supported file formats for read: https://docs.vtk.org/en/latest/supported_data_formats.html
* ParaView supported file formats for write: Page probably needs to be created. Note, have two sections on this page - Save Data and Export scene. Explain both.5.14 (Fall 2024)https://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/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/22479Release ParaView 5.12.0-RC32024-02-13T14:34:45-05:00Ryan Krattigerryan.krattiger@kitware.comRelease ParaView 5.12.0-RC3<!--
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
- `-RC3` - 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
- `-RC3` - 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-RC3` 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-RC3 release
echo 5.12.0-RC3 > version.txt
git commit -m 'Update version number to 5.12.0-RC3' 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)
- [ ] Pull the script for each release; it may have been updated since it
was last used
- [ ] Add your development fork as a remote named `gitlab`
- [ ] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m release`
- [ ] 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.
- [ ] Remove fixup commit: `git reset --hard @^`
- [ ] Get positive review
- [x] `Do: merge`
- [x] Create tag: `git tag -a -m '5.12.0-RC3' v5.12.0-RC3 commit-that-updated-version.txt`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.12.0-RC3`)
- 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)
- [x] 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-RC3 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`)
- [ ] ARG PARAVIEW_TAG=v5.12.0-RC3
- [ ] ARG SUPERBUILD_TAG=v5.12.0-RC3
- [ ] ARG PARAVIEW_VERSION_STRING=paraview-5.12
- [x] 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-RC3"`
- 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:
- [ ] `git commit --allow-empty -m "paraview: add release 5.12.0"`
- [ ] Create tag: `git tag -a -m 'ParaView superbuild 5.12.0-RC3' v5.12.0-RC3 HEAD`
- [x] Force `5.12.0-RC3` 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-RC3" CACHE STRING "Force version to 5.12.0-RC3" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- [x] 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.
- [x] 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)
- [x] 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 release`
- 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 @^`
- [x] Get positive review
- [x] Force push `git push -f gitlab`
- [x] `Do: merge`
- Software process updates (these can all be done independently)
- [x] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [x] 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-RC3.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.12.0-RC3.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-RC3`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.12.0-RC3`.
# 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.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/125.12 (Winter 2023)Ryan Krattigerryan.krattiger@kitware.comRyan Krattigerryan.krattiger@kitware.com2024-02-10https://gitlab.kitware.com/paraview/paraview/-/issues/22455ParaView date based versioning is incomplete2024-01-18T03:12:38-05:00Mathieu Westphal (Kitware)ParaView date based versioning is incompleteParaView recently switched to date based versionning, however it seems incomplete.
The date appears in `version.txt` as well as in the package names generated by ParaView-superbuild.
But it seems to be incorrect in many other places.
...ParaView recently switched to date based versionning, however it seems incomplete.
The date appears in `version.txt` as well as in the package names generated by ParaView-superbuild.
But it seems to be incorrect in many other places.
- `paraview --version` reports `paraview version 5.12.0-RC2-330-g0cf0dc5a12`
- About dialog reports `5.12.0-RC2-330-g0cf0dc5a12`
- ParaView dialog is `5.12.0-RC2-330-g0cf0dc5a12`
- find_package(ParaView) report a ParaView_VERSION `5.12.0-RC2-330-g0cf0dc5a12`
It would be nice if the versionning was coherent. Using VTK has an example would be fine imo.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22435Release ParaView 5.12.0-RC22024-01-11T10:51:01-05:00Ryan Krattigerryan.krattiger@kitware.comRelease ParaView 5.12.0-RC2# Update ParaView
- Update the local copy of `release`.
- update `release`
```
git fetch origin
git checkout release
git merge --ff-only origin/release # if this fails, there are local commits that need to ...# Update ParaView
- Update the local copy of `release`.
- 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`):
- [ ] Assemble release notes into `Documentation/release/ParaView-5.12.0.md`.
- [ ] Update `version.txt` and tag the commit (tag this commit below)
```
git checkout -b update-to-v5.12.0-RC2 44aa28bd3151d850dea75a937d50e3141493bdaf
echo 5.12.0-RC2 > version.txt
git commit -m 'Update version number to 5.12.0-RC2' version.txt
```
- Make a commit for each of these `release`-only changes
- [ ] `.gitmodules` to track the `paraview/release` branch of VTK
- [ ] 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
- [ ] Add your development fork as a remote named `gitlab`
- [ ] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m 44aa28bd3151d850dea75a937d50e3141493bdaf`
- [ ] 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).
- [ ] Run the test with `Do: test` and get a green dashboard.
- [ ] Get positive review
- [x] `Do: merge`
- [x] Create tag: `git tag -a -m '5.12.0-RC2' v5.12.0-RC2 commit-that-updated-version.txt`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.12.0-RC2`)
- Upload tarballs to `paraview.org`
- [ ] Setup your `~/.ssh/config` and add the web host (@vbolea).
- [ ] `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
- [ ] Update release branch for **paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [ ] Create new branch `git checkout -b update-to-v5.12.0-RC2 release`
- 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-RC2
- [ ] ARG SUPERBUILD_TAG=v5.12.0-RC2
- [ ] 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-RC2"`
- Make a commit for each of these `release`-only changes
- [ ] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups (if `release` 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-RC2' v5.12.0-RC2 HEAD`
- [ ] Create a commit that changes the paraview _DEFAULT_ source to the git
url source in the `versions.cmake` file.
- [ ] Force `5.12.0-RC2` 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-RC2" CACHE STRING "Force version to 5.12.0-RC2" 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 f1d34a7bd18b3e2b97d431890a2936a21153a156`
- [ ] 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.
- [x] 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-RC2.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.12.0-RC2.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
```
- [ ] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.12.0-RC2`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.12.0-RC2`.
# 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.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/).
- [x] 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/12Ryan Krattigerryan.krattiger@kitware.comRyan Krattigerryan.krattiger@kitware.com2024-01-05https://gitlab.kitware.com/paraview/paraview/-/issues/22429Macs don't show what data format is needed for grayed out filters2024-01-02T11:17:24-05:00W. Alan ScottMacs don't show what data format is needed for grayed out filtersLinux and Windows will show you what data format is needed as input for filters that are grayed out. Mac does not. This needs to be fixed.
* 5.12.0-RC1, Mac, builtin server.
* Open can.exo. Apply.
* Filters/ Alphabetical. Float the m...Linux and Windows will show you what data format is needed as input for filters that are grayed out. Mac does not. This needs to be fixed.
* 5.12.0-RC1, Mac, builtin server.
* Open can.exo. Apply.
* Filters/ Alphabetical. Float the mouse over Connectivity. You cann't see why it is grayed out.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22424Catalyst error when different versions of Conduit are used2023-12-21T13:55:48-05:00W. Alan ScottCatalyst error when different versions of Conduit are usedThe following is a thread from users. This issue is a place to discuss my user's issues with Conduit with Catalyst. I cherrypicked from this thread.
Summary: The catalyst error “catalyst_status_error_conduit_mismatch” is triggered when ...The following is a thread from users. This issue is a place to discuss my user's issues with Conduit with Catalyst. I cherrypicked from this thread.
Summary: The catalyst error “catalyst_status_error_conduit_mismatch” is triggered when a simulation code built with a libcatalyst that uses external conduit tries to communicate with a Paraview built with a libcatalyst that uses its built-in conduit. I believe this is an overly strict check and should be at most a warning. The “CxxFullExample” appears to work correctly with the “mismatched” conduits. If kitware/paraview don't want to support this use case then I guess we can build paraview and alegra against the same libcatalyst/conduit stack but I'd rather not have to do that.
Michael and I are on the Alegra team and trying to integrate Catalyst with the AMR version of Alegra. We’ve found that if the application-side Catalyst2 library is built with a newer version of Conduit than the ParaView Catalyst backend is built with, something goes wrong at runtime (Michael can give details of how it fails). I brought this up at today’s Catalyst meeting and Berk recommended creating a ParaView issue and mentioning Cory Quammen, Christos Tsolakis, and Corey Wetter-Nelson. Michael and I are happy to provide any supporting information for this issue, please let us know how we can help.
From a test:
I just threw some printf’s into the catalyst that I’ve been building and I get:
(in and around catalyst_api.c line 230)
```plaintext
impl-\>version 2
impl-\>conduit_is_external 0
conduit_is_external 0
CATALYST_WITH_EXTERNAL_CONDUIT 1
Failed to initialize Catalyst: 7
```
THEN
\***interestingly**\* when I disable the check
```plaintext
[https://gitlab.kitware.com/paraview/catalyst/-/blob/v2.0.0-rc4/src/catalyst/catalyst_api.c?ref_type=tags#L232](https://gitlab.kitware.com/paraview/catalyst/-/blob/v2.0.0-rc4/src/catalyst/catalyst_api.c?ref_type=tags#L232 "https://gitlab.kitware.com/paraview/catalyst/-/blob/v2.0.0-rc4/src/catalyst/catalyst_api.c?ref_type=tags#L232")
```
It works perfectly!
I should add: somewhere in conduit someone requires MPI::CXX, so I had to modify the catalyst CMakeLists.txt:
```plaintext
if(CATALYST_USE_MPI)
\- find_package(MPI COMPONENTS C REQUIRED)
\+ find_package(MPI COMPONENTS C CXX REQUIRED)
endif()
```
I am of the opinion that this bad usage on the conduit side and they should change it.https://gitlab.kitware.com/paraview/paraview/-/issues/22416Time Manager - Animation - Follow Path is not editable2024-01-15T08:42:15-05:00W. Alan ScottTime Manager - Animation - Follow Path is not editableThe Time Manager, Animation, Follow Path is not editable. Here is how to replicate:
* 5.12.0-RC1, Linux, builtin server
* File/ open/ examples/ can.exo. Apply.
* View/ Time Manager.
* Animations/ Camera/ Follow Path. Blue +.
* Click the...The Time Manager, Animation, Follow Path is not editable. Here is how to replicate:
* 5.12.0-RC1, Linux, builtin server
* File/ open/ examples/ can.exo. Apply.
* View/ Time Manager.
* Animations/ Camera/ Follow Path. Blue +.
* Click the track. Click the "path". (Side issue, this is not obvious that you need to do this. A comment somewhere would be nice.). Camera Position.
Issue 1) I have no mouse control whatsoever of the control points. This is a feature loss. Please add it back. Next, please add the normal - enhanced mouse controls - X, Y, Z.
Issue 2) The control points are set for the can in it's intial position. It should be for the camera when the Follow Path is created. You can see this by using the steps above, but:
* After reading in the can, move the camera.
* After creating the path, click "play".5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22415Time Manager Animations needs to be clarified2023-12-07T20:48:07-05:00W. Alan ScottTime Manager Animations needs to be clarifiedThe Time Manager Animations needs clarification. Do the following:
* 5.12.0-RC1, Linux, builtin server.
* File/ Open/ Examples/ can.exo. Apply
* View/ Time Manager.
Now, we want to create an animation track.
* Animations/ Camera/ Fo...The Time Manager Animations needs clarification. Do the following:
* 5.12.0-RC1, Linux, builtin server.
* File/ Open/ Examples/ can.exo. Apply
* View/ Time Manager.
Now, we want to create an animation track.
* Animations/ Camera/ Follow Path. Click the magic blue +.
I now don't know what type of Camera control I have made. My first suggestion would be to add the words right on the track - "Follow Path Animation. Click here to customize". If that doesn't work, add another line below Camera - Renderview1.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22401Superbuild is failing using system python2024-02-07T07:46:44-05:00W. Alan ScottSuperbuild is failing using system pythonSuperbuild is failing using system python. The issue is pythonwheel is trying to be built and installed, and the install is trying to update the system. We don't have permission to write into system Python. Thus, the build breaks.
I ...Superbuild is failing using system python. The issue is pythonwheel is trying to be built and installed, and the install is trying to update the system. We don't have permission to write into system Python. Thus, the build breaks.
I have given detailed information to Ben offline.
This doesn't impact ParaView itself, but rather memory footprint for Catalyst.
@ben.boeckel5.12.1 (Spring 2024)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22393The IOSS reader is failing reading variables2024-01-04T21:24:45-05:00W. Alan ScottThe IOSS reader is failing reading variablesThe IOSS reader is failing reading variable data for a dataset. This shows with one file of the 640 file dataset. I am giving this file to @cory.quammen. It is ok to pass to anyone at Kitware, but file is DoNotRelease.
* 5 12.0-RC1, L...The IOSS reader is failing reading variable data for a dataset. This shows with one file of the 640 file dataset. I am giving this file to @cory.quammen. It is ok to pass to anyone at Kitware, but file is DoNotRelease.
* 5 12.0-RC1, Linux, builtin server.
* Open IOSS-VariablesDontRead-DoNotRelease.exo. Apply. This will read all blocks and variables.
* Try to paint by a variable from the Properties tab variable list. You can't. This is a bug.
* Delete the file.
* Tools/ Manage Plugins/ load the LegacyExodusReader.
* Open IOSS-VariablesDontRead-DoNotRelease.exo. Use the LegacyExodusReader. Turn on the variables. Apply.
* You will be able to paint by different variables from the Properties tab.
@spiros.tsalikis5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22383ParaView 5.12.0-RC1: failure to build with ADIOS2023-12-31T14:29:30-05:00Jean M. FavreParaView 5.12.0-RC1: failure to build with ADIOSthe following commands lead to errors with ADIOS
```
spack add paraview@5.12.0-RC1 %gcc@11.2.0 +python -qt +mpi +hdf5 +egl +tbb +libcatalyst +adios2 target=haswell ^cray-mpich
spack concretize; spack install
```
```
==> Installing adios...the following commands lead to errors with ADIOS
```
spack add paraview@5.12.0-RC1 %gcc@11.2.0 +python -qt +mpi +hdf5 +egl +tbb +libcatalyst +adios2 target=haswell ^cray-mpich
spack concretize; spack install
```
```
==> Installing adios2-2.9.2-z44xov6mkru4uoyzaadsajmhwzjwcdsi [77/85]
==> No binary for adios2-2.9.2-z44xov6mkru4uoyzaadsajmhwzjwcdsi found: installing from source
==> Fetching https://mirror.spack.io/_source-cache/archive/78/78309297c82a95ee38ed3224c98b93d330128c753a43893f63bbe969320e4979.tar.gz
==> Applied patch /scratch/snx3000tds/jfavre/spack-dom/var/spack/repos/builtin/packages/adios2/2.9.2-cmake-find-threads-package-first.patch
==> adios2: Executing phase: 'cmake'
==> adios2: Executing phase: 'build'
==> adios2: Executing phase: 'install'
==> adios2: Successfully installed adios2-2.9.2-z44xov6mkru4uoyzaadsajmhwzjwcdsi
Stage: 2.93s. Cmake: 40.56s. Build: 1m 23.64s. Install: 27.06s. Post-install: 1.13s. Total: 2m 36.12s
[+] /scratch/snx3000tds/jfavre/spack-dom/opt/spack/cray-cnl7-haswell/gcc-11.2.0/adios2-2.9.2-z44xov6mkru4uoyzaadsajmhwzjwcdsi
[+] /scratch/snx3000tds/jfavre/spack-dom/opt/spack/cray-cnl7-haswell/gcc-11.2.0/py-python-dateutil-2.8.2-idmwz2aunfm5ks7cdddumoodjg73hkng
[+] /scratch/snx3000tds/jfavre/spack-dom/opt/spack/cray-cnl7-haswell/gcc-11.2.0/py-numpy-1.25.2-4tt2cppokuqjlvpwb5kcti4dsg6hwjla
[+] /scratch/snx3000tds/jfavre/spack-dom/opt/spack/cray-cnl7-haswell/gcc-11.2.0/py-bottleneck-1.3.7-ja5qhbsiw7kky3fjcvkbbeetyvsymb2k
[+] /scratch/snx3000tds/jfavre/spack-dom/opt/spack/cray-cnl7-haswell/gcc-11.2.0/py-numexpr-2.8.4-lnz7777kvvyvpmt3uyxjj6owaarcavc7
[+] /scratch/snx3000tds/jfavre/spack-dom/opt/spack/cray-cnl7-haswell/gcc-11.2.0/py-contourpy-1.0.7-qqr2c5perf3m2vd2imqi6zuhdjsdqms7
[+] /scratch/snx3000tds/jfavre/spack-dom/opt/spack/cray-cnl7-haswell/gcc-11.2.0/py-pandas-1.5.3-bjzwjqrnux4vsl3xn7tiviinlhhd2ik5
[+] /scratch/snx3000tds/jfavre/spack-dom/opt/spack/cray-cnl7-haswell/gcc-11.2.0/py-matplotlib-3.8.0-xnxbjjpyezlpjyic4ekfkkyzaj5s6gx5
==> Installing paraview-5.12.0-RC1-5psysxmoey6j2mozikbgcbqjyiec44fy [85/85]
==> No binary for paraview-5.12.0-RC1-5psysxmoey6j2mozikbgcbqjyiec44fy found: installing from source
==> Fetching http://www.paraview.org/files/v5.12/ParaView-v5.12.0-RC1.tar.xz
3 out of 3 hunks FAILED -- saving rejects to file VTK/IO/ADIOS2/CMakeLists.txt.rej
1 out of 1 hunk FAILED -- saving rejects to file VTK/IO/ADIOS2/Testing/Cxx/CMakeLists.txt.rej
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n] n
1 out of 1 hunk ignored -- saving rejects to file VTK/IO/ADIOS2/vtk.module.rej
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
6 out of 6 hunks ignored -- saving rejects to file VTK/IO/ADIOS2/vtkADIOS2CoreImageReader.cxx.rej
==> Patch /scratch/snx3000tds/jfavre/spack-dom/var/spack/repos/builtin/packages/paraview/vtk-adios2-module-no-kit-5.12.patch failed.
==> Error: ProcessError: Command exited with status 1:
'/usr/bin/patch' '-s' '-p' '1' '-i' '/scratch/snx3000tds/jfavre/spack-dom/var/spack/repos/builtin/packages/paraview/vtk-adios2-module-no-kit-5.12.patch' '-d' '.'
==> Updating view at /scratch/snx3000tds/jfavre/spack-dom/var/spack/environments/paraview512-gpu/.spack-env/view
==> Warning: Skipping external package: cray-mpich@7.7.18%gcc@11.2.0 build_system=generic arch=cray-cnl7-haswell/4fvufk3
==> Warning: Skipping external package: egl@1.5.0%gcc@11.2.0 build_system=bundle arch=cray-cnl7-haswell/iiidmpa
==> Warning: Skipping external package: pkg-config@0.29.2%gcc@11.2.0+internal_glib build_system=autotools arch=cray-cnl7-haswell/aiasbqf
==> Warning: Skipping external package: netcdf-c@4.7.4.4%gcc@11.2.0+blosc~byterange~dap~fsync~hdf4~jna+mpi~nczarr_zip+optimize+parallel-netcdf+pic+shared+szip+zstd build_system=autotools patches=cb928a9 arch=cray-cnl7-haswell/lagcnjb
```5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/22379Allow midpoints of color maps to be adjusted with adjacent points being moved2023-11-27T13:41:28-05:00W. Alan ScottAllow midpoints of color maps to be adjusted with adjacent points being movedHere is a proposal from Ken Moreland. Great idea, and it is needed as we add a new default color map. In essence, allow adjustment of control points in the color map editor to proportionally scale all other control points. Keep the ori...Here is a proposal from Ken Moreland. Great idea, and it is needed as we add a new default color map. In essence, allow adjustment of control points in the color map editor to proportionally scale all other control points. Keep the original behavior as an option. Make the new behavior the default.
From Ken:
To follow up on Francesca’s description of moving the midpoint of the colormap, I suggested a slightly more general feature. The idea would be that you would be able to adjust a control point such that the remaining control points would be proportionally scaled with respect to that point. The main use case would be to change the center point as Francesca suggests, but it would work with any control point.
To make the idea clearer, here is an example. Let’s say you have a colormap with 7 evenly spaced control points. Now let’s say you grab the middle control point (the 4th one) and move it to the left. The rest of the control points stay exactly where they are, and the movement of the middle point is constrained to be between the 3rd and 5th point. To really adjust the color map to move the “middle point” from the center of the range, you must independently adjust all the control points, which is problematic even with only 7. What we would like is an alternate move mode where when I move the 4th control point to the left, the 2nd and 3rd control points move closer together and left so that points 1, 2, 3, and 4 remain evenly spaced. Likewise, the 5th and 6th control points move further apart and left so that points 4, 5, 6, and 7 remain evenly spaced.
@kmorel5.13 (Summer 2024)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 Tsalikis