ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-08-28T09:39:51-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/11918Prism Filter does not accept point data as input2018-08-28T09:39:51-04:00Kitware RobotPrism Filter does not accept point data as input**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11918). Further discussion may take place here.**
---
The prism filter expects cell data as pipeline input, but this should not ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11918). Further discussion may take place here.**
---
The prism filter expects cell data as pipeline input, but this should not be a requirement. A significant capability that relies on the input being cell data is linked selection - selection in the prism view is associated by GlobalElementID to the data in the other view(s).https://gitlab.kitware.com/paraview/paraview/-/issues/117762d axis needs enhancing2018-08-28T09:39:51-04:00Kitware Robot2d axis needs enhancing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11776). Further discussion may take place here.**
---
We need to enhance the 2d axis. I am using sources/ mandlebrot as an exam...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11776). Further discussion may take place here.**
---
We need to enhance the 2d axis. I am using sources/ mandlebrot as an example.
I can think of a few options, such as:
* Lock the axis to reasonable numbers. With mandelbrot, use a Y range from -1.5 to 1.5.
* Let the user to select the range, and thus the size of the axis.
* Allow user to add a grid pattern.
* Allow user to turn on/off different axes (for instance, upper and right.)
https://gitlab.kitware.com/paraview/paraview/-/issues/11960CTH reader: Optionally calculate "derived variables" density and material de...2018-08-28T09:39:51-04:00Kitware RobotCTH reader: Optionally calculate "derived variables" density and material densities.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11960). Further discussion may take place here.**
---
In spcth files, derived variables are not saved in the file because they c...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11960). Further discussion may take place here.**
---
In spcth files, derived variables are not saved in the file because they can (usually) be calculated from the other variables that are written to the file. However, the spcth reader does not do this. The feature request is to optionally compute several derived variables if the variables they depend on are in the file and if the user requests them (through the variable checkboxes on the preperties panel.) Formulas given in Additional Information.
The motivation for this request is that the Prism plugin is much more effective when the material densities are available, so this request is focused on just these quantities. A more complete solution would be to optionally compute all the derived variables, which would be straightforward and not too much more work after computing the material densities.https://gitlab.kitware.com/paraview/paraview/-/issues/11962Turn on/off coordinate frames2018-08-28T09:39:51-04:00Kitware RobotTurn on/off coordinate frames**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11962). Further discussion may take place here.**
---
The coordinate frames are stored in the exodus files, and can be extracted...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11962). Further discussion may take place here.**
---
The coordinate frames are stored in the exodus files, and can be extracted using standard calls such as ex_get_coordinate_frames(). There may be up to a few hundred frames in a model. Each frame is defined fairly simply,
1. An index
2. An indicator of cartesian, cylindrical or spherical
3. An origin (3 reals)
4. A Z direction vector (3 reals)
5. A point in the XZ plane (3 reals).
Eventually, we would like to turn on/off any of these frames, but initially we would be happy if they could all be turned on/off together.
Display is a simple glyph like the one currently used for displaying the origin. The glyph should indicate the coordinate axes.
The need for this is immediate (what isn't). What is happening is that we are seeing support issues because this data is stored in the file and can't be examined in any way be the analysts.
https://gitlab.kitware.com/paraview/paraview/-/issues/11821(Mars) Prism - autoscaling should differ for multiple surfaces2018-08-28T09:39:50-04:00Kitware Robot(Mars) Prism - autoscaling should differ for multiple surfaces**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11821). Further discussion may take place here.**
---
In prism (both filter and sesame reader), surfaces are rescaled so that th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11821). Further discussion may take place here.**
---
In prism (both filter and sesame reader), surfaces are rescaled so that they have an aspect ratio of 1:1:1 in the three coordinate directions. This is because the coordinates are thermodynamic variables, rather than e.g. length, and are independent and have different units. For a single surface this seems to work fine. However, when two or more surfaces are shown, they are rescaled independently. As a result, the same coordinates on each surface are not at the same location in the view.https://gitlab.kitware.com/paraview/paraview/-/issues/119702d charts colors are bad after redirecting input2018-08-28T09:39:50-04:00Kitware Robot2d charts colors are bad after redirecting input**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11970). Further discussion may take place here.**
---
Trunk, Windows, local server.
* Open Can.exo.
* Plot over Line filter. A...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11970). Further discussion may take place here.**
---
Trunk, Windows, local server.
* Open Can.exo.
* Plot over Line filter. Apply.
* Highlight can.exo. Calculator filter. Formula VEL*2. Apply.
* In the pipeline browser, on Plot Over Line, change input to Calculator.
* Now, highlight the Plot Over Line filter,Display Tab. Notice that the colors don't match the colors of the lines.https://gitlab.kitware.com/paraview/paraview/-/issues/119712D Charts Sometimes Pick Ugly Colors2018-08-28T09:39:50-04:00Kitware Robot2D Charts Sometimes Pick Ugly Colors**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11971). Further discussion may take place here.**
---
Although a lot of thought went into choosing the colors for 2D charts, the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11971). Further discussion may take place here.**
---
Although a lot of thought went into choosing the colors for 2D charts, the way colors are selected sometimes undermines the color palette. For an example, do the following:
1. Load can.ex2, load all variables, apply.
2. Plot Over Line. Apply.
The resulting plot (an example is attached) has terrible colors. The colors have poor contrast with each other and with the background. In addition, it just does not look good.
The problem is that colors are assigned to all variables, but only a few are actually drawn (some are suppressed for good reason). The best colors are the first in the list, and most of those are skipped over.https://gitlab.kitware.com/paraview/paraview/-/issues/11848Print out size of viewport during redraw2018-08-28T09:39:50-04:00Kitware RobotPrint out size of viewport during redraw**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11848). Further discussion may take place here.**
---
I have a user that constantly resizes his ParaView window, trying to get t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11848). Further discussion may take place here.**
---
I have a user that constantly resizes his ParaView window, trying to get the size of the viewport to exactly match previous runs. This way, he can create a flipbook that matches. This is currently very difficult.
Please add an output of some type (maybe on the bottom part of the window) that shows the size of the 3d viewport as it is resized.
Thanks.https://gitlab.kitware.com/paraview/paraview/-/issues/12018Save screenshots and 2d windows different.2018-08-28T09:39:50-04:00Kitware RobotSave screenshots and 2d windows different.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12018). Further discussion may take place here.**
---
From a user:
The attached figs show the result of a 'Save Screenshot' i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12018). Further discussion may take place here.**
---
From a user:
The attached figs show the result of a 'Save Screenshot' in PV 3.10.0 64 bit, vs. what's actually on the screen (captured with PrtSc). In the line-plots, 'Save Screenshot' changed both the font and tick-marks from what's on the screen. I manually increased the rez for the screenshot, but would like the fonts etc to stay the same.
https://gitlab.kitware.com/paraview/paraview/-/issues/11853Allow variables to be normalized to the min and max in the dataset2018-08-28T09:39:50-04:00Kitware RobotAllow variables to be normalized to the min and max in the dataset**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11853). Further discussion may take place here.**
---
I have a user that would like to normalize a variable to the range of 0-1....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11853). Further discussion may take place here.**
---
I have a user that would like to normalize a variable to the range of 0-1. His data is good data, but the scale is incorrect and unknown. Thus, he wants to present his data in 0-1 space.
I used the formula (X - min) / (max - min) for my user.
Maybe we need some filter called AnalysisFunctions or something, and this could be one of the first entries?https://gitlab.kitware.com/paraview/paraview/-/issues/11854Add multiple variable selection to AMR Contour2018-08-28T09:39:50-04:00Kitware RobotAdd multiple variable selection to AMR Contour**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11854). Further discussion may take place here.**
---
We need to add multiple variable support for the AMR Contour, and probably...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11854). Further discussion may take place here.**
---
We need to add multiple variable support for the AMR Contour, and probably AMR Clip filters. I have a user that is looking at an object, such as a car. Every part of the car is a different Material Volume Fraction (engine, transmission, frame, alternator - around 15-20 of these), and he would like to be able to select them in one step, rather than one by one, over and over again.
A example would be Dave's small CTH dataset - we want to select the ball and plate with one filter.
What I want is basically the code in the Material Interface Filter.https://gitlab.kitware.com/paraview/paraview/-/issues/12023Block names not save/read in/from VTM files.2018-08-28T09:39:50-04:00Kitware RobotBlock names not save/read in/from VTM files.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12023). Further discussion may take place here.**
---
Refer to thread: http://markmail.org/thread/72vc7cal3mrqclrf
**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12023). Further discussion may take place here.**
---
Refer to thread: http://markmail.org/thread/72vc7cal3mrqclrf
https://gitlab.kitware.com/paraview/paraview/-/issues/12048Add a "find data" icon2018-08-28T09:39:50-04:00Kitware RobotAdd a "find data" icon**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12048). Further discussion may take place here.**
---
We really should have a way to get at find data from the main gui. This i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12048). Further discussion may take place here.**
---
We really should have a way to get at find data from the main gui. This is too important of functionality to be hidden under "edit".
Another option would be to allow the find data dialog to be brought up from a right click on an object.https://gitlab.kitware.com/paraview/paraview/-/issues/12052Loading plugins are not captured in python trace2018-08-28T09:39:50-04:00Kitware RobotLoading plugins are not captured in python trace**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12052). Further discussion may take place here.**
---
With python trace activated, a plugin is loaded. The user continues to dev...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12052). Further discussion may take place here.**
---
With python trace activated, a plugin is loaded. The user continues to develop their pipeline and stops the trace. The trace is saved to a file. Upon reading the file (running the saved trace) the filter in the loaded plugin is not recognized and the python script fails. There is no record in the python file that a plugin was loaded.https://gitlab.kitware.com/paraview/paraview/-/issues/12053Cannot coerce hscth reader for hscth file that is does not match naming conve...2018-08-28T09:39:50-04:00Kitware RobotCannot coerce hscth reader for hscth file that is does not match naming convention**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12053). Further discussion may take place here.**
---
The hscth reader is invoked for files ending ".hscth". It turns out that "...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12053). Further discussion may take place here.**
---
The hscth reader is invoked for files ending ".hscth". It turns out that "hsct?" should also be matched, where "?" is a wildcard for a single character. The first minor bug fix is to match this second pattern for hscth files.
The second, more serious, issue is that when I selected the file to open and then specifically selected to use the hscth reader to open it, I got a failure with an error message referring to the visit silo reader. In the end, I could not open the file until I renamed it to end with ".hscth".https://gitlab.kitware.com/paraview/paraview/-/issues/12059ParaView should check memory and issue warning before faulting2018-08-28T09:39:50-04:00Kitware RobotParaView should check memory and issue warning before faulting**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12059). Further discussion may take place here.**
---
ParaView should keep an eye on memory better, and should give the user a w...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12059). Further discussion may take place here.**
---
ParaView should keep an eye on memory better, and should give the user a warning that it is low on memory. At the very least, it should put up a warning right before dying. I would think that a warning at 90% or 95% full would be acceptable.
On production clusters there is no swap space - thus, you run out of memory, you die. In really confusing, frustrating way. Without letting the user know.
Requested by Mars.https://gitlab.kitware.com/paraview/paraview/-/issues/12080PlotOverLine is problematic with 2d data2018-08-28T09:39:50-04:00Kitware RobotPlotOverLine is problematic with 2d data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12080). Further discussion may take place here.**
---
ParaView 3.10.0, Windows, local server.
* Sources/ Wavelet. Apply. ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12080). Further discussion may take place here.**
---
ParaView 3.10.0, Windows, local server.
* Sources/ Wavelet. Apply. Surface. Color by: RTData.
* Slice. Z Normal. Apply. Turn off Show Plane.
* Data Analysis/ Plot over line. Apply.
>> Now, go to the 3d window, grab the ends of the lines, and move them slightly away from the ends of the square. You will never get the 2d plot again.
https://gitlab.kitware.com/paraview/paraview/-/issues/12126Prism Slow performance for large SESAME files2018-08-28T09:39:50-04:00Kitware RobotPrism Slow performance for large SESAME files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12126). Further discussion may take place here.**
---
I loaded a sesame file with 1000x1000 density x temperature points and the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12126). Further discussion may take place here.**
---
I loaded a sesame file with 1000x1000 density x temperature points and the interactive response was much slower. In addition, it seems each frame in a time series was slow; does this mean that the sesame file is being reread at each time? SESAME files do not have time, so it would be better to read it just once.https://gitlab.kitware.com/paraview/paraview/-/issues/12127Prism treatment of negative pressure when log scaling2018-08-28T09:39:50-04:00Kitware RobotPrism treatment of negative pressure when log scaling**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12127). Further discussion may take place here.**
---
It is possible that pressure, internal energy, and other thermodynamic var...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12127). Further discussion may take place here.**
---
It is possible that pressure, internal energy, and other thermodynamic variables (except density and temperature) can be negative. When the user selects to log scale these variables, Prism replaces the negative values with an arbitrary small positive number. The feature request is to set this number to be two orders of magnitude smaller than the smallest positive value for that variable.https://gitlab.kitware.com/paraview/paraview/-/issues/12168Cleanup ResetCache for Exodus reader2018-08-28T09:39:50-04:00Kitware RobotCleanup ResetCache for Exodus reader**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12168). Further discussion may take place here.**
---
We need to understand and cleanup the Exodus reader ResetCache code. This...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12168). Further discussion may take place here.**
---
We need to understand and cleanup the Exodus reader ResetCache code. This code is problematic with ParaView, and when turned off, has been problematic with Pat at Sandia. We really should try to figure out what this code does, and turn it off in a way that doesn't hurt Pat.