ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-07-16T16:13:28-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/19155Spreadsheet does not scale fonts correctly2019-07-16T16:13:28-04:00W. Alan ScottSpreadsheet does not scale fonts correctlyThe Spreadsheet View is not scaling correctly when you select Edit/ Settings/ Override Font.
* 5.7.0-RC1, Linux, local server.The Spreadsheet View is not scaling correctly when you select Edit/ Settings/ Override Font.
* 5.7.0-RC1, Linux, local server.https://gitlab.kitware.com/paraview/paraview/-/issues/19154Exodus reader crash with superelements2020-06-24T17:59:03-04:00W. Alan ScottExodus reader crash with superelementsWe have a crash in an exodus dataset. This dataset has superelements.
* 5.7.0-RC1, Linux, local server.
* Open SAND2017-5827O-FSM_Residual-bad-eigen.e. ParaView will crash in the reader freeing memory that it doesn't own.
This data...We have a crash in an exodus dataset. This dataset has superelements.
* 5.7.0-RC1, Linux, local server.
* Open SAND2017-5827O-FSM_Residual-bad-eigen.e. ParaView will crash in the reader freeing memory that it doesn't own.
This dataset opens correctly with EnSight.
I will send two datasets to Utkarsh and Cory. Datasets are UUR.
* SAND2017-5827O-FSM_Residual-bad-eigen.e
* SAND2017-5827O-FSM_Residual-good-eigen.e5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19153Crashes when create/update HTG grid with inconsistent descriptor and maximum ...2019-07-15T17:57:57-04:00Feimi YuCrashes when create/update HTG grid with inconsistent descriptor and maximum level@demarle @yufeimi
Ubuntu Linux at 32321d09
To reproduce the problem:
1. Create a `source->Data Objects->Hyper Tree Grid`
2. Set `Maximum Level` to 3 and `Descriptor` to "R"
OR
Set `Maximum level` to 4 and `Descriptor` to "R|.........@demarle @yufeimi
Ubuntu Linux at 32321d09
To reproduce the problem:
1. Create a `source->Data Objects->Hyper Tree Grid`
2. Set `Maximum Level` to 3 and `Descriptor` to "R"
OR
Set `Maximum level` to 4 and `Descriptor` to "R|........"
Guess the reason is that when it hits an "R" that is not yet the maximum level it will go further to search for whether to split the derived cells. Undefined behavior happens when the string is not long enough.https://gitlab.kitware.com/paraview/paraview/-/issues/19152ParaView 5.7.0-RC1 linux: GenericIOReader fails to load2019-08-06T19:10:18-04:00Cory Quammencory.quammen@kitware.comParaView 5.7.0-RC1 linux: GenericIOReader fails to load* Start ParaView, builtin server
* Tools -> Manage Plugins...
* Load GenericIOReader plugin
Loading fails with the error message:
```
ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/bu...* Start ParaView, builtin server
* Tools -> Manage Plugins...
* Load GenericIOReader plugin
Loading fails with the error message:
```
ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/ParaViewCore/ClientServerCore/Core/vtkPVPluginLoader.cxx, line 417
vtkPVPluginLoader (0x98c58e0): libvtkGenericIOReader.so: cannot open shared object file: No such file or directory
```
`ldd` shows that it is linking against libgfortran, but can't find it.
```
> ldd `find . -name libvtkGenericIOReader.so`
linux-vdso.so.1 (0x00007ffc1c1d7000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fdcede08000)
libvtkParallelMPI-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkParallelMPI-pv5.7.so.1 (0x00007fdcedbf3000)
libvtkParallelCore-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkParallelCore-pv5.7.so.1 (0x00007fdced99e000)
libvtkCommonExecutionModel-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonExecutionModel-pv5.7.so.1 (0x00007fdced6c1000)
libvtkCommonDataModel-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonDataModel-pv5.7.so.1 (0x00007fdced079000)
libvtkCommonTransforms-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonTransforms-pv5.7.so.1 (0x00007fdcece4a000)
libvtkCommonMath-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonMath-pv5.7.so.1 (0x00007fdcecc2a000)
libvtkCommonCore-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonCore-pv5.7.so.1 (0x00007fdcec4c6000)
libvtksys-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtksys-pv5.7.so.1 (0x00007fdcec26a000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fdcec066000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fdcebe47000)
libtbb.so.2 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libtbb.so.2 (0x00007fdcebbe9000)
libmpi.so.12 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libmpi.so.12 (0x00007fdceb6ad000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fdceb324000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fdceaf86000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fdcead6e000)
/lib64/ld-linux-x86-64.so.2 (0x00007fdcee429000)
libvtkIOLegacy-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkIOLegacy-pv5.7.so.1 (0x00007fdceaaca000)
libvtkIOCore-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkIOCore-pv5.7.so.1 (0x00007fdcea864000)
libvtkCommonSystem-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonSystem-pv5.7.so.1 (0x00007fdcea650000)
libvtkCommonMisc-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonMisc-pv5.7.so.1 (0x00007fdcea435000)
libvtkloguru-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkloguru-pv5.7.so.1 (0x00007fdcea1ef000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fdce9fe7000)
libgfortran.so.3 => not found
libvtkdoubleconversion-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkdoubleconversion-pv5.7.so.1 (0x00007fdce9dd8000)
libvtklz4-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtklz4-pv5.7.so.1 (0x00007fdce9bb2000)
libvtklzma-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtklzma-pv5.7.so.1 (0x00007fdce9982000)
libz.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libz.so.1 (0x00007fdce9768000)
```
Of note: `libgfortran.so.3 => not found`. However, `libgfortran.so.3` is in the `lib` directory in the binary directory. Indeed, adding `<full/path/to>/lib` to `LD_LIBRARY_PATH` resolves the issue.5.7 (Summer 2019)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19151ParaView 5.7.0-RC1 linux: libxml2 warning message2019-08-06T19:17:34-04:00Cory Quammencory.quammen@kitware.comParaView 5.7.0-RC1 linux: libxml2 warning messageUpon startup, we are getting the following:
```
bin/paraview: /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/bin/../lib/libxml2.so.2: no version information available (required by /home/coryquammen/Downloads/ParaView-5.7...Upon startup, we are getting the following:
```
bin/paraview: /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/bin/../lib/libxml2.so.2: no version information available (required by /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/bin/../lib/libvtkIOInfovis-pv5.7.so.1)
```5.7 (Summer 2019)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19150ParaView 5.7.0-RC1 macOS: Crash during reset2019-07-08T11:28:39-04:00Cory Quammencory.quammen@kitware.comParaView 5.7.0-RC1 macOS: Crash during resetI thought I filed an issue about this before, but couldn't find it.
* Run ParaView, builtin server
* Edit -> Reset Session. Crash.
Stack trace
```
Thread 0 Crashed:: paraview Dispatch queue: com.apple.main-thread
0 libospray_module...I thought I filed an issue about this before, but couldn't find it.
* Run ParaView, builtin server
* Edit -> Reset Session. Crash.
Stack trace
```
Thread 0 Crashed:: paraview Dispatch queue: com.apple.main-thread
0 libospray_module_ispc.dylib 0x0000000128f3a771 ospray::ManagedObject*& ospcommon::utility::Any::get<ospray::ManagedObject*>() + 449
1 libospray.0.dylib 0x0000000117588c0d ospray::api::Device::createDevice(char const*) + 205
2 libospray.0.dylib 0x000000011756da29 ospInit + 5577
3 libvtkRenderingRayTracing-pv5.7.1.dylib 0x00000001174f60c2 rtwInit() + 50
4 libvtkRenderingRayTracing-pv5.7.1.dylib 0x000000011751319c vtkOSPRayPass::vtkOSPRayPass() + 92
5 libvtkRenderingRayTracing-pv5.7.1.dylib 0x000000011751310c vtkOSPRayPass::New() + 28
6 libvtkPVClientServerCoreRendering-pv5.7.1.dylib 0x0000000111d55c0b vtkPVRenderView::vtkInternals::vtkInternals() + 59
7 libvtkPVClientServerCoreRendering-pv5.7.1.dylib 0x0000000111d4dc15 vtkPVRenderView::vtkPVRenderView() + 293
8 libvtkPVClientServerCoreRendering-pv5.7.1.dylib 0x0000000111d4d9dc vtkPVRenderView::New() + 28
9 libvtkClientServer-pv5.7.1.dylib 0x000000011372b9d7 vtkClientServerInterpreter::NewInstance(char const*) + 327
10 libvtkPVServerImplementationCore-pv5.7.1.dylib 0x0000000112108462 vtkSIProxy::CreateVTKObjects() + 50
11 libvtkPVServerImplementationCore-pv5.7.1.dylib 0x0000000112107617 vtkSIProxy::InitializeAndCreateVTKObjects(paraview_protobuf::Message*) + 1415
12 libvtkPVServerImplementationCore-pv5.7.1.dylib 0x0000000112106dab vtkSIProxy::Push(paraview_protobuf::Message*) + 43
13 libvtkPVServerImplementationCore-pv5.7.1.dylib 0x00000001120ef092 vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) + 1634
14 libvtkPVServerImplementationCore-pv5.7.1.dylib 0x00000001120ef381 vtkPVSessionCore::PushState(paraview_protobuf::Message*) + 49
15 libvtkPVServerImplementationCore-pv5.7.1.dylib 0x00000001120ecfd6 vtkPVSessionBase::PushState(paraview_protobuf::Message*) + 38
16 libvtkPVServerManagerCore-pv5.7.1.dylib 0x0000000111fcf076 vtkSMProxy::CreateVTKObjects() + 1110
17 libvtkPVServerManagerRendering-pv5.7.1.dylib 0x0000000111bf1e88 vtkSMViewProxy::CreateVTKObjects() + 40
18 libvtkPVServerManagerRendering-pv5.7.1.dylib 0x0000000111bc7341 vtkSMRenderViewProxy::CreateVTKObjects() + 49
19 libvtkPVServerManagerCore-pv5.7.1.dylib 0x0000000111fce781 vtkSMProxy::UpdateVTKObjects() + 33
20 libvtkPVServerManagerCore-pv5.7.1.dylib 0x0000000111fa348e vtkSMGlobalPropertiesProxy::Link(char const*, vtkSMProxy*, char const*) + 910
21 libvtkPVServerManagerCore-pv5.7.1.dylib 0x0000000111fb8b12 vtkSMParaViewPipelineController::SetupGlobalPropertiesLinks(vtkSMProxy*) + 562
22 libvtkPVServerManagerCore-pv5.7.1.dylib 0x0000000111fbc4ef vtkSMParaViewPipelineController::PreInitializeProxy(vtkSMProxy*) + 63
23 libpqCore-pv5.7.1.dylib 0x00000001118267d8 pqObjectBuilder::createView(QString const&, pqServer*) + 392
24 libpqApplicationComponents-pv5.7.1.dylib 0x0000000110076b3e pqDefaultViewBehavior::onServerCreation(pqServer*) + 366
25 org.qt-project.QtCore 0x0000000110fac09c QMetaObject::activate(QObject*, int, int, void**) + 3132
26 libpqCore-pv5.7.1.dylib 0x000000011188651f pqServerManagerModel::serverAdded(pqServer*) + 63
27 libpqCore-pv5.7.1.dylib 0x0000000111862401 pqServerManagerModel::onConnectionCreated(long long) + 833
28 org.qt-project.QtCore 0x0000000110fac09c QMetaObject::activate(QObject*, int, int, void**) + 3132
29 libpqCore-pv5.7.1.dylib 0x0000000111887a0f pqServerManagerObserver::connectionCreated(long long) + 63
30 org.qt-project.QtCore 0x0000000110fac09c QMetaObject::activate(QObject*, int, int, void**) + 3132
31 libvtkGUISupportQt-pv5.7.1.dylib 0x0000000111a9d29c vtkQtConnection::EmitExecute(vtkObject*, unsigned long, void*, void*, vtkCommand*) + 108
32 libvtkCommonCore-pv5.7.1.dylib 0x000000011605f1e1 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 33
33 libvtkCommonCore-pv5.7.1.dylib 0x0000000116230df5 vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) + 981
34 libvtkPVClientServerCoreCore-pv5.7.1.dylib 0x0000000112a0dc90 vtkProcessModule::RegisterSession(vtkSession*) + 288
35 libpqCore-pv5.7.1.dylib 0x0000000111828f6e pqObjectBuilder::resetServer(pqServer*) + 174
36 libpqApplicationComponents-pv5.7.1.dylib 0x0000000110077839 pqDeleteReaction::deleteAll() + 137
37 libpqApplicationComponents-pv5.7.1.dylib 0x00000001100787b6 pqDeleteReaction::onTriggered() + 278
```5.7 (Summer 2019)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/19149ParaView 5.7.0-RC1 Windows: NVIDIA IndeX representation causes ParaView to crash2021-09-16T17:34:30-04:00Cory Quammencory.quammen@kitware.comParaView 5.7.0-RC1 Windows: NVIDIA IndeX representation causes ParaView to crash* ParaView, builtin server
* Tools -> Manage Plugins...
* Load `pvNVIDIAIndeX`
* Add **Wavelet**
* Switch representation to "NVIDIA IndeX"
* ParaView crashes* ParaView, builtin server
* Tools -> Manage Plugins...
* Load `pvNVIDIAIndeX`
* Add **Wavelet**
* Switch representation to "NVIDIA IndeX"
* ParaView crashes5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19148ParaView 5.7.0-RC1 windows: IndeX gives warning message when loading Wavelet2021-04-22T21:11:37-04:00Cory Quammencory.quammen@kitware.comParaView 5.7.0-RC1 windows: IndeX gives warning message when loading Wavelet* Run ParaView, builtin server
* Tools -> Manage Plugins...
* Load `pvNVIDIAIndeX`
* Add **Wavelet** source.
Immediately, IndeX produces a warning:
```
nvindex: 0.0 INDEX main warn : Index_debug_configuration: Unknown key 'async_s...* Run ParaView, builtin server
* Tools -> Manage Plugins...
* Load `pvNVIDIAIndeX`
* Add **Wavelet** source.
Immediately, IndeX produces a warning:
```
nvindex: 0.0 INDEX main warn : Index_debug_configuration: Unknown key 'async_subset_load' used with value '0'
```
It is not required to switch to the NVIDIA IndeX representation to see this warning.
/cc @eolivares5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19147ParaView 5.7.0-RC1: Error message when loading example visualizations2019-09-11T21:37:37-04:00Cory Quammencory.quammen@kitware.comParaView 5.7.0-RC1: Error message when loading example visualizations* Run ParaView, builtin
* Go to Help -> Example Visualizations
* Click on "Exodus II file with timesteps, Clip filter"
The visualization will load, but you'll get the following error 3 times:
```
ERROR: In C:\bbd\ecd3383f\build\superbu...* Run ParaView, builtin
* Go to Help -> Example Visualizations
* Click on "Exodus II file with timesteps, Clip filter"
The visualization will load, but you'll get the following error 3 times:
```
ERROR: In C:\bbd\ecd3383f\build\superbuild\paraview\src\ParaViewCore\ServerManager\Core\vtkSMGlobalPropertiesProxy.cxx, line 107
vtkSMGlobalPropertiesProxy (00000223AD89DB70): Incorrect target property name: Color
```
Looks like the state file needs to be updated, or `vtkSMStateVersionController` should be updated to remove/update this property.5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19146Streamlines filter uses inconsistent seed ids in parallel2019-07-25T14:44:23-04:00Utkarsh AyachitStreamlines filter uses inconsistent seed ids in parallelSteps
* pvserver (2 ranks)
* open can.ex2, all variables apply
* go to second last timestep
* apply streamtracer with SeedType=Point Source, Center=(0.9, 2.6,-14), Radius=0, Number of Points=1, Apply
* Show streamline cell data in spread...Steps
* pvserver (2 ranks)
* open can.ex2, all variables apply
* go to second last timestep
* apply streamtracer with SeedType=Point Source, Center=(0.9, 2.6,-14), Radius=0, Number of Points=1, Apply
* Show streamline cell data in spreadsheet view, you'll see the following:
![image](/uploads/5bc314e248385eeba96da0fc7dcf0309/image.png)
The seed id should have been the same for both the cells.
This is a Watney bug.5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19145Release ParaView 5.7-RC12019-08-02T11:54:29-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.7-RC1# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0-RC1.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0-...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0-RC1.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0-RC1.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.7.0-RC1.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Assemble release notes into `Documentation/release/ParaView-5.7.0-RC1`.
- [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
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.7.0-RC1
echo 5.7.0-RC1 > version.txt
git commit -m 'Update version number to 5.7.0-RC1' version.txt
git tag -a -m 'ParaView 5.7.0-RC1' v5.7.0-RC1 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`
- Update VTK's `paraview/release` branch
- [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] `git config -f .gitmodules submodule.VTK.branch paraview/release`
- [x] `git commit -m 'release: follow VTK's paraview/release branch' .gitmodules`
- [x] `git push origin update-to-v5.7.0-RC1:release v5.7.0-RC1`
- [x] Update kwrobot with the new `release` branch rules
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.7.0-RC1`)
- [ ] Catalyst (`Catalyst/generate-tarballs.sh v5.7.0-RC1`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.7/`
# Update ParaView-Superbuild
- [x] Update `master` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout master
git merge --ff-only origin/master
```
- Update `CMakeLists.txt`
- [x] `git checkout -b update-to-v5.7.0-RC1`
- [x] Update PARAVIEW_5.7.0-RC1_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.7.0-RC1" CACHE STRING "Force version to 5.7.0-RC1" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update `versions.cmake`
- [x] Guide selections in `versions.cmake`
- [x] `git add versions.cmake CMakeLists.txt`
- [x] `git commit -m "Update the default version to 5.7.0-RC1"`
- Update default versions in container build recipes
- Docker: update default tag strings (in `Scripts/docker/ubuntu/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.7.0-RC1
- [x] ARG SUPERBUILD_TAG=v5.7.0-RC1
- 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 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-RC1' v5.7.0-RC1 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0-RC1:release v5.7.0-RC1`
- [x] Update kwrobot with the new `release` branch rules
# 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
- [ ] IndeX runs
- [x] 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
- Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.7/`)
- [x] Ask @chuck.atkins to sign macOS binary
- [x] 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
- [ ] Write and publish blog post with release notes.
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit
/cc @demarle5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19144STLWriter complains when writing empty datasets2022-05-23T13:30:41-04:00Utkarsh AyachitSTLWriter complains when writing empty datasetsTo replicate, do the following:
* Linux, master (v5.6.1-1795-g3190975), remote server. Use 16 ranks.
* Load g1s1. Apply.
* Extract Surface. Apply.
* File/ Save Data. .stl. OK.
* Number of I/O Ranks - 4. OK.
We get the following errors...To replicate, do the following:
* Linux, master (v5.6.1-1795-g3190975), remote server. Use 16 ranks.
* Load g1s1. Apply.
* Extract Surface. Apply.
* File/ Save Data. .stl. OK.
* Number of I/O Ranks - 4. OK.
We get the following errors:
```
ERROR: In /snip/src/VTK/IO/Geometry/vtkSTLWriter.cxx, line 76 vtkSTLWriter (0x3f8f950): No data to write!
ERROR: In /snip/src/VTK/IO/Geometry/vtkSTLWriter.cxx, line 76 vtkSTLWriter (0x3f8f950): No data to write!
```5.11 (Spring 2022)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/19142Save Data including the same save-settings as in Animation2022-11-27T22:24:16-05:00Tobias HolzmannSave Data including the same save-settings as in AnimationHi all, it would be very nice if the file names (if we save time dependent data using 'Save Data') are set as in the 'Save Animation Mask'. I guess the implementation is not difficult as everything is already built in. My suggestion is t...Hi all, it would be very nice if the file names (if we save time dependent data using 'Save Data') are set as in the 'Save Animation Mask'. I guess the implementation is not difficult as everything is already built in. My suggestion is that the files should have the same numbering (leading zero) as the animation files. E.g.
We save the data from time 1 to 100. The data file name is "foobar.txt" which will result in
foobar.1.txt
foobar.2.txt
.
.
.
However, it would be nicer (e.g. for sorting etc) to have the file names as:
foobar.0001.txt
foobar.0002.txt
foobar.0003.txt
.
.
.
Furthermore, it would be nice if one can set the time frame (as it is already available for the animation set-up). E.g., we have extracted the time from 0 to 45 and want to restart later from 46 to the end.
I hope I described the feature in a way everybody understands it. Right now, I have to reorganize the data using bash scripts which is fine but if it would be already within ParaView, it would be exzellent too.
Thank you in advance,
Tobias HolzmannAron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/19141Control left-click puts RenderView in permanent zoom in/out mode2020-01-07T20:10:06-05:00Cory Quammencory.quammen@kitware.comControl left-click puts RenderView in permanent zoom in/out modeParaView 5.6.1, macOS on MacBook Pro with trackpad.
* ParaView, builtin server
* Add any data source
* Control-left click in the Render View. ParaView will get stuck in a permanent zoom in/out mode.ParaView 5.6.1, macOS on MacBook Pro with trackpad.
* ParaView, builtin server
* Add any data source
* Control-left click in the Render View. ParaView will get stuck in a permanent zoom in/out mode.https://gitlab.kitware.com/paraview/paraview/-/issues/19140vtkCompleteArrays/vtkXMLPRectilinearGridWriter doesn't work for rectilinear g...2019-08-07T07:47:42-04:00Andrew BauervtkCompleteArrays/vtkXMLPRectilinearGridWriter doesn't work for rectilinear grids without data on process 0vtkCompleteArrays needs to pass the X, Y and Z arrays to process 0 if process 0 has no data on it so that the vtkXMLPRectilinearGridWriter will write out the meta-data on process 0 properly. Steps to reproduce are:
1. Run ParaView and c...vtkCompleteArrays needs to pass the X, Y and Z arrays to process 0 if process 0 has no data on it so that the vtkXMLPRectilinearGridWriter will write out the meta-data on process 0 properly. Steps to reproduce are:
1. Run ParaView and connect to a pvserver with 8 MPI processes
2. Open cth.vtr which is available under ./ExternalData/Testing/Data/cth.vtr or ./ExternalData/VTK/Testing/Data/cth.vtr
3. Create an Aggregate Dataset filter with Number Of Target Processes set to 3
4. Save the output
This will fail when trying to load the saved file back into ParaView with the message "Could not find PCoordinates element with 3 arrays".5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19139Plot over line in different times in same line chart2019-06-30T04:23:06-04:00AlexLadinoPlot over line in different times in same line chartI have an openfoam case with results field for different times.
I want to plot over line a variable at time X and the same variable plot over line at time Y and plot them in the same line chart.
Any idea of how to do that?
paraview 5.4.1I have an openfoam case with results field for different times.
I want to plot over line a variable at time X and the same variable plot over line at time Y and plot them in the same line chart.
Any idea of how to do that?
paraview 5.4.1https://gitlab.kitware.com/paraview/paraview/-/issues/19138CGNS outline mode blank remote server2019-07-02T18:14:31-04:00W. Alan ScottCGNS outline mode blank remote serverWe are getting either nothing showing up, or only one block showing up, with CGNS. 5.6.0 does not show this issue. Here is how to replicate:
* Linux, remote server (16 ranks), master (v5.6.1-1778-g702a95d).
* Open Whitney 144 file cgns...We are getting either nothing showing up, or only one block showing up, with CGNS. 5.6.0 does not show this issue. Here is how to replicate:
* Linux, remote server (16 ranks), master (v5.6.1-1778-g702a95d).
* Open Whitney 144 file cgns dataset. Apply.
* It will come up in outline mode, colored by block colors.
Nothing shows up! This is a bug.
Note - I have also seen only one block (generally a yellow one) show up. It is inconsistent.
@utkarsh.ayachit @cory.quammen I hate to do this, but I think this is a showstopper for the 5.7 release.
Watney bug.
Also verify that the fix does not bring back previously closed issues #19084 and #19037.5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19137Load state for new directory always fails2019-07-02T16:34:14-04:00W. Alan ScottLoad state for new directory always failsLoad state for a new directory always fails.
* Make a directory, such as junkDir. Make a second directory inside this one, for instance, work. Copy can.exo into work.
* Linux, master, builtin server.
* Open junkDir/work/can.exo. Apply...Load state for a new directory always fails.
* Make a directory, such as junkDir. Make a second directory inside this one, for instance, work. Copy can.exo into work.
* Linux, master, builtin server.
* Open junkDir/work/can.exo. Apply.
* Save state file in junkDir.
* Reset Session.
* Move can.exo from junkDir/work to junkDir.
* Load State. Search Files under Specified Directory. It will automagically load the correct directory.
Fail. Here is the output.
Cannot find '' in '/MySnipHere/junkDir'. Using ''.
ERROR: In /snip/ParaView5/VTK/IO/Exodus/vtkExodusIIReader.cxx, line 3847
vtkExodusIIReaderPrivate (0x3d94370): Exodus filename pointer was nullptr or pointed to an empty string.
ERROR: In /snip/ParaView5/VTK/IO/Exodus/vtkExodusIIReader.cxx, line 5490
vtkPExodusIIReader (0x3d9b1d0): Unable to open file "" to read metadata
ERROR: In /snip/ParaView5/VTK/IO/Exodus/vtkExodusIIReader.cxx, line 3847
vtkExodusIIReaderPrivate (0x3d94370): Exodus filename pointer was nullptr or pointed to an empty string.
ERROR: In /snip/ParaView5/VTK/IO/Exodus/vtkExodusIIReader.cxx, line 5490
vtkPExodusIIReader (0x3d9b1d0): Unable to open file "" to read metadata
Since this makes state files useless for anyone and any dataset other than the original, This is a showstopper bug for 5.7.5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19136new findhdf5 not compatible with crayhdf52019-07-01T13:56:52-04:00David E. DeMarlenew findhdf5 not compatible with crayhdf5Under cray programming environment, findhdf5 does not return a library, as compiler has built in knowledge about it. ParaView's fails to configure in this case because the modified findhdf5 we use wants to query the library in
vtk_detect...Under cray programming environment, findhdf5 does not return a library, as compiler has built in knowledge about it. ParaView's fails to configure in this case because the modified findhdf5 we use wants to query the library in
vtk_detect_library_type.5.7 (Summer 2019)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19134pvpython support for plugins in .app layouts and classic unix-style layouts2020-05-07T21:24:21-04:00Joshua Levinepvpython support for plugins in .app layouts and classic unix-style layoutsThis issue is about the default search path for plugins on pvpython, particularly when compiled on MacOS
It seems the standard behavior is for pvpython to look for plugins using linux-style paths (e.g. `lib/paraviewX.Y/plugins`). By co...This issue is about the default search path for plugins on pvpython, particularly when compiled on MacOS
It seems the standard behavior is for pvpython to look for plugins using linux-style paths (e.g. `lib/paraviewX.Y/plugins`). By comparison, when ParaView is compiled as a .app, the default location for plugins is embedded in the .app (e.g. `paraview.app/Contents/MacOS/plugins` is reported by Tools->Manage Plugins). Plugins installed and working correctly for ParaView thus are not seen by pvpython.
I understand the build system for ParaView master is changing, but it would be useful to enable a consistent location for plugins across paraview/pvpython and across operating systems.