ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-03-05T10:47:42-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/5553Grab current camera position from Animation View dialogs2019-03-05T10:47:42-05:00Kitware RobotGrab current camera position from Animation View dialogs**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5553). Further discussion may take place here.**
---
There needs to be a way to grab the current camera position from withing th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5553). Further discussion may take place here.**
---
There needs to be a way to grab the current camera position from withing the dialogs generated by animation view. That is, there should be a button in the dialog box to set the camera position to grab the current camera position.https://gitlab.kitware.com/paraview/paraview/-/issues/5552Array leaked when reading Exodus metadata2019-03-05T10:47:42-05:00Kitware RobotArray leaked when reading Exodus metadata**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5552). Further discussion may take place here.**
---
If you have compiled ParaView with VTK_DEBUG_LEAKS ON (and all us developer...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5552). Further discussion may take place here.**
---
If you have compiled ParaView with VTK_DEBUG_LEAKS ON (and all us developers should), it reports that an array leaks when you load Exodus metadata. To see the problem, load disk_out_ref and turn on the Meta Data flag under the File Pattern group. After you accept and then exit ParaView, vtkDebugLeaks reports a vtkCharArray is still around.https://gitlab.kitware.com/paraview/paraview/-/issues/5543Change representation/view groups to "representations"/"views"2019-03-05T10:47:42-05:00Kitware RobotChange representation/view groups to "representations"/"views"**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5543). Further discussion may take place here.**
---
Since old view modules/displays are now gone, we need to rename the xml gro...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5543). Further discussion may take place here.**
---
Since old view modules/displays are now gone, we need to rename the xml group for representations/views accordingly.https://gitlab.kitware.com/paraview/paraview/-/issues/5542using timeseries stored in a vtk xml file2019-03-05T10:47:42-05:00Kitware Robotusing timeseries stored in a vtk xml file**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5542). Further discussion may take place here.**
---
I would like to be able to store multiple time steps in a single
vtk_xml f...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5542). Further discussion may take place here.**
---
I would like to be able to store multiple time steps in a single
vtk_xml file (no problem) and process them with paraview.
Storing multiple time steps is supported in the vtk xml format however
when opening such a file paraview tells me that there is only a single
timestep. googling for some usefull comments resulted in some
unsettling info. It seems that this is indeed not supported in
paraview and that i will have to use the paraview format. however
however this file type is more or less a list of vtk xml files (if I
understood correctly). Does that mean that if i want to use any vtk
based storage method i will have to store each time step in a separate
file? and does this also mean that i will have to store the mesh info
for each time step? We work with a fixed mesh and i am looking at
storing hundreds of timestep.https://gitlab.kitware.com/paraview/paraview/-/issues/5534add a few constants in vtkConstants.py2019-03-05T10:47:42-05:00Kitware Robotadd a few constants in vtkConstants.py**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5534). Further discussion may take place here.**
---
I add a few useful constants about cells description in vtkConstants.py,
c...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5534). Further discussion may take place here.**
---
I add a few useful constants about cells description in vtkConstants.py,
copied from vtkCellType.h
BTW, the last cell types ("higher order") seem to do not exist for
python wrapping.https://gitlab.kitware.com/paraview/paraview/-/issues/5523Transformation of many/all objects of the pipeline at once2019-03-05T10:47:48-05:00Kitware RobotTransformation of many/all objects of the pipeline at once**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5523). Further discussion may take place here.**
---
A user has requested that we be able to do transformations on numerous obje...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5523). Further discussion may take place here.**
---
A user has requested that we be able to do transformations on numerous objects in the pipeline browser at once, and that objects that are derived from a previous object keep the applied transformation.
Example:
* Open Can.exo. Apply.
* Clip. Apply.
* Highlight Can.exo in Pipeline Browser, Clip. Inside out. Apply.
* Highlight the first clip in the pipeline browser, Display, Transformation, Translate, Y, =1.0.
* Highlight the second clip in the pipeline browser, Display, Transformation, Translate, Y, =1.0.
- User wants to do this with only one sequence of commands. He/she may have hundreds of parts that require transformation.
* Highlight the last clip. Cut, Apply. Now, turn the eyeball back on for the last clip.
- Notice that the cut is not derived from the output of clip, but rather from the original data. User wants all derived objects to be from the input filter, not the original data.
https://gitlab.kitware.com/paraview/paraview/-/issues/5521Add a ruler source/filter2019-03-05T10:47:48-05:00Kitware RobotAdd a ruler source/filter**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5521). Further discussion may take place here.**
---
A user has requested that we add a ruler type feature to ParaView. This us...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5521). Further discussion may take place here.**
---
A user has requested that we add a ruler type feature to ParaView. This user wants to know how far two cells, points, or objects are from each other. https://gitlab.kitware.com/paraview/paraview/-/issues/5520Automatic Center-of-Rotation for Interaction2019-03-05T10:47:48-05:00Kitware RobotAutomatic Center-of-Rotation for Interaction**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5520). Further discussion may take place here.**
---
The center of rotation for a camera is very important for interacting with ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5520). Further discussion may take place here.**
---
The center of rotation for a camera is very important for interacting with data/geometry in paraview. Setting it to the center of the data bounds is good enough for interaction with the camera placed far from the model such that it fits on screen. However when zooming in to a small portion of the geometry then rotation causes the user to get lost quickly. Additionally when the center of rotation is behind the camera the translation is backwards, and when the COR is at the camera the translation is very slow. Instead the center of rotation must be set to some point on the small portion of geometry in view. In PV 2.x this could be done by a pick operation, but even that was prohibitive.
I propose a feature to enable an (optional) interaction mode that automatically selects a new center of rotation after any translation/zoom of the camera. The selected center should cause rotation to be close to what the human viewing the window expects. Obviously this is a bit subjective but any policy is probably better than the current behavior. Perhaps it could be something as simple as a weighted average of the z-buffer with higher weight given to the samples at the center of the window.
https://gitlab.kitware.com/paraview/paraview/-/issues/5518SNL: Glyph filter doesn't provide reasonable "Scale Factor" when "Scale Mode"...2019-03-05T10:47:48-05:00Kitware RobotSNL: Glyph filter doesn't provide reasonable "Scale Factor" when "Scale Mode" changed**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5518). Further discussion may take place here.**
---
When the Scale Mode is changed from "vector" to "scalar" (or, I assume, "ve...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5518). Further discussion may take place here.**
---
When the Scale Mode is changed from "vector" to "scalar" (or, I assume, "vector components"), the "Set Scale Factor" entry is not changed. While this is good because it's irritating to enter a scale factor only to have it overwritten when you change the scale mode, this also means that no reasonable default is provided when either the scale mode or the particular field used for scaling is altered. These reasonable values are hard to get without switching to the information tab of another filter.
Perhaps a button to compute a reasonable scale factor should be provided to the right of the label entry?https://gitlab.kitware.com/paraview/paraview/-/issues/5517Object inspector information panel is not updated2019-03-05T10:47:48-05:00Kitware RobotObject inspector information panel is not updated**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5517). Further discussion may take place here.**
---
To reproduce:
* Create sphere
* apply
* Check number of cells in the inf...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5517). Further discussion may take place here.**
---
To reproduce:
* Create sphere
* apply
* Check number of cells in the information panel
* Change resolution
* apply
* Check number of cells in the information panel
The number of cells is the same. To force the information panel to update, you have to select another source first and select sphere again.https://gitlab.kitware.com/paraview/paraview/-/issues/5516Save Screenshot fails for file names with multiple dots in name2019-03-05T10:47:48-05:00Kitware RobotSave Screenshot fails for file names with multiple dots in name**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5516). Further discussion may take place here.**
---
Linux. ParaView 3.0.2. File/Save Screenshot fails when the user tries to ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5516). Further discussion may take place here.**
---
Linux. ParaView 3.0.2. File/Save Screenshot fails when the user tries to save to a name that has two dots in it. This is at least true for .tif files. For instance, screenshot.two.tif will fail.
Nice to have fixed, but we have a good workaround.
https://gitlab.kitware.com/paraview/paraview/-/issues/5515CTH crashes when toggling down convert volume fraction2019-03-05T10:47:48-05:00Kitware RobotCTH crashes when toggling down convert volume fraction**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5515). Further discussion may take place here.**
---
I can get a consistent crash using ParaView 3.0.2, using CTH data. Crash ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5515). Further discussion may take place here.**
---
I can get a consistent crash using ParaView 3.0.2, using CTH data. Crash is as follows:
XP (Originally found using Linux)
ParaView version 3.0.2
* Open file 3D_Flat/spcth.spcth (file is 292,234 bytes)
* Turn on all cell data.
* Apply.
* Change from Outline to Surface. (Not sure if this step is necessary.)
* De-select the "Down Convert Volume Fraction" button.
* Apply.
Crash. (Sometimes it doesn't crash, but I am not sure if this is user error or an inconsistent crash.)
Before crash, # of cells is 27648 - as found in the Information tab.
After crash, # of cells is 33800 - as found in the Information tab.
Error is as follows:
ERROR: In \alan\paraviewWork\src3.0.2\ParaView3\Vtk\Filtering\vtkDataSet.cxx, line 432
vtkRectilinearGrid (03FD8530): Cell array Temperature (eV) with 1 components, has only 27648 tuples but there are 33800 cells
ERROR: In \alan\paraviewWork\src3.0.2\ParaView3\Vtk\Filtering\vtkExecutive.cxx, line 757
vtkCompositeDataPipeline (06933E50): Algorithm vtkPVGeometryFilter(04324B80) returned failure for request: vtkInformation (0696F878)
Debug: Off
Modified Time: 663038
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA
FORWARD_DIRECTION: 0
ALGORITHM_AFTER_FORWARD: 1
KEYS_TO_COPY: UPDATE_BLOCKS
FROM_OUTPUT_PORT: 0
https://gitlab.kitware.com/paraview/paraview/-/issues/5514Slider in Current Time Controls toolbar2019-03-05T10:47:48-05:00Kitware RobotSlider in Current Time Controls toolbar**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5514). Further discussion may take place here.**
---
It would be really handy to have a slider in the current time controls tool...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5514). Further discussion may take place here.**
---
It would be really handy to have a slider in the current time controls toolbar that would allow you to easily move large distances of time without having to type in a number or traverse time steps one at a time.https://gitlab.kitware.com/paraview/paraview/-/issues/5513Default keyframe values sometimes strange2019-03-05T10:47:48-05:00Kitware RobotDefault keyframe values sometimes strange**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5513). Further discussion may take place here.**
---
Do the following
1. Create a sphere source.
2. Create a keyframe for th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5513). Further discussion may take place here.**
---
Do the following
1. Create a sphere source.
2. Create a keyframe for the StartTheta property. The default values go from 0 to 360 (as you would expect).
3. Create a keyframe for the Radius property. The default values for this also go from 0 to 360, which is not what one would expect.
The values for the radius are clearly taken from the start theta. If you create the radius track first, the values go from 0 to 0.5, which is much more logical.https://gitlab.kitware.com/paraview/paraview/-/issues/5512Deleted track space not consumed2019-03-05T10:47:48-05:00Kitware RobotDeleted track space not consumed**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5512). Further discussion may take place here.**
---
When you delete a track from the animation view (which right now you can on...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5512). Further discussion may take place here.**
---
When you delete a track from the animation view (which right now you can only do by removing all of the keyframes within the animation inspector), the space that it was taken up by the tracks is not consumed by the panel. The current time line still descends down to where the track used to be. If there was a scroll bar, it scrolls down to empty space where the track used to be.https://gitlab.kitware.com/paraview/paraview/-/issues/5511In-place interpolation selection2019-03-05T10:47:48-05:00Kitware RobotIn-place interpolation selection**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5511). Further discussion may take place here.**
---
Open up the Animation Keyframes dialog box for one of the tracks in the Ani...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5511). Further discussion may take place here.**
---
Open up the Animation Keyframes dialog box for one of the tracks in the Animation View. In order to modify the interpolation, a dialog box is popped up. It would be much nicer if there was a combo box right in the table that you could use to select the interpolation directly.https://gitlab.kitware.com/paraview/paraview/-/issues/5510Missing track name for sub properties in glyphs2019-03-05T10:47:48-05:00Kitware RobotMissing track name for sub properties in glyphs**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5510). Further discussion may take place here.**
---
Do the following:
1. Create a glyph filter with spheres as its glyph typ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5510). Further discussion may take place here.**
---
Do the following:
1. Create a glyph filter with spheres as its glyph type.
2. Create a keyframe for the glyph radius (right now this can only be done in the animation inspector).
3. The track shows up in the animation view, but there is no name associated with it.https://gitlab.kitware.com/paraview/paraview/-/issues/5509Playback controls in animation view2019-03-05T10:47:48-05:00Kitware RobotPlayback controls in animation view**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5509). Further discussion may take place here.**
---
There are several playback controls critical to set up an animation: start ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5509). Further discussion may take place here.**
---
There are several playback controls critical to set up an animation: start and end times/indices, play mode, and frames/duration. Since the Animation View will undoubtedly be the mode of choice for setting up animations, it is inconvenient to go to the Animation Inspector to set these values.
Ideally these values would be added to the top of the animation view (similar to how they are shown in http://www.paraview.org/ParaQ/index.php/Animation_GUI). However, there is a good chance that these GUI components will not fit well in the panel. In this case, maybe the animation view could become a tabbed panel with one tab showing the tracks and the other showing the playback controls and animation settings. Another option would be to remove the track selection from the animation inspector and then default the location of the two views to be on top of each other (i.e., the dockable windows will be tabbed).https://gitlab.kitware.com/paraview/paraview/-/issues/5508No zoom controls in animation view2019-03-05T10:47:48-05:00Kitware RobotNo zoom controls in animation view**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5508). Further discussion may take place here.**
---
There is no way to adjust the "zoom level" of the tracks in the animation v...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5508). Further discussion may take place here.**
---
There is no way to adjust the "zoom level" of the tracks in the animation view. That is, the tracks are always shown from start time to end time. There needs to be a way to zoom in to show only a fraction of the actual animation time.
The design document at http://www.paraview.org/ParaQ/index.php/Animation_GUI gives a specification of what these zoom controls should look like.https://gitlab.kitware.com/paraview/paraview/-/issues/5507Out-of-order keyframes2019-03-05T10:47:48-05:00Kitware RobotOut-of-order keyframes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5507). Further discussion may take place here.**
---
The Animation Keyframes dialog box allows you to set arbitrary values for t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5507). Further discussion may take place here.**
---
The Animation Keyframes dialog box allows you to set arbitrary values for the time of each keyframe. This is good, but results in the possibility of keyframes that are out of order.
The keyframes should be reordered whenever the time of one is moved outside of the range of the surrounding keyframes. The correct interpolation used becomes a bit ambiguous. Just pick values that make sense based on the existing interpolation. They are easy enough to change if they are wrong.