ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-06-22T19:38:12-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/17995LoadState documentation is missing2021-06-22T19:38:12-04:00W. Alan ScottLoadState documentation is missingI have a user that is trying to LoadState in Python, and got completely confused. I took a look, and got confused also. Using Python, LoadState documentation is missing and/or out of date. Here is what I mean:
* [x] Load State added f...I have a user that is trying to LoadState in Python, and got completely confused. I took a look, and got confused also. Using Python, LoadState documentation is missing and/or out of date. Here is what I mean:
* [x] Load State added features to allow loading to occur from either directories in the state file, or a specific directory, or specific files. This can now be done in Python. Whoot! This is documented here, at the bottom. https://blog.kitware.com/new-options-when-loading-paraview-state-files/. This is the verbose version, without any detail or explanation. If possible, this blog entry should be edited to say details are in the Users Guide.
* [x] The User Guide has a whole chapter dedicated to Loading State. But, none of the complex commands listed above are explained, or even mentioned. Please document these options, with examples, and explain when they are needed and not needed. This is chapter 8.4. The simpler cases do work correctly - why would anyone ever want the complex versions?
* [x] The Trace Recorder always dumps the complex version. I would rather this command was simpler for the simpler cases, but don't think it is a big deal. Would it be simple to modify the code to write the simple case?
* [x] In Python, I tried help(LoadState). This came up with the following: 'LoadState(filename, connection=None, **extraArgs)'. Not what I am looking for... Shouldn't this filter/command be documented, so users can see a bit of usage? Or, did I do this wrong?
@utkarsh.ayachit @cory-quammen @shawn.waldon
Thanks guys!5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17856Python state files should set the backwards compatibility version2021-11-09T13:35:30-05:00Shawn WaldonPython state files should set the backwards compatibility versionIf a python state file is written out and then loaded into a newer version of ParaView, it will fail unless the user edits the state file to add the compatibility version. All that has to be added is this:
```
import paraview
paraview....If a python state file is written out and then loaded into a newer version of ParaView, it will fail unless the user edits the state file to add the compatibility version. All that has to be added is this:
```
import paraview
paraview.compatibility.major = 5
paraview.compatibility.minor = 4
```
I think ParaView should add this automatically when saving out a Python state file so that the state files are forwards compatible with newer versions (until those backwards compatibility options are no longer supported).
@utkarsh.ayachit @cory-quammen5.10 (Fall 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17660Name-preserving `Group Datasets` filter2022-09-20T06:19:36-04:00Utkarsh AyachitName-preserving `Group Datasets` filterSteps:
* open several files (doesn't matter which) or create mutiple sources.
* next group all of them using "Group Datasets".
While now you can apply filters to the group collectively, the names used for each of the source in the pipel...Steps:
* open several files (doesn't matter which) or create mutiple sources.
* next group all of them using "Group Datasets".
While now you can apply filters to the group collectively, the names used for each of the source in the pipeline browser are not preserved in the multiblock structure and hence one cannot effectively use the Multblock Inspector to control block visibilities etc.
We need a "Group Dataset" mode where the names for inputs are preserved.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/17343Icons are too small2022-01-10T06:15:11-05:00W. Alan ScottIcons are too smallWith ParaView 5.3.0, icons became much smaller. Users are complaining (and I agree) that they are now hard to find. Please increase their size to what we had before. Further, the icons for selection really are an eye test for anyone o...With ParaView 5.3.0, icons became much smaller. Users are complaining (and I agree) that they are now hard to find. Please increase their size to what we had before. Further, the icons for selection really are an eye test for anyone older than 40. Could we increase their size somewhat?
Related issues: #15922, #18235.5.10 (Fall 2021)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/16800Color palettes and undo/redo causes crash2021-06-22T21:53:17-04:00Kitware RobotColor palettes and undo/redo causes crash**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16800). Further discussion may take place here.**
---
Color palettes are not behaving correctly with the undo/redo feature. It i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16800). Further discussion may take place here.**
---
Color palettes are not behaving correctly with the undo/redo feature. It is causing lots of bizarre behavior including crashes. To replicate, do the following:
1. Create a Cylinder source. Apply.
2. Hit undo until you reach the end of the stack.
3. Hit redo until you reach the end of the stack.
4. Change the color palette to Black Background
When you change the color palette to Black Background, ParaView crashes. (I can replicate this on Windows and Mac.)
There is other weird behavior that is probably related. For example, if you follow steps 1-3 and then go to settings, the Color Palette tab is missing.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/16038Block ID selection in Find Data does nothing2021-11-09T16:36:37-05:00Kitware RobotBlock ID selection in Find Data does nothing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16038). Further discussion may take place here.**
---
On some selections in the Find Data dialog box, there is a criterium line ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16038). Further discussion may take place here.**
---
On some selections in the Find Data dialog box, there is a criterium line that allows you to select the Block ID. This selection seems to do nothing. To replicate, do the following:
1. Open can.ex2. Turn on all variables. Apply.
2. Open the Find Data dialog.
3. Set the top row to "Cell(s)" from "can.ex2" (the default).
4. Set the first criterium to "ID" "is >=" "0"
5. When you select ID as the thing to select, a second criterium line appears. Set this to "Block ID" "is" "2"
6. Click "Run Selection Query"
You can see that both blocks (numbered 2 and 3) are selected instead of just block 2.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/15757Color palette weirdnesses2021-06-22T21:59:47-04:00Kitware RobotColor palette weirdnesses**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15757). Further discussion may take place here.**
---
We are seeing color palette weirdness's. This needs to be fixed.
* Start...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15757). Further discussion may take place here.**
---
We are seeing color palette weirdness's. This needs to be fixed.
* Start by deleting your config files.
* ParaView 4.4.0, Linux, local server.
<<Bug 1>>
* Color Palette icon. Change to gradient background.
* Edit current palette.
* Change background color to white. OK, OK. All is fine.
* Color Palette icon. Change to black background.
* Color Palette icon. Change to gradient background.
The white color was not remembered. This is a bug.
* Exit ParaView, restart ParaView.
* The gradient background now looks as it should, dark blue top, white bottom.
Once again, delete your config files.
<<Bug 2>>
* Properties tab, change Background to Gradient.
* On the Color palette icon, change to white background.
We are still in Gradient mode. This is a bug.
Bottom color correctly changes to white, top color stays dark blue. This is a bug.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/15459Add animation controls for the Slice representation2020-12-02T16:36:03-05:00Kitware RobotAdd animation controls for the Slice representation**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15459). Further discussion may take place here.**
---
I want to animate the location of the slice when displaying by the slice r...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15459). Further discussion may take place here.**
---
I want to animate the location of the slice when displaying by the slice representation. Please add it.
This can be demonstrated by creating a stack of the same tiff, or the turtle dataset that Utkarsh has.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/15454Gradient background and print background don't work properly2021-06-22T14:44:03-04:00Kitware RobotGradient background and print background don't work properly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15454). Further discussion may take place here.**
---
* Linux, master, local server.
* Sources/ sphere. Apply.
* Change backgro...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15454). Further discussion may take place here.**
---
* Linux, master, local server.
* Sources/ sphere. Apply.
* Change background to gradient.
* File/ Save Screenshot. Use Print Pallet.
The picture won't have a white background, rather it will look like a weird gradient.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/15037Wiki - show how to start a remote server2022-01-18T17:31:12-05:00Kitware RobotWiki - show how to start a remote server**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15037). Further discussion may take place here.**
---
Please update the wiki to show the very common case where a local client c...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15037). Further discussion may take place here.**
---
Please update the wiki to show the very common case where a local client connects to a remote server. This remote server should be automatically started (not manually started by the user). Further, the server actually gets started from a login node. Use reverse connect, since this is very common. Add a second example, where ports are forwarded. (This one is complex.) Ask me for details, if needed.
The executive summary is as follows:
* A local script will ssh into the remote cluster login node, and run a server script. The local script will then start paraview, waiting for a connection.
* The remote script (running on the login node) will write an auto-generated script, written into /tmp. It then does a qsub, with this auto-gen script as input.
* The auto-gen script is now being run on the compute nodes, and starts pvserver with correct arguments.
For the case of port forwarding reverse connect, the only way I have ever gotten this to work is to have the cluster side script start an ssh back to the client machine. The issue here is that the client doesn't know what the compute node names will be when it starts - only the compute nodes know their names.
For the case of port forwarding forward connect, it is crazy. The client doesn't know the name of compute node 0, so you have to start the servers first. That cluster script then figures out it's node 0 name, and sends that back to the client side (I have done this as s scp file). After waiting an appropriate number of seconds (or some type of polling loop), have the client side read the compute node 0 name, and connect to it.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/14977add selection support for selection by location2021-04-22T21:39:27-04:00Kitware Robotadd selection support for selection by location**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14977). Further discussion may take place here.**
---
add selection support for selection by location. We lost this when we lost...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14977). Further discussion may take place here.**
---
add selection support for selection by location. We lost this when we lost the Selection inspector.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/13998Spreadsheet View and Labels can cause errors on occasion.2021-04-16T19:35:54-04:00Kitware RobotSpreadsheet View and Labels can cause errors on occasion.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13998). Further discussion may take place here.**
---
* Open can.ex2, all variables, apply
* Open Find Data dialog and create a ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13998). Further discussion may take place here.**
---
* Open can.ex2, all variables, apply
* Open Find Data dialog and create a cell selection (any selection would do, I just created a global id selection with cell #12)
* Create selection and then label with EQPS.
* Create spread sheet view to show the can.ex2
* Now simply click in the spreadsheet view, on any of the rows to create a new selection, you;ll get the following errors:
Warning: In /Users/utkarsh/Kitware/ParaView/ParaView/VTK/Rendering/Label/vtkLabeledDataMapper.cxx, line 442
vtkLabeledDataMapper (0x126cbe0b0): Could not find label array (EQPS) in input.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/13179Individual file open not possible of multiple file dataset2021-10-20T04:31:18-04:00Kitware RobotIndividual file open not possible of multiple file dataset**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13179). Further discussion may take place here.**
---
We cannot open an individual file of a multiple file dataset. For instanc...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13179). Further discussion may take place here.**
---
We cannot open an individual file of a multiple file dataset. For instance, (and this is true for any multiple file dataset), file open, then go to z_pinch1. If you click on the + sign, I see the following:
z_pinch1.exo.8
z_pinch1.exo.8.0
What I expect to see is as follows:
z_pinch1.exo.8
z_pinch1.exo.8.0
z_pinch1.exo.8.1
z_pinch1.exo.8.2
z_pinch1.exo.8.3
z_pinch1.exo.8.4
z_pinch1.exo.8.5
z_pinch1.exo.8.6
z_pinch1.exo.8.7
Found on git master, Linux, local server.
I am leaving this normal priority, but it would be really nice to have.5.10 (Fall 2021)https://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/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/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/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/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/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 Ayachit