ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-05-25T10:49:06-04:00https://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/22108Paraview opens ADIOS2-VTX BP5 files as BP42024-01-05T11:38:23-05:00Massimiliano LeoniParaview opens ADIOS2-VTX BP5 files as BP4[I am filing with Paraview but this might as well be a VTK problem].
With the release of ADIOS2 2.9.0, BP5 is now the default file engine [cfr. https://github.com/ornladios/ADIOS2/releases/tag/v2.9.0 ]. I tried to open BP5-VTX files cre...[I am filing with Paraview but this might as well be a VTK problem].
With the release of ADIOS2 2.9.0, BP5 is now the default file engine [cfr. https://github.com/ornladios/ADIOS2/releases/tag/v2.9.0 ]. I tried to open BP5-VTX files created through my code that uses the newest version of ADIOS2 and I get a `BP4Reader` error, whereas running with a debugger I verified that the file is created by a `BP5Writer`.
I suspect Paraview should instead be using a `BP5Reader`.Caitlin RossCaitlin Rosshttps://gitlab.kitware.com/paraview/paraview/-/issues/21816[Feature Request] Ship ParaView with a mangled VTK2023-03-15T13:17:55-04:00Julien Fausty[Feature Request] Ship ParaView with a mangled VTK## Problem Statement
When including ParaView into applications that already compile and link to VTK, collisions between ParaView's VTK version and the application's can occur at runtime leading to a crash if the VTK versions are incompa...## Problem Statement
When including ParaView into applications that already compile and link to VTK, collisions between ParaView's VTK version and the application's can occur at runtime leading to a crash if the VTK versions are incompatible.
As an example, this can happen when using ParaView's `Catalyst` implementation in a code that already links to an external system VTK.
## Proposed Solution
Given that it is much more likely for another application that already links VTK to develop a dependency on ParaView than it is for ParaView to develop a dependency on another application using VTK, it seems only natural that it should be ParaView's responsibility to mangle its internal VTK libraries using the relatively new `VTK_ABI_NAMESPACE` feature developed in https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8993 (discourse here: https://discourse.vtk.org/t/new-feature-in-vtk-vtk-abi-namespace/9421).
This functionality wraps all of VTK in a compile time defined namespace. The symbols are then "sealed" against collision.
Thoughts?https://gitlab.kitware.com/paraview/paraview/-/issues/21789PythonAlgorithmExamples.py fails to load2023-02-26T20:15:47-05:00Juan Jose CasafrancaPythonAlgorithmExamples.py fails to loadThe PythonAlgorithmExamples.py examples fail to load in Paraview 5.10 and Paraview 5.11 which are the version I have tested it.
```
Failed to call `paraview.detail.pythonalgorithm.load_plugin`.
Traceback (most recent call last):
File...The PythonAlgorithmExamples.py examples fail to load in Paraview 5.10 and Paraview 5.11 which are the version I have tested it.
```
Failed to call `paraview.detail.pythonalgorithm.load_plugin`.
Traceback (most recent call last):
File "/opt/paraview/lib/python3.10/site-packages/paraview/detail/pythonalgorithm.py", line 509, in load_plugin
spec.loader.exec_module(module)
File "<frozen importlib._bootstrap_external>", line 883, in exec_module
File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
File "/home/jjcasmar/Downloads/PythonAlgorithmExamples.py", line 16, in <module>
class PythonSuperquadricSource(VTKPythonAlgorithmBase):
File "/home/jjcasmar/Downloads/PythonAlgorithmExamples.py", line 57, in PythonSuperquadricSource
def SetThetaResolution(self, x):
File "/opt/paraview/lib/python3.10/site-packages/paraview/detail/pythonalgorithm.py", line 76, in decorator
updated_attrs = update_func(original_func, attrs)
File "/opt/paraview/lib/python3.10/site-packages/paraview/detail/pythonalgorithm.py", line 144, in _update_vectorproperty_defaults
assert attrs["number_of_elements"] == _count(attrs["default_values"])
AssertionError
( 9.646s) [paraview ] vtkPVPluginLoader.cxx:532 ERR| vtkPVPluginLoader (0x56122d209ba0): /home/jjcasmar/Downloads/PythonAlgorithmExamples.py: /home/jjcasmar/Downloads/PythonAlgorithmExamples.py: invalid ELF header
```5.11.1 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21776qt.core.qobject.connect: QObject::connect: No such slot QTableView::sortByCol...2023-02-17T06:07:56-05:00Julien Schuellerqt.core.qobject.connect: QObject::connect: No such slot QTableView::sortByColumn(int)probably from Qt/Components/pqDataInformationWidget.cxx:
```
// Clicking on the header should sort the column.
QObject::connect(this->View->horizontalHeader(), SIGNAL(sectionClicked(int)), this->View,
SLOT(sortByColumn(int)));
``...probably from Qt/Components/pqDataInformationWidget.cxx:
```
// Clicking on the header should sort the column.
QObject::connect(this->View->horizontalHeader(), SIGNAL(sectionClicked(int)), this->View,
SLOT(sortByColumn(int)));
```
probably because it has an extra argument "order":
https://doc.qt.io/qt-5/qtableview.htmlhttps://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/21671OSPRay warning prints should be silent when OSPRay turned off2023-04-25T16:30:30-04:00W. Alan ScottOSPRay warning prints should be silent when OSPRay turned offWhen the environment variables VTK_DISABLE_VISRTX and VTK_DISABLE_OSPRAY are set, OSPRay should be turned off. We should also not have a warming print that says:
```
vtkPVRenderView.cxx:3273 WARN| vtkPVRenderView (0x15618570): Refusing...When the environment variables VTK_DISABLE_VISRTX and VTK_DISABLE_OSPRAY are set, OSPRay should be turned off. We should also not have a warming print that says:
```
vtkPVRenderView.cxx:3273 WARN| vtkPVRenderView (0x15618570): Refusing to enable OSPRay because it is not supported running in this configuration.
```5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://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/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/21466ParaView crashes when selecting "Use Window Location" for Text Source positio...2024-03-07T20:23:50-05:00Artem BodrinParaView crashes when selecting "Use Window Location" for Text Source position after a state loadIf Text Source was saved with "AnyLocation" property set, switching it to "Use Window Location" in Display dock after a state load crashes ParaView.
Affected versions: 5.9.1, 5.10.1
![paraview_crash](/uploads/5c1d683f2cdb7dee606b38128...If Text Source was saved with "AnyLocation" property set, switching it to "Use Window Location" in Display dock after a state load crashes ParaView.
Affected versions: 5.9.1, 5.10.1
![paraview_crash](/uploads/5c1d683f2cdb7dee606b38128ef23aa8/paraview_crash.mp4)
One of the possible solutions (no crash):
```c++
//-----------------------------------------------------------------------------
void pqTextLocationWidget::radioButtonLocationClicked()
{
auto button = this->Internals->Ui.buttonGroupLocation->checkedButton();
// --- there can be no checked button after a state loaded
if (!button)
{
button = this->Internals->Ui.toolButtonUL;
button->setChecked(true);
}
QString locationStr(button->property("location").toString());
this->setWindowLocation(locationStr);
}
```
The other one is to set a default checked button in UI file. Did not tested that.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21439Warp By Vector, Warp By Scalar: Always calculated with single precision2022-06-16T19:44:37-04:00Kenichiro YoshimiWarp By Vector, Warp By Scalar: Always calculated with single precisionThe **Warp By Vector** filter always computes in single precision, even when given double precision coordinates and displacement vectors. The **Warp By Scalar** filter also has the same phenomenon.
https://discourse.paraview.org/t/viewi...The **Warp By Vector** filter always computes in single precision, even when given double precision coordinates and displacement vectors. The **Warp By Scalar** filter also has the same phenomenon.
https://discourse.paraview.org/t/viewing-measurements-in-submicrometer/9817/5https://gitlab.kitware.com/paraview/paraview/-/issues/21156Save screenshots & movie to client or server2023-09-15T12:28:03-04:00Berk GeveciSave screenshots & movie to client or serverCurrently, images and animations are saved on the client side when running ParaView in client-server mode. In some situations, this is inconvenient. For example, when the client is running on a "thin client" computer, there may be limite...Currently, images and animations are saved on the client side when running ParaView in client-server mode. In some situations, this is inconvenient. For example, when the client is running on a "thin client" computer, there may be limited space to save large movies or image sequences. Or the user may perform their main workflow on the server side, requiring them to upload the images or movies later. It should be possible to save these on either the client or the server side. The file browser should let the user browse both sides (possibly through the folder dropdown where the top level is the machine) and allow to save on either.5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21123Copy and paste filters in pipeline browser2023-10-18T11:26:24-04:00Boonthanome NouanesengsyCopy and paste filters in pipeline browserWe would like the ability to copy and paste filters in the pipeline browser, so that a user can easily replicate a pipeline on another dataset. A feature request for this is also at: https://gitlab.kitware.com/paraview/paraview/-/issues/...We would like the ability to copy and paste filters in the pipeline browser, so that a user can easily replicate a pipeline on another dataset. A feature request for this is also at: https://gitlab.kitware.com/paraview/paraview/-/issues/18771.
There is already a copy and paste option when right clicking items in the pipeline browser, but that is for values of a filter. It won't create new pipeline elements.
Another way to do this is to save the state, then load the state with another dataset. While this is nice, being able to copy and paste pipeline elements would be cleaner and faster.
@patchett2002 @ethan.stam @cory.quammen @utkarsh.ayachit5.12 (Winter 2023)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21063v5.10-RC1 documentation of particle tracers2021-10-28T02:37:16-04:00Jean M. Favrev5.10-RC1 documentation of particle tracersin filters_filtersflowpaths.xml, there are three distinct filters ("ParticlePath", "ParticleTracer","StreakLine"). Yet, they have exactly the same short_help, although their class differ, resp. vtkParticlePathFilter, vtkParticleTracer, v...in filters_filtersflowpaths.xml, there are three distinct filters ("ParticlePath", "ParticleTracer","StreakLine"). Yet, they have exactly the same short_help, although their class differ, resp. vtkParticlePathFilter, vtkParticleTracer, vtkStreaklineFilter.
This is utterly confusing for the users.https://gitlab.kitware.com/paraview/paraview/-/issues/20819Fluent 2021 R1 (Ensight Case Gold) solution files to ParaView 5.9.02023-05-31T11:35:43-04:00Cory Quammencory.quammen@kitware.comFluent 2021 R1 (Ensight Case Gold) solution files to ParaView 5.9.0First reported on [Discourse](https://discourse.paraview.org/t/fluent-2021-r1-ensight-case-gold-solution-files-to-paraview-5-9-0/7512):
Hello:
Looks like in Fluent 2021 R1 Engisht Case Gold file format has some changes. Did anyone use t...First reported on [Discourse](https://discourse.paraview.org/t/fluent-2021-r1-ensight-case-gold-solution-files-to-paraview-5-9-0/7512):
Hello:
Looks like in Fluent 2021 R1 Engisht Case Gold file format has some changes. Did anyone use the recent Ensight Gold format in ParaView 5.9.0? If you can share your experience much appreciated.
When I try to read using Ensight Reader, I get the error message: Can’t read *.geo file .
Attachment note: Please combine the two zip files first (using 7- zip or similar tools), then unzip it.
[Ensight_Gold.zip.001 (4 MB)](https://discourse.paraview.org/uploads/short-url/sXshY4CCROvGafzgo7Oq2sGGs23.001)
[Ensight_Gold.zip.002 (2.4 MB)](https://discourse.paraview.org/uploads/short-url/yj4V6hKsZ3xL9ANg5OR1QGYwZrr.002)
The first [reply](https://discourse.paraview.org/t/fluent-2021-r1-ensight-case-gold-solution-files-to-paraview-5-9-0/7512/2) hints at a solution:
There is a simple fix I found over on cfd online.
Open the .encas or .case file with a text editor
Search and replace all double quotes (") with a blank field (i.e. delete all double quotes).
Also at the bottom of the file might be a couple lines starting with “script” - delete those lines
Save the file, this is where I usually rename the extension from .encase to .case so Paraview automatically recognizes it as an Ensight dataset.https://gitlab.kitware.com/paraview/paraview/-/issues/20746Rewrite Ensight Gold Reader2024-03-07T20:23:45-05:00Utkarsh AyachitRewrite Ensight Gold ReaderThe EnSight readers could use some rework. They should be unified (avoid separate binary and ascii readers) and the produce PartitionedDataSetCollection instead of Multiblock.The EnSight readers could use some rework. They should be unified (avoid separate binary and ascii readers) and the produce PartitionedDataSetCollection instead of Multiblock.5.13 (Summer 2024)Caitlin RossCaitlin Rosshttps://gitlab.kitware.com/paraview/paraview/-/issues/20547Standardization of string substitutions2021-09-23T15:46:16-04:00Utkarsh AyachitStandardization of string substitutionsThere are several cases in ParaView where strings are substituted for runtime values. Currently,
however, there is no standard form for specifying these substitutions and various components
follow their own pattern inconsistently. This t...There are several cases in ParaView where strings are substituted for runtime values. Currently,
however, there is no standard form for specifying these substitutions and various components
follow their own pattern inconsistently. This task involves developing a framework for supporting
string substitutions across the application. The implementation may introduce third-party libraries
such as fmt for improved string formatting. The proposal aims to support named and well-
documented namespaces that make it easier for users to be aware of available string substitution
keywords within any given context.
[ref: proposal](https://discourse.paraview.org/t/standardizing-string-substitutions/4719)5.10 (Fall 2021)Spiros TsalikisSpiros Tsalikis2021-07-31https://gitlab.kitware.com/paraview/paraview/-/issues/20248Add new slice type: Cone, Frustum and revolution2022-09-25T18:41:32-04:00Haris MusaefendicAdd new slice type: Cone, Frustum and revolutionHello,
**Context:**
Only 4 types of slice available in paraview
- Plane
- Box
- Sphere
- Cylinder
**Request:**
Add new types of slice:
- Cone
- Frustum
- Revolution
These cuts are of interest for turbomachinery type applications. The ...Hello,
**Context:**
Only 4 types of slice available in paraview
- Plane
- Box
- Sphere
- Cylinder
**Request:**
Add new types of slice:
- Cone
- Frustum
- Revolution
These cuts are of interest for turbomachinery type applications. The problems are often axially symmetrical. Having access to these new sections would facilitate the postprocessing and visualization.
For information, these types are available with ensight. See ensight manual
- https://dav.lbl.gov/archive/NERSC/Software/ensight/doc/Manuals/HowTo.pdf
- cone tool: page 146
- revolution tool: page 148https://gitlab.kitware.com/paraview/paraview/-/issues/19637Filters naming convention2020-05-06T12:41:52-04:00Joachim PouderouxFilters naming conventionMost filter names are decomposed in words separated with spaces in the filters menu (eg. "Aggregate Dataset"), but some of them are named in camel case (eg. "ParticlePath", "ParticleTracer", "PassArrays"). Also, some use the name "Datase...Most filter names are decomposed in words separated with spaces in the filters menu (eg. "Aggregate Dataset"), but some of them are named in camel case (eg. "ParticlePath", "ParticleTracer", "PassArrays"). Also, some use the name "Dataset", other "DataSet").
It would be nice to uniformize the naming convention for filters.https://gitlab.kitware.com/paraview/paraview/-/issues/19058VTK/VTU 2D points (two components)2021-03-24T05:28:37-04:00Nico SchlömerVTK/VTU 2D points (two components)The VTK/VTU file format specification states implicitly that points have to have three components. Not sure if this is intentional.
Alas, when creating 2D meshes (using, e.g., [meshio](https://github.com/nschloe/meshio)), the reference ...The VTK/VTU file format specification states implicitly that points have to have three components. Not sure if this is intentional.
Alas, when creating 2D meshes (using, e.g., [meshio](https://github.com/nschloe/meshio)), the reference tool ParaView _segfaults._
```
vtkPoints (0x6046fa0): Number of components is different...can't set data
Segmentation fault (core dumped)
```
[circle.vtu](/uploads/16570253057c92281e81c938207750da/circle.vtu)
Other file formats like XDMF are displayed correctly with 2D meshes.
[circle.xdmf](/uploads/167cae0651e6268ee6204efec4b9eac9/circle.xdmf)
[circle.h5](/uploads/ae93e8714165b1aee5c2effa66d8850d/circle.h5)
Any change of allowing 2D points in VTK/VTU for display?