ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-06-09T20:28:14-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/13871Add annotate time feature to 2d plots2020-06-09T20:28:14-04:00Kitware RobotAdd annotate time feature to 2d plots**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13871). Further discussion may take place here.**
---
A user has asked that we add the annotate time filter type of functionalit...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13871). Further discussion may take place here.**
---
A user has asked that we add the annotate time filter type of functionality to the 2d plots. This includes placing annotate time at a different location than the title. It also includes the ability to change the font size, color, etc.5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/12425Upgrade Exodus version to support long names2020-06-16T21:24:39-04:00Kitware RobotUpgrade Exodus version to support long names**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12425). Further discussion may take place here.**
---
Upgrade Exodus version to support long names**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12425). Further discussion may take place here.**
---
Upgrade Exodus version to support long names5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/12340Allow Sources/ Text on 2d windows2020-07-01T07:32:23-04:00Kitware RobotAllow Sources/ Text on 2d windows**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12340). Further discussion may take place here.**
---
Create a sphere, then a Plot over line filter. We should be able to add a...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12340). Further discussion may take place here.**
---
Create a sphere, then a Plot over line filter. We should be able to add a text message on top of this 2d window.5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/12322Exodus reader does not deal with attributes, but needs to.2020-06-29T20:32:07-04:00Kitware RobotExodus reader does not deal with attributes, but needs to.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12322). Further discussion may take place here.**
---
The Exodus reader needs to fully implement attributes. It is half way the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12322). Further discussion may take place here.**
---
The Exodus reader needs to fully implement attributes. It is half way there, but seems to never have been finished. Attributes are variables that are specific to a block, with no time data. They are basically per cell or point input data to the upstream physics packages that is then passed through. An example would be the thickness of the sheet metal on the blocks representing the skin of a car. As with this example, the engine would not have attributes (the engine has no thickness), but could have other attributes (percent aluminum, or some stress tensor, etc).
ParaView needs to deal with the case where these blocks are split across multiple files, and for files that don't include any cells for a block, there is no attribute data. I have seen cases where the number of attributes is different (but not zero) between blocks.
Please just create a union of all attributes. For blocks that don't have an attribute (for instance an engine and skin thickness), please fill with NaN.
This has already been implemented in EnSight numerous years ago, and is an issue with these people moving to ParaView. See attached screenshot from EnSight. In the attached picture, red is attributes, blue is the underlying color.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/12187Crash in Exodus reader's ReadMetaDataFile2020-06-29T20:33:45-04:00Kitware RobotCrash in Exodus reader's ReadMetaDataFile**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12187). Further discussion may take place here.**
---
I have a .bin file that I want to open with the raw image reader. Paravie...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12187). Further discussion may take place here.**
---
I have a .bin file that I want to open with the raw image reader. Paraview doesn't recognize the .bin extension though, so it presents me with a list of readers to choose from. In order to compile the list of available readers, paraview calls CanReadFile("test.bin") on every reader. When it gets to the vtkExodusFileSeriesReader there is a crash.
It goes:
1) vtkFileSeriesReader::CanReadFile("test.bin")
2) if (this->UseMetaFile) <-- true
3) vtkFileSeriesReader::ReadMetaDataFile("test.bin")
This routine opens test.bin as an ifstream and reads the contents into a std::string: metafile >> fname;
Now fname contains garbage, because this is a raw image file.
4) vtkExodusIIReader::CanReadFile(<garbage>)
This routine fails to open the file, tries to create an error message and calls strcpy on the garbage value and crashes.
So this can be avoided if we check that metafile >> fname reads only ascii characters. One solution is adding:
for (size_t i = 0; i < fname.size(); ++i)
{
if (static_cast<unsigned char>(fname[i]) > 127)
{
return 0;
}
}
Is it ok to call metafile >> fname on binary files? We could read metafile character by character instead of checking fname after the fact. Are there any scenarios where metafile uses a non ascii text encoding that should be supported?5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20677Release ParaView 5.9.1-RC2 (source and tags only)2021-04-29T13:05:29-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.9.1-RC2 (source and tags only)# Update ParaView
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
...# Update ParaView
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.9.1-RC2
echo 5.9.1-RC2 > version.txt
git commit -m 'Update version number to 5.9.1-RC2' version.txt
git tag -a -m 'ParaView 5.9.1-RC2' v5.9.1-RC2 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] `Do: merge`
- Integrate changes to `release` branch (push the `update-to-v5.9.1-RC2` branch to be the new `release` branch)
- [x] `git push origin update-to-v5.9.1-RC2:release`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.9.1-RC2`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs user@host:ParaView_Release/v5.9/`
# Update ParaView-Superbuild
- [x] Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
git checkout -b update-to-v5.9.1-RC2
```
- Update `CMakeLists.txt`
- [x] Update PARAVIEW_VERSION_DEFAULT to the release version (without RC*)
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] `paraview_SOURCE_SELECTION` version in `README.md`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.9.1-RC2
- [x] ARG SUPERBUILD_TAG=v5.9.1-RC2
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.9
- [x] Commit changes and push to GitLab
```
git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile
git commit -m "Update the default version to 5.9.1-RC2"
git gitlab-push
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release` to description)
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.9.1-RC2' v5.9.1-RC2 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.9.1-RC2:release`
# Update web site
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website
```
buildListing.sh
updateMD5sum.sh v5.9
```
- [x] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.9.1-RC2`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.9.1-RC2`.
# 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.gueunet5.9.1 (Spring 2021)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20556Background black with volume rendering2021-04-08T22:19:18-04:00W. Alan ScottBackground black with volume renderingWe have an intermitent black background occuring with split views, remote server, volume rendering (unfortunately). Here is how to replicate. State file attached, along with a good, and bad screenshot.
* Linux, 5.9.0, remote server. ...We have an intermitent black background occuring with split views, remote server, volume rendering (unfortunately). Here is how to replicate. State file attached, along with a good, and bad screenshot.
* Linux, 5.9.0, remote server. (I tried local server, did not replicate.) (16 ranks, I bet 2 shows it.)
* Load g1s1.e.16.[0-15]. All vars on. Apply.
* Merge Blocks. Apply.
* Split views vertically. Turn on the Merge blocks in this view.
* Last timestep. Back one timestep.
* Paint with displ, then Volume Render.
* View. Animation View. Change to Sequence. Change max steps to 500.
* Save Animation. .jpg's. OK. Save all views. OK.
Now, a few of these frames will have a black lower view. Note that it appears to be the screen clear, as rendering IS going on.
Note to developers - Talk to Utkarsh about this one. We will decide if fixes go into 5.9.1 or 5.10, depending on how disruptive it is.5.9.1 (Spring 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20483Annotate Global Data filter incorrect for integers2021-03-23T12:14:57-04:00Boonthanome NouanesengsyAnnotate Global Data filter incorrect for integersIn the Annotate Global Data filter, the default Format string is "%7.5g". If a field data has the value 1, then in Paraview 5.8.1, the annotation would show 1. In Paraview 5.9.0, the annotation now shows 0. In python, the output of `"%7....In the Annotate Global Data filter, the default Format string is "%7.5g". If a field data has the value 1, then in Paraview 5.8.1, the annotation would show 1. In Paraview 5.9.0, the annotation now shows 0. In python, the output of `"%7.5g" % 1` is 1, so this looks like a bug.
Here is a test dataset: [wavelet.vti](/uploads/dc4eb224042e5c24881336af76b3d817/wavelet.vti)
To reproduce:
- Open the file in Paraview 5.9.0, and create an Annotate Global Data Filter
- Hit Apply, and the annotation will show 0, but the actual value of the field data is 1
Edit: I just tried this on the latest master, and with master the annotation says 6.9531e-310.
@patchett2002 @cory.quammen @utkarsh.ayachit
![screenshot](/uploads/1ee2c6a21c6ce8de0daf510efcd675fd/screenshot.png)5.9.1 (Spring 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20462vtkOSPRayMaterialLibrar error prints2021-04-26T19:57:22-04:00W. Alan ScottvtkOSPRayMaterialLibrar error printsThis error is showing in the 5.9.0 release, without OSPRay turned on. 5.9.0 release, paraview.org download client, Linux, remote server.
Showing up client side, after connecting to the server.
```
( 14.440s) [paraview ]vtkO...This error is showing in the 5.9.0 release, without OSPRay turned on. 5.9.0 release, paraview.org download client, Linux, remote server.
Showing up client side, after connecting to the server.
```
( 14.440s) [paraview ]vtkOSPRayMaterialLibrar:280 ERR| vtkOSPRayMaterialLibrary (0x152b6dd0): JSON parsing error: * Line 1, Column 1
Syntax error: value, object or array expected.
ERROR: In /builds/gitlab-kitware-sciviz-ci/build/superbuild/paraview/src/VTK/Rendering/RayTracing/vtkOSPRayMaterialLibrary.cxx, line 280
vtkOSPRayMaterialLibrary (0x152b6dd0): JSON parsing error: * Line 1, Column 1
Syntax error: value, object or array expected.
```
Note that I CANNOT hide this one from users.5.9.1 (Spring 2021)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/20459VisRTXBackend.cxx error prints2021-04-26T20:13:42-04:00W. Alan ScottVisRTXBackend.cxx error printsI am seeing dozens of the following errors with the 5.9.0 release, Linux, download from the Kitware website, builtin server. There are 38 error lines. This needs to be fixed, at least in 5.9.1.
```
( 2.011s) [paraview ] ...I am seeing dozens of the following errors with the 5.9.0 release, Linux, download from the Kitware website, builtin server. There are 38 error lines. This needs to be fixed, at least in 5.9.1.
```
( 2.011s) [paraview ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.034s) [paraview ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.034s) [paraview ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.034s) [paraview ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
```5.9.1 (Spring 2021)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20443Cinemasci server not working with 5.9.0-RC42021-02-18T10:09:47-05:00Ethan StamCinemasci server not working with 5.9.0-RC4@utkarsh.ayachit @dhr is aware and working on a fix. If this can still make it into 5.9.0, that would be great. Thanks.
Steps to reproduce:
1. Download and install 5.9.0-RC4 from paraview.org
2. Run the cinemasci server (no cinema datab...@utkarsh.ayachit @dhr is aware and working on a fix. If this can still make it into 5.9.0, that would be great. Thanks.
Steps to reproduce:
1. Download and install 5.9.0-RC4 from paraview.org
2. Run the cinemasci server (no cinema database needed to reproduce) with `/Applications/ParaView-5.9.0-RC4.app/Contents/bin/pvpython -m paraview.tpl.cinemasci.server`
```console
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Traceback (most recent call last):
File "/Applications/ParaView-5.9.0-RC4.app/Contents/Libraries/lib/python3.8/runpy.py", line 185, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/Applications/ParaView-5.9.0-RC4.app/Contents/Libraries/lib/python3.8/runpy.py", line 144, in _get_module_details
return _get_module_details(pkg_main_name, error)
File "/Applications/ParaView-5.9.0-RC4.app/Contents/Libraries/lib/python3.8/runpy.py", line 111, in _get_module_details
__import__(pkg_name)
File "/Applications/ParaView-5.9.0-RC4.app/Contents/Python/paraview/tpl/cinemasci/server/__init__.py", line 14, in <module>
import cinemasci
ModuleNotFoundError: No module named 'cinemasci'
```5.9.1 (Spring 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20612VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx std:array's don'...2021-04-27T13:09:37-04:00Ethan StamVTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx std:array's don't compile with gcc 5.3.0@cory.quammen @utkarsh.ayachit
We are trying to compile paraview with gcc-5.3.0 in Spack.
Using this gcc version, I got this error at around 54% into paraview:
```console
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnew...@cory.quammen @utkarsh.ayachit
We are trying to compile paraview with gcc-5.3.0 in Spack.
Using this gcc version, I got this error at around 54% into paraview:
```console
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnewzxlnodgnu6aeeylkumv3/spack-src/VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx:99:64: error: array must be initialized with a brace-enclosed initializer
std::array<char, 4> StringTypeFormats = { 'c', 'C', 's', 'S' };
^
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnewzxlnodgnu6aeeylkumv3/spack-src/VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx:99:64: error: too many initializers for 'std::array<char, 4ul>'
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnewzxlnodgnu6aeeylkumv3/spack-src/VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx:100:70: error: array must be initialized with a brace-enclosed initializer
std::array<char, 2> StringTypes = { VTK_STRING, VTK_UNICODE_STRING };
^
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnewzxlnodgnu6aeeylkumv3/spack-src/VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx:100:70: error: too many initializers for 'std::array<char, 2ul>'
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnewzxlnodgnu6aeeylkumv3/spack-src/VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx:101:83: error: array must be initialized with a brace-enclosed initializer
std::array<char, 8> FloatTypeFormats = { 'a', 'A', 'e', 'E', 'f', 'F', 'g', 'G' };
^
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnewzxlnodgnu6aeeylkumv3/spack-src/VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx:101:83: error: too many initializers for 'std::array<char, 8ul>'
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnewzxlnodgnu6aeeylkumv3/spack-src/VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx:102:59: error: array must be initialized with a brace-enclosed initializer
std::array<int, 2> FloatTypes = { VTK_FLOAT, VTK_DOUBLE };
^
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnewzxlnodgnu6aeeylkumv3/spack-src/VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx:102:59: error: too many initializers for 'std::array<int, 2ul>'
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnewzxlnodgnu6aeeylkumv3/spack-src/VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx:103:76: error: array must be initialized with a brace-enclosed initializer
std::array<char, 6> IntegralTypeFormats = { 'd', 'i', 'o', 'u', 'x', 'X' };
^
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnewzxlnodgnu6aeeylkumv3/spack-src/VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx:103:76: error: too many initializers for 'std::array<char, 6ul>'
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnewzxlnodgnu6aeeylkumv3/spack-src/VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx:106:43: error: array must be initialized with a brace-enclosed initializer
VTK_LONG_LONG, VTK_UNSIGNED_LONG_LONG };
^
/tmp/stam/spack-stage/spack-stage-paraview-master-6zgs7q3gnnewzxlnodgnu6aeeylkumv3/spack-src/VTKExtensions/FiltersGeneral/vtkAnnotateGlobalDataFilter.cxx:106:43: error: too many initializers for 'std::array<char, 12ul>'
```
I did some googling, and this may be related to [this old gcc bug](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65815)5.9.1 (Spring 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20733ParaView Guide doc generation failing for v5.9.1 tag2021-05-22T13:59:55-04:00Cory Quammencory.quammen@kitware.comParaView Guide doc generation failing for v5.9.1 tagThere are failures on readthedocs.org when generating the v5.9.1 documentation. See https://readthedocs.org/projects/paraview/builds/13772617/ for details.There are failures on readthedocs.org when generating the v5.9.1 documentation. See https://readthedocs.org/projects/paraview/builds/13772617/ for details.5.9.1 (Spring 2021)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20620package module_mpi with the linux binaries2021-06-24T11:54:21-04:00David E. DeMarlepackage module_mpi with the linux binaries5.9.0 PVSB can build OSPRay's module MPI extension, but Kitware's binaries do not have it turned on. If the Linux binaries included it users could very easily use it (via environment variables no less) to accelerate high fidelity renderi...5.9.0 PVSB can build OSPRay's module MPI extension, but Kitware's binaries do not have it turned on. If the Linux binaries included it users could very easily use it (via environment variables no less) to accelerate high fidelity rendering on clusters like so:
> export OSPRAY_LOAD_MODULES=mpi
> export OSPRAY_DEVICE=mpiOffload
> mpiexec -n 1 paraview --no-mpi : -n <NUMNODES> ospray_mpi_worker5.9.1 (Spring 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20615Backports for 5.9.12021-04-19T13:09:33-04:00Cory Quammencory.quammen@kitware.comBackports for 5.9.1These MRs should be backported to ParaView's `release` branch in preparation for 5.9.1:
* [x] https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4792
* [x] https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4789
* ...These MRs should be backported to ParaView's `release` branch in preparation for 5.9.1:
* [x] https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4792
* [x] https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4789
* [x] https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4704
* [x] https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4796
* [x] https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4853
* [x] !4743
* [x] !4894
ParaView superbuild backports for 5.9.1:
* [x] https://gitlab.kitware.com/paraview/paraview-superbuild/-/merge_requests/852
* [x] https://gitlab.kitware.com/paraview/paraview-superbuild/-/merge_requests/857
These VTK MRs should be backported to VTK's `paraview/release` branch for ParaView 5.9.1 as well:
* [x] https://gitlab.kitware.com/vtk/vtk/-/merge_requests/7798
* [x] VTK commit 72be1f0fc4a10d5ed679465258e317c9032207a8
* [x] https://gitlab.kitware.com/vtk/vtk/-/merge_requests/7836
* [x] https://gitlab.kitware.com/vtk/vtk/-/merge_requests/7837
* [x] vtk/vtk!7838
* [x] vtk/vtk!78475.9.1 (Spring 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20568ospray offload mode is not working2021-06-24T11:51:02-04:00David E. DeMarleospray offload mode is not workingParaView 5.9's superbuild can enable ospray's module_mpi, but the linux binary does not have it turned on.
More importantly, a local build of the 5.9 tag with it turned on produces what seems to be a good build of everything, but when I...ParaView 5.9's superbuild can enable ospray's module_mpi, but the linux binary does not have it turned on.
More importantly, a local build of the 5.9 tag with it turned on produces what seems to be a good build of everything, but when I run it locally like so: "mpiexec -n 1 ./bin/paraview --no-mpi : -n 1 ./bin/ospray_mpi_worker"
I get a crash.
Does not seem to be MPI threading related, as I am using mpich. There were some issues with ospray's module_mpi around the osp 2.4 tag that might account for this.5.9.1 (Spring 2021)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/20548The error message appears during interactive cell selection with labels turn on2021-04-29T20:17:22-04:00Petr MelnikovThe error message appears during interactive cell selection with labels turn on# Steps to reproduce
1. Open data set can.ex2 from examples
2. Selection Display Inspector / Cell Labels / ID (or any other cell array, it doesn't matter)
3. Turn on Interactive Select Cells
4. Click on cell and move the mouse a little ...# Steps to reproduce
1. Open data set can.ex2 from examples
2. Selection Display Inspector / Cell Labels / ID (or any other cell array, it doesn't matter)
3. Turn on Interactive Select Cells
4. Click on cell and move the mouse a little (if click without moving the error message doesn't appear)
The error message:
`ERROR: In /home/melnikov/repos/paraview/source/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 760
vtkCompositeDataPipeline (0x559dc28fda30): Input for connection index 0 on input port index 0 for algorithm vtkCellCenters(0x559dc25a1140) is of type vtkDataObject, but a vtkDataSet is required.`
![Screenshot_from_2021-03-11_09-38-57](/uploads/0be44631738f9a74811a41fe0ebb4e34/Screenshot_from_2021-03-11_09-38-57.png)5.9.1 (Spring 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20450paraview 5.9.0 fails to build in Fedora Rawhide2021-04-29T21:24:23-04:00Orion Poplawskiparaview 5.9.0 fails to build in Fedora RawhideI've been building successfully the 5.9.0 RCs for a while in Fedora Rawhide, but now 5.9.0 build fails with:
```
[100%] Built target pvpython
make[2]: Leaving directory '/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu'
/usr...I've been building successfully the 5.9.0 RCs for a while in Fedora Rawhide, but now 5.9.0 build fails with:
```
[100%] Built target pvpython
make[2]: Leaving directory '/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu'
/usr/bin/make -f Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/build.make Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/depend
make[3]: Entering directory '/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu'
cd /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /builddir/build/BUILD/ParaView-v5.9.0 /builddir/build/BUILD/ParaView-v5.9.0/Utilities/Sphinx /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/DependInfo.cmake --color=
Dependee "/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/DependInfo.cmake" is newer than depender "/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/depend.internal".
Dependee "/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/depend.internal".
Scanning dependencies of target ParaViewPythonDoc
make[3]: Leaving directory '/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu'
/usr/bin/make -f Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/build.make Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/build
make[3]: Entering directory '/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu'
cd /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx && ../../bin/pvpython --no-mpi /builddir/build/BUILD/ParaView-v5.9.0/Utilities/Sphinx/sphinx_apidoc.py -o /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/Utilities/Sphinx/config /builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu/lib64/paraview/python3.9/site-packages/paraview
make[3]: Leaving directory '/builddir/build/BUILD/ParaView-v5.9.0/x86_64-redhat-linux-gnu'
unknown option --no-mpi
usage: /lib64/vtkpython [option] ... [-c cmd | -m mod | file | -] [arg] ...
Try `python -h' for more information.
Loguru caught a signal: SIGSEGV
Stack trace:
9 0x55f77263d8ae ../../bin/pvpython(+0x28ae) [0x55f77263d8ae]
8 0x7f6ccadbdb75 __libc_start_main + 213
7 0x55f77263e268 ../../bin/pvpython(+0x3268) [0x55f77263e268]
6 0x7f6cc9cba3b3 vtkInitializationHelper::Finalize() + 211
5 0x7f6cc93c64da vtkProcessModule::Finalize() + 314
4 0x7f6cc8a60286 Py_FinalizeEx + 134
3 0x7f6cc8a605f3 _PyThreadState_DeleteExcept + 35
2 0x7f6cc89a996c PyThread_acquire_lock_timed + 220
1 0x7f6cc8479c3d sem_wait + 13
0 0x7f6ccadd3300 /lib64/libc.so.6(+0x3d300) [0x7f6ccadd3300]
( 0.212s) [paraview ] :0 FATL| Signal: SIGSEGV
make[3]: *** [Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/build.make:79: Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc] Segmentation fault (core dumped)
make[2]: *** [CMakeFiles/Makefile2:39505: Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:39512: Utilities/Sphinx/CMakeFiles/ParaViewPythonDoc.dir/rule] Error 2
make: *** [Makefile:10781: ParaViewPythonDoc] Error 2
```
I'm building docs:
```
export LANG=en_US.UTF-8
%make_build ParaViewDoxygenDoc ParaViewPythonDoc
```
after building the serial version of paraview.
Full logs: https://kojipkgs.fedoraproject.org//work/tasks/8138/60518138/build.log5.9.1 (Spring 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20379Pass Arrays filter a bit weird with vtkGhostType2021-05-07T10:31:32-04:00Andrew BauerPass Arrays filter a bit weird with vtkGhostTypeThe Pass Arrays filter has weird behavior with vtkGhostType arrays. If the input dataset has a vtkGhostType array and the user unchecks the vtkGhostType array for the Pass Arrays filter, that array is still in the output. See the attache...The Pass Arrays filter has weird behavior with vtkGhostType arrays. If the input dataset has a vtkGhostType array and the user unchecks the vtkGhostType array for the Pass Arrays filter, that array is still in the output. See the attached pvsm file. [passarrays_vtkghosttype.pvsm](/uploads/47bf0ed7937808e0b4548ae214a35c63/passarrays_vtkghosttype.pvsm)
Note that this happens with other dataset types as well. The original issue was found with an spcth dataset from a multiblock of rectilinear grids. I can't share that dataset though but it appears to happen with more than just vtkUniformGrid datasets.
I know there is the Remove Ghost Information filter which should be used here but am just wondering what is the proper behavior here. I think the new behavior is to allow the user full control of such "special" arrays like vtkGhostType and such. My guess is that this filter should still show the vtkGhostType array (and other special arrays) and allow them to be removed but would probably be fine with not showing special arrays. I'm more just reporting this behavior because of the incorrect behavior to try and get a fix for it.5.9.1 (Spring 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21003PSTLWriter hangs when using 3 or more MPI processors2021-11-15T17:50:33-05:00Spiros TsalikisPSTLWriter hangs when using 3 or more MPI processorsTo replicate, do the following:
* Linux, 5.10.0-RC1, remote server. Use 3 or more ranks.
* Load g1s1-10fps.e.16.00. Apply.
* Extract Surface. Apply.
* File/ Save Data. server hangs
If you cancel the server while it's hanging with `ctrl...To replicate, do the following:
* Linux, 5.10.0-RC1, remote server. Use 3 or more ranks.
* Load g1s1-10fps.e.16.00. Apply.
* Extract Surface. Apply.
* File/ Save Data. server hangs
If you cancel the server while it's hanging with `ctrl+c`, you get the following output
```
Stack trace:
38 0x55d20ba3550e ./pvserver(+0x250e) [0x55d20ba3550e]
37 0x7f3987061b25 __libc_start_main + 213
36 0x55d20ba35490 ./pvserver(+0x2490) [0x55d20ba35490]
35 0x7f39853a2e3f vtkMultiProcessController::BroadcastProcessRMIs(int, int) + 239
34 0x7f39853a2bf8 vtkMultiProcessController::ProcessRMI(int, void*, int, int) + 232
33 0x7f3985a5c4f5 vtkPVSessionCore::ExecuteStreamSatelliteCallback() + 181
32 0x7f3985a5c297 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 247
31 0x7f39855b103d vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
30 0x7f39855b0b4e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 190
29 0x7f39855b0a2d vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 1229
28 0x7f3985f653f3 vtkParallelSerialWriterCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 3267
27 0x7f398349376f vtkParallelSerialWriter::Write() + 63
26 0x7f39852ff8d7 vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 279
25 0x7f39852fe509 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 921
24 0x7f39852a3a9d vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 877
23 0x7f398529de21 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 129
22 0x7f39852a11a9 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 57
21 0x7f39852a6c40 vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 80
20 0x7f39834939f4 vtkParallelSerialWriter::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 420
19 0x7f3983493380 vtkParallelSerialWriter::WriteATimestep(vtkDataObject*) + 1728
18 0x7f3983492665 vtkParallelSerialWriter::WriteAFile(std::string const&, vtkDataObject*) + 501
17 0x7f39852ff8d7 vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 279
16 0x7f39852fe509 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 921
15 0x7f39852a3a9d vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 877
14 0x7f398529de21 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 129
13 0x7f39852a11a9 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 57
12 0x7f39852a6c40 vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 80
11 0x7f39830285d7 vtkReductionFilter::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 103
10 0x7f3983027e2b vtkReductionFilter::Reduce(vtkDataObject*, vtkDataObject*) + 1163
9 0x7f398539863c vtkCommunicator::Gather(vtkDataObject*, std::vector<vtkSmartPointer<vtkDataObject>, std::allocator<vtkSmartPointer<vtkDataObject> > >&, int) + 268
8 0x7f3985397d27 vtkCommunicator::GatherV(vtkDataArray*, vtkDataArray*, vtkSmartPointer<vtkDataArray>*, int) + 103
7 0x7f3985397ba1 vtkCommunicator::GatherV(vtkDataArray*, vtkDataArray*, vtkIdTypeArray*, vtkIdTypeArray*, int) + 433
6 0x7f398539789b vtkCommunicator::GatherV(vtkDataArray*, vtkDataArray*, long long*, long long*, int) + 235
5 0x7f39800aeb7d vtkMPICommunicator::GatherVVoidArray(void const*, void*, long long, long long*, long long*, int, int) + 253
4 0x7f397ffeb010 PMPI_Gatherv + 832
3 0x7f397c128696 mca_pml_ob1_send + 822
2 0x7f397dd2bf5c opal_progress + 44
1 0x7f397c0d2bcc ompi_coll_libnbc_progress + 12
0 0x7f3987076da0 /usr/lib/libc.so.6(
```
This issue was detected when I was trying to solve https://gitlab.kitware.com/paraview/paraview/-/issues/19144.
It might be a result of https://gitlab.kitware.com/paraview/paraview/-/merge_requests/3351 (to be checked).
@utkarsh.ayachit @cory.quammen @wascott5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachit