ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-03-05T10:38:57-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/11146saving animation from python doesn't capture all views2019-03-05T10:38:57-05:00Kitware Robotsaving animation from python doesn't capture all views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11146). Further discussion may take place here.**
---
When you have multiple views and try to save an animation from python it b...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11146). Further discussion may take place here.**
---
When you have multiple views and try to save an animation from python it behaves nonsensically.
If you have more two 3d views side by side it will save only the active view. If you then add a plot view it will save all of the views, but the plot view area will be black. If you are running in batch mode it behaves entirely differently.
It should save the plot views.
It should default to saving all of the visible views.
It should do something intelligent in batch mode such as saving all views simply laid out in a strip automatically.
https://gitlab.kitware.com/paraview/paraview/-/issues/11139Slice Representation crash2019-03-05T10:38:57-05:00Kitware RobotSlice Representation crash**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11139). Further discussion may take place here.**
---
1. Extract bigoutx100x100x100.vtk.bz2
2. Open bigoutx100x100x100.vtk from...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11139). Further discussion may take place here.**
---
1. Extract bigoutx100x100x100.vtk.bz2
2. Open bigoutx100x100x100.vtk from ParaView
3. Make bigoutx100x100x100.vtk visible
4. From the Object Inspector -> Display choose Slice Representationhttps://gitlab.kitware.com/paraview/paraview/-/issues/11138Python: Support loading lookup table xml files from python2019-03-05T10:38:57-05:00Kitware RobotPython: Support loading lookup table xml files from python**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11138). Further discussion may take place here.**
---
Python: Support loading lookup table xml files from python. The xml files ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11138). Further discussion may take place here.**
---
Python: Support loading lookup table xml files from python. The xml files are the ones saved from the lookuptable mananger in the GUI.
https://gitlab.kitware.com/paraview/paraview/-/issues/11135Issues with Block Selection GUI.2019-03-05T10:38:57-05:00Kitware RobotIssues with Block Selection GUI.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11135). Further discussion may take place here.**
---
* Open can.ex2
* Apply extract block
* click on the "root" node. It ente...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11135). Further discussion may take place here.**
---
* Open can.ex2
* Apply extract block
* click on the "root" node. It enters a tri-state, when it should only toggle from checked to unchecked state.https://gitlab.kitware.com/paraview/paraview/-/issues/11133Improved CompositeData support in ParaView2019-03-05T10:38:57-05:00Kitware RobotImproved CompositeData support in ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11133). Further discussion may take place here.**
---
Avoid appending of blocks for rendering
vtkPVGeometryFilter appends bl...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11133). Further discussion may take place here.**
---
Avoid appending of blocks for rendering
vtkPVGeometryFilter appends blocks before rendering. We need to avoid that. That will save initial render time.
Fix selection to work with non-appended geometry.
Fix Ordered compositing to work with composite datasets.https://gitlab.kitware.com/paraview/paraview/-/issues/11117Color legend needs to be wider of use smaller fonts2019-03-05T10:38:57-05:00Kitware RobotColor legend needs to be wider of use smaller fonts**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11117). Further discussion may take place here.**
---
I have a user that has made complaints about font layout on the color scal...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11117). Further discussion may take place here.**
---
I have a user that has made complaints about font layout on the color scale editor. After looking at it, I think he has a seed of truth to his complaint.
Use case:
ParaView trunk, local server, Windows.
Open disk_out_ref.exo.
Calculator. Use GlobalNodeId*1e6-1e6+1.2345678 in the formula.
Color Legend.
With Windows, if you make ParaView non full screened, and grab the right edge of the ParaView Window, and move it slowly left and right, you will see that the max values will bounce from 1 to 2 digits. Either the Color Legend needs to be widened so this doesn't happen, or the the font needs to be smaller so this doesn't happen. Min and Max should never have fewer than 2 digits of precision.
See attached screenshot. Note that I was using the default width for the color editor.https://gitlab.kitware.com/paraview/paraview/-/issues/11115Color legend has too many digits in the exponent.2019-03-05T10:38:58-05:00Kitware RobotColor legend has too many digits in the exponent.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11115). Further discussion may take place here.**
---
I have a user that has made complaints about font layout on the color scal...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11115). Further discussion may take place here.**
---
I have a user that has made complaints about font layout on the color scale editor. After looking at it, I think he has a seed of truth to his complaint.
Use case:
ParaView trunk, local server, Windows.
Open disk_out_ref.exo.
Calculator. Use GlobalNodeId*1e6-1e6+1.2345678 in the formula.
Turn on the color legend.
* Bug - On windows, when the data needs an exponent, there are three digits of precision in the exponent. This is excessive, and should be 2.
See attached screenshot.
https://gitlab.kitware.com/paraview/paraview/-/issues/11107Color scale font layout could be improved2019-03-05T10:39:04-05:00Kitware RobotColor scale font layout could be improved**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11107). Further discussion may take place here.**
---
I have a user that has made complaints about font layout on the color scal...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11107). Further discussion may take place here.**
---
I have a user that has made complaints about font layout on the color scale editor. After looking at it, I think he has a seed of truth to his complaint. I will post his comments at the end of this report, but realize that he is thinking if terms of data precision - not character spaces. Thus, here is my proposal.
Use case:
ParaView trunk, local server, Windows.
Open disk_out_ref.exo.
Calculator. Use GlobalNodeId*1e6-1e6+1.2345678 in the formula.
* Bug - we only get one digit of precision when using scientific notation, but 3 on the exponent. A problem is that this always gives a maximum that is repeated somewhere down the color scale. Example - 8e+009
* Solution - what I want - lets try using something like %-#6.2g, giving at least 2 digits of precision when using exponents. Example - 8.5e+009, or better yet, 8.5e+09. Furthermore, we would now get the same number of digits of precision for the min and max - i.e., 1.2 to 8.5e+09.
* Bug - when you turn "Automatic Label Format" off, everything jumps - due to a different output format being used.
* Solution - The "default" for auto formatting off should be the same as auto formatting on.
* Bug - min number and max number font size should always be the same size.
* Example - change the font size to 18. No matter what the user asks for, use the closest to requested size that is usable for min and max.
* Another possible bug - I have seen cases where the font size through the numbers for the ticks is different size. We should figure out ONE font size that will work for all ticks, and use that. Note that I could not replicate with a vertical color legend. https://gitlab.kitware.com/paraview/paraview/-/issues/11100LOD delay should be configurable2019-03-05T10:39:04-05:00Kitware RobotLOD delay should be configurable**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11100). Further discussion may take place here.**
---
ParaView now delays changing from LOD to full resolution. This delay shou...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11100). Further discussion may take place here.**
---
ParaView now delays changing from LOD to full resolution. This delay should be configurable. For instance, for my system, a delay of 0.2 seconds would be fine. The current 2 seconds is extreme.https://gitlab.kitware.com/paraview/paraview/-/issues/11097histogram crash on master2019-03-05T10:39:04-05:00Kitware Robothistogram crash on master**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11097). Further discussion may take place here.**
---
ParaView trunk, local server, Windows.
Open ParaView 3.8 dataset (from ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11097). Further discussion may take place here.**
---
ParaView trunk, local server, Windows.
Open ParaView 3.8 dataset (from the ParaView download page) named dualSphereAnimation.pvd. Apply.
Filters/ Data Analysis/ Histogram. Apply.
Move mouse over 2d and 3d windows. ParaView will crash. https://gitlab.kitware.com/paraview/paraview/-/issues/11096NRRD reader fails with windows line endings2019-03-05T10:39:04-05:00Kitware RobotNRRD reader fails with windows line endings**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11096). Further discussion may take place here.**
---
When you create a NRRD header file on a typical windows text editor, it ad...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11096). Further discussion may take place here.**
---
When you create a NRRD header file on a typical windows text editor, it adds CRLF line endings. The NRRD reader is splitting lines on the LF only and not stripping out the CR. This makes string comparisons to things like data type fail. For example, when loading the attached aneurism.nhdr file, you get an error like
Generic Warning: In ..\..\..\..\src\ParaView3\VTK\Parallel\vtkPNrrdReader.cxx, line 192
Unknown type: unsigned char
https://gitlab.kitware.com/paraview/paraview/-/issues/11091Slice representation does not turn off map scalars2019-03-05T10:39:04-05:00Kitware RobotSlice representation does not turn off map scalars**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11091). Further discussion may take place here.**
---
In general, if vectors of unsigned char are drawn as scalars, ParaView wil...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11091). Further discussion may take place here.**
---
In general, if vectors of unsigned char are drawn as scalars, ParaView will assume that these are colors, turn off the "Map Scalars" option, and draw the vectors directly as colors. That is, most of the time. I noticed that when you load in a 3D volume of unsigned char data and then view it with the slice representation, the colors are mapped. To replicate, do the following:
1. Load the attached file (aneurism_subsampled.vti). Apply.
2. Change representation from Outline to Slice.
3. Go to the Display panel and browse through the slices. Note that they are all mapped through the default color map. Also note that Map Scalars is checked.
4. Apply the slice filter.
5. Note that the slice is colored by the grayscales in the image (as it should be). Also note that Map Scalars is now off.https://gitlab.kitware.com/paraview/paraview/-/issues/11090Color legend misleading when not mapping scalars2019-03-05T10:39:04-05:00Kitware RobotColor legend misleading when not mapping scalars**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11090). Further discussion may take place here.**
---
When you draw data with unsigned char vectors, ParaView by default treats ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11090). Further discussion may take place here.**
---
When you draw data with unsigned char vectors, ParaView by default treats those as color vectors and draws them directly as colors rather than sending them through a color map (which can be toggled with the "Map Scalars" display option).
That behavior is correct, but when that is happening, the user can still click the Color Legend and Edit Colors toolbar buttons to display the scalar bar and edit the colors in it. This is misleading as those colors are meaningless for the current rendering of the data. When viewing data with the "Map Scalars" option on, these two toolbar buttons should be grayed out. If Map Scalars is turned off and the color bar is visible, it should be implicitly made invisible.
To replicate, load in the Arrow.png baseline image in the ParaViewData directory, apply, then turn on the color map. Misleading as those colors have nothing to do with those shown.https://gitlab.kitware.com/paraview/paraview/-/issues/11087Data is bad for raw image files2019-03-05T10:39:04-05:00Kitware RobotData is bad for raw image files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11087). Further discussion may take place here.**
---
ParaView trunk, local server, windows.
Download the file aneurism.raw fro...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11087). Further discussion may take place here.**
---
ParaView trunk, local server, windows.
Download the file aneurism.raw from http://www.gris.uni-tuebingen.de/edu/areas/scivis/volren/datasets/datasets.html.
Although not necessary, this bug is obvious if you open the Color Editor, then change Choose Preset to the Blue to Red rainbow.
You must follow the following steps, or the bug goes away.
Open with ParaView, Data Scalar Type is Unsigned Char, Data extents are 0-255, 0-255, 0-255. Apply.
Slice, Apply. Turn off show plane. Turn off eyeball for aneurism.raw dataset.
Click on the Color Legend.
Bug - notice that we are just seeing a grayscale, from white to black. But, there is no black, gray or white in the selected color map!
I am marking this as important, since it is incorrectly changing how data is represented.
https://gitlab.kitware.com/paraview/paraview/-/issues/11082Bilinear functions over QUADs rendered incorrectly2019-03-05T10:39:04-05:00Kitware RobotBilinear functions over QUADs rendered incorrectly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11082). Further discussion may take place here.**
---
Hi,
I created a 5x5 uniform grid of quadrilaterals on the unit square a...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11082). Further discussion may take place here.**
---
Hi,
I created a 5x5 uniform grid of quadrilaterals on the unit square and wrote a VTK (.vtu) file with data symmetric w.r.t. the midpoint of the square.
In each of the quadrilaterals, I expected the function to be rendered as a bilinear function. This seems to happen, except for the elements in the corners of the domain. This way, the solutions appears asymmetric.
The VTK file is attached.
Cheers,
Nicohttps://gitlab.kitware.com/paraview/paraview/-/issues/11073Extract Surfaces filter not working correctly on imported fluent.cas files2019-03-05T10:39:04-05:00Kitware RobotExtract Surfaces filter not working correctly on imported fluent.cas files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11073). Further discussion may take place here.**
---
I import an ASCII format Fluent Case (*.cas) file, with it's companion .da...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11073). Further discussion may take place here.**
---
I import an ASCII format Fluent Case (*.cas) file, with it's companion .dat file.
I then perform an 'extract surfaces' filter. The true surface is extracted, but some grid connectivity must be lost in the import, as there are curious artefacts on the surface - faces of cells adjacent to the true surface are also extracted, resulting in the 'double surface' or 'castellation' shown in the attached image.
I can supply a Case file and Paraview state file featuring this problem if required (~310mb in zipped form).https://gitlab.kitware.com/paraview/paraview/-/issues/11072Float value limitation in Server/Client Mode2019-03-05T10:39:04-05:00Kitware RobotFloat value limitation in Server/Client Mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11072). Further discussion may take place here.**
---
While loading an Ascii vtu files in Client(win32)/server mode(Linux):
val...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11072). Further discussion may take place here.**
---
While loading an Ascii vtu files in Client(win32)/server mode(Linux):
values smaller than "1.e-45" cannot be loaded if "Float32" in the block header.
but:
====
-same problem in local (Linux32 and linux64)
-works fine in local (Windows32).
-works fine in local and server/client if "Float64" in the header (but double the file size)https://gitlab.kitware.com/paraview/paraview/-/issues/11070Crash client/server when plugins don't match2019-03-05T10:39:04-05:00Kitware RobotCrash client/server when plugins don't match**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11070). Further discussion may take place here.**
---
Linux, remote servers (4), trunk.
Special setup of ParaView:
* Clien...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11070). Further discussion may take place here.**
---
Linux, remote servers (4), trunk.
Special setup of ParaView:
* Client - Go into lib/paraview3.9. Edit .plugins. Turn on the following plugins: Moments, pvblot, PointSprite_Plugin, and H5PartReader.
* Server - Have nothing in the lib/paraview3.9/plugins directory.
OK, start ParaView client/ remote server. Open can.exo. All vars on. Apply.
Crash.
I suppose this could be put off until 3.10 if a fix isn't simple, but we would need to document this VERY LOUDLY somewhere - maybe the wiki? It took some time to figure out what it was.
This bug has been around since 3.8.0.
https://gitlab.kitware.com/paraview/paraview/-/issues/11068toolbar that calls macros2019-03-05T10:39:04-05:00Kitware Robottoolbar that calls macros**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11068). Further discussion may take place here.**
---
We should add the ability to create a toolbar, with buttons that just call...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11068). Further discussion may take place here.**
---
We should add the ability to create a toolbar, with buttons that just call python scripts. This could do such things as Read in a file in wireframe mode, or wireframe mode, cull front faces.https://gitlab.kitware.com/paraview/paraview/-/issues/11067surface with blocks2018-08-28T09:39:51-04:00Kitware Robotsurface with blocks**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11067). Further discussion may take place here.**
---
My user has requested that we add another representation for CTH data. In...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11067). Further discussion may take place here.**
---
My user has requested that we add another representation for CTH data. Instead of Surface with Edges (which draws lines around every surface cell), he wants Surface with Blocks (solid, then drawing lines around each surface block).