ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-07-16T21:10:12-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/18068pqNamedWidgets documentation still visible in paraview nightly doc2018-07-16T21:10:12-04:00Mathieu Westphal (Kitware)pqNamedWidgets documentation still visible in paraview nightly docpqNamedWidgets [documentation](https://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/classpqNamedWidgets.html) is still accessible and looks like it is an available, up to date class, when it actually have been removed from paraview ...pqNamedWidgets [documentation](https://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/classpqNamedWidgets.html) is still accessible and looks like it is an available, up to date class, when it actually have been removed from paraview quite a long time ago.
This is quite misleading.5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16931Gradient filter should only average values from cells of the same dimensionality2018-07-16T21:09:04-04:00Kenneth MorelandGradient filter should only average values from cells of the same dimensionalityThe Gradient of Unstructured Data Set filter does a local gradient computations in each cell and averages those results on points. Right now, each point averages gradients from all incident cells. However, it is of dubious physical or pr...The Gradient of Unstructured Data Set filter does a local gradient computations in each cell and averages those results on points. Right now, each point averages gradients from all incident cells. However, it is of dubious physical or practical use to combine the gradients of cells of different dimensionality (e.g. mixing 3D polyhedra with 2D polygons).
One place where this comes up is a mesh might combine both internal grid cells and boundary elements. Because gradients use finite differences and boundary elements are flat, the gradient through the boundary elements is not captured and the average incorrectly drops the gradient in that direction. (See, for example, this email thread: http://public.kitware.com/pipermail/paraview/2016-September/038129.html).
Thus, the behavior of the gradient of unstructured data set filter would be closer to what is expected if it determined the highest dimensionality of cells on each point and only averaged gradient values from cells of the highest dimensionality.Andrew BauerAndrew Bauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/17748Add ability to make output of ExtractCTHParts be a 3d solid.2018-07-16T16:55:43-04:00W. Alan ScottAdd ability to make output of ExtractCTHParts be a 3d solid.Please add an option to have the Extract CTH Parts filter return a filled 3d object, rather than a contour. For instance, what I want is for every Volume Array selected, run Cell Data to Point Data, then Clip/ Scalar/ each variable. De...Please add an option to have the Extract CTH Parts filter return a filled 3d object, rather than a contour. For instance, what I want is for every Volume Array selected, run Cell Data to Point Data, then Clip/ Scalar/ each variable. Default off.5.6 (Fall 2018)Shreeraj JadhavShreeraj Jadhavhttps://gitlab.kitware.com/paraview/paraview/-/issues/18288MKL library dependency from Anaconda Python used for Annotate Global Data Filter2018-07-16T16:43:03-04:00John PatchettMKL library dependency from Anaconda Python used for Annotate Global Data FilterFor the in situ ParaView Use Case we have an issue with one of our codes that has an MKL dependency. We are unable to use the AnnotateGlobalDataFilter because that filter uses numpy which in turn uses MKL requiring a version match betwe...For the in situ ParaView Use Case we have an issue with one of our codes that has an MKL dependency. We are unable to use the AnnotateGlobalDataFilter because that filter uses numpy which in turn uses MKL requiring a version match between simulation and in situ library for MKL. This is a new issue in ParaView 5.5 @boonth may be able to fill in missing aspects to this complaint.https://gitlab.kitware.com/paraview/paraview/-/issues/18120optimize cinema exports - threadedImageWriter2018-07-16T16:16:06-04:00David E. DeMarleoptimize cinema exports - threadedImageWriterThe task is to merge Pat and Seb's changes in VTK, Cinema and ParaView that improve cinema export speed.
Speedups of about 2x are expected.The task is to merge Pat and Seb's changes in VTK, Cinema and ParaView that improve cinema export speed.
Speedups of about 2x are expected.David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/18042Cinema database export/import doesn't work2018-07-16T12:57:41-04:00DavidCinema database export/import doesn't workLoad example vis of wavelet. Immediately export->scene save Cinema database without compositing, phi/theta camera, pngs. Export happens. Load Cinema database through File->Import Cinema Database. Database loads, but shows that camera cen...Load example vis of wavelet. Immediately export->scene save Cinema database without compositing, phi/theta camera, pngs. Export happens. Load Cinema database through File->Import Cinema Database. Database loads, but shows that camera center of rotation is wrong (doesn't rotate around center of data, scalar bar moves around, etc.)5.5.1 (Summer 2018)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/17787Crash OpenFOAM reader in Paraview v5.3.0 and greater2018-07-16T05:22:21-04:00Andrew JacksonCrash OpenFOAM reader in Paraview v5.3.0 and greaterI am testing the Paraview 5.3.0 version for Linux (Paraview-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz) on the Suse 13.2 machine and getting a segmentation fault when loading an OpenFOAM case using the native reader. It seems to load ok in...I am testing the Paraview 5.3.0 version for Linux (Paraview-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz) on the Suse 13.2 machine and getting a segmentation fault when loading an OpenFOAM case using the native reader. It seems to load ok in older versions of Paraview.
The crash is not repeatable but should be reproducible by toggling the "Decompose polyhedra" switch a number of times. I have attached a small simplified case that should hopefully be able to reproduce the issue.
Regards
Andrew
[paraview5.3.0.crash.tar.bz2](/uploads/987762006ba6d732149a573bd989024e/paraview5.3.0.crash.tar.bz2)Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/17418Correct Information tab for global data that is a string2018-07-13T14:35:46-04:00W. Alan ScottCorrect Information tab for global data that is a stringThe information tab is incorrect for strings. For instance, load can.exo, which has a Title of "self contact test problem". (You can verify this with the Annotate Global Data filter.) The information tab has Title listed as NA. Pleas...The information tab is incorrect for strings. For instance, load can.exo, which has a Title of "self contact test problem". (You can verify this with the Annotate Global Data filter.) The information tab has Title listed as NA. Please fix this.5.6 (Fall 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/18294batch-mode SaveAnimation using a fixed number of frames?2018-07-13T03:33:47-04:00Jean M. Favrebatch-mode SaveAnimation using a fixed number of frames?I have an issue with writing an animation with a Source that has N timesteps (N **is greate**r than 10)
if running in an interactive session, all N images with be written correctly.
if running in batch, **only 10** frames are written w...I have an issue with writing an animation with a Source that has N timesteps (N **is greate**r than 10)
if running in an interactive session, all N images with be written correctly.
if running in batch, **only 10** frames are written with timesteps which are linearly interpolated between my Tmin and Tmax.
I have created two python files to demonstrate this:
first I generate a time series of *vti files, encoded as a JSON series
`pvpython testSaveAnimation.py > collection.vti.series`
then I read it back and save images.
`pvpython read_collection.py`
Only **10** images are saved and the time labels are not my original time labels.
[read_collection.py](/uploads/4d7c0bf02d0acf19e5e4afc6404921e2/read_collection.py)[testSaveAnimation.py](/uploads/02376b6b21188b4966bc29ccf0718f24/testSaveAnimation.py)
tested with PV5.5.2https://gitlab.kitware.com/paraview/paraview/-/issues/18124Extract CTH Parts cannot be applied to non-down converted volume fraction arrays2018-07-12T21:32:15-04:00Utkarsh AyachitExtract CTH Parts cannot be applied to non-down converted volume fraction arrays1. open any CTH dataset e.g. `ball_and_box.spcth` from ParaView data, select all arrays
2. uncheck **Down Convert Volume Fraction** and then hit Apply
3. now create, **Extract CTH Parts** filter -- no arrays are shown in the **Volume Ar...1. open any CTH dataset e.g. `ball_and_box.spcth` from ParaView data, select all arrays
2. uncheck **Down Convert Volume Fraction** and then hit Apply
3. now create, **Extract CTH Parts** filter -- no arrays are shown in the **Volume Arrays** list.
4. try the same without without unchecking **Down Convert...** on the reader and you get the volume fraction arrays listed correctly.
Issue introduced in a fix for paraview/paraview#178855.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/15629Need option to have color legend placement be sticky2018-07-12T21:25:39-04:00Kitware RobotNeed option to have color legend placement be sticky**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15629). Further discussion may take place here.**
---
We need an option that allows a user to place the color legend one place, ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15629). Further discussion may take place here.**
---
We need an option that allows a user to place the color legend one place, and keep the size and location of the color legend between filters, and between sessions. This is a big deal for one of my users.5.6 (Fall 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/16855`InteractiveViewLinkOffscreen` fails on BigMac with OpenGL2 backend2018-07-12T21:15:14-04:00Utkarsh Ayachit`InteractiveViewLinkOffscreen` fails on BigMac with OpenGL2 backendThe test `InteractiveViewLinkOffscreen` fails on bigmac with OpenGL2 backend with following errors. The test has been excluded on the dashboard.
~~~~
19: Test (0): Event: /menuTools: activate : actionTesting_Window_Size
ERROR: In /...The test `InteractiveViewLinkOffscreen` fails on bigmac with OpenGL2 backend with following errors. The test has been excluded on the dashboard.
~~~~
19: Test (0): Event: /menuTools: activate : actionTesting_Window_Size
ERROR: In /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-debug_clang_gui_opengl2_python/source/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper2D.cxx, line 915
vtkSMTestDriver: ***** Test will fail, because the string: "ERROR:"
vtkSMTestDriver: ***** was found in the following output from the client:
"ERROR: In /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-debug_clang_gui_opengl2_python/source/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper2D.cxx, line 915"
vtkOpenGLPolyDataMapper2D (0x7f8e7a446c80): failed after RenderOverlay 1 OpenGL errors detected
0 : (1286) Invalid framebuffer operation
ERROR: In /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-debug_clang_gui_opengl2_python/source/VTK/Rendering/OpenGL2/vtkOpenGLActor.cxx, line 107
vtkOpenGLActor (0x7f8e7a6069d0): failed after Render 1 OpenGL errors detected
0 : (1286) Invalid framebuffer operation
Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/18205Bad error message in Follow Data2018-07-12T21:14:17-04:00W. Alan ScottBad error message in Follow DataWe have a new, incorrect message with follow data.
* Linux, 5.5.0, built-in server
* File/ open. can.exo. Apply.
* View/ Animation View. Camera. Follow Data. Click the blue +.
Warning messages as follows: (btw, we should NEVER ...We have a new, incorrect message with follow data.
* Linux, 5.5.0, built-in server
* File/ open. can.exo. Apply.
* View/ Animation View. Camera. Follow Data. Click the blue +.
Warning messages as follows: (btw, we should NEVER see warning messages in a release.)
Generic Warning: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, line 641
Call not supported for the current property type.
Generic Warning: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, line 641
Call not supported for the current property type.5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18217State file value precision for the threshold filter2018-07-12T20:47:47-04:00Ghost UserState file value precision for the threshold filterDear maintainers, (@mwestphal)
## Minimal example
Here is a simple VTU file: [Threshold.vtu](/uploads/9c15c10227625365e00920fc8b771509/Threshold.vtu).
It contains two lines associated with a cell data corresponding to their length.
If ...Dear maintainers, (@mwestphal)
## Minimal example
Here is a simple VTU file: [Threshold.vtu](/uploads/9c15c10227625365e00920fc8b771509/Threshold.vtu).
It contains two lines associated with a cell data corresponding to their length.
If you load this data set and apply a *Threshold* filter without changing any value, the data set stay the same.
But now, if you save this in a state file (like [Threshold.pvsm](/uploads/b26d8f22a4019bf7f027dbe8b820b40b/Threshold.pvsm)), quit and load this state, one of the two lines is missing.
## Bug reason
The reason is the maximum value of the *Threshold* which is normally : 4.210691007669084
In the state file, it is saved as: 4.21069100766908. The last digit is dropped and so the real maximum value become greater than the saved one, thus omitting the larger line when loading the state.
Charles5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16926OSPRay surface color mapping is wrong when clipping data range2018-07-12T20:18:11-04:00pggesOSPRay surface color mapping is wrong when clipping data rangeWhen rendering a surface reperesentation colored by data using OSPRay the data to color mapping has errors when rescaling to a custom data range.
Data that is outside the range is not clipped as expected and the color seems to wrap aroun...When rendering a surface reperesentation colored by data using OSPRay the data to color mapping has errors when rescaling to a custom data range.
Data that is outside the range is not clipped as expected and the color seems to wrap around to the other end of the colormap.
How to reproduce:
* Select Wavelet Source
* Color surface representation by RTData
* Rescale to custom data range 10 to 150
* Enable OSPRay rendering5.6 (Fall 2018)Michael FoglemanMichael Foglemanhttps://gitlab.kitware.com/paraview/paraview/-/issues/17682Edit color palette is broken2018-07-12T19:35:36-04:00W. Alan ScottEdit color palette is brokenEdit color palette is broken. We want to change the background. Here is how to replicate:
* Mac, 5.4.1, local server.
* Palette icon. Edit current Palette.
* Click on Color Used for Background for the View.
* Use 90, 90, 90. OK.
* T...Edit color palette is broken. We want to change the background. Here is how to replicate:
* Mac, 5.4.1, local server.
* Palette icon. Edit current Palette.
* Click on Color Used for Background for the View.
* Use 90, 90, 90. OK.
* The Edit current Palette dialog disappears, so you can't click OK! This is a bug.
* The only way around this is to edit the current Palette again, and since the new colors are sticky, say Apply or OK.5.6 (Fall 2018)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/5626Make array calculator operate on field data2018-07-12T19:30:00-04:00Kitware RobotMake array calculator operate on field data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5626). Further discussion may take place here.**
---
The array calculator should be able to operate on field data. I think ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5626). Further discussion may take place here.**
---
The array calculator should be able to operate on field data. I think there are two use cases for this. First, there should be a field data option in addition to point data and cell data that allows the calculator to create a new field data array. Second, there probably should be a way to apply a field data variable to the calculation of point or cell data.5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18243Gaussian cube reader fails when loading state2018-07-12T19:05:45-04:00Utkarsh AyachitGaussian cube reader fails when loading stateWhen loading state file, the gaussian cude reader is causing error. See [discourse](https://discourse.paraview.org/t/error-when-reloading-state-that-opens-a-cube-file/171).When loading state file, the gaussian cude reader is causing error. See [discourse](https://discourse.paraview.org/t/error-when-reloading-state-that-opens-a-cube-file/171).5.6 (Fall 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/18248Catalyst warn about unneeded missing modules2018-07-12T19:01:43-04:00Nicolas VuailleCatalyst warn about unneeded missing modulesSee this on discourse : https://discourse.paraview.org/t/missing-vtkpvservermanagerdefault-and-vtkpvanimation-in-catalyst-edition/192
servermanager.py print error message for missing modules but in catalyst it is not necessary an error.See this on discourse : https://discourse.paraview.org/t/missing-vtkpvservermanagerdefault-and-vtkpvanimation-in-catalyst-edition/192
servermanager.py print error message for missing modules but in catalyst it is not necessary an error.https://gitlab.kitware.com/paraview/paraview/-/issues/18220SaveScreenshot() hangs in pvpython2018-07-12T18:24:03-04:00Boonthanome NouanesengsySaveScreenshot() hangs in pvpythonI'm trying to create a python script that loads a dataset, and outputs an image. In the ParaView gui, I start a python trace, then load the data, then save a screenshot. I stop the trace, and put all of the python commands in a script.
...I'm trying to create a python script that loads a dataset, and outputs an image. In the ParaView gui, I start a python trace, then load the data, then save a screenshot. I stop the trace, and put all of the python commands in a script.
When trying to run the resulting script in pvpython, it seems to hang at SaveScreenshot(). Running pvpython hangs in Paraview 5.5, but the same procedure will work with Paraview 5.4. I've tried this on my machine, and the HCP machines at LANL, and ParaView 5.5 will hang at the same place for both machines.
The script I'm trying to run: [image_vf_pv55.py](/uploads/88116c6d13a867a565ee7c019bf75ded/image_vf_pv55.py)
The dataset I'm loading: [vf.tar](/uploads/b9e70f340906b9222535e73b7e8c6de5/vf.tar)
@patchett2002 @acbauer5.6 (Fall 2018)Allison Vacantialliepiper16@gmail.comAllison Vacantialliepiper16@gmail.com