ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-10-28T16:10:31-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/18567Release ParaView 5.6.0-RC32018-10-28T16:10:31-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.6.0-RC3# Preparatory steps
- Update ParaView guides
- [x] User manual
- [x] Rename to ParaViewGuide-5.6.0-RC3.pdf
- [x] Upload to www.paraview.org/files/v5.6
- [x] Catalyst Guide
- [x] Rename to ParaViewCatalystGuid...# Preparatory steps
- Update ParaView guides
- [x] User manual
- [x] Rename to ParaViewGuide-5.6.0-RC3.pdf
- [x] Upload to www.paraview.org/files/v5.6
- [x] Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.6.0-RC3.pdf
- [x] Upload to www.paraview.org/files/v5.6
- [x] Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.6.0-RC3.pdf
- [x] Upload to www.paraview.org/files/v5.6
- [ ] Assemble release notes into `Documentation/release/ParaView-5.6.0-RC3`.
- [ ] 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
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.6.0-RC3
echo 5.6.0-RC3 > version.txt
git commit -m 'Update version number to 5.6.0-RC3' version.txt
git tag -a -m 'ParaView 5.6.0-RC3' v5.6.0-RC3 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.6.0-RC3:release v5.6.0-RC3`
If making a non-RC release, additionally:
- Update documentation page
- [ ] See `https://github.com/Kitware/paraview-docs/blob/gh-pages/versions.json`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --zip -v v5.6.0-RC3`)
- [x] Catalyst (`Catalyst/generate-tarballs.sh v5.6.0-RC3`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.6/`
# Update ParaView-Superbuild
- Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
```
- 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.6.0-RC3" CACHE STRING "Force version to 5.6.0-RC3" 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.6.0-RC3"`
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP
- [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.6.0-RC3' v5.6.0-RC3 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.6.0-RC3:release v5.6.0-RC3`
# 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
- [x] 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`
- [x] `rsync -rptv $binaries paraview.release:ParaView_Release/v5.6/`
- [x] Ask @chuck.atkins to sign macOS binary
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt`
```
buildListing.sh
updateMD5sum.sh v5.6
```
- [x] Test download links
# 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.ayachit5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18550Integrate variable filter needs performance improvements2018-11-02T15:33:21-04:00W. Alan ScottIntegrate variable filter needs performance improvementsThe integrate variables filter needs performance improvements. I believe this can be replicated as follows:
* Linux, builtin server, 5.5.2.
* sources/ Unstructured Cell Types/ Tet/ Block Dimensions 100 100 100, Apply.
* IntegrateVa...The integrate variables filter needs performance improvements. I believe this can be replicated as follows:
* Linux, builtin server, 5.5.2.
* sources/ Unstructured Cell Types/ Tet/ Block Dimensions 100 100 100, Apply.
* IntegrateVariables filter. Apply.
A million cells should not take this long to process. I would hope and expect it should be around or less than the time to create the unstructured cell type in the first place. Here is a Timer Log:
```
PropertiesPanel::Apply, 159.472 seconds
RenderView::Update, 10.0236 seconds
vtkPVView::Update, 10.0233 seconds
Execute vtkCellTypeSource id: 8000, 2.0739 seconds
Execute vtkGeometryRepresentationWithFaces id: 8315, 7.90282 seconds
UnstructuredCellTypes::GatherInformation, 0.110369 seconds
vtkPVView::Update, 149.183 seconds
Execute vtkIntegrateAttributes id: 8372, 149.181 seconds
<Snip>
Still Render, 0.036104 seconds
Render (use_lod: 0), (use_distributed_rendering: 0), (use_ordered_compositing: 0)
OpenGL Dev Render, 0.032254 seconds
Render (use_lod: 0), (use_distributed_rendering: 0), (use_ordered_compositing: 0
```
Here is what I found:
In file VTK/Filters/Parallel/vtkIntegrateAttributes,
In function vtkIntegrateAttributes::ExecuteBloc(), there is a for loop, running through all cells in the dataset. Everything below here should be performance code.
```
for (cellId = 0; cellId < numCells; ++cellId)
{
....
this->IntegrateTetrahedron(); // line 264.
....
}
vtkIntegrateAttributes::IntegrateTetrahedron() calls
this->IntegrateData1() and then this->IntegrateData4().
Again, this happens per cell.
vtkIntegrateAttributes::IntegrateData1() and vtkIntegrateAttributes::IntegrateData4() have the following:
// GetNumberOfFields calls Prune, which then leads to garbage collection -
// PER CELL.
// This is a major slowdown.
numArrays = fieldList.GetNumberOfFields();
// I assume for every variable? Now, we are every variable of every cell.
for (i = 0; i < numArrays; ++i)
{
// GetFieldIndex is slow. I didn't dig into why. Please look, and speed it up.
if (fieldList.GetFieldIndex(i) < 0)
continue;
// Comment in code. We could template for speed.
// NO - isn't it possible to pick up this index once?
inArray = inda->GetArray(fieldList.GetDSAIndex(index, i));
// GetFieldIndex is being found a second time! Get rid of this second call,
// use results from first call. Also, isn't it possible to get this array once?
outArray = outda->GetArray(fieldList.GetFieldIndex(i));
numComponents = inArray->GetNumberOfComponents();
// Everything from here on down is surprisingly noise.
for (j = 0; j < numComponents; ++j)
{
vIn1 = inArray->GetComponent(pt1Id, j);
vOut = outArray->GetComponent(0, j);
dv = vIn1;
vOut += dv * k;
outArray->SetComponent(0, j, vOut);
}
}
```
I am attaching the performance profile that I acquired from vtune. This shows GetNumberOfFields expanded.
![Capture](/uploads/ce02fee13b3d7ac1393a7b6a3e013d3e/Capture.JPG)
Here is GetFieldIndex expanded:
![Capture1](/uploads/9249591df38cb4901fdcbfe44dfa604c/Capture1.JPG)
And here is GetIDSIndex expanded:
![Capture2](/uploads/7bfc707bbc1bbfcacbdd1b7552b392bc/Capture2.JPG)5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18492Find Data is min/max feature is broken2018-10-04T19:31:03-04:00Kenneth MorelandFind Data is min/max feature is brokenWhile going through the ParaView tutorial for version 5.6 (with RC2), I ran into the following issue. When you open the `Find Data` dialog box and try to do a selection where the field is max or is min, you get a bunch of Python errors a...While going through the ParaView tutorial for version 5.6 (with RC2), I ran into the following issue. When you open the `Find Data` dialog box and try to do a selection where the field is max or is min, you get a bunch of Python errors and nothing is selected. To replicate, do the following.
1. Load can.ex2. Load all variables. Apply.
2. Go to the last time step.
3. Open the `Find Data` dialog box.
4. In the second row of combo boxes, select `Global ID` and `is min`.
5. Click `Run Selection Query`
When you run the selection query, you get the following error messages.
```
Error: Failed to evaluate Expression 'GlobalElementId == min(GlobalElementId)'. The following exception stack should provide additional developer specific information. This typically implies a malformed expression. Verify that the expression is valid.
Warning: In C:\bbd\6c27b535\source-paraview\ParaViewCore\ClientServerCore\Core\vtkPythonSelector.cxx, line 76
vtkPythonSelector (00000281446F7E10): Could not invoke 'python_selector.execute()'
Traceback (most recent call last):
File "C:/Program Files/ParaView 5.6.0-RC2-Qt5-MPI-Windows-msvc2015-64bit/bin\Lib/site-packages\paraview\python_selector.py", line 76, in execute
maskArray = calculator.compute(inputs, query, ns=elocals)
File "C:/Program Files/ParaView 5.6.0-RC2-Qt5-MPI-Windows-msvc2015-64bit/bin\Lib/site-packages\paraview\calculator.py", line 140, in compute
retVal = eval(expression, globals(), mylocals)
File "<string>", line 1, in <module>
File "C:/Program Files/ParaView 5.6.0-RC2-Qt5-MPI-Windows-msvc2015-64bit/bin\Lib/site-packages\vtkmodules\numpy_interface\algorithms.py", line 396, in min
return _global_func(MinImpl(), array, axis, controller)
File "C:/Program Files/ParaView 5.6.0-RC2-Qt5-MPI-Windows-msvc2015-64bit/bin\Lib/site-packages\vtkmodules\numpy_interface\algorithms.py", line 196, in _global_func
from mpi4py import MPI
ImportError: No module named mpi4py
```5.6 (Fall 2018)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/18490ospray and embree won't build with cray programming environment in paraview 5.62018-09-27T18:14:14-04:00David E. DeMarleospray and embree won't build with cray programming environment in paraview 5.6Per discourse discussion:
https://discourse.paraview.org/t/building-5-6-0-rc1-on-cray/570
confirmed on theta@anlPer discourse discussion:
https://discourse.paraview.org/t/building-5-6-0-rc1-on-cray/570
confirmed on theta@anl5.6 (Fall 2018)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/18476Application bundle icon missing on macOS2018-10-02T21:31:24-04:00Cory Quammencory.quammen@kitware.comApplication bundle icon missing on macOSSomewhere along the way since 5.5.2 we lost the macOS application icon:
![image](/uploads/e08ee0178371ec5862b01544a26ac3c9/image.png)Somewhere along the way since 5.5.2 we lost the macOS application icon:
![image](/uploads/e08ee0178371ec5862b01544a26ac3c9/image.png)5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18473Release ParaView 5.6.0-RC22018-10-02T20:46:51-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.6.0-RC2# Preparatory steps
- Update ParaView guides
- [x] User manual
- [x] Rename to ParaViewGuide-5.6.0-RC2.pdf
- [x] Upload to www.paraview.org/files/v5.6
- [x] Catalyst Guide
- [x] Rename to ParaViewCatalystGuid...# Preparatory steps
- Update ParaView guides
- [x] User manual
- [x] Rename to ParaViewGuide-5.6.0-RC2.pdf
- [x] Upload to www.paraview.org/files/v5.6
- [x] Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.6.0-RC2.pdf
- [x] Upload to www.paraview.org/files/v5.6
- [x] Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.6.0-RC2.pdf
- [x] Upload to www.paraview.org/files/v5.6
- [ ] Assemble release notes into Documentation/release/ParaView-5.6.0-RC2.
- [ ] Get positive review and merge.
# Update ParaView
If making a release from the `release` branch, e.g., `v5.6.0-RC2 or above`:
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.6.0-RC2
echo 5.6.0-RC2 > version.txt
git commit -m 'Update version number to 5.6.0-RC2' version.txt
git tag -a -m 'ParaView 5.6.0-RC2' v5.6.0-RC2 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.6.0-RC2:release v5.6.0-RC2`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --zip -v v5.6.0-RC2`)
- [x] Catalyst (`Catalyst/generate-tarballs.sh v5.6.0-RC2`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.6/`
# Update ParaView-Superbuild
If making a release from the `release` branch, e.g., `v5.6.0-RC2 or above`:
- Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
```
- Update `CMakeLists.txt`
- [x] `git checkout -b update-to-v5.6.0-RC2`
- [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.6.0-RC2" CACHE STRING "Force version to 5.6.0-RC2" 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.6.0-RC2"`
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP
- [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
```
- Finish merge request
- [x] Remove WIP from merge request title
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.6.0-RC2' v5.6.0-RC2 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.6.0-RC2:release v5.6.0-RC2`
# 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
- Upload binaries to `paraview.org`
- [x] `rsync -rptv $binaries paraview.release:ParaView_Release/v5.6/`
- [x] Ask @chuck.atkins to sign macOS binary
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt`
```
buildListing.sh
updateMD5sum.sh v5.6
```
- [x] Test download links
# 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/).
<!--
These items only apply to non-RC releases.
- [ ] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
-->
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18472add .gc as an exodus extension2018-10-02T21:09:21-04:00W. Alan Scottadd .gc as an exodus extensionPlease add .gc as an exodus extension. This is needed for a customer.Please add .gc as an exodus extension. This is needed for a customer.5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18470Parallel Ghost Cell Generator -> Extract Surface bug in 5.6.0-RC12018-12-19T13:33:04-05:00Ethan StamParallel Ghost Cell Generator -> Extract Surface bug in 5.6.0-RC1Tested 5.6.0-RC1 with a local and remote 3 MPI rank pvserver,
Using the data from https://data.kitware.com/#item/5b96a8898d777f43cca36aea
To recreate:
* Load test2.vtm
* Merge Blocks
* GhostCellGenerator with 1 level
* Extract Sur...Tested 5.6.0-RC1 with a local and remote 3 MPI rank pvserver,
Using the data from https://data.kitware.com/#item/5b96a8898d777f43cca36aea
To recreate:
* Load test2.vtm
* Merge Blocks
* GhostCellGenerator with 1 level
* Extract Surface
* Smooth
I get errors in ParaView and the pvserver:
ERROR: In /Users/stam/GitParaVTK/super-recent-master/superbuild/paraview/src/VTK/Common/DataModel/vtkDataSet.cxx, line 468
vtkUnstructuredGrid (0x7fd9c35c39b0): Cell array vtkOriginalCellIds with 1 components, has only 838802 tuples but there are 884356 cells
ERROR: In /Users/stam/GitParaVTK/super-recent-master/superbuild/paraview/src/VTK/Common/DataModel/vtkDataSet.cxx, line 468
vtkUnstructuredGrid (0x7f8a087f8020): Cell array vtkOriginalCellIds with 1 components, has only 3147340 tuples but there are 3160565 cells
ERROR: In /Users/stam/GitParaVTK/super-recent-master/superbuild/paraview/src/VTK/Common/DataModel/vtkDataSet.cxx, line 468
vtkUnstructuredGrid (0x7f884b313e70): Cell array vtkOriginalCellIds with 1 components, has only 11679520 tuples but there are 11716447 cells
I tried to recreate the error with a different vtm dataset. Using one timestep from the YA31 asteroid full res data here: https://oceans11.lanl.gov/deepwaterimpact/yA31.html, I was not able to reproduce the errors.5.6 (Fall 2018)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/18469Change fast uniform grid to output floats2018-10-02T21:42:50-04:00W. Alan ScottChange fast uniform grid to output floatsPlease change Sources/ Fast Uniform Grid to output float data, not double data. We want this code to be fast!
@mwestphal @cory.quammen Setting this to 5.7, so it doesn't impact 5.6. Cory, your choice if it gets done for 5.6.Please change Sources/ Fast Uniform Grid to output float data, not double data. We want this code to be fast!
@mwestphal @cory.quammen Setting this to 5.7, so it doesn't impact 5.6. Cory, your choice if it gets done for 5.6.5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18468can.exo and the new glyph filter interact poorly2018-10-05T12:32:28-04:00W. Alan Scottcan.exo and the new glyph filter interact poorlyHere is how to make the glyph filter not work correctly. The root problem is that the glyph filer/ Properties tab/ Glyph Data Range/ Minimum and Maximum are initialized to 0.0. The issue is that ParaView doesn't work correctly when we ...Here is how to make the glyph filter not work correctly. The root problem is that the glyph filer/ Properties tab/ Glyph Data Range/ Minimum and Maximum are initialized to 0.0. The issue is that ParaView doesn't work correctly when we start Glyph with a timestep that doesn't have any range in the variables.
Here is how to replicate:
* 5.6.0 RC1, Linux, local server.
* Reset session.
* Open can.exo. All vars on. Apply.
* Glyph. Apply. (This will use ACCL for Scale and Orientation.)
* Move forward one timestep.
Notice that you have lots of glyphs all over the place. They should only be at the can/brick interface.
I'm not sure what the "correct thing" to do is.5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18464update diy to latest2018-10-02T21:47:10-04:00Utkarsh Ayachitupdate diy to latestSee diatomic/diy!27See diatomic/diy!275.6 (Fall 2018)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/18440zoom to box border doesn't show2018-09-21T10:26:09-04:00W. Alan Scottzoom to box border doesn't showThe zoom to box border no longer draws. Here is how to replicate:
* 5.6.0-rc1, local server, linux.
* Sources/ Wavelet. Apply.
* Zoom to box. Choose the upper, left corner. Rubber band select the corner.
The zoom box doesn't show! ...The zoom to box border no longer draws. Here is how to replicate:
* 5.6.0-rc1, local server, linux.
* Sources/ Wavelet. Apply.
* Zoom to box. Choose the upper, left corner. Rubber band select the corner.
The zoom box doesn't show! This is a bug.
Note - using RGS.5.6 (Fall 2018)Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/18433Select Points On broken2018-10-04T19:38:45-04:00W. Alan ScottSelect Points On brokenSelect points on is broken. Here is how to replicate:
* 5.6.0-rc1, local server, Linux.
* Start Paraview -dr (or, delete your configuration files.)
* Open Can.exo. Apply.
* +Y
* Select Points On. Now, select a point, middle of the ca...Select points on is broken. Here is how to replicate:
* 5.6.0-rc1, local server, Linux.
* Start Paraview -dr (or, delete your configuration files.)
* Open Can.exo. Apply.
* +Y
* Select Points On. Now, select a point, middle of the can, maybe 1 inch below the top of the can. Nothing is selected.
* If you rubber band select, you will also get no selection.
* Amazingly, selections work for Solid Color, and also Wireframe.
Showstopper for 5.6.0 release.5.6 (Fall 2018)Ken MartinKen Martinhttps://gitlab.kitware.com/paraview/paraview/-/issues/184275.6 RC1 has proxy problem with Catalyst and ADIOSWriter2018-10-04T20:53:35-04:00Jean M. Favre5.6 RC1 has proxy problem with Catalyst and ADIOSWriter/local/apps/ParaView/ParaView-v5.6.0Build/bin/paraview
Warning: In /local/apps/ParaView/ParaView-v5.6.0-RC1/ParaViewCore/ServerManager/Core/vtkSMProxy.cxx, line 1705
vtkSMWriterProxy (0x556bb214e7f0): Failed to locate property 'CatalystW.../local/apps/ParaView/ParaView-v5.6.0Build/bin/paraview
Warning: In /local/apps/ParaView/ParaView-v5.6.0-RC1/ParaViewCore/ServerManager/Core/vtkSMProxy.cxx, line 1705
vtkSMWriterProxy (0x556bb214e7f0): Failed to locate property 'CatalystWriteFrequency' on subproxy 'CatalystOptions': ADIOSWriter
Warning: In /local/apps/ParaView/ParaView-v5.6.0-RC1/ParaViewCore/ServerManager/Core/vtkSMPropertyGroup.cxx, line 197
vtkSMPropertyGroup (0x556bb217fcb0): Failed to locate property 'CatalystWriteFrequency' for PropertyGroup. Skipping.
Warning: In /local/apps/ParaView/ParaView-v5.6.0-RC1/ParaViewCore/ServerManager/Core/vtkSMProxy.cxx, line 1705
vtkSMWriterProxy (0x556bb0b59820): Failed to locate property 'CatalystWriteFrequency' on subproxy 'CatalystOptions': ADIOSWriter
Warning: In /local/apps/ParaView/ParaView-v5.6.0-RC1/ParaViewCore/ServerManager/Core/vtkSMPropertyGroup.cxx, line 197
vtkSMPropertyGroup (0x556bb08be5b0): Failed to locate property 'CatalystWriteFrequency' for PropertyGroup. Skipping.5.6 (Fall 2018)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/18419LOD appears messed up for remote rendering2018-09-11T21:08:18-04:00W. Alan ScottLOD appears messed up for remote rendering@utkarsh.ayachit @cory.quammen Can one of you guys replicate this?
LOD appears broken for large datasets remote rendering. Here is how to replicate:
* I blew away my configuration files before this test (I believe).
* Master (v5.5.2-9...@utkarsh.ayachit @cory.quammen Can one of you guys replicate this?
LOD appears broken for large datasets remote rendering. Here is how to replicate:
* I blew away my configuration files before this test (I believe).
* Master (v5.5.2-964-g39af75), Linux, remote server (16 ranks).
* Wavelet. Extents as follows (notice the last numbers). This creates a thick bar. Error shows for ALL extents over about this size.
-100, 100
-100, 100
-400, 400
* Apply.
* Now, rotate the object. You will notice that it doesn't decimate, but rather disappears. Upon removing the mouse, object appears again.
I would sure like this for 5.6, but I suppose slipping to 5.7 would be OK.5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18418Add reminder in trace to uncomment ViewSize2018-10-02T21:25:19-04:00W. Alan ScottAdd reminder in trace to uncomment ViewSizePlease add a block right at the top of all traces that show the following. We are having users that are missing this action.
```
# trace generated using paraview version #.#.# (where this is the ParaView version)
#
# SEARCH FOR, AND UN-...Please add a block right at the top of all traces that show the following. We are having users that are missing this action.
```
# trace generated using paraview version #.#.# (where this is the ParaView version)
#
# SEARCH FOR, AND UN-COMMENT THE LINE THAT SAYS renderView1.ViewSize = [#,#] for all batch processing
#
```
OK to slip to 5.7 if necessary.5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18417Categorical color warning in DiskOutRefExample.pvsm2018-10-04T19:32:40-04:00Cory Quammencory.quammen@kitware.comCategorical color warning in DiskOutRefExample.pvsm* Launch ParaView
* Help -> Example Visualizations
* Select the "Exodus II, Clip filter, Stream Tracer filter, ..." example.
* Now click on `disk_out_ref.ex2`. A warning message about "Could not initialize annotations for categorical col...* Launch ParaView
* Help -> Example Visualizations
* Select the "Exodus II, Clip filter, Stream Tracer filter, ..." example.
* Now click on `disk_out_ref.ex2`. A warning message about "Could not initialize annotations for categorical coloring..." comes up.
* Make `disk_out_ref.ex2` visible and then invisible. Click on `disk_out_ref.ex2` again and you won't see the warning.5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18416Release ParaView 5.6-RC12018-09-21T16:24:42-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.6-RC1# Preparatory steps
- Update ParaView guides
- [x] User manual
- [x] Rename to ParaViewGuide-5.6.0-RC1.pdf
- [x] Upload to www.paraview.org/files/v5.6
- [x] Catalyst Guide
- [x] Rename to ParaViewCatalystGuid...# Preparatory steps
- Update ParaView guides
- [x] User manual
- [x] Rename to ParaViewGuide-5.6.0-RC1.pdf
- [x] Upload to www.paraview.org/files/v5.6
- [x] Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.6.0-RC1.pdf
- [x] Upload to www.paraview.org/files/v5.6
- [x] Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.6.0-RC1.pdf
- [x] Upload to www.paraview.org/files/v5.6
- [ ] Assemble release notes into Documentation/release/ParaView-5.6.0-RC1.
- [ ] 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.6.0-RC1
echo 5.6.0-RC1 > version.txt
git commit -m 'Update version number to 5.6.0-RC1' version.txt
git tag -a -m 'ParaView 5.6.0-RC1' v5.6.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`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.6.0-RC1:release v5.6.0-RC1`
- [x] Update kwrobot with the new `release` branch rules
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --zip -v v5.6.0-RC1`)
- [x] Catalyst (`Catalyst/generate-tarballs.sh v5.6.0-RC1`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.6/`
# 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.6.0-RC1`
- [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.6.0-RC1" CACHE STRING "Force version to 5.6.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.6.0-RC1"`
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP
- [x] Build binaries (`Do: test`)
- [ ] 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
```
- Create merge request
- [x] Remove WIP from merge request title
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.6.0-RC1' v5.6.0-RC1 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.6.0-RC1:release v5.6.0-RC1`
- [ ] Update kwrobot with the new `release` branch rules
# Validating binaries
- For each binary, check
- [ ] Getting started guide opens
- [ ] Examples load and match thumbnails in dialog
- [ ] Python
- [ ] `import compiler, 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
- Upload binaries to `paraview.org`
- [x] `rsync -rptv $binaries paraview.release:ParaView_Release/v5.6/`
- [x] Ask @chuck.atkins to sign macOS binary
- [ ] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt`
```
buildListing.sh
updateMD5sum.sh v5.6
```
- [x] Test download links
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [ ] Write and publish blog post with release notes.
<!--
These items only apply to non-RC releases.
- [ ] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
-->
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit5.6 (Fall 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/18400Error when building with Qt 5.6.22018-09-04T21:38:50-04:00Ethan StamError when building with Qt 5.6.2Building on Mac OS High Sierra 10.13.6, commit 08ad7547, and Qt version 5.6.2
Seems like QOverload is not recognized by Qt 5.6.x, is it time for me to upgrade Qt?
[ 97%] Building CXX object Qt/ApplicationComponents/CMakeFiles/pqApplica...Building on Mac OS High Sierra 10.13.6, commit 08ad7547, and Qt version 5.6.2
Seems like QOverload is not recognized by Qt 5.6.x, is it time for me to upgrade Qt?
[ 97%] Building CXX object Qt/ApplicationComponents/CMakeFiles/pqApplicationComponents.dir/pqStatusBar.cxx.o<br/>
[ 97%] Building CXX object Qt/ApplicationComponents/CMakeFiles/pqApplicationComponents.dir/pqStreamingTestingEventPlayer.cxx.o<br/>
/Users/stam/GitParaVTK/super-recent-master/superbuild/paraview/src/Qt/ApplicationComponents/pqSpreadSheetViewDecorator.cxx:255:25: error: use of undeclared identifier 'QOverload'<br/>
 internal.Attribute, QOverload<int>::of(&QComboBox::currentIndexChanged), callback);<br/>
<br/>
/Users/stam/GitParaVTK/super-recent-master/superbuild/paraview/src/Qt/ApplicationComponents/pqSpreadSheetViewDecorator.cxx:255:38: error: expected '(' for function-style cast or type construction<br/>
internal.Attribute, QOverload<int>::of(&QComboBox::currentIndexChanged), callback);<br/>
<br/>
/Users/stam/GitParaVTK/super-recent-master/superbuild/paraview/src/Qt/ApplicationComponents/pqSpreadSheetViewDecorator.cxx:255:41: error: no member named 'of' in the global namespace<br/>
internal.Attribute, QOverload<int>::of(&QComboBox::currentIndexChanged), callback);<br/>
<br/>
3 errors generated.5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18391issues reading legacy VTK files with field data2018-10-16T15:23:46-04:00Utkarsh Ayachitissues reading legacy VTK files with field dataSteps to reproduce:
1. open `multicomb_0.vts` from ParaView Data, Apply
2. create Programmable Filter with following script:
```python
o = dsa.WrapDataObject(self.GetOutputDataObject(0))
o.FieldData.append(numpy.zeros(1), "zeros-1")
o.Fi...Steps to reproduce:
1. open `multicomb_0.vts` from ParaView Data, Apply
2. create Programmable Filter with following script:
```python
o = dsa.WrapDataObject(self.GetOutputDataObject(0))
o.FieldData.append(numpy.zeros(1), "zeros-1")
o.FieldData.append(numpy.zeros(10), "zeros-10")
```
3. save generate data as a legacy vtk file.
4. open the generated file. you'll get errors as follows:
```
ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/source-paraview/VTK/IO/Parallel/vtkPDataSetReader.cxx, line 835
vtkPDataSetReader (0x554d200): Could not seek past field.
ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/source-paraview/VTK/IO/Parallel/vtkPDataSetReader.cxx, line 681
vtkPDataSetReader (0x554d200):
ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/source-paraview/VTK/IO/Parallel/vtkPDataSetReader.cxx, line 685
vtkPDataSetReader (0x554d200): Expecting 'DIMENSIONS' instead of:
```5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachit