ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-02-08T00:24:08-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/19239CSV writer: limit arrays to pass-through widget to arrays of selected a2020-02-08T00:24:08-05:00Utkarsh AyachitCSV writer: limit arrays to pass-through widget to arrays of selected a* disk_out_ref, check all variables, apply
* save data, choose csv, and check *Choose Arrays To Write*, you'll see the following widget
![image](/uploads/f03894e887090a1b798d480597f5e5e4/image.png)
Note the array selection shows cell ...* disk_out_ref, check all variables, apply
* save data, choose csv, and check *Choose Arrays To Write*, you'll see the following widget
![image](/uploads/f03894e887090a1b798d480597f5e5e4/image.png)
Note the array selection shows cell arrays, but since **Field Association** is set to **Points**, cell arrays won't be saved and hence should not be shown in the widget.https://gitlab.kitware.com/paraview/paraview/-/issues/13604Abaqus odb reader needed2020-01-28T14:43:40-05:00Kitware RobotAbaqus odb reader needed**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13604). Further discussion may take place here.**
---
I have a user that would like to read Abaqus odb files. Please add a read...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13604). Further discussion may take place here.**
---
I have a user that would like to read Abaqus odb files. Please add a reader.
Alanhttps://gitlab.kitware.com/paraview/paraview/-/issues/19156Settings does not scale correctly2019-07-18T13:53:08-04:00W. Alan ScottSettings does not scale correctlySettings dialogs do not scale correctly with Edit/ Settings/ Scale font.
* Linux, 5.7.0-RC1, local server.Settings dialogs do not scale correctly with Edit/ Settings/ Scale font.
* Linux, 5.7.0-RC1, local server.https://gitlab.kitware.com/paraview/paraview/-/issues/19143Hard to select directory for state file inputs2019-07-03T10:07:59-04:00Kenneth MorelandHard to select directory for state file inputsWhen you load a state file, one of the handy options is to select a directory from which to load files so that you can transfer a state file from one computer to another with a different file system. However, when you try to select a dir...When you load a state file, one of the handy options is to select a directory from which to load files so that you can transfer a state file from one computer to another with a different file system. However, when you try to select a directory to use with the file browser, it is more difficult than it should be. You should be able to browse to the directory and hit `OK`, but you cannot.
To demonstrate, download this state file that loads a file in the `Examples` directory distributed with ParaView: [FieldAtTime0.pvsm](/uploads/6ba60a3b24c846f0dc9aa2b6d1c6cf55/FieldAtTime0.pvsm).
1. `File` -> `Load State...`
2. Select the [FieldAtTime0.pvsm](/uploads/6ba60a3b24c846f0dc9aa2b6d1c6cf55/FieldAtTime0.pvsm) that you downloaded.
3. Change `Load State Data File Options` to `Search files under a specified directory`.
4. Click the `...` button next to the new `Data Directory` option to open the file browser.
5. In the file browser, double-click the `Examples` directory in the list of common system directories. This is the directory you want to select.
At this point you should be able to just select `OK` to select this directory. But you can't. You have to go up a directory, then select the subdirectory, and then click `OK`, which is awkward as heck. Compare that to a normal system file browser in directory mode. (For example, you can see it in the CMake GUI when selecting a directory.)
The way it should work is for the `OK` button to be active if no files/directories are selected. In this case, the currently navigated folder will be selected.https://gitlab.kitware.com/paraview/paraview/-/issues/18332Feature to change 2d linechartview background2018-07-30T13:45:17-04:00W. Alan ScottFeature to change 2d linechartview backgroundPlease add the ability to customize the background of 2d linechartviews. Probably should do this through a palette, not the Properties tab background.Please add the ability to customize the background of 2d linechartviews. Probably should do this through a palette, not the Properties tab background.https://gitlab.kitware.com/paraview/paraview/-/issues/16893mouse zoom is confusing/ wrong with animation/ follow data2018-02-26T13:15:57-05:00W. Alan Scottmouse zoom is confusing/ wrong with animation/ follow dataThe mouse zoom is confusing/ wrong with the animation view/ add camera track/ follow data. The primary issue is that zooming with the left mouse button and zooming with the wheel act differently. This is extremely confusing to users, a...The mouse zoom is confusing/ wrong with the animation view/ add camera track/ follow data. The primary issue is that zooming with the left mouse button and zooming with the wheel act differently. This is extremely confusing to users, and needs to be fixed. Two options would work - some type of a popup warning telling users they are zooming with the wheel rather than the right button, or make the behavior the same.
Here is how to replicate.
* Linux, master, local server.
* Open can.exo. Apply.
* Rotate the can around. Select a half dozen cells on the lower part of the can.
* Extract selection. Apply.
* Reset.
* (Note that ExtractSelection should still be selected in the Pipeline Browser)
* View/ Animation View/ New track/ Camera/ Follow Data/ +
* Turn visibility on for can.exo in the pipeline browser.
* Not necessary, but definately pretty - change variable to GlobalNodeId.
* Play. Note that we stay zoomed on the extract selection elements. This is as it should be.
* Zoom out with the right mouse button. Play. Note what happens to the view - it resets to have the Extract Selection fill the view. This is as it should be.
* Zoom out with the mouse wheel. Play. Notice what happens to the view - nothing. This is NOT as it should be.https://gitlab.kitware.com/paraview/paraview/-/issues/16773Add colors to pov file2018-02-26T13:15:56-05:00Kitware RobotAdd colors to pov file**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16773). Further discussion may take place here.**
---
From a user:
At the moment, ParaView will output a .pov file that I can...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16773). Further discussion may take place here.**
---
From a user:
At the moment, ParaView will output a .pov file that I can render into an image, but the coloring of the objects are not retained. As it is, all objects are written out as one giant mesh2 block, and that gets assigned one solid color at the end of that block. Using the POVray export feature is useful for rendering a high-quality images with different textures, finishes, etc., but not useful for displaying meaningful data that has coloring (e.g. color some object by pressure, or temperature). The following link on mesh2 objects suggests that it is possible to retain color thorough the addition of a “texture_list”: http://www.povray.org/documentation/view/3.6.0/68/. This is where my knowledge ends, so I’m not sure how difficult of a task it would be to gather the coloring information for each block face, and relay that to the .pov file that gets generated.Chet NieterChet Nieterhttps://gitlab.kitware.com/paraview/paraview/-/issues/15808Add ability to show block names in spreadsheet view2018-02-26T13:15:56-05:00Kitware RobotAdd ability to show block names in spreadsheet view**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15808). Further discussion may take place here.**
---
Please add the ability to show block names in the spreadsheet view, on the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15808). Further discussion may take place here.**
---
Please add the ability to show block names in the spreadsheet view, on the Point and Cell page.https://gitlab.kitware.com/paraview/paraview/-/issues/15646Dragging text annotation creates too many undo events2018-02-26T13:15:55-05:00Kitware RobotDragging text annotation creates too many undo events**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15646). Further discussion may take place here.**
---
When you click and drag a text annotation to move it to another part of th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15646). Further discussion may take place here.**
---
When you click and drag a text annotation to move it to another part of the screen, it should create a single undo event to restore the annotation to its initial position. Instead, an undo event appears to be created for each mouse event the GUI received. To replicate, do the following.
1. Sources -> Text. Apply.
2. Drag the text annotation to another part of the view far away.
3. Press Undo.
The undo should restore the text to its initial position. Instead, it moves it a little bit. Continuing to press Undo moves the text incrementally to its start, but the undo stack probably maxes out before then.https://gitlab.kitware.com/paraview/paraview/-/issues/15510Python Annotation Filter in custom filter generate table2018-02-26T13:15:55-05:00Kitware RobotPython Annotation Filter in custom filter generate table**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15510). Further discussion may take place here.**
---
(Git master versin, as well in 4.3.1)
Putting an Python Annotation Filter...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15510). Further discussion may take place here.**
---
(Git master versin, as well in 4.3.1)
Putting an Python Annotation Filter in a custom filter, then using this new custom filter will only generate table data.
How to reproduce:
Create a source
Add a python annotation , using "Test" as a expression, Apply
Create a custom filter with the python annotation filter
Add the new custom filter to the source, Apply
What is seen:
A new spreadsheet view open showing the "Test" data, the icon of the custom filter is a table
What is expected:
Th render view should show a "Test" Annotation, the custom filter icon should be a "green cube" like standard filter.https://gitlab.kitware.com/paraview/paraview/-/issues/15226Add tool bar button for annotate time, and other annotations2018-02-26T13:15:55-05:00Kitware RobotAdd tool bar button for annotate time, and other annotations**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15226). Further discussion may take place here.**
---
Please add a tool bar button to annotate time. If a person has time data,...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15226). Further discussion may take place here.**
---
Please add a tool bar button to annotate time. If a person has time data, they will very often want this on.
Also, I have asked for additional annotations in bug 13645. Maybe make a button that goes to a dialog box that gives all of these items as options?https://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/13644Add continuous spin mode2018-02-26T13:15:53-05:00Kitware RobotAdd continuous spin mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13644). Further discussion may take place here.**
---
A cool feature in VisIt is spin mode. Click this icon (toggle on), and th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13644). Further discussion may take place here.**
---
A cool feature in VisIt is spin mode. Click this icon (toggle on), and then click in the 3d window. The 3d object will slowly spin in space. If you click/drag, the rotation will be in the direction and speed of your click.https://gitlab.kitware.com/paraview/paraview/-/issues/13338Algorithm for polygon faceting for polyhedral finite elements2018-02-26T13:15:53-05:00Kitware RobotAlgorithm for polygon faceting for polyhedral finite elements**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13338). Further discussion may take place here.**
---
This is a request for a minor(?) alter in a VTK rendering algorithm.
...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13338). Further discussion may take place here.**
---
This is a request for a minor(?) alter in a VTK rendering algorithm.
Polyhedral finite elements are reaching a level of numerical maturity where
their use is likely to become widespread -- and correspondingly an
increased desire to display them in ParaView. For convex polygonal faces of
a polyhedron, the VTK algorithms work fine, and omitting the interior
triangle edges was a nice rendering improvement.
However, the discrete numerical algorithms that have emerged surprisingly
work for polyhedrons that have the "star property." Long story told short,
the attached ParaView figure in the right hand panel contains a polyhedral
finite element that has a non-planar, concave polygonal face. Numerically,
this polyhedral configuration works very well.
Would it be possible for rendering purposes, to create the polygon's
triangular sub-facets by starting with the polygon's vertex closest to the
average coordinate of the polygon's vertex nodal points? Maybe this
particular polygon vertex becomes a "common" vertex for all of the
sub-triangles?
Samuel W. Key
FMA Development, LLC
(Sandia contractor)