ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-06-15T08:21:25-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/10926Custom filters are loaded before plugins, bug if custom filter refers to plug...2023-06-15T08:21:25-04:00Kitware RobotCustom filters are loaded before plugins, bug if custom filter refers to plugin proxy**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10926). Further discussion may take place here.**
---
If you make a custom filter using a proxy that was loaded by a plugin, the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10926). Further discussion may take place here.**
---
If you make a custom filter using a proxy that was loaded by a plugin, then the next time you start paraview the custom filter will not work. Paraview fails to load the custom filter definition because it tries to load it before loading the plugins, even if the plugins are set to auto load.https://gitlab.kitware.com/paraview/paraview/-/issues/12785XDMF Function SQRT results in segfault2023-06-15T08:18:56-04:00Kitware RobotXDMF Function SQRT results in segfault**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12785). Further discussion may take place here.**
---
defining a node attribute
in an XDMF file (see uploaded file)
using the It...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12785). Further discussion may take place here.**
---
defining a node attribute
in an XDMF file (see uploaded file)
using the ItemType "Function" as follows
results in a segfault
of a precompiled 64-bit ParaView 3.12.0
on CentOS 5.2
XDMF Function Definition:
Function="SQRT(($0 * $0) + ($1 * $1) + ($2 * $2))"https://gitlab.kitware.com/paraview/paraview/-/issues/9489Automatically adjust point/line sizes for screenshots with different resolution2023-06-15T08:16:58-04:00Kitware RobotAutomatically adjust point/line sizes for screenshots with different resolution**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9489). Further discussion may take place here.**
---
If you have points or lines in the scene and you take a screen shot at a hi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9489). Further discussion may take place here.**
---
If you have points or lines in the scene and you take a screen shot at a higher resolution than the current window (say 5000x5000), many of the objects stay the same size (spheres, planes, triangulated meshes) but many objects get much smaller (points, lines). Surely this is because the points and lines are specified in arbitrary units (Point Size = 3, Line Width=2, for example). An example is here:
http://rpi.edu/~doriad/Paraview_List/linesize.jpg
Notice the lines in the screenshot are much thinner.
It would be nice to have theses sizes automatically adjusted to the relative difference between the screenshot size and the render window size, so screenshots will look the same.https://gitlab.kitware.com/paraview/paraview/-/issues/21856Link Objects: does not work correctly for Render Views2023-06-15T08:11:24-04:00Julien FaustyLink Objects: does not work correctly for Render Views## Problem statement
When using the "Link Manager" to link objects in ParaView, one can link two filters, sources or representations together (i.e. link all their properties) but you cannot do the same thing for "Render Views". The link...## Problem statement
When using the "Link Manager" to link objects in ParaView, one can link two filters, sources or representations together (i.e. link all their properties) but you cannot do the same thing for "Render Views". The link manager shows an `Unknown` entry in properties:
![image](/uploads/3bd9a13fb42d336b20608ebad026f7ad/image.png)
This link between "Render Views" links the cameras of the two views without linking any of their properties.https://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/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/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/21770Create a repository of spack build examples2023-06-12T16:09:41-04:00W. Alan ScottCreate a repository of spack build examplesPlease create a repository of spack build examples. We are basically looking for a toolbox of examples.Please create a repository of spack build examples. We are basically looking for a toolbox of examples.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/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/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/20694python calculator partially handle FieldData2023-06-08T10:23:51-04:00Nicolas Vuaillepython calculator partially handle FieldDataAs mentioned in the [doc](https://docs.paraview.org/en/latest/UsersGuide/filteringData.html?highlight=python%20calculator#basic-operations), FieldData array can easily be used in Python Calculator expressions.
But I notice some unexpect...As mentioned in the [doc](https://docs.paraview.org/en/latest/UsersGuide/filteringData.html?highlight=python%20calculator#basic-operations), FieldData array can easily be used in Python Calculator expressions.
But I notice some unexpected behavior.
The combobox `Array Association` does not offer the FieldData choice, but using an expression containing only a FieldData create a FieldData array.
* load test_fielddata.vtk
* Python Calculator
* `inputs[0].FieldData["Field_1D"]`, Apply
-> a FieldData named result is created.
also maybe related to https://gitlab.kitware.com/paraview/paraview/-/issues/21649https://gitlab.kitware.com/paraview/paraview/-/issues/21163Spack package file in repo and upstream are out of sync2023-06-07T17:55:00-04:00Nils VuSpack package file in repo and upstream are out of syncThe Spack `package.py` file in the repo and the one upstream (https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py) have diverged. See also https://gitlab.kitware.com/paraview/paraview/-/issues...The Spack `package.py` file in the repo and the one upstream (https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py) have diverged. See also https://gitlab.kitware.com/paraview/paraview/-/issues/21158 for some discussion on this.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/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/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/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/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 Boeckel