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/19401ospray amr bug2024-03-07T20:47:11-05:00Carson Brownleeospray amr bugswitching on and off ospray rendering with an amr volume appears to crash in some cases. Reproducible with amr guassian source. @demarleswitching on and off ospray rendering with an amr volume appears to crash in some cases. Reproducible with amr guassian source. @demarle5.13 (Summer 2024)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/19060Ghost Zone Handling2021-04-01T11:03:03-04:00Burlen LoringGhost Zone HandlingI am experiencing multiple issues with ghost zone processing running in situ w/ catalyst. We are doing zero copy transfer from an AMR simulation that has 4 ghost zones around each block.
1. When I am trying to set up the catalyst script...I am experiencing multiple issues with ghost zone processing running in situ w/ catalyst. We are doing zero copy transfer from an AMR simulation that has 4 ghost zones around each block.
1. When I am trying to set up the catalyst script I save a dataset using the vth writer. The vth reader attempts to re-generate the ghost zones based on the number of levels slider in its PV UI. It correctly generates the mask for nested blocks. However it doesn't re-generate the 4 ghost zones. This leads to rendering data in the ghost zones.
2. The array range calculations seem to be including values in the ghost zones. I think that the range calculations are made inside vtkDataArray and hence don't have access to ghost zones?
I have not had time to work on this so I wanted to document some of the issues.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/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/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/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/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/18960Selection when Render Points As Spheres enabled prevents selection2020-11-19T14:48:04-05:00Andrew BauerSelection when Render Points As Spheres enabled prevents selectionSteps to reproduce:
1. Create a `Point Source` with a single point
2. Under `Styling` set `Point Size` to 5 and enable `Render Points as Spheres`
3. Uncheck the `Show Point` option under `Point Parameters`
4. Fit to screen and try to...Steps to reproduce:
1. Create a `Point Source` with a single point
2. Under `Styling` set `Point Size` to 5 and enable `Render Points as Spheres`
3. Uncheck the `Show Point` option under `Point Parameters`
4. Fit to screen and try to select the point, it won't show being highlighted with the purple highlight color
Can split the view and have the second view be the Spreadsheet view and enable `Show only selected elements.` to verify that the point isn't being selected. If `Render Points as Spheres` is disabled then it allows the point to be selected.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/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/18887Odd background when background image specified in state file is not found2021-03-24T05:10:35-04:00Cory Quammencory.quammen@kitware.comOdd background when background image specified in state file is not foundLoad the attached state file which specifies a background image. [state.pvsm](/uploads/48ac473a96b0544fd01d00c245a7e1f4/state.pvsm). Don't fix any file paths in the state file after loading it. The background will display the axes image ...Load the attached state file which specifies a background image. [state.pvsm](/uploads/48ac473a96b0544fd01d00c245a7e1f4/state.pvsm). Don't fix any file paths in the state file after loading it. The background will display the axes image (or do some other strange thing) and you will get the following error message:
```
ERROR: In /home/cory.quammen/src/paraview-review/VTK/Rendering/OpenGL2/vtkOpenGLTexture.cxx, line 200
vtkOpenGLTexture (0x2ef93b0): No scalar values found for texture input!
ERROR: In /home/cory.quammen/src/paraview-review/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper2D.cxx, line 814
vtkOpenGLPolyDataMapper2D (0x381cbd0): failed after RenderOverlay 1 OpenGL errors detected
0 : (1281) Invalid value
```
What I see on linux is:![AxesBackground](/uploads/453a6a63e005d00c8067fa2490d03ea5/AxesBackground.png)
ParaView should give a warning and abort loading of the background image.https://gitlab.kitware.com/paraview/paraview/-/issues/18884keyboard shortcuts don't work in fullscreen mode2021-03-24T05:11:04-04:00Utkarsh Ayachitkeyboard shortcuts don't work in fullscreen modewhen the render window is made fullscreeen, keyboard shortcuts don't seem to work.when the render window is made fullscreeen, keyboard shortcuts don't seem to work.https://gitlab.kitware.com/paraview/paraview/-/issues/18883Progress is not handling well for temporal filter2021-03-24T05:11:22-04:00Mathieu Westphal (Kitware)Progress is not handling well for temporal filterProgress is unreadable when using temporal filter in the Pipeline.
Consider the following usecase:
* Open FileSeries->Wavelet*.vti
* RandomVectors, Apply
* StreamTracer, 100 points, apply
* PlotDataOverTime, Apply
* the progress b...Progress is unreadable when using temporal filter in the Pipeline.
Consider the following usecase:
* Open FileSeries->Wavelet*.vti
* RandomVectors, Apply
* StreamTracer, 100 points, apply
* PlotDataOverTime, Apply
* the progress bar will go from 0 to 100 at least 4 times, on for each timesteps/stream tracer execution, **without giving any sense of remaining execution time.**
* It actually is possible to see the PlotDataOverTime progress, but it is displayed very fast, after the stream tracer progress.https://gitlab.kitware.com/paraview/paraview/-/issues/18879Render View (Comparative) visibility and opacity features are not working cor...2021-03-24T05:11:32-04:00Mathieu Westphal (Kitware)Render View (Comparative) visibility and opacity features are not working correctlyRender View (Comparative) visibility and opacity features are not working correctly.
How to reproduce :
* Open ParaView
* Wavelet, Apply
* Create new Render View (Comparative)
* Show the Comparative Panel
* Add Wavelet1 -> visibili...Render View (Comparative) visibility and opacity features are not working correctly.
How to reproduce :
* Open ParaView
* Wavelet, Apply
* Create new Render View (Comparative)
* Show the Comparative Panel
* Add Wavelet1 -> visibility property in the Comparative Panel
* ** Modify the property on any panel, no effect**
* Remove the property
* Show the Wavelet in the Render View (Comparative) using the pipeline browser
* Add Wavelet1 -> visibility property in the Comparative Panel
* **Modify the property on any of the first three panel, the wavelet disappears and do not reappear**
* **Set the property to 1 on the fourth panel, the wavelet appears on all four panels**
(May be linked to #18875 #18876 #18877 #18878 #18879)https://gitlab.kitware.com/paraview/paraview/-/issues/18878Render View (Comparative) does not reset center2021-03-24T05:11:39-04:00Mathieu Westphal (Kitware)Render View (Comparative) does not reset centerThe Render View (Comparative) center of rotation is not resetted automatically when showing data.
How to reproduce :
* Open ParaView
* Create Wavelet, Apply
* Transform -> Translate X 1000 -> Apply
* Create a Render View (Comparati...The Render View (Comparative) center of rotation is not resetted automatically when showing data.
How to reproduce :
* Open ParaView
* Create Wavelet, Apply
* Transform -> Translate X 1000 -> Apply
* Create a Render View (Comparative)
* Show the transform in it
* Move the camera with the mouse
* **Unexpected movement**
* Click on reset Center of rotation
* Move the camera with the mouse
* Expected movement
(May be linked to #18875 #18876 #18877 #18878 #18879)https://gitlab.kitware.com/paraview/paraview/-/issues/18877Render View (Comparative) Layout bugs2021-03-24T05:11:44-04:00Mathieu Westphal (Kitware)Render View (Comparative) Layout bugsWhen changing the layout of a comparative view, they are a few bugs.
How to reproduce :
* Open ParaView
* Create Render View (Comparative)
* Create Wavelet, Apply
* Change to surface representation
* Click once on the horizontal l...When changing the layout of a comparative view, they are a few bugs.
How to reproduce :
* Open ParaView
* Create Render View (Comparative)
* Create Wavelet, Apply
* Change to surface representation
* Click once on the horizontal layout up arrow
* **New views appears, but are not on surface representation**
* Click once on the vertical layout up arrow
* **ParaView behave as if you clicked two time on the arrow**
* Add Wavelet -> Center as a property
* Delete Wavelet
* **The property is still visible, it should not**
* Create a new view, any type,
* Show the Render View (Comparative)
* **The property is now named "Unrecognized proxy::Center"**
* Create a new Render View (Comparative)
* Create a Wavelet, Apply
* Add Wavelet -> Center as a property
* **There is 12 property to change instead of 4.**
* Changing the property there has unexpected results.
(May be linked to #18875 #18876 #18877 #18878 #18879)https://gitlab.kitware.com/paraview/paraview/-/issues/18876Render View (Comparative) Delete Property limitation2021-03-24T05:11:48-04:00Mathieu Westphal (Kitware)Render View (Comparative) Delete Property limitationWhen deleting and recreating a property with the Render View (Comparative), it does not show the expected value.
How to reproduce :
* Open ParaView
* Create Render View (Comparative)
* Create Wavelet, Apply
* Add Wavelet -> Center ...When deleting and recreating a property with the Render View (Comparative), it does not show the expected value.
How to reproduce :
* Open ParaView
* Create Render View (Comparative)
* Create Wavelet, Apply
* Add Wavelet -> Center as a property
* Set values to -10, 10, -20, 20
* Delete property
* Add Wavelet -> Center as a property
* **Property values shown are all 20, like the last one.**
* Change a property value, all the 20s are applied as well
(Some of these bugs are visible with Line Chart View (Comparative) as well)
(May be linked to #18875 #18876 #18877 #18878 #18879)https://gitlab.kitware.com/paraview/paraview/-/issues/18875Render View (Comparative) "Overlay All Comparisons" bugs.2021-03-24T05:11:53-04:00Mathieu Westphal (Kitware)Render View (Comparative) "Overlay All Comparisons" bugs."Overlay All Comparisons" option breaks the comparative view.
How to reproduce :
* Open ParaView
* Create a new Render View (Comparative)
* Create a Wavelet, show it in the comparative view
* Show the comparative view panel
* Add ..."Overlay All Comparisons" option breaks the comparative view.
How to reproduce :
* Open ParaView
* Create a new Render View (Comparative)
* Create a Wavelet, show it in the comparative view
* Show the comparative view panel
* Add Wavelet -> Center property
* set -10, 10, -20, 20 as values
* All is looking good
* Check "Overlay All Comparisons"
* Uncheck "Overlay All Comparisons"
* **Only the first view show the surace rep, the others shows an outline**
* Set representations to slice, then back to surface in order to recover the correct rendering
* **The first view in incorrect**
* Change the Center property, **it has no effect, instead of the last one that changes the first view**
* Delete the wavelet
* **The wavelet is still visible.**
(Some of these bugs are visible with Line Chart View (Comparative) as well)
(May be linked to #18875 #18876 #18877 #18878 #18879)https://gitlab.kitware.com/paraview/paraview/-/issues/18867ParaView python backward compatibility mechanism does not allow to change enu...2021-03-24T05:12:18-04:00Mathieu Westphal (Kitware)ParaView python backward compatibility mechanism does not allow to change enumeration valueWhen changing the enumeration value of a property in a proxy, a user using paraview.compatibility would expect to be able to use the old value in setter and getter.
It is possible to set it but it is not possible to get the value, as it ...When changing the enumeration value of a property in a proxy, a user using paraview.compatibility would expect to be able to use the old value in setter and getter.
It is possible to set it but it is not possible to get the value, as it is stored in the locals of the python object hence no backward compatibility code is ever called.
How to reproduce :
* Apply this [backwardCompat.patch](/uploads/e6eb86f003b2a5629790d5a6ea78ace7/backwardCompat.patch) on master. This patch change an enum name from "Points" to "Foo" in the PlotDataOverTime filter, and tries to handle the backward compatibility.
* build paraview with python enabled
* run paraview
* open python shell
* run the following commands
```
paraview.compatibility.major=5
paraview.compatibility.major=5
Wavelet()
a=PlotDataOverTime()
a.FieldAssociation = "Cells"
a.FieldAssociation = "Points" -> the setter is working great
a.FieldAssociation -> Here we expect "Points" but we get "Foo"
```
I added a print trace to the getter, it is never called.
it impacts !2038 and !3095