ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-06-15T03:21:12-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/22175Export OpenVDB from ParaView and import it back into ParaView, the data is di...2023-06-15T03:21:12-04:00Huang ChaoExport OpenVDB from ParaView and import it back into ParaView, the data is different, is there something wrong?I use Paraview 5.11.1 and use the Wavelet data which is in the paraview Source, I export it to OpenVDB
format and then load the vdb file back. But I figure out that the two datasets’s cell number and point number are different. Is that r...I use Paraview 5.11.1 and use the Wavelet data which is in the paraview Source, I export it to OpenVDB
format and then load the vdb file back. But I figure out that the two datasets’s cell number and point number are different. Is that right? Thanks for response.
![image](/uploads/1953ea1a1b4cfc73678e9011763733b5/image.png)
![image](/uploads/61e8f1cff657ff0ac86bf45de600bc6c/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22174Right click context menu failing2023-06-13T13:33:52-04:00Phil SmithRight click context menu failingTested on MacOS x86 ParaView 5.11.1 Master. The right click context menu will fail to find the correct block/position when menu item View->Preview->" Any resolution that is not supported by current monitor or video driver" shows.
This i...Tested on MacOS x86 ParaView 5.11.1 Master. The right click context menu will fail to find the correct block/position when menu item View->Preview->" Any resolution that is not supported by current monitor or video driver" shows.
This is intermittent at times when the ParaView window is moved from one monitor to another. Please see the example below:
![image](/uploads/b9f9c2db18d2f87c91872656b5d4d53f/image.png)
![image](/uploads/c5b459925e8500d30b406504e2166778/image.png)
Please reference this Discourse issue: [12083](https://discourse.paraview.org/t/right-click-context-menu-will-failed-to-find-the-correct-position-when-set-view-preview-that-not-supported/12083)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22173A proposal to redesign file series2023-06-13T11:52:44-04:00Mathieu Westphal (Kitware)A proposal to redesign file series# Status
file series is a useful mechanism in ParaView that lets anyone create transient data using multiple dataset as individual timesteps.
It can either be based on the names of the datasets (`data_1.ext`, `data_2.ext`, ...) or manag...# Status
file series is a useful mechanism in ParaView that lets anyone create transient data using multiple dataset as individual timesteps.
It can either be based on the names of the datasets (`data_1.ext`, `data_2.ext`, ...) or managed using a `.series` file.
While very useful, this approach has many downsides:
1. XML complexity
The way it is currently implemented rely on the vtkFileSeriesReader that encapsulate the reader doing the actual reading.
It makes senses to use this VTK class for this purpose however it requires an exlicit usage of a FileSeriesReader proxy that also encapsulate
the actual reader proxy, which is internal.
This means that adding the series feature to a reader is a not a simple boolean to turn on or off and is actually quite complex to setup for beginners.
This approach also do not scale at all, one cannot add, eg, a new "BlockSeries" concept to this.
2. Extensions configuration
Some readers actually defined `.ext.series` as compatible in the XML of the reader, which means that a reader with multiple extension supported should duplicate
each of them. Once again, not scallable.
3. Confusion for readers supporting temporal data
Some readers supports temporal data, yet also support file series, increasing the complexity again.
# Solution
file series should not be part of a reader declaration but should be a feature of ParaView directly, completely hidden from the XML declaration.
For the rare cases where a reader wants to opt out of the file series mechanism, a dedicated hint could be added.
# Implementation design
TODO if we agree to move forward.
WDYT @julien.fausty @cory.quammenhttps://gitlab.kitware.com/paraview/paraview/-/issues/22172Camera and camera widget links should be mutually exclusive2023-06-13T07:19:17-04:00Charly BollingerCamera and camera widget links should be mutually exclusive## Description
With the new `Camera Widget View Link` available in the ̀Manage Links` and `Camera Link` panels, we can both link two cameras and create a camera widget view link. This does not make any sense because if cameras are link...## Description
With the new `Camera Widget View Link` available in the ̀Manage Links` and `Camera Link` panels, we can both link two cameras and create a camera widget view link. This does not make any sense because if cameras are linked (i.e. have the same point of view), we can't see the camera widget in the controlling render view.
This is due to the fact that the default link when selecting two render views is the camera link, with no possibility to deactivate it. The expected behavior would be to make unavailable a camera link when a camera widget view link is already present between two render views (and vice versa).
## Possible solution
The UI of these two panels could be reworked to explicitly exposed the type of link being created, and make options unavailable when a link is already present. As the `Camera Link` panel works a bit differently (i.e. we don't know which render view is going to be selected), we should just ignore clicking on a render view that already has a link, the same way we ignore clicking on the same render view. A message could be print to warn users.
Camera Widget View Link MR: !6349Charly BollingerCharly Bollingerhttps://gitlab.kitware.com/paraview/paraview/-/issues/22171Using the Trace function will not work when using the spreadsheet to select a...2023-06-12T03:39:13-04:00Phil SmithUsing the Trace function will not work when using the spreadsheet to select a point and Plotting Over Time, to produce a script properlyUsing Linux 5.11.1 master an error is produced when using the spreadsheet to select a point in your dataset, and saving this as a script or macro. Here are the steps to reproduce this error:
* Open bake.e; Apply
* Tools > Start Trace
* ...Using Linux 5.11.1 master an error is produced when using the spreadsheet to select a point in your dataset, and saving this as a script or macro. Here are the steps to reproduce this error:
* Open bake.e; Apply
* Tools > Start Trace
* Click OK to accept all default settings
* Open a spreadsheet view
* In the spreadsheet view, select any point
* Select Filters-> Plot Data Over Time; Yes; Apply
* Tools > Stop Trace
* Within the Script editor select File->Save As Script
* Reset session
* Open bake.e; Apply
* Run the script
Here is the error that is produced:
```
Traceback (most recent call last):
File "<string>", line 37, in <module>
File "/projects/viz/paraview/ParaView/5.11.1-kw/Linux-cee-rhel7-x86_64/lib/python3.9/site-packages/paraview/selection.py", line 402, in SelectCompositeDataIDs
selectIDsHelper('CompositeDataIDSelectionSource', **locals())
NameError: name 'selectIDsHelper' is not defined
```
It looks like there are no points selected within the spreadsheet when the script is run.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22170Using the Trace function will not work with Find Data/plot over time to produ...2023-06-13T17:35:10-04:00Phil SmithUsing the Trace function will not work with Find Data/plot over time to produce a macro properlyUsing Linux 5.11.1 master an error is produced when using find data to select a point using the point ID. Here are the steps to reproduce this error:
- Open bake.e; Apply
- Tools > Start Trace
- Click OK to accept all default settings
...Using Linux 5.11.1 master an error is produced when using find data to select a point using the point ID. Here are the steps to reproduce this error:
- Open bake.e; Apply
- Tools > Start Trace
- Click OK to accept all default settings
- View > Find Data
- In the Find Data tab, set selection criteria
- Data Producer: bake.e
- Element Type: Point
- “ids” “is” “3125”
- Click “Find Data”
- Select datapoint
- Click “Plot Over Time”
- Click “Apply”
- Tools > Stop Trace
- Within the Script editor select File->Save As Macro
- Reset session
- Open bake.e; Apply
- Click "Your Macro" on the toolbar
- NameError: name ‘plotSelectionOverTime1’ is not defined
I looked at the Python code and plotSelectionOverTime1 is never set.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22168Update Find Data/ point/ nearest/ deprecate epsilon2023-06-08T21:01:49-04:00W. Alan ScottUpdate Find Data/ point/ nearest/ deprecate epsilonPlease update the Find Data dialog/ points/ nearest to, to have an option, default on, to select the nearest point without an epsilon. If a user asks for nearest point she probably means nearest point. Actually, have the option on to a...Please update the Find Data dialog/ points/ nearest to, to have an option, default on, to select the nearest point without an epsilon. If a user asks for nearest point she probably means nearest point. Actually, have the option on to add or enable the epsilon. Credit @phismith25 - this is a good idea.
While in this dialog, please move the X, Y and Z input boxes to the next line (next to the sometimes available epsilon). Currently, default width, X, Y and Z are way too narrow.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22167Mac Pro with AMD Radeon Pro W5500X throws a frame buffer warning. But ParaVie...2023-06-12T03:39:47-04:00Phil SmithMac Pro with AMD Radeon Pro W5500X throws a frame buffer warning. But ParaView does not uncheck the option in properties panelOn My Mac Pro with AMD Radeon Pro W5500X it still gives that irritating waring, but as Cory says, it does give some useful information. However, even though it says that is is disabling the floating point framebuffer, it still is checked...On My Mac Pro with AMD Radeon Pro W5500X it still gives that irritating waring, but as Cory says, it does give some useful information. However, even though it says that is is disabling the floating point framebuffer, it still is checked as active in the properties panel.:
https://gitlab.kitware.com/paraview/paraview/uploads/5580523859737e2033e157197bc13a0f/image.png
![image](/uploads/d6ca8e6a28a15a0cd1172aa5fec8420c/image.png)
Can we get it to uncheck or hide the Use Floating point Frame buffer in the properties panel with the AMD Radeon graphics card, so the message and the checkbox are consistent?
I looked on my MacBook Pro with Intel Iris Plus Graphics 655, and did not see the Use Floating Point Frame Buffer option or the warning with v5.11.1 master.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22166vtkPVGeometryFilter SetUseStrips and SetForceUseStrips needs state compatibil...2024-02-07T10:41:35-05:00Mathieu Westphal (Kitware)vtkPVGeometryFilter SetUseStrips and SetForceUseStrips needs state compatibily work before being deprecatedIn https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5799, vtkPVGeometryFilter SetUseStrips and SetForceUseStrips are "deprecated" but no work has been done in
`Remoting/ServerManager/vtkSMStateVersionController.cxx` and `W...In https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5799, vtkPVGeometryFilter SetUseStrips and SetForceUseStrips are "deprecated" but no work has been done in
`Remoting/ServerManager/vtkSMStateVersionController.cxx` and `Wrapping/Python/paraview/_backwardscompatibilityhelper.py`. It should be done before any actual deprecation/removal happens.https://gitlab.kitware.com/paraview/paraview/-/issues/22165Make the Color Legend Editor stand on it's own.2023-06-06T18:34:00-04:00W. Alan ScottMake the Color Legend Editor stand on it's own.The Color Legend Editor hangs off the Color Map Editor. (It's the little color legend icon with an e at the top of the Color Map Editor). This is totally wrong. Please make it equal to the Color Map Editor. In other words, remove it'...The Color Legend Editor hangs off the Color Map Editor. (It's the little color legend icon with an e at the top of the Color Map Editor). This is totally wrong. Please make it equal to the Color Map Editor. In other words, remove it's icon from the Color Map Editor. Add it's icon to the tool bars just to the right of the Color Map Editor icon. Add it to the View menu as it's own view. Give it the same properties as the Color Map Editor., making it dockable. As with the Color Map Editor, make it non-modal. Ask @cory.quammen for specific ideas.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22163PHTG reading of ParaView written files does not work since version 5.92023-06-07T03:14:48-04:00maximilian-techPHTG reading of ParaView written files does not work since version 5.9PHTG reading of ParaView written files does not work (segfaults) since ParaView 5.9.
Steps to reproduce
* Start pvserver (goto `<paraview>/bin/`, execute `./mpiexec -np 4 ./pvserver --mpi -sp=11116`
* Observe Connection URL: `cs://<us...PHTG reading of ParaView written files does not work (segfaults) since ParaView 5.9.
Steps to reproduce
* Start pvserver (goto `<paraview>/bin/`, execute `./mpiexec -np 4 ./pvserver --mpi -sp=11116`
* Observe Connection URL: `cs://<user-hostname>:11116`
* Connect with client `./paraview --server-url=cs://<user-hostname>:11116`
* Make sure that correctly started with MPI using `View -> Memory Inspector`, verify server has multiple processes.
* Create `Sources->Alphabetical->Hyper Tree Grid (Random)`
* Save via `Ctrl+S` as `*.phtg`
* Delete `HyperTreeGridRandom1`
* Open the previously saved `*.phtg`
* Observe `Segmentation fault`
This also fails when trying to load the `*.phtg` with serial `./paraview`
This **fails** with `ParaView v5.9.1/v5.10.1/v5.11.1`.
This **works** with `ParaView v5.8.1`.
`Paraview v5.11.1` cannot open a `ParaView v5.8.1` `*.phtg` and vice versa.
The [phtg_files.zip](/uploads/f3021a02ecfab7880df3f0ff4cd698e2/phtg_files.zip) are appended.https://gitlab.kitware.com/paraview/paraview/-/issues/22161Artefact when rendering with pvbatch and MPI2023-06-06T04:23:51-04:00Eve Le GuillouArtefact when rendering with pvbatch and MPIHi all,
I am using Paraview 5.11.0 and MPI 4.0.3.
I noticed a bug in the produced image when I execute the following pipeline:
Wavelet > MaskPoints(GenerateVertices = 1) > SaveScreenShot
Here is the full pipeline with the visuali...Hi all,
I am using Paraview 5.11.0 and MPI 4.0.3.
I noticed a bug in the produced image when I execute the following pipeline:
Wavelet > MaskPoints(GenerateVertices = 1) > SaveScreenShot
Here is the full pipeline with the visualization details [test.py](/uploads/22433c852033f6932a7178e92ffe2db7/test.py)
Points are shown using the RenderPointsAsSphere option.
When executing the pipeline using the command:
mpirun -n 2 pvbatch test.py
I obtain the following image:
![test](/uploads/bcf02df929f8674d70073fe85180e578/test.jpeg)
Artefacts can be seen on the image. The more processes are used, the more artefacts there are.
The problem doesn't appear when the pipeline is executed using pvserver and the paraview client.https://gitlab.kitware.com/paraview/paraview/-/issues/22160slice widget z-fighting when resizing the circle2023-06-06T09:47:19-04:00Dan Lipsaslice widget z-fighting when resizing the circleFor version 5.11.1, for the new slice widget (with round slice) there is Z-fighting between the slice widget (green) and the slice when
resizing the circle.
To test this:
Wavelet, Apply;
Slice, Apply;
Resize circleFor version 5.11.1, for the new slice widget (with round slice) there is Z-fighting between the slice widget (green) and the slice when
resizing the circle.
To test this:
Wavelet, Apply;
Slice, Apply;
Resize circleSpiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22159REQUIRED_PLUGINS mechanism is non fonctionnal on Windows2023-06-01T06:51:19-04:00Mathieu Westphal (Kitware)REQUIRED_PLUGINS mechanism is non fonctionnal on WindowsREQUIRED_PLUGINS mechanism (in `paraview_client_add` CMake macro) is non fonctionnal on Windows.
Steps to reproduce (on Windows):
- compile and install ParaView
- compile SimpleParaView example
- run simple_paraview
- MyElevation filte...REQUIRED_PLUGINS mechanism (in `paraview_client_add` CMake macro) is non fonctionnal on Windows.
Steps to reproduce (on Windows):
- compile and install ParaView
- compile SimpleParaView example
- run simple_paraview
- MyElevation filter is not available
FYI @ben.boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22158When using file name format fooN.vtk, "Open" shows VTK file series as group, ...2023-05-31T10:30:46-04:00Rafael BagoodWhen using file name format fooN.vtk, "Open" shows VTK file series as group, but loads it as multiple groups instead.As in the title, if you have a VTK file series named fooN.vtk, it'll appear as a single file group in "Open" but loading divided file series. This problem is solved though when you use the file format foo_N.vtk.
Link for images:
[https:...As in the title, if you have a VTK file series named fooN.vtk, it'll appear as a single file group in "Open" but loading divided file series. This problem is solved though when you use the file format foo_N.vtk.
Link for images:
[https://discourse.paraview.org/t/vtk-files-appear-as-series-in-file-loader-but-are-separated-when-loeaded-in/12196/3?u=bloop](url)https://gitlab.kitware.com/paraview/paraview/-/issues/22157ParaView 5.11 crashes when opening vth file2023-06-02T04:01:19-04:00Xiaowen ShanParaView 5.11 crashes when opening vth file[crash.zip](/uploads/31c4efb6046bb929ebfaf63efc4f71d1/crash.zip)
As the title says, the window disappears while clicking the vth file. the vti files that the vth refers to are OK.
Moving the vti files to the folder of vth file won't he...[crash.zip](/uploads/31c4efb6046bb929ebfaf63efc4f71d1/crash.zip)
As the title says, the window disappears while clicking the vth file. the vti files that the vth refers to are OK.
Moving the vti files to the folder of vth file won't help. Hand-editing the vth file to remove the directory part of the file names won't help either. But, if remove all the Blocks except the first one (level 0), it won’t crash.
The files and directories were created by vtkXMLPUniformGridAMRWriter.https://gitlab.kitware.com/paraview/paraview/-/issues/22155Segfault when loading ASCII PVTU2023-06-15T15:01:43-04:00FG-TUMSegfault when loading ASCII PVTUThis issue is a follow-up to the discussion over at the ParaView forums: https://discourse.paraview.org/t/segfault-when-loading-pvtu/12082.
TL;Dr:
Opening a pvtu file, which references 64 vtu files with 20MB each, can cause segfaults. T...This issue is a follow-up to the discussion over at the ParaView forums: https://discourse.paraview.org/t/segfault-when-loading-pvtu/12082.
TL;Dr:
Opening a pvtu file, which references 64 vtu files with 20MB each, can cause segfaults. The stack trace suggests that it has to do with the data being in ASCII format.
Data to reproduce: https://send.kitware.io/download.php?id=2037&token=qfJiGxmcc4FltggysAjMqhVkCNtZG2h3https://gitlab.kitware.com/paraview/paraview/-/issues/22154Missing dlls for cxx tests inside ParaView plugins on Windows2023-06-02T11:00:31-04:00Thomas GallandMissing dlls for cxx tests inside ParaView plugins on WindowsCurrently, the VTK testing framework do not allow to run `cxx` tests written inside ParaView plugins without doing some "hacks".
By default test executables are put in `paraview_build_dir\bin\paraview-X.XX\plugins\MyPlugin` while VTK m...Currently, the VTK testing framework do not allow to run `cxx` tests written inside ParaView plugins without doing some "hacks".
By default test executables are put in `paraview_build_dir\bin\paraview-X.XX\plugins\MyPlugin` while VTK module libraries are in `paraview_build_dir\bin`, so they are not able to find the dlls at runtime.
A workaround is to edit the `PATH` environment variable for these tests specifically, for example:
```
file(TO_NATIVE_PATH "${CMAKE_BINARY_DIR}/${CMAKE_INSTALL_BINDIR}" paraview_libraries_path)
set(test_path "$ENV{PATH};${paraview_libraries_path}")
string(REPLACE ";" "\;" test_path "${test_path}")
foreach(test IN LISTS tests)
string(REPLACE ".cxx" "" test "${test}")
set_tests_properties(MyPlugin::MyModuleCxx-${test} PROPERTIES
ENVIRONMENT "PATH=${test_path}"
)
endforeach()
```
Is there a good way to add `cxx` tests from plugins, that we can add to the testing framework ?
FYI @mwestphal @ben.boeckel @francois.mazenBen BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22153Axis grid is SLOW when zoomed in2023-05-25T10:49:06-04:00W. Alan ScottAxis grid is SLOW when zoomed inThe axis grid is slow when zoomed in. It can be bad enough that it appears to hang. Here is how to replicate.
* 5.11.1, Linux, builtin server.
* Open can.exo. Don't touch it. Apply.
* Axis grid.
* On the left side you will see a coor...The axis grid is slow when zoomed in. It can be bad enough that it appears to hang. Here is how to replicate.
* 5.11.1, Linux, builtin server.
* Open can.exo. Don't touch it. Apply.
* Axis grid.
* On the left side you will see a coordinate of 4 on the y axis. Place your mouse on the edge of the can just to the right of the 4.
* <CTRL>, and now Right mouse button, and pull down. Do down (zoom in) until the axis grid goes away, and then reverse until the axis grid reappears. Let go of the mouse.
ParaView will tend to freeze as a bazillion axis grid labels are calculated. This is very, very bad behavior. We need to fix it.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22151OpenFOAM reader in 5.11.1 selects geometry regions incorrectly if "Read zones...2023-05-23T06:50:20-04:00Åsmund ErvikOpenFOAM reader in 5.11.1 selects geometry regions incorrectly if "Read zones" is enabledI'm encountering a bug in Paraview with the OpenFOAM reader, where ticking the "Read zones" option causes an incorrect selection of mesh regions.
In the first screenshot below, I have selected a single patch (boundary region) of a geome...I'm encountering a bug in Paraview with the OpenFOAM reader, where ticking the "Read zones" option causes an incorrect selection of mesh regions.
In the first screenshot below, I have selected a single patch (boundary region) of a geometry, without "Read zones", and the patch is displayed correctly.
![paraview-read-zones-correct](/uploads/d32cec987ed668cd5883799e1c11554a/paraview-read-zones-correct.png)
If I enable the "Read zones" option **without changing anything else**, the displayed selection of mesh regions changes significantly and gives me something that is obviously wrong, since it includes parts of the interior mesh.
![paraview-read-zones-incorrect](/uploads/7e8f4d16362cfd15aee706442733ff72/paraview-read-zones-incorrect.png)
I'm getting this error on Paraview 5.11.1 on Arch Linux. I don't have an older Paraview install that I can test with, but I think maybe this used to work fine in the past.
The screenshots taken here are from the OpenFOAM v2112 tutorial case "incompressible/pisoFoam/RAS/cavity" such that you have an example for reproducing. I have uploaded also the case folder if that's easier to use: [cavity-read-zones-bug.zip](/uploads/f42b49803bf1a9b23e58b67b30e0005f/cavity-read-zones-bug.zip)