ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-11-01T20:42:34-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/19344Release ParaView 5.7.02019-11-01T20:42:34-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.7.0# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Assemble release notes into `Documentation/release/ParaView-5.7.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.7.0
echo 5.7.0 > version.txt
git commit -m 'Update version number to 5.7.0' version.txt
git tag -a -m 'ParaView 5.7.0' v5.7.0 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] Get positive review
- [x] `Do: merge`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0:release v5.7.0`
- Update documentation page
- [x] See `https://github.com/Kitware/paraview-docs/blob/gh-pages/versions.json`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.7.0`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.7/`
# 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.7.0
```
- 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.7.0" CACHE STRING "Force version to 5.7.0" 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/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.7.0
- [x] ARG SUPERBUILD_TAG=v5.7.0
- [x] Commit changes and push to GitLab
```
git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/Dockerfile
git commit -m "Update the default version to 5.7.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 (`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
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.7.0' v5.7.0 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0:release v5.7.0`
# 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.7.0.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.7.0.app/`
# Validating binaries
- For each binary, check
- [x] Getting started guide opens
- [x] Examples load and match thumbnails in dialog
- [x] Python
- [x] `import numpy`
- [x] Plugins are present and load properly
- [x] Text source LaTeX `$A^2$`
- [x] OSPRay raycasting and pathtracing runs
- [x] OptiX pathtracing runs
- [x] IndeX runs
- [x] 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.7/`)
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website
```
buildListing.sh
updateMD5sum.sh v5.7
```
- [x] Test download links on https://www.paraview.org/download
# Update documentation
- [x] Upload versioned documentation to `https://github.com/kitware/paraview-docs`
- [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] Update 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.ayachit5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19343Assert Crash: double click on the scalar bar2021-11-09T13:48:54-05:00Nicolas VuailleAssert Crash: double click on the scalar barThis is a regression (see https://gitlab.kitware.com/paraview/paraview/issues/18215).
This was experienced on 5.7-RC4 and on master (8decb43ef3193540ae829b714cccae009e999af4)
**Only in Debug build as only an assert fails.**
### Steps
...This is a regression (see https://gitlab.kitware.com/paraview/paraview/issues/18215).
This was experienced on 5.7-RC4 and on master (8decb43ef3193540ae829b714cccae009e999af4)
**Only in Debug build as only an assert fails.**
### Steps
* wavelet, apply
* color by RTData
* double click on scalar bar
-> crash
### Trace
```
paraview: /home/nicolas/ParaView/paraview/ParaViewCore/ServerManager/Rendering/vtkSMScalarBarWidgetRepresentationProxy.cxx:146: void vtkSMScalarBarWidgetRepresentationProxy::BeginTrackingPropertiesForTrace(): Assertion `this->TraceItem == NULL' failed.
Loguru caught a signal: SIGABRT
Stack trace:
34 0x55e84ff39c5e ./bin/paraview(+0x7c5e) [0x55e84ff39c5e]
33 0x7fdd404efee3 __libc_start_main + 243
32 0x55e84ff400f8 ./bin/paraview(+0xe0f8) [0x55e84ff400f8]
31 0x7fdd3f284326 QCoreApplication::exec() + 150
30 0x7fdd3f27c4ec QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 300
29 0x7fdd3f2d5a03 QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 99
28 0x7fdd33b77201 g_main_context_iteration + 49
27 0x7fdd33b771c1 /usr/lib/libglib-2.0.so.0(+0x6c1c1) [0x7fdd33b771c1]
26 0x7fdd33b753ae g_main_context_dispatch + 638
25 0x7fdd28bf412c /usr/lib/libQt5XcbQpa.so.5(+0x6c12c) [0x7fdd28bf412c]
24 0x7fdd3f5f5afc QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 188
23 0x7fdd3f61b49b QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 635
22 0x7fdd3f619b45 QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 1573
21 0x7fdd3f27d9c2 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 386
20 0x7fdd3fc45e11 QApplication::notify(QObject*, QEvent*) + 817
19 0x7fdd3fc3c4f5 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 133
18 0x7fdd3e6c8f30 QVTKOpenGLWindow::event(QEvent*) + 96
17 0x7fdd3e6c9f4b QVTKRenderWindowAdapter::handleEvent(QEvent*) + 123
16 0x7fdd3e6c1d30 QVTKInteractorAdapter::ProcessEvent(QEvent*, vtkRenderWindowInteractor*) + 928
15 0x7fdd368e4da3 vtkObject::InvokeEvent(unsigned long, void*) + 61
14 0x7fdd368e463b /home/nicolas/ParaView/paraview-build/bin/../lib64/libvtkCommonCore-pv5.7.so.1(+0x7bb63b) [0x7fdd368e463b]
13 0x7fdd366c5819 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 71
12 0x7fdd3c93046f vtkAbstractWidget::ProcessEventsHandler(vtkObject*, unsigned long, void*, void*) + 553
11 0x7fdd3caeba71 vtkWidgetCallbackMapper::InvokeCallback(unsigned long) + 157
10 0x7fdd3c9629b5 vtkBorderWidget::SelectAction(vtkAbstractWidget*) + 903
9 0x7fdd368e4da3 vtkObject::InvokeEvent(unsigned long, void*) + 61
8 0x7fdd368e4887 /home/nicolas/ParaView/paraview-build/bin/../lib64/libvtkCommonCore-pv5.7.so.1(+0x7bb887) [0x7fdd368e4887]
7 0x7fdd3e49e4e0 /home/nicolas/ParaView/paraview-build/bin/../lib64/libvtkPVServerManagerRendering-pv5.7.so.1(+0xd04e0) [0x7fdd3e49e4e0]
6 0x7fdd3e4c3feb vtkSMScalarBarWidgetRepresentationProxy::ExecuteEvent(unsigned long) + 51
5 0x7fdd3e4c4239 vtkSMScalarBarWidgetRepresentationProxy::BeginTrackingPropertiesForTrace() + 77
4 0x7fdd404fc026 /usr/lib/libc.so.6(+0x33026) [0x7fdd404fc026]
3 0x7fdd404ee727 /usr/lib/libc.so.6(+0x25727) [0x7fdd404ee727]
2 0x7fdd404ee851 abort + 293
1 0x7fdd40503755 gsignal + 325
0 0x7fdd405037e0 /usr/lib/libc.so.6(+0x3a7e0) [0x7fdd405037e0]
( 10.396s) [paraview ] :0 FATL| Signal: SIGABRT
[1] 546436 abort (core dumped) ./bin/paraview
```
### System info
gcc 9.1;
cmake 3.15.3;
qt 5.13.15.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19340Custom filters spread like viruses2019-11-19T20:09:51-05:00W. Alan ScottCustom filters spread like virusesParaView seems to append all custom filters to any statefile that is saved (even custom filters that are used), and further stores any custom filter, that is read from a statefile, in the local config.
Full writeup, with .pvsm, is here:...ParaView seems to append all custom filters to any statefile that is saved (even custom filters that are used), and further stores any custom filter, that is read from a statefile, in the local config.
Full writeup, with .pvsm, is here: https://discourse.paraview.org/t/custom-filters-spread-like-viruses/2597
OK to slip to 5.9.5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19337Opening case and pvsm from command line2019-09-19T07:52:59-04:00Maarten MOSTERTOpening case and pvsm from command lineHello everyone,
I am a bit new and try to open ParaView with the following command line
paraFoam -case /home/myhomedir/OpenFOAM/myhomedir-7/run/propeller -state=/home/myhomedir/OpenFOAM/myhomedir-7/run/basicMesh.pvsm
I tried various va...Hello everyone,
I am a bit new and try to open ParaView with the following command line
paraFoam -case /home/myhomedir/OpenFOAM/myhomedir-7/run/propeller -state=/home/myhomedir/OpenFOAM/myhomedir-7/run/basicMesh.pvsm
I tried various variants and understood that the -state part could be omitted but nothing really works.
Thank you for your help
Maarten,https://gitlab.kitware.com/paraview/paraview/-/issues/19336Bad QT UI rescaling on Win10, Intel graphics, PV 5.7RC2 or RC42019-11-13T13:56:42-05:00Aron HelserBad QT UI rescaling on Win10, Intel graphics, PV 5.7RC2 or RC4Just had a driver update on my Win10 laptop, with:
- Intel(R) UHD Graphics 630
- OpenGL version: 3.2.0 - Build 26.20.100.6999 (this is the Intel driver version)
and when I choose a field for 'Coloring', the gui scales to double-size
![i...Just had a driver update on my Win10 laptop, with:
- Intel(R) UHD Graphics 630
- OpenGL version: 3.2.0 - Build 26.20.100.6999 (this is the Intel driver version)
and when I choose a field for 'Coloring', the gui scales to double-size
![image](/uploads/cdb7c42b397c679f5daf549f419199bf/image.png)
i.e. Choose a Sphere source, Apply, under Display.. Coloring, choose Normals - and the screenshot results.
I have a high-dpi primary display, and an a normal external monitor attached. I'm pretty sure this started with the update to the Intel graphics drivers.
This may be a FYI more than anything - if I force PV to use my Nvidia card instead, the issue is gone.https://gitlab.kitware.com/paraview/paraview/-/issues/19335Setting of background image in render view is not traced with Python tracing2020-05-22T14:10:02-04:00Cory Quammencory.quammen@kitware.comSetting of background image in render view is not traced with Python tracingOriginal discussion here:
https://discourse.paraview.org/t/programmatically-set-background-image/2574Original discussion here:
https://discourse.paraview.org/t/programmatically-set-background-image/2574Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/19334Make ParaView buildable with WSL on windows and document the prodecure2019-09-30T21:48:31-04:00William YoungMake ParaView buildable with WSL on windows and document the prodecureParaView does not seem to build on WSL because of xmlpatterns not working.
Please make ParaView buildable on WSL and if it is already, document the procedure.
Initial bug report was as follows :
> Paraview cmake error with the ...ParaView does not seem to build on WSL because of xmlpatterns not working.
Please make ParaView buildable on WSL and if it is already, document the procedure.
Initial bug report was as follows :
> Paraview cmake error with the "AcceleratedAlgorithms_doc" dependency
>
> Hi, I am trying to make a build of open source Paraview using the ubuntu bash terminal, my machine runs on Windows 10. I thought I had downloaded all of the required dependencies, as per this documentation: https://www.paraview.org/Wiki/ParaView:Build_And_Install#Download_And_Install_CMake
> but at the "Build Paraview" part of the documentation, I run into this error once I get to the part of the cmake where the AcceleratedAlgorithms_doc is scanned:
>
> `CMake Error at /mnt/c/Users/mmmto/OneDrive/Documents/GitHub/ParaView/CMake/ParaViewClient.cmake:577 (message):
> Failed to convert servermanager XML: xmlpatterns: could not exec
> '/usr/lib/qt5/bin/xmlpatterns': No such file or directory`
>
> I know that xmlpatterns exists on my machine, but it exists in `/usr/lib`, and not `/usr/lib/qt5/bin/`.
>
> Any help would be appreciated.https://gitlab.kitware.com/paraview/paraview/-/issues/19333ParaView hangs when reading big CGNS SIL2020-09-30T02:59:13-04:00Mickael PHILITParaView hangs when reading big CGNS SILWhen opening a CGNS file with around 400 CGNS zones, calls to ClearSelections or SetSelections of the SIL class are very slow to process and ends up with the interface hanging.
Initialization of the SIL status is not fast enough.When opening a CGNS file with around 400 CGNS zones, calls to ClearSelections or SetSelections of the SIL class are very slow to process and ends up with the interface hanging.
Initialization of the SIL status is not fast enough.https://gitlab.kitware.com/paraview/paraview/-/issues/19332Modify ghost cells generator filter to also work with topologically regular g...2021-09-08T13:48:06-04:00Andrew BauerModify ghost cells generator filter to also work with topologically regular gridsThis is useful for loading silo files through the VisIt bridge where they come in as a composite dataset of rectilinear grids. I can convert them to a single rectilinear grid using a programmable filter but in parallel I don't have ghost...This is useful for loading silo files through the VisIt bridge where they come in as a composite dataset of rectilinear grids. I can convert them to a single rectilinear grid using a programmable filter but in parallel I don't have ghost information available for filters that need them.
This could also be useful for Catalyst for simulation codes that produce topologically regular grids.
I'm marking this as a 5.8 milestone as this is a semi-urgent need for some users. Please let me know if this doesn't seem reasonable for the 5.8 release since I'm not sure how soon our funding will be in place.5.10 (Fall 2021)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19331Write htg as phtg not working on master branch2020-01-14T11:06:26-05:00Ethan StamWrite htg as phtg not working on master branchTested with master build, MacOS
@sebastien.jourdain @yohann.bearzi I am unable to write .phtg's with the current paraview master branch.
To reproduce:
* Open paraview
* Sources -> Hyper Tree Grid (random) -> Apply
* File -> Save as ...Tested with master build, MacOS
@sebastien.jourdain @yohann.bearzi I am unable to write .phtg's with the current paraview master branch.
To reproduce:
* Open paraview
* Sources -> Hyper Tree Grid (random) -> Apply
* File -> Save as phtg with default settings
I get the error:
```
( 20.623s) [paraview ]vtkDemandDrivenPipeline:813 ERR| vtkPVCompositeDataPipeline (0x7f84e25c7db0): Input for connection index 0 on input port index 0 for algorithm vtkPassSelectedArrays(0x7f84e208be60) is of type vtkHyperTreeGrid, but a vtkDataSet is required.
```
I added this to vtkPassArrays. It seemed to work, but I'm not sure if it's the right fix...
```c++
info->Append(vtkAlgorithm::INPUT_REQUIRED_DATA_TYPE(), "vtkHyperTreeGrid");
```5.8 (Winter 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19330HTG serial write as vtm not working2020-06-05T11:38:58-04:00Ethan StamHTG serial write as vtm not workingTested on MacOS with 5.7.0-RC4
I can't write out Hyper Tree Grid's as a vtm with the current RC.
To reproduce:
* Open ParaView
* Sources -> Hyper Tree Grid (Random) -> Apply
* File -> Save
* Choose vtm as the format and save with t...Tested on MacOS with 5.7.0-RC4
I can't write out Hyper Tree Grid's as a vtm with the current RC.
To reproduce:
* Open ParaView
* Sources -> Hyper Tree Grid (Random) -> Apply
* File -> Save
* Choose vtm as the format and save with the default settings
I get the following error, and nothing is written:
```
ERROR: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVCompositeDataPipeline (0x6080009a2f40): Input for connection index 0 on input port index 0 for algorithm vtkXMLPMultiBlockDataWriter(0x7f971f9164e0) is of type vtkHyperTreeGrid, but a vtkMultiBlockDataSet is required.
```
@sebastien.jourdain @patchett20025.8 (Winter 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19329Color under opacity curve in not updated properly2019-11-07T05:28:57-05:00Michael MiglioreColor under opacity curve in not updated properlyTested on current master (commit 3ac4bc1ddd)
- Create a Wavelet
- Open Color Map Editor
- Change Diverging to HSV
- Color is not updated
- Moving the mouse cursor to the curve trigger the update
![2019-09-17-095627_402x592](/uploads/6b...Tested on current master (commit 3ac4bc1ddd)
- Create a Wavelet
- Open Color Map Editor
- Change Diverging to HSV
- Color is not updated
- Moving the mouse cursor to the curve trigger the update
![2019-09-17-095627_402x592](/uploads/6b4c07810a715417538c46582958d955/2019-09-17-095627_402x592.png)Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19328incorrect cache when playing animation2020-10-27T18:32:50-04:00Utkarsh Ayachitincorrect cache when playing animationWhile rare, this highlights a peculiar case when animation cache my not be cleared when needed.
* Ensure animation caching is enabled in the **Settings** dialog
* Sphere, Apply
* Hit ![image](/uploads/63c8c43fc7c49b5559ef01ac8f8998c8/im...While rare, this highlights a peculiar case when animation cache my not be cleared when needed.
* Ensure animation caching is enabled in the **Settings** dialog
* Sphere, Apply
* Hit ![image](/uploads/63c8c43fc7c49b5559ef01ac8f8998c8/image.png) -- time 0 is cached
* Hit ![image](/uploads/0446fe4002198f0a5835a3465584b7d9/image.png) -- time 0.11111 is cached
* Animation View, add track for Sphere, Start Theta -- default values
* Hit ![image](/uploads/63c8c43fc7c49b5559ef01ac8f8998c8/image.png) -- time 0, start theta is 0
* Hit ![image](/uploads/0446fe4002198f0a5835a3465584b7d9/image.png) -- time 0.11111, start theta is not 0, but the rendering shows full sphere i.e. obsolete values from cache are being used!
* Hit ![image](/uploads/0446fe4002198f0a5835a3465584b7d9/image.png) on more time and correct frame is rendered for time 0.22222, however going back to frame 1, you'll get bad sphere.https://gitlab.kitware.com/paraview/paraview/-/issues/19327FXAA has no effect on Eye dome lighting2021-12-23T13:05:10-05:00Jonathan BorduasFXAA has no effect on Eye dome lightingDear users/devs of the Eye Dome Lighting plugin: @patchett2002 @ethan.stam @demarle @utkarsh.ayachit,
The FXAA seems to have no effects on the hard edge anti-aliasing of an Eye Dome Lighting View port.
When zooming out, the aliasing e...Dear users/devs of the Eye Dome Lighting plugin: @patchett2002 @ethan.stam @demarle @utkarsh.ayachit,
The FXAA seems to have no effects on the hard edge anti-aliasing of an Eye Dome Lighting View port.
When zooming out, the aliasing effects can be quite important (opaque purple surface on transparent grey surface).
![image](/uploads/1748e72854fca17869da94d9f3f57aa9/image.png)
The same setup using a screenshot export in 4K resolution creates a good result:
![image](/uploads/137047f49c0b9094cb46c954c4540c82/image.png)
If both surface are opaque, the anti-aliasing is acceptable:
![image](/uploads/8de47147b485f0aaca8e798c5a6c9f95/image.png)
Is it normal that a opaque/transparent combination increase drastically the aliasing effects ?
Is there a setting to reduce the aliasing ?
I am testing on ParaView-latest-MPI-Windows-Python3.7-msvc2015-64bit.exeSankhesh JhaveriSankhesh Jhaverihttps://gitlab.kitware.com/paraview/paraview/-/issues/19326Release ParaView 5.7.0-RC42019-09-16T13:24:31-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.7.0-RC4# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Assemble release notes into `Documentation/release/ParaView-5.7.0`.
- [ ] 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.7.0-RC4
echo 5.7.0-RC4 > version.txt
git commit -m 'Update version number to 5.7.0-RC4' version.txt
git tag -a -m 'ParaView 5.7.0-RC4' v5.7.0-RC4 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] Get positive review
- [x] `Do: merge`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0-RC4:release v5.7.0-RC4`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.7.0-RC4`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.7/`
# 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.7.0-RC4
```
- 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.7.0-RC4" CACHE STRING "Force version to 5.7.0-RC4" 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/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.7.0-RC4
- [x] ARG SUPERBUILD_TAG=v5.7.0-RC4
- [x] `git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/Dockerfile`
- [x] `git commit -m "Update the default version to 5.7.0-RC4"`
- [x] `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
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.7.0-RC4' v5.7.0-RC4 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0-RC4:release v5.7.0-RC4`
# Validating binaries
- For each binary, check
- [ ] Getting started guide opens
- [ ] Examples load and match thumbnails in dialog
- [ ] Python
- [ ] `import numpy`
- [ ] Plugins are present and load properly
- [ ] Text source LaTeX `$A^2$`
- [ ] OSPRay
- [ ] IndeX runs
- [ ] AutoMPI
- Binary checklist
- [x] macOS
- [x] Linux
- [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.7/`)
- [x] Ask @chuck.atkins to sign macOS binary
- [ ] Regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt`
```
buildListing.sh
updateMD5sum.sh v5.7
```
- [x] Test download links on https://www.paraview.org/download
# 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.7 (Summer 2019)https://gitlab.kitware.com/paraview/paraview/-/issues/19325SaveScreenshot scalar bar too big even for high resolution2020-02-19T14:06:09-05:00Dan LipsaSaveScreenshot scalar bar too big even for high resolutionI see this on the master branch.
In Python scripting I use
SaveScreenshot(imageName) to get a 300 x 300 image. The scalar bar is big because probably there is a lower limit on how many pixels fonts use.
![low_warpx](/uploads/eda4005ae9...I see this on the master branch.
In Python scripting I use
SaveScreenshot(imageName) to get a 300 x 300 image. The scalar bar is big because probably there is a lower limit on how many pixels fonts use.
![low_warpx](/uploads/eda4005ae9c1bd81f73b772949cdaaf3/low_warpx.png)
If I use
SaveScreenshot(imageName, ImageResolution=(1024, 1024))
I get the following image. The fonts have a lot more pixels to work with, but the scalar bar has the same proportional size as before. I do use a reset camera in my script.
![high_warpx](/uploads/1c0d29e687cd6a4f0f68cad05b066b20/high_warpx.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19324CMake Configuration Step of PV 5.7.0-RC3 fails2019-09-17T00:09:14-04:00Max ZeyenCMake Configuration Step of PV 5.7.0-RC3 failsThe VTK associated with PV 5.7.0-RC3 gives CMake errors during the configuration step. (Unknown CMake command check_symbol_exists in VTK/Common/Core/CMakeLists.txt:442).
Compared to VTK master, there is an `include(CheckSymbolExists)` mi...The VTK associated with PV 5.7.0-RC3 gives CMake errors during the configuration step. (Unknown CMake command check_symbol_exists in VTK/Common/Core/CMakeLists.txt:442).
Compared to VTK master, there is an `include(CheckSymbolExists)` missing before the first `check_symbol_exists` call.https://gitlab.kitware.com/paraview/paraview/-/issues/19323Have edit boxes select all text when they grab focus2020-03-23T21:56:12-04:00W. Alan ScottHave edit boxes select all text when they grab focusPlease have edit boxes select all text when they grab focus. This is in response to a user complaint.
Here are some details on how to replicate:
* If you bring up a FastUniformGrid, then clip it, then rotate the clip around, you get e...Please have edit boxes select all text when they grab focus. This is in response to a user complaint.
Here are some details on how to replicate:
* If you bring up a FastUniformGrid, then clip it, then rotate the clip around, you get edit boxes for the normal. These are filled in with half a dozen numbers, but if you click on them, they expand to around two dozen numbers. Further, your cursor is now in the middle of the number, which is useless.
* Next, if you click in the Normal X, to change it to 1.0, you get as I describe above. Note that you now have to arrow the cursor to the right, and then delete everything – or, <ctrl>a, then delete everything.5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19322Temporal cache crash in 5.7.0-RC32020-06-09T20:24:54-04:00Tim BiedertTemporal cache crash in 5.7.0-RC3Reproducer: ParaView-5.7.0-RC3-Windows-Python3.7-msvc2015-64bit from website
**Sphere source -> Apply -> Temporal cache -> Apply -> Crash**
Stack trace (for this release build) seems like a nullptr access in vtkFiltersHybrid-pv5.7.dll.Reproducer: ParaView-5.7.0-RC3-Windows-Python3.7-msvc2015-64bit from website
**Sphere source -> Apply -> Temporal cache -> Apply -> Crash**
Stack trace (for this release build) seems like a nullptr access in vtkFiltersHybrid-pv5.7.dll.https://gitlab.kitware.com/paraview/paraview/-/issues/19321some new variables in vtkSpreadSheetView class should be protected, not private2019-09-17T03:55:17-04:00Cornelis Bockemühlsome new variables in vtkSpreadSheetView class should be protected, not privateIn order to derive a view from the vtkSpreadSheetView, some internal variables need to be protected and not private:
CRMICallbackTag
PRMICallbackTag
Identifier
If they are private, too much of the class needs to be completely duplicated!In order to derive a view from the vtkSpreadSheetView, some internal variables need to be protected and not private:
CRMICallbackTag
PRMICallbackTag
Identifier
If they are private, too much of the class needs to be completely duplicated!