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/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/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/19086parallel translucent rendering has holes in some cases2019-06-25T20:39:34-04:00Utkarsh Ayachitparallel translucent rendering has holes in some casesSteps:
* pvserver (2 ranks), connect with paraview, force remote rendering
* open `g1s1-10fps.e16.*` apply
* merge blocks, apply
* change opacity to 0.5, you'll see holes. looks like ghost cells are being marked incorrectly or something ...Steps:
* pvserver (2 ranks), connect with paraview, force remote rendering
* open `g1s1-10fps.e16.*` apply
* merge blocks, apply
* change opacity to 0.5, you'll see holes. looks like ghost cells are being marked incorrectly or something like that.https://gitlab.kitware.com/paraview/paraview/-/issues/19080Outdated Wiki pages2023-08-02T02:22:36-04:00Mathieu Westphal (Kitware)Outdated Wiki pagesThe wiki contains a lot of outdated information.
Here are some that either need to be updated/replaced/removed imo.
* https://www.paraview.org/Wiki/ParaView/ThirdPartyLicenses : @ben.boeckel may know the right way to fix this, could we...The wiki contains a lot of outdated information.
Here are some that either need to be updated/replaced/removed imo.
* https://www.paraview.org/Wiki/ParaView/ThirdPartyLicenses : @ben.boeckel may know the right way to fix this, could we generate something ?
* https://www.paraview.org/Wiki/ParaView:Build_And_Install : Should be replaced by a link to (build.md)[https://github.com/Kitware/ParaView/blob/master/Documentation/dev/build.md]
* https://www.paraview.org/Wiki/ParaView/Binaries : Simply refer to https://gitlab.kitware.com/paraview/paraview-superbuild/tags/ instead of each version
* https://www.paraview.org/Wiki/ParaView/ParaView_Readers_and_Parallel_Data_Distribution : to remove
* https://www.paraview.org/Wiki/ParaView/Plugin_HowTo : Should point to
* https://pluginwizard.mirarco.org/ : to remove
* https://www.paraview.org/Wiki/ParaView/User_Created_Plugins : Should be removed or integrated in ParaView plugins. This is non-builded, non-tested user provided code.
* https://www.paraview.org/Wiki/ParaView/PythonRecipes : We should have a Python Examples stuff, similar to the VTK examples.
* https://www.paraview.org/Wiki/Howtos : This could be removed I supose.
* https://www.paraview.org/Wiki/Related_Publications : We should find a way to keep this up to date somehow
* https://www.paraview.org/Wiki/Time_in_ParaView : Should be removed
* https://www.paraview.org/Wiki/Suggested_online_help_documentation_changes : Should be removed
* https://www.paraview.org/Wiki/ServerManager_XML_Hints : All info should be moved into markdown and available in doc
* https://www.paraview.org/Wiki/ParaView/Guidelines_for_Contributing_Plugins : Should be removed
* https://www.paraview.org/Wiki/Terminology_map : Should be removed
Other pages may need to be updated or moved to the ParaView guide as well.https://gitlab.kitware.com/paraview/paraview/-/issues/19078Reader, Filters and Writers reference wiki page is outdated2023-08-02T02:22:36-04:00Mathieu Westphal (Kitware)Reader, Filters and Writers reference wiki page is outdatedThe references page in the wiki should be replaced by the content of the auto generated Filters, Reader and Writers reference that is available in ParaView.
* https://www.paraview.org/Wiki/ParaView/Users_Guide/List_of_writers
* https://...The references page in the wiki should be replaced by the content of the auto generated Filters, Reader and Writers reference that is available in ParaView.
* https://www.paraview.org/Wiki/ParaView/Users_Guide/List_of_writers
* https://www.paraview.org/Wiki/ParaView/Users_Guide/List_of_filters
* https://www.paraview.org/Wiki/ParaView/Users_Guide/List_of_readers
It actually used to be the case here : https://www.paraview.org/OnlineHelpCurrent/
But this does not exists anymore.
I think this should be generated from the xml files in ParaView.https://gitlab.kitware.com/paraview/paraview/-/issues/19077Catalyst extract are not supported in state files2020-05-05T00:21:45-04:00Mathieu Westphal (Kitware)Catalyst extract are not supported in state filesSaving a state of ParaView with a extract from catalyst does not work, as catalyst extract are based on PVTrivialProducer.
How to reproduce :
* Run a catalyst live simulation connect to a ParaView
* Extract some data
* Finish the si...Saving a state of ParaView with a extract from catalyst does not work, as catalyst extract are based on PVTrivialProducer.
How to reproduce :
* Run a catalyst live simulation connect to a ParaView
* Extract some data
* Finish the simulation
* Save a statefile
* Load the statefile
```
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e0251d6dd0): Input for connection index 0 on input port index 0 for algorithm vtkPolarAxesRepresentation(0x55e025499aa0) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e024bae070): Input for connection index 0 on input port index 0 for algorithm vtkFeatureEdgesRepresentation(0x55e01f8a04a0) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e0258ff270): Input for connection index 0 on input port index 0 for algorithm vtkGlyph3DRepresentation(0x55e021e27c20) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e024f03140): Input for connection index 0 on input port index 0 for algorithm vtkOutlineRepresentation(0x55e0243d3910) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e020199f50): Input for connection index 0 on input port index 0 for algorithm vtkPointGaussianRepresentation(0x55e023ade340) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e0238f9330): Input for connection index 0 on input port index 0 for algorithm vtkDataLabelRepresentation(0x55e0244ea1a0) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e025965830): Input for connection index 0 on input port index 0 for algorithm vtkGeometryRepresentationWithFaces(0x55e01fd15d40) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e025965830): Input for connection index 0 on input port index 0 for algorithm vtkGeometryRepresentationWithFaces(0x55e01fd15d40) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 782
vtkCompositeDataPipeline (0x55e0258c6c80): Algorithm vtkPVGeometryFilter(0x55e025965ee0) returned failure for request: vtkInformation (0x55e022e445c0)
Debug: Off
Modified Time: 2941746
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e0236b5f30): Input for connection index 0 on input port index 0 for algorithm vtkGeometryRepresentation(0x55e02299e0e0) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 782
vtkCompositeDataPipeline (0x55e022fa41e0): Algorithm vtkPVGeometryFilter(0x55e0236b6b50) returned failure for request: vtkInformation (0x55e023c91c70)
Debug: Off
Modified Time: 2941840
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e01f7747f0): Input for connection index 0 on input port index 0 for algorithm vtkPVGridAxes3DRepresentation(0x55e0257a8e20) is of type vtkDataObject, but a vtkCompositeDataSet is required.
```https://gitlab.kitware.com/paraview/paraview/-/issues/19071Individual dialogs don't scale properly with Override Font2019-07-05T21:38:13-04:00W. Alan ScottIndividual dialogs don't scale properly with Override FontEdit/ Settings/ General/ Override Font. Change to 18, OK. This is Linux, master.
![Capture](/uploads/547cc37e60d2fc98f83357b3cdf23a87/Capture.PNG)Edit/ Settings/ General/ Override Font. Change to 18, OK. This is Linux, master.
![Capture](/uploads/547cc37e60d2fc98f83357b3cdf23a87/Capture.PNG)https://gitlab.kitware.com/paraview/paraview/-/issues/19063Support proxies written in Python that are embedded in a compiled module2019-06-17T09:18:42-04:00Ben BoeckelSupport proxies written in Python that are embedded in a compiled modulePython modules added to a plugin via `PYTHON_MODULES` may create proxies using the decorators. These do not work as one might expect right now because the proxy is not hooked into the global registration mechanism since the import happen...Python modules added to a plugin via `PYTHON_MODULES` may create proxies using the decorators. These do not work as one might expect right now because the proxy is not hooked into the global registration mechanism since the import happens in the Python shell, not at plugin load time.
See https://discourse.paraview.org/t/how-embedding-python-source-as-modules/1978 for discussion.
Cc: @utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19062vtkSMProxyGroupDomain does not Invoke DomainModifiedEvent2019-06-04T07:56:58-04:00Mathieu Westphal (Kitware)vtkSMProxyGroupDomain does not Invoke DomainModifiedEventvtkSMProxyGroupDomain never Invoke DomainModifiedEvent, even when the group is modified.
This forces Group Domain users to monitor proxy creation instead.vtkSMProxyGroupDomain never Invoke DomainModifiedEvent, even when the group is modified.
This forces Group Domain users to monitor proxy creation instead.https://gitlab.kitware.com/paraview/paraview/-/issues/19061Create "Reset only window layout to default settings"2019-05-30T14:20:26-04:00W. Alan ScottCreate "Reset only window layout to default settings"When a user selects Edit/ Reset to Default Settings, and the Reset custom settings to default dialog comes up, lets add the option somehow to ask - reset everything, or only reset window layout only.
This is needed because some users ac...When a user selects Edit/ Reset to Default Settings, and the Reset custom settings to default dialog comes up, lets add the option somehow to ask - reset everything, or only reset window layout only.
This is needed because some users accidentally click the X on the Properties tab, or drag it off, and don't know how to put it back. Reset to Default Settings is pretty draconian to just fix this simple problem. (Of course, being taught the correct way to get the tab back is really the answer. But, we work with what we got.)https://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/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/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/19038ParaView Quad Buffer Crystal Eyes stereo does not work on certain system conf...2022-04-01T12:28:31-04:00Mathieu Westphal (Kitware)ParaView Quad Buffer Crystal Eyes stereo does not work on certain system configuration"Crystal Eyes" stereo rendering has been reintroduced in ParaView master. However it does not seem to work on certain system.
How to reproduce :
- Use a stereo capable computer (Quad Buffer GPU, 120Hz screen, no compositor)
- check that..."Crystal Eyes" stereo rendering has been reintroduced in ParaView master. However it does not seem to work on certain system.
How to reproduce :
- Use a stereo capable computer (Quad Buffer GPU, 120Hz screen, no compositor)
- check that stereo is working on your system with `glxgears -stereo`
- Download ParaView 5.7.0 release (5.3 -> 5.6.0 is not working )
- ./bin/paraview --stereo --stereo-type="Crystal Eyes"
- Wavelet, Apply
- check for visible stereo
| GPU | Driver | OS | Desktop Environment | ParaView version | State |
| ------ | ------ | ------ | ------ | ------ | ------ |
| K620 | 390.116 / 440.32 | Ubuntu 16.04 | Any | 5.X | KO |
| K1100M | 390.? | Debian 9 | Xfce | ? | KO |
| P4000 | 390.116 | Ubuntu 18.04 | awesome | ? | OK |
| M4000 | ? | ? | ? | ? | OK |
| K4200 | ? | ? | ? | ? | OK |
| A6000 | 510.14 | Ubuntu 20.04 | OpenBox | 5.10.1 | KO |
| AMD WX3100 | 26.20.13028.13 | Windows 10 21H2 | - | 5.10.0 | OK* |
* OK - works
* KO - doesn't work
\* Generates OpenGL GL_DRAW_BUFFER cache state related warningshttps://gitlab.kitware.com/paraview/paraview/-/issues/19035StructuredGridVolumeRendering fails when run on 2 ranks with sanitizer2019-05-16T13:43:32-04:00Utkarsh AyachitStructuredGridVolumeRendering fails when run on 2 ranks with sanitizerOn `vall` which setups by various environment variables, the `StructuredGridVolumeRendering` fails when run with 2 ranks.
```
> env
MALLOC_CHECK_=3
MALLOC_PERTURB_=96
MEMCPY_CHECK_=1
MallocCheckHeapAbort=1
MallocCheckHeapEach=...On `vall` which setups by various environment variables, the `StructuredGridVolumeRendering` fails when run with 2 ranks.
```
> env
MALLOC_CHECK_=3
MALLOC_PERTURB_=96
MEMCPY_CHECK_=1
MallocCheckHeapAbort=1
MallocCheckHeapEach=1000000
MallocCheckHeapStart=1
MallocErrorAbort=1
MallocGuardEdges=1
MallocLogFile=/dev/null
MallocPreScribble=1
MallocScribble=1
```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/19018Add/update vthb file reader2019-05-13T13:07:19-04:00W. Alan ScottAdd/update vthb file readerWe need to add or modify a/the vthb file reader.
* When I try to open the attached .vthb file, ParaView doesn't know which reader to use.
* In a discourse issue, Mathieu said that he was able to correctly select these files, which the...We need to add or modify a/the vthb file reader.
* When I try to open the attached .vthb file, ParaView doesn't know which reader to use.
* In a discourse issue, Mathieu said that he was able to correctly select these files, which then didn't open correctly or crashed.
Lets start with this example, I believe from the VTK examples. (i.e., UUR)
[Gaussian3D.vthb](/uploads/51a97fdb5db7e81096c34dce69656ebb/Gaussian3D.vthb)