ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-23T12:14:57-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/20483Annotate Global Data filter incorrect for integers2021-03-23T12:14:57-04:00Boonthanome NouanesengsyAnnotate Global Data filter incorrect for integersIn the Annotate Global Data filter, the default Format string is "%7.5g". If a field data has the value 1, then in Paraview 5.8.1, the annotation would show 1. In Paraview 5.9.0, the annotation now shows 0. In python, the output of `"%7....In the Annotate Global Data filter, the default Format string is "%7.5g". If a field data has the value 1, then in Paraview 5.8.1, the annotation would show 1. In Paraview 5.9.0, the annotation now shows 0. In python, the output of `"%7.5g" % 1` is 1, so this looks like a bug.
Here is a test dataset: [wavelet.vti](/uploads/dc4eb224042e5c24881336af76b3d817/wavelet.vti)
To reproduce:
- Open the file in Paraview 5.9.0, and create an Annotate Global Data Filter
- Hit Apply, and the annotation will show 0, but the actual value of the field data is 1
Edit: I just tried this on the latest master, and with master the annotation says 6.9531e-310.
@patchett2002 @cory.quammen @utkarsh.ayachit
![screenshot](/uploads/1ee2c6a21c6ce8de0daf510efcd675fd/screenshot.png)5.9.1 (Spring 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20482Add ability to write cinema recolorable images with the extracts generator2021-04-08T08:58:24-04:00Ethan StamAdd ability to write cinema recolorable images with the extracts generator@dhr @utkarsh.ayachit
ParaView should have the capability to save recolorable images and cinema databases with recolorable images using the extract generators. Those should also be readable using the viewers available in the cinemasci ...@dhr @utkarsh.ayachit
ParaView should have the capability to save recolorable images and cinema databases with recolorable images using the extract generators. Those should also be readable using the viewers available in the cinemasci third party library.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachit2021-03-31https://gitlab.kitware.com/paraview/paraview/-/issues/20481Cinemasci: add a test for running the server and viewers on Kitware's dashboards2024-03-07T20:23:44-05:00Ethan StamCinemasci: add a test for running the server and viewers on Kitware's dashboards@dhr @utkarsh.ayachit
There should be a test on Kitware's side for the cinemasci viewer server. David and I will work on this. Maybe it could be an extra step at the end of the wavelet miniapp tests for the extracts generator.@dhr @utkarsh.ayachit
There should be a test on Kitware's side for the cinemasci viewer server. David and I will work on this. Maybe it could be an extra step at the end of the wavelet miniapp tests for the extracts generator.5.13 (Summer 2024)Ethan StamEthan Stamhttps://gitlab.kitware.com/paraview/paraview/-/issues/20462vtkOSPRayMaterialLibrar error prints2021-04-26T19:57:22-04:00W. Alan ScottvtkOSPRayMaterialLibrar error printsThis error is showing in the 5.9.0 release, without OSPRay turned on. 5.9.0 release, paraview.org download client, Linux, remote server.
Showing up client side, after connecting to the server.
```
( 14.440s) [paraview ]vtkO...This error is showing in the 5.9.0 release, without OSPRay turned on. 5.9.0 release, paraview.org download client, Linux, remote server.
Showing up client side, after connecting to the server.
```
( 14.440s) [paraview ]vtkOSPRayMaterialLibrar:280 ERR| vtkOSPRayMaterialLibrary (0x152b6dd0): JSON parsing error: * Line 1, Column 1
Syntax error: value, object or array expected.
ERROR: In /builds/gitlab-kitware-sciviz-ci/build/superbuild/paraview/src/VTK/Rendering/RayTracing/vtkOSPRayMaterialLibrary.cxx, line 280
vtkOSPRayMaterialLibrary (0x152b6dd0): JSON parsing error: * Line 1, Column 1
Syntax error: value, object or array expected.
```
Note that I CANNOT hide this one from users.5.9.1 (Spring 2021)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/20459VisRTXBackend.cxx error prints2021-04-26T20:13:42-04:00W. Alan ScottVisRTXBackend.cxx error printsI am seeing dozens of the following errors with the 5.9.0 release, Linux, download from the Kitware website, builtin server. There are 38 error lines. This needs to be fixed, at least in 5.9.1.
```
( 2.011s) [paraview ] ...I am seeing dozens of the following errors with the 5.9.0 release, Linux, download from the Kitware website, builtin server. There are 38 error lines. This needs to be fixed, at least in 5.9.1.
```
( 2.011s) [paraview ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.034s) [paraview ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.034s) [paraview ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.034s) [paraview ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
```5.9.1 (Spring 2021)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20454XL build of ParaView 5.8.1 and 5.9.0 fails at curly brace initializing2021-02-17T18:15:18-05:00Ethan StamXL build of ParaView 5.8.1 and 5.9.0 fails at curly brace initializing@ben.boeckel
Relevant discussion here: https://gitlab.kitware.com/paraview/paraview/-/issues/20253#note_892895
Using ibm xlc 16.1.1.7, xlf 16.1.1.7, gcc 8.3.0, cuda-11.0 . ParaView 5.8.1 and 5.9.0 builds fail with:
```console
In file...@ben.boeckel
Relevant discussion here: https://gitlab.kitware.com/paraview/paraview/-/issues/20253#note_892895
Using ibm xlc 16.1.1.7, xlf 16.1.1.7, gcc 8.3.0, cuda-11.0 . ParaView 5.8.1 and 5.9.0 builds fail with:
```console
In file included from .../VTK/Common/DataModel/vtkStaticCellLinksTemplate.h:162:
.../VTK/Common/DataModel/vtkStaticCellLinksTemplate.txx:359:61: error: 1540-2991 The expression is not supported.
std::atomic<TIds>* counts = new std::atomic<TIds>[numPts] {};
^
```
https://www.ibm.com/support/knowledgecenter/en/SSXVZZ_16.1.1/com.ibm.xlcpp1611.lelinux.doc/language_ref/standard_features.html shows XL does not fully support std::atomic . We were not hitting this issue when vtkAtomic was used.
Edit: It looks like std::atomic is not the root cause, but the use of `{}` is. Possible workaround in https://gitlab.kitware.com/paraview/paraview/-/issues/20454#note_896613https://gitlab.kitware.com/paraview/paraview/-/issues/20446Release Paraview 5.9.02021-03-18T12:24:32-04:00Vicente Boleavicente.bolea@kitware.comRelease Paraview 5.9.0# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.9.0.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Assemble release notes into `Documentation/release/ParaView-5.9.0`.
- [x] Get positive review and merge.
# Update ParaView
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.9.0
echo 5.9.0 > version.txt
git commit -m 'Update version number to 5.9.0' version.txt
git tag -a -m 'ParaView 5.9.0' v5.9.0 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] `Do: merge`
- Integrate changes to `release` branch (push the `update-to-v@version@` branch to be the new `release` branch)
- [x] `git push origin update-to-v5.9.0:release`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.9.0`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs user@host:ParaView_Release/v5.9/`
# Update ParaView-Superbuild
- [x] Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
git checkout -b update-to-v5.9.0
```
- Update `CMakeLists.txt`
- [x] Update PARAVIEW_VERSION_DEFAULT to the release version (without RC*)
- [x] Set ParaView source selections in `CMakeLists.txt` and force explicit
version in `CMakeLists.txt`:
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.9.0" CACHE STRING "Force version to 5.9.0" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] `paraview_SOURCE_SELECTION` version in `README.md`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.9.0
- [x] ARG SUPERBUILD_TAG=v5.9.0
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.9
- [x] Commit changes and push to GitLab
```
git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile
git commit -m "Update the default version to 5.9.0"
git gitlab-push
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP (do *not* add `Backport: release` to description)
- [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 explicit version forcing added in `CMakeLists.txt` and force push
```
git add CMakeLists.txt
git commit --amend --no-edit
git gitlab-push -f
```
- Finalize merge request
- [x] Remove WIP from merge request title
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.9.0' v5.9.0 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.9.0:release`
# 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.9.0.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.9.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
- 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
- OptiX pathtracing runs
- IndeX runs
- AutoMPI
Binary checklist
- [x] macOS
- [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.9/`)
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website
```
buildListing.sh
updateMD5sum.sh v5.9
```
- [x] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.9.0`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.9.0`.
# Spack
- [x] Update Spack package: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py
# Update documentation
- [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 [ParaView docs](https://gitlab.kitware.com/paraview/paraview-docs/-/tags) with v5.9.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/).
- [x] Request DoD vulnerability scan
- [x] Request update of version number in "Download Latest Release" text on www.paraview.org
- [x] Request update of link to ParaView Guide PDF at https://www.paraview.org/paraview-guide/
- [x] Move unclosed issues to next release milestone in GitLab
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachitVicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20443Cinemasci server not working with 5.9.0-RC42021-02-18T10:09:47-05:00Ethan StamCinemasci server not working with 5.9.0-RC4@utkarsh.ayachit @dhr is aware and working on a fix. If this can still make it into 5.9.0, that would be great. Thanks.
Steps to reproduce:
1. Download and install 5.9.0-RC4 from paraview.org
2. Run the cinemasci server (no cinema datab...@utkarsh.ayachit @dhr is aware and working on a fix. If this can still make it into 5.9.0, that would be great. Thanks.
Steps to reproduce:
1. Download and install 5.9.0-RC4 from paraview.org
2. Run the cinemasci server (no cinema database needed to reproduce) with `/Applications/ParaView-5.9.0-RC4.app/Contents/bin/pvpython -m paraview.tpl.cinemasci.server`
```console
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Traceback (most recent call last):
File "/Applications/ParaView-5.9.0-RC4.app/Contents/Libraries/lib/python3.8/runpy.py", line 185, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/Applications/ParaView-5.9.0-RC4.app/Contents/Libraries/lib/python3.8/runpy.py", line 144, in _get_module_details
return _get_module_details(pkg_main_name, error)
File "/Applications/ParaView-5.9.0-RC4.app/Contents/Libraries/lib/python3.8/runpy.py", line 111, in _get_module_details
__import__(pkg_name)
File "/Applications/ParaView-5.9.0-RC4.app/Contents/Python/paraview/tpl/cinemasci/server/__init__.py", line 14, in <module>
import cinemasci
ModuleNotFoundError: No module named 'cinemasci'
```5.9.1 (Spring 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20436Release ParaView 5.9.0-RC42021-01-19T09:56:58-05:00Vicente Boleavicente.bolea@kitware.comRelease ParaView 5.9.0-RC4# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.9.0.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Assemble release notes into `Documentation/release/ParaView-5.9.0`.
- [x] Get positive review and merge.
# Update ParaView
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.9.0-RC4
echo 5.9.0-RC4 > version.txt
git commit -m 'Update version number to 5.9.0-RC4' version.txt
git tag -a -m 'ParaView 5.9.0-RC4' v5.9.0-RC4 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] `Do: merge`
- Integrate changes to `release` branch (push the `update-to-v@version@-RC4` branch to be the new `release` branch)
- [x] `git push origin update-to-v5.9.0-RC4:release`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.9.0-RC4`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs user@host:ParaView_Release/v5.9/`
# Update ParaView-Superbuild
- [x] Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
git checkout -b update-to-v5.9.0-RC4
```
- Update `CMakeLists.txt`
- [x] Update PARAVIEW_VERSION_DEFAULT to the release version (without RC*)
- [x] Set ParaView source selections in `CMakeLists.txt` and force explicit
version in `CMakeLists.txt`:
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.9.0-RC4" CACHE STRING "Force version to 5.9.0-RC4" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] `paraview_SOURCE_SELECTION` version in `README.md`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.9.0-RC4
- [x] ARG SUPERBUILD_TAG=v5.9.0-RC4
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.9
- [x] Commit changes and push to GitLab
```
git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile
git commit -m "Update the default version to 5.9.0-RC4"
git gitlab-push
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP (do *not* add `Backport: release` to description)
- [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 explicit version forcing added in `CMakeLists.txt` and force push
```
git add CMakeLists.txt
git commit --amend --no-edit
git gitlab-push -f
```
- Finalize merge request
- [x] Remove WIP from merge request title
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.9.0-RC4' v5.9.0-RC4 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.9.0-RC4:release`
# 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.9.0-RC4.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.9.0-RC4.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
- 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
- OptiX pathtracing runs
- IndeX runs
- AutoMPI
Binary checklist
- [x] macOS
- [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.9/`)
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website
```
buildListing.sh
updateMD5sum.sh v5.9
```
- [x] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.9.0-RC4`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.9.0-RC4`.
# Spack
- [x] Update Spack package: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [ ] Request DoD vulnerability scan
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20432Information Tab does not list time correctly2021-01-19T11:02:11-05:00Boonthanome NouanesengsyInformation Tab does not list time correctlyAt the bottom of the Information Tab, there is a list of all the timesteps, along with their time. For the latest master as of January 8th, all the time values are listed as 0.0. If I load the same dataset in Paraview 5.8.1, the proper t...At the bottom of the Information Tab, there is a list of all the timesteps, along with their time. For the latest master as of January 8th, all the time values are listed as 0.0. If I load the same dataset in Paraview 5.8.1, the proper time values are listed.
Example dataset: [mg_diff_small.tar.gz](/uploads/40244d0e8d0bf37885d667f9c2ae0a4d/mg_diff_small.tar.gz)
Screenshot of Information Tab when loading the example dataset in the latest master:
![info_tab](/uploads/976607fae9f1594e79282e0ad34641c1/info_tab.png)
While on this topic, why is the second column of this labeled `Value`? Could we perhaps label this as `Time`, so it's clear what it is?
@patchett2002 @cory.quammen @utkarsh.ayachit5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20422Numeric keypad not recognized on Ubuntu machines2021-04-30T15:50:00-04:00John TourtellottNumeric keypad not recognized on Ubuntu machinesOn Ubuntu machines, paraview only responds to numeric keys in the main keyboard area, and does NOT respond to the numeric keypad. Using ParaView-5.9.0-RC3-MPI-Linux-Python3.8-64bit.tar.gz from paraview.org/download:
* Create Wavelet sou...On Ubuntu machines, paraview only responds to numeric keys in the main keyboard area, and does NOT respond to the numeric keypad. Using ParaView-5.9.0-RC3-MPI-Linux-Python3.8-64bit.tar.gz from paraview.org/download:
* Create Wavelet source
* Try editing one of the numeric fields (e.g., "Whole Extent", "Center")
* You can edit with the numeric keys in the main keyboard but not the numeric keypad on the side.
Tested/confirmed with Ubuntu 16.04 and 20.04 machines.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20421Spreadsheet view does not show field data2021-09-07T14:46:57-04:00Boonthanome NouanesengsySpreadsheet view does not show field dataField data is not shown in the spreadsheet view. Below is a screenshot of Paraview. You can see some field data on the left, and in the spreadsheet view at the bottom, nothing is shown.
Here is the dataset shown: [mg_diff.tar.gz](/uploa...Field data is not shown in the spreadsheet view. Below is a screenshot of Paraview. You can see some field data on the left, and in the spreadsheet view at the bottom, nothing is shown.
Here is the dataset shown: [mg_diff.tar.gz](/uploads/a7d948234cd89f608fd16b467eeeccd8/mg_diff.tar.gz)
![no_fielddata](/uploads/350fa5923a5e0e1e98e4ed5a2b90a899/no_fielddata.png)
@patchett2002 @cory.quammen @utkarsh.ayachit5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20420Show field data strings in Information Tab2021-01-21T13:55:27-05:00Boonthanome NouanesengsyShow field data strings in Information TabCurrently, if you look at field data that is of data type string in the Information Tab, the Data Range will have a value of "NA". It would be nice to see string field data somehow. An image of what it currently looks like is below.
It ...Currently, if you look at field data that is of data type string in the Information Tab, the Data Range will have a value of "NA". It would be nice to see string field data somehow. An image of what it currently looks like is below.
It would be nice to have some way to see string field data in the Information Tab. Either show a certain number of characters in the Data Range column, or maybe have a separate box in the Information Tab that shows all field data.
Here is an example dataset with some string field data: [mg_diff.tar.gz](/uploads/f7ec397703d1ac12077a05102ea3c9f4/mg_diff.tar.gz)
![fielddata](/uploads/b42719a69572d50735bb511c6b9e512d/fielddata.png)
@patchett2002 @cory.quammen @utkarsh.ayachit5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20409Connecting to the server using the binary release is very slow2023-10-09T11:51:44-04:00Mathieu Westphal (Kitware)Connecting to the server using the binary release is very slowConnecting to a server with 5.9-RC2 is really slow.
Steps to reproduce:
```
./bin/pvserver -dr
./bin/paraview -dr
connect to localhost
```
* 5.8.1: 2s
* 5.9: 40s
* 5.10.0: 16s
* 5.11: 30s
* master (debug): 2s
@cory.quammen @utkarsh...Connecting to a server with 5.9-RC2 is really slow.
Steps to reproduce:
```
./bin/pvserver -dr
./bin/paraview -dr
connect to localhost
```
* 5.8.1: 2s
* 5.9: 40s
* 5.10.0: 16s
* 5.11: 30s
* master (debug): 2s
@cory.quammen @utkarsh.ayachit5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20403Windows: ParaView 5.9.0-RC2 + mesa-opengl-64 dll's doesn't open2022-07-18T18:03:43-04:00Ethan StamWindows: ParaView 5.9.0-RC2 + mesa-opengl-64 dll's doesn't open@utkarsh.ayachit @cory.quammen @patchett2002
LANL has windows machines without GPU's that need to be able to run paraview. I tested on a machine that does have a GPU, if that could cause problems.
Using the mesa dll's (https://www.par...@utkarsh.ayachit @cory.quammen @patchett2002
LANL has windows machines without GPU's that need to be able to run paraview. I tested on a machine that does have a GPU, if that could cause problems.
Using the mesa dll's (https://www.paraview.org/files/dependencies/mesa-opengl-win64.zip) with 5.9.0-RC2 zipped for Windows (https://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.9&type=binary&os=Windows&downloadFile=ParaView-5.9.0-RC2-Windows-Python3.8-msvc2017-64bit.zip) does not work. Opening paraview starts an output window that closes after a bit without any output.
Steps to reproduce:
1. Download and unzip both links above
2. Copy the 3 dll's from `mesa-opengl-win64` to the same directory as `paraview.exe`
3. Run `paraview.exe`https://gitlab.kitware.com/paraview/paraview/-/issues/20399Release Paraview 5.9.0-RC32020-12-21T21:10:13-05:00Vicente Boleavicente.bolea@kitware.comRelease Paraview 5.9.0-RC3# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.9.0.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Assemble release notes into `Documentation/release/ParaView-5.9.0`.
- [x] Get positive review and merge.
# Update ParaView
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.9.0-RC3
echo 5.9.0-RC3 > version.txt
git commit -m 'Update version number to 5.9.0-RC3' version.txt
git tag -a -m 'ParaView 5.9.0-RC3' v5.9.0-RC3 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] `Do: merge`
- Integrate changes to `release` branch (push the `update-to-v@version@-RC3` branch to be the new `release` branch)
- [x] `git push origin update-to-v5.9.0-RC3:release`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.9.0-RC3`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs user@host:ParaView_Release/v5.9/`
# Update ParaView-Superbuild
- [x] Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
git checkout -b update-to-v5.9.0-RC3
```
- Update `CMakeLists.txt`
- [x] Update PARAVIEW_VERSION_DEFAULT to the release version (without RC*)
- [x] Set ParaView source selections in `CMakeLists.txt` and force explicit
version in `CMakeLists.txt`:
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.9.0-RC3" CACHE STRING "Force version to 5.9.0-RC3" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] `paraview_SOURCE_SELECTION` version in `README.md`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.9.0-RC3
- [x] ARG SUPERBUILD_TAG=v5.9.0-RC3
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.9
- [x] Commit changes and push to GitLab
```
git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile
git commit -m "Update the default version to 5.9.0-RC3"
git gitlab-push
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP (do *not* add `Backport: release` to description)
- [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 explicit version forcing added in `CMakeLists.txt` and force push
```
git add CMakeLists.txt
git commit --amend --no-edit
git gitlab-push -f
```
- Finalize merge request
- [x] Remove WIP from merge request title
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.9.0-RC3' v5.9.0-RC3 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.9.0-RC3:release`
# 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.9.0-RC3.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.9.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
- 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
- OptiX pathtracing runs
- IndeX runs
- AutoMPI
Binary checklist
- [x] macOS
- [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.9/`)
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website
```
buildListing.sh
updateMD5sum.sh v5.9
```
- [x] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.9.0-RC3`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.9.0-RC3`.
# Spack
- [x] Update Spack package: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [ ] Request DoD vulnerability scan
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachitVicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20388make the Annotate Global Data Filter not depend on numpy2021-02-15T18:42:14-05:00Boonthanome Nouanesengsymake the Annotate Global Data Filter not depend on numpyThe Annotate Global Data Filter currently depends on the python module numpy. This has caused problems for use in the past, as sometimes numpy will not be present in a python, or numpy will cause conflicts with other dependencies. It wou...The Annotate Global Data Filter currently depends on the python module numpy. This has caused problems for use in the past, as sometimes numpy will not be present in a python, or numpy will cause conflicts with other dependencies. It would be nice if the numpy dependency was removed.
@cory.quammen @utkarsh.ayachit @patchett20025.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20387Redundant calculator icon2020-12-16T15:47:24-05:00W. Alan ScottRedundant calculator iconWe have a redundant calculator icon that has appeared in 5.9.0-RC1. One is in the common filters toolbar, the other is in the Data Analysis toolbar. The Data Analysis one is a mistake, and should be removed.
@utkarsh.ayachit @cory.qu...We have a redundant calculator icon that has appeared in 5.9.0-RC1. One is in the common filters toolbar, the other is in the Data Analysis toolbar. The Data Analysis one is a mistake, and should be removed.
@utkarsh.ayachit @cory.quammen Not sure how to schedule this. We are late to remove it, but it should be deleted.https://gitlab.kitware.com/paraview/paraview/-/issues/20386Material volume fraction filter crashes in spreadsheet2021-01-21T13:36:56-05:00W. Alan ScottMaterial volume fraction filter crashes in spreadsheetThe material volume fraction filter crashes when you try to display the data in the spreadsheet. I believe the issue is with the spreadsheet. This works correctly with ParaView 5.8.0. Here is how to replicate:
* 5.9.0-RC2, Linux, rem...The material volume fraction filter crashes when you try to display the data in the spreadsheet. I believe the issue is with the spreadsheet. This works correctly with ParaView 5.8.0. Here is how to replicate:
* 5.9.0-RC2, Linux, remote server (I am using 16 ranks).
* Load Dave's small cth dataset. It will have 4 files. All vars on. Apply.
* Split screen vertical.
* Spreadsheet.
There will be the following warning message. Note that this error message occurs builtin server:
Warning: In /projects/viz/paraview/src/ParaView/5.9.0-RC2/ParaView5/VTK/Common/DataModel/vtkDataObject.cxx, line 498
vtkMultiBlockDataSet (0xc2c5140): Attempted to ShallowCopy from null.
* Close the Spreadsheet View. Close the Output View.
* Material Interface Filter. Only select the "Material volume fraction - 1" variable. Select Mass Arrays: "Mass (g) -1". Apply.
* Split Vertical. Spreadsheet.
Crash. Note this crash does NOT occur builtin server. Server side crash. I am on a release build, could make it debug if desired.
@utkarsh.ayachit @cory.quammen Showstopper bug for the 5.9.0 release.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20382RC2 is having issues with CGNS and Point Gaussian2020-12-15T12:01:34-05:00W. Alan ScottRC2 is having issues with CGNS and Point GaussianWhen reading the HiFIRE CGNS dataset, and using representation Point Gaussian, it appears that it isn't Z buffering correctly. Here is how to replicate:
* remote server (64 ranks), 5.9.0-RC2, Linux.
* Load the cgns HiFire dataset. I t...When reading the HiFIRE CGNS dataset, and using representation Point Gaussian, it appears that it isn't Z buffering correctly. Here is how to replicate:
* remote server (64 ranks), 5.9.0-RC2, Linux.
* Load the cgns HiFire dataset. I turned all vars on, but not necessary. Apply.
* Point Gaussian.
It will look jumbled.
@utkarsh.ayachit @cory.quammen Not sure if we need to fix this for 5.9.0. Thoughts?5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachit