ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-10-24T11:18:13-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/21546Servers in PVbatch are still running after "File not found" error2023-10-24T11:18:13-04:00Eloise BServers in PVbatch are still running after "File not found" errorHello,
I begin to use PVbatch in parallel and I found a weird behavior:
When I launch ```mpirun -n 4 pvbatch file_not_found.py``` with a wrong path in argument, I can see the "file not found" error as expected (because there is no file...Hello,
I begin to use PVbatch in parallel and I found a weird behavior:
When I launch ```mpirun -n 4 pvbatch file_not_found.py``` with a wrong path in argument, I can see the "file not found" error as expected (because there is no file with that name) but the servers are still running and waiting for something.
I thought they would end (even with an error) as they end when the script succeed.
Is that normal ?
I checked this with a master version of paraview from last week (I don't have the commit now sorry).
Regards
Eloïsehttps://gitlab.kitware.com/paraview/paraview/-/issues/21544Broken volume rendering on MacOS Monterey 12.1 M1 Max2023-06-07T22:12:31-04:00Linnea PalmstromBroken volume rendering on MacOS Monterey 12.1 M1 MaxTo reproduce, load fast uniform grid source and apply a threshold from -10 to 10 (the default settings) in ParaView 5.11.0 RC1. Then switch to a volume representation. It does not appear to clear the last frames as you move the camera an...To reproduce, load fast uniform grid source and apply a threshold from -10 to 10 (the default settings) in ParaView 5.11.0 RC1. Then switch to a volume representation. It does not appear to clear the last frames as you move the camera and the background color changes to black.
@patchett2002
@ethan.stam
@maxwelljackson002
![Screen_Shot_2022-09-08_at_1.17.53_PM](/uploads/a5029a0e6a545398f1972683ce707992/Screen_Shot_2022-09-08_at_1.17.53_PM.png)5.12 (Winter 2023)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21543Clip widget disappears when typing in search2023-01-26T10:56:49-05:00Maxwell JacksonClip widget disappears when typing in search@spiros.tsalikis @ethan.stam @patchett2002 In Paraview 5.11.0-RC1, the clip widget disappears when typing in the search box in the properties. This is on MacOS and has a different response on Windows
- Sources -> Wavelet, click apply
- ...@spiros.tsalikis @ethan.stam @patchett2002 In Paraview 5.11.0-RC1, the clip widget disappears when typing in the search box in the properties. This is on MacOS and has a different response on Windows
- Sources -> Wavelet, click apply
- Add clip, click apply
- In the properties window, click search, start typing "pl"
- When adding a third letter such as "a", the widget disappears
This issue also occurs with the slice filter, but with two lettersAron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/215425.11-RC1 memory leak in ParaView-Catalyst2022-11-07T11:03:58-05:00Alexandre Minot5.11-RC1 memory leak in ParaView-CatalystHello,
When I run my simulation code in ASAN mode with ParaView-Catalyst, I get the following error:
```
==24848==ERROR: AddressSanitizer: alloc-dealloc-mismatch (operator new [] vs free) on 0x611001035500
0x611001035500 is located 0 b...Hello,
When I run my simulation code in ASAN mode with ParaView-Catalyst, I get the following error:
```
==24848==ERROR: AddressSanitizer: alloc-dealloc-mismatch (operator new [] vs free) on 0x611001035500
0x611001035500 is located 0 bytes inside of 236-byte region [0x611001035500,0x6110010355ec)
allocated by thread T0 here:
#0 0x1f3ef08 in operator new[](unsigned long) <LLVM_ROOT>/projects/compiler-rt/lib/asan/asan_new_delete.cc:95
#1 0x7f46d4b6b715 in vtkPythonInterpreter::SetupPythonPrefix() (<PARAVIEW_ROOT>/lib64/catalyst/libcatalyst-paraview.so+0x45c7715)
SUMMARY: AddressSanitizer: alloc-dealloc-mismatch
```
I built ParaView in ASAN mode too, but it did not give me more info. I tried looking in the code but did not find this mismatch. I'm on the v5.11-RC1 tag.
Thanks, Alex5.11 (Spring 2022)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/215415.11-RC1 CGNS file load crashes ParaView2022-10-27T11:48:05-04:00Menno Deij - van Rijswijk5.11-RC1 CGNS file load crashes ParaViewIf you select `Base_Surface_elements` in the attached CGNS file, ParaView crashes on loading the file.
As far as I'm concerned this is a blocker for 5.11 release. I'll try to find out what is going on.
@Mick7 @mwestphal
[flatplate64x...If you select `Base_Surface_elements` in the attached CGNS file, ParaView crashes on loading the file.
As far as I'm concerned this is a blocker for 5.11 release. I'll try to find out what is going on.
@Mick7 @mwestphal
[flatplate64x64_ERROR.cgns](/uploads/0b5e06061ad8a8fab9a0ecf21626e915/flatplate64x64_ERROR.cgns)5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/215405.11-RC1: Elevation range not correct2022-09-08T03:19:42-04:00Menno Deij - van Rijswijk5.11-RC1: Elevation range not correctIn the attached data and state file, the elevation is computed along the Y-axis. The range in elevation values should be `[0.198755 .. 0.2]` but the data reports `[0..1]` and so does the color bar.
@mwestphal
[elevation.zip](/uploads/...In the attached data and state file, the elevation is computed along the Y-axis. The range in elevation values should be `[0.198755 .. 0.2]` but the data reports `[0..1]` and so does the color bar.
@mwestphal
[elevation.zip](/uploads/25cde13855519c8f98508c1e31e85419/elevation.zip)
![image](/uploads/e3483a161bc74f22e13e09b35adfdc80/image.png)5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21539Number pad no longer works2023-01-30T21:49:18-05:00W. Alan ScottNumber pad no longer worksThe number pad worked in ParaView 5.10.1. It no longer works. Here is how to replicate:
* Linux, 5.10.1, builtin server.
* can.exo. Apply.
* Transform filter. Place cursor focus in Translate X box. Type 123. It shows up in the Tran...The number pad worked in ParaView 5.10.1. It no longer works. Here is how to replicate:
* Linux, 5.10.1, builtin server.
* can.exo. Apply.
* Transform filter. Place cursor focus in Translate X box. Type 123. It shows up in the Translate X box.
* Linux, 5.11.0-RC1, builtin server.
* can.exo. Apply.
* Transform filter. Place cursor focus in Translate X box. Type 123. It DOES NOT show up in the Translate X box.
@cory.quammenhttps://gitlab.kitware.com/paraview/paraview/-/issues/21538Is it possible to make the contour labeling automated especially using macros?2022-09-15T21:58:17-04:00Leila SaberiIs it possible to make the contour labeling automated especially using macros?Hi,
I am using Paraview 5.10.1 to create contours and I would like to label my contours for multiple figures and would like to make it automated. Currently I created a macro script that does everything up to labeling contours: it clips ...Hi,
I am using Paraview 5.10.1 to create contours and I would like to label my contours for multiple figures and would like to make it automated. Currently I created a macro script that does everything up to labeling contours: it clips the map, transform it, converts to points, create the contour, but does not label the contours! And since I have to run this for over 100 cases, I cannot label them manually! Could you please let me know if this feature exist in Paraview 5.10.1 or is there a way I can include it in my macro script?
Thank youhttps://gitlab.kitware.com/paraview/paraview/-/issues/21535Superquadric Crashes from Clip2022-09-27T16:10:52-04:00Maxwell JacksonSuperquadric Crashes from Clip@ethan.stam @patchett2002 @cory.quammen
In Paraview 5.1.0-RC1 on MacOS and Windows, the Superquadric crashes when clip is applied
- Sources -> Alphabetical -> Superquadric
- Clip, default values -> Click Apply@ethan.stam @patchett2002 @cory.quammen
In Paraview 5.1.0-RC1 on MacOS and Windows, the Superquadric crashes when clip is applied
- Sources -> Alphabetical -> Superquadric
- Clip, default values -> Click Apply5.11 (Spring 2022)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21534Multiple ParaView help items lead to non-existant pages in 5.11.0-RC12022-09-27T16:04:13-04:00Ethan StamMultiple ParaView help items lead to non-existant pages in 5.11.0-RC1In 5.11.0-RC1, when you go to Help -> ParaView Classroom tutorials or Help -> ParaView Self Directed tutorial, you are taken to a page that does not exist.
Also the ParaView guide, and the Readers, Writers, and Sources reference is miss...In 5.11.0-RC1, when you go to Help -> ParaView Classroom tutorials or Help -> ParaView Self Directed tutorial, you are taken to a page that does not exist.
Also the ParaView guide, and the Readers, Writers, and Sources reference is missing.
Setting to required as it seems like an easy fix.https://gitlab.kitware.com/paraview/paraview/-/issues/21533Crash on reset session when Looping2022-09-27T16:25:16-04:00Maxwell JacksonCrash on reset session when Looping@ethan.stam @patchett2002 @cory.quammen
In Paraview 5.11.0-RC1, when looping a visualization, pressing the reset button without pausing the loop causes a crash, MacOS 10.15.7 and Windows 10
- Help - Example Visualizations
- Use "Exod...@ethan.stam @patchett2002 @cory.quammen
In Paraview 5.11.0-RC1, when looping a visualization, pressing the reset button without pausing the loop causes a crash, MacOS 10.15.7 and Windows 10
- Help - Example Visualizations
- Use "Exodus II with time steps, Clip filter" example
- Click loop button
- Click reverse play button
- Let visualization play and don’t click pause
- Click reset button (Crash happens here)5.11 (Spring 2022)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21529v5.11.0-RC1 fail to compile on Cray login node2022-10-13T15:00:04-04:00Jean M. Favrev5.11.0-RC1 fail to compile on Cray login node
```
cd /scratch/e1000/jfavre/ParaView/ParaView-v5.11.0-RC1Build/Remoting/ServerManager && ../../bin/vtkprotoc-pv5.11 --cpp_out dllexport_decl=VTKREMOTINGSERVERMANAGER_EXPORT:/scratch/e1000/jfavre/ParaView/ParaView-v5.11.0-RC1Build/Remot...
```
cd /scratch/e1000/jfavre/ParaView/ParaView-v5.11.0-RC1Build/Remoting/ServerManager && ../../bin/vtkprotoc-pv5.11 --cpp_out dllexport_decl=VTKREMOTINGSERVERMANAGER_EXPORT:/scratch/e1000/jfavre/ParaView/ParaView-v5.11.0-RC1Build/Remoting/ServerManager -I /scratch/e1000/jfavre/ParaView/ParaView-v5.11.0-RC1/Remoting/ServerManager /scratch/e1000/jfavre/ParaView/ParaView-v5.11.0-RC1/Remoting/ServerManager/vtkPVMessage.proto
terminate called after throwing an instance of 'std::system_error'
what(): Unknown error -1
make[2]: *** [Remoting/ServerManager/CMakeFiles/vtkPVMessage_protobuf_compile.dir/build.make:80: Remoting/ServerManager/vtkPVMessage.pb.h] Aborted
make[2]: Leaving directory '/scratch/e1000/jfavre/ParaView/ParaView-v5.11.0-RC1Build'
make[1]: *** [CMakeFiles/Makefile2:35626: Remoting/ServerManager/CMakeFiles/vtkPVMessage_protobuf_compile.dir/all] Error 2
make[1]: Leaving directory '/scratch/e1000/jfavre/ParaView/ParaView-v5.11.0-RC1Build'
make: *** [Makefile:158: all] Error 2
```
/opt/cray/pe/craype/2.7.17/bin/CC
/opt/cray/pe/gcc/10.3.0/bin/gcc
Any advice on how to fix this is welcome.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21527Text Annotation not in Filter Menu2022-09-02T10:45:56-04:00Phil SmithText Annotation not in Filter MenuThe Text Annotation is not in the filter menu. It can be selected via the search tool, so I know it is implemented, but it is just not in the menu. I looked in the alphabetical menu as well as the Annotation menu
Tested on Mac OS Monter...The Text Annotation is not in the filter menu. It can be selected via the search tool, so I know it is implemented, but it is just not in the menu. I looked in the alphabetical menu as well as the Annotation menu
Tested on Mac OS Monterey x86 5.11.0-RC1 master. The can.ex2 was used.https://gitlab.kitware.com/paraview/paraview/-/issues/21526v5.11.0-RC1 No target "VTK::sqlitebin" ERROR2022-11-01T22:13:25-04:00Sam Sarwarv5.11.0-RC1 No target "VTK::sqlitebin" ERRORI am trying to install ParaView 5.11 on my computer which runs ubuntu 20.04. I have downloaded the latest release as per the instructions:
My configuration for the build are:
`ccmake ../paraview-superbuild/ -DENABLE_cxx11=on -DENABLE_c...I am trying to install ParaView 5.11 on my computer which runs ubuntu 20.04. I have downloaded the latest release as per the instructions:
My configuration for the build are:
`ccmake ../paraview-superbuild/ -DENABLE_cxx11=on -DENABLE_cxx14=on -DENABLE_paraview=on -DENABLE_python3=on -DENABLE_boost=on -DENABLE_hdf5=on -DENABLE_netcdf=on -DENABLE_paraviewweb=on -DENABLE_matplotlib=on -DENABLE_nvidiaindex=on -DENABLE_png=on -DENABLE_vortexfinder2=on -DENABLE_xdmf3=on -DENABLE_ospray=on -DENABLE_ffmpeg=on -DENABLE_visitbridge=on -DENABLE_vtkm=on -DENABLE_mesa=off -DENABLE_ospraymaterials=on -DENABLE_paraviewtutorialdata=on -DENABLE_paraviewgettingstartedguide=on -DENABLE_qt5=OFF -DENABLE_mpi=ON -DENABLE_egl=ON -DPARAVIEW_DEFAULT_SYSTEM_GL=ON -DParaView_FROM_GIT=OFF -DENABLE_sqlite=on`
after the successful configuration process I then type
`make`
the make command fails with the following error:
\`-- Check size of void\* - done -- Enabled modules: VTK(177), ParaView(46 + 8) -- Found nlohmann_json: /home/shahzad/Downloads/Para_build/install/lib/cmake/nlohmann_json/nlohmann_jsonConfig.cmake (found version "3.9.1") -- Configuring done CMake Error at VTK/ThirdParty/libproj/vtklibproj/data/CMakeLists.txt:45 (add_custom_command): Error evaluating generator expression:
```
$<TARGET_FILE:VTK::sqlitebin>
```
No target "VTK::sqlitebin"
CMake Error at VTK/ThirdParty/libproj/vtklibproj/data/CMakeLists.txt:45 (add_custom_command): Error evaluating generator expression:
```
$<TARGET_FILE:VTK::sqlitebin>
```
No target "VTK::sqlitebin"
\-- Generating done CMake Generate step failed. Build files cannot be regenerated correctly. CMake Error at /home/shahzad/Downloads/Para_build/superbuild/sb-paraview-configure.cmake:47 (message): Failed with exit code 1
make\[2\]: \*\*\* \[superbuild/CMakeFiles/paraview.dir/build.make:118: superbuild/paraview/stamp/paraview-configure\] Error 1 make\[1\]: \*\*\* \[CMakeFiles/Makefile2:8835: superbuild/CMakeFiles/paraview.dir/all\] Error 2 make: \*\*\* \[Makefile:136: all\] Error 2 \` I have spent a few hours trying to get this to work, without success. I would appreciate the help in getting this installed.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21522Artifacts displaying with clip filter and different Arrays2022-09-07T08:21:38-04:00Phil SmithArtifacts displaying with clip filter and different ArraysTested MAC Monterey 12.4 x86, local, 5.11.0-RC1 nightly
To Reproduce:
- Open can.ex2 --Apply
- Color by displacement
- select clip --apply
- Color by Vel
- Show both the can and the clip
- The clip will have artifacts shown on it. Rota...Tested MAC Monterey 12.4 x86, local, 5.11.0-RC1 nightly
To Reproduce:
- Open can.ex2 --Apply
- Color by displacement
- select clip --apply
- Color by Vel
- Show both the can and the clip
- The clip will have artifacts shown on it. Rotate it around and they will vary.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21521Building ParaView v4.0.02022-08-31T07:12:32-04:00saulo1131Building ParaView v4.0.0I need to use Paraview on an old machine that has old OpenGL. So I tried installing an older version of Paraview, eg v4.0.0. But when I do git submodule update --init --recursive, it returns some errors to clone some submodules. can anyb...I need to use Paraview on an old machine that has old OpenGL. So I tried installing an older version of Paraview, eg v4.0.0. But when I do git submodule update --init --recursive, it returns some errors to clone some submodules. can anybody help me, please?https://gitlab.kitware.com/paraview/paraview/-/issues/21520External volumes not appearing in file dialog on Windows or linux2022-11-01T22:01:25-04:00Cory Quammencory.quammen@kitware.comExternal volumes not appearing in file dialog on Windows or linuxFrom this [Discourse post](https://discourse.paraview.org/t/paraview-open-file-from-external-drive-not-given-as-an-option/10207):
In both Linux and Windows Paraview does not have an option to read a file from an external disk dive. Clic...From this [Discourse post](https://discourse.paraview.org/t/paraview-open-file-from-external-drive-not-given-as-an-option/10207):
In both Linux and Windows Paraview does not have an option to read a file from an external disk dive. Clicking on ‘File’, then ‘Open’ brings up the ‘Open File’ window, and you can only see the internal computer drive (normally C:/ in Windows); no external drives are visible. Similarly on Linux, there’s no option to read from an external drive.5.12 (Winter 2023)Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/21518Slice filter plane/ring cannot be disabled2022-10-18T13:08:47-04:00Håkon Strandenesh.strandenes@km-turbulenz.noSlice filter plane/ring cannot be disabledI am testing Paraview nightly, this time `ParaView-master-5.10.2-1615-g2ba26e00d8-MPI-Linux-Python3.9-x86_64`. I have found another problem with the slice filter, the red ring and plane outline cannot be disabled when several render wind...I am testing Paraview nightly, this time `ParaView-master-5.10.2-1615-g2ba26e00d8-MPI-Linux-Python3.9-x86_64`. I have found another problem with the slice filter, the red ring and plane outline cannot be disabled when several render windows are active simultaneously.
Steps to reproduce:
1. AMR Gaussian pulse source, default settings, Apply
2. Slice filter, Apply
3. Disable "show plane"
4. Open another render view, the plane and red ring is there. Trying to enable/disable the plane/ring (toggle "show plane" on/off) does not help, it's there.
5. If focus is shifted back to the original view, the plane appears there as well.
This effectively prevent making good visualizations where you need several render views (e.g. comparisons).
I have a screencast of the problem attached:
![cinnamon-20220826-8](/uploads/23a1ec38c1e4febdbd0af16f3d68804c/cinnamon-20220826-8.webm)5.11 (Spring 2022)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21516Surface with Edges after clipping is different before - It creates additional...2022-08-25T20:30:25-04:00Leila SaberiSurface with Edges after clipping is different before - It creates additional edges or removes some edgesI am using Paraview 10.1 and I have a grid that looks fine before clipping (like the first figure), but after I clip it, there are extra lines in the grid when I choose "surface with edges" (second figure) or sometimes it deletes some of...I am using Paraview 10.1 and I have a grid that looks fine before clipping (like the first figure), but after I clip it, there are extra lines in the grid when I choose "surface with edges" (second figure) or sometimes it deletes some of the edges. Could someone helps me with this issue? What I am doing is simply using the clip and then choosing the representation to be "surface with edges". Thanks.
![1](/uploads/3f23669179b9ba73c94bac4df4c74a83/1.PNG)
![2](/uploads/f111f1c26e4a9424c8fd5520b68374d5/2.PNG)https://gitlab.kitware.com/paraview/paraview/-/issues/21514Release ParaView 5.11.0-RC12022-09-20T19:01:37-04:00Vicente Boleavicente.bolea@kitware.comRelease ParaView 5.11.0-RC1# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewTutorial-5.11.0.pdf
- [x] Upload to www.paraview.org/files/v5.11
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.11....# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewTutorial-5.11.0.pdf
- [x] Upload to www.paraview.org/files/v5.11
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.11.0.pdf
- [x] Upload to www.paraview.org/files/v5.11
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.11.0.pdf
- [x] Upload to www.paraview.org/files/v5.11
- macOS sigining machine
- [x] if the machine is offline, request to be switched on.
# Update ParaView
- Update the local copy of `master`.
- If `0-RC1` is `0-RC1`, update `master`
- Otherwise, update `release`
```
git fetch origin
git checkout master
git merge --ff-only origin/master # if this fails, there are local commits that need to be removed
git submodule update --recursive --init
```
- If `master` is not `master`, ensure merge requests which should be
in the release have been merged. The [`backport-mrs.py`][backport-mrs]
script can be used to find and ensure that merge requests assigned to the
associated milestone are available on the `release` branch.
- Integrate changes.
- Make a commit for each of these `release`-only changes on a single topic
(suggested branch name: `update-to-v5.11.0`):
- Assemble release notes into `Documentation/release/ParaView-5.11.0.md`.
- [ ] If `PATCH` is greater than 0, add items to the end of this file.
- [x] Update `version.txt` and tag the commit (tag this commit below)
```
git checkout -b update-to-v5.11.0-RC1 2ba26e00d8ae8143b4b51f137e0739f8c481bb1b
echo 5.11.0-RC1 > version.txt
git commit -m 'Update version number to 5.11.0-RC1' version.txt
```
- [x] Update VTK's `paraview/release` branch. The
[`release-mr`][release-mr] script should be used to do this. Pass
`-c .kitware-release-paraview.json` to use the appropriate
configuration file.
- [x] Merge the VTK `paraview/release` update MR
- [ ] Update kwrobot with the new `paraview/release` branch rules (@ben.boeckel)
- [x] `.gitmodules` to track the `paraview/release` branch of VTK
- [x] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups
- Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- Pull the script for each release; it may have been updated since it
was last used
- `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m 2ba26e00d8ae8143b4b51f137e0739f8c481bb1b`
- The script outputs the information it will be using to create the
merge request. Please verify that it is all correct before creating
the merge request. See usage at the top of the script to provide
information that is either missing or incorrect (e.g., if its data
extraction heuristics fail).
- [x] Get positive review
- [x] `Do: merge`
- [x] Create tag: `git tag -a -m '5.11.0-RC1' 5.11.0-RC1 commit-that-updated-version.txt`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.11.0-RC1`)
- Upload tarballs to `paraview.org`
- [x] Setup your `~/.ssh/config` and add the web host (@vbolea).
- [x] `rsync -rptv $tarballs web:ParaView_Release/v5.11/`
- Software process updates (these can all be done independently)
- [x] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [x] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [x] Add (or update if `master` is `release`) version selection entry
in paraview-superbuild
[backport-mrs]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/backport-mrs.py
[release-mr]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/release-mr.py
[cdash-update-groups]: https://gitlab.kitware.com/utils/cdash-utils/-/blob/master/cdash-update-groups.py
# Update ParaView-Superbuild
- [x] Update master branch for **paraview-superbuild**
```
git fetch origin
git checkout master
git merge --ff-only origin/master
git submodule update --recursive --init
```
- [x] Create new branch `git checkout -b update-to-v5.11.0-RC1 2ba26e00d8ae8143b4b51f137e0739f8c481bb1b`
- Integrate changes.
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] `paraview_SOURCE_SELECTION` version in `README.md`
- [x] `PARAVIEW_VERSION_DEFAULT` in CMakeLists.txt
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.11.0-RC1
- [x] ARG SUPERBUILD_TAG=v5.11.0-RC1
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.11
- [x] Commit changes
- [x] `git add README.md versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile`
- [x] `git commit -m "Update the default version to 5.11.0-RC1"`
- Make a commit for each of these `release`-only changes
- [x] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups (if `master` is `master`)
- Create a commit which will be tagged:
- [x] `git commit --allow-empty -m "paraview: add release 5.11.0"`
- [x] Created tag: `git tag -a -m 'ParaView superbuild 5.11.0-RC1' v5.11.0-RC1 HEAD`
- Force `5.11.0-RC1` in CMakeLists.txt
- [x] Append to the top of CMakeLists.txt (After project...) The following
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.11.0-RC1" CACHE STRING "Force version to 5.11.0-RC1" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- [x] Create fixup commit `git commit -a --fixup=@`
- Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- Pull the script for each release; it may have been updated since it
was last used
- `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m 2ba26e00d8ae8143b4b51f137e0739f8c481bb1b`
- [x] Build binaries
- [x] Build binaries (start all pipelines)
- [x] Download the binaries that have been generated from the Pipeline
build products. They will be deleted within 24 hours.
- [x] Get positive review
- [x] Remove fixup commit: `git reset --hard @^`
- [x] Force push `git push -f gitlab`
- [x] `Do: merge`
- Software process updates (these can all be done independently)
- [x] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [x] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [x] Add (or update if `master` is `release`) version selection entry
in paraview-superbuild
# Sign Windows binaries
- [ ] Request Windows binary signings (only .exe archives) on the Package
Signing repo. Example request [here][win-sign-example].
# Sign macOS binaries
- [x] Upload to signing server, run script, download resulting .pkg and .dmg files
- [x] Install from .pkg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.11.0-RC1.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.11.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
Binary checklist
- [x] macOS arm64
- [x] macOS x86\_64
- [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.11/`)
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website
```
buildListing.sh
updateMD5sum.sh v5.11
```
- [x] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.11.0-RC1`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.11.0-RC1`.
# Spack
- [x] Update Spack package: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [ ] Request DoD vulnerability scan
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit
/cc @charles.gueunet
[win-sign-example]: https://kwgitlab.kitware.com/software-process/package-signing/-/issues/125.11 (Spring 2022)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.com