ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2017-11-22T15:14:21-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/15875Color legend doesn't show very small data2017-11-22T15:14:21-05:00Kitware RobotColor legend doesn't show very small data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15875). Further discussion may take place here.**
---
The color legend fails with very small data. For analysts working wit...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15875). Further discussion may take place here.**
---
The color legend fails with very small data. For analysts working with atoms, this fails. There are two ways to replicate this, both need to be fixed.
* 4.4.0, local server, Windows
* Wavelet. Apply.
* Calculator. Use formula RTData*1e-20. Apply. Surface, color by Result.
>> Bug - Rescale to Data Range. Notice that the max should be something e-19, but it is stuck at 1e-16.
>> Bug - Rescale to custom range. Try to change the max to be 1e-17. It fails.5.2 (SC-16)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/5402Color legend doesn't track what is visible2019-03-05T10:48:08-05:00Kitware RobotColor legend doesn't track what is visible**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5402). Further discussion may take place here.**
---
Open can.exo. Turn on all variables. Apply. Clip. Apply. Change color ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5402). Further discussion may take place here.**
---
Open can.exo. Turn on all variables. Apply. Clip. Apply. Change color to cellNormals. In the Pipeline Browser, click on can.exo, turn on this eye, turn off the other eye. Toggle color legend visibility. BlockId will now come on. Unselect can.exo eyeball, select clip eyeball. Wrong. Turn off color legend visibility, then back on. Still wrong. The user has to understand that the eyeball does not effect visibility of the color legend - only the pipeline browser highlighting does.
A user mentioned that this was very risky, since they could think they were looking at one color legend when they were looking at a different one.https://gitlab.kitware.com/paraview/paraview/-/issues/14557Color legend doesn't update properly2018-08-08T22:26:06-04:00Kitware RobotColor legend doesn't update properly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14557). Further discussion may take place here.**
---
Marking high, since this can misrepresent data. Must be fixed for 4.2.
...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14557). Further discussion may take place here.**
---
Marking high, since this can misrepresent data. Must be fixed for 4.2.
Linux, master, local server.
Open can.exo. All vars on. Apply.
Color by EQPS. Color legend on. Show Color Editor.
Rescale to data range over all timesteps.
Do exactly as follows:
Click Yes. Don't move the mouse. Min and Max on EQPS has not changed.
Slowly move the mouse right, over the color legend. Color legend will update. This doesn't need clicking the Update icon. Either it should automatically update, or it should require clicking the Update icon.
If I had my preference, both Rescale to Data Range (on the toolbars and in the Color Map Editor) and Rescale to Data Range over All Timesteps would automatically apply.
This is a bug.
https://gitlab.kitware.com/paraview/paraview/-/issues/14646Color legend doesn't work correctly if it's laid out horizontally by default.2018-08-08T22:26:01-04:00Kitware RobotColor legend doesn't work correctly if it's laid out horizontally by default.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14646). Further discussion may take place here.**
---
+ Load attached state. This is state with a horizontally laid out scalar b...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14646). Further discussion may take place here.**
---
+ Load attached state. This is state with a horizontally laid out scalar bar.
+ If you move your mouse over the scalar bar, you'll see handles that allow you to resize the scalar bar vertically, that's wrong!! The handles should have allowed use to resize the scalar bar horizontally. The handles are expected to allow the user to resize the scalar bar along the length, irrespective of the orientation.
+ If you restart ParaView and manually setup a horizontal scalar bar by interacting with it, the handles work as expected.
This needs to be fixed soon since we're working on changing how the scalar bars are placed and oriented by default.https://gitlab.kitware.com/paraview/paraview/-/issues/21264Color legend dragging no longer works when first clicked2022-04-27T22:15:12-04:00Cory Quammencory.quammen@kitware.comColor legend dragging no longer works when first clickedParaView behavior as of this MR: !5348
* Run ParaView builtin server
* Add Wavelet
* Color by RTData to make the color legend appear
* Click on the color legend. You used to be able to drag it to position it at least as far back as Para...ParaView behavior as of this MR: !5348
* Run ParaView builtin server
* Add Wavelet
* Color by RTData to make the color legend appear
* Click on the color legend. You used to be able to drag it to position it at least as far back as ParaView 5.7. Now you cannot.5.11 (Spring 2022)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/19831Color legend font sizes wrong with batch2020-09-30T19:00:44-04:00W. Alan ScottColor legend font sizes wrong with batchColor legend font sizes are wrong with batch. Here is how to replicate. I am sure it doesn't matter, but I am going to create a slice, with surface with edges.
* Linux, 5.8.0, builtin server.
* Start trace. Take defaults.
* Load disk_...Color legend font sizes are wrong with batch. Here is how to replicate. I am sure it doesn't matter, but I am going to create a slice, with surface with edges.
* Linux, 5.8.0, builtin server.
* Start trace. Take defaults.
* Load disk_out_ref.exo. All variables on. Apply.
* Slice. Z Normal. Hide plane tool. Apply.
* Color by Temp.
* Surface with Edges.
* Now, drag the color legend to the middle, bottom of the view. I want it to be horizontal.
* Save Screenshot.
* Stop trace. Uncomment the ViewSize command. Save somewhere as myTrace.py.
* Rename your screenshot from above to screenshotOriginal.png
* /.../pvbatch /.../myTrace.py
If you compare the screenshot from pvbatch and the original, you will see that the color legend text is different sizes. This is a bug.
This is possibly related to #198165.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/12899Color legend has no numbers with log scale2018-08-23T15:17:14-04:00Kitware RobotColor legend has no numbers with log scale**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12899). Further discussion may take place here.**
---
ParaView trunk. Linux. Local server.
Whipple_Shield 32, all vars on, ap...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12899). Further discussion may take place here.**
---
ParaView trunk. Linux. Local server.
Whipple_Shield 32, all vars on, apply.
Filters/ Cell data to point data.
Contour. VOLFRC1. 0.1. Apply.
Color by pressure. Turn on color legend. Color editor/ Use logarithmic scale.
The color bar has no numbers or ticks, except the max and min.
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/14913Color legend incorrectly keeps visibility2018-08-08T22:25:44-04:00Kitware RobotColor legend incorrectly keeps visibility**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14913). Further discussion may take place here.**
---
the color legend incorrectly keeps visibility. This is really confusing, ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14913). Further discussion may take place here.**
---
the color legend incorrectly keeps visibility. This is really confusing, thus lets try to fix for 4.2.
* Master, Linux, local server.
* can.exo. All vars on. Apply.
* Move forward one timestep, placing reasonable data in the variables.
* Color by ACCL.
* To make bug glaringly obvious, drag the Color Legend into the middle of the screen
-- Note - notice where the Color Legend is.
* Color by Solid Color.
<<Bug>> Now, slide your mouse over the area of the now hidden Color Legend. Mouse focus changes, and you can no longer control the 3d window.
* Color by DISPL. The Color Legend will appear in the lower right corner.
<<Bug>> The now hidden ACCL Color Legend still blocks interaction with the 3d window!
Lets fix this for 4.2https://gitlab.kitware.com/paraview/paraview/-/issues/15667Color legend is crazy for very precise data.2017-11-30T11:37:59-05:00Kitware RobotColor legend is crazy for very precise data.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15667). Further discussion may take place here.**
---
The color legend gives crazy number of digits of precision.
* Linux, ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15667). Further discussion may take place here.**
---
The color legend gives crazy number of digits of precision.
* Linux, master, local server.
* Open can.exo. All vars on. Apply.
* Calculator filter. Use formula: GlobalElementId*0.000001+1
* Color by Result.
We don't need 20 characters of precision!!!!
Please make the default "automatic mode" the same as the suggested non automatic mode on the Color Legend Editor - i.e., %-#6.3g
https://gitlab.kitware.com/paraview/paraview/-/issues/17447Color legend is insanely small for can example visualization2017-06-28T16:57:35-04:00W. Alan ScottColor legend is insanely small for can example visualization* Windows, 5.4.0-RC2, local server. Binary from Kitware website.
* Run ParaView -dr (or delete config files).
* From splash screen, Example Visualizations. Can (i.e., left) example.
* Color Legend fonts are insanely small.
* Click...* Windows, 5.4.0-RC2, local server. Binary from Kitware website.
* Run ParaView -dr (or delete config files).
* From splash screen, Example Visualizations. Can (i.e., left) example.
* Color Legend fonts are insanely small.
* Click on Clip2. Edit color legend. Font sizes are 7. Restore Settings, now fonts are a reasonable 16.
At least the examples in Example Visualization should work correctly. Marking appropriately.5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/11573color legend is not getting updated in all windows of the multiview when they...2019-03-05T10:38:31-05:00Kitware Robotcolor legend is not getting updated in all windows of the multiview when they get rescaled**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11573). Further discussion may take place here.**
---
When the color legend is rescaled, the behavior with multiple views is tha...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11573). Further discussion may take place here.**
---
When the color legend is rescaled, the behavior with multiple views is that all views that have a color legend of the same variable should have the same range. This doesn't happen on changing the scale and I have to change the active view before it does.
The included picture shows the problem.https://gitlab.kitware.com/paraview/paraview/-/issues/16082Color legend labels are wacked2017-11-22T15:14:18-05:00Kitware RobotColor legend labels are wacked**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16082). Further discussion may take place here.**
---
Color legend labels are wacky on the current nightly. ParaView-5.0.1-345-...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16082). Further discussion may take place here.**
---
Color legend labels are wacky on the current nightly. ParaView-5.0.1-345-gdc79ae2-Qt4-OpenGL2-MPI-Linux-64bit.
* Linux, local server, nightly.
* Open bake.e. Apply.
* The color legend annotations are huge, and don't fit properly. This worked on 5.0.1.
https://gitlab.kitware.com/paraview/paraview/-/issues/13130color legend layout should allow manual control2018-08-23T15:17:06-04:00Kitware Robotcolor legend layout should allow manual control**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13130). Further discussion may take place here.**
---
We need to add the ability to manually set the color legend to be horizont...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13130). Further discussion may take place here.**
---
We need to add the ability to manually set the color legend to be horizontal or vertical. Currently this is automatic, which is problematic if you need numerous, horizontal color legends on the right side of the screen. https://gitlab.kitware.com/paraview/paraview/-/issues/14835Color legend log minimum color is wrong2018-08-08T22:25:47-04:00Kitware RobotColor legend log minimum color is wrong**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14835). Further discussion may take place here.**
---
When a user has positive data that is to be logged, and includes 0 or nega...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14835). Further discussion may take place here.**
---
When a user has positive data that is to be logged, and includes 0 or negative data, ParaView will arbitrarily change this the minimum to 1. Please add more intelligence to this algorithm. What I would like is as follows:
If (data is all positive)
Leave algorithm as is.
else (i.e., we have 0 or negative data)
Possible-Min = max/(1e-4)
If (Possible-Min < 1)
Minimum = Possible-Min
Else
Minimum = 1https://gitlab.kitware.com/paraview/paraview/-/issues/14837Color legend log ranges - advanced2020-05-06T17:18:47-04:00Kitware RobotColor legend log ranges - advanced**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14837). Further discussion may take place here.**
---
Here is an e-mail thread created about modifications to the min and max co...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14837). Further discussion may take place here.**
---
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/15069Color legend marks are crazy.2017-12-04T12:46:55-05:00Kitware RobotColor legend marks are crazy.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15069). Further discussion may take place here.**
---
The color legend marks calculator is crazy. I realize that this is a hard...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15069). Further discussion may take place here.**
---
The color legend marks calculator is crazy. I realize that this is a hard problem, but what we have isn't correct. Here is an example, with two screenshots.
Linux, 4.2.0, local server.
* Load can.exo. Apply.
* Last time step. Color by ACCL.
* The next part is dependent on the size of ParaView - thus, varies. I manually change the color range to be 4000 to 2e8th, and get a minimum and maximum tick mark, and one in the middle. Changing the range to be 4100 to 2e8, I see a minimum and maximum, and 4 in the middle. There is a huge jump here, with font rescaling and everything. It is very disruptive. Please make it transition better.
https://gitlab.kitware.com/paraview/paraview/-/issues/14679color legend master bug2018-08-08T22:25:59-04:00Kitware Robotcolor legend master bug**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14679). Further discussion may take place here.**
---
This is a master bug that I will hang others from. This pertains to bugs/...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14679). Further discussion may take place here.**
---
This is a master bug that I will hang others from. This pertains to bugs/features/ corrections/ enhancements with the color legend.https://gitlab.kitware.com/paraview/paraview/-/issues/12643color legend memory leak2019-03-05T10:36:49-05:00Kitware Robotcolor legend memory leak**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12643). Further discussion may take place here.**
---
After using paraview for several weeks (Mac OS 10.4 and 10.5; ParaView v3....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12643). Further discussion may take place here.**
---
After using paraview for several weeks (Mac OS 10.4 and 10.5; ParaView v3.8.X and 3.10.1), toggling the color legend takes 100% of cpu and requires an increasingly long time (ie, longer and longer with each toggle). Once it takes about ten seconds per toggle, I restart ParaView to avoid the problem for a few weeks.
The behavior is consistent across Paraview versions, from 3.6 through 3.10.1. It only requires a hundred or so toggles. I usually load new timeseries each time. (ie, normal use of Paraview (for me).)
This is not using separate data or view servers (paraview-server or paraview-client). Just clicking on the Paraview app to run.
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.