ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-03-15T13:17:55-04:00https://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/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/16901Save State and Data2023-06-15T11:28:31-04:00W. Alan ScottSave State and DataFrom UserVoice. Good idea.
Add the ability to save both the state file and copy the data file(s) into the same directory.From UserVoice. Good idea.
Add the ability to save both the state file and copy the data file(s) into the same directory.5.11 (Spring 2022)https://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/15607Add ability to change colors of the orientation axis and center axis2018-08-08T22:24:38-04:00Kitware RobotAdd ability to change colors of the orientation axis and center axis**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15607). Further discussion may take place here.**
---
Please add the ability for a user to change the colors of the orientation ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15607). Further discussion may take place here.**
---
Please add the ability for a user to change the colors of the orientation axis and center axis.https://gitlab.kitware.com/paraview/paraview/-/issues/14655Animation view - follow path enhancement2022-07-05T06:14:37-04:00Kitware RobotAnimation view - follow path enhancement**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14655). Further discussion may take place here.**
---
The animation view, camera controls, follow path is fairly clunky. Instea...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14655). Further discussion may take place here.**
---
The animation view, camera controls, follow path is fairly clunky. Instead of just giving a user a list of nodes to manually edit, or allowing a user to drag the 3d nodes around on a 2d screen, we should allow the user to also jump from node to node, place the camera where they want it, and be able to say "Use Current" for that node. Repeat. https://gitlab.kitware.com/paraview/paraview/-/issues/13019improved coprocessing functionality2020-05-04T05:00:49-04:00Kitware Robotimproved coprocessing functionality**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13019). Further discussion may take place here.**
---
As the coprocessing tools move forward, there needs to really be 3 modes o...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13019). Further discussion may take place here.**
---
As the coprocessing tools move forward, there needs to really be 3 modes of use with the user able to switch between any of them. The 3 modes are:
1) batch -- the user specifies some pipelines to be executed at certain intervals. This is currently supported in paraview.
2) interactive with simulation code being stalled -- the user can change the current pipeline (including parameters of filters in the pipeline), add new pipelines, remove old pipelines with data from the simulation. The simulation code waits for the user to specify that they're done with the data and/or pipelines before control is returned to the simulation code.
3) interactive with simulation code continuing running -- same as above except that while the user is interacting with the data and/or pipelines, the simulation code keeps running. when the user is satisfied with the pipelines they can push that information back to the simulation code to be used the next time coprocessing is to be performed.https://gitlab.kitware.com/paraview/paraview/-/issues/12677Can't glyph 2d vectors2022-02-17T10:23:19-05:00Kitware RobotCan't glyph 2d vectors**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12677). Further discussion may take place here.**
---
I often want to visualize 2D vector fields. However, I can't glyph vectors...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12677). Further discussion may take place here.**
---
I often want to visualize 2D vector fields. However, I can't glyph vectors unless they have 3 components.https://gitlab.kitware.com/paraview/paraview/-/issues/22515Transformation (rotation) of tensor variables2024-03-08T07:43:50-05:00cmorsbachTransformation (rotation) of tensor variablesAs suggested by @mwestphal in https://discourse.paraview.org/t/transformation-of-tensor-variables/14112, I'm opening a ticket for this feature request:
Currently, the _Transform_ filter in ParaView applies the correct transformation (ro...As suggested by @mwestphal in https://discourse.paraview.org/t/transformation-of-tensor-variables/14112, I'm opening a ticket for this feature request:
Currently, the _Transform_ filter in ParaView applies the correct transformation (rotation) to vectors stored as 3-component float arrays. As there is support for Cartesian rank 2 tensors (6-component symmetric and 9-component general) in ParaView, it would be good, if these were transformed as well. Currently (ParaView 5.11), they are not, which leads to an inconsistent dataset when _Transform_ or _AngularPeriodicFilter_ are applied.https://gitlab.kitware.com/paraview/paraview/-/issues/21826feature request: Python Editor does _not_ notice script modification by exter...2023-03-21T05:22:53-04:00Pfiffikusfeature request: Python Editor does _not_ notice script modification by external editor e.g.When an opened script is manipulated by any external programme, the script editor runs nevertheless the outdated version of the script :disappointed:
What about to ask for a refresh when the editor gets focus again?
Alternatively a man...When an opened script is manipulated by any external programme, the script editor runs nevertheless the outdated version of the script :disappointed:
What about to ask for a refresh when the editor gets focus again?
Alternatively a manual refresh should be supported; currently closing & reopening of the obsolete version is necessary ...!?
Or could the workflow be optimized somewhere else?https://gitlab.kitware.com/paraview/paraview/-/issues/21202Export animated scene (.vtkjs) in pvpython2022-04-08T06:43:42-04:00Andreja28Export animated scene (.vtkjs) in pvpythonIs there any way to export animated scene (**_.vtkjs_**) using pvpython?
I am building an automated batch job inside a docker container, so the use of GUI is out of the question.
Up until now I have used either the official documentation...Is there any way to export animated scene (**_.vtkjs_**) using pvpython?
I am building an automated batch job inside a docker container, so the use of GUI is out of the question.
Up until now I have used either the official documentation or generating the stack trace in Paraview to find the corresponding pvpython functions to use, but for exporting **_.vtkjs_** there is none. Stack trace does not generate anything, and I cannot find the functionality in the documentation.
Is there any way to do this beside building my own script that manually creates **_.vtkjs_**?
For example in the past I have saved .ogv animations with _SaveAnimation()_ function.
Thanks in advance.https://gitlab.kitware.com/paraview/paraview/-/issues/21188Add option to hide duplicate and hidden ghosts from Spread Sheet View2022-01-20T13:18:11-05:00Yohann Bearzi (Kitware)Add option to hide duplicate and hidden ghosts from Spread Sheet ViewAs mentioned [here](https://discourse.paraview.org/t/paraview-5-9-1-ghostcells/8807), the spread sheet view doesn't filter out duplicate or hidden ghost cells (and likely ghost points as well). It did filter them out in 5.8.1. This chang...As mentioned [here](https://discourse.paraview.org/t/paraview-5-9-1-ghostcells/8807), the spread sheet view doesn't filter out duplicate or hidden ghost cells (and likely ghost points as well). It did filter them out in 5.8.1. This change of behavior is likely linked to the migration from `vtkMultiBlockDataSet` to `vtkPartitionedDataSet`.
This can be detrimental when analyzing data directly on the spreed sheet, or when exporting, as duplicated data (duplicated ghosts), or uninitialized data (hidden ghosts) can show up in the spread sheet. An option to display or not ghost information could possibly be useful if the user really wants to check ghost data.https://gitlab.kitware.com/paraview/paraview/-/issues/21158Add Spack installation test to CI2023-08-23T07:59:21-04:00Nils VuAdd Spack installation test to CII often encounter issues when installing ParaView and its dependencies with [Spack](https://github.com/spack/spack). Would it be possible to add a few automated tests that regularly ensure ParaView builds correctly for a few selected con...I often encounter issues when installing ParaView and its dependencies with [Spack](https://github.com/spack/spack). Would it be possible to add a few automated tests that regularly ensure ParaView builds correctly for a few selected configurations? My suggestion is to test the matrix [gcc, clang, apple-clang] x [ubuntu, macOS] for the following configuration:
```
spack install paraview +python3 +qt +hdf5
```https://gitlab.kitware.com/paraview/paraview/-/issues/21110ResampleToImage pass partial arrays2021-12-02T07:39:24-05:00Theodore BaltisResampleToImage pass partial arraysFeature request.
Similar to how ResampleWithDataset was updated in 5.10 to pass partial arrays, add the same functionality to ResampleToImage.Feature request.
Similar to how ResampleWithDataset was updated in 5.10 to pass partial arrays, add the same functionality to ResampleToImage.https://gitlab.kitware.com/paraview/paraview/-/issues/21007Property widget: table with two columns2022-06-09T14:09:40-04:00David ThompsonProperty widget: table with two columnsWe have a customer who would like a custom widget that accepts 2 extensible string-vector properties and displays them as columns in a table. (The widget should constraint the properties to have the same number of entries.)
One property...We have a customer who would like a custom widget that accepts 2 extensible string-vector properties and displays them as columns in a table. (The widget should constraint the properties to have the same number of entries.)
One property will have a file-list domain (so a file-browser pop-up should be provided with a "…" button) while the other property will not. The use case is a widget for assigning nicknames to files that will be used in a python filter script; the nicknames will be used in the output dataset to tag information presented from each file.
This is a follow-on to #20929. It is acceptable that this be a separate plugin rather than in ParaView proper.2021-10-31https://gitlab.kitware.com/paraview/paraview/-/issues/20771Better segfault catching2023-06-15T10:29:57-04:00Mathieu Westphal (Kitware)Better segfault catchingIt can happen that ParaView segfaults. Currently, nothing is being done.
It would be nice to have the possibility to catch these segfaults and do the following:
1. Save a state (like when server disconnect)
2. Save an actual callstack ...It can happen that ParaView segfaults. Currently, nothing is being done.
It would be nice to have the possibility to catch these segfaults and do the following:
1. Save a state (like when server disconnect)
2. Save an actual callstack to be shared with developpers
3. Automatic online sharing mechanism (not sure about this one)
Wdyt @utkarsh.ayachit ?https://gitlab.kitware.com/paraview/paraview/-/issues/20770Unlink camera should be available from render view2021-06-10T08:35:56-04:00Mathieu Westphal (Kitware)Unlink camera should be available from render viewBy right clicking on a render view, one can "Link Camera" with another view camera. A "Unlink Camera" option would be nice.
Currently it is need to go into Tools -> Manage Link to remove the link.By right clicking on a render view, one can "Link Camera" with another view camera. A "Unlink Camera" option would be nice.
Currently it is need to go into Tools -> Manage Link to remove the link.https://gitlab.kitware.com/paraview/paraview/-/issues/20749MaterialEditor: add the export materials feature2021-06-04T05:53:03-04:00Paul LafoixMaterialEditor: add the export materials featureFeature will be relevant when !4939 will be merged
When the feature will be available in VTK, add some code and UI into the pqMaterialEditor to handle exporting a material into Json :
```
/ .h
SLOT:
void exportMaterials();
// .cxx
Q...Feature will be relevant when !4939 will be merged
When the feature will be available in VTK, add some code and UI into the pqMaterialEditor to handle exporting a material into Json :
```
/ .h
SLOT:
void exportMaterials();
// .cxx
QObject::connect(this->Internals->Ui.ExportMaterials, SIGNAL(clicked()), this, SLOT(exportMaterials()));
// .ui
<item>
<widget class="QToolButton" name="ExportMaterials">
<property name="toolTip">
<string>Export materials</string>
</property>
<property name="text">
<string/>
</property>
<property name="icon">
<iconset resource="../../../Components/Resources/pqComponents.qrc">
<normaloff>:/pqWidgets/Icons/pqSave.svg</normaloff>:/pqWidgets/Icons/pqSave.svg</iconset>
</property>
</widget>
</item>
```Paul LafoixPaul Lafoixhttps://gitlab.kitware.com/paraview/paraview/-/issues/20691Fix TestResampledAMRImageSourceWithPointData2022-07-08T04:25:31-04:00Mathieu Westphal (Kitware)Fix TestResampledAMRImageSourceWithPointDataTestResampledAMRImageSourceWithPointData is currently disabled as it is failing in segfault.
It should be reenabled and fixed.
Here is a patch to reenable it and be able to build it and use it.
[pv.patch](/uploads/34764e03b00b532d2a7ff...TestResampledAMRImageSourceWithPointData is currently disabled as it is failing in segfault.
It should be reenabled and fixed.
Here is a patch to reenable it and be able to build it and use it.
[pv.patch](/uploads/34764e03b00b532d2a7ffe2070392d37/pv.patch)https://gitlab.kitware.com/paraview/paraview/-/issues/20501Usability: Point "Save Extracts" arrow down2021-03-24T09:31:21-04:00Dan LipsaUsability: Point "Save Extracts" arrow downOpen, Load State have icons that include an up arrow.
Save data, Save State have icons that include a down arrow.
Why is then Save Extracts include an (mostly) up arrow? Is it because it is aligned with the "Save Catalyst State" flask?
...Open, Load State have icons that include an up arrow.
Save data, Save State have icons that include a down arrow.
Why is then Save Extracts include an (mostly) up arrow? Is it because it is aligned with the "Save Catalyst State" flask?
In that case, maybe orient the flask and the arrow mostly down.