ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-04-08T08:58:24-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/20482Add ability to write cinema recolorable images with the extracts generator2021-04-08T08:58:24-04:00Ethan StamAdd ability to write cinema recolorable images with the extracts generator@dhr @utkarsh.ayachit
ParaView should have the capability to save recolorable images and cinema databases with recolorable images using the extract generators. Those should also be readable using the viewers available in the cinemasci ...@dhr @utkarsh.ayachit
ParaView should have the capability to save recolorable images and cinema databases with recolorable images using the extract generators. Those should also be readable using the viewers available in the cinemasci third party library.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachit2021-03-31https://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/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/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/21811Add option to select which arrays to save with CGNSWriter (in gui and python)2023-05-08T11:29:15-04:00Serge ToxopeusAdd option to select which arrays to save with CGNSWriter (in gui and python)When writing data to vtm, it is possible to select which array to write, both in the gui and through python (ChooseArraysToWrite=1 in combination with e.g. CellDataArrays=[...]). It would be nice to also have this option when writing to ...When writing data to vtm, it is possible to select which array to write, both in the gui and through python (ChooseArraysToWrite=1 in combination with e.g. CellDataArrays=[...]). It would be nice to also have this option when writing to CGNS. When writing multiple cgns files, this saves defining several PassArray filters.
(@mennodeij1)5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21619Refactor macro management2023-11-20T08:30:11-05:00Nicolas VuailleRefactor macro management## Context
With https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5872 we add a way to set up an icon to the python macro script.
For now, this icon should be manually placed alongside the macro script in the paraview setting...## Context
With https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5872 we add a way to set up an icon to the python macro script.
For now, this icon should be manually placed alongside the macro script in the paraview settings.
It will be nice to create a user interface to do that.
## Proposal
From cited MR (https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5872#note_1235277):
* ~remove the `Macros` menu and add a `Manage Macros ...` submenu in `Tools`~
* remove `edit macros` and `delete macros` submenus and add a `Edit macros` entry instead.
* this submenu would take us to a manager kind of looking like `Manage Expression` ui.
* Manager main widget would be a table view with one column for the name, one column for the logo and one for the actual macro.
* Of course button `Add new` `Remove` and `Remove all` would be integrated in the manager.
I also personnaly think that we may re-think all the `Manage XXX` tools to ensure some consistency.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/21415Make it possible to associate icons with macros2024-02-23T08:49:22-05:00Cory Quammencory.quammen@kitware.comMake it possible to associate icons with macrosRight now, macros can appear in the toolbar with just their name. Make it possible to associate an icon with them.Right now, macros can appear in the toolbar with just their name. Make it possible to associate an icon with them.5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21236Add environment variables as Favorites2022-11-10T13:09:52-05:00Cory Quammencory.quammen@kitware.comAdd environment variables as FavoritesRequest from Andy Bauer:
Make it possible to specify a `Favorite` directory which is just stored in `Settings` as an environment variable that isn't evaluated until the user requests to go to that location, e.g. $WORKDIR, $SCRATCH, $SCR...Request from Andy Bauer:
Make it possible to specify a `Favorite` directory which is just stored in `Settings` as an environment variable that isn't evaluated until the user requests to go to that location, e.g. $WORKDIR, $SCRATCH, $SCRATCH_DIR, etc., which are often used on many HPC machines as environment variables to more efficient storage other than $HOME, but are slightly different on each HPC machine. E.g. for me $WORKDIR may be /p/work/bauer on one machine but /p/gpfs/bauer on another machine.5.11 (Spring 2022)Aron HelserAron Helserhttps://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/21159MPI: enable big message support available in MPI 4.02023-06-07T20:23:52-04:00Cory Quammencory.quammen@kitware.comMPI: enable big message support available in MPI 4.0MPI 4.0 introduces API calls that specify message sizes as type `MPI_Count` rather than `int`. This promises to solve the problem of messages that have a number of items greater than the largest number representable by `int`. Update Para...MPI 4.0 introduces API calls that specify message sizes as type `MPI_Count` rather than `int`. This promises to solve the problem of messages that have a number of items greater than the largest number representable by `int`. Update ParaView to enable use of MPI 4.0 and this new API to support larger messages.Aron HelserAron Helserhttps://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/21114Comment out traces of blocks and variable names2023-01-03T11:45:02-05:00W. Alan ScottComment out traces of blocks and variable namesPlease stop explicitly setting the loading of blocks and variables in a trace. As blocks and variables are loaded by default, this is not necessary. Further, it makes the trace significantly more restricted. Here is the discourse disc...Please stop explicitly setting the loading of blocks and variables in a trace. As blocks and variables are loaded by default, this is not necessary. Further, it makes the trace significantly more restricted. Here is the discourse discussion: https://discourse.paraview.org/t/explicitly-naming-variables-and-blocks-in-trace/8515.
So, for the trace of the load of can.exo, change
```
canex2 = IOSSReader(registrationName='can.ex2', FileName=['/Applications/PV/can.ex2'])
canex2.ElementBlocks = ['block_1', 'block_2']
canex2.NodeBlockFields = ['accl', 'displ', 'vel']
canex2.ElementBlockFields = ['eqps']
```
to
```
canex2 = IOSSReader(registrationName='can.ex2', FileName=['/Applications/PV/can.ex2'])
# canex2.ElementBlocks = ['block_1', 'block_2']
# canex2.NodeBlockFields = ['accl', 'displ', 'vel']
# canex2.ElementBlockFields = ['eqps']
```5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://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/20929Need a repeatable file property2021-10-05T11:42:14-04:00David ThompsonNeed a repeatable file propertyWe have a customer who needs a pqPropertyWidget that displays a list-view whose rows are file-property widgets (i.e., an editable path with a "..." button for browsing the filesystem). The server-side StringVectorProperty will be extensi...We have a customer who needs a pqPropertyWidget that displays a list-view whose rows are file-property widgets (i.e., an editable path with a "..." button for browsing the filesystem). The server-side StringVectorProperty will be extensible, so the property-widget should have the typical "+/-/x" buttons to the right of the list view. The StringVectorProperty will have a FileListDomain.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20798Add animation stride2021-11-18T11:45:09-05:00Timothee ChabatAdd animation strideIt is sometimes interesting to control how many frames we want to display in SnapToTimesteps and Sequence mode, and to be able to change the granularity of the display.
See MR: https://gitlab.kitware.com/paraview/paraview/-/merge_reques...It is sometimes interesting to control how many frames we want to display in SnapToTimesteps and Sequence mode, and to be able to change the granularity of the display.
See MR: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4987Timothee ChabatTimothee Chabathttps://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.