ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-24T05:34:25-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/19096"Export Inspector" cannot save different resolution images at different feque...2021-03-24T05:34:25-04:00Utkarsh Ayachit"Export Inspector" cannot save different resolution images at different fequenciesUse case:
I want to save high-res PNG images from the same view every 100th frame, but save low-res PNG images from the same view every 10th frame. Currently, this is not supported by the Export Inspector.Use case:
I want to save high-res PNG images from the same view every 100th frame, but save low-res PNG images from the same view every 10th frame. Currently, this is not supported by the Export Inspector.https://gitlab.kitware.com/paraview/paraview/-/issues/19111vtkProcessId is incorectly computed in Outline representation2021-03-24T05:33:29-04:00Mathieu Westphal (Kitware)vtkProcessId is incorectly computed in Outline representationvtkProcessId is computed on the representation of the Geometry when working in Parallel with ParaView, providing then an invalid range which is a bit cumbersome.
How to reproduce :
* run mpirun -np 4 ./bin/pvserver
* ./bin/paraview
...vtkProcessId is computed on the representation of the Geometry when working in Parallel with ParaView, providing then an invalid range which is a bit cumbersome.
How to reproduce :
* run mpirun -np 4 ./bin/pvserver
* ./bin/paraview
* connect to server
* Wavelet, Apply
* Color by vtkProcessId
* **ColorMap is incorrectly ranged from 0 to 1e-38**, visual representation is all 0, which is incorrect as well.
* Change representation to surface, range is still incorect (which is expected but cumbersome).
![bbb](/uploads/077496b8cc5d914c6bc5be562cf7df90/bbb.png)
![aaa](/uploads/d7f60ce8a126b0e3b3330bb48f5e5e22/aaa.png)
A quick work around would be to not generate vtkProcessId for outline in vtkPVGeometryFilter.cxxhttps://gitlab.kitware.com/paraview/paraview/-/issues/19113vtkMolecule File->SaveData propose an incorrect usage of the vtkLegacyWriter2021-03-24T05:33:05-04:00Mathieu Westphal (Kitware)vtkMolecule File->SaveData propose an incorrect usage of the vtkLegacyWriterWhen saving a vtkMolecule using file->SaveData, a .vtk format is proposed.
It write sucessfully, but the resulting file is unreadable with ParaView.
[aaa.vtk](/uploads/4c09f26420fb3dd58c09154e072e94c0/aaa.vtk)
How to reproduce :
* Ope...When saving a vtkMolecule using file->SaveData, a .vtk format is proposed.
It write sucessfully, but the resulting file is unreadable with ParaView.
[aaa.vtk](/uploads/4c09f26420fb3dd58c09154e072e94c0/aaa.vtk)
How to reproduce :
* Open ParaView
* Open a .pdb file, Apply
* Select the secondary output, File -> SaveData
* Write a .vtk file (only possible choice)
* File -> Open -> .vtk file
* No reader is able to open it.
Ideally, we should add a .pdb or .mol writer.
@nicolas.vuaillehttps://gitlab.kitware.com/paraview/paraview/-/issues/19122RayTracing of Lines has wrong colors2021-03-24T05:32:31-04:00Jean M. FavreRayTracing of Lines has wrong colorsThe OpenGL, OSPRay and OptiX rendering of line segments differs in a big way. OpenGL correctly does a linear interpolation of colors between the two vertices making one Line Segment. OSPRay does a constant coloring using only the data of...The OpenGL, OSPRay and OptiX rendering of line segments differs in a big way. OpenGL correctly does a linear interpolation of colors between the two vertices making one Line Segment. OSPRay does a constant coloring using only the data of the 0-th vertex of the segment. OptiX does worse, in an order that does not seem obvious.
included is a vtkPolyData to test: [SevenLines.vtp](/uploads/3256ad7adae24fa3c90316ccdea21c00/SevenLines.vtp)https://gitlab.kitware.com/paraview/paraview/-/issues/19034pqConsoleWidget does not handle selection correctly2021-03-24T05:30:17-04:00Mathieu Westphal (Kitware)pqConsoleWidget does not handle selection correctlyWhen selecting in the pqConsoleWidget (PythonShell, OutputMessage with full messages), the selected text can be incorrect.
How to reproduce :
* Open ParaView with python
* Open Python Shell
* Type some commands in it
* Select some...When selecting in the pqConsoleWidget (PythonShell, OutputMessage with full messages), the selected text can be incorrect.
How to reproduce :
* Open ParaView with python
* Open Python Shell
* Type some commands in it
* Select some text by pressing the left button of the mouse within the widget, keep the button pressed until it is fully out of the widget on the left of the widget
* Unpress the button
* move the mouse in the widget
* selection is changed even though the button is not currently pressed.
![Peek_2019-05-16_18-45](/uploads/065ae628ebfae965ee643a12a392cea9/Peek_2019-05-16_18-45.gif)https://gitlab.kitware.com/paraview/paraview/-/issues/19041Box clip widget interaction bug.2021-03-24T05:29:17-04:00Aron HelserBox clip widget interaction bug.ParaView 5.6 and recent master, windows 10 laptop, nvidia graphics.
All data seem to reproduce to some extent, but a wavelet from 1000 -> 1100 in all dimensions with a center of 1000 reproduces easily for me. Rotate so it's at an angle.
...ParaView 5.6 and recent master, windows 10 laptop, nvidia graphics.
All data seem to reproduce to some extent, but a wavelet from 1000 -> 1100 in all dimensions with a center of 1000 reproduces easily for me. Rotate so it's at an angle.
Add a Clip filter, choose the 'Box' clip type.
Drag the center handle of one side so the side translates along its axis.
Drag the side past the opposite side. The box will often 'vibrate' and move the opposite side as well, and the yellow side highlight flips between the two sides.
With some data, like a pointset VTP where the center is not at zero, the box widget just disappears after dragging past the opposite side. Can share example privately.https://gitlab.kitware.com/paraview/paraview/-/issues/19055NVidia Index Plugin2021-03-24T05:28:56-04:00Gabriel AxtmannNVidia Index PluginHi, the NvidiaIndexPlugin does not run with data obtained by openFOAM or via foamtoVTK converted data. Reported this issues via mail long time ago. Verbose Output does not say anything, just no picture appears on screen. Witha created da...Hi, the NvidiaIndexPlugin does not run with data obtained by openFOAM or via foamtoVTK converted data. Reported this issues via mail long time ago. Verbose Output does not say anything, just no picture appears on screen. Witha created data source object "wavelet" everything runs fine on my computer. So the functionality is given in principle.https://gitlab.kitware.com/paraview/paraview/-/issues/19058VTK/VTU 2D points (two components)2021-03-24T05:28:37-04:00Nico SchlömerVTK/VTU 2D points (two components)The VTK/VTU file format specification states implicitly that points have to have three components. Not sure if this is intentional.
Alas, when creating 2D meshes (using, e.g., [meshio](https://github.com/nschloe/meshio)), the reference ...The VTK/VTU file format specification states implicitly that points have to have three components. Not sure if this is intentional.
Alas, when creating 2D meshes (using, e.g., [meshio](https://github.com/nschloe/meshio)), the reference tool ParaView _segfaults._
```
vtkPoints (0x6046fa0): Number of components is different...can't set data
Segmentation fault (core dumped)
```
[circle.vtu](/uploads/16570253057c92281e81c938207750da/circle.vtu)
Other file formats like XDMF are displayed correctly with 2D meshes.
[circle.xdmf](/uploads/167cae0651e6268ee6204efec4b9eac9/circle.xdmf)
[circle.h5](/uploads/ae93e8714165b1aee5c2effa66d8850d/circle.h5)
Any change of allowing 2D points in VTK/VTU for display?https://gitlab.kitware.com/paraview/paraview/-/issues/19089vtu parsing2021-03-24T05:27:28-04:00Lukas Wirzvtu parsingA vtu file that contains wrong entries in <DataArray ... Name="offsets" ...> instantly leads to a segfault if the indices point before or after the previously given array of node-indices. Surely, there should instead be an error message...A vtu file that contains wrong entries in <DataArray ... Name="offsets" ...> instantly leads to a segfault if the indices point before or after the previously given array of node-indices. Surely, there should instead be an error message.
I am using the paraview version that ships with debian testing (what they call 5.4.1+dfsg4-3.1+b2).https://gitlab.kitware.com/paraview/paraview/-/issues/19091cannot delete rows in Color Map editor's advanced/table view2021-03-24T05:27:17-04:00Utkarsh Ayachitcannot delete rows in Color Map editor's advanced/table view* Wavelet, Apply
* Color by RTData, open Color Map Editor
* Hit on the gear next to the transfer function to view the entires in the color and opacity transfer function in a table view. While one can edit the entries in the table view, t...* Wavelet, Apply
* Color by RTData, open Color Map Editor
* Hit on the gear next to the transfer function to view the entires in the color and opacity transfer function in a table view. While one can edit the entries in the table view, there's no way to add or remove rowshttps://gitlab.kitware.com/paraview/paraview/-/issues/18975Exporting high-resolution LIC pictures2021-03-24T05:24:53-04:00Maria DimitrovaExporting high-resolution LIC picturesAs suggested by Mathieu Westphal on the [Paraview forum](https://discourse.paraview.org/t/exporting-high-resolution-lic/1733), I'm opening an issue regarding the LIC plugin.
If I export a screenshot up to the size of my working window,...As suggested by Mathieu Westphal on the [Paraview forum](https://discourse.paraview.org/t/exporting-high-resolution-lic/1733), I'm opening an issue regarding the LIC plugin.
If I export a screenshot up to the size of my working window, everything looks fine. However, if I double it, there are inconsistencies at the stitch points between the four separate rectangles the image is split into. I would be glad if it would be possible to for the full image to be rendered in four pieces seamlessly. A sample picture is attached and if needed, I can provide the Paraview state file and the source data.
![azaborine-LIC-z0](/uploads/e7cfae2fb1bdfb0be2accf6ef2dfc2a1/azaborine-LIC-z0.jpeg)https://gitlab.kitware.com/paraview/paraview/-/issues/18977Allow multiple colors in 3D glyph2021-03-24T05:24:37-04:00Gabriel DevillersAllow multiple colors in 3D glyphIn order to visualize the trajectory (position and orientation) over time of a referential (Robot arm referential, Camera, Lidar, integrated IMU, etc.) it would be very convenient to position 3 axis (X,Y,Z) oriented correctly at every/so...In order to visualize the trajectory (position and orientation) over time of a referential (Robot arm referential, Camera, Lidar, integrated IMU, etc.) it would be very convenient to position 3 axis (X,Y,Z) oriented correctly at every/some points of the trajectory.
Graphically the set of three axis would be similar to vtkAxesActor: the axis would be identified by a color (such as red for axis X, green for axis Y, blue for axis Z).
One solution that I am thinking of to achieve this is using a 3D glyph representation.
The problem is that currently ParaView does not support multiple colors inside a 3D glyph.
This is technically possible according to my discussion with @michael.migliore and @mwestphal but requires either writing a plugin or modifying ParaView.https://gitlab.kitware.com/paraview/paraview/-/issues/18999"Zoom to Data" zooms to data bounds, not representation bounds2021-03-24T05:21:52-04:00Cory Quammencory.quammen@kitware.com"Zoom to Data" zooms to data bounds, not representation boundsThe "Zoom to Data" button in the "Camera Controls" toolbar resets the camera to fix the data bounds produced by the source instead of bounds of the representation. This can lead to the representation being out of bounds when using the "3...The "Zoom to Data" button in the "Camera Controls" toolbar resets the camera to fix the data bounds produced by the source instead of bounds of the representation. This can lead to the representation being out of bounds when using the "3D Glyphs" representation for instance, with large glyphs. To see this try the following:
* Run ParaView, built-in server
* Add a **Sphere** source
* Change the representation to "3D Glyphs"
Click on "Zoom to Data". The camera is reset, but the tips of the glyphs stick outside the render view, like so:
![image](/uploads/35a12c591c6c2b6c3f20c19908e7a590/image.png)
In contrast, click the "Reset" toolbutton in the same toolbar. All glyphs fit nicely within the render view:
![image](/uploads/b0430a7d4540351e2fe19ca33a95b047/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19025"Screen Pixels Per Inch" setting overridden by pqQVTKWidget unscaled DPI2021-03-24T05:20:55-04:00Cory Quammencory.quammen@kitware.com"Screen Pixels Per Inch" setting overridden by pqQVTKWidget unscaled DPIThis was observed on ParaView master (c1e7c8c5ca6f4355b9bc6c1ceb632c00e2047cc0) on a MacBook Pro with Retina display./
Steps to reproduce symptoms:
* Start ParaView
* Add **Wavelet** source. Color by "RTData".
* Open Settings/Preference...This was observed on ParaView master (c1e7c8c5ca6f4355b9bc6c1ceb632c00e2047cc0) on a MacBook Pro with Retina display./
Steps to reproduce symptoms:
* Start ParaView
* Add **Wavelet** source. Color by "RTData".
* Open Settings/Preferences. Set the *Screen Pixels Per Inch* setting in the *General* tab to 100 and click OK. On a HiRes display, the text will shrink in size. On a lower res display, the text should grow slightly.
* Now grab a corner of the main window and resize it. Notice that the text snaps back to the original size and the *Screen Pixels Per Inch* setting is ignored.
The problem is that `QVTKRenderWindowAdapter::resize()` resets the DPI in the `vtkRenderWindow` whenever the window size changes. This DPI overrides the "Screen PPI" setting.
The "Screen PPI" setting is currently used only in `vtkPVView` and subclasses and when saving screenshots using `vtkSMSaveScreenshotProxy`. However, using this while `vtkRenderWindow` uses the actual DPI of the display causes font scaling to be totally incorrect most of the time.
The "Screen Pixels Per Inch" setting should modify the unscaled DPI in pqQVTKWidget.
/cc @utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18892Invalid point/cell ID at end of VTKCellArray causes segfaults; triage "fix"2021-03-24T05:18:44-04:00Erik KeeverInvalid point/cell ID at end of VTKCellArray causes segfaults; triage "fix"I am using Paraview 5.6 to visualize a large structured dataset, but it has been unusable due to a relentless segfault. This has never occurred in PV 5.5.2.
The following "fix" intercepts the crash, whines to the console about it, and o...I am using Paraview 5.6 to visualize a large structured dataset, but it has been unusable due to a relentless segfault. This has never occurred in PV 5.5.2.
The following "fix" intercepts the crash, whines to the console about it, and overwrites the offending nonsense point ID with zero (which is garbage, and does introduce the visual glitch you might expect, but at least it doesn't take the entire program down).
[icky_patch](/uploads/3d264ab7036b1c4dc32944b329db230b/icky_patch)
Wherever it happens, it always occurs at the end of a traversal of a vtkCellArray at which one of the cell pointers/IDs is absurd (the input 3DSMesh here has 32M points, and the contour that causes the crash has 600K in change, typical junk values are around 1 billion).
Based on what I am able to observe it seems to be an uninitialized value:
- When both of the patched routines above (before the 1st one was changed to overwrite it) hit the bug, they had the same invalid ID. When gdb intercepted a segfault in a third location, the same invalid ID index was present there too.
- I've altered the "fix" to overwrite it with a valid (albeit garbage) ID and the console complaint occurs only once: the bad triangle causes a visual glitch
- The glitch persists when I change data frames
- It even persists when I delete the original contour and add a new one, or change the values being contoured.
I don't even know where to begin to look to find out where the junk value is being introduced and actually fix the bug.
Steps to reproduce:
The following test dataset causes this problem 100% of the time for me. Please be kind, it is 10GB:
shell.uoregon.edu/~ekeever1/test_data.tar
- mpirun -np 2 pvserver & paraview
- paraview -> connect localhost
- localhost pipeline -> open -> xmtest2_meta.xdmf
- uncheck all but 'mass' to speed things up a bit
- apply
- create contour
- delete default value, create range for contour, choose log scale
- apply
- (patch whines to console)
- contour appears on screenhttps://gitlab.kitware.com/paraview/paraview/-/issues/18893frame rate shown in the render view annotation is hugely incorrect2021-03-24T05:16:56-04:00Utkarsh Ayachitframe rate shown in the render view annotation is hugely incorrectframe rate shown in the render view annotation is very incorrect!frame rate shown in the render view annotation is very incorrect!https://gitlab.kitware.com/paraview/paraview/-/issues/18917Annotations can't be shown/hidden on a state loaded view.2021-03-24T05:14:04-04:00Mathieu Westphal (Kitware)Annotations can't be shown/hidden on a state loaded view.Annotations (from the Settings -> Render View -> Show Annotations setting) can't be shown or hidden on a view created during a LoadState.
How to reproduce :
* delete ParaView settings
* Open ParaView
* File->SaveState->state.pvsm
...Annotations (from the Settings -> Render View -> Show Annotations setting) can't be shown or hidden on a view created during a LoadState.
How to reproduce :
* delete ParaView settings
* Open ParaView
* File->SaveState->state.pvsm
* Edit->Settings->Render View->Check Show annotations
* File->Load State->state.pvsm
* **Annotations are not shown and changing Edit->Settings->Render View->Show annotations has no effect**
* Edit->Settings->Render View->Check Show annotations if not already
* File->SaveState->state.pvsm
* Edit->Settings->Render View->Uncheck Show annotations
* File->Load State->state.pvsm
* **Annotations are shown and changing Edit->Settings->Render View->Show annotations has no effect**https://gitlab.kitware.com/paraview/paraview/-/issues/18925Python calculator doesn't work for Lagrange hexahedron cell types2021-03-24T05:13:54-04:00vrkssaiPython calculator doesn't work for Lagrange hexahedron cell typesIn regard to the below discourse post: https://discourse.paraview.org/t/vorticity-and-gradient-calculation-numerics-gives-wrong-result/1514?u=vrkssai
The filter "Gradient of Unstructured data" and Vorticity Calculation using python calc...In regard to the below discourse post: https://discourse.paraview.org/t/vorticity-and-gradient-calculation-numerics-gives-wrong-result/1514?u=vrkssai
The filter "Gradient of Unstructured data" and Vorticity Calculation using python calculator for Lagrange Hexahedron Grids give erroneous results.The steps and files to reproduce are in the post.https://gitlab.kitware.com/paraview/paraview/-/issues/18857Different behaviour in 'RenderViewComparative' and 'LineChartViewComparative'2021-03-24T05:13:00-04:00Evgeny KolosovDifferent behaviour in 'RenderViewComparative' and 'LineChartViewComparative'For ‘RenderViewComparative’ if I change one representation, then all other representations change synchronously.
[render_view_comparative.avi](/uploads/3239ef15c1ae8b9258f6cbca8e538ddc/render_view_comparative.avi)
For ‘LineChartViewComp...For ‘RenderViewComparative’ if I change one representation, then all other representations change synchronously.
[render_view_comparative.avi](/uploads/3239ef15c1ae8b9258f6cbca8e538ddc/render_view_comparative.avi)
For ‘LineChartViewComparative’ if I change the first representation, then i need to hover the mouse over the representation and if I change not the first representation, then other representations will not be updated.
[linechart_view_comparative.avi](/uploads/04f9edc1c3e0a5ab36cf54e9a7376c51/linechart_view_comparative.avi)
Need to update the line chart views immediately like the render views.https://gitlab.kitware.com/paraview/paraview/-/issues/18862Record Test does not support Ctrl-Space2021-03-24T05:12:40-04:00Mathieu Westphal (Kitware)Record Test does not support Ctrl-SpaceWhen recording a test via Tools -> Record Test, Ctrl-Space is not recorded in any way. The recorded test will then fail.
How to reproduce :
* Open ParaView
* Tools -> Record Test, select a file.
* Click on ParaView Main Window
* Ct...When recording a test via Tools -> Record Test, Ctrl-Space is not recorded in any way. The recorded test will then fail.
How to reproduce :
* Open ParaView
* Tools -> Record Test, select a file.
* Click on ParaView Main Window
* Ctrl-Space, **no event is recorded**
* Select a filter to add, an event is recorded, but it will fail to play.