ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-08-24T21:50:10-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/20778PlotOverLine in PVSM fails2021-08-24T21:50:10-04:00Ethan StamPlotOverLine in PVSM fails@utkarsh.ayachit @cory.quammen
I can't reload a `pvsm` state that has `PlotOverLine`. Interestingly, saving the state as a python state is fine. In the filter, I am using the `Sample at Cell Boundaries` option. When reloading the state...@utkarsh.ayachit @cory.quammen
I can't reload a `pvsm` state that has `PlotOverLine`. Interestingly, saving the state as a python state is fine. In the filter, I am using the `Sample at Cell Boundaries` option. When reloading the state, I get the error repeatedly:
```
ERROR: In /opt/glr/paraview/paraview-ci/source-paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 753
vtkPVCompositeDataPipeline (0x6000003f5500): Algorithm vtkPProbeFilter(0x7f986ecab0b0) returned failure for request: vtkInformation (0x60000223ae80)
Debug: Off
Modified Time: 1422074
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
```
Steps to reproduce:
- Download latest nightly binary for macos
- File -> Open -> Examples/can.ex2
- Filters -> PlotOverLine
- In PlotOverLine properties:
* Change sampling pattern to `Sample at Cell Boundaries` -> Apply
- File -> Save State (as `.pvsm`)
- Reset ParaView
- File -> Load State -> Use File Names From State -> OK5.10 (Fall 2021)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20777`Hover Cells On` broken with can.ex2 example dataset2021-09-21T16:39:45-04:00Ethan Stam`Hover Cells On` broken with can.ex2 example dataset@utkarsh.ayachit @cory.quammen
`Hover Cells On` does not work with the can.ex2 example dataset, may fail with other `vtkPartitionedDataSetCollection`. I get the error:
```
ERROR: In /opt/glr/paraview/paraview-ci/source-paraview/VTK/Co...@utkarsh.ayachit @cory.quammen
`Hover Cells On` does not work with the can.ex2 example dataset, may fail with other `vtkPartitionedDataSetCollection`. I get the error:
```
ERROR: In /opt/glr/paraview/paraview-ci/source-paraview/VTK/Common/DataModel/vtkMultiBlockDataSet.cxx, line 78
vtkMultiBlockDataSet (0x60000c0dc000): vtkPartitionedDataSetCollection cannot be added as a block.
```
Steps to reproduce:
- File -> Open -> Examples/can.ex2 -> Apply
- Toggle `Hover Cells On` for RenderView1
- Move Cursor over the dataset
I hit this on MacOS with a nightly binary:
```
Client Information:
Version: 5.9.1-1209-ge0ef3e46c9
VTK Version:
Qt Version: 5.15.2
vtkIdType size: 64bits
Embedded Python: On
Python Library Path: /Users/stam/Applications/ParaView-5.9.1-1209-ge0ef3e46c9.app/Contents/Libraries/lib/python3.9
Python Library Version: 3.9.5 (default, Jun 6 2021, 01:02:46) [Clang 12.0.0 (clang-1200.0.32.29)]
Python Numpy Support: On
Python Numpy Path: /Users/stam/Applications/ParaView-5.9.1-1209-ge0ef3e46c9.app/Contents/Python/numpy
Python Numpy Version: 1.20.3
Python Matplotlib Support: On
Python Matplotlib Path: /Users/stam/Applications/ParaView-5.9.1-1209-ge0ef3e46c9.app/Contents/Python/matplotlib
Python Matplotlib Version: 3.2.1
Python Testing: Off
MPI Enabled: On
ParaView Build ID: superbuild b69f8df2e47647ef4e91fa17adce63292b9c1374 (master)
Disable Registry: Off
Test Directory:
Data Directory:
OpenGL Vendor: NVIDIA Corporation
OpenGL Version: 4.1 NVIDIA-12.0.24 355.11.10.50.10.103
OpenGL Renderer: NVIDIA GeForce GT 750M OpenGL Engine
Connection Information:
Remote Connection: No
```5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20775IOSS: CGNS incorrect side blocks2021-06-22T17:44:49-04:00Utkarsh AyachitIOSS: CGNS incorrect side blocks* open sparc-volume.cgns.36.* using IOSS reader
* uncheck all blocks and check **wall** under Sets. Apply
* You'll get a shell with gaps. The gaps are incorrect.* open sparc-volume.cgns.36.* using IOSS reader
* uncheck all blocks and check **wall** under Sets. Apply
* You'll get a shell with gaps. The gaps are incorrect.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20773Make it possible to cancel export of extracts2021-09-08T21:53:13-04:00Cory Quammencory.quammen@kitware.comMake it possible to cancel export of extractsJust as it is possible to abort saving of an animation, make it possible to abort the export of extracts. Also, provide a progress bar to show the state of the extract export.Just as it is possible to abort saving of an animation, make it possible to abort the export of extracts. Also, provide a progress bar to show the state of the extract export.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20769Plot Over Line can fail in parallel2021-08-24T17:26:34-04:00Cory Quammencory.quammen@kitware.comPlot Over Line can fail in parallelThe rework of **Plot Over Line** !4795 can fail when run in parallel. Steps to reproduce:
* Start ParaView, connect to remote server running on 2 ranks (`mpiexec -np 2 pvserver`)
* Add **Unstructured Cell Types** source. Change **Block ...The rework of **Plot Over Line** !4795 can fail when run in parallel. Steps to reproduce:
* Start ParaView, connect to remote server running on 2 ranks (`mpiexec -np 2 pvserver`)
* Add **Unstructured Cell Types** source. Change **Block Dimensions** property to [11, 10, 10]
* Add **Plot Over Line** filter. Change **Sampling Pattern** to "Sample At Cell Boundaries". Click Apply.
* You will get the following warning message:
```
ERROR: In /Users/cory.local/src/paraview/VTK/Filters/Parallel/vtkPProbeFilter.cxx, line 108
vtkPProbeFilter (0x612000b4d240): vtkPProbeFilter assumes the whole geometry dataset (which determines positions to probe) is available on all nodes, however nodes 0 is different than node 1
```
Looking at the line samples in the Render View, there are only two points from rank 1 and both are marked as not valid (vtkValidPointMask == 0).5.10 (Fall 2021)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20763Add assemblies to the Multiblock inspector2023-08-28T15:14:53-04:00W. Alan ScottAdd assemblies to the Multiblock inspectorPlease add assemblies to the multiblock inspector.
OK to push to 5.11. If so, please mark as required.Please add assemblies to the multiblock inspector.
OK to push to 5.11. If so, please mark as required.5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/20761IOSS reader fails with different multifile datasets with same name2021-06-22T17:04:03-04:00W. Alan ScottIOSS reader fails with different multifile datasets with same nameThe Exodus reader will read two datasets, with the same name, but different file counts. For instance, using can.exo, it would properly read can.e.4.[0-3] if can.e.2.[0-1] were in the same directory. This can easily happen as an analys...The Exodus reader will read two datasets, with the same name, but different file counts. For instance, using can.exo, it would properly read can.e.4.[0-3] if can.e.2.[0-1] were in the same directory. This can easily happen as an analyst is ramping up the size of a simulation.
The IOSS reader fails under these conditions.
Super easy way to replicate.
* Copy g1s1.* into a sandbox directory.
* cp g1s1-10fps.e.16.00 g1s1-10fps.e.2.0
* cp g1s1-10fps.e.16.01 g1s1-10fps.e.2.1
* master, Linux, builtin server.
* Open g1s1-10fps.e.16. It will fail as follows:
```
ERROR: In /snip/5.10.0-alpha3/ParaView5/VTK/IO/Ioss/vtkIossReader.cxx, line 611
vtkIossReader (0x5422ce0): Filenames specified use inconsistent naming schemes. 'g1s1-10fps.e.2.0' has incorrect processor-count (2), '16' was expected.
ERROR: In /snip/5.10.0-alpha3/ParaView5/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 753
vtkPVCompositeDataPipeline (0x5663550): Algorithm vtkIossReader(0x5422ce0) returned failure for request: vtkInformation (0x5210d30)
Debug: Off
Modified Time: 385946
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
```5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20757IOSS reader and Assemblies2021-06-22T17:47:31-04:00W. Alan ScottIOSS reader and AssembliesCurrently, on master, the IOSS reader and ParaView deals with assembles in the Extract Block filter and Multi-block inspector (work still in progress). The reader also shows assemblies in the Information tab.
The IOSS reader currentlyd...Currently, on master, the IOSS reader and ParaView deals with assembles in the Extract Block filter and Multi-block inspector (work still in progress). The reader also shows assemblies in the Information tab.
The IOSS reader currentlydoes not allow a user to selectively load assembles within the IOSS reader's Properties tab. This needs to be implemented, as assemblies will potentially be used for large data, and will be one of the primary mechanisms to load subsets of datasets.
@utkarsh.ayachit5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20747Ensight reader does not support undefined and partial variables2021-07-09T11:49:37-04:00Boonthanome NouanesengsyEnsight reader does not support undefined and partial variablesThe Ensight reader currently does not support undefined or partial variables.
Here is a synthetic Ensight dataset that contains both undefined and partial variables:
ascii version: [grid_ascii.tar.gz](/uploads/46c6da14af2cca5d2d3d08f...The Ensight reader currently does not support undefined or partial variables.
Here is a synthetic Ensight dataset that contains both undefined and partial variables:
ascii version: [grid_ascii.tar.gz](/uploads/46c6da14af2cca5d2d3d08fe30611325/grid_ascii.tar.gz) \
binary version: [grid_bin.tar.gz](/uploads/50bc3f30ba9e23e0d8372fd0cc676bea/grid_bin.tar.gz)
@patchett2002 @utkarsh.ayachit @cory.quammen5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20737Cell Size filter is broken for Wedges2021-06-22T18:07:29-04:00W. Alan ScottCell Size filter is broken for WedgesI have a dataset that is failing using the Integrate Variables filter. We have a trivial test case, with known expected values. Here is how to replicate it, then an analysis.
* Master or 5.9.1 or 5.9.0, Linux or Mac, builtin server.
*...I have a dataset that is failing using the Integrate Variables filter. We have a trivial test case, with known expected values. Here is how to replicate it, then an analysis.
* Master or 5.9.1 or 5.9.0, Linux or Mac, builtin server.
* Open mesh_mb.g. Apply.
Note that this mesh (cuboid) is 1X2X3 in size. There are 4 blocks within this cuboid.
* Calculator. Formula is 1. Apply.
* Integrate Variables filter. Apply.
In the spreadsheet, note that Result integrates to 2. Switch to Cell. Volume is 2. This is a bug.
Note that if you do the same thing with mesh_sb.g, the integrated Result and volume is 6. This is correct.
* Click on the calculator in the pipeline browser.
* Cell Size filter. Apply.
* Change spreadsheet to Cell Size filter (if it isn't already there). Cells. Now, click on volume column. Sort smallest to largest.
The volumes for Wedges will be negative!
That is at least the start of the issue. Note that when corrected, if the integrated volumes aren't 6, we still have bugs.
I will pass the dataset to Utkarsh and Cory.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20721Release Paraview 5.9.12021-05-28T17:14:31-04:00Vicente Boleavicente.bolea@kitware.comRelease Paraview 5.9.1# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.9.1.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.9.1.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.9.1.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.9.1.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.9.1.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Assemble release notes into `Documentation/release/ParaView-5.9.1`.
- [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.1
echo 5.9.1 > version.txt
git commit -m 'Update version number to 5.9.1' version.txt
git tag -a -m 'ParaView 5.9.1' v5.9.1 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.1:release`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.9.1`)
- 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.1
```
- 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.1" CACHE STRING "Force version to 5.9.1" 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.1
- [x] ARG SUPERBUILD_TAG=v5.9.1
- [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.1"
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.1' v5.9.1 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.9.1: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.1.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.9.1.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
- 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.1`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.9.1`.
# 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.1.
- [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 update of version number in "Download Latest Release" text on www.paraview.org
- [x] Move unclosed issues to next release milestone in GitLab
# After a week of updating the Spack Package
- [x] Move RC binaries to the RCs folder in www.paraview.org/files/v5.9
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit
/cc @charles.gueunetVicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20720Spack build of paraview master fails at link step for catalyst_replay2021-05-26T13:03:00-04:00Ethan StamSpack build of paraview master fails at link step for catalyst_replay@utkarsh.ayachit @cory.quammen
Last night our spack builds of `paraview@master` failed at the link step for `catalyst_replay`. The paraview spec was `paraview@master%gcc@7.4.0~advanced_debug~cuda~examples+hdf5~ipo+kits+mpi+opengl2+osme...@utkarsh.ayachit @cory.quammen
Last night our spack builds of `paraview@master` failed at the link step for `catalyst_replay`. The paraview spec was `paraview@master%gcc@7.4.0~advanced_debug~cuda~examples+hdf5~ipo+kits+mpi+opengl2+osmesa+plugins~python+python3~qt+shared build_type=RelWithDebInfo cuda_arch=native arch=linux-rhel7-broadwell`
Output of the error:
```console
[100%] Linking CXX executable ../../../../../bin/catalyst_replay
cd /tmp/stam/spack-stage/spack-stage-paraview-master-ffgrcmqjeawokr4qcx6t2l35ojdz5idx/spack-build-ffgrcmq/ThirdParty/catalyst/vtkcatalyst/catalyst/replay && /yellow/usr/projects/paraview/fusion/nightly-snow/spack/spack/opt/spack/linux-rhel7-broadwell/gcc-7.4.0/cmake-3.15.3-2hqjqbsmkqxnz5qqb5dgtdbiflbn5ot2/bin/cmake -E cmake_link_script CMakeFiles/catalyst_replay.dir/link.txt --verbose=1
/yellow/usr/projects/paraview/fusion/nightly-snow/spack/spack/lib/spack/env/gcc/g++ -O2 -g -DNDEBUG -Wl,-lc -Wl,-lc CMakeFiles/catalyst_replay.dir/catalyst_replay.cpp.o -o ../../../../../bin/catalyst_replay -Wl,-rpath,/tmp/stam/spack-stage/spack-stage-paraview-master-ffgrcmqjeawokr4qcx6t2l35ojdz5idx/spack-build-ffgrcmq/lib64:/usr/projects/hpcsoft/toss3/common/x86_64/anaconda/5.0.1-python-3.6/lib ../../../../../lib64/libcatalyst.so.2 -Wl,-rpath-link,/usr/projects/hpcsoft/toss3/common/x86_64/anaconda/5.0.1-python-3.6/lib
/yellow/usr/projects/paraview/fusion/nightly-snow/spack/spack/opt/spack/linux-rhel7-broadwell/gcc-7.4.0/netcdf-c-4.8.0-tdmo2wgwleqmtsqc3dk2amoz5dhsm6px/lib/libnetcdf.so.19: undefined reference to `H5Pset_all_coll_metadata_ops'
/yellow/usr/projects/paraview/fusion/nightly-snow/spack/spack/opt/spack/linux-rhel7-broadwell/gcc-7.4.0/netcdf-c-4.8.0-tdmo2wgwleqmtsqc3dk2amoz5dhsm6px/lib/libnetcdf.so.19: undefined reference to `H5Pset_dxpl_mpio'
/yellow/usr/projects/paraview/fusion/nightly-snow/spack/spack/opt/spack/linux-rhel7-broadwell/gcc-7.4.0/netcdf-c-4.8.0-tdmo2wgwleqmtsqc3dk2amoz5dhsm6px/lib/libnetcdf.so.19: undefined reference to `H5Pset_coll_metadata_write'
/yellow/usr/projects/paraview/fusion/nightly-snow/spack/spack/opt/spack/linux-rhel7-broadwell/gcc-7.4.0/netcdf-c-4.8.0-tdmo2wgwleqmtsqc3dk2amoz5dhsm6px/lib/libnetcdf.so.19: undefined reference to `H5Pset_fapl_mpio'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/catalyst_replay] Error 1
```5.10 (Fall 2021)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/20698Reset Camera Closest and Zoom to Box and Link Camera broken2021-12-20T20:47:32-05:00W. Alan ScottReset Camera Closest and Zoom to Box and Link Camera brokenReset Camera Closest Zoom to Box and Link Camera are broken. Here is how to replicate:
* Master, Linux, builtin server.
* Sources/ Sphere. Apply.
* Split Views horizontally.
* Turn visibility on for the new view.
* Link cameras.
* Res...Reset Camera Closest Zoom to Box and Link Camera are broken. Here is how to replicate:
* Master, Linux, builtin server.
* Sources/ Sphere. Apply.
* Split Views horizontally.
* Turn visibility on for the new view.
* Link cameras.
* Reset.
* Reset Camera Closest.
Only one of the views zooms in. Cameras are linked, thus,they should zoom in together.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/20693Reset Camera Closest is broken2021-12-27T06:04:47-05:00W. Alan ScottReset Camera Closest is brokenZoom close to data is way broken. Here is how to replicate it:
* Master, Linux, builtin server.
* Make ParaView's renderview window about twice as wide as it is tall. In File/ Save Screenshot, I have 1842X897.
* Sources/ Cylinder. App...Zoom close to data is way broken. Here is how to replicate it:
* Master, Linux, builtin server.
* Make ParaView's renderview window about twice as wide as it is tall. In File/ Save Screenshot, I have 1842X897.
* Sources/ Cylinder. Apply.
* Reset. +Y.
* Adjust Camera. Elevation = 35. Azimuth = 35.
* Reset Camera Closest.
![Screen_Shot_2021-05-04_at_4.53.13_PM](/uploads/7bfc9c015ebcebccc2441e2c428ef432/Screen_Shot_2021-05-04_at_4.53.13_PM.png)5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/20688Loading a multiblock with symmetric mode creates an error2021-05-10T13:54:46-04:00Boonthanome NouanesengsyLoading a multiblock with symmetric mode creates an errorI have a python script that loads a multiblock, applies the Integrate Variables filter, then writes out the resulting data in a csv file. When running the script in symmetric mode, the following error pops up:
```
( 0.591s) [pvbatch ...I have a python script that loads a multiblock, applies the Integrate Variables filter, then writes out the resulting data in a csv file. When running the script in symmetric mode, the following error pops up:
```
( 0.591s) [pvbatch ] vtkPVSessionCore.cxx:372 ERR| vtkPVSessionCore (0x7fb82709c1d0): Object type: vtkXMLMultiBlockDataReader, could not find requested method: "SetActiveTimeDataArrayName"
or the method was called with incorrect arguments.
```
There are more error messages after that. Even though these error messages appear, the csv file does show up, so it doesn't actually seem to affect anything. But these error messages should be looked into.
If I run without the symmetric flag, no error messages appear.
Test dataset: [symmetric.tar.gz](/uploads/ec25b3454d51271e3a1a7f9b4dd1ae56/symmetric.tar.gz)
To reproduce:
- untar the test dataset. there will be a python script and vtm file there.
- mpirun -np 1 pvbatch --symmetric integrate.py
- lots of error messages pop up
This is with the latest master branch of Paraview. Be sure to use the latest master when reproducing, as the script does not work with 5.9.0.
@patchett2002 @cory.quammen5.10 (Fall 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20677Release ParaView 5.9.1-RC2 (source and tags only)2021-04-29T13:05:29-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.9.1-RC2 (source and tags only)# 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
...# 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.1-RC2
echo 5.9.1-RC2 > version.txt
git commit -m 'Update version number to 5.9.1-RC2' version.txt
git tag -a -m 'ParaView 5.9.1-RC2' v5.9.1-RC2 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-v5.9.1-RC2` branch to be the new `release` branch)
- [x] `git push origin update-to-v5.9.1-RC2:release`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.9.1-RC2`)
- 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.1-RC2
```
- Update `CMakeLists.txt`
- [x] Update PARAVIEW_VERSION_DEFAULT to the release version (without RC*)
- 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.1-RC2
- [x] ARG SUPERBUILD_TAG=v5.9.1-RC2
- [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.1-RC2"
git gitlab-push
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release` to description)
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.9.1-RC2' v5.9.1-RC2 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.9.1-RC2:release`
# Update web site
- [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.1-RC2`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.9.1-RC2`.
# 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.ayachit
/cc @charles.gueunet5.9.1 (Spring 2021)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20673Error remote server with IOSS reader2021-08-24T17:38:58-04:00W. Alan ScottError remote server with IOSS readerWe have an error print when running the IOSS reader in parallel. Here is how to replicate:
* master, Linux, remote server.
* Open can.exo. Apply.
We see millions of these. They appear to be coming from the server side.
( 67.626s) ...We have an error print when running the IOSS reader in parallel. Here is how to replicate:
* master, Linux, remote server.
* Open can.exo. Apply.
We see millions of these. They appear to be coming from the server side.
( 67.626s) [paraview ] vtkOutputWindow.cxx:76 ERR| ERROR: In /snip/VTK/Common/DataModel/vtkDataObjectTree.cxx, line 381
vtkMultiBlockDataSet (0xb53a600): Structure does not match. You must use CopyStructure before calling this method.
( 67.626s) [paraview ] vtkOutputWindow.cxx:76 ERR| ERROR: In /snip/VTK/Common/DataModel/vtkDataObjectTree.cxx, line 381
vtkMultiBlockDataSet (0xb53c660): Structure does not match. You must use CopyStructure before calling this method.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20662Release Paraview 5.9.1-RC12021-04-28T12:30:30-04:00Vicente Boleavicente.bolea@kitware.comRelease Paraview 5.9.1-RC1# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.9.1.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.9.1.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.9.1.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.9.1.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.9.1.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Assemble release notes into `Documentation/release/ParaView-5.9.1`.
- [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.1-RC1
echo 5.9.1-RC1 > version.txt
git commit -m 'Update version number to 5.9.1-RC1' version.txt
git tag -a -m 'ParaView 5.9.1-RC1' v5.9.1-RC1 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@-RC1` branch to be the new `release` branch)
- [x] `git push origin update-to-v5.9.1-RC1:release`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.9.1-RC1`)
- 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.1-RC1
```
- 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.1-RC1" CACHE STRING "Force version to 5.9.1-RC1" 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.1-RC1
- [x] ARG SUPERBUILD_TAG=v5.9.1-RC1
- [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.1-RC1"
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.1-RC1' v5.9.1-RC1 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.9.1-RC1: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.1-RC1.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.9.1-RC1.app/`
# Validating binaries
For each binary, open the Python shell and run the following:
```python
import numpy
s = Show(Sphere())
ColorBy(s, ('POINTS', 'Normals', 'X'))
Show(Text(Text="$A^2$"))
```
Check that
- Getting started guide opens
- 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.1-RC1`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.9.1-RC1`.
# 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.ayachit
/cc @charles.guenuetVicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20656IOSS: exodus block ids are not produced in the output dataset2021-06-22T19:06:26-04:00Utkarsh AyachitIOSS: exodus block ids are not produced in the output datasetExodus block ids are not produced in the output dataset. Let's add those as "objectids" (or similar)Exodus block ids are not produced in the output dataset. Let's add those as "objectids" (or similar)5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20654IOSS: errors when local rendering2021-08-24T17:48:16-04:00Utkarsh AyachitIOSS: errors when local rendering* pvserver (2 ranks), ensure remote rendering is not being used by setting remote render threshold to max
* open can.ex2 with IOSS reader, apply
you'll get following errors:
```
( 61.191s) [pvserver.0 ] vtkDataObjectTree.cxx:380...* pvserver (2 ranks), ensure remote rendering is not being used by setting remote render threshold to max
* open can.ex2 with IOSS reader, apply
you'll get following errors:
```
( 61.191s) [pvserver.0 ] vtkDataObjectTree.cxx:380 ERR| vtkMultiBlockDataSet (0x557c13088d60): Structure does not match. You must use CopyStructure before calling this method.
( 61.192s) [pvserver.0 ] vtkDataObjectTree.cxx:380 ERR| vtkMultiBlockDataSet (0x557c13088d60): Structure does not match. You must use CopyStructure before calling this method.
( 61.193s) [pvserver.0 ] vtkDataObjectTree.cxx:380 ERR| vtkMultiBlockDataSet (0x557c13088d60): Structure does not match. You must use CopyStructure before calling this method.
( 61.193s) [pvserver.0 ] vtkDataObjectTree.cxx:380 ERR| vtkMultiBlockDataSet (0x557c13088d60): Structure does not match. You must use CopyStructure before calling this method.
( 96.710s) [pvserver.0 ] vtkDataObjectTree.cxx:380 ERR| vtkMultiBlockDataSet (0x557c0ef2dae0): Structure does not match. You must use CopyStructure before calling this method.
( 96.711s) [pvserver.0 ] vtkDataObjectTree.cxx:380 ERR| vtkMultiBlockDataSet (0x557c0ef2dae0): Structure does not match. You must use CopyStructure before calling this method.
( 96.711s) [pvserver.0 ] vtkDataObjectTree.cxx:380 ERR| vtkMultiBlockDataSet (0x557c0ef2dae0): Structure does not match. You must use CopyStructure before calling this method.
( 96.712s) [pvserver.0 ] vtkDataObjectTree.cxx:380 ERR| vtkMultiBlockDataSet (0x557c0ef2dae0): Structure does not match. You must use CopyStructure before calling this method.
```5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachit