ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-24T08:56:41-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/20418Invalid reported time values with some OpenFoam data2021-03-24T08:56:41-04:00Sebastien JourdainInvalid reported time values with some OpenFoam data`simple.GetAnimationScene().TimeKeeper.TimestepValues` is not always reporting a list of values but a single time value instead (float vs [float]).
Initially reported [here](https://github.com/Kitware/paraviewweb/issues/524)`simple.GetAnimationScene().TimeKeeper.TimestepValues` is not always reporting a list of values but a single time value instead (float vs [float]).
Initially reported [here](https://github.com/Kitware/paraviewweb/issues/524)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20417Window layout not saved in 5.9-RC32021-04-20T14:15:39-04:00Pierre CrepierWindow layout not saved in 5.9-RC3I've been playing around with the 5.9 release candidates (downloaded from paraview.org), both on my windows laptop and on a linux cluster.
On the linux version, if I toogle the view of the output messages and the python shell for example...I've been playing around with the 5.9 release candidates (downloaded from paraview.org), both on my windows laptop and on a linux cluster.
On the linux version, if I toogle the view of the output messages and the python shell for example, they appear on the screen.
Then I close ParaView, and re-open it. Now I expect that the two views I toogled before would be shown, but it is not the case.
This happens only with the linux version, I do not experience this with the windows build.
I had not this issue with versions 5.6, 5.7 and 5.8.
Is this the expected behavior, or I am missing a save button hidden somehwere ?https://gitlab.kitware.com/paraview/paraview/-/issues/20416v5.9.0-RC3: Normals and colors missing from Contour filter when first contour...2021-01-04T18:57:50-05:00Cory Quammencory.quammen@kitware.comv5.9.0-RC3: Normals and colors missing from Contour filter when first contour value lies outside data rangeSteps to reproduce:
* Add **Wavelet** source
* Add **Contour** filter. Set the isovalue to 0.0. Apply.
* Change the isovalue to 100. Apply.
* The resulting geometry will be displayed without any pseudocoloring applied or normals, even t...Steps to reproduce:
* Add **Wavelet** source
* Add **Contour** filter. Set the isovalue to 0.0. Apply.
* Change the isovalue to 100. Apply.
* The resulting geometry will be displayed without any pseudocoloring applied or normals, even though those arrays are the same.
* Create a new **Contour** filter with the isovalue set to 100 before clicking Apply. The surface will be pseudocolored and the surface will be smooth.
Active scalars/normals are set in the output's point data as expected.https://gitlab.kitware.com/paraview/paraview/-/issues/20415Windows Mesa support in binaries2021-03-24T08:57:32-04:00Utkarsh AyachitWindows Mesa support in binariesOn linux, we bundle Mesa `.so`s with the package and make it easier for users to run paraview using Mesa by passing a command line argument. We don't have any such support on Windows. Here's how to add it:
* [ ] add mesa (with swr) bina...On linux, we bundle Mesa `.so`s with the package and make it easier for users to run paraview using Mesa by passing a command line argument. We don't have any such support on Windows. Here's how to add it:
* [ ] add mesa (with swr) binary building support to ParaVIew superbuild
* [ ] add "launcher" scripts (or executables) that setup appropriate environment variables and then launch the actual executables
* [ ] add shortcuts to launch paraview with different command lines for mesa, mesa+swr etc.
ref: paraview/paraview#20403https://gitlab.kitware.com/paraview/paraview/-/issues/20414Gitlab-CI master bug2023-06-19T10:43:34-04:00Utkarsh AyachitGitlab-CI master bugI am creating this issue to discuss and track missing features / bug with gitlab ci.
* [ ] get `Do: test` working. Without this, it's not easy for developers to tell which builds must be run on the MR. For example, we have spack and doc...I am creating this issue to discuss and track missing features / bug with gitlab ci.
* [ ] get `Do: test` working. Without this, it's not easy for developers to tell which builds must be run on the MR. For example, we have spack and doc builders that don't need to be run on MRs.
* [ ] Make it easier to go to CDash link. Once `Do: test` starts working, this will probably work out of the box. The way it is exposed currently is confusing.
* [ ] ParaView-Superbuild CI jobs don't show up correctly on CDash. The builds and tests are not getting appended.
cc: @ben.boeckel @cory.quammen @mwestphal @vboleahttps://gitlab.kitware.com/paraview/paraview/-/issues/20413Segmentation Fault: Load State with Saved Python Animation Track2021-01-15T07:49:27-05:00Joel A. KuleszaSegmentation Fault: Load State with Saved Python Animation TrackObserved with ParaView 5.9.0 RC3 on macOS 10.14.6.
# Summary
Loading a ParaView state `.pvsm` file with a saved Python track crashes. I wonder whether this is because of "cruft" stored in the state file to deal with the editor (e.g., ...Observed with ParaView 5.9.0 RC3 on macOS 10.14.6.
# Summary
Loading a ParaView state `.pvsm` file with a saved Python track crashes. I wonder whether this is because of "cruft" stored in the state file to deal with the editor (e.g., `<Element index="0" value="def start_cue(self): pass

def tick(self): 
 print("Hello")

def end_cue(self): pass"/>`)...
# Steps to Reproduce
1. Launch ParaView 5.9.0 RC3
2. Open View -> Animation View
3. Add Python Track (click "+" next to Python selected in track dropdown)
4. Double click on Python track to get code editor, enter:
```python
def start_cue(self): pass
def tick(self):
print("Hello")
def end_cue(self): pass
```
5. Click OK on code editor
6. File -> Save State
7. Quit ParaView
8. Relaunch ParaView 5.9.0 RC3
9. File -> Load State -> Select previously saved file
10. **crash**
I see the attached log using the attached state file.
/cc @patchett2002 @ethan.stam
# P.S.
When I open the code editor here (or another, e.g., Programmable Filter), I see:
```
warning: In unknown, line 0
warning: Populating font family aliases took 744 ms. Replace uses of missing font family "Monospace" with one that exists to avoid this cost.
```
This seems to be "new" behavior---is this expected?
[pytrack_crash.pvsm](/uploads/060ea127b04b93185a74bb52aa61a5b3/pytrack_crash.pvsm)
[pytrack_crash.log](/uploads/bb0e827895f0b9efef144f4dfc3188bf/pytrack_crash.log)5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20412loading plugin causes2021-02-01T10:46:17-05:00Nico Schlömerloading plugin causesWhen loading the ParaView plugin from meshio, https://github.com/nschloe/meshio#paraview-plugin, with PV 5.9.0-RC3, I'm getting
```
malloc(): invalid size (unsorted)
Loguru caught a signal: SIGABRT
```
What can I do to debug?When loading the ParaView plugin from meshio, https://github.com/nschloe/meshio#paraview-plugin, with PV 5.9.0-RC3, I'm getting
```
malloc(): invalid size (unsorted)
Loguru caught a signal: SIGABRT
```
What can I do to debug?https://gitlab.kitware.com/paraview/paraview/-/issues/20411CDI reader error2021-01-04T05:39:15-05:00Samuel LapereCDI reader errorHi, I've installed the pre-built ParaView-5.8.1 binaries on a remote server to visualize a very large NetCDF file with ParaView's built-in CDI reader plugin. When I try to load the file, I receive the following message:
`ERROR: In /home...Hi, I've installed the pre-built ParaView-5.8.1 binaries on a remote server to visualize a very large NetCDF file with ParaView's built-in CDI reader plugin. When I try to load the file, I receive the following message:
`ERROR: In /home/buildslave/dashboards/buildbot/paraview_release-pvbinsdash-linux-shared-release_osmesa_superbuild/build/superbuild/paraview/src/Plugins/CDIReader/Reader/vtkCDIReader.cxx, line 1098
vtkCDIReader (0x1709a60): Couldn't open file: No such file or directory`
The path referred to in the error ("/home/buildslave/...") does not exist on the server. Anyone knows how this could be solved?https://gitlab.kitware.com/paraview/paraview/-/issues/20410Create a script to manage dynamic groups2021-01-14T21:24:13-05:00Ben BoeckelCreate a script to manage dynamic groupsCDash has [an API](https://github.com/Kitware/CDash/issues/1099) that we can use to manage the Dynamic Build Groups on CDash. Let's create a script to do this since the web UI is finicky and typos can be easy to get wrong.
Cc: @cory.qua...CDash has [an API](https://github.com/Kitware/CDash/issues/1099) that we can use to manage the Dynamic Build Groups on CDash. Let's create a script to do this since the web UI is finicky and typos can be easy to get wrong.
Cc: @cory.quammen @vbolea @utkarsh.ayachitBen BoeckelBen Boeckelhttps://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/20408glTF Exporter only export first block from multiblock2022-12-08T09:04:39-05:00Mathieu Westphal (Kitware)glTF Exporter only export first block from multiblockglTF Exporter only export first block from multiblock
Steps to reproduce:
* Open ParaView
* Open Can.ex2
* Export scene to glTF
* Visualize glTF in another tools
* Only first block is exported
@ken-martinglTF Exporter only export first block from multiblock
Steps to reproduce:
* Open ParaView
* Open Can.ex2
* Export scene to glTF
* Visualize glTF in another tools
* Only first block is exported
@ken-martinhttps://gitlab.kitware.com/paraview/paraview/-/issues/20407Add support for shortcuts with toolbar actions2022-12-06T05:08:46-05:00Mathieu Westphal (Kitware)Add support for shortcuts with toolbar actionsIt would be nice to be able to set shortcuts for actions usually controlled by toolbar actions.It would be nice to be able to set shortcuts for actions usually controlled by toolbar actions.https://gitlab.kitware.com/paraview/paraview/-/issues/20406create_tarballs.bash fails to include vtk-m subdmodule in tarballs with git 2...2021-01-18T08:47:40-05:00Cory Quammencory.quammen@kitware.comcreate_tarballs.bash fails to include vtk-m subdmodule in tarballs with git 2.28.0vtk-m source files are not copied into tarballs.
The extracted source directory `VTK/ThirdParty/vtkm/vtkvtkm/vtk-m` should exist. With git 2.28.0, it does not.
Note: I suspect the git version is at play here, but I do not know exactly ...vtk-m source files are not copied into tarballs.
The extracted source directory `VTK/ThirdParty/vtkm/vtkvtkm/vtk-m` should exist. With git 2.28.0, it does not.
Note: I suspect the git version is at play here, but I do not know exactly which version the problem started with.Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/20405Loading saved states from scripts does not work2021-01-04T16:27:10-05:00Emanuele LeggioLoading saved states from scripts does not workThe following simple script writes a test.pvsm state, that state is unreadable by the GUI with the following versions of ParaView:
* 5.7.0
* 5.8.1
* 5.9.0-RC2
```python
from paraview.simple import *
cone = Cone()
rv = GetRenderView()
...The following simple script writes a test.pvsm state, that state is unreadable by the GUI with the following versions of ParaView:
* 5.7.0
* 5.8.1
* 5.9.0-RC2
```python
from paraview.simple import *
cone = Cone()
rv = GetRenderView()
dr = Show(cone, rv)
SaveState('test.pvsm')
```
Screenshot of ParaView 5.7.0 GUI when trying to open test.pvsm
![PV57GUI_loading_state](/uploads/b501b03bd1deadc66a3db81b648feca5/PV57GUI_loading_state.png)
No problem with ParaView 5.3.0
![PV53GUI_loading_state](/uploads/21b1f36904e840cb4b194ca895b10ab2/PV53GUI_loading_state.png)
In my tests i used pvbatch and paraview of the same version to run the script and to open the test.pvsm state.https://gitlab.kitware.com/paraview/paraview/-/issues/20404Unable to Launch Paraview on Windows Server 20192021-03-24T09:20:42-04:00faizah crUnable to Launch Paraview on Windows Server 2019HI Support Team,
im having difficulties on Running Paraview Version 5.8.1 on windows Server 2019.May i know is there any issue on this OS
I Having no issue on Windows 10.
Thanks
RegardsHI Support Team,
im having difficulties on Running Paraview Version 5.8.1 on windows Server 2019.May i know is there any issue on this OS
I Having no issue on Windows 10.
Thanks
Regardshttps://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/20402v5.9-RC2 unsupported option ‘–unresolved-symbols=ignore-in-shared-libs’2023-04-27T08:19:17-04:00Jean M. Favrev5.9-RC2 unsupported option ‘–unresolved-symbols=ignore-in-shared-libs’While compiling ParaView 5.9, my cmake (v3.19.2) generates compilation options which my compiler does not support.
See output details here:
https://discourse.cmake.org/t/cmake-generates-compiler-options-not-supported/2391While compiling ParaView 5.9, my cmake (v3.19.2) generates compilation options which my compiler does not support.
See output details here:
https://discourse.cmake.org/t/cmake-generates-compiler-options-not-supported/2391https://gitlab.kitware.com/paraview/paraview/-/issues/20401v5.9-RC2 plugin search path2023-11-27T09:29:40-05:00Jean M. Favrev5.9-RC2 plugin search pathplugins are said to be automatically searched for in <INSTALL_PATH>/bin/plugins, yet they are installed in <INSTALL_PATH>/lib64/paraview-5.9/plugins. The search path should be updated. Full discussion here:
https://discourse.paraview.or...plugins are said to be automatically searched for in <INSTALL_PATH>/bin/plugins, yet they are installed in <INSTALL_PATH>/lib64/paraview-5.9/plugins. The search path should be updated. Full discussion here:
https://discourse.paraview.org/t/plugins-search-path/6080Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/20400v5.9-RC2 No module named 'vtkmodules.vtkFiltersVerdict when compiling the REN...2021-03-24T08:49:40-04:00Jean M. Favrev5.9-RC2 No module named 'vtkmodules.vtkFiltersVerdict when compiling the RENDERING edition```
from vtk.numpy_interface import algorithms as algs
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/scratch/e1000/jfavre/ParaView5.9/lib64/python3.8/site-packages/vtkmodules/numpy_interface/algorithms...```
from vtk.numpy_interface import algorithms as algs
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/scratch/e1000/jfavre/ParaView5.9/lib64/python3.8/site-packages/vtkmodules/numpy_interface/algorithms.py", line 20, in <module>
from . import internal_algorithms as algs
File "/scratch/e1000/jfavre/ParaView5.9/lib64/python3.8/site-packages/vtkmodules/numpy_interface/internal_algorithms.py", line 8, in <module>
from vtkmodules.vtkFiltersVerdict import vtkCellSizeFilter, vtkCellQuality, vtkMatrixMathFilter
ModuleNotFoundError: No module named 'vtkmodules.vtkFiltersVerdict'
```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.com