ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-11-18T13:28:28-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/20318Rotations seems to be inverted in pqCameraToolbar2020-11-18T13:28:28-05:00MelanieCarriereRotations seems to be inverted in pqCameraToolbarThe `CW` and the `CCW`rotations seems to be inverted https://gitlab.kitware.com/paraview/paraview/-/blob/master/Qt/ApplicationComponents/pqCameraToolbar.cxx#L52The `CW` and the `CCW`rotations seems to be inverted https://gitlab.kitware.com/paraview/paraview/-/blob/master/Qt/ApplicationComponents/pqCameraToolbar.cxx#L52Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20317PlotMatrixViewDensityMaps is failing2020-12-16T17:38:33-05:00Utkarsh AyachitPlotMatrixViewDensityMaps is failingIt highlights an issue with loading proxy definitions.
see discussion here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4490#note_855522It highlights an issue with loading proxy definitions.
see discussion here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4490#note_8555225.9 (Fall 2020)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/20316Compilation with NVIDIA EGL fails on ppc64le2020-11-10T17:11:22-05:00Robert Manson-SawkoCompilation with NVIDIA EGL fails on ppc64leHello,
I am trying to compile ParaView v5.8.1 with EGL using NVIDIA stack. They changed slightly how they package OpenGL and friends `ppc64le` RHEL and now all libraries sit in `/usr/lib64/*_nvidia.so*` rather than in the separate direc...Hello,
I am trying to compile ParaView v5.8.1 with EGL using NVIDIA stack. They changed slightly how they package OpenGL and friends `ppc64le` RHEL and now all libraries sit in `/usr/lib64/*_nvidia.so*` rather than in the separate directory.
I use the following:
```bash
cmake \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DBUILD_TESTING=OFF \
-DPARAVIEW_USE_PYTHON=OFF \
-DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON \
-DPARAVIEW_USE_MPI=ON \
-DVTK_USE_X=OFF \
-DOPENGL_egl_LIBRARY=/usr/lib64/libEGL_nvidia.so.0 \
-DOPENGL_gles2_LIBRARY=/usr/lib64/libGLESv2_nvidia.so.2 \
-DOPENGL_gles3_LIBRARY=/usr/lib64/libGLESv2_nvidia.so.2 \
-DOPENGL_glx_LIBRARY=/usr/lib64/libGLX_nvidia.so.0 \
-DPARAVIEW_USE_QT=OFF \
-DCMAKE_INSTALL_PREFIX=${INSTALL_DIR} \
../ParaView-v${VERSION} \
&& make -j20 \
&& rm -rf $INSTALL_DIR \
&& make install
```
This is the error I am encountering:
```
/gpfs/users/shared/apps/core/gcc/9.2.0/bin/g++ -O2 -g -DNDEBUG -Wl,-lc -Wl,-lc -Wl,-rpath=/gpfs/users/shared/apps/compiler/gcc/9.2/openmpi/3.1.4/lib CMakeFiles/vtkProbeOpenGLVersion.dir/vtkProbeOpenGLVersion.cxx.o -o ../../../bin/vtkProbeOpenGLVersion-pv5.8 -Wl,-rpath,/gpfs/users/rrs59-sxa03/sources/paraview/build-paraview-5.8.1-gcc-ompi/lib64: ../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8 ../../../lib64/libvtkRenderingCore-pv5.8.so.5.8 ../../../lib64/libvtkFiltersCore-pv5.8.so.5.8 ../../../lib64/libvtkglew-pv5.8.so.5.8 /usr/lib64/libEGL_nvidia.so.0 /usr/lib64/libOpenGL.so ../../../lib64/libvtkCommonExecutionModel-pv5.8.so.5.8 ../../../lib64/libvtkCommonDataModel-pv5.8.so.5.8 ../../../lib64/libvtkCommonTransforms-pv5.8.so.5.8 ../../../lib64/libvtkCommonMisc-pv5.8.so.5.8 ../../../lib64/libvtkCommonMath-pv5.8.so.5.8 ../../../lib64/libvtkCommonCore-pv5.8.so.5.8 -lpthread ../../../lib64/libvtksys-pv5.8.so.5.8 -ldl -Wl,-rpath-link,/gpfs/users/rrs59-sxa03/sources/paraview/build-paraview-5.8.1-gcc-ompi/lib64
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglQueryString'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglCreateContext'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglGetCurrentDisplay'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglGetDisplay'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglGetProcAddress'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglQuerySurface'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglMakeCurrent'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglDestroyContext'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglGetError'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglChooseConfig'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglSwapBuffers'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglCreatePbufferSurface'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglGetCurrentContext'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglTerminate'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglDestroySurface'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglGetCurrentSurface'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglBindAPI'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglInitialize'
collect2: error: ld returned 1 exit status
```
Please advise.https://gitlab.kitware.com/paraview/paraview/-/issues/20315CGNSSeriesReader Blocks.Available is broken in PV 5.8.0?2021-02-12T05:45:48-05:00Serge ToxopeusCGNSSeriesReader Blocks.Available is broken in PV 5.8.0?In PV 5.6, I could use the CGNSSeriesReader's Blocks.Available property to see which "blocks" are available in my CGNS file. However, doing the same in PV 5.8.0 shows an empty list. Am I doing something wrong, or is this option broken?
...In PV 5.6, I could use the CGNSSeriesReader's Blocks.Available property to see which "blocks" are available in my CGNS file. However, doing the same in PV 5.8.0 shows an empty list. Am I doing something wrong, or is this option broken?
Consider the following python script (mwe.py) together with the attached cgns file:
```
from paraview.simple import *
reader = CGNSSeriesReader(FileNames=["example_grid.cgns"],guiName="reader")
AvailableBlocks = reader.Blocks.Available
print AvailableBlocks
```
If I run this in PV 5.6, I get:
```
['/Families', '/Hierarchy/Base_Surface_elements/Zone_XMAX/Grid', '/Hierarchy/Base_Surface_elements/Zone_XMIN/Grid', '/Hierarchy/Base_Surface_elements/Zone_YMAX/Grid', '/Hierarchy/Base_Surface_elements/Zone_YMIN/Grid', '/Hierarchy/Base_Surface_elements/Zone_ZSYM/Grid', '/Hierarchy/Base_Volume_elements/Zone_Interior/Grid', '/Patches/Base_Surface_elements/Zone_XMAX', '/Patches/Base_Surface_elements/Zone_XMIN', '/Patches/Base_Surface_elements/Zone_YMAX', '/Patches/Base_Surface_elements/Zone_YMIN', '/Patches/Base_Surface_elements/Zone_ZSYM', '/Patches/Base_Volume_elements/Zone_Interior']
```
In PV 5.8.0, apart from display information, only an empty list is returned:
```
VisRTX 0.1.6, using devices:
0: Quadro P4000 (Total: 8.5 GB, Available: 7.6 GB)
[]
```
Any help is very much appreciated.
[mwe.py](/uploads/6f325b758ba58415d89d6c2a315c9539/mwe.py)
[example_grid.cgns](/uploads/be9f6cd934d37934791205cdbccb61ec/example_grid.cgns)https://gitlab.kitware.com/paraview/paraview/-/issues/20314v5.9-RC1 file is constantly re-opened and read when playing camera keyframes ...2020-11-20T08:43:47-05:00Jean M. Favrev5.9-RC1 file is constantly re-opened and read when playing camera keyframes animationThe issue raised https://discourse.paraview.org/t/xmlimagedatareader-keeps-re-executing-with-a-static-dataset-when-playing-keyframes-animation/5692 appears in v5.9-RC1. A reproducer is included on the discourse pageThe issue raised https://discourse.paraview.org/t/xmlimagedatareader-keeps-re-executing-with-a-static-dataset-when-playing-keyframes-animation/5692 appears in v5.9-RC1. A reproducer is included on the discourse page5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20313Custom Filenamesuffix (from list) in SaveData using pvbatch2021-04-20T17:12:04-04:00NiazCustom Filenamesuffix (from list) in SaveData using pvbatchPlease add TimestepValues (from a python list) as an option for Filenamesuffix in SavaData.
Original Discussion: https://discourse.paraview.org/t/custom-filenamesuffix-from-list-in-savedata-using-pvbatch/5707Please add TimestepValues (from a python list) as an option for Filenamesuffix in SavaData.
Original Discussion: https://discourse.paraview.org/t/custom-filenamesuffix-from-list-in-savedata-using-pvbatch/5707https://gitlab.kitware.com/paraview/paraview/-/issues/20312CI: testing gaps2024-03-07T20:47:17-05:00Ben BoeckelCI: testing gapsThere are a few gaps in testing right now:
- TBB on Windows. We should download the binaries the superbuild is using and extract them.
- Qt minimum version testing. This should be combined with a minimum GCC and Python test set on L...There are a few gaps in testing right now:
- TBB on Windows. We should download the binaries the superbuild is using and extract them.
- Qt minimum version testing. This should be combined with a minimum GCC and Python test set on Linux. We should be able to download Qt 5.12.x and Python 3.5 binaries and run them on a Fedora 33 instance or so.
Things to test yet:
- [x] ADIOS (!4804)
- [ ] RayTracing
- [ ] macOS + venv things (e.g., `matplotlib`)
- [ ] ASan
- [ ] UBSan
- [x] clang-tidy
See also #20304
Cc: @vbolea @utkarsh.ayachit5.13 (Summer 2024)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/20311Support plugins knowing where they live2021-01-19T15:23:10-05:00Ben BoeckelSupport plugins knowing where they liveSome plugins would like to know where they were loaded from so that they can access their own resources beside themselves. This is known to the `vtkPVPlugin` instance via its `GetFileName()` method (`nullptr` in static plugins). There sh...Some plugins would like to know where they were loaded from so that they can access their own resources beside themselves. This is known to the `vtkPVPlugin` instance via its `GetFileName()` method (`nullptr` in static plugins). There should be a new plugin interface type to call code with this location so that a plugin can know where it lives to access other resources beside itself.
`paraview_plugin_add_self_awareness(CLASS_NAME <classname> INTERFACES <var> SOURCES <var>)` (feel free to bikeshed the name)
This would basically just call `<classname>::SetPluginFileName(plugin->GetFileName())` (a static method). The plugin can then do whatever it wants with this information.
Cc: @john.tourtellott @utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20310Save data with Extract Surface with sidesets crashes2024-03-07T20:47:17-05:00W. Alan ScottSave data with Extract Surface with sidesets crashesWe have a crash when trying to save data that is derived from the Extract Surfaces filter for sidesets. Here is how to replicate:
* Master, Linux (and Mac), builtin server.
* Open can.exo. Advanced. Turn off all blocks. Turn on Sets...We have a crash when trying to save data that is derived from the Extract Surfaces filter for sidesets. Here is how to replicate:
* Master, Linux (and Mac), builtin server.
* Open can.exo. Advanced. Turn off all blocks. Turn on Sets/ Unnamed set ID: 4. Apply.
* Extract Surface. Apply.
* File/ Save Data. Exodus data. Take defaults. OK.
This will crash with the following:
```
Stack trace:
60 0x407baa /.../paraview() [0x407baa]
59 0x7f7d3964f545 __libc_start_main + 245
58 0x40780a /.../paraview() [0x40780a]
57 0x7f7d3727e364 QCoreApplication::exec() + 132
56 0x7f7d37275ada QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 298
55 0x7f7d372cd5df QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 95
54 0x7f7d26d0745c g_main_context_iteration + 44
53 0x7f7d26d073a8 /lib64/libglib-2.0.so.0(+0x4c3a8) [0x7f7d26d073a8]
52 0x7f7d26d07049 g_main_context_dispatch + 345
51 0x7f7d0a64c450 /.../plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0x86450) [0x7f7d0a64c450]
50 0x7f7d3761ba9b QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 171
49 0x7f7d37642205 QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 261
48 0x7f7d376408bb QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 1739
47 0x7f7d372774c8 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 280
46 0x7f7d38cab9c4 QApplication::notify(QObject*, QEvent*) + 628
45 0x7f7d38ca464c QApplicationPrivate::notify_helper(QObject*, QEvent*) + 156
44 0x7f7d38cfcaa1 /../bin/../lib/libQt5Widgets.so.5(+0x1b2aa1) [0x7f7d38cfcaa1]
43 0x7f7d38cfa3a2 /../bin/../lib/libQt5Widgets.so.5(+0x1b03a2) [0x7f7d38cfa3a2]
42 0x7f7d38caaf6f QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) + 447
41 0x7f7d372774c8 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 280
40 0x7f7d38cabf1f QApplication::notify(QObject*, QEvent*) + 1999
39 0x7f7d38ca464c QApplicationPrivate::notify_helper(QObject*, QEvent*) + 156
38 0x7f7d38e1997b QMenu::event(QEvent*) + 171
37 0x7f7d38ce03c8 QWidget::event(QEvent*) + 472
36 0x7f7d38e17783 QMenu::mouseReleaseEvent(QMouseEvent*) + 403
35 0x7f7d38e168cf /../bin/../lib/libQt5Widgets.so.5(+0x2cc8cf) [0x7f7d38e168cf]
34 0x7f7d38e0f83c /../bin/../lib/libQt5Widgets.so.5(+0x2c583c) [0x7f7d38e0f83c]
33 0x7f7d38ca096c QAction::activate(QAction::ActionEvent) + 204
32 0x7f7d38c9e4d2 QAction::triggered(bool) + 50
31 0x7f7d372a49da QMetaObject::activate(QObject*, int, int, void**) + 1898
30 0x7f7d392f25ef pqSaveDataReaction::saveActiveData() + 1423
29 0x7f7d392f1867 pqSaveDataReaction::saveActiveData(QString const&) + 1399
28 0x7f7d366998e1 vtkSMWriterProxy::UpdatePipeline() + 113
27 0x7f7d3653cf75 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 53
26 0x7f7d3653df4b vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 59
25 0x7f7d3653e112 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 242
24 0x7f7d340eddbd vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
23 0x7f7d340edb1e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1294
22 0x7f7d340ed3ed vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 1229
21 0x7f7d340ecd89 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 345
20 0x7f7d2e24f24e vtkPExodusIIWriterCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 446
19 0x7f7d340ecd89 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 345
18 0x7f7d2e25bb01 vtkExodusIIWriterCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 1121
17 0x7f7d340ecd89 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 345
16 0x7f7d2e6b81c0 vtkWriterCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 1920
15 0x7f7d2b5e367c vtkWriter::Write() + 44
14 0x7f7d32133fbd vtkStreamingDemandDrivenPipeline::UpdateWholeExtent() + 333
13 0x7f7d32134d4a vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 282
12 0x7f7d32105386 vtkDemandDrivenPipeline::UpdateData(int) + 134
11 0x7f7d32133989 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 953
10 0x7f7d321063c6 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 310
9 0x7f7d32100bb1 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 113
8 0x7f7d32103d47 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 55
7 0x7f7d32109b1e vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 62
6 0x7f7d1cd15fa6 vtkExodusIIWriter::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 310
5 0x7f7d1cd1efed vtkExodusIIWriter::WriteData() + 1197
4 0x7f7d1cf5d8f3 vtkPExodusIIWriter::CheckParameters() + 83
3 0x7f7d1cd1ea48 vtkExodusIIWriter::CheckParametersInternal(int, int) + 136
2 0x7f7d1cd1bb1a vtkExodusIIWriter::CreateDefaultMetadata() + 346
1 0x7f7d1cd131f7 vtkExodusIIWriter::CreateSetsMetadata(vtkModelMetadata*) + 1703
0 0x7f7d396633f0 /lib64/libc.so.6(+0x363f0) [0x7f7d396633f0]
```
@cory.quammen @utkarsh.ayachit Crash, thus probably needs to be fixed for 5.9.0.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20309Paraview 5.7.0 opacity problem2020-11-05T21:25:49-05:00Joaquin GonzalezParaview 5.7.0 opacity problemHello, I just entered here, this is my first post. I recently incorporated ubuntu 20.04 to windows 10 on my laptop because I am using liggghts in ubuntu, to visualize the simulations for my pregrade in Santiago,Chile. I use paraview 5.7....Hello, I just entered here, this is my first post. I recently incorporated ubuntu 20.04 to windows 10 on my laptop because I am using liggghts in ubuntu, to visualize the simulations for my pregrade in Santiago,Chile. I use paraview 5.7.0 and I have the same problem as #17553 and #18030.
When I change the opacity to less than 1 the object disappears, I have tried to use the command "VTK_USE_LEGACY_DEPTH_PEELING = 1 paraview" in terminal but apparently no results.
This is my output for
```bash
> glxinfo | grep OpenGL
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.8
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.8
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.8
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
```
I also have a nvidia GTX1650 video card (In windows I have downloaded the updated drivers and in Ubuntu select the one that said tested), which I don't know if it can generate this error when the object disappears. Finally I apologize for my English which is not my native language and I would really appreciate it if you could help me with this.
![Captura_de_pantalla_de_2020-11-04_13-50-11](/uploads/622f9933ff408e367a29567d845f9768/Captura_de_pantalla_de_2020-11-04_13-50-11.png)https://gitlab.kitware.com/paraview/paraview/-/issues/20308__file__ is not defined when ParaView python state file is loaded through ``F...2020-11-17T22:29:50-05:00Nima Tofighi__file__ is not defined when ParaView python state file is loaded through ``File->Load State...''When loading a python state file through ``File->Load State...'' the __file__ variable is not defined. This makes it impossible to use relative paths inside python state files when loaded in this manner. Loading the state file through Py...When loading a python state file through ``File->Load State...'' the __file__ variable is not defined. This makes it impossible to use relative paths inside python state files when loaded in this manner. Loading the state file through Python Shell via Run Script works as expected and __file__ points to the location of the state file.
Example file:
[placeholder.py](/uploads/67fb103c0b3a10dea251dc39b3f79b61/placeholder.py)
Error message:
Traceback (most recent call last):
File "<string>", line 14, in <module>
NameError: name '__file__' is not defined5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20307Release ParaView 5.9.0-RC12020-11-20T15:50:39-05:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.9.0-RC1# 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 `master` branch for **paraview**
```
git fetch origin
git checkout master
git merge --ff-only origin/master
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.9.0-RC1
echo 5.9.0-RC1 > version.txt
git commit -m 'Update version number to 5.9.0-RC1' version.txt
git tag -a -m 'ParaView 5.9.0-RC1' v5.9.0-RC1 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] `Do: merge`
- Update VTK's `paraview/release` branch
- [x] Change directory to VTK source
- [x] `git push origin <paraview-vtk-submodule-hash>:paraview/release`
- [x] Update kwrobot with the new `paraview/release` branch rules
- Integrate changes to `release` branch
- [x] Change directory to ParaView source. Stay on the `update-to-v5.9.0-RC1` branch.
- [x] `git config -f .gitmodules submodule.VTK.branch paraview/release`
- [x] `git commit -m "release: follow VTK's paraview/release branch" .gitmodules`
- [x] Merge new `release` branch into `master` using `-s ours`
- `git checkout master`
- `git merge --no-ff -s ours -m "Merge branch 'release'" update-to-v5.9.0-RC1`
- [x] `git push origin master update-to-v5.9.0-RC1:release`
- [x] Update kwrobot with the new `release` branch rules
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.9.0-RC1`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release: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
git checkout -b update-to-v5.9.0-RC1
```
- Update `CMakeLists.txt`
- [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-RC1" CACHE STRING "Force version to 5.9.0-RC1" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.9.0-RC1
- [x] ARG SUPERBUILD_TAG=v5.9.0-RC1
- [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-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 (`Do: test`)
- [x] Download the binaries that have been generated in the dashboard results. They will be deleted within 24 hours.
- [x] Remove explicit version forcing added in CMakeLists.txt, amend the commit, 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-RC1' v5.9.0-RC1 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.9.0-RC1:release`
# 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.9.0-RC1.app/`
- [ ] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.9.0-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.0-RC1`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.9.0-RC1`.
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/20306pvpython generated states have empty selections2021-03-24T08:41:21-04:00Andreas Naumannpvpython generated states have empty selectionsI generate a selection of (one) point using its id and store the generated state in a state file. With the GUI I get the correct state [extractSelState.pvsm](/uploads/5b19f23c70daf13fbae5ebf0a4e08e69/extractSelState.pvsm) with the select...I generate a selection of (one) point using its id and store the generated state in a state file. With the GUI I get the correct state [extractSelState.pvsm](/uploads/5b19f23c70daf13fbae5ebf0a4e08e69/extractSelState.pvsm) with the selection containing the point.
At the same time, I traced the selection and obtained the python trace [trace.py](/uploads/75cd05e445603ea35a3a6d623e47b34c/trace.py). If I add the line
```
SaveState('stateFromPython.pvsm')
```
to the end, I get the state file [stateFromPython.pvsm](/uploads/3c246f10f9ebf25b6857262191707997/stateFromPython.pvsm), which have an empty selection. Furthermore the selection does not show the query anymore.
The selection is correctly generated and contains the point. But it is missing in the state file. Is there a **simple** workaround for that? At the moment I use generate a python-programmable filter in the pvpython generated state file, which selects the points by hand.
My paraview and pvpython versions are 5.8.0, where pvpython used the python3.7-64bit backend.https://gitlab.kitware.com/paraview/paraview/-/issues/20305Mac/Python 3 issue with -m option2020-11-18T16:16:15-05:00Sebastien JourdainMac/Python 3 issue with -m optionRunning the following command should give you the following
```
$ pvbatch -m paraview.apps -l
Available applications:
divvy
flow
lite
visualizer
```
On Mac with ParaView-5.8.1-1539-ge438006c96.app we get
```
./pvbatch -m parav...Running the following command should give you the following
```
$ pvbatch -m paraview.apps -l
Available applications:
divvy
flow
lite
visualizer
```
On Mac with ParaView-5.8.1-1539-ge438006c96.app we get
```
./pvbatch -m paraview.apps -l
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Available applications:
```Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20304gitlab-ci: move vall to gitlab-ci2021-02-12T11:56:31-05:00Utkarsh Ayachitgitlab-ci: move vall to gitlab-ci* [ ] move linux-shared-debug+adios2+extdeps+gui+mpi+python3 on `vall` to gitlab-ci
* [ ] reinstall vall to become a standard gitlab-ci linux runner
cc: @ben.boeckel @cory.quammen* [ ] move linux-shared-debug+adios2+extdeps+gui+mpi+python3 on `vall` to gitlab-ci
* [ ] reinstall vall to become a standard gitlab-ci linux runner
cc: @ben.boeckel @cory.quammenVicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20303Please start building llvm and mesa libraries static2024-03-07T20:47:17-05:00W. Alan ScottPlease start building llvm and mesa libraries staticOne of the biggest sources currently for .so libraries on clusters is the llvm library suite. Please add the option, default on, to build llvm static within Paraview. This will primarily benefit Catalyst.
@patchett2002 OK to add LANL ...One of the biggest sources currently for .so libraries on clusters is the llvm library suite. Please add the option, default on, to build llvm static within Paraview. This will primarily benefit Catalyst.
@patchett2002 OK to add LANL to this request?
@jamauld5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20302zoom-to-box not centered correctly2024-03-07T20:47:17-05:00Utkarsh Ayachitzoom-to-box not centered correctlyzoom-to-box is not centering the box at the mouse down position.
see discussion here: paraview/paraview#20299zoom-to-box is not centering the box at the mouse down position.
see discussion here: paraview/paraview#202995.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20301Catalyst Trace is not capturing extractor options2020-11-17T21:12:20-05:00chart3388Catalyst Trace is not capturing extractor optionsWhen executing save extracts within a catalyst trace it is not capturing the extractor options. It is only providing a save screenshot call in the trace output and not the options for the extract object. So we cannot manipulate the sav...When executing save extracts within a catalyst trace it is not capturing the extractor options. It is only providing a save screenshot call in the trace output and not the options for the extract object. So we cannot manipulate the save frequency for instance.
`# save screenshot
SaveScreenshot('extracts/image_000008.png', renderView1, ImageResolution=[1212, 700])`
FYI @utkarsh.ayachit @bob.obara5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20300XML testing : Event activate in color button not caught2021-03-24T08:41:58-04:00Paul LafoixXML testing : Event activate in color button not caughtWhen recording a XML, the event that opens the color dialog is not recorded, and must be added manually in the XML:
`<pqevent object="pqClientMainWindow/propertiesDock/propertiesPanel/scrollArea/qt_scrollarea_viewport/scrollAreaWidgetCo...When recording a XML, the event that opens the color dialog is not recorded, and must be added manually in the XML:
`<pqevent object="pqClientMainWindow/propertiesDock/propertiesPanel/scrollArea/qt_scrollarea_viewport/scrollAreaWidgetContents/DisplayFrame/ProxyPanel/BorderColor/ColorButton" command="activate" arguments="" />`https://gitlab.kitware.com/paraview/paraview/-/issues/20299Zoom to box bug with linked views.2021-07-19T15:32:03-04:00Greg AbramZoom to box bug with linked views.When using Zoom-to-box on a view which is linked with another, zoom is not correctly applied on the second view.
Steps to reproduce:
* Open ParaView, Wavelet, Apply
* Create another view, show wavelet in it
* Right click on view 1, ...When using Zoom-to-box on a view which is linked with another, zoom is not correctly applied on the second view.
Steps to reproduce:
* Open ParaView, Wavelet, Apply
* Create another view, show wavelet in it
* Right click on view 1, link camera, click on view 2
* Click on zoom to box, select in view 1, release
* view 2 is not correctly zoomed and the camera are not correctly linked anymore.
Second part of the video shows the bug.
![pvbug](/uploads/ff78af08deebb82ef6a8223506bd9eeb/pvbug.mp4)