ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-12-18T12:18:54-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/20398Fix warning and ambiguous typing in vtkSMSessionProxyManager::GetXMLState(std...2020-12-18T12:18:54-05:00chart3388Fix warning and ambiguous typing in vtkSMSessionProxyManager::GetXMLState(std::set<vtkSMProxy *>)The returned pointer is deleted unless it is assigned to a clunky auto. It was deleting my pointer even when I assigned it to vtkSmartPointer<vtkPVXMLElement>.
In the return statement of this method, Clang warns: "prior to the resolutio...The returned pointer is deleted unless it is assigned to a clunky auto. It was deleting my pointer even when I assigned it to vtkSmartPointer<vtkPVXMLElement>.
In the return statement of this method, Clang warns: "prior to the resolution of a defect report against ISO C++11. local variable would have been copied despite being returned by name, due to its not matching the function return type ('vtkSmartPointer<vtkPVXMLElement>' vs 'vtkNew<vtkPVXMLElement>'). Note call 'std::move' explicitly to avoid copying on older compilers". rootElement is declared as vtkNew<vtkPVXMLElement>.
I think we are what they mean by "older compilers". It can be fixed by return std::move(rootElement), but a cleaner style in keeping with VTK would be to declare and initialize rootElement with vtkSmartPointer<>::New(). This way no conversion is inferred by the compiler.chart3388chart3388https://gitlab.kitware.com/paraview/paraview/-/issues/20397Background settings oddities2021-03-24T08:51:21-04:00Mathieu Westphal (Kitware)Background settings odditiesTwo oddities with the background setting saving:
1. Saving settings when not needed
* Open ParaView
* Click on "Save View Settings"
* Close ParaView
* Background settings is being saved in ParaView-UserSettings but has not been changed ...Two oddities with the background setting saving:
1. Saving settings when not needed
* Open ParaView
* Click on "Save View Settings"
* Close ParaView
* Background settings is being saved in ParaView-UserSettings but has not been changed by the user in any way, it should not
2. Saving single color settings doesn't have expected behavior
* Open ParaView
* Set a background color to not default (color1)
* Click on "Save View Settings"
* Close ParaView
* Open ParaView
* Edit->Settings->ColorPallette->Gradient
* Background is changed to a gradient using color1 and another color, this is unexpected.https://gitlab.kitware.com/paraview/paraview/-/issues/20396ResampleToImage with CTH data produces bad output.2021-01-21T13:42:19-05:00Utkarsh AyachitResampleToImage with CTH data produces bad output.Steps:
* in builtin mode, load `ball_and_box.spcth` from ParaView test data; all variables, apply
* create Resample To Image filter, Apply and change to volume rendering, the result has holes
![image](/uploads/3f41434f51b117e8b465beb787...Steps:
* in builtin mode, load `ball_and_box.spcth` from ParaView test data; all variables, apply
* create Resample To Image filter, Apply and change to volume rendering, the result has holes
![image](/uploads/3f41434f51b117e8b465beb78764ce8f/image.png)5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20395Saving transfer function by name other than default not working correctly2020-12-16T10:01:24-05:00Andrew BauerSaving transfer function by name other than default not working correctlyWhen trying to save a transfer function in the GUI by a name other than the default, the name still gets saved as Preset (or Preset # if Preset is already used). Steps to reproduce with ParaView master (roughly around ParaView 5.9 releas...When trying to save a transfer function in the GUI by a name other than the default, the name still gets saved as Preset (or Preset # if Preset is already used). Steps to reproduce with ParaView master (roughly around ParaView 5.9 release candidate 2):
1. Create Wavelet source
2. Make the representation into Volume
3. Bring up the Color Map Editor and edit the default slightly
4. Click on `Save to preset`
5. For `Preset name`, choose something other than the default of `Preset` and click on Ok
The name will be something like `Preset` or `Preset #`.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20394Slice Value Range doesn't update2022-11-01T22:06:00-04:00Andrew BauerSlice Value Range doesn't updateIn ParaView master (roughly around ParaView 5.9 release candidate 2) the `Value Range` is not properly updating for the `Slice` filter, even when clicking the `Reset using current data values` button (though I'm not sure if that's what t...In ParaView master (roughly around ParaView 5.9 release candidate 2) the `Value Range` is not properly updating for the `Slice` filter, even when clicking the `Reset using current data values` button (though I'm not sure if that's what that button is for). To reproduce the issue:
1. Create a Wavelet with Whole Extent [-10, 100, -10, 10, -10, 10]
2. Create a Slice filter
3. Click on the Y Normal
The `Value Range` should be [-17.3205, 17.3205], i.e. the values if the Wavelet Whole Extent was [-10, 10, -10, 10, -10, 10] but is instead [-56.7891,56.7891].Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/20393netCDF Time Annotation Filter not woring anymore ...2021-02-10T11:59:12-05:00Niklas RoebernetCDF Time Annotation Filter not woring anymore ...The netCDF Time Annotation Plugin, that reads out and prints the time values from netCDF files, is not working anymore, probably due to the Python upgrade, as Python was used underneath.
To test, simply open a regular netCDF file, load...The netCDF Time Annotation Plugin, that reads out and prints the time values from netCDF files, is not working anymore, probably due to the Python upgrade, as Python was used underneath.
To test, simply open a regular netCDF file, load the plugin and apply it.https://gitlab.kitware.com/paraview/paraview/-/issues/20392Sphere only scales to about 1024 X 10242021-09-02T23:33:29-04:00W. Alan ScottSphere only scales to about 1024 X 1024Sources/ Sphere only scales to about 1024 X 1024 Phi and Theta. If you continue to increase, Information/ Number of Cells and Number of points stops increasing.
This is an important bug, as Sources/ Sphere is used for performance wor...Sources/ Sphere only scales to about 1024 X 1024 Phi and Theta. If you continue to increase, Information/ Number of Cells and Number of points stops increasing.
This is an important bug, as Sources/ Sphere is used for performance work, when a lot of triangles are needed.5.10 (Fall 2021)Sankhesh JhaveriSankhesh Jhaverihttps://gitlab.kitware.com/paraview/paraview/-/issues/20391Overload PrintXML function to modify a stringstream passed by reference.2021-01-05T11:49:17-05:00chart3388Overload PrintXML function to modify a stringstream passed by reference.Overload PrintXML function to modify a stringstream passed by reference.Overload PrintXML function to modify a stringstream passed by reference.chart3388chart3388https://gitlab.kitware.com/paraview/paraview/-/issues/20390ParaView build from source Mac, hangs on file -> load2021-03-30T13:59:14-04:00Ethan StamParaView build from source Mac, hangs on file -> load@utkarsh.ayachit @cory.quammen
I am still on MacOS 10.14.6, cmake options are enabling python (3.8) and Release instead of Debug. Qt version is 5.12.
Doing File -> Load, File -> Save, Load state all cause the gui to hang. It seems any...@utkarsh.ayachit @cory.quammen
I am still on MacOS 10.14.6, cmake options are enabling python (3.8) and Release instead of Debug. Qt version is 5.12.
Doing File -> Load, File -> Save, Load state all cause the gui to hang. It seems anything that opens a file browser causes a hang.
Steps to reproduce:
1. Build paraview from source (release branch)
- Enable python (3) and choose release instead of debug build
2. File -> load -> pinwheel and have to kill the process
Video (doesn't show the pinwheel, but it's there)
![file-browser-hangs](/uploads/c707673c71b95a8070d1d5aaaa48f6c2/file-browser-hangs.gif)https://gitlab.kitware.com/paraview/paraview/-/issues/20389enforce GetXMLState the saving of a restricted state even if restricted state...2020-12-23T10:49:19-05:00chart3388enforce GetXMLState the saving of a restricted state even if restricted state is emptyenforce GetXMLState the saving of a restricted state even if restricted state is empty. This way if foreRestriction is true the state will still be limited.enforce GetXMLState the saving of a restricted state even if restricted state is empty. This way if foreRestriction is true the state will still be limited.chart3388chart3388https://gitlab.kitware.com/paraview/paraview/-/issues/20388make the Annotate Global Data Filter not depend on numpy2021-02-15T18:42:14-05:00Boonthanome Nouanesengsymake the Annotate Global Data Filter not depend on numpyThe Annotate Global Data Filter currently depends on the python module numpy. This has caused problems for use in the past, as sometimes numpy will not be present in a python, or numpy will cause conflicts with other dependencies. It wou...The Annotate Global Data Filter currently depends on the python module numpy. This has caused problems for use in the past, as sometimes numpy will not be present in a python, or numpy will cause conflicts with other dependencies. It would be nice if the numpy dependency was removed.
@cory.quammen @utkarsh.ayachit @patchett20025.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20387Redundant calculator icon2020-12-16T15:47:24-05:00W. Alan ScottRedundant calculator iconWe have a redundant calculator icon that has appeared in 5.9.0-RC1. One is in the common filters toolbar, the other is in the Data Analysis toolbar. The Data Analysis one is a mistake, and should be removed.
@utkarsh.ayachit @cory.qu...We have a redundant calculator icon that has appeared in 5.9.0-RC1. One is in the common filters toolbar, the other is in the Data Analysis toolbar. The Data Analysis one is a mistake, and should be removed.
@utkarsh.ayachit @cory.quammen Not sure how to schedule this. We are late to remove it, but it should be deleted.https://gitlab.kitware.com/paraview/paraview/-/issues/20386Material volume fraction filter crashes in spreadsheet2021-01-21T13:36:56-05:00W. Alan ScottMaterial volume fraction filter crashes in spreadsheetThe material volume fraction filter crashes when you try to display the data in the spreadsheet. I believe the issue is with the spreadsheet. This works correctly with ParaView 5.8.0. Here is how to replicate:
* 5.9.0-RC2, Linux, rem...The material volume fraction filter crashes when you try to display the data in the spreadsheet. I believe the issue is with the spreadsheet. This works correctly with ParaView 5.8.0. Here is how to replicate:
* 5.9.0-RC2, Linux, remote server (I am using 16 ranks).
* Load Dave's small cth dataset. It will have 4 files. All vars on. Apply.
* Split screen vertical.
* Spreadsheet.
There will be the following warning message. Note that this error message occurs builtin server:
Warning: In /projects/viz/paraview/src/ParaView/5.9.0-RC2/ParaView5/VTK/Common/DataModel/vtkDataObject.cxx, line 498
vtkMultiBlockDataSet (0xc2c5140): Attempted to ShallowCopy from null.
* Close the Spreadsheet View. Close the Output View.
* Material Interface Filter. Only select the "Material volume fraction - 1" variable. Select Mass Arrays: "Mass (g) -1". Apply.
* Split Vertical. Spreadsheet.
Crash. Note this crash does NOT occur builtin server. Server side crash. I am on a release build, could make it debug if desired.
@utkarsh.ayachit @cory.quammen Showstopper bug for the 5.9.0 release.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20385vtkRedistributeDataSet does not handle dataset without cells2021-03-24T08:51:28-04:00Utkarsh AyachitvtkRedistributeDataSet does not handle dataset without cellsIssue surfaced when debugging paraview/paraview#20382. Once fixed, make sure `vtkPointGaussianRepresentation` is updated to avoid creating of vertex-cells.Issue surfaced when debugging paraview/paraview#20382. Once fixed, make sure `vtkPointGaussianRepresentation` is updated to avoid creating of vertex-cells.https://gitlab.kitware.com/paraview/paraview/-/issues/20384ParaView 5.9 RC2 binary Ubuntu 18.04: NVIDIA Optix Pathtracer is not enabled2021-04-19T21:03:45-04:00Dan LipsaParaView 5.9 RC2 binary Ubuntu 18.04: NVIDIA Optix Pathtracer is not enabledParaView 5.8 RC2 binary does not enable NVIDIA Optix on my Ubuntu 18.04. It does work with ParaView 5.8.1 binary.
It might be related to an error I see for nvidia-smi, but as I said it does work for ParaView 5.8.1 binary.
Here is the out...ParaView 5.8 RC2 binary does not enable NVIDIA Optix on my Ubuntu 18.04. It does work with ParaView 5.8.1 binary.
It might be related to an error I see for nvidia-smi, but as I said it does work for ParaView 5.8.1 binary.
Here is the output for nvidia-smi:
<pre>
[~/external/ParaView-5.8.1-MPI-Linux-Python3.7-64bit]$ nvidia-smi
/usr/bin/nvidia-modprobe: unrecognized option: “-s”
ERROR: Invalid commandline, please run /usr/bin/nvidia-modprobe --help for usage information.
/usr/bin/nvidia-modprobe: unrecognized option: “-s”
ERROR: Invalid commandline, please run /usr/bin/nvidia-modprobe --help for usage information.
Thu Dec 10 14:33:56 2020
±----------------------------------------------------------------------------+
| NVIDIA-SMI 450.80.02 Driver Version: 450.80.02 CUDA Version: 11.0 |
|-------------------------------±---------------------±---------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 Quadro M4000 Off | 00000000:03:00.0 On | N/A |
| 49% 47C P0 44W / 120W | 394MiB / 8104MiB | 2% Default |
| | | N/A |
±------------------------------±---------------------±---------------------+
±----------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=============================================================================|
| 0 N/A N/A 3437 G /usr/lib/xorg/Xorg 123MiB |
| 0 N/A N/A 3577 G /usr/bin/gnome-shell 116MiB |
| 0 N/A N/A 5316 C /usr/NX/bin/nxnode.bin 85MiB |
| 0 N/A N/A 13881 G …AAAAAAAA== --shared-files 59MiB |
±----------------------------------------------------------------------------+
[~/external/ParaView-5.8.1-MPI-Linux-Python3.7-64bit]$
</pre>https://gitlab.kitware.com/paraview/paraview/-/issues/20383XML Settings only proxy fails to build because of automatic documentation gen...2021-03-24T08:52:08-04:00Mathieu Westphal (Kitware)XML Settings only proxy fails to build because of automatic documentation generationA plugin containing only a `<SettingsProxy>` fails to build with the following error:
```
<ParaViewPlugin>
<ServerManagerConfiguration>
<ProxyGroup name="settings">
<SettingsProxy name="PacManSettings" label="PacMan"
...A plugin containing only a `<SettingsProxy>` fails to build with the following error:
```
<ParaViewPlugin>
<ServerManagerConfiguration>
<ProxyGroup name="settings">
<SettingsProxy name="PacManSettings" label="PacMan"
processes="client|dataserver|renderserver">
<Documentation>
Settings for the PacMan plugin.
</Documentation>
<IntVectorProperty name="TestOption"
number_of_elements="1"
default_values="0">
<Documentation>
This is a simple boolean test option.
</Documentation>
<BooleanDomain name="bool" />
</IntVectorProperty>
<Hints>
<UseDocumentationForLabels />
</Hints>
</SettingsProxy>
</ProxyGroup>
</ServerManagerConfiguration>
</ParaViewPlugin>
```
```
[ 42%] Compiling Qt help for ReaderXMLOnly
CMake Error at /home/glow/work/paraview/pv3/build/lib/cmake/paraview-5.9/ParaViewClient.cmake:892 (message):
No matching files given without a table of contents
make[2]: *** [Plugin/CMakeFiles/ReaderXMLOnly_qch.dir/build.make:80: Plugin/paraview_help/ReaderXMLOnly.qch] Error 1
make[1]: *** [CMakeFiles/Makefile2:145: Plugin/CMakeFiles/ReaderXMLOnly_qch.dir/all] Error 2
make: *** [Makefile:149: all] Error 2
```
Adding a single dummy `<SourceProxy>` fixes the issue.
Attached is an example to reproduce easily.
[ReaderXMLOnly.tgz](/uploads/bada628f85e7342849d24e1823e8b656/ReaderXMLOnly.tgz)https://gitlab.kitware.com/paraview/paraview/-/issues/20382RC2 is having issues with CGNS and Point Gaussian2020-12-15T12:01:34-05:00W. Alan ScottRC2 is having issues with CGNS and Point GaussianWhen reading the HiFIRE CGNS dataset, and using representation Point Gaussian, it appears that it isn't Z buffering correctly. Here is how to replicate:
* remote server (64 ranks), 5.9.0-RC2, Linux.
* Load the cgns HiFire dataset. I t...When reading the HiFIRE CGNS dataset, and using representation Point Gaussian, it appears that it isn't Z buffering correctly. Here is how to replicate:
* remote server (64 ranks), 5.9.0-RC2, Linux.
* Load the cgns HiFire dataset. I turned all vars on, but not necessary. Apply.
* Point Gaussian.
It will look jumbled.
@utkarsh.ayachit @cory.quammen Not sure if we need to fix this for 5.9.0. Thoughts?5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20381Mac OS/Brew: ccmake does not detect Qt5.152020-12-16T16:38:08-05:00Matthew L.Mac OS/Brew: ccmake does not detect Qt5.15If you installed qt5 via Brew, then you will get this error:
CMake Error at /usr/local/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:15 (message):
The imported target "Qt5::Core" references the file
"/usr/local//mkspecs/macx-clang"
**S...If you installed qt5 via Brew, then you will get this error:
CMake Error at /usr/local/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:15 (message):
The imported target "Qt5::Core" references the file
"/usr/local//mkspecs/macx-clang"
**Solution**: change the qt5_dir to your proper. In my case it was
`/usr/local/Cellar/qt/5.15.2/lib/cmake/Qt5`
Change the location for other generated qt5 as well.
If you have Anaconda installed. Chances are it will pick up qt5.9 from conda, which is not supported. Uninstall qt5.9 from condahttps://gitlab.kitware.com/paraview/paraview/-/issues/20380XDMF: Save -> Load -> Crash2020-12-11T06:41:52-05:00Ken SheldonXDMF: Save -> Load -> CrashObserved in Paraview 5.9.0-RC2 on Windows
1. Create a point set (Sources -> alphabetical -> Point Source, #npoints=100, radius=5)
2. Save data using xdmf or xdmf3 writer
3. Disconnect (delete all data sources)
4. Load the data saved in ...Observed in Paraview 5.9.0-RC2 on Windows
1. Create a point set (Sources -> alphabetical -> Point Source, #npoints=100, radius=5)
2. Save data using xdmf or xdmf3 writer
3. Disconnect (delete all data sources)
4. Load the data saved in step 2.
crash
It makes no difference which writer or which reader you choose.https://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.com