ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-08-25T17:07:52-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/20458Text property alignement action order is not coherent2021-08-25T17:07:52-04:00Mathieu Westphal (Kitware)Text property alignement action order is not coherentHorizontal justification actions are in the following order:
* Left
* Right
* Center
While Vertical justification actions are in the following order:
* Center
* Bottom
* Top
Imo it should be:
* Left
* Center
* Right
and
* Top
...Horizontal justification actions are in the following order:
* Left
* Right
* Center
While Vertical justification actions are in the following order:
* Center
* Bottom
* Top
Imo it should be:
* Left
* Center
* Right
and
* Top
* Center
* Bottom
@paul.lafoixhttps://gitlab.kitware.com/paraview/paraview/-/issues/20457MathText Matplotlib text rendering does not support font settings2021-01-28T10:51:27-05:00Mathieu Westphal (Kitware)MathText Matplotlib text rendering does not support font settingsWhen rendering text with matplotlib, changing the font, boldness, italicness and shadowing has no effect
Steps to reproduce:
* Open ParaView
* Add **Text** source
* In the **Text** property, enter
```
$A^2$
$B^2$
```
* Change the font
...When rendering text with matplotlib, changing the font, boldness, italicness and shadowing has no effect
Steps to reproduce:
* Open ParaView
* Add **Text** source
* In the **Text** property, enter
```
$A^2$
$B^2$
```
* Change the font
* Nothing happens
FYI @paul.lafoixhttps://gitlab.kitware.com/paraview/paraview/-/issues/20456Python Editor open file issue2023-06-15T15:42:41-04:00Mathieu Westphal (Kitware)Python Editor open file issue- Tools -> Python Editor
- File -> Open
- **The window is called Save File and actually behave like a save file window**, this is a bug
- Open a file.py
@thomas.caissard- Tools -> Python Editor
- File -> Open
- **The window is called Save File and actually behave like a save file window**, this is a bug
- Open a file.py
@thomas.caissardhttps://gitlab.kitware.com/paraview/paraview/-/issues/20455Sometime isnan is a macro2021-01-28T08:59:04-05:00Alain MiniussiSometime isnan is a macroWhen building 4.9.0 with Intel 2020 update2 on top of Gcc 8.3 (library support) on CentOS7, I get the following error:
```
[337/20298] Generating the wrap hierarchy for VTK::CommonCore
FAILED: lib64/vtk/hierarchy/ParaView/vtkCommonCore-h...When building 4.9.0 with Intel 2020 update2 on top of Gcc 8.3 (library support) on CentOS7, I get the following error:
```
[337/20298] Generating the wrap hierarchy for VTK::CommonCore
FAILED: lib64/vtk/hierarchy/ParaView/vtkCommonCore-hierarchy.txt
cd /beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/paraview_build/VTK/Common/Core && /beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/paraview_build/bin/vtkWrapHierarchy-pv5.9 @/beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/paraview_build/VTK/Common/Core/CMakeFiles/vtkCommonCore-hierarchy.Release.args -o /beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/paraview_build/lib64/vtk/hierarchy/ParaView/vtkCommonCore-hierarchy.txt /beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/paraview_build/VTK/Common/Core/CMakeFiles/vtkCommonCore-hierarchy.data @/beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/paraview_build/VTK/Common/Core/CMakeFiles/vtkCommonCore-hierarchy.depends.args
vtkWrapHierarchy-pv5.9: In /beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/VTK/Common/Core/vtkGenericDataArrayLookupHelper.h:39: syntax error.
[378/20298] Building C object VTK/ThirdParty/glew/vtkglew/CMakeFiles/glew.dir/src/glew.c.o
ninja: build stopped: subcommand failed.
```
The error disappear if I insert:
```
#ifdef isnan
#undef isnan
#endif
```
before line 39
Thankshttps://gitlab.kitware.com/paraview/paraview/-/issues/20454XL build of ParaView 5.8.1 and 5.9.0 fails at curly brace initializing2021-02-17T18:15:18-05:00Ethan StamXL build of ParaView 5.8.1 and 5.9.0 fails at curly brace initializing@ben.boeckel
Relevant discussion here: https://gitlab.kitware.com/paraview/paraview/-/issues/20253#note_892895
Using ibm xlc 16.1.1.7, xlf 16.1.1.7, gcc 8.3.0, cuda-11.0 . ParaView 5.8.1 and 5.9.0 builds fail with:
```console
In file...@ben.boeckel
Relevant discussion here: https://gitlab.kitware.com/paraview/paraview/-/issues/20253#note_892895
Using ibm xlc 16.1.1.7, xlf 16.1.1.7, gcc 8.3.0, cuda-11.0 . ParaView 5.8.1 and 5.9.0 builds fail with:
```console
In file included from .../VTK/Common/DataModel/vtkStaticCellLinksTemplate.h:162:
.../VTK/Common/DataModel/vtkStaticCellLinksTemplate.txx:359:61: error: 1540-2991 The expression is not supported.
std::atomic<TIds>* counts = new std::atomic<TIds>[numPts] {};
^
```
https://www.ibm.com/support/knowledgecenter/en/SSXVZZ_16.1.1/com.ibm.xlcpp1611.lelinux.doc/language_ref/standard_features.html shows XL does not fully support std::atomic . We were not hitting this issue when vtkAtomic was used.
Edit: It looks like std::atomic is not the root cause, but the use of `{}` is. Possible workaround in https://gitlab.kitware.com/paraview/paraview/-/issues/20454#note_896613https://gitlab.kitware.com/paraview/paraview/-/issues/20453Doxygen and ReadTheDocs docs are not pushed when in a tag2021-01-27T14:06:43-05:00Vicente Boleavicente.bolea@kitware.comDoxygen and ReadTheDocs docs are not pushed when in a tag`Doxygen` and `ReadTheDocs` docs are generated when the pipeline is "scheduled"
We currently only schedule docs jobs for the "master" branch and the results are pushed as the nightly version of the docs.
For some reason we cannot get ...`Doxygen` and `ReadTheDocs` docs are generated when the pipeline is "scheduled"
We currently only schedule docs jobs for the "master" branch and the results are pushed as the nightly version of the docs.
For some reason we cannot get the same results for ParaView tags.https://gitlab.kitware.com/paraview/paraview/-/issues/20452python completion triggers RequestData2023-07-07T12:40:31-04:00Nicolas Vuaillepython completion triggers RequestDataIn pvpython and in python shell, asking for completion trigger the RequestData of the targeted object.
To reproduce in pvpython:
```bash
Python 3.9.1 (default, Dec 13 2020, 11:55:53)
[GCC 10.2.0] on linux
Type "help", "copyright", "cre...In pvpython and in python shell, asking for completion trigger the RequestData of the targeted object.
To reproduce in pvpython:
```bash
Python 3.9.1 (default, Dec 13 2020, 11:55:53)
[GCC 10.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from paraview.simple import *
>>> s = Sphere()
>>> s.( 26.482s) [paraview ] vtkSphereSource.cxx:69 WARN| vtkSphereSource (0x556286e79310): request data called
```
(I press tab to ask for members of `s` and I previously **put a vtkWarningMacro in vtkSphereSource::RequestData**)
```
--- a/Filters/Sources/vtkSphereSource.cxx
+++ b/Filters/Sources/vtkSphereSource.cxx
@@ -61,6 +61,7 @@ vtkSphereSource::vtkSphereSource(int res)
int vtkSphereSource::RequestData(vtkInformation* vtkNotUsed(request),
vtkInformationVector** vtkNotUsed(inputVector), vtkInformationVector* outputVector)
{
+ vtkWarningMacro("SphereSource::RequestData");
// get the info object
vtkInformation* outInfo = outputVector->GetInformationObject(0);
```https://gitlab.kitware.com/paraview/paraview/-/issues/20451Definition not found for SurfaceLICRepresentation in ParaView-5.9.02021-08-24T21:07:29-04:00Jan KrautterDefinition not found for SurfaceLICRepresentation in ParaView-5.9.0With the latest version I am getting the following kind of error messages, when trying to use the Surface LIC representation in parallel/batch through python. Interactively the plugin works and the commands/names seem to be the same as b...With the latest version I am getting the following kind of error messages, when trying to use the Surface LIC representation in parallel/batch through python. Interactively the plugin works and the commands/names seem to be the same as before. The same script was working with 5.7.0 and before.
I am not sure if anything has changed? Or if this is a bug.
```
[0m�[31m( 26.345s) [pvbatch.3 ]vtkSIProxyDefinitionMan:526 ERR| vtkSIProxyDefinitionManager (0x11d1f80): No proxy that matches: group=representations and proxy=SurfaceLICRepresentation were found.�[0m
�[0m�[31m( 26.345s) [pvbatch.4 ]vtkSIProxyDefinitionMan:526 ERR| vtkSIProxyDefinitionManager (0x1d88610): No proxy that matches: group=representations and proxy=SurfaceLICRepresentation were found.�[0m
�[0m�[31m( 26.345s) [pvbatch.1 ]vtkSIProxyDefinitionMan:526 ERR| vtkSIProxyDefinitionManager (0x25e4d90): No proxy that matches: group=representations and proxy=SurfaceLICRepresentation were found.�[0m
�[0m�[31m( 26.345s) [pvbatch.5 ]vtkSIProxyDefinitionMan:526 ERR| vtkSIProxyDefinitionManager (0x226fe50): No proxy that matches: group=representations and proxy=SurfaceLICRepresentation were found.�[0m
�[0m�[31m( 26.345s) [pvbatch.1 ] vtkSIProxy.cxx:326 ERR| vtkSISourceProxy (0xa961640): Definition not found for xml_group: representations and xml_name: SurfaceLICRepresentation
global_id: 716
location: 21
[paraview_protobuf.DefinitionHeader.client_class]: "vtkSMRepresentationProxy"
[paraview_protobuf.DefinitionHeader.server_class]: "vtkSISourceProxy"
[paraview_protobuf.ProxyState.xml_group]: "representations"
[paraview_protobuf.ProxyState.xml_name]: "SurfaceLICRepresentation"
[paraview_protobuf.ProxyState.vtk_classname]: "vtkSurfaceLICRepresentation"
```
For reference: I am using BALANCED CompositeStrategy, not sure if that has anything to do with it tbh, but maybe it helps.
Thank you for any help5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20450paraview 5.9.0 fails to build in Fedora Rawhide2021-04-29T21:24:23-04:00Orion Poplawskiparaview 5.9.0 fails to build in Fedora RawhideI've been building successfully the 5.9.0 RCs for a while in Fedora Rawhide, but now 5.9.0 build fails with:
```
[100%] Built target pvpython
make[2]: Leaving directory '/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu'
/usr...I've been building successfully the 5.9.0 RCs for a while in Fedora Rawhide, but now 5.9.0 build fails with:
```
[100%] Built target pvpython
make[2]: Leaving directory '/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu'
/usr/bin/make -f Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/build.make Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/depend
make[3]: Entering directory '/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu'
cd /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /builddir/build/BUILD/ParaView-v5.9.0 /builddir/build/BUILD/ParaView-v5.9.0/Utilities/Sphinx /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/DependInfo.cmake --color=
Dependee "/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/DependInfo.cmake" is newer than depender "/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/depend.internal".
Dependee "/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/depend.internal".
Scanning dependencies of target ParaViewPythonDoc
make[3]: Leaving directory '/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu'
/usr/bin/make -f Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/build.make Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/build
make[3]: Entering directory '/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu'
cd /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx && ../../bin/pvpython --no-mpi /builddir/build/BUILD/ParaView-v5.9.0/Utilities/Sphinx/sphinx_apidoc.py -o /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx/config /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/lib64/paraview/python3.9/site-packages/paraview
make[3]: Leaving directory '/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu'
unknown option --no-mpi
usage: /lib64/vtkpython [option] ... [-c cmd | -m mod | file | -] [arg] ...
Try `python -h' for more information.
Loguru caught a signal: SIGSEGV
Stack trace:
9 0x55f77263d8ae ../../bin/pvpython(+0x28ae) [0x55f77263d8ae]
8 0x7f6ccadbdb75 __libc_start_main + 213
7 0x55f77263e268 ../../bin/pvpython(+0x3268) [0x55f77263e268]
6 0x7f6cc9cba3b3 vtkInitializationHelper::Finalize() + 211
5 0x7f6cc93c64da vtkProcessModule::Finalize() + 314
4 0x7f6cc8a60286 Py_FinalizeEx + 134
3 0x7f6cc8a605f3 _PyThreadState_DeleteExcept + 35
2 0x7f6cc89a996c PyThread_acquire_lock_timed + 220
1 0x7f6cc8479c3d sem_wait + 13
0 0x7f6ccadd3300 /lib64/libc.so.6(+0x3d300) [0x7f6ccadd3300]
( 0.212s) [paraview ] :0 FATL| Signal: SIGSEGV
make[3]: *** [Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/build.make:79: Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc] Segmentation fault (core dumped)
make[2]: *** [CMakeFiles/Makefile2:39505: Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:39512: Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/rule] Error 2
make: *** [Makefile:10781: ParaViewPythonDoc] Error 2
```
I'm building docs:
```
export LANG=en_US.UTF-8
%make_build ParaViewDoxygenDoc ParaViewPythonDoc
```
after building the serial version of paraview.
Full logs: https://kojipkgs.fedoraproject.org//work/tasks/8138/60518138/build.log5.9.1 (Spring 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/204495.9.0 known issues2021-05-18T21:45:43-04:00Cory Quammencory.quammen@kitware.com5.9.0 known issuesThis issues tracks known issues in 5.9.0 that should be fixed in any patch release that might be made.
- [x] https://gitlab.kitware.com/paraview/paraview/-/issues/20443
- [ ] https://gitlab.kitware.com/paraview/paraview/-/issues/20447
-...This issues tracks known issues in 5.9.0 that should be fixed in any patch release that might be made.
- [x] https://gitlab.kitware.com/paraview/paraview/-/issues/20443
- [ ] https://gitlab.kitware.com/paraview/paraview/-/issues/20447
- [x] https://gitlab.kitware.com/vtk/vtk/-/merge_requests/7540
- [x] https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4594
/cc @utkarsh.ayachit @mwestphal @acbauer @ben.boeckel @vbolea5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20448Save .vtk data as Meta Image File (.mhd) returns empty .zraw fle2021-01-25T13:53:35-05:00Scott GSave .vtk data as Meta Image File (.mhd) returns empty .zraw fleWhen attempting to save the `.vtk` data in .mhd format, the .mhd file contains header information but the `.zraw` file is completely empty. The process applied for this issue was:
**Attempt 1**
1. Open a `*.vtk` file - click Apply
2. Ap...When attempting to save the `.vtk` data in .mhd format, the .mhd file contains header information but the `.zraw` file is completely empty. The process applied for this issue was:
**Attempt 1**
1. Open a `*.vtk` file - click Apply
2. Apply the filter ResampleToImage - click Apply (make sure the input field is the selected variable of interest)
3. `File>>Save Data>>Meta Image file (*.mhd)`
4. Check contents... they are empty :(
**Attempt 2**
1. Same as Attempt but add a Calculator filter between the resample step and save data step.
- https://discourse.paraview.org/t/resampletoimage-filter-output-save-as-a-mhd-file/5318/5
2. Check contents... they are empty :(
**ParaView Versions Tested:**
- Linux 5.6.0 and 5.9
- Windows 5.8.0
Any insight on if this is something which can be fixed or worked around would be greatly appreciated.
----
`test.mhd` contents
````
ObjectType = Image
NDims = 3
BinaryData = True
BinaryDataByteOrderMSB = False
CompressedData = True
TransformMatrix = 1 0 0 0 1 0 0 0 1
Offset = -1000 -1000 -1000
CenterOfRotation = 0 0 0
ElementSpacing = 20.202020645141602 20.202020645141602 20.202020645141602
DimSize = 100 100 100
AnatomicalOrientation = ???
ElementType = MET_DOUBLE
ElementDataFile = test.zraw
````https://gitlab.kitware.com/paraview/paraview/-/issues/20447File Open can cause ParaView to crash when invalid volume mounted2024-02-14T10:20:15-05:00Kenneth MorelandFile Open can cause ParaView to crash when invalid volume mountedMultiple users have reported that ParaView crashes immediately on mac after clicking on `File` -> `Open`. The crash happens before the file browser appears, so it has nothing to do with a malformed file. Here are two references to such a...Multiple users have reported that ParaView crashes immediately on mac after clicking on `File` -> `Open`. The crash happens before the file browser appears, so it has nothing to do with a malformed file. Here are two references to such a problem:
* https://www.paraview.org/pipermail/paraview/2017-March/039781.html
* https://discourse.paraview.org/t/paraview-crashes-immediately-when-opened/6278
In both cases, the problem appeared to be an issue with the system having mounted a volume that cannot be accessed. One of the users reported that running `ls -l /Volumes` caused the error `ls: volume_name: Permission denied` to occur. Unmounting the inaccessible volume seems to fix the problem with ParaView.
ParaView seems to be crashing when it is not able to access mounted volumes (probably when it is collecting the "special" directories). ParaView should instead either issue a warning or just ignore the directory.
This might be related to #17536, which appears to be a similar problem on Windows.
A workaround to this problem is to unmount any file system that you don't have access to.5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20446Release Paraview 5.9.02021-03-18T12:24:32-04:00Vicente Boleavicente.bolea@kitware.comRelease Paraview 5.9.0# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.9.0.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.9.0.pdf
- [x] Upload to www.paraview.org/files/v5.9
- Assemble release notes into `Documentation/release/ParaView-5.9.0`.
- [x] Get positive review and merge.
# Update ParaView
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.9.0
echo 5.9.0 > version.txt
git commit -m 'Update version number to 5.9.0' version.txt
git tag -a -m 'ParaView 5.9.0' v5.9.0 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] `Do: merge`
- Integrate changes to `release` branch (push the `update-to-v@version@` branch to be the new `release` branch)
- [x] `git push origin update-to-v5.9.0:release`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.9.0`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs user@host:ParaView_Release/v5.9/`
# Update ParaView-Superbuild
- [x] Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
git checkout -b update-to-v5.9.0
```
- Update `CMakeLists.txt`
- [x] Update PARAVIEW_VERSION_DEFAULT to the release version (without RC*)
- [x] Set ParaView source selections in `CMakeLists.txt` and force explicit
version in `CMakeLists.txt`:
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.9.0" CACHE STRING "Force version to 5.9.0" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] `paraview_SOURCE_SELECTION` version in `README.md`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.9.0
- [x] ARG SUPERBUILD_TAG=v5.9.0
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.9
- [x] Commit changes and push to GitLab
```
git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile
git commit -m "Update the default version to 5.9.0"
git gitlab-push
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP (do *not* add `Backport: release` to description)
- [x] Build binaries (start all pipelines)
- [x] Download the binaries that have been generated from the Pipeline build products. They will be deleted within 24 hours.
- [x] Remove explicit version forcing added in `CMakeLists.txt` and force push
```
git add CMakeLists.txt
git commit --amend --no-edit
git gitlab-push -f
```
- Finalize merge request
- [x] Remove WIP from merge request title
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.9.0' v5.9.0 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.9.0:release`
# Sign macOS binaries
- [x] Upload to signing server, run script, download resulting .pkg and .dmg files
- [x] Install from .pkg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.9.0.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.9.0.app/`
# Validating binaries
For each binary, open the Python shell and run the following:
```python
import numpy
s = Show(Sphere())
ColorBy(s, ('POINTS', 'Normals', 'X'))
Show(Text(Text="$A^2$"))
```
Check that
- Getting started guide opens
- Examples load and match thumbnails in dialog
- Python. Open the Python shell and run
- Plugins are present and load properly
- OSPRay raycasting and pathtracing runs
- OptiX pathtracing runs
- IndeX runs
- AutoMPI
Binary checklist
- [x] macOS
- [x] Linux
- [x] Linux osmesa
- [x] Windows MPI (.exe)
- [x] Windows MPI (.zip)
- [x] Windows no-MPI (.exe)
- [x] Windows no-MPI (.zip)
# Upload binaries
- [x] Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.9/`)
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website
```
buildListing.sh
updateMD5sum.sh v5.9
```
- [x] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.9.0`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.9.0`.
# Spack
- [x] Update Spack package: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py
# Update documentation
- [x] Upload versioned documentation to `https://github.com/kitware/paraview-docs` (see `https://github.com/Kitware/paraview-docs/blob/master/README.md`)
- [x] Tag the [ParaView docs](https://gitlab.kitware.com/paraview/paraview-docs/-/tags) with v5.9.0.
- [x] Activate the tag on [readthedocs](https://readthedocs.org/projects/paraview/versions/) and build it [here](https://readthedocs.org/projects/paraview/)
- [x] Go to readthedocs.org and activate
- [x] Write and publish blog post with release notes.
- [x] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [x] Request DoD vulnerability scan
- [x] Request update of version number in "Download Latest Release" text on www.paraview.org
- [x] Request update of link to ParaView Guide PDF at https://www.paraview.org/paraview-guide/
- [x] Move unclosed issues to next release milestone in GitLab
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachitVicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20445Text and logo annotations state is not restored correctly2021-11-10T11:46:53-05:00Stephen SanchezText and logo annotations state is not restored correctlyIn ParaView master, when saving a state file that contains logo and/or text annotations, restoring that state file doesn't restore the annotation using the same settings that they were saved with. For example, size and coordinates are c...In ParaView master, when saving a state file that contains logo and/or text annotations, restoring that state file doesn't restore the annotation using the same settings that they were saved with. For example, size and coordinates are completely changed.
Steps to reproduce:
1. Add a source like sphere or box.
2. Add a logo annotation. Resize and place on the render view where desired.
3. Do the same as in step 2 with a text annotation.
4. Save the state file.
5. Reset session or close ParaView and reopen. Load the state file.
BUG: You'll see that the annotations have been moved and resized from where they were when they were originally saved.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20444seg fault running simple python script with mpi (5.9.0 RC4)2023-06-15T11:25:25-04:00Scott Wittenburgseg fault running simple python script with mpi (5.9.0 RC4)I downloaded release candidate binary for mac os (ParaView-5.9.0-RC4-MPI-OSX10.13-Python3.8-64bit.dmg), and then tried to run a simple python script, and it resulted in a segmentation fault.
Here is the `pvpython`/`pvbatch` script:
```...I downloaded release candidate binary for mac os (ParaView-5.9.0-RC4-MPI-OSX10.13-Python3.8-64bit.dmg), and then tried to run a simple python script, and it resulted in a segmentation fault.
Here is the `pvpython`/`pvbatch` script:
```python
import paraview.simple as simple
simple.servermanager.Connect("localhost")
print("connected")
cone = simple.Cone()
print("cone created")
```
Here are the steps to reproduce:
Start the server
```console
/Applications/ParaView-5.9.0-RC4.app/Contents/bin/pvserver --force-offscreen-rendering
```
Start the client
```console
/Applications/ParaView-5.9.0-RC4.app/Contents/bin/pvbatch ./client_script.py
```
Here's the output from the client:
```console
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
connected
Loguru caught a signal: SIGSEGV
Stack trace:
24 0x2 28 ??? 0x0000000000000002 0x0 + 2
23 0x7fff721b2cc9 start + 1
22 0x10fc99742 ParaViewPython::Run(int, int, char**) + 818
21 0x11026a91e vtkPythonInterpreter::PyMain(int, char**) + 558
20 0x111e2eb9b Py_Main + 43
19 0x111e2ed46 pymain_main + 406
18 0x111e2e77a Py_RunMain + 2234
17 0x111e0e76f PyRun_SimpleFileExFlags + 271
16 0x111e0f373 PyRun_FileExFlags + 291
15 0x111dbc1f0 PyEval_EvalCode + 48
14 0x111dc8223 _PyEval_EvalCodeWithName + 3459
13 0x111dc38bd _PyEval_EvalFrameDefault + 30253
12 0x111dc7092 call_function + 354
11 0x111ce056e _PyFunction_Vectorcall + 254
10 0x111dc8223 _PyEval_EvalCodeWithName + 3459
9 0x111dc38bd _PyEval_EvalFrameDefault + 30253
8 0x111dc7092 call_function + 354
7 0x111ce2f3b method_vectorcall + 171
6 0x111ce056e _PyFunction_Vectorcall + 254
5 0x111dc8223 _PyEval_EvalCodeWithName + 3459
4 0x111dc3e04 _PyEval_EvalFrameDefault + 31604
3 0x111ce00b3 cfunction_call_varargs + 323
2 0x12ac450b8 PyvtkSMParaViewPipelineController_RegisterPipelineProxy(_object*, _object*) + 504
1 0x10fd52c6a vtkSMParaViewPipelineController::RegisterPipelineProxy(vtkSMProxy*, char const*) + 442
0 0x4 4 ??? 0x0000000000000004 0x0 + 4
( 8.031s) [pvbatch ] :0 FATL| Signal: SIGSEGV
Segmentation fault: 11
```
Here's the output from the server:
```console
Waiting for client...
Connection URL: cs://Scotts-MacBook-Pro-2.local:11111
Accepting connection(s): Scotts-MacBook-Pro-2.local:11111
Client connected.
( 22.205s) [pvserver ]vtkSocketCommunicator.c:781 ERR| vtkSocketCommunicator (0x7fb044e19d80): Could not receive tag. 1
( 22.205s) [pvserver ]vtkTCPNetworkAccessMana:297 ERR| vtkTCPNetworkAccessManager (0x7fb044d117a0): Some error in socket processing.
( 22.205s) [pvserver ] vtkSocket.cxx:532 ERR| vtkClientSocket (0x7fb044e171b0): Socket error in call to send. Broken pipe.
( 22.205s) [pvserver ] vtkSocket.cxx:532 ERR| vtkClientSocket (0x7fb044e171b0): Socket error in call to send. Broken pipe.
...
( 22.319s) [pvserver ] vtkSocket.cxx:532 ERR| vtkClientSocket (0x7fb044e171b0): Socket error in call to send. Broken pipe.
Segmentation fault: 11
```
For brevity, in the server output above, I omitted many, many of those `Socket error in call to send. Broken pipe.` messages in favor of `...`.https://gitlab.kitware.com/paraview/paraview/-/issues/20443Cinemasci server not working with 5.9.0-RC42021-02-18T10:09:47-05:00Ethan StamCinemasci server not working with 5.9.0-RC4@utkarsh.ayachit @dhr is aware and working on a fix. If this can still make it into 5.9.0, that would be great. Thanks.
Steps to reproduce:
1. Download and install 5.9.0-RC4 from paraview.org
2. Run the cinemasci server (no cinema datab...@utkarsh.ayachit @dhr is aware and working on a fix. If this can still make it into 5.9.0, that would be great. Thanks.
Steps to reproduce:
1. Download and install 5.9.0-RC4 from paraview.org
2. Run the cinemasci server (no cinema database needed to reproduce) with `/Applications/ParaView-5.9.0-RC4.app/Contents/bin/pvpython -m paraview.tpl.cinemasci.server`
```console
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Traceback (most recent call last):
File "/Applications/ParaView-5.9.0-RC4.app/Contents/Libraries/lib/python3.8/runpy.py", line 185, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/Applications/ParaView-5.9.0-RC4.app/Contents/Libraries/lib/python3.8/runpy.py", line 144, in _get_module_details
return _get_module_details(pkg_main_name, error)
File "/Applications/ParaView-5.9.0-RC4.app/Contents/Libraries/lib/python3.8/runpy.py", line 111, in _get_module_details
__import__(pkg_name)
File "/Applications/ParaView-5.9.0-RC4.app/Contents/Python/paraview/tpl/cinemasci/server/__init__.py", line 14, in <module>
import cinemasci
ModuleNotFoundError: No module named 'cinemasci'
```5.9.1 (Spring 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20442Paraview 5.7.0 not working when loading a new project in Vmware2021-01-19T06:44:50-05:00Khalid MParaview 5.7.0 not working when loading a new project in VmwareI just got into using paraview and Linux in general for a final year project of mine. The project files work fine they have been tested on another machine. The problem is that it doesn't load the design and the view panel will often beco...I just got into using paraview and Linux in general for a final year project of mine. The project files work fine they have been tested on another machine. The problem is that it doesn't load the design and the view panel will often become see through. I'm using VMware, Ubuntu 20.04 on a windows 10 machine.
Any help will be appreciated and thank you.https://gitlab.kitware.com/paraview/paraview/-/issues/20441VTP reading speed and animations2021-01-19T13:13:28-05:00Riccardo RossiVTP reading speed and animationsI use Paraview (latest release) on a remote cluster via VNC and virtualgl.
When I need to make a video from an OpenFOAM simulation, I usually save a bunch of vtp files at runtime along with the associated vtp.series file, then I open it...I use Paraview (latest release) on a remote cluster via VNC and virtualgl.
When I need to make a video from an OpenFOAM simulation, I usually save a bunch of vtp files at runtime along with the associated vtp.series file, then I open it in Paraview and save png images via "save animation" (I finally process the png files via menconder).
However, if I have say 1500 files of 16MB size each, it takes more than 2 hours for Paraview to complete the process and looks like most of the time is spent reading the files.
Is this scenario reasonable? If so, is there a way to speed up the process or is there a better way to create animations?https://gitlab.kitware.com/paraview/paraview/-/issues/20440Opening PVTU file yields different results than opening each piece separetely2021-01-18T11:13:56-05:00Gonzalo SáezOpening PVTU file yields different results than opening each piece separetelyHi everyone,
I'm facing an issue when visualizing the attached `pvtu` file. If I open this file in Paraview (5.9.0RC4 and other older versions) I see weird artifacts. However, if I open each `piece` of the considered `pvtu` file separet...Hi everyone,
I'm facing an issue when visualizing the attached `pvtu` file. If I open this file in Paraview (5.9.0RC4 and other older versions) I see weird artifacts. However, if I open each `piece` of the considered `pvtu` file separetely I can observe the expected results. I attach a picture to explain this issue.
Does anyone know if this is problem is related to VTK? I have generated these files using the `vtkXMLPUnstructuredGridWriter` class.
Thank you!
![image](/uploads/381acb3ee46191e8babf5b28af631e05/image.png)
[DP1__000000.rar](/uploads/95ca66413b692fc0f8a4ad848532fd54/DP1__000000.rar)https://gitlab.kitware.com/paraview/paraview/-/issues/20439Redistribute DataSet filter when applied to a Multiblock causes block names t...2021-04-07T20:19:38-04:00Utkarsh AyachitRedistribute DataSet filter when applied to a Multiblock causes block names to change.With changes to Redistribute DataSet filter to use `vtkPartitionedDataSetCollectionToMultiBlockDataSet` and `vtkDataObjectToPartitionedDataSetCollection` internally to handle multiblock dataset, we end up with block names changed in the ...With changes to Redistribute DataSet filter to use `vtkPartitionedDataSetCollectionToMultiBlockDataSet` and `vtkDataObjectToPartitionedDataSetCollection` internally to handle multiblock dataset, we end up with block names changed in the output.
Input: ![image](/uploads/cc116747630b3a5507016a0ca68356f0/image.png)
Output: ![image](/uploads/b11357a0b0ef1b38c80a47c9bdac4e4f/image.png)5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachit