ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-06-15T20:13:39-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/15208Bug: Warning with Reset Camera to Normal2023-06-15T20:13:39-04:00Kitware RobotBug: Warning with Reset Camera to Normal**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15208). Further discussion may take place here.**
---
A particular case return a warning:
- Create a Sphere
- Apply a Slice filt...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15208). Further discussion may take place here.**
---
A particular case return a warning:
- Create a Sphere
- Apply a Slice filter with normal (0,1,0)
- Set view direction to +Z (in the toolbar "Camera Controls")
- Click on "Reset Camera To Normal" (in the property panel)https://gitlab.kitware.com/paraview/paraview/-/issues/15207Bug: Wrong selection of nodes on quadratic mesh2017-12-04T12:46:52-05:00Kitware RobotBug: Wrong selection of nodes on quadratic mesh**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15207). Further discussion may take place here.**
---
Attached test_selection_on_nodes_0_0.vtu file contains quaratic mesh, sele...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15207). Further discussion may take place here.**
---
Attached test_selection_on_nodes_0_0.vtu file contains quaratic mesh, selection of the nodes on this mesh is wrong.
To test it click on "select points on" and draw a rectangle around some nodes on a cylindrical face..
The selected nodes are not those wanted, but are scattered in the mesh.https://gitlab.kitware.com/paraview/paraview/-/issues/15183Imp: Add "Use Cell Centers" option in the Glyph filter2017-12-04T12:46:53-05:00Kitware RobotImp: Add "Use Cell Centers" option in the Glyph filter**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15183). Further discussion may take place here.**
---
“Auto convert properties” allows to apply filters which requires node fiel...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15183). Further discussion may take place here.**
---
“Auto convert properties” allows to apply filters which requires node field on a cell field, auto applying the filter “cell data to point data”. However, this filter computes mean values on the nodes. The resulting field data is an approximation of the initial field, with different min and max values. In order to keep the initial values, we must use the filter “cell centers”. This can be done for the filter glyph, but not for the filter contour for which the result of “cell centers” cannot be used as an input. That’s why we need to be able to set to use “cell centers” when the result can be used for a filter but still use “cell data to point data” otherwise, at least for the Glyph filter.https://gitlab.kitware.com/paraview/paraview/-/issues/15173Imp: Add UI control to activate/deactivate 3D stereo and to select the stereo...2017-12-04T12:46:53-05:00Kitware RobotImp: Add UI control to activate/deactivate 3D stereo and to select the stereo mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15173). Further discussion may take place here.**
---
Currently, 3D view can be changed to stereo mode only at ParaView start-up...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15173). Further discussion may take place here.**
---
Currently, 3D view can be changed to stereo mode only at ParaView start-up with the following options:
--stereo:--stereo-type=SplitViewportHorizontal
or by some python code:
GetRenderView().StereoRender=1
GetRenderView().StereoType="SplitViewportHorizontal"
To be more user friendly, we need an icon in the top of 3D views to be able to activate/deactivate 3D stereo and to select which stereo mode to use in a drop-down list.https://gitlab.kitware.com/paraview/paraview/-/issues/15172Imp: Generating annotations corresponding to discrete colours2017-12-04T12:46:53-05:00Kitware RobotImp: Generating annotations corresponding to discrete colours**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15172). Further discussion may take place here.**
---
When we plot with discrete colours (5 or 6 colours in order to see the dis...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15172). Further discussion may take place here.**
---
When we plot with discrete colours (5 or 6 colours in order to see the distribution of values better), we want to know the range corresponding to each colour.
In Paraview, what is displayed are rounded values and not the bounds corresponding to each colour. Therefore, it is impossible to interpret the visualization.
For instance:
- Load the attached file TempField_4_0.vtu
- Display the scalar bar
- Edit the bar in order to display 6 discrete colours
=> The labels are : 0, 20, 40, 60, 75
Furthermore, if we change the number of labels to 7, we still have only 5 labels displayed. We should have labels: 0, 12.5, 25, 37.5, 50, 62.5, 75.https://gitlab.kitware.com/paraview/paraview/-/issues/15171Imp: Place the camera in front of the plane widget2017-10-31T04:56:02-04:00Kitware RobotImp: Place the camera in front of the plane widget**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15171). Further discussion may take place here.**
---
In order to better manipulate the result of the filters (slice filter for ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15171). Further discussion may take place here.**
---
In order to better manipulate the result of the filters (slice filter for example), it would be useful to place camera on the front of the plane widget.https://gitlab.kitware.com/paraview/paraview/-/issues/15170Imp: Be able to drag and drop the legend of plot charts2017-12-04T12:46:53-05:00Kitware RobotImp: Be able to drag and drop the legend of plot charts**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15170). Further discussion may take place here.**
---
In a 3D view, we can drag and drop the colour legend to change its positio...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15170). Further discussion may take place here.**
---
In a 3D view, we can drag and drop the colour legend to change its position.
We want to be able to do the same for the legend of plot charts. https://gitlab.kitware.com/paraview/paraview/-/issues/15147Imp: In the bar chart, display the ticks limiting each bar by default2021-03-23T11:52:59-04:00Kitware RobotImp: In the bar chart, display the ticks limiting each bar by default**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15147). Further discussion may take place here.**
---
When calling the filter histogram, a bar chart view is created with rounde...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15147). Further discussion may take place here.**
---
When calling the filter histogram, a bar chart view is created with rounded values in the X-axis. In order to know a bar correspond to which interval, the X-axis must have values corresponding to the interval of computation of each bar. This can be obtained via:
- View properties
- Bottom axis layout
- Specify axis labels explicitly
- Generate:
- From: min value of the field
- To: max value of the field
- Steps: number of bars + 1
This should be the default behaviour so as to understand what each bar means. https://gitlab.kitware.com/paraview/paraview/-/issues/15146Imp: Be able to select points in python: in simple.py, create SelectPoints li...2017-12-04T12:46:54-05:00Kitware RobotImp: Be able to select points in python: in simple.py, create SelectPoints like SelectCells and refactor the code**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15146). Further discussion may take place here.**
---
To be able to make some selections in Python, there is already a SelectCel...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15146). Further discussion may take place here.**
---
To be able to make some selections in Python, there is already a SelectCells() function defined in simple.py.
It would be useful to have the same function for points. https://gitlab.kitware.com/paraview/paraview/-/issues/15144Imp: In the color bar, be able to deactivate sub-tick marks2017-12-04T12:46:54-05:00Kitware RobotImp: In the color bar, be able to deactivate sub-tick marks**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15144). Further discussion may take place here.**
---
In the colour bar properties, one can deactivate all ticks, but it would b...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15144). Further discussion may take place here.**
---
In the colour bar properties, one can deactivate all ticks, but it would be useful to deactivate only the sub-tick marks.https://gitlab.kitware.com/paraview/paraview/-/issues/15142Imp: Data reloading from a file and pipeline updating and views with the new ...2020-05-27T15:44:12-04:00Kitware RobotImp: Data reloading from a file and pipeline updating and views with the new values**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15142). Further discussion may take place here.**
---
The feature would allow to reload the data from a file (a table file in cs...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15142). Further discussion may take place here.**
---
The feature would allow to reload the data from a file (a table file in csv, or a field in other file formats), which has changed since its previous load, so that the charts and the 3D views using this data are updated with the updated source.
Expected work:
- In GUI, provide an icon to reload the file.
- In Python, provide a function to update in batch. For instance reader.Update(), where reader is the result of a call to CSVReader().https://gitlab.kitware.com/paraview/paraview/-/issues/15141Imp: Improve the 3D view manipulation for long objects2017-12-04T12:46:54-05:00Kitware RobotImp: Improve the 3D view manipulation for long objects**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15141). Further discussion may take place here.**
---
For objects which have a dimension much bigger than the others, the view m...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15141). Further discussion may take place here.**
---
For objects which have a dimension much bigger than the others, the view manipulation is not easy, because the rotation is too fast.
As an example, create a cylinder source with the properties:
- Resolution: 36
- Height: 200
- Radius: 0.5
and make several zooms and rotations to see the problems.https://gitlab.kitware.com/paraview/paraview/-/issues/15140Imp: Use the mouse cursor as the center of zoom2020-05-27T15:41:48-04:00Kitware RobotImp: Use the mouse cursor as the center of zoom**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15140). Further discussion may take place here.**
---
Default PV interactor should have a mode which allow the user to zoom at t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15140). Further discussion may take place here.**
---
Default PV interactor should have a mode which allow the user to zoom at the current position of the mouse cursor.https://gitlab.kitware.com/paraview/paraview/-/issues/15103Major performance issue on GUI side of ParaView2020-05-06T03:15:47-04:00Kitware RobotMajor performance issue on GUI side of ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15103). Further discussion may take place here.**
---
In the attached archive MKWReader.tar.gz a dummy small reader plug-in to h...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15103). Further discussion may take place here.**
---
In the attached archive MKWReader.tar.gz a dummy small reader plug-in to highlight the problem of performance we meet in our reader plug-in.
After investigation, the problem of performance we meet is client side when the number of entries in a tree is ~4000 elements (instances of linked pqTreeWidgetItemObject).
A brief description of this small Plugin: it reads a dummy file with *.mkw extension containing an unsigned integer; this file (in the Doc directory) is called OneIntegerFile.mkw.
The example reader generates a server side unstructured grid containing just one cell (to show that the server side is particularly light ) and a field array called "FakeField" containing a single component, the unique value of the field is specified on the client side. On the client side, there is a list of <nb_of_value_in_mkw_file> pqTreeWidgetItemObject objects in the tree view "Select a value for your field on VTK_QUAD".
THE PROBLEM: the ellapsed time needed to have a rendering is quite big (the moment between we click on "Apply" and the time to have the rendering of the single cell):
1000 items in browser : ~3 s
2000 items in browser : ~12 s
4000 items in browser : ~44 s
Another problem is the reactivity of the tree with 4000 items. Each click in the tree takes 1 second. We remark that all the time is spent on the Client-side, more especially in the GUI part of paraview.
We need thousands of items in our real reader plug-in, consequently such amount of time is blocking for us.https://gitlab.kitware.com/paraview/paraview/-/issues/15009Naming conflict with gtk package2017-12-04T12:46:56-05:00Kitware RobotNaming conflict with gtk package**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15009). Further discussion may take place here.**
---
In Paraview 4.1, there is a python module called gtk:
[PARAVIEW_INSTALL...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15009). Further discussion may take place here.**
---
In Paraview 4.1, there is a python module called gtk:
[PARAVIEW_INSTALL_DIR]/lib/paraview-4.1/site-packages/vtk/gtk
Problem is that this is also the name of standard python package.
Thus, any software using the gtk module may find the ParaView module instead of the standard one.
Is it possible to rename the gtk package in the Paraview to avoid naming conflict?https://gitlab.kitware.com/paraview/paraview/-/issues/15007Problem with the Magnitude calculation for a low values2017-12-04T12:46:56-05:00Kitware RobotProblem with the Magnitude calculation for a low values**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15007). Further discussion may take place here.**
---
Open attached file RES_DEPL_0_0.vtu
For the field RES_DEPL, the 3 compone...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15007). Further discussion may take place here.**
---
Open attached file RES_DEPL_0_0.vtu
For the field RES_DEPL, the 3 components DX, DY and DZ are well filled with values but the magnitude is not computed correctly for all the cells.
This can be seen by coloring the mesh according to each of these components (DX, DY, DZ, Magnitude).
The RES_DEPL_Magnituge.png picture demostrates the problem.
Note that the values are particularly low for DX and DY ~ 1e-17 in average, up to 1e-39 in some cases.https://gitlab.kitware.com/paraview/paraview/-/issues/14987The presentation automatically updated in case visualization of the 2 fileds ...2020-05-26T22:06:14-04:00Kitware RobotThe presentation automatically updated in case visualization of the 2 fileds with the same names in the different views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14987). Further discussion may take place here.**
---
1) Open attached files file1.vtm and file2.vtm (from the files.tar.gz arch...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14987). Further discussion may take place here.**
---
1) Open attached files file1.vtm and file2.vtm (from the files.tar.gz archive)
2) Display and color first presentation by the "depl___DEPL" data array and "DX" component, show Color Map
3) Split view and create new Render View
4) Display and color second presentation by the "depl___DEPL" data array and "DY" component, in the second view, show Color Map
5) Activate the first view and select first presentation in the pipeline browser
6) Select the "DZ" as a Coloring component.
=> In the result a both view are updated, but expected updating only a first view.
In case if fields have a different names, the automatic update of the second view is not done.
The possibility to compare two components of the same field could be useful.https://gitlab.kitware.com/paraview/paraview/-/issues/14980Scalar bar legend labels have not reliable behaviour for display2017-12-04T12:46:57-05:00Kitware RobotScalar bar legend labels have not reliable behaviour for display**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14980). Further discussion may take place here.**
---
In the "Color map editor", there is a dialog box "Edit color legend parame...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14980). Further discussion may take place here.**
---
In the "Color map editor", there is a dialog box "Edit color legend parameters".
It allows to choose the number of labels that you want to show along the scalar bar legend by filling the field "Number Of Labels".
But the number of the labels asked for the displaying doesn't correspond to the real number of the displayed labels.
The behaviour is similar to the following:
Number Of Labels = 1 --> 0 label is displayed
Number Of Labels = 2 --> 1 label is displayed
Number Of Labels = 3 to 5 --> 2 labels are displayed
Number Of Labels = 6 to 14 --> 5 labels are displayed
Number Of Labels = 15 to 23 --> 14 labels are displayed
Number Of Labels = 24 to 29 --> 23 labels are displayed
Number Of Labels = 30 to 59 --> 29 labels are displayed
Number Of Labels => 60 OR = 0 --> 59 labels are displayed
Could it be possible that the number of labels asked is exactly the number of labels displayed ?5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/14948Plot Matrix View doesn't create/show selections properly when plotting cell d...2017-12-04T12:46:58-05:00Kitware RobotPlot Matrix View doesn't create/show selections properly when plotting cell data.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14948). Further discussion may take place here.**
---
+ Open attached dataset (it's a small wavelet with data only on cells)
+ ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14948). Further discussion may take place here.**
---
+ Open attached dataset (it's a small wavelet with data only on cells)
+ Apply Plot Data filter and show the result in Render View and Plot Matrix View.
In the scatter plot, each point corresponds to cell in input dataset, since all attributes are on cells.
Issue 1:
Now select a point in the Plot Matrix view, instead of seeing a selected "cell" in the Render View, we see a point.
Issue 2:
Select a single cell in the Render View (you will have to swicth the representation type to Surface for that). Instead of seeing a single point highlighted in the Plot Matrix view, we see several points selected (image attached).
https://gitlab.kitware.com/paraview/paraview/-/issues/14947Selections in line plots don't work properly when cell-based selections are m...2020-05-06T04:44:37-04:00Kitware RobotSelections in line plots don't work properly when cell-based selections are made in render view**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14947). Further discussion may take place here.**
---
+ Wavelet, Apply
+ Plot Data, Apply
+ Show output of Plot Data in both t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14947). Further discussion may take place here.**
---
+ Wavelet, Apply
+ Plot Data, Apply
+ Show output of Plot Data in both the "Render View" and "Line Chart View".
+ Switch to show surface in Render View so you can make selections on it.
If you select points in Render View, they show up properly in the Line Chart View. If you select cells, however, the Chart View doesn't show correct selection.