ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-24T05:27:28-04:00https://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/19092viridis colormap bug2024-03-07T20:47:07-05:00Tomáš Létalviridis colormap bugThere seems to be wrong color segment in viridis colormap - see the attachment. It is apparent on the data, but you can see it also on the colorbar as a thin line approximately in the middle.
![paraview_viridis_bug](/uploads/4cc6ec8cc71f...There seems to be wrong color segment in viridis colormap - see the attachment. It is apparent on the data, but you can see it also on the colorbar as a thin line approximately in the middle.
![paraview_viridis_bug](/uploads/4cc6ec8cc71fd0abb9a9ed80c596bef4/paraview_viridis_bug.png)
ParaView version: 5.6.1 64-bit on Windows 10.5.13 (Summer 2024)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/19156Settings does not scale correctly2019-07-18T13:53:08-04:00W. Alan ScottSettings does not scale correctlySettings dialogs do not scale correctly with Edit/ Settings/ Scale font.
* Linux, 5.7.0-RC1, local server.Settings dialogs do not scale correctly with Edit/ Settings/ Scale font.
* Linux, 5.7.0-RC1, local server.https://gitlab.kitware.com/paraview/paraview/-/issues/19188Non consistant plot colors2021-03-24T05:35:30-04:00Yohann Bearzi (Kitware)Non consistant plot colorsIssue discovered while working on issue #19108.
When running:
$ ctest -R PartialArrayInLineChart -V
The plots' color randomly permute.Issue discovered while working on issue #19108.
When running:
$ ctest -R PartialArrayInLineChart -V
The plots' color randomly permute.https://gitlab.kitware.com/paraview/paraview/-/issues/19212Glyph default values are not always correct2021-03-24T05:34:53-04:00Mathieu Westphal (Kitware)Glyph default values are not always correctWhen using glyph with only a scalar in point data and a vector in cell data, default values are incorrect and no glyphs is shown.
How to reproduce :
* Open ParaView
* Wavelet, Apply
* Random Attributes, (Cell Vectors), Apply
* Gly...When using glyph with only a scalar in point data and a vector in cell data, default values are incorrect and no glyphs is shown.
How to reproduce :
* Open ParaView
* Wavelet, Apply
* Random Attributes, (Cell Vectors), Apply
* Glyph, Apply
* No glyphs are shown and this warning appears
```
Warning: In /home/glow/work/paraview/paraviewFirst/paraview/ParaViewCore/VTKExtensions/Default/vtkPVGlyphFilter.cxx, line 752
vtkPVGlyphFilter (0x5584a6dd0c30): Mismatched attributes:
RTData is a point attribute whereas RandomCellVectors is a cell attribute.
```https://gitlab.kitware.com/paraview/paraview/-/issues/19223Immense cone make rendering disappear2021-03-24T09:59:25-04:00Mathieu Westphal (Kitware)Immense cone make rendering disappearHow to reproduce :
* Create a cone
* Radius 2e39, Apply
* Nothing is shownHow to reproduce :
* Create a cone
* Radius 2e39, Apply
* Nothing is shownhttps://gitlab.kitware.com/paraview/paraview/-/issues/19243In 2D mode, camera zoom is not visible/settable in Adjust Camera dialog2021-03-24T05:43:08-04:00Mathieu Westphal (Kitware)In 2D mode, camera zoom is not visible/settable in Adjust Camera dialogIn 2D mode, camera zoom is not visible/settable in Adjust Camera dialog, preventing it to be set manually
Steps to reproduce :
* Open ParaView
* Create Wavelet
* Open Adjust Camera dialog
* zoom/unzoom with mouse wheel or right cli...In 2D mode, camera zoom is not visible/settable in Adjust Camera dialog, preventing it to be set manually
Steps to reproduce :
* Open ParaView
* Create Wavelet
* Open Adjust Camera dialog
* zoom/unzoom with mouse wheel or right click
* position is updated in the adjust camera dialog
* Set the view to 2D mode
* zoom/unzoom with mouse wheel or right click
* **position is not updated in the adjust camera dialog**https://gitlab.kitware.com/paraview/paraview/-/issues/19244file opening for files without an extension2021-03-24T05:42:59-04:00Chelsea Harrisfile opening for files without an extensionI have a group of files representing a time series that I should be able to open with the VisitFlashReader, but do not have a file handle (each frame file name instead ends with the frame number). Paraview does not load the data when I t...I have a group of files representing a time series that I should be able to open with the VisitFlashReader, but do not have a file handle (each frame file name instead ends with the frame number). Paraview does not load the data when I try to read them in. An idea for why this is happening was: "The file series reader that we inject into the pipeline to treat numbered series of files as a time series... appears to get confused without a file extension"https://gitlab.kitware.com/paraview/paraview/-/issues/19251Popout layout is very small with ParaView 5.7-RC2 on windows2021-03-24T05:41:52-04:00Mathieu Westphal (Kitware)Popout layout is very small with ParaView 5.7-RC2 on windowsWith ParaView 5.7-RC2, on windows, the Popout layout is very small by default. It can be resized without any issue but not really practical. Issue does not appear on linux nor with 5.6.
Steps to reproduce :
* Run ParaView 5.7-RC2 rele...With ParaView 5.7-RC2, on windows, the Popout layout is very small by default. It can be resized without any issue but not really practical. Issue does not appear on linux nor with 5.6.
Steps to reproduce :
* Run ParaView 5.7-RC2 release on windows
* Click on pop out layout
![2019-08-13](/uploads/19f63d97ab9182aa8a4d1e4b5ea776d1/2019-08-13.png)
@cory.quammen @utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19259LineChartView does not support multipiece input2021-03-24T05:38:00-04:00Mathieu Westphal (Kitware)LineChartView does not support multipiece inputLineChartView does not support multipiece input
* Open ParaView
* Open MultiBlockWithMultiPiece.vtm
* Filters -> PlotData, Apply
* Not Data can be shown
* Selection MultiBlockWithMultiPiece.vtm,
* Filter -> Merge Blocks, Apply
* ...LineChartView does not support multipiece input
* Open ParaView
* Open MultiBlockWithMultiPiece.vtm
* Filters -> PlotData, Apply
* Not Data can be shown
* Selection MultiBlockWithMultiPiece.vtm,
* Filter -> Merge Blocks, Apply
* Filters -> PlotData, Apply
* Works finehttps://gitlab.kitware.com/paraview/paraview/-/issues/19262Strange behavior with the ResetLight button2021-03-24T05:36:30-04:00Mathieu Westphal (Kitware)Strange behavior with the ResetLight buttonResetLight has some strange behavior that depend of the current status of the light.
How to reproduce :
* Open ParaView
* View -> Light Inspector
* Add Light
* Move Light around
* Reset Light
* Works perfectly
* Change to a Headl...ResetLight has some strange behavior that depend of the current status of the light.
How to reproduce :
* Open ParaView
* View -> Light Inspector
* Add Light
* Move Light around
* Reset Light
* Works perfectly
* Change to a Headlight light
* Reset Light
* Light is not reset to expected position but to another position
@wascott : more lights weirdnesshttps://gitlab.kitware.com/paraview/paraview/-/issues/19281ColorOpacityWidget has strange behavior with negative range and log2021-03-24T05:48:04-04:00Mathieu Westphal (Kitware)ColorOpacityWidget has strange behavior with negative range and logColorOpacityWidget has strange behavior with negative range and log.
It change the range so it is compatible with log, that is expected, but then rescaling goes wrong.
Steps to reproduce :
* Open ParaView
* Wavelet, Apply
* Calculat...ColorOpacityWidget has strange behavior with negative range and log.
It change the range so it is compatible with log, that is expected, but then rescaling goes wrong.
Steps to reproduce :
* Open ParaView
* Wavelet, Apply
* Calculator, RTData - 200, Apply
* Show "Results" array
* Edit Color Map
* The following warning appears, expected
```
Generic Warning: In /home/glow/work/paraview/paraviewFirst/paraview/Qt/ApplicationComponents/pqColorOpacityEditorWidget.cxx, line 709
Ranges not valid for log-space. Changed the range to (0.0126829, 126.829).
```
* Click on "Rescale to data range"
* The warning appears again, expected, but the results in the widget incorrect
![2019-08-28-130802_496x286_scrot](/uploads/178fd7d257dc0d7f426aee7bc1945c19/2019-08-28-130802_496x286_scrot.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19299ColorBar editor position settings has unexpected behavior2021-03-24T05:47:04-04:00Mathieu Westphal (Kitware)ColorBar editor position settings has unexpected behaviorThe ColorBar editor as a position settings. However, it does not behave as expected.
Steps to reproduce :
* Open paraview -dr
* Wavelet, apply
* Color by RTData
* Edit Color Map, Edit color legend properties
* Uncheck auto-orient ...The ColorBar editor as a position settings. However, it does not behave as expected.
Steps to reproduce :
* Open paraview -dr
* Wavelet, apply
* Color by RTData
* Edit Color Map, Edit color legend properties
* Uncheck auto-orient and Select "Horizontal" (just to check it is working for certain settings)
* Set "Window Location" to Upper Right Corner, Apply
* **"Position" settings has not been updated and still shows "0.89" "0.2" when it should be "0.63" "0.91". Also it should be greyed out instead of uneditable**
* Set "Window Location" to Any Location, Apply
* Color bar does not move, expected
* **"Position" settings is still incorrect and still shows "0.89" "0.2" when it should be "0.63" "0.91".**
* Set Position to "0.63" "0.5"
* Apply, color bar is correctly placed
* Save Settings as default
* Create a new view,
* Show wavelet, color by RTData
* **ColorBar is incorectly placed, see screenshot**
* Edit Color Map, Edit color legend properties
* **Position is "0.89" "0.2" when it should be "0.63" "0.5".**
![2019-09-04-070832_1227x879_scrot](/uploads/02398c8d44d01edc62f731256213ddbf/2019-09-04-070832_1227x879_scrot.png)
@rrossi @cory.quammenhttps://gitlab.kitware.com/paraview/paraview/-/issues/19313Plugin auto-load option: "no entry in PV plugin manager"2021-03-24T05:45:02-04:00Cornelis BockemühlPlugin auto-load option: "no entry in PV plugin manager"Own plugins can be written and directly integrated into a custom application. Loading them can be automatic with the REQUIRED_PLUGINS list of the paraview_client_add cmake function or inside the program using the vtkPVPluginTracker class...Own plugins can be written and directly integrated into a custom application. Loading them can be automatic with the REQUIRED_PLUGINS list of the paraview_client_add cmake function or inside the program using the vtkPVPluginTracker class.
In all these cases, the plugins will appear in the list of the plugin manager - as "loaded".
But this does not make too much sense because loading them is not any more required, and unloading makes not much sense (and I would even doubt whether it can be reliable to "unload" a shared library from a running program!?)
Having an an option during plugin auto-load to not show a plugin in the PV plugin manager makes sense thus and avoids filling the list with useless entries.https://gitlab.kitware.com/paraview/paraview/-/issues/19338ParaView crashing when specifying wrong extents for RAW ImageData2021-03-24T05:58:44-04:00Matthieu DorierParaView crashing when specifying wrong extents for RAW ImageDataI'm using ParaView 5.6.2 on MacOSX.
I'm opening a RAW file containing a 3D array of integers (30x30x30 elements). If I specify extents such that the product would be larger than the data size (e.g. if I set [0,30]x[0,30]x[0,30] instead o...I'm using ParaView 5.6.2 on MacOSX.
I'm opening a RAW file containing a 3D array of integers (30x30x30 elements). If I specify extents such that the product would be larger than the data size (e.g. if I set [0,30]x[0,30]x[0,30] instead of [0,29]x[0,29]x[0,29]), ParaView hangs when I click "apply" and I have to kill it.https://gitlab.kitware.com/paraview/paraview/-/issues/19339Assert fail when the legend takes too much space in a line chart view2021-03-24T05:53:01-04:00Mathieu Westphal (Kitware)Assert fail when the legend takes too much space in a line chart viewIf the legend takes too much spaces, the chart fails to draws on an assert and ParaView segfaults.
Steps to reproduce :
* Open ParaView
* Open SinceWaves.csv, Apply
* Show in a LineChartView
* Show all arrays
* place legend at the...If the legend takes too much spaces, the chart fails to draws on an assert and ParaView segfaults.
Steps to reproduce :
* Open ParaView
* Open SinceWaves.csv, Apply
* Show in a LineChartView
* Show all arrays
* place legend at the bottom
* Hide last three arrays
* Increase legend font size to 14
* Show one more array
```
paraview: /home/glow/work/paraview/paraviewFirst/paraview/VTK/Rendering/Context2D/vtkContextClip.cxx:71: virtual void vtkContextClip::SetClip(float, float, float, float): Assertion `width >= 0 && height >= 0' failed.
Thread 1 "paraview" received signal SIGABRT, Aborted.
0x00007ffff7c08755 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0 0x00007ffff7c08755 in raise () from /usr/lib/libc.so.6
#1 0x00007ffff7bf3851 in abort () from /usr/lib/libc.so.6
#2 0x00007ffff7bf3727 in __assert_fail_base.cold () from /usr/lib/libc.so.6
#3 0x00007ffff7c01026 in __assert_fail () from /usr/lib/libc.so.6
#4 0x00007ffff16c8b05 in vtkContextClip::SetClip (this=0x555559abcda0, x=20, y=574, width=242, height=-2) at /home/glow/work/paraview/paraviewFirst/paraview/VTK/Rendering/Context2D/vtkContextClip.cxx:71
```https://gitlab.kitware.com/paraview/paraview/-/issues/19345Automatic selection of objects in pipeline browser when mouse-picked in rende...2021-03-24T05:52:02-04:00Riccardo RossiAutomatic selection of objects in pipeline browser when mouse-picked in render viewBack in the 4.3.1 release, the objects in the pipeline browser where automatically selected when picked in the render view with the mouse.
For example, if you have two tiles in the render view and two objects active separately in each t...Back in the 4.3.1 release, the objects in the pipeline browser where automatically selected when picked in the render view with the mouse.
For example, if you have two tiles in the render view and two objects active separately in each tile, by clicking one or the other they would be also selected in the pipeline.
In my understanding this feature is gone and now an extra click is required to perform the same operation, one to change the active tile and another one to select the object in the same tile.
If that's the case, would be nice to have it back or at least be able to activate such behavior.