ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2022-07-05T06:14:37-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/14718Pause in animation track2022-07-05T06:14:37-04:00Kitware RobotPause in animation track**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14718). Further discussion may take place here.**
---
I have a user that would like to use create an animation track, interpolat...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14718). Further discussion may take place here.**
---
I have a user that would like to use create an animation track, interpolate between camera locations. He would like to have a pause function. Otherwise, if you have two views that are the same, don't move the camera as the animation inspector moves between the two, same views. For instance, if he wants to look at the front of a car, then look at the back of the car, he would start looking at the front of the car, pause for numerous seconds, fly around the car to the back, then pause for numerous seconds. Currently, the only way to do this is to create numerous views in the track that are the same point - and the camera moves as the track runs from a view to the same view.https://gitlab.kitware.com/paraview/paraview/-/issues/14715remove semicolon from VTK classes that use the vtkTypeMacro and have the sem...2020-05-06T09:28:46-04:00Kitware Robotremove semicolon from VTK classes that use the vtkTypeMacro and have the semicolon there**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14715). Further discussion may take place here.**
---
Both the CUDA compilers and the GCC -pedantic flag give warnings when ther...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14715). Further discussion may take place here.**
---
Both the CUDA compilers and the GCC -pedantic flag give warnings when there are extra semicolons. The output from nvcc looks like:
/home/acbauer/CODE/ParaView/ParaView-v4.1.0/VTK/Common/Core/vtkDataArray.h(48): warning: extra ";" ignored
To get cleaner compiles these should be fixed in both VTK and ParaView.
https://gitlab.kitware.com/paraview/paraview/-/issues/14749Suggestions for improvement of point/cell display labels2024-03-07T20:47:39-05:00Kitware RobotSuggestions for improvement of point/cell display labels**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14749). Further discussion may take place here.**
---
We need to add a "are you sure?" warning when users try to select a large ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14749). Further discussion may take place here.**
---
We need to add a "are you sure?" warning when users try to select a large number of cells and/or points, and the display labels is turned on. This causes crashes.
We also need to give the user the option to depopulate the cells and points that have display labels turned on - with say 100 as a maximum. Maximum to be user selectable. Use same random method as used by the glyph filter for huge numbers of points or vectors.
Marking high, since this leads to crashes.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/14786Camera orbit doesn't work when rotating about X axis2020-05-06T05:15:09-04:00Kitware RobotCamera orbit doesn't work when rotating about X axis**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14786). Further discussion may take place here.**
---
Encountered in ParaView master and new MatViz application - when selecting...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14786). Further discussion may take place here.**
---
Encountered in ParaView master and new MatViz application - when selecting the X axis the rotation flips as you move through the series. It does not seem to be possible to rotate about this axis without the flipping artifact.https://gitlab.kitware.com/paraview/paraview/-/issues/14798generated coprocessing script don't output proper locations for Text and Anno...2020-05-06T05:14:25-04:00Kitware Robotgenerated coprocessing script don't output proper locations for Text and AnnotateTime sources**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14798). Further discussion may take place here.**
---
If a Catalyst script is output with rendering turned on it always puts the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14798). Further discussion may take place here.**
---
If a Catalyst script is output with rendering turned on it always puts the Text and AnnotateTime sources in the default (lower left for me) location in the view. Thus when the script is run these sources overlap instead of being in the desired spot. An example is for the cpannotate.py script which should create images like correctannotationoutput.png but instead creates images like image_24.png. https://gitlab.kitware.com/paraview/paraview/-/issues/14800No consistency for Catalyst generated scripts and state files with regards to...2020-05-06T05:14:07-04:00Kitware RobotNo consistency for Catalyst generated scripts and state files with regards to floating point number formatting**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14800). Further discussion may take place here.**
---
Bob Kares sent an email with:
Why is there no consistency in the output...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14800). Further discussion may take place here.**
---
Bob Kares sent an email with:
Why is there no consistency in the output format used for numbers that appear in the Catalyst generated .py script? For example, one of my palettes uses a data range -2e+10 to 2e+10. When I look at what the Catalyst plugin generates by default, the CreatePiecewiseFunction line generated by the Catalyst plugin has -20000000000 and 20000000000. Sometimes "e" format is used instead, but I can’t really discern what the rule is.
This same problem occurs in the state files ParaView writes out. This is
more than a cosmetic issues because it makes data values you know are
there hard to find with a text editor.https://gitlab.kitware.com/paraview/paraview/-/issues/14861Color legend incorrect if empty title given from the python2021-03-23T09:58:04-04:00Kitware RobotColor legend incorrect if empty title given from the python**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14861). Further discussion may take place here.**
---
Execute attached script test_color_legend.py (attached in the script+data....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14861). Further discussion may take place here.**
---
Execute attached script test_color_legend.py (attached in the script+data.tar.gz) several times in the Python Shell.(Before executing correct the path to the deplacements_et_contraintes.0001.vtu file if need). As shown on attached screen-shots, we randomly get a blue color legend at the bottom of the viewer, or a color legend without the Component, or a color legend whose Component is displayed under the color legend.
In the attached script replace
color_legend_title = ""
by the
color_legend_title = " "
and execute the script several times. The display is correct.
It should be able to create a color legend with the empty title from python, as it is possible from the GUI.https://gitlab.kitware.com/paraview/paraview/-/issues/14868segfault reading triangle grid2021-03-23T11:50:30-04:00Kitware Robotsegfault reading triangle grid**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14868). Further discussion may take place here.**
---
Paraview 4.1 crashes (Segmentation Fault) opening the included file.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14868). Further discussion may take place here.**
---
Paraview 4.1 crashes (Segmentation Fault) opening the included file.https://gitlab.kitware.com/paraview/paraview/-/issues/14884ghost cells causing problems in pvti files2020-05-14T21:38:31-04:00Kitware Robotghost cells causing problems in pvti files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14884). Further discussion may take place here.**
---
Ghost cells are causing "cracks" between partitions of the original subdom...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14884). Further discussion may take place here.**
---
Ghost cells are causing "cracks" between partitions of the original subdomains.
Steps to reproduce:
run the following script with pvbatch with 2 processes:
from paraview.simple import *
Wavelet()
g = GradientOfUnstructuredDataSet()
g.ScalarArray = ['POINTS', 'RTData']
w = XMLPImageDataWriter()
w.FileName = "ghosts.pvti"
w.UpdatePipeline()
Load that into paraview and change to surface view.
Berk GeveciBerk Gevecihttps://gitlab.kitware.com/paraview/paraview/-/issues/148962d plot log ranges - advanced2018-02-26T13:15:54-05:00Kitware Robot2d plot log ranges - advanced**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14896). Further discussion may take place here.**
---
The following explains an advanced implementation for log Y axis, 2d plots...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14896). Further discussion may take place here.**
---
The following explains an advanced implementation for log Y axis, 2d plots. It is the same algorithm that is needed for log color map. See bug 14895 for a use case.
Here is an e-mail thread created about modifications to the min and max color ranges for log scaling. This should be implemented in 4.3.
I would like to propose a few changes in our log scaling algorithm for painting a dataset by a variable. I discussed this with Utkarsh, and he asked that I bounce it off the e-mail list. So, here goes.
Currently, when a user log scales a variable, if all data is positive, ParaView just uses the normal min and max. There are times when this is not proper – for instance when looking at the temperature or density of material in a supernova, or velocity of outbound gas. Another example is large data, with noise around zero. I would like to propose that we have a user selectable option to set the minimum at maximum*10^-q, where q is user defined but defaults to 4. In other words, the minimum would be set to 1*10^-4 of what the maximum is.
If all of the user’s data is negative, ParaView grumbles, and then seg faults using a current master git pull – not optimal behavior. In PV 4.1, it just sets min and max to 0. I would like to propose that ParaView calculate the log of the data, as follows: Index= -(log(abs(Var))). Then, just draw the color legend as normal – for instance, red at top, white in the middle and blue at bottom. Tick marks will be the reverse of positive log scaling – with the dense numbers, more negative numbers at the bottom and less dense, less negative numbers at the top.
The problem arises with data that spans positive and negative numbers. Since the log of 0 is infinity, we have to deal with very small numbers in a special way. I propose that we find maxVal = max(maximum, abs(minimum)). Then, we set the color bar to run from maxVal to –maxVal. We log scale the top half of the color legend, running from maxVal to maxVal*10^-4, and we reverse log scale the bottom half of the color legend, running from –maxVal*10^-4 to –maxVal. We calculate this negative range the same as the all negative data section above. All data between maxVal*10^-4 and -maxVal*10^-4 would remain white by default, or user selectable black.
User selectable functionality would be as follows:
• to allow/ not allow negative numbers (default allow)
• to be able to change the q exponent (i.e., 4 above) (default 4)
• to be able to change the painting color that is too small (default white)
• to clamp minimum to some number (such as q == 4 above). (default on).
Thoughts?
Alan
Reply to a question on negative numbers:
Regarding negative values, my bad - I was not clear. A vertical normal log scale bar, going from a 1e8 to 1e4 may have minor labels (working down) of 1e8, 1e7, 1e6, 1e5, and 1e4. I.e., each tick towards the top representing a change of 10 million units, each tick towards the top representing a change of a thousand units. Now, for the negative case, this would be reversed. The color bar remains colored as before (for default color map, red on top, blue on bottom). Since more positive numbers are always on top, we would run as follows (working down the minor labels): -1e4, -1e5, -1e6, -1e7 and -1e8. Units change by the thousands at the top of the color legend, and millions towards the bottom.https://gitlab.kitware.com/paraview/paraview/-/issues/149162d plot title needs multiple line option2020-05-06T04:57:43-04:00Kitware Robot2d plot title needs multiple line option**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14916). Further discussion may take place here.**
---
We need to be able to split a title onto multiple lines on 2d plots.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14916). Further discussion may take place here.**
---
We need to be able to split a title onto multiple lines on 2d plots.https://gitlab.kitware.com/paraview/paraview/-/issues/14930Disable Rescale to Custom Data Range when using solid color2020-05-06T04:50:20-04:00Kitware RobotDisable Rescale to Custom Data Range when using solid color**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14930). Further discussion may take place here.**
---
Normally when you hit the Rescale to Custom Data Range toolbar button, you...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14930). Further discussion may take place here.**
---
Normally when you hit the Rescale to Custom Data Range toolbar button, you get a dialog that allows you to select the range of scalar values. However, if currently coloring by a solid color, clicking this box does nothing. This is confusing behavior if you are expecting a dialog box to pop up.
When the color is solid color, the Rescale to Custom Data Range button should be disabled (grayed out). The adjacent Rescale to Data Range should probably also be disabled for consistency.https://gitlab.kitware.com/paraview/paraview/-/issues/14932XDMF - 8 byte precision UInt is broken2020-05-07T09:44:10-04:00Kitware RobotXDMF - 8 byte precision UInt is broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14932). Further discussion may take place here.**
---
This problem relates to opening XDMF files in Paraview 4.1.
Support for...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14932). Further discussion may take place here.**
---
This problem relates to opening XDMF files in Paraview 4.1.
Support for XDMF DataItem elements of NumberType=UInt with Precision="8" is broken when using topology stored in an external data file with Format="Binary".
I suspect the driver is trying to interpret the binary value as a signed int rather than an unsigned int.
Using NumberType=Int works OK with Precision="8" and is a satisfatory work around for now.
This might be a trivial fix if it is just a case of correctly casting the data.
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.https://gitlab.kitware.com/paraview/paraview/-/issues/14946Parallel coordinates view selection handles don't update properly2020-05-06T04:45:22-04:00Kitware RobotParallel coordinates view selection handles don't update properly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14946). Further discussion may take place here.**
---
+ Show a dataset in the "Parallel Coordinates View" and "Render View" at t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14946). Further discussion may take place here.**
---
+ Show a dataset in the "Parallel Coordinates View" and "Render View" at the same time.
+ Create a selection in Parallel Coordinates View. Works as expected with the elements getting highlighted in the "Render View".
+ Now create a new selection on the same dataset in the "Render View", the "Parallel Coordinates View" updates, but the "red-handles" still reflect the old selection and you see something like the attached image.
The handles should have been removed entirely.https://gitlab.kitware.com/paraview/paraview/-/issues/14951Values for decimation threshold in interactive rendering options makes no sense2020-05-06T04:40:46-04:00Kitware RobotValues for decimation threshold in interactive rendering options makes no sense**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14951). Further discussion may take place here.**
---
Under the Render View tab in settings, the values used for the slider unde...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14951). Further discussion may take place here.**
---
Under the Render View tab in settings, the values used for the slider under Interactive Rendering Options that controls the threshold for when to employ decimation make no sense. There are two really odd values being set:
1. The default threshold (until the user changes it) is 5MB. That is ridiculously small. I doubt there exist any ParaView users that need such a small threshold. This should be at least 50 or 100MB.
2. The max value is 100GB. That seem excessively high. The real problem is that having a slider going from 0 to 102400 means that each tiny movement of the slider is for a full gigabyte. That makes the slider totally useless.https://gitlab.kitware.com/paraview/paraview/-/issues/14959probe filter should return input grid cell data as cell data instead of addin...2020-05-06T04:39:23-04:00Kitware Robotprobe filter should return input grid cell data as cell data instead of adding it to point data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14959). Further discussion may take place here.**
---
the probe filter should set the cell data from its input to cell data on i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14959). Further discussion may take place here.**
---
the probe filter should set the cell data from its input to cell data on its output but instead sets it to point data. if there is a point data field with the same name it uses those values and doesn't give any information on the cell values at the specified location.
also, this filter doesn't appear to work properly for cell data for multiblock data set inputs.https://gitlab.kitware.com/paraview/paraview/-/issues/14973New writers cannot be added to Catalyst through Live2020-05-06T04:36:10-04:00Kitware RobotNew writers cannot be added to Catalyst through Live**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14973). Further discussion may take place here.**
---
While a Catalyst pipeline that includes writers can be generated using the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14973). Further discussion may take place here.**
---
While a Catalyst pipeline that includes writers can be generated using the CoProcessing plugin, it would be nice if a running Catalyst pipeline could be modified through Live to add writers.https://gitlab.kitware.com/paraview/paraview/-/issues/14972Delete is disabled for Catalyst Live filters and writers2020-05-06T04:36:18-04:00Kitware RobotDelete is disabled for Catalyst Live filters and writers**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14972). Further discussion may take place here.**
---
Filters and writers cannot be deleted from a Catalyst pipeline. Implementi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14972). Further discussion may take place here.**
---
Filters and writers cannot be deleted from a Catalyst pipeline. Implementing this feature would allow a more complete pipeline manipulation (besides filter parameter changes)https://gitlab.kitware.com/paraview/paraview/-/issues/14992vtkSMDomain::SetDefaultValues() overrides custom setting defaults in some cases2020-05-06T04:24:20-04:00Kitware RobotvtkSMDomain::SetDefaultValues() overrides custom setting defaults in some cases**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14992). Further discussion may take place here.**
---
In particular, this makes it impossible to set the default representation ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14992). Further discussion may take place here.**
---
In particular, this makes it impossible to set the default representation type for GeometryRepresentation with the following JSON:
"representations" : {
"GeometryRepresentation" : {
"Representation" : "Surface With Edges"
}
}
The reason is that custom default values are set prior to domains being reset. Some domains, such as vtkSMBooleanDomain, do nothing in SetDefaultValues(). Others, such as vtkSMRepresentationTypeDomain, change property values.