ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-03-29T17:05:39-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/21799Release ParaView 5.11.1-RC12023-03-29T17:05:39-04:00Ryan Krattigerryan.krattiger@kitware.comRelease ParaView 5.11.1-RC1<!--
This template is for tracking a release of ParaView. Please replace the
following strings with the associated values:
- `5.11.1` - replace with base version, e.g., 5.7.0
- `-RC1` - for release candidates, replace with "-RC?". F...<!--
This template is for tracking a release of ParaView. Please replace the
following strings with the associated values:
- `5.11.1` - replace with base version, e.g., 5.7.0
- `-RC1` - for release candidates, replace with "-RC?". For final, replace with "".
- `5` - replace with major version number
- `11` - replace with minor version number
- `1` - replace with patch version number
- `release`: The branch to create the release on (for `x.y.0-RC1`,
`master`, otherwise `release`)
- `e39c9fe7beebc506fc3640b9ec579ba61dba65db`: The ParaView commit where the release should be started
Please remove this comment.
-->
# Preparatory steps
- Update ParaView guides
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.11.1.pdf
- [x] Upload to www.paraview.org/files/v5.11
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.11.1.pdf
- [x] Upload to www.paraview.org/files/v5.11
- macOS signing machine
- [x] Check that the macOS signing machine is reachable. If not, request it to be switched on.
# Update ParaView
- Update the local copy of `release`.
- If `1-RC1` is `0-RC1`, update `master`
- Otherwise, update `release`
```
git fetch origin
git checkout release
git merge --ff-only origin/release # if this fails, there are local commits that need to be removed
git submodule update --recursive --init
```
- If `release` is not `master`, ensure merge requests which should be
in the release have been merged. The [`backport-mrs.py`][backport-mrs]
script can be used to find and ensure that merge requests assigned to the
associated milestone are available on the `release` branch.
- Integrate changes.
- Make a commit for each of these `release`-only changes on a single topic
(suggested branch name: `update-to-v5.11.1`):
- Assemble release notes into `Documentation/release/ParaView-5.11.1.md`.
- [x] Update `version.txt` and tag the commit (tag this commit below)
```
git checkout -b update-to-v5.11.1-RC1 e39c9fe7beebc506fc3640b9ec579ba61dba65db
echo 5.11.1-RC1 > version.txt
git commit -m 'Update version number to 5.11.1-RC1' version.txt
```
- [ ] Update VTK's `paraview/release` branch. The
[`release-mr`][release-mr] script should be used to do this. Pass
`-c .kitware-release-paraview.json` to use the appropriate
configuration file.
- [ ] Merge the VTK `paraview/release` update MR
- [ ] Update kwrobot with the new `paraview/release` branch rules (@ben.boeckel)
- [ ] `.gitmodules` to track the `paraview/release` branch of VTK
- [ ] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups
- Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- [x] Pull the script for each release; it may have been updated since it
was last used
- [x] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m e39c9fe7beebc506fc3640b9ec579ba61dba65db`
- [x] The script outputs the information it will be using to create the
merge request. Please verify that it is all correct before creating
the merge request. See usage at the top of the script to provide
information that is either missing or incorrect (e.g., if its data
extraction heuristics fail).
- [x] Get positive review
- [x] `Do: merge`
- [x] Create tag: `git tag -a -m '5.11.1-RC1' v5.11.1-RC1 commit-that-updated-version.txt`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.11.1-RC1`)
- Upload tarballs to `paraview.org`
- [x] Setup your `~/.ssh/config` and add the web host (@vbolea).
- [x] `rsync -rptv $tarballs web:ParaView_Release/v5.11/`
- Software process updates (these can all be done independently)
- [ ] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [ ] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [ ] Add (or update if `release` is `release`) version selection entry
in paraview-superbuild
[backport-mrs]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/backport-mrs.py
[release-mr]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/release-mr.py
[cdash-update-groups]: https://gitlab.kitware.com/utils/cdash-utils/-/blob/master/cdash-update-groups.py
# Update ParaView-Superbuild
- [x] Update release branch for **paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Create new branch `git checkout -b update-to-v5.11.1-RC1 release`
- Integrate changes.
- Update versions
- [x] Guide selections in `versions.cmake` and ensure that the paraview
http URL source is the _DEFAULT_ source.
- [x] `paraview_SOURCE_SELECTION` version in `README.md`
- [x] `PARAVIEW_VERSION_DEFAULT` in CMakeLists.txt
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.11.1-RC1
- [x] ARG SUPERBUILD_TAG=v5.11.1-RC1
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.11
- [x] Commit changes
- [x] `git add README.md versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile`
- [x] `git commit -m "Update the default version to 5.11.1-RC1"`
- Make a commit for each of these `release`-only changes
- [x] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups (if `release` is `master`)
- Create a commit which will be tagged:
- [x] `git commit --allow-empty -m "paraview: add release 5.11.1"`
- [x] Create tag: `git tag -a -m 'ParaView superbuild 5.11.1-RC1' v5.11.1-RC1 HEAD`
- Force `5.11.1-RC1` in CMakeLists.txt
- [x] Append to the top of CMakeLists.txt (After project...) The following
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.11.1-RC1" CACHE STRING "Force version to 5.11.1-RC1" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- [x] Create fixup commit with the above changes `git commit -a --fixup=@`. The fixup commit will prevent merging of the temporary code above; it will be removed in a future step.
- [x] Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- [x] Pull the script for each release; it may have been updated since it
was last used
- [x] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m e39c9fe7beebc506fc3640b9ec579ba61dba65db`
- [x] Build binaries
- [x] Build binaries (start all pipelines)
- [x] Download the binaries that have been generated from the Pipeline
build products. They will be deleted within 24 hours.
- [x] Remove fixup commit: `git reset --hard @^`
- [x] Get positive review
- [x] Force push `git push -f gitlab`
- [x] `Do: merge`
- Software process updates (these can all be done independently)
- [ ] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [ ] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [ ] Add (or update if `release` is `release`) version selection entry
in paraview-superbuild
# Sign Windows binaries
- [x] Request Windows binary signings (only .exe archives) on the Package
Signing repo. Example request [here][win-sign-example].
# Sign macOS binaries
- [x] Upload to signing server, run script, download resulting .pkg and .dmg files
- [ ] Install from .pkg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.11.1-RC1.app/`
- [ ] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.11.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
- Help lists Readers, Writers, Filters, and Sources properly
- Examples load and match thumbnails in dialog
- Python. Open the Python shell and run
- Plugins are present and load properly
- OSPRay raycasting and pathtracing runs ("Enable Ray Tracing" property in View panel)
- OptiX pathtracing runs (not macOS)
- IndeX runs (load pvNVIDIAIndeX plugin, add a Wavelet dataset, change representaiton to NVIDIA IndeX)
Binary checklist
- [x] macOS arm64
- [x] macOS x86\_64
- [x] Linux
- [x] Linux osmesa
- [x] Linux EGL
- [x] Windows MPI (.exe)
- [x] Windows MPI (.zip)
- [x] Windows no-MPI (.exe)
- [x] Windows no-MPI (.zip)
# Upload binaries
- [x] Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.11/`)
- [ ] Ask @jonthan.volks (Kitware comm team) to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website from within the directory corresponding to www.paraview.org/files/
```
buildListing.sh
updateMD5sum.sh v5.11
```
- [ ] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.11.1-RC1`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.11.1-RC1`.
# Spack
- [ ] Update Spack package: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py
<!--
If making a non-RC release:
# Update documentation
- [ ] Submit a Merge Request for release that updates the version to 5.11.1 in https://gitlab.kitware.com/paraview/paraview-docs/-/blob/master/doc/source/conf.py` for `paraview-docs`
- [ ] Upload versioned documentation to `https://github.com/kitware/paraview-docs` (see `https://github.com/Kitware/paraview-docs/blob/master/README.md`)
- [ ] Tag the HEAD of release in [ParaView docs](https://gitlab.kitware.com/paraview/paraview-docs/-/tags) with v5.11.1.
- [ ] Activate the tag on [readthedocs](https://readthedocs.org/projects/paraview/versions/) and build it [here](https://readthedocs.org/projects/paraview/)
- [ ] Go to readthedocs.org and activate
- [ ] Write and publish blog post with release notes.
- [ ] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
-->
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [ ] Request DoD vulnerability scan
- [ ] Request an XRInterface plugin validation using [TESTING.md](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Plugins/XRInterface/TESTING.md) protocol from KEU
<!--
If making a non-RC release:
- [ ] Request from comm@kitware.com an update of version number in "Download Latest Release" text on www.paraview.org
- [ ] Move unclosed issues in GitLab to the next release milestone in GitLab
-->
/cc @ben.boeckel
/cc @cory.quammen
/cc @charles.gueunet
/cc @mwestphal
[win-sign-example]: https://kwgitlab.kitware.com/software-process/package-signing/-/issues/125.11.1 (Winter 2023)Ryan Krattigerryan.krattiger@kitware.comRyan Krattigerryan.krattiger@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21722Catalyst: two data pipes with two different scripts fails in coprocessing.py2024-03-27T10:37:25-04:00Jeff MauldinCatalyst: two data pipes with two different scripts fails in coprocessing.pyWhen using Catalyst, users will sometimes want to create different datasets to be sent to different catalyst python scripts. For example, in SPARC users might send surface/wall data to one script and volume/airflow data to a different sc...When using Catalyst, users will sometimes want to create different datasets to be sent to different catalyst python scripts. For example, in SPARC users might send surface/wall data to one script and volume/airflow data to a different script.
In ParaView 5.10 and 5.11.0 this capability fails. It worked in 5.9. The problem is in coprocessort.py. I am attaching my altered coprocessor.py which works. You can diff with the 5.11.0 Wrapping/Python/paraview/coprocessing.py to see the changes I had to make to get it to work. I don't insist on exactly these changes, but our ioss catalyst test suite (that Ben Boeckle can run on SNL HPCs like vortex and eclipse) will need to pass the related two pipe/two script tests.[coprocessing.py](/uploads/c9acb4266c3c5bf9d08ccf1edc931abc/coprocessing.py)
I also undid a change which disallowed multiple data pipes to have the same name. In our sierra catalyst implementation we have been using the same name ("input") for all incoming data pipes and it has worked fine. I don't absolutely have to have the capability to give multiple pipes the same name, but it would be nice to be warned formally about the change.5.11.1 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21683object_id variable not present after performing clip filter2022-12-13T11:46:03-05:00Phil Smithobject_id variable not present after performing clip filterTested on Mac ParaView v5.11.0 nightly. To reproduce:
Open Can.ex0 -- Apply
Filters -> clip Apply
object_id variable is no longer present
This works in 5.10.1 with the clip filter. The object_id variable is still present when a slice f...Tested on Mac ParaView v5.11.0 nightly. To reproduce:
Open Can.ex0 -- Apply
Filters -> clip Apply
object_id variable is no longer present
This works in 5.10.1 with the clip filter. The object_id variable is still present when a slice filter is applied when using v5.11.0 nightly, so it looks like this issue is unique to the clip filter. The other odd thing I noticed is that if you select the crinkle clip check box using 5.11.0, the object_id variable is present after you apply the changes.5.11.1 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21781Multiblock Inspector Can't Set an Opacity Value, anything less than 1 causes ...2023-03-01T15:59:42-05:00Ethan StamMultiblock Inspector Can't Set an Opacity Value, anything less than 1 causes geometry to disappear@cory.quammen @boonth @patchett2002
I am using ParaView 5.11.0 on MacOS downloaded from paraview.org
When using the opacity controls in the multiblock inspector, I am trying to set the opacity to less than 1, but anything less than 1 ...@cory.quammen @boonth @patchett2002
I am using ParaView 5.11.0 on MacOS downloaded from paraview.org
When using the opacity controls in the multiblock inspector, I am trying to set the opacity to less than 1, but anything less than 1 causes the block to disappear.
Steps to reproduce:
1. Open bake.e dataset
2. View -> Multiblock inspector
3. Hide all blocks except for `block_1`
4. Double click its opacity and set it to 1. The block shows correctly
5. Double click its opacity and set it to 0.99. The block disappears5.11.1 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21682TOC Links on ParaView release notes do not work2022-12-01T16:22:01-05:00Phil SmithTOC Links on ParaView release notes do not workTested with ParaView 5.11.0 Nightly. To reproduce the issue:
Select Help->Release Notes from ParaView -- Works great
Click on New Features, Rendering Enhancements, etc and nothing happens
These links should bring you to the specific head...Tested with ParaView 5.11.0 Nightly. To reproduce the issue:
Select Help->Release Notes from ParaView -- Works great
Click on New Features, Rendering Enhancements, etc and nothing happens
These links should bring you to the specific heading within the webpage that explains these improvements or changes.
@wascott @cory.quammen
Release Notes link is https://www.kitware.com/paraview-5-11-0-release-notes/5.11.1 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21789PythonAlgorithmExamples.py fails to load2023-02-26T20:15:47-05:00Juan Jose CasafrancaPythonAlgorithmExamples.py fails to loadThe PythonAlgorithmExamples.py examples fail to load in Paraview 5.10 and Paraview 5.11 which are the version I have tested it.
```
Failed to call `paraview.detail.pythonalgorithm.load_plugin`.
Traceback (most recent call last):
File...The PythonAlgorithmExamples.py examples fail to load in Paraview 5.10 and Paraview 5.11 which are the version I have tested it.
```
Failed to call `paraview.detail.pythonalgorithm.load_plugin`.
Traceback (most recent call last):
File "/opt/paraview/lib/python3.10/site-packages/paraview/detail/pythonalgorithm.py", line 509, in load_plugin
spec.loader.exec_module(module)
File "<frozen importlib._bootstrap_external>", line 883, in exec_module
File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
File "/home/jjcasmar/Downloads/PythonAlgorithmExamples.py", line 16, in <module>
class PythonSuperquadricSource(VTKPythonAlgorithmBase):
File "/home/jjcasmar/Downloads/PythonAlgorithmExamples.py", line 57, in PythonSuperquadricSource
def SetThetaResolution(self, x):
File "/opt/paraview/lib/python3.10/site-packages/paraview/detail/pythonalgorithm.py", line 76, in decorator
updated_attrs = update_func(original_func, attrs)
File "/opt/paraview/lib/python3.10/site-packages/paraview/detail/pythonalgorithm.py", line 144, in _update_vectorproperty_defaults
assert attrs["number_of_elements"] == _count(attrs["default_values"])
AssertionError
( 9.646s) [paraview ] vtkPVPluginLoader.cxx:532 ERR| vtkPVPluginLoader (0x56122d209ba0): /home/jjcasmar/Downloads/PythonAlgorithmExamples.py: /home/jjcasmar/Downloads/PythonAlgorithmExamples.py: invalid ELF header
```5.11.1 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21709"Enable opacity mapping for surfaces": data disappears when one or more block...2023-02-14T09:50:15-05:00Cory Quammencory.quammen@kitware.com"Enable opacity mapping for surfaces": data disappears when one or more blocks set to not visibleReproducer:
* Load can.ex2, all variables on
* Go to last time step.
* Color by ACCL
* In the Color Map Editor, check "Enable opacity mapping for surfaces"
* Set the opacity of the lowest data value something more than 0 so you can see ...Reproducer:
* Load can.ex2, all variables on
* Go to last time step.
* Color by ACCL
* In the Color Map Editor, check "Enable opacity mapping for surfaces"
* Set the opacity of the lowest data value something more than 0 so you can see the geometry better.
* Open the MultiBlock Inspector
* Uncheck the visibility of "block_1". The entire geometry disappears, not just the block you set to not visible.5.11.1 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21687Compile error in vtkWidgetRepresentation.cxx2022-12-07T06:13:11-05:00Kenneth MorelandCompile error in vtkWidgetRepresentation.cxxWhen compiling ParaView 5.11.0 with GCC 6.5.0, I get a compile error about an ambiguous overload of `std::abs`. The problem is that `std::abs` is being called with a `double` value. The compiler does not know whether to use the `long` or...When compiling ParaView 5.11.0 with GCC 6.5.0, I get a compile error about an ambiguous overload of `std::abs`. The problem is that `std::abs` is being called with a `double` value. The compiler does not know whether to use the `long` or `long long` version of the function. The error happens on line 371 of VTK/Interaction/Widgets/vtkWidgetRepresentation.cxx.
The problem appears to be introduced by https://gitlab.kitware.com/vtk/vtk/-/merge_requests/9081. I realize this is technically a VTK bug, but it is affecting the ParaView 5.11 rollout.
The full error is below.
```
[2023/20869] Building CXX object VTK/Interaction/Widgets/CMakeFiles/InteractionWidgets.dir/vtkWidgetRepresentation.cxx.o
FAILED: VTK/Interaction/Widgets/CMakeFiles/InteractionWidgets.dir/vtkWidgetRepresentation.cxx.o
/sw/andes/gcc/6.5.0/bin/g++ -DInteractionWidgets_EXPORTS -Dkiss_fft_scalar=double -DvtkRenderingCore_AUTOINIT_INCLUDE=\"/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/CMakeFiles/vtkModuleAutoInit_919f0246f6cf0fd410088f15e62762e0.h\" -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Interaction/Widgets -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Interaction/Widgets -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Common/Core -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Common/Core -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Common/ExecutionModel -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Common/ExecutionModel -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Common/DataModel -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Common/DataModel -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Common/Math -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Common/Math -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/ThirdParty/kissfft/vtkkissfft -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/ThirdParty/kissfft/vtkkissfft -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Common/Transforms -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Common/Transforms -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Filters/General -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Filters/General -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Common/Misc -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Common/Misc -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Filters/Core -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Filters/Core -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Filters/Sources -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Filters/Sources -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Rendering/Core -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Rendering/Core -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Rendering/Context2D -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Rendering/Context2D -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Common/ComputationalGeometry -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Common/ComputationalGeometry -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Common/System -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Common/System -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Filters/Hybrid -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Filters/Hybrid -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Filters/Geometry -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Filters/Geometry -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Filters/Modeling -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Filters/Modeling -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Filters/Texture -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Filters/Texture -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Imaging/Color -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Imaging/Color -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Imaging/Core -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Imaging/Core -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Imaging/General -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Imaging/General -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Imaging/Hybrid -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Imaging/Hybrid -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Interaction/Style -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Interaction/Style -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Rendering/Annotation -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Rendering/Annotation -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Rendering/FreeType -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Rendering/FreeType -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Rendering/Volume -I/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Rendering/Volume -isystem /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Utilities/KWIML -isystem /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Utilities/KWIML -isystem /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/Utilities/KWSys -isystem /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Utilities/KWSys -isystem /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/ThirdParty/kissfft -isystem /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/ThirdParty/kissfft -isystem /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/build/VTK/ThirdParty/freetype -isystem /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/ThirdParty/freetype -isystem /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/install/include/freetype2 -fPIC -std=c++11 -O3 -DNDEBUG -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -std=c++11 -MD -MT VTK/Interaction/Widgets/CMakeFiles/InteractionWidgets.dir/vtkWidgetRepresentation.cxx.o -MF VTK/Interaction/Widgets/CMakeFiles/InteractionWidgets.dir/vtkWidgetRepresentation.cxx.o.d -o VTK/Interaction/Widgets/CMakeFiles/InteractionWidgets.dir/vtkWidgetRepresentation.cxx.o -c /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Interaction/Widgets/vtkWidgetRepresentation.cxx
/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Interaction/Widgets/vtkWidgetRepresentation.cxx: In member function 'bool vtkWidgetRepresentation::NearbyEvent(int, int, double*)':
/ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Interaction/Widgets/vtkWidgetRepresentation.cxx:371:24: error: call of overloaded 'abs(double)' is ambiguous
if (abs(dFocus[0] - X) < threshold && abs(dFocus[1] - Y) < threshold)
^
In file included from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/cstdlib:75:0,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/ext/string_conversions.h:41,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/bits/basic_string.h:5429,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/string:52,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/bits/locale_classes.h:40,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/bits/ios_base.h:41,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/ios:42,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/istream:38,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/fstream:38,
from /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Common/Core/vtkIOStream.h:29,
from /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Common/Core/vtkNew.h:47,
from /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Interaction/Widgets/vtkWidgetRepresentation.h:46,
from /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Interaction/Widgets/vtkWidgetRepresentation.cxx:15:
/usr/include/stdlib.h:837:12: note: candidate: int abs(int)
extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^~~
In file included from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/ext/string_conversions.h:41:0,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/bits/basic_string.h:5429,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/string:52,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/bits/locale_classes.h:40,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/bits/ios_base.h:41,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/ios:42,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/istream:38,
from /autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/fstream:38,
from /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Common/Core/vtkIOStream.h:29,
from /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Common/Core/vtkNew.h:47,
from /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Interaction/Widgets/vtkWidgetRepresentation.h:46,
from /ccs/home/kmorel/world-shared/builds/andes-2022-12-02/paraview-v5.11.0/build/superbuild/paraview/src/VTK/Interaction/Widgets/vtkWidgetRepresentation.cxx:15:
/autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/cstdlib:180:3: note: candidate: long long int std::abs(long long int)
abs(long long __x) { return __builtin_llabs (__x); }
^~~
/autofs/nccs-svm1_sw/andes/gcc/6.5.0/include/c++/6.5.0/cstdlib:172:3: note: candidate: long int std::abs(long int)
abs(long __i) { return __builtin_labs(__i); }
^~~
```5.11.1 (Winter 2023)Kenneth MorelandKenneth Morelandhttps://gitlab.kitware.com/paraview/paraview/-/issues/216805.11.0: open File dialog Favorites section does not allow removing or renamin...2022-12-13T11:53:17-05:00Cory Quammencory.quammen@kitware.com5.11.0: open File dialog Favorites section does not allow removing or renaming on macOS* Run ParaView, local sever
* File -> Open...
* Left-click one of the items in the Favorites section.
* The context menu will appear, but you cannot select either of the items.
This is probably the same underlying issue that caused #20981.* Run ParaView, local sever
* File -> Open...
* Left-click one of the items in the Favorites section.
* The context menu will appear, but you cannot select either of the items.
This is probably the same underlying issue that caused #20981.5.11.1 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21629ParaView 5.11 RC2 compilation issue with VS 20172023-01-17T20:55:44-05:00Nabil G.ParaView 5.11 RC2 compilation issue with VS 2017Hi
Paraview 5.11 RC2 candidate fails to compile on Windows with Visual Studio C++ 2017 because of one header which was removed from vtkUniformHyperTreeGrid.h header file. Header was present in RC1.
```
--- ParaView-5.11-RC2-ref/VTK/Com...Hi
Paraview 5.11 RC2 candidate fails to compile on Windows with Visual Studio C++ 2017 because of one header which was removed from vtkUniformHyperTreeGrid.h header file. Header was present in RC1.
```
--- ParaView-5.11-RC2-ref/VTK/Common/DataModel/vtkUniformHyperTreeGrid.h 2022-10-27 17:11:36.740861077 +0200
+++ ParaView-5.11-RC2-fix/VTK/Common/DataModel/vtkUniformHyperTreeGrid.h 2022-10-27 17:11:46.572811110 +0200
@@ -30,6 +30,7 @@
#ifndef vtkUniformHyperTreeGrid_h
#define vtkUniformHyperTreeGrid_h
+#include <algorithm> // std::min/std::max
#include "limits.h" // UINT_MAX
#include <cmath> // std::round
```
Enclosed the patch: [vtkUniformHyperTreeGrid.h.patch](/uploads/b576597b9bc0a00e0990d388a1ef5e79/vtkUniformHyperTreeGrid.h.patch)
I did not test with more recent versions of Visual Studio c++ versions.
Regards5.11.1 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/224855.12.0-RC3 volume Rendering produces constant warnings only when connected to...2024-03-25T09:34:04-04:00Phil Smith5.12.0-RC3 volume Rendering produces constant warnings only when connected to a serverUsing the procedure in the latest tutorials, section [**2.10 Clip to Scalar filter**](https://docs.paraview.org/en/latest/Tutorials/ClassroomTutorials/beginningSourcesAndFilters.html#clip-to-scalar-filter) when you are connected to a ser...Using the procedure in the latest tutorials, section [**2.10 Clip to Scalar filter**](https://docs.paraview.org/en/latest/Tutorials/ClassroomTutorials/beginningSourcesAndFilters.html#clip-to-scalar-filter) when you are connected to a server the following warning are displayed:
Generic Warning: In vtkBlockSortHelper.h, line 421 SortFrontToBackImplementation failed with allowDisconnected=1
Generic Warning: In vtkBlockSortHelper.h, line 509 sorting failed
Generic Warning: In vtkBlockSortHelper.h, line 421 SortFrontToBackImplementation failed with allowDisconnected=1
Generic Warning: In vtkBlockSortHelper.h, line 509 sorting failed
Generic Warning: In vtkBlockSortHelper.h, line 421 SortFrontToBackImplementation failed with allowDisconnected=1
Generic Warning: In vtkBlockSortHelper.h, line 509 sorting failed
This continues to populate the output messages popup for the entire time you have it displayed. If the object is moved around it populates it faster.
I tested this with the builtin on v5.12.0-RC3 and it did not display these errors. I also tested it with 5.11.1 both built-in and remote server and it did not display these warnings.
I also noticed that if you move the object around that it has a lot of aliasing happening. Attached is a screenshot of what I am seeing.
![image.png](/uploads/91376946f5e6a23563b1d3a0adba0970/image.png)5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/22465.avi Movie creation crashes on server side2024-01-29T19:35:49-05:00Phil Smith.avi Movie creation crashes on server sideHere is how to replicate.
* Linux client from Kitware download, remote server (32 ranks, I bet it dies with any number over 16 and possibly even possibly 2), 5.12.0-RC2 (Alan built and Kitware built pvserver). (I used 16 ranks and it st...Here is how to replicate.
* Linux client from Kitware download, remote server (32 ranks, I bet it dies with any number over 16 and possibly even possibly 2), 5.12.0-RC2 (Alan built and Kitware built pvserver). (I used 16 ranks and it still died)
* g1s1. This dataset has 16 files.
* Save Animation/ avi. OK.
* Crash.
I used both toss4 and toss2 servers with 36 and 16 ranks respectively, and it still crashed. This was using both the server and the client on Linux. Both the client and the server were Kitware builds.
I received the same errors as Alan:
```
( 46.851s) \[pvserver.6 \] vtkSIProxyProperty.cxx:237 ERR| Property 'Writer' on \['misc', 'RemoteWriterHelper'\] has a value that is not available on this process. That typically indicates that the Location for the Proxy may not be correct. Aborting for debugging purposes.
( 46.852s) \[pvserver.3 \] vtkSIProxyProperty.cxx:237 ERR| Property 'Writer' on \['misc', 'RemoteWriterHelper'\] has a value that is not available on this process. That typically indicates that the Location for the Proxy may not be correct. Aborting for debugging purposes.
( 46.860s) \[pvserver.11 \] vtkSIProxyProperty.cxx:237 ERR| Property 'Writer' on \['misc', 'RemoteWriterHelper'\] has a value that is not available on this process. That typically indicates that the Location for the Proxy may not be correct. Aborting for debugging purposes.
( 46.850s) \[pvserver.22 \] vtkSIProxyProperty.cxx:237 ERR| Property 'Writer' on \['misc', 'RemoteWriterHelper'\] has a value that is not available on this process. That typically indicates that the Location for the Proxy may not be correct. Aborting for debugging purposes.
error: exception occurred: Segmentation fault
error: exception occurred: Segmentation fault
\[proxy:0:0@sb49\] HYD_pmcd_pmip_control_cmd_cb (proxy/pmip_cb.c:480): assert (!closed) failed
\[proxy:0:0@sb49\] HYDT_dmxu_poll_wait_for_event (lib/tools/demux/demux_poll.c:76): callback returned error status
\[proxy:0:0@sb49\] main (proxy/pmip.c:127): demux engine error waiting for event
srun: error: sb49: task 0: Exited with exit code 7
\[mpiexec@sb49\] HYDT_bscu_wait_for_completion (lib/tools/bootstrap/utils/bscu_wait.c:109): one of the processes terminated badly; aborting
\[mpiexec@sb49\] HYDT_bsci_wait_for_completion (lib/tools/bootstrap/src/bsci_wait.c:21): launcher returned error waiting for completion
\[mpiexec@sb49\] HYD_pmci_wait_for_completion (mpiexec/pmiserv_pmci.c:197): launcher returned error waiting for completion
\[mpiexec@sb49\] main (mpiexec/mpiexec.c:252): process manager error waiting for completion
```5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22464ParaView doesn't compile due to missing documentation header2024-01-25T10:27:57-05:00Juan Jose CasafrancaParaView doesn't compile due to missing documentation headerI am trying to compile ParaView, I have tried master and 5.12-RC2 branches. In both cases, there is an issue with a missing header
```
/usr/bin/c++ -DFMT_SHARED -DPARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION=1 -DPARAVIEW_USE_MATERIALEDITOR=0 ...I am trying to compile ParaView, I have tried master and 5.12-RC2 branches. In both cases, there is an issue with a missing header
```
/usr/bin/c++ -DFMT_SHARED -DPARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION=1 -DPARAVIEW_USE_MATERIALEDITOR=0 -DPARAVIEW_USE_PYTHON=0 -DPROTOBUF_USE_DLLS -DQT_CORE5COMPAT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGLWIDGETS_LIB -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -Dkiss_fft_scalar=double -I/home/jjcasmar/seddi/projects/paraview/build/build/Clients/ParaView/paraview_autogen/include -I/home/jjcasmar/seddi/projects/paraview/Clients/ParaView
...
-I/home/jjcasmar/seddi/projects/paraview/build/build/Clients/ParaView ParaViewMainWindow.cxx.o -MF Clients/ParaView/CMakeFiles/paraview.dir/ParaViewMainWindow.cxx.o.d -o Clients/ParaView/CMakeFiles/paraview.dir/ParaViewMainWindow.cxx.o -c /home/jjcasmar/seddi/projects/paraview/Clients/ParaView/ParaViewMainWindow.cxx
/home/jjcasmar/seddi/projects/paraview/Clients/ParaView/ParaViewMainWindow.cxx:41:10: fatal error: ParaViewDocumentationInitializer.h: No such file or directory
41 | #include "ParaViewDocumentationInitializer.h"
```
The file is looking for is under the ParaView/Documentation directory,
```
find ../.. -iname ParaViewDocumentationInitializer.h
../../Clients/ParaView/Documentation/ParaViewDocumentationInitializer.h
```
but that directory is not included in the included directories.
Can be fixed by not compiling the documentation
```
cmake_dependent_option(PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION
"Build the ParaView help menu documentation for ParaView and its plugins" ON
"PARAVIEW_USE_QT" ON)
mark_as_advanced(PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION)
...
if (PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION)
#------------------------------------------------------------------------------
# Build Online-Help (aka Embedded Help) for the ParaView application.
# This is done after the above piece of code that sets the application_gui_xmls
# variable. Documentation/CMakeLists.txt depends on it.
add_subdirectory(Documentation)
endif ()
```
but the option is not exposed in CMake5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22444Saving an animation file fails when a trace is played back2024-01-22T12:22:41-05:00Phil SmithSaving an animation file fails when a trace is played backThis was tested on Mac OSx86 and Linux using ParaView version 5.12.0-RC2.
When performing a trace everything works great until you try and use pvpython or pvbatch to replay the trace. Both of the utilities give the same error as shown b...This was tested on Mac OSx86 and Linux using ParaView version 5.12.0-RC2.
When performing a trace everything works great until you try and use pvpython or pvbatch to replay the trace. Both of the utilities give the same error as shown below:
```
Set PVPYTHON_PYTHONPATH to include custom python modules
OpenGL core version = 4.6
hardwareRender = 1
This is version 5.12.0-RC2-kw of pvpython.
Rendering in Hardware!
VisRTX 0.1.6, using devices:
0: GRID V100S-4Q (Total: 4.3 GB, Available: 2.9 GB)
Traceback (most recent call last):
File "snip/can_test_Two.py", line 106, in <module>
SaveAnimation('snip/cantestTwo.avi', renderView1, 16, ImageResolution=[1616, 788],
File "sinp/5.12.0-RC2-kw/Linux-cee-rhel7-x86_64/lib/python3.10/site-packages/paraview/simple.py", line 1583, in SaveAnimation
options.AnimationScene = scene
File "snip/5.12.0-RC2-kw/Linux-cee-rhel7-x86_64/lib/python3.10/site-packages/paraview/servermanager.py", line 485, in __setattr__
setter(self, value)
File "snip/5.12.0-RC2-kw/Linux-cee-rhel7-x86_64/lib/python3.10/site-packages/paraview/servermanager.py", line 2618, in setProperty
return self.SetPropertyWithName(propName, value)
File "snip/5.12.0-RC2-kw/Linux-cee-rhel7-x86_64/lib/python3.10/site-packages/paraview/servermanager.py", line 344, in SetPropertyWithName
prop.SetData(arg)
File "snip/5.12.0-RC2-kw/Linux-cee-rhel7-x86_64/lib/python3.10/site-packages/paraview/servermanager.py", line 1385, in SetData
self.SMProperty.AddProxy(value_proxy)
TypeError: AddProxy argument 1: method requires a VTK object
```
Here is the file that was generated via Linux and the trace function of paraview:
[can_test_Two.py](/uploads/4cbe400f9b477710c2d4974faa85adde/can_test_Two.py)
The procedure I used to construct the trace, is in the tutorials section [14.3.1.2. Let's create a Python trace](https://docs.paraview.org/en/latest/Tutorials/ClassroomTutorials/pythonAndBatchPvpythonAndPvbatch.html#lets-create-a-python-trace).
@cory.quammen @spiros.tsalikis @wascott5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22412Remote server-Ghost Cell generator hangs v5.12.0-230-Master.2024-03-25T15:15:05-04:00Phil SmithRemote server-Ghost Cell generator hangs v5.12.0-230-Master.Tested on Windows, MacOS x86 and Linux Paraview v5.12.0-230-Master. Steps to reproduce:
1. Connect to our favorite remote server
2. Open g1s1 dataset
3. Apply Ghost cell generator filter
The application freezes up and will not respond. ...Tested on Windows, MacOS x86 and Linux Paraview v5.12.0-230-Master. Steps to reproduce:
1. Connect to our favorite remote server
2. Open g1s1 dataset
3. Apply Ghost cell generator filter
The application freezes up and will not respond. Need to force quit the application to get it to respond. The server stops responding, so I suspect that the server is crashing. The ghost cells are not produced.5.12 (Winter 2023)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/22404Update NVIDIA IndeX plugin for ParaView 5.12.02023-12-06T08:47:45-05:00Cory Quammencory.quammen@kitware.comUpdate NVIDIA IndeX plugin for ParaView 5.12.0* [x] update CI infrastructure with new drivers to support the new version
* [x] [superbuild changes](https://gitlab.kitware.com/paraview/paraview-superbuild/-/merge_requests/1133 "Adapt to NVIDIA IndeX binaries for ParaView 5.12.")
* [x...* [x] update CI infrastructure with new drivers to support the new version
* [x] [superbuild changes](https://gitlab.kitware.com/paraview/paraview-superbuild/-/merge_requests/1133 "Adapt to NVIDIA IndeX binaries for ParaView 5.12.")
* [x] [paraview changes](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6582 "NVIDIA IndeX plugin for ParaView 5.12.0")
cc @ben.boeckel5.12 (Winter 2023)Jörg MensmannJörg Mensmannhttps://gitlab.kitware.com/paraview/paraview/-/issues/223945.12.0-RC1 crashes on Windows saving animation mp42024-01-08T13:42:26-05:00W. Alan Scott5.12.0-RC1 crashes on Windows saving animation mp4We have a crash trying to save an mp4 animation. Here is how to replicate:
* 5.12.0-RC1, Windows, builtin server.
* can.exo. Apply.
* File/ Save Animation. mp4. OK, OK
This will crash.
First reported here: https://discourse.paravi...We have a crash trying to save an mp4 animation. Here is how to replicate:
* 5.12.0-RC1, Windows, builtin server.
* can.exo. Apply.
* File/ Save Animation. mp4. OK, OK
This will crash.
First reported here: https://discourse.paraview.org/t/paraview-5-12-0-rc1-crashes-when-exporting-animation-in-windows-11/133675.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22392Updated Fast color map2024-01-08T11:16:38-05:00W. Alan ScottUpdated Fast color mapAfter further evaluation, we (Ken, Francesca and I) determined that we needed a few more control points to create a really good color map. Thus, we need to update the Fast map. It will now include 9 control points. Here is the new Fast...After further evaluation, we (Ken, Francesca and I) determined that we needed a few more control points to create a really good color map. Thus, we need to update the Fast map. It will now include 9 control points. Here is the new Fast map, along with the old Fast map.
![Old_and_new_Fast2](/uploads/fe6213992f05eb3808a9bf8ac6fa32a2/Old_and_new_Fast2.png)
This must be done for 5.12.0-RC2.
Attached is the .xml from Francesca Samsel. I am also including the text version. Please use these control points for the Fast map.
[Fast-30FINAL.xml](/uploads/8ad43bc7c2782d500806b7fada0d8e25/Fast-30FINAL.xml)
```
<ColorMaps>
<ColorMap name="Divergent 1" space="RGB" interpolationspace="lab" interpolationtype="linear" creator="CCC-Tool">
<Point x="0" o="1" r="0.05639999999999999" g="0.05639999999999999" b="0.47" cms="1" isMoT="true"/>
<Point x="0.17159223942480895" o="1" r="0.24300000000000013" g="0.4603500000000004" b="0.81" cms="1" isMoT="true"/>
<Point x="0.2984914818394138" o="1" r="0.3568143826543521" g="0.7450246485363142" b="0.954367702893722" cms="1" isMoT="true"/>
<Point x="0.4321287371255907" o="1" r="0.6882" g="0.93" b="0.9179099999999999" cms="1" isMoT="true"/>
<Point x="0.5" o="1" r="0.8994959551205902" g="0.944646394975174" b="0.7686567142818399" cms="1" isMoT="true"/>
<Point x="0.5882260353170073" o="1" r="0.957107977357604" g="0.8338185108985666" b="0.5089156299842102" cms="1" isMoT="true"/>
<Point x="0.7061412605695164" o="1" r="0.9275207599610714" g="0.6214389091739178" b="0.31535705838676426" cms="1" isMoT="true"/>
<Point x="0.8476395308725272" o="1" r="0.8" g="0.3520000000000001" b="0.15999999999999998" cms="1" isMoT="true"/>
<Point x="1" o="1" r="0.59" g="0.07670000000000013" b="0.11947499999999994" cms="1" isMoT="true"/>
<NaN r="0" g="0" b="0"/>
<Above r="0" g="0" b="0"/>
<Below r="0" g="0" b="0"/>
</ColorMap>
</ColorMaps>
```5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22388symbols not found in some libraries in binary build2024-01-25T13:36:35-05:00Dan Lipsasymbols not found in some libraries in binary buildThis happens for ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64 and ParaView-master-5.12.0-RC1-160-g92dacc77cb-MPI-Linux-Python3.10-x86_64
```
[~/external]$ tar xzf ~/Downloads/ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64.tar.gz
[~/...This happens for ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64 and ParaView-master-5.12.0-RC1-160-g92dacc77cb-MPI-Linux-Python3.10-x86_64
```
[~/external]$ tar xzf ~/Downloads/ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64.tar.gz
[~/external]$ cd ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64/
~/external/ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64]$ for i in `find . -name '*.so'`; do echo $i;ldd $i | grep 'not found'; done > not_found.txt
```
[not_found.txt](/uploads/d8b853d09f6fc7f9dd1d080d05279709/not_found.txt)
filtered list of libraries:
[not_found_filtered.txt](/uploads/18dda1f5901def3101bedf2e3874a252/not_found_filtered.txt)5.12 (Winter 2023)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22348vtkPVDataSetAlgorithmSelectorFilter does not fully support composite input2023-12-11T08:31:15-05:00Charly BollingervtkPVDataSetAlgorithmSelectorFilter does not fully support composite inputThe `vtkPVDataSetAlgorithmSelectorFilter` used to be able to switch active filter on the fly takes `vtkDataSet` and `vtkHyperTreeGrid` in input (see `FillInputPortInformation`). This means the pipeline will execute the selected filter on...The `vtkPVDataSetAlgorithmSelectorFilter` used to be able to switch active filter on the fly takes `vtkDataSet` and `vtkHyperTreeGrid` in input (see `FillInputPortInformation`). This means the pipeline will execute the selected filter on each dataset of the composite. This is what happens with `vtkPVMetaClipDataSet` (ie. `Clip`) or `vtkPVMetaSliceDataSet` (ie. `Slice`).
However, if a filter can explicitely execute on composite datasets, like the `vtkGhostCellsGenerator`, it will not execute correctly.
This is the issue described in #22343.
On the other hand, setting input port information to `vtkDataObject`, although fixing above issue, will make the composite pipeline to stop working. This means `Slice`, for example, will not work anymore on a composite dataset.5.12 (Winter 2023)Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)