ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-05-06T05:05:17-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/14854Bug with the shifted selection of the nodes2020-05-06T05:05:17-04:00Kitware RobotBug with the shifted selection of the nodes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14854). Further discussion may take place here.**
---
When selecting points on a mesh, the displayed selection does not
corresp...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14854). Further discussion may take place here.**
---
When selecting points on a mesh, the displayed selection does not
correspond exactly to the position of the node of the mesh. The attached
image illustrates this situation where the pink points are shifted from
the nodes.https://gitlab.kitware.com/paraview/paraview/-/issues/14731After relaunching a python script, the last scalar bar stays displayed when h...2020-05-06T05:16:49-04:00Kitware RobotAfter relaunching a python script, the last scalar bar stays displayed when hiding the representation**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14731). Further discussion may take place here.**
---
Launch the script playing_with_scalar_bar_paraview.py (attached).
In the ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14731). Further discussion may take place here.**
---
Launch the script playing_with_scalar_bar_paraview.py (attached).
In the Pipeline Browser, click on the eye left of MeshQuality1.
=> The representation and the scalar bar are hidden.
Re-launch the script.
Click on the eye left of MeshQuality2.
=> The representation is hidden, but the scalar is still displayed.https://gitlab.kitware.com/paraview/paraview/-/issues/15670Imp: Add possibility to specify exact size of the Tick labels of the Color Map2020-05-06T16:08:18-04:00Kitware RobotImp: Add possibility to specify exact size of the Tick labels of the Color Map**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15670). Further discussion may take place here.**
---
Currently in the paraview application there is no possibility to specify e...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15670). Further discussion may take place here.**
---
Currently in the paraview application there is no possibility to specify exact size of the Tick labels of the Color Map. The size of the Tick labels is computed automatically on the base of the size of the render window, size and orientation of the Color Map … etc.
Is it possible to implement feature which allows specify exact size of the Tick labels?https://gitlab.kitware.com/paraview/paraview/-/issues/15685Box Chart View is not showing the box chart2020-05-08T16:25:12-04:00Kitware RobotBox Chart View is not showing the box chart**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15685). Further discussion may take place here.**
---
In the attachement there's a datafile mysample.csv (a 100 integers from 1 ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15685). Further discussion may take place here.**
---
In the attachement there's a datafile mysample.csv (a 100 integers from 1 to 100) to illustrate the question below.
The workflow is:
- open the csv file;
- open a new view and choose box chart view;
- click on the eye of the csv file to display it into that box chart view.
You get a box chart which is not what you expect from a box chart (a box with an inside line equal to the second quartile or the median (here 50), its bottom and its top equal to the first quartile (here 25) and the third quartile (here 75) and a whisker. You can actually see what you expect with the Compute quartiles filter.
But the question is: what does the box chart view represent after the workflow above?
https://gitlab.kitware.com/paraview/paraview/-/issues/15370Single node hot spot in temperature field2020-05-12T21:42:15-04:00Kitware RobotSingle node hot spot in temperature field**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15370). Further discussion may take place here.**
---
I tried syrthes thermal analysis earlier with version of paraview 3.12 and...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15370). Further discussion may take place here.**
---
I tried syrthes thermal analysis earlier with version of paraview 3.12 and everything was working. When I started using paraview in version 4.2 or 4.3 I get from the same results file very high peak of temperature (always 4e+22). this peak is allways on node that is on edge of geometry. I attached two files, one with smooth results from praview 3.12 and second from 4.3 with nodal hot spot.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/14893Strange behavior when visualizing a field2020-05-27T15:08:37-04:00Kitware RobotStrange behavior when visualizing a field**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14893). Further discussion may take place here.**
---
Load the binary file from the meppen4_proj_sb_bin.tgz archive
First sce...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14893). Further discussion may take place here.**
---
Load the binary file from the meppen4_proj_sb_bin.tgz archive
First scenario:
- Visualize the field ECRO.
- Display the color legend and go to the end of the animation.
=> The visualization is correct.
- Rescale to data range.
=> The visualization is incorrect, see attached wrong_prs.png
Second scenario:
- Visualize the field ECRO and go to the end of the animation.
- Visualize the field CONT.
- Visualize the field ECRO
=> The visualization is incorrect.
About data to reproduce a problem: unfortunately files to reproduce a problem too big and I can’t attach files in the mantis. To obtain these files please send request to the bugmaster.salome@opencascade.com and I’ll send you link and password to the FTP server, or alternatively I can upload these files to the any provided server.https://gitlab.kitware.com/paraview/paraview/-/issues/15275Calculator filter grants forbidden calculation and do not prevent errors2020-05-27T15:37:37-04:00Kitware RobotCalculator filter grants forbidden calculation and do not prevent errors**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15275). Further discussion may take place here.**
---
When using the calculator filter in ParaView, it has been noticed 2 issues...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15275). Further discussion may take place here.**
---
When using the calculator filter in ParaView, it has been noticed 2 issues :
- forbidden calculations as /0, sqrt(negative number), ln(0)... return 0 value as a result which is not intuitive;
- if we fill in a wrong formula, for instance cossin(my_field) or my_field**2, there is no warning or error message display. The "Result" field is simply not available which is, once more, not really intuitive.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/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/15414Bug with cut-lines (plotOverLine): wrong element found when searching for the...2020-06-09T20:15:31-04:00Kitware RobotBug with cut-lines (plotOverLine): wrong element found when searching for the point inside**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15414). Further discussion may take place here.**
---
I found a bug in Paraview, any version (3 and 4 tested) when making a cut-...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15414). Further discussion may take place here.**
---
I found a bug in Paraview, any version (3 and 4 tested) when making a cut-line (PlotOverLine filter in ParaView 4). Details and data (in french only) are available on code_Carmel website : http://code-carmel.univ-lille1.fr/fr/node/286.
Summarizing, ParaView may not find the element which contains a given point (in the cut-line). And thus give a wrong result, significant sometimes. This is not due to a lack of accuracy. It occurs with MED (SALOME and PARAVIS module) and VTK file formats (ParaView release), the only one tested.
A bug ticket was also created on the SALOME site (http://salome-platform.org).
Best regards,
Loïc Chevallier.https://gitlab.kitware.com/paraview/paraview/-/issues/15682Extract Bag Plot filter does not have unitary tests2020-06-09T21:44:58-04:00Kitware RobotExtract Bag Plot filter does not have unitary tests**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15682). Further discussion may take place here.**
---
According to the Kitware gitlab, Extract Bag Plot filter does not have uni...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15682). Further discussion may take place here.**
---
According to the Kitware gitlab, Extract Bag Plot filter does not have unitary tests. The only existing test is an integration test described here: https://gitlab.kitware.com/paraview/paraview/blob/master/Applications/ParaView/Testing/XML/FunctionalBagPlots.xml.
According to the user, the data used in that test are not appropriate to test the actual algorithm (sinewaves.csv): the white noise, without temporal covariance, is not consistent to find outliers. Thus, it does not represent a practical case of physics simulation outcome (no regularity of the function).
In addition, the paper used in the current test is using nuclear data which are confidental and cannot be integrated to Paraview code.
In the attachment please find data (gaussiansine.csv produced with the Scilab script test.sce) and numerical calculation results produced with the statistics software R and a classical PCA (ACP_classique.R). These results can easily be used to build unitary tests comparing numerical values produced by Paravew with those produced by R.
Please find a desciption hereafter of the tests which can be built:
N is the number of curves and T is the number of points in each curve. We distinguish T>N cases and T<N cases because of calculation performance. The matrix X is sized of T*N. The covariance matrix Xt*X is sized of T*T. If T<N, it is consistent to evaluate the covariance matrix and to compute its T eigenvalues and eigenvectors. If T>N, it is not necessary to evaluate the covariance matrix. One can compute directly the SVD of matrix X which gives N singular non-zero values.
T>N is the most classical case. Consequently, the minimal unitary tests list is:
test 1 : classical PCA with T>N
test 2 : robust PCA with T>N
Complementary list is:
test 3 : classical PCA with T<N
test 4 : robust PCA with T<N
https://gitlab.kitware.com/paraview/paraview/-/issues/15686Extract bag plot filter is not using the most adequate 2D kernel density esti...2020-06-29T20:51:22-04:00Kitware RobotExtract bag plot filter is not using the most adequate 2D kernel density estimation.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15686). Further discussion may take place here.**
---
In Paraview, HDR plot uses a 2D kernel density estimation in the plane ass...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15686). Further discussion may take place here.**
---
In Paraview, HDR plot uses a 2D kernel density estimation in the plane associated to the first 2 principal components. In Paraview, a symmetrical normal kernel is used and its width, given by the user, is by default equal to 1. This 2D density approximation is not accurate.
In the Rainbow package, the method used is the kernel density estimation is based on a generic Gaussian not necessarily symmetrical. In addition, kernel's parameters (i.e. the covariance matrix) are determined by crosschecking (implying a optimization)
To validate this functionality, the "gaussian sine" case can be used.https://gitlab.kitware.com/paraview/paraview/-/issues/13820ParaView filters and non-conservation of the Representation2020-06-29T20:52:22-04:00Kitware RobotParaView filters and non-conservation of the Representation**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13820). Further discussion may take place here.**
---
Hello,
In ParaView the representation of an object is "non-conservati...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13820). Further discussion may take place here.**
---
Hello,
In ParaView the representation of an object is "non-conservative". I will explain that with an example:
1) I open a mesh, then select "Surface with edges" as its representation.
2) I apply a Clip filter to this mesh.
3) The representation of the resulting clip is not "Surface with edges" but "Surface".
This behaviour is not what the users expect, it is also general and not only for the Clip filter. I would like to have a "representation conservation" in ParaView.
Regards,
Alejandro.
https://gitlab.kitware.com/paraview/paraview/-/issues/15683Extract bag plot filter does not use good criteria to choose outliers2021-04-29T12:19:54-04:00Kitware RobotExtract bag plot filter does not use good criteria to choose outliers**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15683). Further discussion may take place here.**
---
The identification of outliers should not be based on a limit of the densi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15683). Further discussion may take place here.**
---
The identification of outliers should not be based on a limit of the density of the data points but on a decreasing sorting in density of points.
In the Rainbow package of the R software, the algorithm used is the Hyndman one to identify high density regions.
Computing and Graphing Highest Density Regions, Rob J. Hyndman, The American Statistician, Vol. 50, No. 2 (May, 1996), pp. 120-126
The ACP_classique.R script is using a classical PCA and does not use the Rainbow package. So those the result can be directly compared to Paraview with default parameters.
The median curve is the number 15 et the only outlier is the 21. Those results can be used to build a simple unitary test. A more complicated one would compare the two PCA projections (execute the R script on the 2 first components).https://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)