ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2022-09-18T22:23:23-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/21567pypython/pvbatch vtkMatplotlibMathTextUtilities parse failure2022-09-18T22:23:23-04:00Colin Starkpypython/pvbatch vtkMatplotlibMathTextUtilities parse failureWhen running pvbatch/pvpython on e.g.
```
SaveAnimation('animation_frames/frame.png', layout1, ImageResolution=[1920, 1080], FrameWindow=[0, 300])
```
failure occurs when parsing e.g.
```
$\epsilon_{rsp}=80.1$
```
giving the error
```
( ...When running pvbatch/pvpython on e.g.
```
SaveAnimation('animation_frames/frame.png', layout1, ImageResolution=[1920, 1080], FrameWindow=[0, 300])
```
failure occurs when parsing e.g.
```
$\epsilon_{rsp}=80.1$
```
giving the error
```
( 118.609s) [paraview]vtkMatplotlibMathTextUt:616 WARN| vtkMatplotlibMathTextUtilities (0x7ffa4e0666e0): Failed to compute rows and cols for cell : $\epsilon_{rsp}=80.1$
```
FWIW I get this error when instantiating pvpython/pvbatch:
```
Could not find platform dependent libraries <exec_prefix>
```
but it's presumably unrelated.https://gitlab.kitware.com/paraview/paraview/-/issues/21568State saved to python does not capture Data Axis Grid2023-05-24T08:05:45-04:00Kenneth MorelandState saved to python does not capture Data Axis GridWhen you save ParaView state as a python file (such as with `Save Catalyst State`), it does not save the visibility of the `Data Axis Grid` if it is turned on for an object.
To replicate, do the following:
1. Load `disk_out_ref` (or an...When you save ParaView state as a python file (such as with `Save Catalyst State`), it does not save the visibility of the `Data Axis Grid` if it is turned on for an object.
To replicate, do the following:
1. Load `disk_out_ref` (or any other data).
2. Turn on `Data Axis Grid` for that object. (Note, this is different than `Axis Grid`.)
3. Click on `Save State` and save to a .py file (not a .pvsm file).
4. Reset the ParaView session.
5. Open the python shell (`View` -> `Python Shell`).
6. Click on `Run Script` and load the state script just saved.
7. When the script is run, the data axis grid is not visible.
The state file is not capturing the `*Display.DataAxesGrid.GridAxesVisibility = 1` necessary to turn on the data axis grid for the object.https://gitlab.kitware.com/paraview/paraview/-/issues/21570Add trame to the superbuild2024-03-07T20:23:52-05:00Ben BoeckelAdd trame to the superbuildFiling here instead of the superbuild for easier project management purposes.
The current plan:
- use a venv (or equivalent) to manage trame with ParaView 5.11
Future ideas (tentative 5.12):
- have an option for "latest" trame for de...Filing here instead of the superbuild for easier project management purposes.
The current plan:
- use a venv (or equivalent) to manage trame with ParaView 5.11
Future ideas (tentative 5.12):
- have an option for "latest" trame for development/deployment test purposes
- add trame to the superbuild with an option for "some specific version" to ship with ParaView itself (probably cannot update external however); this would pin "latest" as of tagging and/or testing checkpoints
/cc @wascott @sebastien.jourdain @cory.quammen5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21571Use of RandomAttributes after GenerateIds makes Paraview drop scalar field of...2022-09-21T22:49:19-04:00Eve Le GuillouUse of RandomAttributes after GenerateIds makes Paraview drop scalar field of idsHi all,
I use Paraview 5.10.1.
I execute the following pipeline:
#### import the simple module from the paraview
from paraview.simple import *
# create a new 'Wavelet'
wavelet1 = Wavelet(registrationName='Wavelet1')...Hi all,
I use Paraview 5.10.1.
I execute the following pipeline:
#### import the simple module from the paraview
from paraview.simple import *
# create a new 'Wavelet'
wavelet1 = Wavelet(registrationName='Wavelet1')
# create a new 'Generate Ids'
generateIds1 = GenerateIds(registrationName='GenerateIds1', Input=wavelet1)
# create a new 'Random Attributes'
randomAttributes1 = RandomAttributes(registrationName='RandomAttributes1', Input=generateIds1)
randomAttributes1.GeneratePointScalars = 1
When looking at the produced results, instead of finding two scalar fields for the points, there is only one: RandomPointScalars. If RandomAttributes is used before GenerateIds, then it is PointIds that is found. But whatever the order of the two filters, a scalar field is dropped unintentionally.
When each filter is used with another filter, such as Elevation, the bug disappears.https://gitlab.kitware.com/paraview/paraview/-/issues/21575Seg fault when trying to render image in catalyst2023-11-08T21:13:56-05:00Boonthanome NouanesengsySeg fault when trying to render image in catalystI’m trying to generate an image in Catalyst (this is Catalyst 1.0) in our Pagosa code, which uses Paraview 5.9.1. The Catalyst adaptor in Pagosa has been working well for writing vtm files to disk. But whenever an image tries to be gener...I’m trying to generate an image in Catalyst (this is Catalyst 1.0) in our Pagosa code, which uses Paraview 5.9.1. The Catalyst adaptor in Pagosa has been working well for writing vtm files to disk. But whenever an image tries to be generated, a seg fault occurs. I’ll post the stacktrace of that at the end of the email, but the stacktrace indicates that the seg fault happens somewhere in the osmesa library.
I’m using a really simple catalyst script that just generates an image of a box. It doesn’t even access the simulation data. The script works with Flag, another catalyst-enabled code.
I then tried running a pvpython script that generates an image. When using the same paraview build that Pagosa uses, the pvpython script works. Next I tried using the filedriver_miniapp.py, using the same catalyst script, with the paraview build that Pagosa uses, and that also works in creating an image.
At this point I’m stumped on what to do next. It looks like Pagosa’s Paraview build works and can generate images using osmesa, but a seg fault occurs when using Catalyst. Is there anything else I can do to debug this further? I’m thinking the next step is to comment out everything in the Pagosa Catalyst adaptor except the necessary bits.
@patchett2002 @pkf @cory.quammen @yohann.bearzi
Below is the stacktrace generated from the seg fault:
```
Loguru caught a signal: SIGFPE
Stack trace:
77 0x40cbf9 /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x40cbf9]
76 0x2aca4b246555 __libc_start_main + 245
75 0x40cce2 /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x40cce2]
74 0x40d336 /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x40d336]
73 0x40f813 /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x40f813]
72 0x82beb3 /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x82beb3]
71 0x8a9c5c /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x8a9c5c]
70 0x8ff94e /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x8ff94e]
69 0x2aca46c83152 vtkCPAdaptorAPI::CoProcess() + 146
68 0x2aca46c8b720 vtkCPProcessor::CoProcess(vtkCPDataDescription*) + 1360
67 0x2aca46c725ae vtkCPPythonScriptPipeline::CoProcess(vtkCPDataDescription*) + 558
66 0x2aca59de0498 vtkPythonInterpreter::RunSimpleString(char const*) + 536
65 0x2aca470a5dc9 PyRun_SimpleStringFlags + 57
64 0x2aca470a5d3f PyRun_StringFlags + 143
63 0x2aca47053f99 PyEval_EvalCode + 41
62 0x2aca4705400b PyEval_EvalCodeEx + 107
61 0x2aca4705497e _PyEval_EvalCodeWithName + 2398
60 0x2aca4714acf5 _PyEval_EvalFrameDefault + 38037
59 0x2aca4714128e /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x29e28e) [0x2aca4714128e]
58 0x2aca46f40ab6 _PyFunction_FastCallKeywords + 774
57 0x2aca471479fa _PyEval_EvalFrameDefault + 24986
56 0x2aca4714128e /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x29e28e) [0x2aca4714128e]
55 0x2aca46f40874 _PyFunction_FastCallKeywords + 196
54 0x2aca4705497e _PyEval_EvalCodeWithName + 2398
53 0x2aca471479fa _PyEval_EvalFrameDefault + 24986
52 0x2aca4714128e /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x29e28e) [0x2aca4714128e]
51 0x2aca46f40874 _PyFunction_FastCallKeywords + 196
50 0x2aca4705497e _PyEval_EvalCodeWithName + 2398
49 0x2aca47147b5c _PyEval_EvalFrameDefault + 25340
48 0x2aca47055f62 /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x1b2f62) [0x2aca47055f62]
47 0x2aca46f4147b _PyFunction_FastCallDict + 459
46 0x2aca4705497e _PyEval_EvalCodeWithName + 2398
45 0x2aca471479fa _PyEval_EvalFrameDefault + 24986
44 0x2aca4714128e /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x29e28e) [0x2aca4714128e]
43 0x2aca46f40874 _PyFunction_FastCallKeywords + 196
42 0x2aca4705497e _PyEval_EvalCodeWithName + 2398
41 0x2aca4714acf5 _PyEval_EvalFrameDefault + 38037
40 0x2aca4714128e /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x29e28e) [0x2aca4714128e]
39 0x2aca46f40874 _PyFunction_FastCallKeywords + 196
38 0x2aca4705497e _PyEval_EvalCodeWithName + 2398
37 0x2aca47147b5c _PyEval_EvalFrameDefault + 25340
36 0x2aca4705607c /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x1b307c) [0x2aca4705607c]
35 0x2aca46f4181e PyCFunction_Call + 142
34 0x2aca93ecabb6 /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/paraview-5.9.1-crgiskfa46kkhbhmmqcj7ja6l42o2lll/lib64/python3.7/site-packages/paraview/modules/vtkRemotingViews.so(+0x18ebb6) [0x2aca93ecabb6]
33 0x2aca50661782 vtkSMSaveScreenshotProxy::WriteImage(char const*, unsigned int) + 1922
32 0x2aca506631c9 vtkSMSaveScreenshotProxy::CapturePreppedImages() + 313
31 0x2aca506664f3 vtkSMSaveScreenshotProxy::vtkStateView::CaptureImage() + 35
30 0x2aca5069bcdc vtkSMViewProxy::CaptureWindow(int, int) + 380
29 0x2aca5069c38d /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/paraview-5.9.1-crgiskfa46kkhbhmmqcj7ja6l42o2lll/lib64/libvtkPVServerManagerKit-pv5.9.so.1(+0x41c38d) [0x2aca5069c38d]
28 0x2aca5069c794 vtkSMViewProxy::CaptureWindowSingle(int, int) + 148
27 0x2aca5069cfd6 vtkSMViewProxy::CaptureWindowInternal(int, int) + 86
26 0x2aca5065ceac vtkSMRenderViewProxy::RenderForImageCapture() + 92
25 0x2aca5069b08e vtkSMViewProxy::StillRender() + 494
24 0x2aca506cc050 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 48
23 0x2aca506ce345 vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 101
22 0x2aca506d03f7 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 167
21 0x2aca5949c529 vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 41
20 0x2aca59499e25 vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 981
19 0x2aca5949b6df vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 303
18 0x2aca5949c8b7 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 855
17 0x2aca4e6bdd56 vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 37766
16 0x2aca505fb40c vtkPVRenderView::StillRender() + 140
15 0x2aca506020bc vtkPVRenderView::Render(bool, bool) + 2812
14 0x2aca50619b96 /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/paraview-5.9.1-crgiskfa46kkhbhmmqcj7ja6l42o2lll/lib64/libvtkPVServerManagerKit-pv5.9.so.1(+0x399b96) [0x2aca50619b96]
13 0x2aca505f027f vtkPVProcessWindow::PrepareForRendering() + 31
12 0x2aca510a8fa0 vtkOpenGLRenderWindow::Render() + 96
11 0x2aca5afcffd7 vtkRenderWindow::Render() + 183
10 0x2aca510a58ab vtkOpenGLRenderWindow::Start() + 27
9 0x2aca5115a39c vtkOSOpenGLRenderWindow::CreateOffScreenWindow(int, int) + 268
8 0x2aca5caedb49 OSMesaCreateContextAttribs + 665
7 0x2aca5c646eee /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x4ddeee) [0x2aca5c646eee]
6 0x2aca5cafba79 /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x992a79) [0x2aca5cafba79]
5 0x2aca5c9237fd /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x7ba7fd) [0x2aca5c9237fd]
4 0x2aca5c92428f /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x7bb28f) [0x2aca5c92428f]
3 0x2aca5c96e933 /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x805933) [0x2aca5c96e933]
2 0x2aca5c919665 /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x7b0665) [0x2aca5c919665]
1 0x2aca5cb21f7a /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x9b8f7a) [0x2aca5cb21f7a]
0 0x2aca5cab4eef /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x94beef) [0x2aca5cab4eef]
( 5.908s) [pvbatch ] :0 FATL| Signal: SIGFPE
```https://gitlab.kitware.com/paraview/paraview/-/issues/21577Allow global data to be used even without mesh data2024-03-07T20:23:52-05:00W. Alan ScottAllow global data to be used even without mesh dataI have a user that needs to be able to plot Exodus global data over time. However, he has no mesh data in the dataset. The Exodus reader reads this data, and the user can then run the plot global data over time filter. However, the IO...I have a user that needs to be able to plot Exodus global data over time. However, he has no mesh data in the dataset. The Exodus reader reads this data, and the user can then run the plot global data over time filter. However, the IOSS reader will not allow the user to run the plot global data over time filter. This feature hole needs to be fixed.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21579Change the way pqItemViewSearchWidget is applied.2022-09-28T12:05:17-04:00David ThompsonChange the way pqItemViewSearchWidget is applied.Currently `pqPVApplicationCore::startSearch()` has a hard-wired list of search exclusions (`pqSpreadsheetViewModel`), but some custom applications need to exclude additional model-views.
Rather than a fixed list of exclusions, we should...Currently `pqPVApplicationCore::startSearch()` has a hard-wired list of search exclusions (`pqSpreadsheetViewModel`), but some custom applications need to exclude additional model-views.
Rather than a fixed list of exclusions, we should query each `QAbstractItemView` to see if a [dynamic property](https://doc.qt.io/qt-6/qobject.html#setProperty) has been added to signal it should be excluded. Then pqSpreadsheetViewModel should set this property in its constructor and custom applications can do this as well. Only QAbstractItemViews without this property will be searched.
FYI @bob.obara @jwilson1881https://gitlab.kitware.com/paraview/paraview/-/issues/21580Line Width Styling of Extract Block Incorrectly Re-Colors Mesh Edges2023-01-12T11:39:59-05:00Halvor HerlyngLine Width Styling of Extract Block Incorrectly Re-Colors Mesh EdgesOS: macOS 12.6
ParaView Version: 5.10.1
Qt Version: 5.15.2
Hi,
I have been working on simulating flow in an axisymmetrical pipe with FEniCSx, and for this purpose I created a rectangular domain where the I tagged the boundary facets of...OS: macOS 12.6
ParaView Version: 5.10.1
Qt Version: 5.15.2
Hi,
I have been working on simulating flow in an axisymmetrical pipe with FEniCSx, and for this purpose I created a rectangular domain where the I tagged the boundary facets of my mesh with integers (1 for left boundary, 2 for right boundary). When writing the mesh and the mesh tags to an XDMF file with Dolfinx and opening the file in Paraview, the correct left and right boundaries of the domain are colored with different colors depending on their tag value (1 or 2). However, when using Extract Block and changing the Line Width in the Styling pane, there is a bug which leads to different (and incorrect) facets of the boundary being colored.![Screenshot_2022-09-28_at_22.00.49](/uploads/ba027a69e9437b528a27cd280dae70d9/Screenshot_2022-09-28_at_22.00.49.png)
![Screenshot_2022-09-28_at_22.01.15](/uploads/bc9a98bee9d9f86da14c06a281c0b164/Screenshot_2022-09-28_at_22.01.15.png)
Attached are two screenshots of the tagget facets of the mesh. In one of the pictures, where the linewidth is set to 1, the left and right boundaries are colored correctly with red and blue, respectively, as they were tagget with 1 and 2, respectively. In the other picture, where the linewidth is set to 10, the right boundary is suddenly colored both red and blue, and the left boundary does not change linewidth at all.
Best,
Halvorhttps://gitlab.kitware.com/paraview/paraview/-/issues/21581Hover on cells and Hover on point do not update when selection an element of ...2022-09-29T00:57:46-04:00Mathieu Westphal (Kitware)Hover on cells and Hover on point do not update when selection an element of the same ID in another blockHover on cells and Hover on point do not update when selection an element of the same ID in another block
Steps to repro:
- Run ParaView
- Open [USGBase_t1.vtm](/uploads/88c67cfdde9439578402337d07cda4fb/USGBase_t1.tgz), Apply
- Hover o...Hover on cells and Hover on point do not update when selection an element of the same ID in another block
Steps to repro:
- Run ParaView
- Open [USGBase_t1.vtm](/uploads/88c67cfdde9439578402337d07cda4fb/USGBase_t1.tgz), Apply
- Hover on cells
- Hover on the triangle strip (in block Domain2)
- Move mouse on the other block (Domain1)
- Tooltip does not update (because this cell has the same Id)
![a](/uploads/c1733853f6f23fcbb842641509747f22/a.png)
![b](/uploads/b254b1fe474e3302ee6de964b0536de6/b.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21582In Pythonshell warnings appear when using the OpenDataFile command2023-02-15T21:53:44-05:00Phil SmithIn Pythonshell warnings appear when using the OpenDataFile commandI tried this on both Linux and Mac 5.11.0 nightly. To reproduce:
Open the Python Shell using the view menu
canex2=OpenDataFile('/..../can2.ex2')
The can opens, but the following warnings appear:
```
warning: In unknown, line 0
warning...I tried this on both Linux and Mac 5.11.0 nightly. To reproduce:
Open the Python Shell using the view menu
canex2=OpenDataFile('/..../can2.ex2')
The can opens, but the following warnings appear:
```
warning: In unknown, line 0
warning: QLayout: Attempting to add QLayout "" to pqMetaDataPropertyWidget "", which already has a layout
warning: In unknown, line 0
warning: QLayout: Attempting to add QLayout "" to pqMetaDataPropertyWidget "", which already has a layout
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21584Save 2D grid as image give a bad result2022-10-04T09:02:05-04:00Charles GueunetSave 2D grid as image give a bad resultI try to save a regular gris as an image file (ctrl-s) but the result is far from the original data.
A test pipeline is the following:
1. Create a Uniform Grid (2D, set the first extent to 1-1 for example)
2. Add scalars with a random g...I try to save a regular gris as an image file (ctrl-s) but the result is far from the original data.
A test pipeline is the following:
1. Create a Uniform Grid (2D, set the first extent to 1-1 for example)
2. Add scalars with a random generator (check the type is `uchar`)
3. Use a pass array to only keep the generated point scalars
4. `Ctrl-s` and save as a jpg / png / tiff file, the result is a single column as shown on the right
![image](/uploads/3986336123867ea9ecfcec8aad7f44cc/image.png)
I do not know if this is related to the bug, but I can only save my image with a 1 componant `uchar` or `ushort` array, where I would expect 3 components and 4 components to also work.https://gitlab.kitware.com/paraview/paraview/-/issues/21588Selection Editor does not display Data Producer and Element Type2022-10-10T22:05:34-04:00Joachim PouderouxSelection Editor does not display Data Producer and Element TypeHow to reproduce:
- Create a `Point Source` with 1000 points in a radius of 1. Apply.
- Press 'g' and select some points.
- Open the `Selection Editor` panel.
- It displays an empty `Data Producer` with a Point `Element Type`.
- Pre...How to reproduce:
- Create a `Point Source` with 1000 points in a radius of 1. Apply.
- Press 'g' and select some points.
- Open the `Selection Editor` panel.
- It displays an empty `Data Producer` with a Point `Element Type`.
- Press `+` button in the editor
- `Data Producer` is now empty and `Element Type` too - even when selecting the added selection.
Note: I might be wrong and might just misunderstood the behavior of those fields.
![pv-seleditorbug](/uploads/9fa9d521a2caf50d937e9f6cfe52fb5d/pv-seleditorbug.png)
@spiros.tsalikis @mwestphalSpiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21590CellDataToPointData produce uninitialized results with dataset containing poi...2022-10-06T00:13:16-04:00Mathieu Westphal (Kitware)CellDataToPointData produce uninitialized results with dataset containing points without cellsCellDataToPointData produce uninitialized results with dataset containing points without cells
Steps to repro:
- run ParaView
- Cone, Apply
- Sphere, Apply
- ConvertToPointCloud, No Cells, Apply
- Select Cone and ConvertToPointCloud
- ...CellDataToPointData produce uninitialized results with dataset containing points without cells
Steps to repro:
- run ParaView
- Cone, Apply
- Sphere, Apply
- ConvertToPointCloud, No Cells, Apply
- Select Cone and ConvertToPointCloud
- AppendDataSet, Apply
- RandomAttributes, Cell Vectors, Apply
- CellDataToPointData, Apply
- Check array range -> Contains initialized values
Values should be NaN in that case IMO.https://gitlab.kitware.com/paraview/paraview/-/issues/21591OctreeImageFIlters test timeouts on windows with CRS mode.2022-10-06T10:36:46-04:00Spiros TsalikisOctreeImageFIlters test timeouts on windows with CRS mode.OctreeImageFIlters test timeouts on windows with CRS mode.OctreeImageFIlters test timeouts on windows with CRS mode.https://gitlab.kitware.com/paraview/paraview/-/issues/21592Bump up dataset size threshold for when lower LOD is used2024-03-07T20:23:53-05:00Cory Quammencory.quammen@kitware.comBump up dataset size threshold for when lower LOD is usedIt's set to 20MB, which is very low and likely to make ParaView's interactive rendering capabilities look poor to new users. Recommend bumping to 256MB at least, maybe larger.It's set to 20MB, which is very low and likely to make ParaView's interactive rendering capabilities look poor to new users. Recommend bumping to 256MB at least, maybe larger.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21593Some Qt element's labels are used for comparison in Qt/ folder2023-01-16T07:51:11-05:00NicolasBSome Qt element's labels are used for comparison in Qt/ folderIn these files, XML Labels are used for comparison in conditions:
* `Qt/ApplicationComponents/pqAddToFavoritesReaction.cxx:100`
* `Qt/Components/pqSettingsDialog.cxx:106`
* [`Qt/ApplicationComponents/pqProxyGroupMenuManager.cxx:693`](htt...In these files, XML Labels are used for comparison in conditions:
* `Qt/ApplicationComponents/pqAddToFavoritesReaction.cxx:100`
* `Qt/Components/pqSettingsDialog.cxx:106`
* [`Qt/ApplicationComponents/pqProxyGroupMenuManager.cxx:693`](https://gitlab.kitware.com/paraview/paraview/-/blob/af2fbde229f40f9ce71397eac575ae742df9adc7/Qt/ApplicationComponents/pqProxyGroupMenuManager.cxx#L691). ProxyName should be used instead of label.
* `Plugins/XRInterface/Plugin/pqXRInterfaceDockPanel.cxx:347`
As I intend to translate labels, we should refactor the code to avoid any incident.
* ~~`Qt/Components/pqLightsInspector.cxx:156`~~ fixed
See also: #21583https://gitlab.kitware.com/paraview/paraview/-/issues/21599Feature request: make camera animation keyframing similar to other 3d programs2023-06-15T10:41:16-04:00Devin BaylyFeature request: make camera animation keyframing similar to other 3d programsI ended up writing a macro to help make this easier for my own work, but there are issues with saving the keyframes I've created #21598 . That said, I think the macro is still worth looking at as a base for a simple improvement to the an...I ended up writing a macro to help make this easier for my own work, but there are issues with saving the keyframes I've created #21598 . That said, I think the macro is still worth looking at as a base for a simple improvement to the animation workflow.
Here's the community forum link that I started with that includes the macro code. https://discourse.paraview.org/t/animation-keytime-integer-error/10454
Here's the macro code for anyone interested.
```
from paraview.simple import *
kf = CameraKeyFrame()
anim = GetAnimationScene()
## change below by dividing by total
kf.KeyTime = anim.AnimationTime/anim.EndTime
print(kf.KeyTime)
rv = GetActiveViewOrCreate("RenderView")
print(rv)
campos = rv.CameraPosition
camfoc = rv.CameraFocalPoint
up = rv.CameraViewUp
kf.Position = campos
kf.FocalPoint = camfoc
kf.ViewUp =up
print(campos,camfoc)
pscale = rv.CameraParallelScale
# typically the camera will have been added after the default one
# todo figure out a better way to select by name Camera
cue = anim.Cues[1]
print(cue)
cue.KeyFrames.append(kf)
print("appended frame")
```https://gitlab.kitware.com/paraview/paraview/-/issues/21600Camera animation data not stored in pvsm when using macro to insert keyframes2023-06-15T10:45:19-04:00Devin BaylyCamera animation data not stored in pvsm when using macro to insert keyframesI'm finding that the keyframes that I'm inserting using my macro method (https://discourse.paraview.org/t/animation-keytime-integer-error/10454) don't survive a save, close and reload of the pvsm file. Any ideas about how to make these a...I'm finding that the keyframes that I'm inserting using my macro method (https://discourse.paraview.org/t/animation-keytime-integer-error/10454) don't survive a save, close and reload of the pvsm file. Any ideas about how to make these animation keyframes stick?
Here's a link to a screen cap with the issue shown.
https://drive.google.com/file/d/17EeDeTmN5fDGOg7LpN0GxM1fja47of6_/view?usp=sharing
I'm using paraview 5.11.
This is a copy of the issue from the community forum https://discourse.paraview.org/t/camera-animation-state-isnt-saving/10486.
In case it's helpful I have run a diff between these pvsms and I see a number of differences https://github.com/DevinBayly/paraview_code/commit/b778261f3fdabd23cc3baa2cb268d5234f5f91c9 but I'm not sure how to reconcile them in my macro since my paraview knowledge is early days.https://gitlab.kitware.com/paraview/paraview/-/issues/21602Unable to open any files on preview 5.11 ARM version2022-10-14T10:04:18-04:00Sushrut KumarUnable to open any files on preview 5.11 ARM versionI am unable to open any files on paraview 5.11 ARM for Mac M1. Even after loading Tecplot ASCII files it shows nothing. I even tried to open the example cases and even they do not open. They opened the first time I installed paraview but...I am unable to open any files on paraview 5.11 ARM for Mac M1. Even after loading Tecplot ASCII files it shows nothing. I even tried to open the example cases and even they do not open. They opened the first time I installed paraview but not later.https://gitlab.kitware.com/paraview/paraview/-/issues/21603GUI issues with the 2D transfer function2024-03-07T20:23:53-05:00Mathieu Westphal (Kitware)GUI issues with the 2D transfer function1. "Choose color box and alpha" button is always clickable
- run ParaView
- Wavelet, Apply, Volume rep, Show color map editor
- "Choose color box and alpha" is visible and clickable, it has no effet but it should not be clickable
2. "E...1. "Choose color box and alpha" button is always clickable
- run ParaView
- Wavelet, Apply, Volume rep, Show color map editor
- "Choose color box and alpha" is visible and clickable, it has no effet but it should not be clickable
2. "Edit 2D transfer function" is not a great name
- run ParaView
- Wavelet, Apply, Volume rep, Show color map editor
- There is a "edit 2D transfer function" checkbox, it should read "Use 2D transfer function" imo
3. In 2D transfer function mode, unchecking "Automatic histo recompute" do not enable the compute histogram button
- run ParaView
- Wavelet, Apply, Volume rep, Show color map editor
- Check "edit 2D transfer function" checkbox
- Check "Automatically recompute histogram" checkbox, "Compute histogram" button become greyed out
- Uncheck "Automatically recompute histogram" checkbox, "Compute histogram" button stays greyed out, unexecpted
4. Previous issue cause multiple issue with the classic histogram
Interacting with the classic histogram after three does not work as execpted, but I expect these issue to be gone once 3 is resolved.
@sankhesh5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21604ExposedProperties label is not used to wrap the property in python2022-10-17T01:33:05-04:00Mathieu Westphal (Kitware)ExposedProperties label is not used to wrap the property in pythonIn ParaView, the label is used to generate the python wrapping of a property, eg:
```
<IntVectorProperty command="SetNumberOfScalarComponents"
default_values="1"
name="NumberOfScal...In ParaView, the label is used to generate the python wrapping of a property, eg:
```
<IntVectorProperty command="SetNumberOfScalarComponents"
default_values="1"
name="NumberOfScalarComponents"
label="MyPrettyLabel"
number_of_elements="1">
<IntRangeDomain name="range" />
<Documentation>This property specifies the number of components the
scalar value at each pixel or voxel has (e.g., RGB - 3 scalar
components).</Documentation>
</IntVectorProperty>
```
It will allow to run :
`reader.MyPrettyLabel` instead of using `NumberOfScalarComponents`.
However, when exposing a property of a subproxy through ExposedProperty, eg:
```
<SubProxy>
<Proxy name="Reader"
proxygroup="internal_sources"
proxyname="ImageReaderCore"></Proxy>
<ExposedProperties>
<Property name="DataScalarType" />
<Property name="DataByteOrder" />
<Property name="DataOrigin" />
<Property name="DataSpacing" />
<Property name="NumberOfScalarComponents" />
<Property name="FileLowerLeft" />
<Property name="ScalarArrayName" />
</ExposedProperties>
</SubProxy>
```
The label is used to generate the proxy GUI, but not to wrap the proxy in python.
To reproduce:
- In `VTKExtensions/IOImage/Resources/readers_pv_ioimage.xml`, add a label to NumberOfScalarComponents RAW image reader proxy
- Rebuild paraview
- Run paraview
- Open a .raw
- Label is correct in ui
- Open python shell
```
s=GetActiveSource()
s.MyPrettyLabel -> KO
s.NumberOfScalarComponents -> OK
```
FYI @cory.quammenhttps://gitlab.kitware.com/paraview/paraview/-/issues/21605Cannot Load Time-Series Ensight Data (*.case file format)2022-10-18T04:33:55-04:00Andrew CarlsonCannot Load Time-Series Ensight Data (*.case file format)Opening an ensight case file formatted for a single data point (i.e. transient or single point in time) works fine...
Having a *.case file that points several data files does not work.
I can open it with a work around. And that is:
...Opening an ensight case file formatted for a single data point (i.e. transient or single point in time) works fine...
Having a *.case file that points several data files does not work.
I can open it with a work around. And that is:
1. Replace the wildcard * with ****
2. Replace the "filename numbers file:" with "filename numbers:" and the list of numbers
3. Repalce the "time values file:" with "time values:" and the times that correspond to each of the filenames
For example, see the attached original ensight data and adjusted to get it working.
- 01_transient_original_ensight_results
- 02_transient_modified_ensight_results
Also there, as a comparison is results from a steady state run (00_steadyState_ensight_results), to show it also works if only a single data point is indicted
My ensight data was created from CFD software Simerics... but this should not be relevant.https://gitlab.kitware.com/paraview/paraview/-/issues/21606Quadratic-Linear Hexahedron Element type2023-09-29T04:44:17-04:00MiguelVCarvalhoQuadratic-Linear Hexahedron Element typeGood afternoon,
Is it possible to output a quadratic-linear hexahedron to Paraview? I can do it for both an 8-node linear hexahedron and a 20-node quadratic hexahedron but I need to view a quadratic cohesive element that has 16 nodes an...Good afternoon,
Is it possible to output a quadratic-linear hexahedron to Paraview? I can do it for both an 8-node linear hexahedron and a 20-node quadratic hexahedron but I need to view a quadratic cohesive element that has 16 nodes and is quadratic in the surfaces and linear in the normal direction.
Something like:
15----14----13
/| /|
16 | 12 |
/ | / |
9----10----11 |
| | | | 3D COHESIVE QUADRATIC
| 7-----6-|---5 16-NODED ELEMENT
| / | /
| 8 | 4
|/ |/
1-----2-----3
From what I could find, this type of element does not exist in the ([VTK source code](https://gitlab.kitware.com/vtk/vtk/blob/master/Common/DataModel/vtkCellType.h)).https://gitlab.kitware.com/paraview/paraview/-/issues/216072D transfer functions and editor in ParaView adding 2nd histogram box2024-03-07T20:23:53-05:00Phil Smith2D transfer functions and editor in ParaView adding 2nd histogram boxUsing the following procedure, adding more than one box in the histogram, it will add the boxes on top of each other and not be apparent that another box was added. I would suggest whenever a new box is added, it be centered wherever the...Using the following procedure, adding more than one box in the histogram, it will add the boxes on top of each other and not be apparent that another box was added. I would suggest whenever a new box is added, it be centered wherever the mouse is within the histogram box.
* Open `Sources` > `Data Objects` > `Wavelet`
* Switch representation to `Volume`
* Enable `Advanced` on the Properties panel.
* Scroll to the `Volume Rendering` group on the Properties panel and enable `Use 2D Transfer Function`
* Open the `Color Map Editor` to reveal the 2D histogram of the data
* Edit the `Number of Bins` property (to 256, say)
* Update the 2D histogram by clicking on the `Compute data histogram` (![image](https://gitlab.kitware.com/paraview/paraview/uploads/f45ca2570aa626154a2c42523de2cd53/image.png)) button next to the histogram.
* Double-click on the histogram to add a new transfer function box
* Click and drag the box to change the volume rendering transfer function. You can also edit the box size by clicking and dragging on the corners of the box.
* Add another box by double-clicking as above.
This second box will appear at the same location and size of the first box, so it appears as though the second box was not created.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/216093D Widget color and interaction consistency2022-11-07T09:33:14-05:00Aron Helser3D Widget color and interaction consistency3D widgets in VTK/ParaView use inconsistent color and interaction schemes. It would be good to try to make them consistent. A possible model is `vtkDisplaySizedImplicitPlaneRepresentation` which was implemented Oct 2021.
Widgets could u...3D widgets in VTK/ParaView use inconsistent color and interaction schemes. It would be good to try to make them consistent. A possible model is `vtkDisplaySizedImplicitPlaneRepresentation` which was implemented Oct 2021.
Widgets could use this pattern:
* Foreground color for all informational objects, like bounding boxes or intersection outlines, which can't be grabbed. Typically white.
* Handle/Interaction color for all objects that can be grabbed, like axes or center points. Current PV default is green.
* Selected Handle/Interaction color, for the handle that is hovered and available to be changed or currently being changed after click/drag has started. Current PV default is red.
(Aside: the current PV defaults of red-green are a poor choice for the most common color-blindness.)
Another area to examine is shortcut keys. Some widgets use "p", some use "1" and "2" for picking points, and all of them are hard-coded. ParaView now includes a shortcut customization dialog for menus, which could be extended for widgets.
Widgets could also be updated to use `vtkNew` for memory management.
This is a potential follow-on to https://gitlab.kitware.com/paraview/paraview/-/issues/20599 and https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5965
@wascott @cory.quammenhttps://gitlab.kitware.com/paraview/paraview/-/issues/21612TimestepValues for AMReXParticles do not align with AMReXGrid2024-03-07T20:23:53-05:00Landon OwenTimestepValues for AMReXParticles do not align with AMReXGridOpening a plot file generated using the AMReX library for a gas phase solution, I get timestep values that match the solution time. However, if I open the particle portion of the file (which was generated using the AMReX particle library...Opening a plot file generated using the AMReX library for a gas phase solution, I get timestep values that match the solution time. However, if I open the particle portion of the file (which was generated using the AMReX particle library), the time steps are listed simply as integers and added to end of the original time values. I am using ParaView version 5.10.1 on MacOS, but the problem also shows up on my Ubuntu machine. I have attached a tar file of plot files that can demonstrate the issue. As a side note, I had to change the version number in `particle/Header` in accordance with the issue mentioned [here](https://gitlab.kitware.com/paraview/paraview/-/issues/21279).
To recreate the issue, open the files with ParaView twice, the first time selecting `AMReX/BoxLib Grid Reader` and the second time selecting `AMReX/BoxLib Particle Reader`. If a workaround using pvpython is possible, I would also appreciate that in the meantime.
[particle_plots.tar](/uploads/e6b5ab24bfc817249c197a6cd8575965/particle_plots.tar)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21613IOSS reader fails reading global data for non standard file range2024-03-07T20:23:53-05:00W. Alan ScottIOSS reader fails reading global data for non standard file rangeIOSS reader is failing to read global data for non standard file ranges. Here is how to replicate.
* Copy can.exo into a workstace directory, such as "sandbox".
* In your sandbox,
* cp can.exo can.e.4.0, cp can.exo can.e.4.1, cp can.ex...IOSS reader is failing to read global data for non standard file ranges. Here is how to replicate.
* Copy can.exo into a workstace directory, such as "sandbox".
* In your sandbox,
* cp can.exo can.e.4.0, cp can.exo can.e.4.1, cp can.exo can.e.4.2, cp can.exo can.e.4.3
* We now have a working 4 file Exodus dataset. Headers, and global data are the same between all files.
The IOSS reader uses a performance trick reading header and global data. The headers and globals between all files must be the same, or technically the dataset is bad. In practice, sometimes a dataset will have a correct header in the 0th file, and the others will be empty. No matter, the global data must be the same. The trick is that we no longer read every file, finding global data for every file, but rather read the 0th file only and use the 0th file's header and global data for all files. Works well, and gave us a huge performance boost.
* Open can.e.4. Apply.
* Notice there are 44 timesteps.
* On the Properties tab, change File Range to be 1 to 3. We should now be using file 1 for header and global data. Apply.
All global data has gone away, including all timesteps other than time step zero. It should have been read from file 1, the first file in the series we are using. This is a bug.
@cory.quammen Showstopper for the 5.12 release. Must not slip. Not required for 5.11.0 release, as users can always use the Legacy Exodus Reader.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21616Feature: "Set reader as default" button should save extension of file opened.2022-12-01T12:52:53-05:00Massimiliano LeoniFeature: "Set reader as default" button should save extension of file opened.The "Set reader as default" button in the "Open Data With..." dialog saves the extensions associated with the reader, as opposed to the extension of the file that the user is trying to open. This can lead to confusion like the original b...The "Set reader as default" button in the "Open Data With..." dialog saves the extensions associated with the reader, as opposed to the extension of the file that the user is trying to open. This can lead to confusion like the original bug report.
One possible solution is to ask the user to set the intended extension (or regexp) after this button is pressed.
Original bug report: [REGRESSION] Cannot open Fides .bp files
The current `master` revision crashes when trying to open a Fides .bp file with the error message:
```
what(): ERROR: neither vtk.xml file or bp attribute was found in file.bp
```
The same file gave no problems up to not long ago [past the current release].https://gitlab.kitware.com/paraview/paraview/-/issues/21617pasting clipboard filename [paraview 5.10.0 / windows]2024-03-07T20:23:54-05:00Theo Igapasting clipboard filename [paraview 5.10.0 / windows]If I want to open a data file by pasting the clipboard to the "Open file" window, I get always a `file:///` prefix in the window, that has to be manually deleted.
Other programs do not show this issue.
![sequence](/uploads/2654756a716d...If I want to open a data file by pasting the clipboard to the "Open file" window, I get always a `file:///` prefix in the window, that has to be manually deleted.
Other programs do not show this issue.
![sequence](/uploads/2654756a716d4cdc18bb8869a844988c/sequence.mp4)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21618Adding Export Animated Scene command to Python2022-10-24T05:12:24-04:00Xabier Morales FerezAdding Export Animated Scene command to PythonAdding a Python command for the Export Animated Scene tool, similar to ExportView(), to automatically export the scenes through macros.Adding a Python command for the Export Animated Scene tool, similar to ExportView(), to automatically export the scenes through macros.https://gitlab.kitware.com/paraview/paraview/-/issues/21620Cell Data is not supported in exporting to GLTF model2022-10-25T23:07:23-04:00Jimmy-KLCell Data is not supported in exporting to GLTF modelIf we use cell data to color the model, the exported gltf model will have an error. Please check the question that I submitted at the community support: [export-glft-error-from-paraview](https://discourse.paraview.org/t/export-glft-error...If we use cell data to color the model, the exported gltf model will have an error. Please check the question that I submitted at the community support: [export-glft-error-from-paraview](https://discourse.paraview.org/t/export-glft-error-from-paraview/10585)
And also I found the coordinate system will be different in gltf model from in paraview. It seems the y and z axis is changed.https://gitlab.kitware.com/paraview/paraview/-/issues/21621Coloring categorical is limited to 32 colors2022-10-25T23:02:41-04:00Eloise BColoring categorical is limited to 32 colorsHello,
I want to display a discrete field with one hundred of values. I click on "Interpret value as category" but there is an error message which says this is limited to 32 colors:
![40d786ed90c9149453a422a0a0f3c445567d1a50](/uploads...Hello,
I want to display a discrete field with one hundred of values. I click on "Interpret value as category" but there is an error message which says this is limited to 32 colors:
![40d786ed90c9149453a422a0a0f3c445567d1a50](/uploads/fb2cbfc83c24f30be6fa52ae2bc75f3d/40d786ed90c9149453a422a0a0f3c445567d1a50.png)
To reproduce, we can try to display the "ids" field from the can.ex2 data as categories.
Is it possible to remove this limit to 32 colors ?
Regards,
Eloïsehttps://gitlab.kitware.com/paraview/paraview/-/issues/21622Any new render view will show sphere when the stream tracer is selected, but...2024-03-07T20:23:54-05:00Phil SmithAny new render view will show sphere when the stream tracer is selected, but not applied yetTested on Windows and Mac. This does not happen on a Mac. Test conditions: ParaView v 5.11.0-RC2
- Open disk_out_ref.ex2 and apply
- Filter-> StreamTracer. Show Sphere is selected
- Open new RenderView
The new RenderView should be blank...Tested on Windows and Mac. This does not happen on a Mac. Test conditions: ParaView v 5.11.0-RC2
- Open disk_out_ref.ex2 and apply
- Filter-> StreamTracer. Show Sphere is selected
- Open new RenderView
The new RenderView should be blank, but it shows the sphere within the whole view as shown in the attachment. This will happen with any new renderview. If more than one is opened under these conditions, only the last one will display the sphere.
![StreamTracerPic](/uploads/e46b4aeeddd2260de2432ab72166a882/StreamTracerPic.png)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21623Catalyst Live causes extractors to fail (Catalyst 2.0)2023-11-08T21:08:29-05:00Caitlin RossCatalyst Live causes extractors to fail (Catalyst 2.0)Initially I thought this was an issue with using Fides with Catalyst 2, but I was able to reproduce this with one of the Catalyst2 examples.
When you have an extractor in your Catalyst script and you try to use Catalyst Live, if you hav...Initially I thought this was an issue with using Fides with Catalyst 2, but I was able to reproduce this with one of the Catalyst2 examples.
When you have an extractor in your Catalyst script and you try to use Catalyst Live, if you have more than one proxy in your pipeline, you end up getting the following error, starting with the next time step after you pull extracts to ParaView to be visualized:
```
( 144.630s) [pvbatch ]vtkSMImageExtractWriter:174 ERR| . . . . vtkSMImageExtractWriterProxy (0x565406c76990): No view provided to generate extract from!
( 144.630s) [pvbatch ]vtkSMExtractsController:191 ERR| . . . . vtkSMExtractsController (0x565408983890): Write failed! Extracts may not be generated correctly!
```
The first step is successful, and checking the address of the writer proxy on the extractor proxy, it's different from the writer proxy listed in the later steps where the extractor fails. So somehow the "Writer" proxy property is being changed, but I can't figure out why or how.
That may end up being a weird side effect of a different issue though. I did some more digging and found that on the Live side, `vtkSMLiveInsituLinkProxy::MarkStateDirty()` is being called when I think it shouldn't be. It seems that is a callback for a `vtkCommand::PropertyModifiedEvent`, but I think nothing should be being modified on these extracts.
This seems to be getting triggered by `pqInputSelectorWidget::updateComboBox()`. In `pqInputSelectorWidget::updateComboBox()`, the list of `pqPipelineSource`s is iterated through, to set the pipeline proxies as the Input proxy to the `FindDataHelper` proxy.
When it's setting the Input Connection on the `FindDataHelper` proxy, the index is always 0, so when `PPInternals->Set()` is called, it always ends up returning true, leading to `Modified()` being called and resulting in `MarkStateDirty()` being called.
In the case there's only a single proxy in the pipeline (e.g., `grid` in the Catalyst2 examples), this all seems to work correctly. The calls to `PPInternals->Set()` ends up returning false, because that proxy is saved and matches the proxy, so `Modified` and `MarkStateDirty` are not called.
But once you add another proxy to the pipeline, both proxies will be saved into `PPInternals`, but both at index 0 in the vector `Proxies`, so in subsequent steps, it will basically just keep overwriting on these `PPInternals->Set()` calls, returning true and always marking the property as modified.
It doesn't seem to me that this should be linked to the extractor/writer issue described earlier, but in `vtkSMLiveInsituLinkProxy.cxx`, if I just set `StateDirty` to always be false, the extractor works correctly when using Catalyst Live. I'm not sure what the actual solution should be.
Not sure who to tag, perhaps @c.wetterer-nelson @danlipsa? Or maybe @francois.mazen?https://gitlab.kitware.com/paraview/paraview/-/issues/21626PlotDataOverTime is not naming blocks correcty2022-10-26T21:26:46-04:00Mathieu Westphal (Kitware)PlotDataOverTime is not naming blocks correctyPlotDataOverTime and PlotSelectionOverTime are not naming blocks correctly when working with composite dataset
- run ParaView
- Open can.ex2, Apply, notice blocks are named Block1 and Block2
- PlotDataOverTime, Apply
- Blocks are named...PlotDataOverTime and PlotSelectionOverTime are not naming blocks correctly when working with composite dataset
- run ParaView
- Open can.ex2, Apply, notice blocks are named Block1 and Block2
- PlotDataOverTime, Apply
- Blocks are named BlockId==2 and BlockId==4, which do not make any sense for the user
- Block name should be conserved through the filtershttps://gitlab.kitware.com/paraview/paraview/-/issues/21628Can't hide widget on splitted view2023-01-26T09:14:43-05:00Charles GueunetCan't hide widget on splitted viewUsing ParaView master, I have the following strange behavior:
![widget_clip](/uploads/450de72e6b95203ad0cb1500c47fff09/widget_clip.gif)
Once I split a window, I can't hide the clip widget anymore (same for transform widget). It is alway...Using ParaView master, I have the following strange behavior:
![widget_clip](/uploads/450de72e6b95203ad0cb1500c47fff09/widget_clip.gif)
Once I split a window, I can't hide the clip widget anymore (same for transform widget). It is always shown on one of the two window.
It can even appear spontaneously under the mouse during interact (instead of moving the camera).
If I go to a third render view, empty, it is still there, but then, coming back to the first split view, a focus on a view may remove one of the widget.
How to reproduce:
* Wavelet
* Transform
* ExtractSurface
* THEN split
* Now we are in the strange state: see this minimal gif:
![widget_min](/uploads/c0d1844a08de2bc580a95e325e0c76ab/widget_min.gif)
It seems this error is in two part:
* The appearance of the widget seems to be weird because of the refresh of the view. Because refreshing more would impact perf, this may be acceptable
* The controle of the widget appearance break once we split the view.
Related discourse: https://discourse.paraview.org/t/paraview-5-10-clip-filter-hide-widget-not-working-after-active-another-view-in-same-layout/9533
@sankhesh @mwestphal @cory.quammen @lucas.givord FYIhttps://gitlab.kitware.com/paraview/paraview/-/issues/21633[5.11.0-RC2] CGNS reload + different base selection => extract block incorrect2024-03-07T20:23:54-05:00Menno Deij - van Rijswijk[5.11.0-RC2] CGNS reload + different base selection => extract block incorrectSteps to reproduce:
1. load `Example_NFace_n.cgns` from ExternalData/Testing/Data
2. Select `Base_Surface_Elements` and then Apply
3. Unselect `Base_Surface_Elements` and select `Base_Volume_Elements`, then right-click the source and ch...Steps to reproduce:
1. load `Example_NFace_n.cgns` from ExternalData/Testing/Data
2. Select `Base_Surface_Elements` and then Apply
3. Unselect `Base_Surface_Elements` and select `Base_Volume_Elements`, then right-click the source and choose `"Reload files > Existing files"`
3. Verify that selected base is `Base_Volume_Elements`
4. Add `Extract Block` filter
5. `Extract Block` filter is populated with blocks from the `Base_Surface_Elements`, not the currently selected `Base_Volume_Elements`
I expected the Extract Block filter to have the block from Base_Volume_Elements to choose.
@MicK7 - Any idea why this happens?5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21635Volume rendering of multiblocks of vtkImageData stops working above 32 blocks2022-11-01T21:41:49-04:00Cory Quammencory.quammen@kitware.comVolume rendering of multiblocks of vtkImageData stops working above 32 blockshttps://gitlab.kitware.com/paraview/paraview/-/issues/21637ParticleTracer segfault with distributed server and non-distributed input2022-11-01T20:31:59-04:00Mathieu Westphal (Kitware)ParticleTracer segfault with distributed server and non-distributed inputParticleTracer segfault with distributed server and non-distributed input
Steps to reproduce:
- `mpirun -np 2 ./bin/pvserver`
- run ParaView, connect to server
- Open [flow.*.vtk](/uploads/5a406b394e12a85f49fb77b655144be5/flow.tgz) (dat...ParticleTracer segfault with distributed server and non-distributed input
Steps to reproduce:
- `mpirun -np 2 ./bin/pvserver`
- run ParaView, connect to server
- Open [flow.*.vtk](/uploads/5a406b394e12a85f49fb77b655144be5/flow.tgz) (data is not distributed, all on rank 0)
- Create a point source anywhere
- Create a particle tracer on the flow and select point source as seed
- Apply
- rank 1 segfault
```
( 114.000s) [pvserver.1 ]vtkParticleTracerBase.c:448 ERR| vtkPParticleTracer (0x555557f94c80): Couldn't find vector array
( 114.000s) [pvserver.1 ]vtkParticleTracerBase.c:906 ERR| vtkPParticleTracer (0x555557f94c80): InitializeInterpolator failed
Thread 1 "pvserver" received signal SIGSEGV, Segmentation fault.
vtkParticleTracerBase::GetCacheDataTime (this=0x555557f94c80, i=0) at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1546
1546 return this->CachedData[i]->GetInformation()->Get(vtkDataObject::DATA_TIME_STEP());
(gdb) bt
#0 vtkParticleTracerBase::GetCacheDataTime (this=0x555557f94c80, i=0)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1546
#1 0x00007fffeca6bf0f in vtkParticleTracerBase::Execute (this=0x555557f94c80,
inputVector=0x5555586fb1f0)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:887
#2 0x00007fffed3b0f86 in vtkPParticleTracerBase::Execute (
this=0x555557f94c80, inputVector=0x5555586fb1f0)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/ParallelFlowPaths/vtkPParticleTracerBase.cxx:75
#3 0x00007fffeca6ebca in vtkParticleTracerBase::RequestData (
this=0x555557f94c80, request=0x555558b42320, inputVector=0x5555586fb1f0,
outputVector=0x555557ca16e0)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1192
#4 0x00007fffeca6710e in vtkParticleTracerBase::ProcessRequest (
this=0x555557f94c80, request=0x555558b42320, inputVector=0x5555586fb1f0,
outputVector=0x555557ca16e0)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:230
```
Of course, using a RedistributeDataSet before the ParticleTracer fixes the issue.https://gitlab.kitware.com/paraview/paraview/-/issues/21639GenerateTimeSteps + ParticleTracer segfaults2022-11-11T04:52:44-05:00Mathieu Westphal (Kitware)GenerateTimeSteps + ParticleTracer segfaultsUsing a ParticleTracer after GenerateTimeSteps can segfaults.
Steps to reproduce:
- run ParaView
- Open [foam.vtu](https://send.kitware.io/download.php?id=1392&token=5D9r4QbLDjLhEejt81wDd5vc7r6mjTw3), Apply
- Generate timesteps, generat...Using a ParticleTracer after GenerateTimeSteps can segfaults.
Steps to reproduce:
- run ParaView
- Open [foam.vtu](https://send.kitware.io/download.php?id=1392&token=5D9r4QbLDjLhEejt81wDd5vc7r6mjTw3), Apply
- Generate timesteps, generate 10 ts, Apply
- Create a point source, -19, 100, 80, Apply
- ParticleTracer on foam.vtu, point source as seed, Apply
- Play animation back and forth until segfault
```
Thread 1 "paraview" received signal SIGSEGV, Segmentation fault.
0x00007fffd9670675 in vtkParticleTracerBase::CalculateVorticity (this=0x55556680b340, cell=0x0, pcoords=0x7fffffffa250, cellVectors=0x5555660fd1f0, vorticity=0x7fffffffa270) at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1537
1537 cell->Derivatives(0, pcoords, cellVel, 3, derivs);
(gdb) bt
#0 0x00007fffd9670675 in vtkParticleTracerBase::CalculateVorticity (this=0x55556680b340, cell=0x0, pcoords=0x7fffffffa250,
cellVectors=0x5555660fd1f0, vorticity=0x7fffffffa270)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1537
#1 0x00007fffd967167c in vtkParticleTracerBase::SetParticle (this=0x55556680b340, info=..., velocity=0x7fffffffaab0,
interpolator=0x555568605da0, particleId=0, cellVectors=0x5555660fd1f0)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1777
#2 0x00007fffd966f9e5 in vtkParticleTracerBase::IntegrateParticle (this=0x55556680b340,
it={CurrentPosition = {x = {-16.698808670043945, 93.088241577148438, 83.561920166015625, 0}}, CachedDataSetId = {0, 0}, CachedCellId = {-1, -1}, LocationState = 0, SourceID = 0, TimeStepAge = 1, InjectedPointId = 4, InjectedStepId = 0, UniqueParticleId = 0, SimulationTime = 0, ErrorCode = 0, age = 0, rotation = 0, angularVel = -8.21364447e-05, time = 0, speed = 10.0119152, PointId = 0, TailPointId = -1}, currentTime=0, targetTime=0, integrator=0x555566839d50, interpolator=0x555568605da0,
cellVectors=0x5555660fd1f0, particleCount=std::atomic<long long> = { 1 }, eraseMutex=..., sequential=true)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1407
#3 0x00007fffd9672dbd in vtkParticleTracerBaseNamespace::ParticleTracerFunctor::operator() (this=0x7fffffffadd0, begin=0,
end=4) at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:844
#4 0x00007fffd966db67 in vtkParticleTracerBase::Execute (this=0x55556680b340, inputVector=0x5555665da620)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1047
#5 0x00007fffd9ec6f86 in vtkPParticleTracerBase::Execute (this=0x55556680b340, inputVector=0x5555665da620)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/ParallelFlowPaths/vtkPParticleTracerBase.cxx:75
#6 0x00007fffd966ebca in vtkParticleTracerBase::RequestData (this=0x55556680b340, request=0x555566857050,
inputVector=0x5555665da620, outputVector=0x55556684fa80)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:1192
#7 0x00007fffd966710e in vtkParticleTracerBase::ProcessRequest (this=0x55556680b340, request=0x555566857050,
inputVector=0x5555665da620, outputVector=0x55556684fa80)
at /home/glow/dev/paraview/pv1/src/VTK/Filters/FlowPaths/vtkParticleTracerBase.cxx:230
#8 0x00007ffff068a64d in vtkExecutive::CallAlgorithm (this=0x55556684f970, request=0x555566857050, direction=1,
inInfo=0x5555665da620, outInfo=0x55556684fa80)
at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkExecutive.cxx:735
#9 0x00007ffff06809da in vtkDemandDrivenPipeline::ExecuteData (this=0x55556684f970, request=0x555566857050,
inInfo=0x5555665da620, outInfo=0x55556684fa80)
at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:462
#10 0x00007ffff0673bd9 in vtkCompositeDataPipeline::ExecuteData (this=0x55556684f970, request=0x555566857050,
inInfoVec=0x5555665da620, outInfoVec=0x55556684fa80)
at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx:163
```https://gitlab.kitware.com/paraview/paraview/-/issues/21640[5.11.0-RC2] Load State is different than File > Recent Files > Load *.pvsm file2022-11-02T22:18:09-04:00Menno Deij - van Rijswijk[5.11.0-RC2] Load State is different than File > Recent Files > Load *.pvsm fileIf I choose File > Load State ... and select a state *.pvsm file, a second question pops up asking me how to select the files (from file, select from directory, select files).
If I choose File > Recent Files > and select the same state ...If I choose File > Load State ... and select a state *.pvsm file, a second question pops up asking me how to select the files (from file, select from directory, select files).
If I choose File > Recent Files > and select the same state *.pvsm file, the second question does not pop up, and the state immediately loads with the "files from file".
It would be nice if loading a state file from the MRU list has the same behavior, i.e. asking me where I would like to get my files from.https://gitlab.kitware.com/paraview/paraview/-/issues/216413DGlyphs Cylinder Orientation Direction Vector Bug2022-11-15T09:58:36-05:00František Prinz3DGlyphs Cylinder Orientation Direction Vector BugThe orientation vector in Orientation Mode Direction for Glyph Type Cylinder is not ident with the symmetrical axis of revolution but perpendicular to it. I suppose there is a bug because another types (Cone, Arrow) are defined correctly...The orientation vector in Orientation Mode Direction for Glyph Type Cylinder is not ident with the symmetrical axis of revolution but perpendicular to it. I suppose there is a bug because another types (Cone, Arrow) are defined correctly paralel axis of revolution.
Could you please fix it?
Thankshttps://gitlab.kitware.com/paraview/paraview/-/issues/21643On Windows pvpython window freezes when moved2022-11-03T09:07:12-04:00Phil SmithOn Windows pvpython window freezes when movedThis was tested with windows paraview v5.11.0-RC2
If a window is created by pvpython interactively, then the window is moved, pvpython can no longer control the widow. Here is the test case:
- Launch pvpython on Windows( I used Windows10...This was tested with windows paraview v5.11.0-RC2
If a window is created by pvpython interactively, then the window is moved, pvpython can no longer control the widow. Here is the test case:
- Launch pvpython on Windows( I used Windows10 cmd line)
- from paraview.simple import *
- sphere = Sphere()
- Show()
- Render()
- Move the window
- shrink = Shrink()
- Hide(sphere)
- Show()
- Render()....It will not hide the sphere
If the mouse is placed within the window the spinning disk appears, You can move the window again by grabbing the top, but it still will not respond. You can exit the window by clicking on the X in the top right corner, or typing exit() in pvpython. It will also exit pvpython if exit() it typedhttps://gitlab.kitware.com/paraview/paraview/-/issues/21645Reset Session will not Reset your session when in interactive mode with pvpython2022-11-04T16:21:22-04:00Phil SmithReset Session will not Reset your session when in interactive mode with pvpythonResetSession() command will not do anything when performed in interactive mode via pypython. To duplicate:
Using ParaView 5.11.0-RC2, Linux
Launch pvpython via the cmd line
Enter the following within pvpython:
- from paraview.simple impo...ResetSession() command will not do anything when performed in interactive mode via pypython. To duplicate:
Using ParaView 5.11.0-RC2, Linux
Launch pvpython via the cmd line
Enter the following within pvpython:
- from paraview.simple import *
- sphere = Sphere()
- Show()
- Render()
- ResetSession() -- At this point the "Render Window" should be blank or disappear, but the Sphere is still showing.
- box=Box()
- Render() --It shows the box
- Hide(box) -- Sphere is showing again
- Hide(sphere) -- "Render Window" is blank. Good
- Show(sphere) -- "Render Window" shows the Sphere?? It should not even know about the Sphere, because of the ResetSession command
I did try a using both pvbatch and pvpython while using a file as the argument and ResetSession worked fine that way, so this will be a nice to have feature.https://gitlab.kitware.com/paraview/paraview/-/issues/21742Optionally set state using dictionaries in traces and state files2024-03-26T13:44:10-04:00W. Alan ScottOptionally set state using dictionaries in traces and state filesAdd the option to set state using dictionaries in traces, ParaView python state and Catalyst state files. Make this option default off. An example was created by Cory as an original file and one using dictionaries. I will add the two ...Add the option to set state using dictionaries in traces, ParaView python state and Catalyst state files. Make this option default off. An example was created by Cory as an original file and one using dictionaries. I will add the two examples to this bug.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21647Catalyst 2 scripts need to account for data operations internal to readers2024-03-07T20:23:54-05:00Cory Quammencory.quammen@kitware.comCatalyst 2 scripts need to account for data operations internal to readersWhen creating Catalyst scripts from readers that perform certain data operations such as selecting only some blocks to read and applying a displacement field to points, we are missing those data operations in the recorded script. When it...When creating Catalyst scripts from readers that perform certain data operations such as selecting only some blocks to read and applying a displacement field to points, we are missing those data operations in the recorded script. When it is used in a Catalyst run, the data comes in untransformed, leading to incorrect data. We need to capture the data transformations inside the reader in the Catalyst pipeline somehow.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21648Save Screenshot fails in Catalyst trace.2024-03-07T20:23:54-05:00W. Alan ScottSave Screenshot fails in Catalyst trace.My user created a Catalyst State file. It created three renderviews. He did an extract image for each of the renderviews, which worked correctly. Next, he used a trace to get the commands to save screenshot for all three renderviews a...My user created a Catalyst State file. It created three renderviews. He did an extract image for each of the renderviews, which worked correctly. Next, he used a trace to get the commands to save screenshot for all three renderviews at one time, cut and pasted that into the Catalyst State file, and ran that. Catalyst said the .png could not be written.
Error was:
```
[pvbatch.0 ] vtkPNGWriter.cxx:254 ERR| vtkPNGWriter (0x2a144d20): Unable to open file ./catalyst_output/panel_
{timestep:06d} {camera}
.png
[pvbatch.0 ] vtkImageWriter.cxx:481 ERR| vtkPNGWriter (0x2a144d20): Ran out of disk space; deleting file(s) already written
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21650Multiple line widget shows strange behavior2022-11-10T04:55:32-05:00Mathieu Westphal (Kitware)Multiple line widget shows strange behaviorMultiple line widget shows strange behavior
- run ParaView
- Wavelet, Apply
- PlotOverLine, Apply
- Select Wavelet
- PlotOverLine, Apply
- close chart view
- select PlotOverLine1
- press P multiples times
- plot over lines filters are s...Multiple line widget shows strange behavior
- run ParaView
- Wavelet, Apply
- PlotOverLine, Apply
- Select Wavelet
- PlotOverLine, Apply
- close chart view
- select PlotOverLine1
- press P multiples times
- plot over lines filters are selected one after another, looks unexepected
@dcthomp @timothee.chabathttps://gitlab.kitware.com/paraview/paraview/-/issues/21656CI: pv.ShaderReplacements test is flaky2022-11-15T10:20:59-05:00Mathieu Westphal (Kitware)CI: pv.ShaderReplacements test is flakyVery occasionnaly, the pv.ShaderReplacements fails on fedora with:
![a](/uploads/e5c8cef777c4a4ca415ab8a422a1745f/a.png)
It has been excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6016
Note: the pvcs vers...Very occasionnaly, the pv.ShaderReplacements fails on fedora with:
![a](/uploads/e5c8cef777c4a4ca415ab8a422a1745f/a.png)
It has been excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6016
Note: the pvcs version does not seems to failhttps://gitlab.kitware.com/paraview/paraview/-/issues/21657CI: pv.StreamLinesRepresentationColor test is flaky2022-11-15T10:20:55-05:00Mathieu Westphal (Kitware)CI: pv.StreamLinesRepresentationColor test is flakyVery occasionnaly, the pv.StreamLinesRepresentationColor fails on fedora with:
![a](/uploads/c4b326cd6f75cfcbce5e8d00c6d71a77/a.png)
Is has been excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6016Very occasionnaly, the pv.StreamLinesRepresentationColor fails on fedora with:
![a](/uploads/c4b326cd6f75cfcbce5e8d00c6d71a77/a.png)
Is has been excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6016https://gitlab.kitware.com/paraview/paraview/-/issues/21658Labels containing LaTeX rendered with the wrong font2022-11-16T04:38:36-05:00Massimiliano LeoniLabels containing LaTeX rendered with the wrong fontWhen adding LaTeX content to a label [with dollar signs] Paraview will correctly render the LaTeX portion of the label. However, the whole label is then rendered with a font of Paraview's choice, not with the one the user wants.
I attach...When adding LaTeX content to a label [with dollar signs] Paraview will correctly render the LaTeX portion of the label. However, the whole label is then rendered with a font of Paraview's choice, not with the one the user wants.
I attach a video that demonstrates the issue.
[labelBug.mkv](/uploads/fd4a530d358c43e64772d7e8415f97a9/vokoscreen-2022-11-15_18-13-16.mkv)https://gitlab.kitware.com/paraview/paraview/-/issues/21660Unsupported topology sphere2024-03-07T20:23:54-05:00W. Alan ScottUnsupported topology sphereMy user has a dataset that is failing. He wrote this up with the following comments:
The SIERRA/SM code represents “rigid body” blocks using a point/element of type “sphere.” Opening a file with such element types produces this messag...My user has a dataset that is failing. He wrote this up with the following comments:
The SIERRA/SM code represents “rigid body” blocks using a point/element of type “sphere.” Opening a file with such element types produces this message in Paraview 5.11.0-RC1:
```
( 14.973s) [paraview ] vtkIOSSUtilities.cxx:393 ERR| Element of topology 'sphere' with 1 nodes is not supported.
( 14.974s) [paraview ] vtkIOSSReader.cxx:2686 ERR| Error reading entity block (or set) named 'rigidbodyoutputpart' from '/snip/global.e'; skipping. Details: Unsupported topology sphere
```
As a result, the location and fields defined on this part can’t be visualized.
* Linux, master (and 5.11.0-RC2), builtin server.
* Open gears-DoNotRelease.e. Only turn on block ridigbodyoutputpart. Apply
An error is seen in the terminal window. Further, as stated, information tab shows no cells or points.
To see what it should look like, turn on and use the LegacyExodusReader in Tools/ Manage Plugins. You should see 5 points. (If needed, do a Reset and rubber band select of the screen. You will see them. Further, you can see them in the information tab.
I will send data to Cory. Data is gears-DoNotRelease.e. OK to share with anyone at Kitware.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21661Incorrect search path in the Plugin manager2022-11-21T02:52:53-05:00NicolasBIncorrect search path in the Plugin managerFor some reason, the search path for the plugin indicates `bin/plugins` instead of `Plugins` (relatitvely to the ParaView path)
![PluginManager](/uploads/afdafd097b8f00d9d76c20e7824bbe22/PluginManager.png)For some reason, the search path for the plugin indicates `bin/plugins` instead of `Plugins` (relatitvely to the ParaView path)
![PluginManager](/uploads/afdafd097b8f00d9d76c20e7824bbe22/PluginManager.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21662mesa warning while running paraview for openfoam2022-12-14T09:12:59-05:00shir levimesa warning while running paraview for openfoamhey, i get this messseng in ubuntu after writing ParaView how can i fix it?
**QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shir'
Mesa warning: Window 2097160 has no colormap!
Mesa warning: Window 2097163 has no...hey, i get this messseng in ubuntu after writing ParaView how can i fix it?
**QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shir'
Mesa warning: Window 2097160 has no colormap!
Mesa warning: Window 2097163 has no colormap!
Mesa warning: Window 2097170 has no colormap!**
the paraview opens and seem to work fine but reacts really slow.
i have windows 11 (i don't familiar with using ubuntu workspace so I will appreciate any help and simple explanation.https://gitlab.kitware.com/paraview/paraview/-/issues/21663OpenVKL initialization error with ospray on master2023-02-06T09:58:38-05:00Lucas GivordOpenVKL initialization error with ospray on masterWhen launching paraview with `VTK_ENABLE_OSPRAY` set to `ON`, we have this error :
```
[openvkl] INITIALIZATION ERROR: could not open module lib openvkl_module_cpu_device: libopenvkl_module_cpu_device_4.so.1: cannot open shared object f...When launching paraview with `VTK_ENABLE_OSPRAY` set to `ON`, we have this error :
```
[openvkl] INITIALIZATION ERROR: could not open module lib openvkl_module_cpu_device: libopenvkl_module_cpu_device_4.so.1: cannot open shared object file: No such file or directory
[openvkl] WARNING: unrecognized device type 'cpu_16'.
[openvkl] INITIALIZATION ERROR: Could not find device of type: cpu_16. Make sure you have the correct VKL libraries linked.
```
@timothee.chabat @charles.gueunethttps://gitlab.kitware.com/paraview/paraview/-/issues/21665OpenVDB reader on multiple mpi ranks crash2022-11-21T03:14:38-05:00Timothee ChabatOpenVDB reader on multiple mpi ranks crashstep to reproduce :
- `mpiexec -n X pvserver` , X > 1
- connect to the server
- load a `.vdb` file, apply : crash
initially reported here https://discourse.paraview.org/t/egl-pvserver-5-11-0-mpi-and-openvdb/10817
reproduced on master...step to reproduce :
- `mpiexec -n X pvserver` , X > 1
- connect to the server
- load a `.vdb` file, apply : crash
initially reported here https://discourse.paraview.org/t/egl-pvserver-5-11-0-mpi-and-openvdb/10817
reproduced on master (6011921f5be11c68c79d492cc276488d006f259f) and 5.11.0 binaryhttps://gitlab.kitware.com/paraview/paraview/-/issues/21668building Paraview 5.11 on Fedora 372022-12-06T15:57:00-05:00Nabil G.building Paraview 5.11 on Fedora 37dear experts,
while trying to build Paraview 5.11 on Fedora 37, I hit one issue related to mpi4py.
Before trying to patch what needs to be patched, do you know whether there is already some branch which supports Python 3.11 ?
```
Singul...dear experts,
while trying to build Paraview 5.11 on Fedora 37, I hit one issue related to mpi4py.
Before trying to patch what needs to be patched, do you know whether there is already some branch which supports Python 3.11 ?
```
Singularity> lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: Fedora
Description: Fedora release 37 (Thirty Seven)
Release: 37
Codename: ThirtySeven
Singularity> python --version
Python 3.11.0
```
Regardshttps://gitlab.kitware.com/paraview/paraview/-/issues/21669Make `--venv` a pvpython/pvbatch/paraview CLI argument2023-03-06T10:36:25-05:00Utkarsh AyachitMake `--venv` a pvpython/pvbatch/paraview CLI argumentCurrently, python scripts can import [`paraview.web.venv`](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Web/Python/paraview/web/venv.py) to setup module paths etc. to load packages from a virualenv. The current approach req...Currently, python scripts can import [`paraview.web.venv`](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Web/Python/paraview/web/venv.py) to setup module paths etc. to load packages from a virualenv. The current approach requires that `import paraview.web.venv` is done in the Python script that pvpython/pvbatch executes, which makes it impossible for the Python script itself to be a part of the virtual env. For example, I have a nice Python package with Viz pipelines that I pip install in a venv. I simply want to run that package with pvpython as follows:
```sh
pvpython -m my_nice_package
```
It's not possible currently. Hence, I propose we move the venv handling to pvpython/pvbatch itself. Thus, make the following work:
```sh
pvpython --venv /.../venv -m my_nice_package
```
It makes sense to add this cmd-line arg to all executables that support Python including the server executables.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21672EnSight case writer writes full data for all processes2022-11-25T18:27:35-05:00Tomáš KarabelaEnSight case writer writes full data for all processesWhen running in parallel, saving to EnSight Gold writes full geometry from each process, instead of just writing the piece that belongs to that process.
**Steps to reproduce**
- start a parallel `pvserver`, eg:
```
cd ParaView-5.11.0-...When running in parallel, saving to EnSight Gold writes full geometry from each process, instead of just writing the piece that belongs to that process.
**Steps to reproduce**
- start a parallel `pvserver`, eg:
```
cd ParaView-5.11.0-MPI-Linux-Python3.9-x86_64
./mpiexec -np 4 ./pvserver
```
- connect to the server
- create Unstructured Cell Types source
- File > Save Data... > EnSight File, save as `test.case`
This creates four identical sets of EnSight Gold geometry and variable files (with .case files currently missing, see #18242):
```
57K test.0.00000.geo
5,5K test.0.00000_n.DistanceToCenter
5,5K test.0.00000_n.Polynomial
57K test.1.00000.geo
5,5K test.1.00000_n.DistanceToCenter
5,5K test.1.00000_n.Polynomial
57K test.2.00000.geo
5,5K test.2.00000_n.DistanceToCenter
5,5K test.2.00000_n.Polynomial
57K test.3.00000.geo
5,5K test.3.00000_n.DistanceToCenter
5,5K test.3.00000_n.Polynomial
```
Each of these contains the full mesh, which can at the moment be checked by creating the .case file manually and loading it into Paraview:
```
cat <<EOF >test.0.case
FORMAT
type: ensight gold
GEOMETRY
model: test.0.00000.geo
# variable files omitted
EOF
```
When saving the same Unstructured Cell Types source but choosing to save it as Parallel VTK XML Unstructured Grid (.pvtu), the individual .vtu pieces only contain part of the original dataset:
```
567 test.pvtu
28K test/test_0.vtu
28K test/test_1.vtu
28K test/test_2.vtu
28K test/test_3.vtu
```
This can be checked by reading the indiviudal .vtu file into Paraview. It's also apparent when comparing the filesize with a .vtu file written from serial Paraview for the same dataset:
```
105K test-serial.vtu
```
![Screenshot_from_2022-11-25_23-32-58](/uploads/b778292f5fb49e0b5f7d965e50925706/Screenshot_from_2022-11-25_23-32-58.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21673Add option to write time steps to EnSight case writer2022-11-25T17:56:35-05:00Tomáš KarabelaAdd option to write time steps to EnSight case writerSaving to EnSight Gold from Paraview currently only saves the current timestep. It would be useful to add a "Write Time Steps" option to save all timesteps (and possibly another option to only write the geometry once, if it is constant)....Saving to EnSight Gold from Paraview currently only saves the current timestep. It would be useful to add a "Write Time Steps" option to save all timesteps (and possibly another option to only write the geometry once, if it is constant).
The underlying `vtkEnSightWriter` class is capable of writing multiple timesteps with constant or transient geometry. It can be achieved like this:
```
writer->SetInputData(...);
writer->SetTimeStep(0);
writer->Write();
writer->SetInputData(...);
writer->SetTimeStep(1);
writer->Write();
writer->SetInputData(...);
writer->SetTimeStep(2);
writer->Write();
writer->WriteCaseFile(3); // number of steps
```
It does not support doing this via `vtkStreamingDemandDrivenPipeline`.https://gitlab.kitware.com/paraview/paraview/-/issues/21675Python. Function CreationRepresentation -> Registering Error ?2024-03-07T20:23:55-05:00Camille YvinPython. Function CreationRepresentation -> Registering Error ?I have a library that use the function CreateRepresentation from servermanager
In Paraview 5.6.0, the following minimal example works :
```python
from paraview.simple import *
from paraview.servermanager import *
rv = GetRenderView()
...I have a library that use the function CreateRepresentation from servermanager
In Paraview 5.6.0, the following minimal example works :
```python
from paraview.simple import *
from paraview.servermanager import *
rv = GetRenderView()
box = sources.Box(registrationGroup="sources", Center=[2., 2., 2.])
display = CreateRepresentation(box, rv, registrationGroup='representations')
display.SetRepresentationType('Surface')
```
In Paraview 5.10.0, the previous example does not work. I have this message :
```python
File "<string>", line 7, in <module>
File "/home/applis/paraview/5.10.0/lib/python3.9/site-packages/paraview/servermanager.py", line 2332, in CreateRepresentation
setattr(proxy, items[0], items[1])
NameError: name 'items' is not defined
```
So I corrected the lines 2331 and 2332 of servermanager.py from
```
for param in extraArgs.items():
setattr(proxy, items[0], items[1])
```
to
```
for param in extraArgs.items():
setattr(proxy, param[0], param[1])
```
Then when I run the minimal example, I have the following message:
```
Traceback (most recent call last):
File "<string>", line 7, in <module>
File "/home/applis/paraview/5.10.0/lib/python3.9/site-packages/paraview/servermanager.py", line 2332, in CreateRepresentation
setattr(proxy, param[0], param[1])
File "/home/applis/paraview/5.10.0/lib/python3.9/site-packages/paraview/servermanager.py", line 489, in __setattr__
raise AttributeError("Attribute %s does not exist. " % name +
AttributeError: Attribute registrationGroup does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute.
````
The proxy does not seem to have the attribute `registrationGroup`. In the documentation of the function, it seems possible to use this attribute :
```python
def CreateRepresentation(aProxy, view, **extraArgs):
"""Creates a representation for the proxy and adds it to the render
module.
This method can also be used to initialize properties by passing
keyword arguments where the key is the name of the property.In addition
registrationGroup and registrationName (optional) can be specified (as
keyword arguments) to automatically register the proxy with the proxy
manager.
This method tries to create the best possible representation for the given
proxy in the given view. Additionally, the user can specify proxyName
(optional) to create a representation of a particular type."""
global rendering
if not aProxy:
raise RuntimeError ("proxy argument cannot be None.")
if not view:
raise RuntimeError ("view argument cannot be None.")
if "proxyName" in extraArgs:
display = CreateProxy("representations", extraArgs['proxyName'], None)
del extraArgs['proxyName']
else:
display = view.SMProxy.CreateDefaultRepresentation(aProxy.SMProxy, 0)
if display:
display.UnRegister(None)
if not display:
return None
proxy = _getPyProxy(display)
proxy.Input = aProxy
for param in extraArgs.items():
setattr(proxy, param[0], param[1])
proxy.UpdateVTKObjects()
view.Representations.append(proxy)
return proxy
```
When I delete the 'registrationGroup' keyword when I called the function CreateRepresentation in the minimal example, it is okay but I have the following message when I exit Paraview (this message appears only when I called the function CreateRepresentation) :
```
# Loguru caught a signal: SIGABRT
# Stack trace:
# 8 0x152dc69dc073 /home/applis/paraview/5.10.0/bin/../lib/../lib/libvtkIOGeometry-pv5.10.so.1(+0x38073) [0x152dc69dc073]
# 7 0x152deabb6037 __cxa_finalize + 247
# 6 0x152dea774136 std::vector<std::string>::~vector() + 198
# 5 0x152deabfeeec /lib64/libc.so.6(+0x82eec) [0x152deabfeeec]
# 4 0x152deabfd5ec /lib64/libc.so.6(+0x815ec) [0x152deabfd5ec]
# 3 0x152deabf64e7 /lib64/libc.so.6(+0x7a4e7) [0x152deabf64e7]
# 2 0x152deab9ddb5 abort + 295
# 1 0x152deabb337f gsignal + 271
# 0 0x152deabb3400 /lib64/libc.so.6(+0x37400) [0x152deabb3400]
# ( 317.581s) [paraview ] :0 FATL| Signal: SIGABRT
```
I think that when the Representation is created, it is not corectly registered which explains this SIGABRT signal. Is someone have an idea of the way that I can correct it ?
Best regards
Camille5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21684Live Sources (including LiveProgrammableSource) do not update as expected whe...2022-12-02T08:21:26-05:00Mathieu Westphal (Kitware)Live Sources (including LiveProgrammableSource) do not update as expected when loaded from a python stateLive Sources (including Live Programmable Sources) pipelines do not update as expected when loaded from a python state.
They only update when interacting with the view instead.
Steps to reproduce:
- run ParaView
- Live Programmable So...Live Sources (including Live Programmable Sources) pipelines do not update as expected when loaded from a python state.
They only update when interacting with the view instead.
Steps to reproduce:
- run ParaView
- Live Programmable Source
- Script: [dna.py](/uploads/5d756f666d6924dbe703aa4c10689324/dna.py)
- CheckNeedsUpdateScript: `self.SetNeedsUpdate(True)`
- Apply (expecting a moving "dna" line on a 3d view)
- Clip, Apply
- File Save State -> Save to **python** state file
- Reset Session
- Load python state file
- "dna" line only move when the view is interacted with
![Peek_2022-12-02_14-19](/uploads/e6fe2e502ae0281151a9a3c78a432fbe/Peek_2022-12-02_14-19.mp4)
Notes:
- CheckNeedsUpdate is being called correctly, but the `Modified()` is not taken into account for some reason
- Not having a second filter makes the bug disappear
- Showing and then hiding the Live source make the bug disapear
- No bug with .pvsm statefile
May be related:
- https://gitlab.kitware.com/paraview/paraview/-/issues/19553
- https://gitlab.kitware.com/paraview/paraview/-/issues/21372https://gitlab.kitware.com/paraview/paraview/-/issues/21685Doxygen Documentation problem online2022-12-05T08:10:40-05:00NicolasBDoxygen Documentation problem onlineOn the online Doxygen documentation, the [plugin Howto](https://kitware.github.io/paraview-docs/nightly/cxx/PluginHowto.html) formatting has a problem with a codeblock on section `Getting the Location of a Dynamically-Loaded Plugin`, eve...On the online Doxygen documentation, the [plugin Howto](https://kitware.github.io/paraview-docs/nightly/cxx/PluginHowto.html) formatting has a problem with a codeblock on section `Getting the Location of a Dynamically-Loaded Plugin`, even on nightly.
Online page:
![image](/uploads/dd6b6aa0261dc52a999ebb71bb337108/image.png)
Local page:
![image](/uploads/3507adb764dbeda9eb084a63b0339256/image.png)
But locally, when I compile the doc with `ninja ParaViewDoxygenDoc`, the page is correctly rendered. The file (`Utilities/Doxygen/pages/PluginHowto.md`) has not be changed for a month now.https://gitlab.kitware.com/paraview/paraview/-/issues/21686Create a simple testing framework for "hidden" interface (eg: Open File Dialog)2022-12-02T10:10:12-05:00Mathieu Westphal (Kitware)Create a simple testing framework for "hidden" interface (eg: Open File Dialog)ParaView has many dialog that are hidden to the XML testing framework.
- Open File Dialog
- Warning popup ( `promptUser`)
- Crash recovery
This is very practical for generic testing purpose to have these shortcuts but it means than the...ParaView has many dialog that are hidden to the XML testing framework.
- Open File Dialog
- Warning popup ( `promptUser`)
- Crash recovery
This is very practical for generic testing purpose to have these shortcuts but it means than these actual behavior are not tested.
The fact that the open file dialog is not tested is critical, as it gets more and more complex and multiple issues have only been detected during RC phase because of that.
Let's figure out a simple way to disable these shortcuts when needed so that ParaView testing can be ever better !https://gitlab.kitware.com/paraview/paraview/-/issues/21689[Feature] Support .png as a 2D Glyphs2022-12-05T04:15:04-05:00Mathieu Westphal (Kitware)[Feature] Support .png as a 2D GlyphsParaView can easily show many type of 2D Glyphs, using different methods, but there is no way to show a .png image as a glyphs in ParaView.
Ideally, this feature should:
- Let the user interactively select a .png image to show on each ...ParaView can easily show many type of 2D Glyphs, using different methods, but there is no way to show a .png image as a glyphs in ParaView.
Ideally, this feature should:
- Let the user interactively select a .png image to show on each point of a geeometry
- Optionnaly, the png should be shown as a "Follower", not a 3D plane that we can see behind/side
A few possible implementations:
- 3D Glyphs Representations -> 2D Glyphs -> Texture properties : 2D glyphs could generate T coords unto a texture could be applied to
- 3D Glyphs representations -> Pipeline Connection -> select a geometry with a texture or without MapScalars
- PointGaussian with a special mode that support texture mappinghttps://gitlab.kitware.com/paraview/paraview/-/issues/21691Plugin EULA prompts are not skipped when using CTest2022-12-06T05:27:13-05:00NicolasBPlugin EULA prompts are not skipped when using CTestWhen using the `LOAD_PLUGINS` argument of the `paraview_add_client_tests()` method, in order to test a plugin with a provided EULA, CTest is stuck at the EULA agreement popup.
This was found during [this discussion](https://gitlab.kitw...When using the `LOAD_PLUGINS` argument of the `paraview_add_client_tests()` method, in order to test a plugin with a provided EULA, CTest is stuck at the EULA agreement popup.
This was found during [this discussion](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6005#note_1285306).https://gitlab.kitware.com/paraview/paraview/-/issues/21692color blocks in a multiblock by different variables2023-12-12T12:20:07-05:00Boonthanome Nouanesengsycolor blocks in a multiblock by different variablesWe would like the ability to color blocks in the same multiblock by different variables. For example, let's say there's a multiblock with two blocks. We would like to be able to color the first block by density, and then the second block...We would like the ability to color blocks in the same multiblock by different variables. For example, let's say there's a multiblock with two blocks. We would like to be able to color the first block by density, and then the second block by velocity. This is achievable with the `Extract Blocks` filter, but we would like an easier way to do this. Maybe in the Multi-block Inspector.
It is important to be able to turn on/off visibility of certain blocks while they are being colored by different variables. We can turn on/off visibility with the Multi-block inspector, but just keep in mind we need to keep that functionality.
@patchett2002 @cory.quammen5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21696Crash using Explicit Structured Grid Slice and Cells Extractor filter (from E...2023-06-15T10:45:39-04:00Francois MazenCrash using Explicit Structured Grid Slice and Cells Extractor filter (from Explicit Structured Grid ParaView Plugin)Using Explicit Structured Grid Slice and Cells Extractor filter triggers crashes ParaView (master branch).
Steps to reproduce:
- Load the ExplicitStructuredGrid plugin
- Create Explicit Structured Grid Generator Source, Apply
- Creat...Using Explicit Structured Grid Slice and Cells Extractor filter triggers crashes ParaView (master branch).
Steps to reproduce:
- Load the ExplicitStructuredGrid plugin
- Create Explicit Structured Grid Generator Source, Apply
- Create Explicit Structured Grid Slice and Cells Extractor, Apply
- Crash!
Call stack (relevant part only):
```
6 0x7fc01708a63d vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 199
5 0x7fc01708ca36 vtkExplicitStructuredGridAlgorithm::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 92
4 0x7fbfd06571f0 vtkExplicitStructuredGridPythonExtractor::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 488
3 0x7fc0164a1db7 vtkExplicitStructuredGrid::DeepCopy(vtkDataObject*) + 237
2 0x7fc0163bfbd1 vtkCellArray::DeepCopy(vtkCellArray*) + 129
1 0x7fc01633cdee /home/francois/dev/paraview/build_paraview/bin/../lib/libvtkCommonDataModel-pv5.11.so.1(+0x13cdee) [0x7fc01633cdee]
0 0x7fc01e7a2a00 /usr/lib/libc.so.6(+0x38a00) [0x7fc01e7a2a00]
( 132.129s) [paraview ] :0 FATL| Signal: SIGSEGV
```
Reproduced with master branch. Do not crash with official release 5.11.0, 5.10.1 nor 5.9.1.https://gitlab.kitware.com/paraview/paraview/-/issues/21697Loading identical .py state and .pvsm states give inconsistent results2022-12-14T12:59:12-05:00Alankar DuttaLoading identical .py state and .pvsm states give inconsistent resultsI’m having a ParaView state saved as .pvsm gives correct position of colorbars and other elements. However, when the same state is stored and loaded as a .py script the colorbars get misplaced. What is the issue? (version: ParaView 5.10....I’m having a ParaView state saved as .pvsm gives correct position of colorbars and other elements. However, when the same state is stored and loaded as a .py script the colorbars get misplaced. What is the issue? (version: ParaView 5.10.1)
I’m putting in the relevant images.
Loading .pvsm state:
![image](/uploads/f697316d154c68a0ded8584968661408/image.png)
Misplaced colorbars on loading .py state produced at the same time in the GUI:
![image](/uploads/3ce703f37ba4df837afdffce2eb48bab/image.png)
The placement of the colorbars become consistent when the .py script is loaded and generated in ParaView 5.11.0 version compared to the inconsistencies in 5.10.1 version. However, the font sizes are still in-consistent and don’t give identical results. The same happens if I change the orientation axes position (not shown in these images), the python saved state keeps the orientation axes at the default lower left position but the .pvsm file works correctly and puts the orientation axes at the changed location. As a result of the font size inconsistency, parts of the text get cut off at the edges. Also, most likely because of this, same issues happen for Catalyst python states as well. Can someone more experienced in the community help me fix this issue?
Here is the screenshot of what happens on loading the .py state script in ParaView 5.11.0:
![image](/uploads/332b62d3e3627864ecc00e6785e68159/image.png)
Related: https://discourse.paraview.org/t/loading-identical-py-state-and-pvsm-states-give-inconsistent-results/10939https://gitlab.kitware.com/paraview/paraview/-/issues/21699ImplicitPlaneWidget has different opacity with distributed remote rendering t...2022-12-12T03:42:36-05:00Gonzalo SáezImplicitPlaneWidget has different opacity with distributed remote rendering than with local renderingSee the attached images (first distributed remote rendering, second local serial rendering). To reproduce
1. `mpirun -np 4 pvserver`
2. `paraview`
3. Connect to the server.
4. Reduce the remote rendering threshold to zero in ParaView's ...See the attached images (first distributed remote rendering, second local serial rendering). To reproduce
1. `mpirun -np 4 pvserver`
2. `paraview`
3. Connect to the server.
4. Reduce the remote rendering threshold to zero in ParaView's `Render View` settings.
5. Create `UnstructuredCellTypes` source.
6. Create a `Slice` filter.
7. Interact with the plane.
At step 7, it's possible to see a difference in the opacity of the widget between distributed remote rendering and local rendering). The same happens with the `DisplaySizedImplicitPlaneWidget` in case it's easier to test with newer ParaView versions. This issue makes it difficult to interact with the plane widget since it hides much of the screen space.
Is there an easy fix to this issue? Thank you
![image_1](/uploads/b0a5022e82c5178bcbdd500a0296b4d8/image_1.png)
![image_2](/uploads/2c33047903037b0e98fdc29a8dd23c27/image_2.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21700Compilation errors with VisRTX2022-12-19T11:45:39-05:00LucasGasparinoBSClucas.gasparino@bsc.esCompilation errors with VisRTX# VisRTX build fail
- branch: master;
## Description
Tried to build the latest master with VisRTX ray-tracing support, but got the following error:
- VisRTXBackend.cxx:6:10: fatal error: VisRTX.h: No such file or directory
Now, I do...# VisRTX build fail
- branch: master;
## Description
Tried to build the latest master with VisRTX ray-tracing support, but got the following error:
- VisRTXBackend.cxx:6:10: fatal error: VisRTX.h: No such file or directory
Now, I do have the latest VisRTX installed (using Anari and OptiX7) and properly pointed at in the environment. And it really does not contain a VisRTX.h header, only the following includes:
- anari_library_visrtx_export.h;
- visrtx.h;
The same applies to the libs: all realted to Anari. My guess is that the change to Anari is not yet reflected in what Paraview expects, or am I missing something? Could you point me to a version of VisRTX that would work in the meantime?
Thanks!https://gitlab.kitware.com/paraview/paraview/-/issues/21703HyperTreeGridToDualGrid BUG2023-01-05T10:05:52-05:00Carlos del ValleHyperTreeGridToDualGrid BUGI have been having problems with Hyper Tree Grids. The data comes from a simulation that uses AMR with Octrees.
- When I use the filter Hyper Tree Grid To Dual Grid, it fails when I change the timestep. The fields appear with a ? mark ...I have been having problems with Hyper Tree Grids. The data comes from a simulation that uses AMR with Octrees.
- When I use the filter Hyper Tree Grid To Dual Grid, it fails when I change the timestep. The fields appear with a ? mark and things that I made based on the dual grid, like contours, disappear.
- When I use the filter Hyper Tree Grid To UnstructuredGrid it works well on every time step but when I use Cell Data to Point Data to then create a contour nothing gets rendered as if the contour was never created.
I found some reports of this bug, apparently, it happens when there's only one tree. Here are some reports of this weird behavior:
- https://discourse.paraview.org/t/hypertreegridtodualgrid-bug/9287
- https://discourse.paraview.org/t/problem-creating-contours-from-hyper-tree-grid-bug/10959
- https://gitlab.kitware.com/paraview/paraview/-/issues/21333
- https://gitlab.kitware.com/paraview/paraview/-/issues/21108https://gitlab.kitware.com/paraview/paraview/-/issues/21704[Enhancement Request] Persistent Open Dialog "Favorites" for Client-server Co...2023-01-03T12:08:13-05:00Joel A. Kulesza[Enhancement Request] Persistent Open Dialog "Favorites" for Client-server ConnectionsIn the attached, I connect Client-server to an institutional HPC resource, File -> Open, navigate to a preferred directory, and then add it to the upper-left box.
When I disconnect and reconnect to the same queue allocation, my entry ...In the attached, I connect Client-server to an institutional HPC resource, File -> Open, navigate to a preferred directory, and then add it to the upper-left box.
When I disconnect and reconnect to the same queue allocation, my entry has disappeared.
From discussion in this issue, the non-persistence appears tied to different port numbers used to make the client-server connection. It would be good if these favorites were preserved on the client side such that connection details (other than perhaps destination machine) did not matter.
![Screen_Shot_2022-12-15_at_07.39.17](/uploads/3825868ead246ee31f391277948e2136/Screen_Shot_2022-12-15_at_07.39.17.png)
FYI: @ethan.stam @patchett2002
Edit: this is observed with ParaView 5.10.1 on macOS 11.7.https://gitlab.kitware.com/paraview/paraview/-/issues/21705Can't save animation with screen width greater than 2100 pixels2023-01-10T22:28:59-05:00Danya AlrawiCan't save animation with screen width greater than 2100 pixelsLoad example visualization "Exodus II file with timesteps" in ParaView then save animation, file type set to VFW AVI. For image resolution select preset 4k UHD. With quality set to worst and frame rate set to 1 the export fails and saves...Load example visualization "Exodus II file with timesteps" in ParaView then save animation, file type set to VFW AVI. For image resolution select preset 4k UHD. With quality set to worst and frame rate set to 1 the export fails and saves an empty file. This is using compressor four CC I420.https://gitlab.kitware.com/paraview/paraview/-/issues/21706Macros are loaded when using --dr argument2024-01-04T08:32:19-05:00NicolasBMacros are loaded when using --dr argumentMacros are loaded when using `--dr` argument, even though we should have a clean environment with no settings set.
## Usages
It causes problems and prevents the `pv.LoadTranslationsTestingPlugin` test from running on Macos CIs: see !60...Macros are loaded when using `--dr` argument, even though we should have a clean environment with no settings set.
## Usages
It causes problems and prevents the `pv.LoadTranslationsTestingPlugin` test from running on Macos CIs: see !6005
[This test](https://open.cdash.org/test/890369785) failed due to macros that should not be present.https://gitlab.kitware.com/paraview/paraview/-/issues/21707ExtractBagPlot segfault with incorectly formated data2022-12-16T08:27:35-05:00Mathieu Westphal (Kitware)ExtractBagPlot segfault with incorectly formated dataExtractBagPlot is unstable and should check inputs before processing is it can segfault if the data contains a String array.
Steps to reproduce:
- run ParaView
- Tools -> ManagePlugins -> BagPlotAndViewsFilters
- File -> Open -> Sine...ExtractBagPlot is unstable and should check inputs before processing is it can segfault if the data contains a String array.
Steps to reproduce:
- run ParaView
- Tools -> ManagePlugins -> BagPlotAndViewsFilters
- File -> Open -> SineWaves.csv, Apply
- TransposeTable -> Apply
- ExtractBagPlot -> Apply
- Segfault
Disabling TransposeTable "Add a column wiuth name" work around the issuehttps://gitlab.kitware.com/paraview/paraview/-/issues/21710HyperTreeGrid HTG Writer produces broken htg in appended mode after calculator2023-03-24T04:30:51-04:00maximilian-techHyperTreeGrid HTG Writer produces broken htg in appended mode after calculatorThe HyperTreeGrid writer produces broken files with more than one array.
The files are fixable but the HyperTreeGrid reader has another issue when reading files of HTG version 2.0 files (see this issue paraview/paraview#21711).
The ori...The HyperTreeGrid writer produces broken files with more than one array.
The files are fixable but the HyperTreeGrid reader has another issue when reading files of HTG version 2.0 files (see this issue paraview/paraview#21711).
The original file as well as the modified file are appended.
* [randomHTG-pv511_unmodified.htg](/uploads/9b545319fc63d006f3f54bf6558c5b54/randomHTG-pv511_unmodified.htg)
* [randomHTG-pv511_modified.htg](/uploads/08dd2e9d7acf0eb9738b5549aa73274f/randomHTG-pv511_modified.htg)
Steps to reproduce a broken HTG (using Paraview v5.11.0)
* Create random HyperTreeGrid Source (`Source -> Alphabetical -> HyperTreeGrid (Random)`)
* Add a new vector array using the `Calculator` and formula `Depth*iHat`)
* Save the calculator with `CTRL+S` to a `*.htg` file in appended mode without compression
* Try open this file (it will fail)
Inspecting the file with VIM reveals three errors
* The header of the file is partially overwritten (` RangeMax="5"02"yperTreeGrid" version="2.0" ...`)
* The array `Depth` has empty offset
* The array `Result` has the wrong offset (in fact the offset of `Depth`)
This errors are fixable by hand
* Reconstruct the file header with `<VTKFile type="HyperTreeGrid" version="2.0" byte_order="LittleEndian" header_type="UInt32">`
* Move the offset of the `Result` array to the `Depth` array
* Calculate `Result` offset by hand ( `4 Byte (HeaderSize) + 65354*8 Byte (depth array size) + 4166 Byte (depth array offset) = 527002 Byte` )
This file can be opened by Paraview without problems.https://gitlab.kitware.com/paraview/paraview/-/issues/21711HyperTreeGrid HTG Reader corrupt read htg file version 2.02023-03-24T04:31:29-04:00maximilian-techHyperTreeGrid HTG Reader corrupt read htg file version 2.0The HyperTreeGrid HTG Reader cannot correctly read htg file version 2.0.
It shows some random behavior as the reader seems to read from corrupted memory and not from the file. Some parts are valid while others changed randomly.
Steps t...The HyperTreeGrid HTG Reader cannot correctly read htg file version 2.0.
It shows some random behavior as the reader seems to read from corrupted memory and not from the file. Some parts are valid while others changed randomly.
Steps to reproduce
* Consider the modified file `randomHTG-pv511_modified.htg` from issue paraview/paraview#21710
* Read this file and look at the `Result` array.
* ![Screenshot_from_2022-12-19_11-16-57](/uploads/94d869073aef7e0bfb716d8d1681a462/Screenshot_from_2022-12-19_11-16-57.png)
* Reload the file (`right click on the file -> Reload Files`)
* Different result
* ![Screenshot_from_2022-12-19_11-17-45](/uploads/c74e560ab6212c6fd2073e5e2f4c482d/Screenshot_from_2022-12-19_11-17-45.png)
I have also observed this behaviour with my own HTG exporter. The appended blob can be read correctly with htg file version 1.0, however shows this corrupted behavior then switching to file version 2.0.https://gitlab.kitware.com/paraview/paraview/-/issues/21713Spreadsheet intermixes and confuses one time header data and global data on t...2022-12-20T13:30:13-05:00W. Alan ScottSpreadsheet intermixes and confuses one time header data and global data on timestepsThe spreadsheet intermixes one time header data and global data on timesteps, and makes it confusing which is which. An example is to open can.exo, and look at the data with a spreadsheet. Exodus data has one time information at the to...The spreadsheet intermixes one time header data and global data on timesteps, and makes it confusing which is which. An example is to open can.exo, and look at the data with a spreadsheet. Exodus data has one time information at the top of the file An example is QA records or info records. This information numerous names for each sub block, I will call it header information. Next is data that is attached to each timestep, sometimes called global data. An example is timestep time, or timestep count, or KE. These need to be labeled and sorted in the Spreadsheet.
Open can.exo. Spreadsheet. Attribute Field Data. These column need to be in a clear, logical order.
Please run this idea by Cory. I wonder if we could add hdr_ to header data, and glob_ to the global data? That way the spreadsheet would sort itself correctly.
Here is an image of what we now have with can.exo.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21714ParaView crashes with a specific .vtu file2022-12-21T03:45:14-05:00chichi72ParaView crashes with a specific .vtu fileHello,
I am trying to load these [vtk files](https://we.tl/t-fJLRLotSWU) into paraview.
This is the [topic](https://discourse.paraview.org/t/paraview-crashing-on-windows-11-while-opening-large-file/11020/4) I have opened in paraview sup...Hello,
I am trying to load these [vtk files](https://we.tl/t-fJLRLotSWU) into paraview.
This is the [topic](https://discourse.paraview.org/t/paraview-crashing-on-windows-11-while-opening-large-file/11020/4) I have opened in paraview support with some details, if it's any help.
Thanks!
Reproduce with ParaView master, on Windows and Linux.https://gitlab.kitware.com/paraview/paraview/-/issues/21716ParaView HPC Scalability Guide2022-12-22T03:06:24-05:00W. Alan ScottParaView HPC Scalability GuidePlease add the HPC Scalability Guide that was created by Mathieu to the ParaView Reference manual. We don't want to lose this really spectacular document.
Document is here: https://www.kitware.com/paraview-hpc-scalability-guide/
My e...Please add the HPC Scalability Guide that was created by Mathieu to the ParaView Reference manual. We don't want to lose this really spectacular document.
Document is here: https://www.kitware.com/paraview-hpc-scalability-guide/
My edit notes, from a year ago, for whatever it is worth, were:
Just because I love bullets, let me do this as bullets.
* I really like this document. We have needed it for a very long time. Well done.
* Taking the title literally, I would strongly argue that you increase the width of this topic. In my experience, performance issues (i.e., can something run well or not) are – in order – 1) Do you have enough memory? How can you tell? (Memory inspector, see below). How do you get your data visualized? (More nodes, fewer variables, smaller dataset. Time count doesn’t matter. Structured over unstructured.). If it won’t fit in memory, cpu performance doesn’t matter. 2) Disk read speed. You covered this. Basically, faster disk, more nodes reading it. I will say that there is one subtopic here – Is the reader doing dumb stuff? For instance, the Exodus reader is HORRIBLE on an uncached disk. It reads a byte at a time, each of which brings in a disk sector. 3) Rendering speeds. Note that speeds don’t need to be anything near what they are for games. 8 or so FPS is plenty. Stefan, a user that visualizes fire, puts up with a frame every 5 or 10 seconds. (He also does insane volume rendering of hero size datasets.). 4) Algorithm speeds. You covered this very well.
* What IS big data and what is huge? Memory Inspector (never go over 70%. Number of variables (over a hundred is huge. Only load what you need.). Number of blocks (over 100 is huge. Only load what you need). Number of sets (over 100 is huge. Only turn on what you need). Number of files (Over 10,000 is huge, I have seen millions. DON’T turn on the advanced information on the Open dialog.). Number of timesteps (100’s are big, 1000’s are huge).
* You did say this, but for someone that doesn’t know what distributed data is, elaborate. This is one of the biggest issues I have – users deciding 1 node (16 or 32 cores) isn’t enough to read one file, so they bring in 8 nodes.
* There is a fairly large disagreement within the community with regards to = software rendering vs GPUs. I believe LLNL has dedicated clusters with GPUs for vis servers. LANL has dedicated clusters, I’m not sure about GPUs. Sandia goes a different direction that has been extremely successful. ParaView is so incredibly good with reducing rendering load, and so incredibly good with distributed server rendering that we just ask for a small slice of the big clusters. Think of it this way. If I have 5 million dollars for Viz, do I want a dedicated small cluster (with GPUs), or a bigger primary cluster with more nodes and memory? Don’t forget this gives us extreme flexibility to expand or contract our node count on a platform with a low cost. All processing at Sandia backend pvserver is osmesa. We get framerates around 50/second, plenty good. Having said all this, once we did implement the back end on a GPU cluster (Doom), and for worst cases, framerates did double.
* Your writeup is somewhat incorrect and confusing when a user has a remote distributed pvserver(s). I get caught by this all the time in testing. If you are running a small dataset (can.exo, disk_out_ref.exo), ParaView will actually render not the data, but the surface on the client. If it’s bigger, it will render the surface on the server. The “switch” is of course Settings/ Rendering/ Remote Rendering Threshold.
* If a user has a slow, or long connection (such as if I am in Albuquerque, and I am connected to a cluster in Los Alamos), if needed, I can decrease the pixels moved back and forth. Edit/ Settings/ Advanced/ Rendering/ Image Reduction Factor. We haven’t heeded to tweak this in years.
* For advanced users, there are three ways I try to figure out “hot spots”. Build debug, and then run ParaView in a debugger. Stop a lot. If you start seeing the same spot over and over, that’s the problem. Alternatively, profilers. Doing this remote server is a challenge. Last, the good old, ancient print statements in the code. This paragraph is probably too much information. Better may be “contact Kitware, we know stuff”.
* The progress bar is useless. I think we really should get rid of it, and just add a MacOS type of spinning wheel of death. The reasons are fairly complex. When you really need a progress bar is remote distributed server. We were passing information back to rank 0 so often 10 years ago that the progress bar was significantly slowing ParaView down. Now, we just use rank zero, and assume that’s good enough, which it isn’t. Many filters go from 0 to 100% done with nothing in between. Many pipelines just flash back and forth like they are crazy ants running around. Again, the progress bar is useless.
* You mentioned the Timer Log (Excellent), but forgot to mention Utkarsh’s more granular and selectable Log Viewer. The Log Viewer is an even more useful tool, especially if you figure out how to use it and start imbedding it in the code with better granularity.
* A really good way to check rendering speeds is with a dataset that is known and everyone has – i.e., Source/ Fast Uniform Grid, or Sphere, or Unstructured Cell Types. Make LOTS of cells, spin. This is a way to push a huge number of vertexes, or pixels, down the pipe.
* There are minor grammatical mistakes in the document. The meaning is perfect, but it is slightly distracting. If you give me a text copy, I can go through it and edit appropriately.
That’s about everything I found. It really is a good job, don’t take my thoughts as too negative. I just see performance issues frequently from a different viewpoint.
Here is the "link" that Ben gave me to this original email: `Message-Id: C87AD652-5912-4DA5-B1E4-8CD9CF603E35@sandia.gov`5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21717Create a "how to create a filter" procedure2024-03-07T20:23:55-05:00W. Alan ScottCreate a "how to create a filter" procedureCory created a Perlin Noise filter a few years ago. When I asked how he figured it out and the steps he used, he gave me the following steps. I think these should be added to the ParaView Reference Manual, along with other tips. At le...Cory created a Perlin Noise filter a few years ago. When I asked how he figured it out and the steps he used, he gave me the following steps. I think these should be added to the ParaView Reference Manual, along with other tips. At least this is a good start! From Cory:
Here's roughly how I figured it out:
* check that there is a VTK class named vtkPerlinNoise. There is! Hmm, but it's not a filter.
* check if there is a VTK class that produces Perline noise on a grid. Nope, nothing else named Perlin.
* look at vtkPerlinNoise again. Hmm, it's a vtkImplicitFunction subclass. That means it is used in a context where points in a dataset are passed to it, and something is done with the resulting value. What other filters exposed in ParaView do something similar? The Clip filter is one. So now I have a model of how to do this.
* What is a filter that takes a vtkImplicitFunction and evaluates it at all points in a VTK dataset? Anything with the name Implicit in it? Indeed! vtkSampleImplicitFunctionFilter.
* Start creating the XML needed for vtkSampleImplicitFunctionFilter. There are not many options in this class, so that is pretty simple.
* Last part - how do I create a vtkPerlinNoise object and get it to the vtkSampleImplicitFunctionFilter? Look to the "Clip" filter. It has a ProxyProperty called ClipFunction. A ProxyProperty is a property that takes another ParaView proxy - in this case, we want it to take a proxy object representing a vtkPerlinNoise object. Using the example of "Clip", we can tell the Clip proxy that its ClipFunction property can be one of the proxies in a list of proxies representing implicit functions. Now I know I have to do the same for the vtkSampleImplicitFunctionFilter proxy, but I need only provide one implicit function, the Perlin noise function.
* Before I can tell the vtkSampleImplicitFunctionFilter proxy about the Perlin noise implicit function, I have to write some XML to describe it. I look for the "Cylinder" implicit function to use as a model and find it in misc_utilities.xml. Here I see that I need to describe properties of the implicit function. In the case of Perlin noise, there are just a couple to expose. Plus, I need to make sure the XML for the Perlin noise function is in the right ProxyGroup - in this case that group is "implicit_functions". It could be anything, really - it just has to match what I put in the XML for the vtkSampleImplicitFunctionFilter proxy.
* Now I am ready to define the property in the vtkSampleImplicitFunctionFilter proxy that is the Perlin noise source. I once again use the "Clip" filter as my model and see that I need to list the Perlin noise proxy in the group of possible proxies for this property.
* Yadda yadda yadda, I've got an XML filter.
So you see, it wasn't that easy. At least, it wouldn't be very easy to write up. On the other hand, including it as an example on the plugins HOWTO isn't far-fetched. People who learn by pattern matching (like me) will be able to use it as a basis for some XML plugins.
@cory.quammen5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21718Doxygen doc "latest" points to 5.10 and includes some pages from nightly2024-03-28T13:28:56-04:00Nicolas VuailleDoxygen doc "latest" points to 5.10 and includes some pages from nightlyIn the [doxygen page](https://kitware.github.io/paraview-docs/latest/cxx/index.html), the "latest" release is configured on 5.10, should be 5.11.
Also in "latest" version the "Navigation" part contains a broken link to the new "Localiza...In the [doxygen page](https://kitware.github.io/paraview-docs/latest/cxx/index.html), the "latest" release is configured on 5.10, should be 5.11.
Also in "latest" version the "Navigation" part contains a broken link to the new "Localization HowTo" page, that exists only on "nightly" version.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21720OSPRay : can't render in Surface LIC2022-12-21T10:23:01-05:00Lucas GivordOSPRay : can't render in Surface LIC`Surface LIC` + `Enable Raytracing` do a `Surface` rendering :
![image](/uploads/9b17a4a8039807d77ecf7fb0b0134c93/image.png)
It looks like `Surface LIC` is a custom vtk rendering it is expected to doesn't have it with OSPRay. So when w...`Surface LIC` + `Enable Raytracing` do a `Surface` rendering :
![image](/uploads/9b17a4a8039807d77ecf7fb0b0134c93/image.png)
It looks like `Surface LIC` is a custom vtk rendering it is expected to doesn't have it with OSPRay. So when we enable raytracing I think we shouldn't have the possibility to set the representation to `Surface LIC` in the GUI I guess.
Step to reproduce:
- create a wavelet
- enable raytracing
- set the representation to `Surface LIC`https://gitlab.kitware.com/paraview/paraview/-/issues/21721Spreadsheet crashes with large data2024-03-08T05:05:10-05:00W. Alan ScottSpreadsheet crashes with large dataSpreadsheet is crashing with large data. This is impacting debugging, thus marking as a showstopper. There may be more than one issue, so if you want me to try master, just let me know. Here is how to replicate.
* I believe my build i...Spreadsheet is crashing with large data. This is impacting debugging, thus marking as a showstopper. There may be more than one issue, so if you want me to try master, just let me know. Here is how to replicate.
* I believe my build is 5.11.0. Linux, Builtin server.
* Sources/ Fast Uniform Grid. Advanced. Turn off Swirl and Distance Squared. You will still have X scalar. Apply.
* Change extent to -1000 to 100, -1000 to 100, -1000 to 100. Apply.
* Split screen vertical. Spreadsheet.
Client side dies (I can see this when I am running remote server).
My guess is we are overflowing some 32 bit int.
Crashes are bad, and this is needed for debugging.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21722Catalyst: two data pipes with two different scripts fails in coprocessing.py2024-03-27T10:37:25-04:00Jeff MauldinCatalyst: two data pipes with two different scripts fails in coprocessing.pyWhen using Catalyst, users will sometimes want to create different datasets to be sent to different catalyst python scripts. For example, in SPARC users might send surface/wall data to one script and volume/airflow data to a different sc...When using Catalyst, users will sometimes want to create different datasets to be sent to different catalyst python scripts. For example, in SPARC users might send surface/wall data to one script and volume/airflow data to a different script.
In ParaView 5.10 and 5.11.0 this capability fails. It worked in 5.9. The problem is in coprocessort.py. I am attaching my altered coprocessor.py which works. You can diff with the 5.11.0 Wrapping/Python/paraview/coprocessing.py to see the changes I had to make to get it to work. I don't insist on exactly these changes, but our ioss catalyst test suite (that Ben Boeckle can run on SNL HPCs like vortex and eclipse) will need to pass the related two pipe/two script tests.[coprocessing.py](/uploads/c9acb4266c3c5bf9d08ccf1edc931abc/coprocessing.py)
I also undid a change which disallowed multiple data pipes to have the same name. In our sierra catalyst implementation we have been using the same name ("input") for all incoming data pipes and it has worked fine. I don't absolutely have to have the capability to give multiple pipes the same name, but it would be nice to be warned formally about the change.5.11.1 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21723Increasing memory usage when reading temporal data2024-01-08T05:29:49-05:00Thomas GallandIncreasing memory usage when reading temporal dataParaView memory consumption seems increasing when reading temporal data.
The following chart shows the consumption of the physical memory (RSS) with the `Xdmf` reader on a ≃ 20GB dataset. \
Each red line correspond to a new timestep req...ParaView memory consumption seems increasing when reading temporal data.
The following chart shows the consumption of the physical memory (RSS) with the `Xdmf` reader on a ≃ 20GB dataset. \
Each red line correspond to a new timestep request:
![image](/uploads/f128826c5190c44ae1f00c79e95505f8/image.png)
Same trends are observed with other readers. For example when opening `.vtm` files :
![image](/uploads/edef16aad68220150060ed3a1b479a33/image.png)
Several things to note at this point :
- In each case, things seems to stabilize over time.
- Going back to a previously read timestep or reading a new one has no significative impact on the results.
- Changing the way to display the output from `Render View` to `SpreadSheet View` as no significative impact as well.
- Using pvpython scripting **without rendering involved** shows the same results.
One of the possible track to follow was to ensure that the animation cache was used correctly. \
When opening a smaller dataset (`Xdmf` ≃ 3GB) and setting the animation cache on and off, we observe the following results:
![image](/uploads/51e4ca4516e650dcb2305efa545bc479/image.png)
![image](/uploads/10867d56326ec5168dcb6a0dd8233ada/image.png)
We can see that:
- With the animation cache, the memory consumption increases on each timestep. Then by looping the animation, memory consumption doesn't change anymore.
- Without the animation cache, I have the same memory consumption, without the plateau once looping.
The first situation seems coherent, as caching data increases naturally the memory usage; then no more cost when eveything is cached. \
But without cache, we can expect no increase of the memory consumption between each timestep. It looks like the data is cached anyway, but not used during the loop.
When trying to reproduce it with VTK alone (with the same input data, `Xdmf` ≃ 3GB) we can observe similar trend as well :
![image](/uploads/f350f5b1a228d62ef19a94c072da75dc/image.png)
This may invalidate the fact that the animation cache is the problem.
Now when using no rendering pipeline at all :
![image](/uploads/7ad8ab61dc1eb73155abc59536b44135/image.png)
Among all the measures I made, this is the only case where memory consumption seems not growing.Thomas GallandThomas Gallandhttps://gitlab.kitware.com/paraview/paraview/-/issues/21728Contour filter is failing on CTH AMR2024-03-07T20:23:55-05:00W. Alan ScottContour filter is failing on CTH AMRThe Contour filter is failing on CTH AMR data. This is critical to get fixed. Here is how to replicate it.
* 5.11.0, builtin server, Linux.
* Load the four file spcta_a.[0-3] dataset. I believe it's called "Dave's Small CTH" or someth...The Contour filter is failing on CTH AMR data. This is critical to get fixed. Here is how to replicate it.
* 5.11.0, builtin server, Linux.
* Load the four file spcta_a.[0-3] dataset. I believe it's called "Dave's Small CTH" or something like that. Turn all variables on. Apply.
* Cell Data to Point Data filter. Apply. (Needed because Contour only works on point data.)
* Contour. Temperature (ev). Reset using current data values. Apply.
Contour fails, and writes out the following:
ERROR: In vtkAlgorithm.cxx, line 639
vtkPVContourFilter (0x27dc5080): Attempt to get point or cell data from a data object
There is a hack that works. Add a clip filter between the Cell Data to Point Data filter. This really should be fixed for 5.12.0.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21729Add minor ticks to the Axis Grid2023-01-10T17:41:24-05:00W. Alan ScottAdd minor ticks to the Axis GridPlease optionally add minor ticks to the Axis grid, default off. My suggestion would be to add 4 additional ticks. For instance, if major ticks are at 0, 5, 10, 15, add minor ticks at 1,2,3,4 etc. Make this work correctly if a user en...Please optionally add minor ticks to the Axis grid, default off. My suggestion would be to add 4 additional ticks. For instance, if major ticks are at 0, 5, 10, 15, add minor ticks at 1,2,3,4 etc. Make this work correctly if a user enables "Show Grid".5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21730PV5.11 Segmentation fault Histogram2D2023-01-11T04:32:46-05:00Jean M. FavrePV5.11 Segmentation fault Histogram2DThe attached Python script demonstrates how v5.11 seg faults when changing the number of input points in the PointSource object. Execute the Python script and change pointSource1.NumberOfPoints to a different value and it seg faults.
[...The attached Python script demonstrates how v5.11 seg faults when changing the number of input points in the PointSource object. Execute the Python script and change pointSource1.NumberOfPoints to a different value and it seg faults.
[pvHistogram2D.py](/uploads/cc1b9d15a22c7d13d7372ed392fcf9f6/pvHistogram2D.py)https://gitlab.kitware.com/paraview/paraview/-/issues/21731Dragging text offscreen makes it go away2023-01-13T00:29:43-05:00W. Alan ScottDragging text offscreen makes it go awayDragging text offscreen makes it go away. Here is how to replicate.
* MacOS, 5.11.0, builtin server
* Sources/ Text. Apply.
* In the properties tab, select "Use Coordinates".
* Make ParaView smaller than the screen. Now we have ar...Dragging text offscreen makes it go away. Here is how to replicate.
* MacOS, 5.11.0, builtin server
* Sources/ Text. Apply.
* In the properties tab, select "Use Coordinates".
* Make ParaView smaller than the screen. Now we have areas of the screen that are not ParaView.
* Drag the text off of the ParaView application. You can never get it back. You have to delete the text and run the sources/text once again.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21732Implement Color Legend Interactivity property2023-01-12T09:58:57-05:00gabokamazeImplement Color Legend Interactivity propertyColor Legend in Render View can be dragged & dropped with left-click mouse, allowing automatic switching from any `WindowLocation` property value toward `‘AnyLocation’`.
A similar GUI behavior is available for the Orientation Axes. But c...Color Legend in Render View can be dragged & dropped with left-click mouse, allowing automatic switching from any `WindowLocation` property value toward `‘AnyLocation’`.
A similar GUI behavior is available for the Orientation Axes. But contrary to the latter, no kind of `Color Legend Interactivity` property is implemented. In consequence, the Color Legend can be innintentionate dragged, that can be annoying.
Such feature (`Color Legend Interactivity`) would be appreciated.
See following original forum post : https://discourse.paraview.org/t/prevent-legend-dragging-automatic-switch-to-windowlocation-anylocation/11119https://gitlab.kitware.com/paraview/paraview/-/issues/21733Ensure ParaView is ready for IPv62023-05-23T18:06:58-04:00Cory Quammencory.quammen@kitware.comEnsure ParaView is ready for IPv6Make sure ParaView can run on IPv6 networks.
The main task seems to be to convert `sockaddr_in`'s to `sockaddr_in6`'s. `vtkSocket` and the CAVEInteraction plugin seem to be the only places that need love. Collaboration code is another p...Make sure ParaView can run on IPv6 networks.
The main task seems to be to convert `sockaddr_in`'s to `sockaddr_in6`'s. `vtkSocket` and the CAVEInteraction plugin seem to be the only places that need love. Collaboration code is another place that might be affected.
https://beej.us/guide/bgnet/html/#jumping-from-ipv4-to-ipv6 may be helpful here.https://gitlab.kitware.com/paraview/paraview/-/issues/21734Paraview 5.11.0 Crash while saving Animation file (.plt files) on Windows2023-04-23T21:02:27-04:00prajwal vcParaview 5.11.0 Crash while saving Animation file (.plt files) on WindowsHi,
Mathieu Westphal has requested to open this issue here.
Please click on the below link for the issue details:
https://discourse.paraview.org/t/paraview-5-11-0-crash-while-saving-animation-file/11140/2
For files please click on ...Hi,
Mathieu Westphal has requested to open this issue here.
Please click on the below link for the issue details:
https://discourse.paraview.org/t/paraview-5-11-0-crash-while-saving-animation-file/11140/2
For files please click on the below link:
https://conceptsnrec.exavault.com/share/view/3aton-8og3kyjo
I hope to hear from you soon.
Best Regards,
Prajwal
Steps to reproduce:
- On Windows
- run paraview.exe
- open solution000002.plt, Apply
- enable P cell data, Apply
- crashMathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21735Catalyst: Set Breakpoint doesn't work2024-01-23T04:15:58-05:00Lucas GivordCatalyst: Set Breakpoint doesn't workOn paraview 5.11, breakpoints setted are ignore when we start a live simulation.
---
Step to reproduce:
- compile `CxxFullExample` in `Examples/Catalyst2`
- add in the `catalyst_options` (to be able to connect the simulation with para...On paraview 5.11, breakpoints setted are ignore when we start a live simulation.
---
Step to reproduce:
- compile `CxxFullExample` in `Examples/Catalyst2`
- add in the `catalyst_options` (to be able to connect the simulation with paraview) :
```py
from paraview import catalyst
options = catalyst.Options()
options.EnableCatalystLive = 1
```
- start paraview, click on `Connect...` inside `Catalyst` toolbar
- click on `Set Breakpoint` and set the value to 3.
- start the simulation
```
bin/CxxFullExample ../catalyst_pipeline.py
```
the simulation will never stop at the end of the 3 time step.
---
Note that the `Pause Simulation` works well.https://gitlab.kitware.com/paraview/paraview/-/issues/21737Windows nightly builds seem broken2023-01-17T08:35:51-05:00Fabian.WeinWindows nightly builds seem brokenWhen I understand the nightly versioning scheme correctly, for
```
* ParaView-release-5.11.0-35-g09163127...
* ParaView-master-5.11.0-599-g79a6058139-...
```
the 35 and 599 are consecutive counters? macOS and Linux have several -5??- ver...When I understand the nightly versioning scheme correctly, for
```
* ParaView-release-5.11.0-35-g09163127...
* ParaView-master-5.11.0-599-g79a6058139-...
```
the 35 and 599 are consecutive counters? macOS and Linux have several -5??- versions and a -35- version to download. Windows currently only -35-. This seems to be quite old, were e.g. CFSReader is not contained yet.https://gitlab.kitware.com/paraview/paraview/-/issues/21738Force using Wayland2024-03-26T04:09:07-04:00dr-brForce using WaylandI use GNOME under Wayland.
When I start Paraview {5.10.1, 5.11.0}, is says
```
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
```
The variables are set correctly, but not take...I use GNOME under Wayland.
When I start Paraview {5.10.1, 5.11.0}, is says
```
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
```
The variables are set correctly, but not taken into account. Using the `xeyes` app I notice, that Paraview indeed does not run natively under Wayland.
Unfortunately, the resolution under XWAYLAND0 is below my native HiDPI resolution, resulting in a very blurred UI.
I got all of my other applications (electron apps, browsers, ...) working correctly (and crisp) under Wayland, Paraview, however, is a tougher nut to crack.
Is there any possibility, to get a decent and crisp UI?
- Is it possible to enforce the usage of Wayland (is there something like a qt5 flag)?
- Would it be possible, to somehow influence the resolution of XWAYLAND0?
Thanks.https://gitlab.kitware.com/paraview/paraview/-/issues/21743Table to point filter fails when coordinates contain NaN2023-01-19T04:58:45-05:00Francesco FiuscoTable to point filter fails when coordinates contain NaNWhen the Table to point filter is used to create points from a CSV file(s), if one of the coordinates is NaN, the filter fails. I have not tried with Paraview 5.10 and 5.11, but this behaviour was observed with versions <= 5.9.When the Table to point filter is used to create points from a CSV file(s), if one of the coordinates is NaN, the filter fails. I have not tried with Paraview 5.10 and 5.11, but this behaviour was observed with versions <= 5.9.https://gitlab.kitware.com/paraview/paraview/-/issues/21744Currently generated ParaView Catalyst Python scripts have no way to modify fi...2023-02-02T09:57:36-05:00Andrew BauerCurrently generated ParaView Catalyst Python scripts have no way to modify filter parameters during calls to CatalystI tested out the ability to set filter properties for Catalyst scripts that vary in time (e.g. having a slice filter output rotate as the simulation proceeds). With the currently GUI generated Catalyst Python scripts (using master on Ja...I tested out the ability to set filter properties for Catalyst scripts that vary in time (e.g. having a slice filter output rotate as the simulation proceeds). With the currently GUI generated Catalyst Python scripts (using master on Jan 18, 2023) the pipeline is created once by Catalyst and not called again. Try out the attached newslice.py script where I've added print statements. If sources in the pipeline were updated every in situ output then the print statement would be called. It would be good for users to be able to edit the GUI generated Catalyst Python scripts to allow filter properties to be updated during every Catalyst output step.
If I modify the Examples/Catalyst/SampleScripts/gridwriter.py script (also attached) and edit the DoCoProcessing() method I can get the slice normal to change with time. This gridwriter.py is the "old style" Catalyst script though and not generated through the GUI.
I think if there was some optional UpdateProperties() like method that was added to the Catalyst scripts where users could modify properties that would be a way to get around this issue. Here, UpdateProperties() would be called every time Catalyst was outputting extracts, images,etc.
[gridwriter.py](/uploads/f9326ff8e208a8cb13341c8dae416547/gridwriter.py)
[newslice.py](/uploads/e352eb44a96e301e1fa28ab56ef1bdbb/newslice.py)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21745Glyph and Warp by Vector unavailable for 2D Exodus vectors with IOSS reader2023-01-19T04:58:26-05:00Weston OrtizGlyph and Warp by Vector unavailable for 2D Exodus vectors with IOSS readerRelated issues #21517 and #21237
ParaView reads the 2D vector fields and allows coloring by magnitude and components but glyph and warp by vector are unavailable until a calculator is used to add the "kHat" component.
Attached below is...Related issues #21517 and #21237
ParaView reads the 2D vector fields and allows coloring by magnitude and components but glyph and warp by vector are unavailable until a calculator is used to add the "kHat" component.
Attached below is an exodus file which exhibits the behavior of not allowing glyph or warp by vector on 2D vectors. This issue still exists in the current nightly (5.11.0-40-g548b8cba56)
Below is a quote from my comment in #21237:
> DISPLACEMENTX, DISPLACEMENTY are mesh displacement which trigger the Legacy Exodus Reader "Apply Displacements"
> DMX, DMY are copies of DISPLACEMENT
> VX, VY are also a vector
> All are read correctly in the Legacy Exodus Reader
> In the new IOSS reader (5.11.0-RC2) they seem to be read as vectors but cannot be warped by vector (option is greyed out)
[out_knife_displ.exoII](/uploads/0e791885994ea8e92791b600e52a49cc/out_knife_displ.exoII)