ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-23T13:49:00-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/17666XML vt* files with timesteps cannot be written fully from paraview2021-03-23T13:49:00-04:00Mathieu Westphal (Kitware)XML vt* files with timesteps cannot be written fully from paraviewvt* XML format supports timesteps in a single file.
They can be read correctly by paraview
But cannot be written as a single file with all timesteps informations:
How to reproduce :
* Run ParaView
* Open [outfile.vtp](/uploads/e4c3c29...vt* XML format supports timesteps in a single file.
They can be read correctly by paraview
But cannot be written as a single file with all timesteps informations:
How to reproduce :
* Run ParaView
* Open [outfile.vtp](/uploads/e4c3c29b9dbfd27f01a6736ed3ef7930/outfile.vtp), two timesteps are present
* Save Data as a .vtp file
* Delete first reader
* Open previously saved file
* No timesteps present
Of course, one can save as a file series as a work around.https://gitlab.kitware.com/paraview/paraview/-/issues/15739X-, Y-, Z-axis rotation lock does not work with multi-rotation tool2020-05-06T01:35:09-04:00Kitware RobotX-, Y-, Z-axis rotation lock does not work with multi-rotation tool**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15739). Further discussion may take place here.**
---
Introduced with ParaView 4.4, you can hold down the x, y, or z button whil...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15739). Further discussion may take place here.**
---
Introduced with ParaView 4.4, you can hold down the x, y, or z button while dragging to lock the camera rotation around the respective axis of the data. This works fine with the default "Rotate" camera manipulator, but does not work with the "Multi-Rotate" camera manipulator. I often replace the rotate tool with the multi-rotate tool when the right mouse button is not as accessible as the left.https://gitlab.kitware.com/paraview/paraview/-/issues/15403Writer of FieldData in a vtkTable2021-03-23T11:57:13-04:00Kitware RobotWriter of FieldData in a vtkTable**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15403). Further discussion may take place here.**
---
It would be useful to have the possibility to export field data of tables....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15403). Further discussion may take place here.**
---
It would be useful to have the possibility to export field data of tables. Currently, the writer doesn't allow to specify the association field, so only the row values can be exported to the csv file (see also http://markmail.org/message/wjqrehocmqc6degh)https://gitlab.kitware.com/paraview/paraview/-/issues/13457When slicing preserve input data type in output (for rectilinear input)2020-05-04T05:46:17-04:00Kitware RobotWhen slicing preserve input data type in output (for rectilinear input)**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13457). Further discussion may take place here.**
---
Currently when a user apply slice filter (on axis aligned plane) on a rect...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13457). Further discussion may take place here.**
---
Currently when a user apply slice filter (on axis aligned plane) on a rectilinear input data type, it generates polygons. We need to preserve the input data type in output.https://gitlab.kitware.com/paraview/paraview/-/issues/20350VTPD reader doesn’t allow selecting which fields to be read in.2021-03-24T08:44:50-04:00Utkarsh AyachitVTPD reader doesn’t allow selecting which fields to be read in.The VTPD reader doesn’t allow selecting which fields to be read in.
see [discourse](https://discourse.paraview.org/t/catalyst-v5-9-issues/5882)The VTPD reader doesn’t allow selecting which fields to be read in.
see [discourse](https://discourse.paraview.org/t/catalyst-v5-9-issues/5882)https://gitlab.kitware.com/paraview/paraview/-/issues/19869vtkSortedTableStreamer: reimplement using DIY2021-03-24T07:34:37-04:00Utkarsh AyachitvtkSortedTableStreamer: reimplement using DIY`diy::sort` should help us simplify implementation in `vtkSortedTableStreamer`.`diy::sort` should help us simplify implementation in `vtkSortedTableStreamer`.https://gitlab.kitware.com/paraview/paraview/-/issues/20429vtkSortedTableStreamer: avoid merging blocks2021-03-24T08:55:30-04:00Utkarsh AyachitvtkSortedTableStreamer: avoid merging blocksvtkSortedTableStreamer merges blocks into a single table. That was okay in the past when the spreadsheet view only showed data from one block at a time. Now that support showing all blocks by default, that can cause considerable slow dow...vtkSortedTableStreamer merges blocks into a single table. That was okay in the past when the spreadsheet view only showed data from one block at a time. Now that support showing all blocks by default, that can cause considerable slow down when dealing with large data. We should change the implementation to avoid that.
cc: @boonth, I think this explains the slowdown you were seeing with spreadsheet view.https://gitlab.kitware.com/paraview/paraview/-/issues/20094vtkPythonView parameters like vtkPythonProgrammableFilter2024-03-08T05:40:53-05:00Felipe BordeuvtkPythonView parameters like vtkPythonProgrammableFilterhi to all,
I'm working in a custom python view. And I would like to have some options exposed to the final user to control the python view in the same way the "SetParameter" of the vtkPythonProgrammableFilter.
The vktPythonProgrammabl...hi to all,
I'm working in a custom python view. And I would like to have some options exposed to the final user to control the python view in the same way the "SetParameter" of the vtkPythonProgrammableFilter.
The vktPythonProgrammableFilter have a series of member functions: SetParameter, AddParameter, ClearParameter... (https://kitware.github.io/paraview-docs/latest/cxx/classvtkPythonProgrammableFilter.html) to set parameter that can be used at execution time by the script. The main idea is to use this feature in the xml plugin to add GUI entries for the end users.
Is this possible with the vtkPythonView class, and is this something useful for the community??
Thanks
Felipehttps://gitlab.kitware.com/paraview/paraview/-/issues/18409VTKPythonAlgorithm writers cannot use same extension as any other ParaView wr...2021-03-23T19:06:43-04:00Bane SullivanVTKPythonAlgorithm writers cannot use same extension as any other ParaView writersWhen creating a `VTKPythonAlgorithmBase` subclass writer algorithm, you cannot use an extension that a ParaView (or another `VTKPythonAlgorithmBase`) writer already uses. For example, I cannot use the `txt` extension because the `DataSet...When creating a `VTKPythonAlgorithmBase` subclass writer algorithm, you cannot use an extension that a ParaView (or another `VTKPythonAlgorithmBase`) writer already uses. For example, I cannot use the `txt` extension because the `DataSetCSVWriter` already has that extension.
```python
@smproxy.writer(extensions="txt", file_description="Some custom writer", support_reload=False)
@smproperty.input(name="Input", port_index=0)
@smdomain.datatype(dataTypes=["vtkDataSet"], composite_data_supported=True)
class PVWriterPlugin(VTKPythonAlgorithmBase):
...
```
If I try to use a writer with that extension it defaults to the `DataSetCSVWriter`:
I choose my custom writer plugin via the pop-up dialog after File->Save Data...:
![Screen_Shot_2018-09-03_at_7.15.12_PM](/uploads/46d0ff73f7d7666c00e0c57892ad7edc/Screen_Shot_2018-09-03_at_7.15.12_PM.png)
After clicking Okay, I am prompted with the configuration options for the `DataSetCSVWriter`:
![Screen_Shot_2018-09-03_at_7.15.26_PM](/uploads/3d9e557237ffeb979fe85bc41d303824/Screen_Shot_2018-09-03_at_7.15.26_PM.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19347vtkPVGridAxes3DRepresentation: avoid calling MarkModified in SetPosition/SetS...2021-03-24T05:51:10-04:00Utkarsh AyachitvtkPVGridAxes3DRepresentation: avoid calling MarkModified in SetPosition/SetScaleMarkModified should not be called unless absolutely necessary since it causes pipeline updates. vtkPVGridAxes3DRepresentation can be easily re-worked to avoid that.MarkModified should not be called unless absolutely necessary since it causes pipeline updates. vtkPVGridAxes3DRepresentation can be easily re-worked to avoid that.https://gitlab.kitware.com/paraview/paraview/-/issues/20176vtkMultiProcessControllerHelper does not support vtkRectilinearGrid2021-03-24T08:30:32-04:00Antonio MemmolovtkMultiProcessControllerHelper does not support vtkRectilinearGridHi all,
This is a followup of the issue
https://discourse.paraview.org/t/bug-live-visualization-of-vtkrectilineargrid-doesnt-work/5140/7
With this, I would like to request to add support to vtkRectilinearGrid in vtkMultiProcessControll...Hi all,
This is a followup of the issue
https://discourse.paraview.org/t/bug-live-visualization-of-vtkrectilineargrid-doesnt-work/5140/7
With this, I would like to request to add support to vtkRectilinearGrid in vtkMultiProcessControllerHelper.
Thanks
Antoniohttps://gitlab.kitware.com/paraview/paraview/-/issues/19098vtkDIYAggregateDataSetFilter needs to not require MPI2021-03-24T07:03:48-04:00Utkarsh AyachitvtkDIYAggregateDataSetFilter needs to not require MPI`vtkDIYAggregateDataSetFilter` currently explicitly requires MPI. We need to rework it to not use MPI. `FiltersParallelDIY2` module is soon to be enabled even on non-mpi builds.
cc: @acbauer`vtkDIYAggregateDataSetFilter` currently explicitly requires MPI. We need to rework it to not use MPI. `FiltersParallelDIY2` module is soon to be enabled even on non-mpi builds.
cc: @acbauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/20427vtkBlockDeliveryPreprocessor needs to be removed2021-03-24T08:56:01-04:00Utkarsh AyachitvtkBlockDeliveryPreprocessor needs to be removedvtkBlockDeliveryPreprocessor needs to be removed. vtkDataTabulator may be a good replacement for its use in vtkChartRepresentation.vtkBlockDeliveryPreprocessor needs to be removed. vtkDataTabulator may be a good replacement for its use in vtkChartRepresentation.https://gitlab.kitware.com/paraview/paraview/-/issues/19510vtkBlockColors is not available when representing a multiblock dataset in Poi...2021-03-24T06:35:53-04:00Mathieu Westphal (Kitware)vtkBlockColors is not available when representing a multiblock dataset in PointGaussian RepresentationvtkBlockColors is not available when representing a multiblock dataset in PointGaussian Representation
Steps to reproduce :
* Open can.ex2
* Color by vtkBlockColors
* Switch to PointGaussian
* vtkBlockColors appears with a ? and is...vtkBlockColors is not available when representing a multiblock dataset in PointGaussian Representation
Steps to reproduce :
* Open can.ex2
* Color by vtkBlockColors
* Switch to PointGaussian
* vtkBlockColors appears with a ? and is not available anymorehttps://gitlab.kitware.com/paraview/paraview/-/issues/20475Vector variable not identified as a vector by calculator filter2021-06-16T08:17:31-04:00JPCVector variable not identified as a vector by calculator filterA strange behaviour is identified with CGNS files written by ANSYS Fluent 2019 for planar problems, on ParaView 5.9.0 Windows 10 64 bits.
1. Open a CGNS file with planar geometry and nodal vector (e.g., velocity... in fact VelocityX and ...A strange behaviour is identified with CGNS files written by ANSYS Fluent 2019 for planar problems, on ParaView 5.9.0 Windows 10 64 bits.
1. Open a CGNS file with planar geometry and nodal vector (e.g., velocity... in fact VelocityX and VelocityY, but no VelocityZ in the solver).
2. Velocity is correctly identified as a 2D vector and a scalar plot can be produced. From the dropdown next to variable selection, you can select _Magnitude_, _VelocityX_ and _VelocityY_ to plot.
3. Create a _Calculator_ filter. Although ParaView identified this variable as a vector, it is **not listed on the _Vectors_ drop down**. The two separate variables are listed in the _Scalars_ dropdown, as **Velocity_VelocityX** and **Velocity_VelocityY**.
Although the components may be listed in the scalar section, the _Velocity_ variable should be available as a vector. Example file is provided.\
[Velocity.cgns](/uploads/2dc517b8a1d57e81c2f4c726f01b695b/Velocity.cgns)
The same happens with a cell-valued velocity file.
On top of this, if the _Attribute Type_ is changed to _Cell Data_, a warning is issued by the user interface when trying to drop down the _Vectors_ button (see #20474).https://gitlab.kitware.com/paraview/paraview/-/issues/20080Use Data Assembly for display properties2021-08-25T08:17:15-04:00Utkarsh AyachitUse Data Assembly for display propertiesWhen dealing with PartionedDataSetCollection (the output produced by IossReader), the composite-id used by ParaView/VTK for setting up things like color properties etc. no longer make sense esp. in parallel where they may be different on...When dealing with PartionedDataSetCollection (the output produced by IossReader), the composite-id used by ParaView/VTK for setting up things like color properties etc. no longer make sense esp. in parallel where they may be different on different ranks since the hierarchical structure is not expected to be consistent across ranks.
This requires that we update all display properties etc. i.e. the stuff we currently setup in Multiblock Inspector to use Data Assembly instead when dealing with these types of datasets.https://gitlab.kitware.com/paraview/paraview/-/issues/19761Use a percentile based color distribution2020-03-13T04:11:31-04:00Sebastien JourdainUse a percentile based color distributionThe idea of such (new) feature would be to apply a color mapping that would be based on a percentile distribution.
For example, currently we can remap a color preset to a log scale thanks to the available color range.
In the present ca...The idea of such (new) feature would be to apply a color mapping that would be based on a percentile distribution.
For example, currently we can remap a color preset to a log scale thanks to the available color range.
In the present case, we'll need to compute the percentile distribution of a given field and then use the distribution to resample (i.e. quartile) the given preset color distribution.
What we see with the scalar bar with the log scale is a good example of what could be done when respecting the data distribution.
![Screen_Shot_2020-03-12_at_14.59.51](/uploads/dc16f81479aff7325a1ff9e482f15b1c/Screen_Shot_2020-03-12_at_14.59.51.png) ![Screen_Shot_2020-03-12_at_15.00.18](/uploads/4869e6bc6ebd3266fc62d9749302aa63/Screen_Shot_2020-03-12_at_15.00.18.png)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.https://gitlab.kitware.com/paraview/paraview/-/issues/20500Usability: Change Properties to Filter2021-03-24T09:34:45-04:00Dan LipsaUsability: Change Properties to FilterInside the Properties Tab you have tree groups of properties:
Properties, Display and View. I propose that the Properties group be renamed to Filter, as those are filter properties.
This way, you will have the Properties Tab that has t...Inside the Properties Tab you have tree groups of properties:
Properties, Display and View. I propose that the Properties group be renamed to Filter, as those are filter properties.
This way, you will have the Properties Tab that has three groups of properties: Filter, Display and View.
@cory.quammen @utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/9372Usability : icons for scalar, vector, etc on Information Tab2023-06-15T12:54:41-04:00Kitware RobotUsability : icons for scalar, vector, etc on Information Tab**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9372). Further discussion may take place here.**
---
To determine if an array is a "scalar" array or "vector" array, one looks a...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9372). Further discussion may take place here.**
---
To determine if an array is a "scalar" array or "vector" array, one looks at information tab and sees if one or more ranges are listed. Adding an icon, which suggests a scalar or vector quantity to the left would make it more intuitive.