ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-05-05T00:24:13-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/18976Color by glyph magnitude not available in v5.62020-05-05T00:24:13-04:00JPCColor by glyph magnitude not available in v5.6When creating a Glyph plot, the magnitude of the vector variable used to construct the plot is not available for coloring in v5.6 (64 bits Win).
Previous versions (e.g. 5.5.2 64 bits Win), created a "GlyphVector" variable for coloring wi...When creating a Glyph plot, the magnitude of the vector variable used to construct the plot is not available for coloring in v5.6 (64 bits Win).
Previous versions (e.g. 5.5.2 64 bits Win), created a "GlyphVector" variable for coloring with the glyph vector magnitude.
Paraview v5.6 is capable of reading a 5.5.2 version saved stated, and then it does find the GlyphVector variable and is able to color by that variable.
In the meantime, the calculator can be used to create a magnitude variable, and used that variable to color the glyphs, but v5.5.2 approach is better, as when choosing GlyphVector variable to color, the "Magnitude", "X", "Y", or "Z" components of the GlyphVector variable can be used to color.
I tried creating a dummy vector variable with the calculator, which is a copy of the original variable, and use that to color, but at least in the example that I tried, Paraview crashed when creating the Glyph plot using the calculator source defined.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/7400Color By menu is not updated properly2019-03-05T10:44:29-05:00Kitware RobotColor By menu is not updated properly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=7400). Further discussion may take place here.**
---
Try this:
* Sphere source
* Programmable filter - create a new array (R...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=7400). Further discussion may take place here.**
---
Try this:
* Sphere source
* Programmable filter - create a new array (Result)
* Apply
* Change the name of the array to Result2
* Apply
The old name sticks in the menu bar and the new one is not shown.https://gitlab.kitware.com/paraview/paraview/-/issues/6571Color By menu on toolbar does not update2019-03-05T10:45:54-05:00Kitware RobotColor By menu on toolbar does not update**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6571). Further discussion may take place here.**
---
If a filter adds a new array, Color By filter does not update to reflect it...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6571). Further discussion may take place here.**
---
If a filter adds a new array, Color By filter does not update to reflect it. Try this:
* Create sphere
* Create a programmable filter - apply
* Set the script to below - apply
The color by menu does not change.
from paraview import vtk
output = self.GetOutputDataObject(0)
numpts = output.GetNumberOfPoints()
fa = vtk.vtkFloatArray()
fa.SetName("foo")
output.GetPointData().AddArray(fa)
for i in range(0, numpts):
fa.InsertNextValue(i)
https://gitlab.kitware.com/paraview/paraview/-/issues/6528Color By menu should list partial arrays2019-03-05T10:46:07-05:00Kitware RobotColor By menu should list partial arrays**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6528). Further discussion may take place here.**
---
Color By menu should list partial arrays**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6528). Further discussion may take place here.**
---
Color By menu should list partial arrayshttps://gitlab.kitware.com/paraview/paraview/-/issues/3245Color by property should have a label.2019-03-05T10:53:17-05:00Kitware RobotColor by property should have a label.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3245). Further discussion may take place here.**
---
When no array is selected, the global color by array selection isblank. Thi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3245). Further discussion may take place here.**
---
When no array is selected, the global color by array selection isblank. This should say something like User Selected Color. Also, it should probably have a label or icon.https://gitlab.kitware.com/paraview/paraview/-/issues/10514Color by vector component is global2020-04-10T20:07:26-04:00Kitware RobotColor by vector component is global**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10514). Further discussion may take place here.**
---
Not sure how to say this, but color by vector component does not stay with...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10514). Further discussion may take place here.**
---
Not sure how to say this, but color by vector component does not stay with a particular filter, but effects all filters.
ParaView trunk, XP, local server.
* Open disk_out_ref.exo
* slice filter. Apply. (Lets call it slice 1)
* Highlight the disk_out_ref.exo reader again. Slice filter. Y Normal. Apply. Turn off show plane. (Lets call it slice 2)
* Slice 1 - color by V.
* Slice 2 - color by V. Now, change the component from magnitude to X.
Bug - Notice that the component for slice 1 also changes. It should stay as magnitude.
Note - This bug shows up with a user that is trying to show X on one slice, and Y on the other.https://gitlab.kitware.com/paraview/paraview/-/issues/659Color by vector component only available from "Edit Color Map..."2019-03-05T10:54:30-05:00Kitware RobotColor by vector component only available from "Edit Color Map..."**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=659). Further discussion may take place here.**
---
Selecting which vector component to color by (or whether to color by vector ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=659). Further discussion may take place here.**
---
Selecting which vector component to color by (or whether to color by vector magnitude) should be available on the Display page for the data (somewhere near the Color by menu). It seems hidden on the "Edit Color Map..." page. Maybe the controls should be in two places (like the ones for data set visibility are).https://gitlab.kitware.com/paraview/paraview/-/issues/9676Color catagories for chart views2019-03-05T10:41:17-05:00Kitware RobotColor catagories for chart views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9676). Further discussion may take place here.**
---
There is no consistency for the coloring in chart-type views and for most o...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9676). Further discussion may take place here.**
---
There is no consistency for the coloring in chart-type views and for most of them there is no way to change the default coloring.
Chart views should follow some color categories for setting things like background and text colors. Also, the color categories the chart-type views follow should be different than those for 3D views. Although I like the greyish background for 3D views, I hate them for charts.https://gitlab.kitware.com/paraview/paraview/-/issues/15750Color display of a crack2017-11-30T11:37:57-05:00Kitware RobotColor display of a crack**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15750). Further discussion may take place here.**
---
The model attached is simulating a crack in a bulk material. The idea of t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15750). Further discussion may take place here.**
---
The model attached is simulating a crack in a bulk material. The idea of this model is to have each node representing the crack with 2 two different values for the field (displacement in general, here Data).
Visualizing such a model and coloring by the displacement field shows not a clean border along the crack as it is expected. https://gitlab.kitware.com/paraview/paraview/-/issues/6090Color editing from toolbar2019-03-05T10:46:34-05:00Kitware RobotColor editing from toolbar**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6090). Further discussion may take place here.**
---
The Active Variable Controls and Representation toolbars have saved me a lo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6090). Further discussion may take place here.**
---
The Active Variable Controls and Representation toolbars have saved me a lot of time by preventing me from having to switch to and from the display panel. However, I find I still have to go to this panel somewhat frequently to change the colors. I think I could avoid going to the Display panel 90% of the time if the following two icons were added to the Active Variable Controls toolbar:
1. A button that is equivalent to hitting the Edit Color Map button in the Display panel. If a solid color is being displayed, then it should be equivalent to the Set Solid Color button.
2. A button that is equivalent to hitting Rescale to Data Range (grayed out when showing a solid color).
It would also be cool if the toggle color visibility or edit color map button had a pulldown menu that allowed you to select one of color scale presents. You could also put one or both of the above options into that pulldown.https://gitlab.kitware.com/paraview/paraview/-/issues/14480Color editor - Choose preset - Remove doesn't work2018-08-08T22:26:10-04:00Kitware RobotColor editor - Choose preset - Remove doesn't work**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14480). Further discussion may take place here.**
---
Color editor - Choose preset - Remove is grayed out.
Local server, Li...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14480). Further discussion may take place here.**
---
Color editor - Choose preset - Remove is grayed out.
Local server, Linux, master.
Wavelet. Apply. Surface. RTData.
Color Editor. Save to Preset. Close.
Choose Preset.
You can't remove the preset you just created (at the bottom of the list).https://gitlab.kitware.com/paraview/paraview/-/issues/14479Color editor - import - needs to save Enable Opacity mapping state2018-08-08T22:26:10-04:00Kitware RobotColor editor - import - needs to save Enable Opacity mapping state**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14479). Further discussion may take place here.**
---
With the color editor, we need to save the state for the opacity mapping f...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14479). Further discussion may take place here.**
---
With the color editor, we need to save the state for the opacity mapping function. Currently there is no way to do this.
https://gitlab.kitware.com/paraview/paraview/-/issues/15076Color editor color mapping data opacity control goes crazy2017-12-04T12:46:55-05:00Kitware RobotColor editor color mapping data opacity control goes crazy**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15076). Further discussion may take place here.**
---
The color editor Mapping Data opacity control goes crazy upon update. Thi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15076). Further discussion may take place here.**
---
The color editor Mapping Data opacity control goes crazy upon update. This needs to be fixed.
* Linux, 4.2.0, local server (I found it originally on master, Windows, so I believe it is still broken)
* Open can.exo, all vars on, Apply.
* Settings/ General/ Color/Opacity Map Range Options/ select Clamp and Update Every Timestep.
* Color by ACCL.
* Open the color editor.
* Go forward one timestep.
<<bug>> The Mapping Data Opacity control will have gone crazy. If you rescale to data range it goes back to normal, but then move forward another time step, and the control goes crazy once again.
https://gitlab.kitware.com/paraview/paraview/-/issues/15115Color editor color mapping import has errors2022-05-11T16:14:15-04:00Kitware RobotColor editor color mapping import has errors**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15115). Further discussion may take place here.**
---
The color table import code reads in twice, and the second line is named i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15115). Further discussion may take place here.**
---
The color table import code reads in twice, and the second line is named incorrectly.
* Master, Linux, local server.
* can.exo. All vars on. Apply.
* Color by Accl.
* Color map editor. (default color map, by the way).
* Click on the middle of the three buttons on the horizontal Mapping Data section. Change the color to yellow. Congratulations - you have created a unique, ugly color map.
* Save to Preset. (This is right below Choose Preset). Change new preset to deleteMe.
* Export this to a file, I chose the name fileDeleteMe.
* Now, remove preset deleteMe.
* Reset Session.
* can.exo. All vars on. Apply.
* Color by Accl.
* Choose Preset. Import. Import fileDeleteMe.
<<Bug - There are two new presets read in, where there should be only one.>>
<<Bug - The second preset has a name of Diverging. Obviously wrong.>>https://gitlab.kitware.com/paraview/paraview/-/issues/15094Color editor dialog won't go off screen2017-12-04T12:46:55-05:00Kitware RobotColor editor dialog won't go off screen**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15094). Further discussion may take place here.**
---
We want the Color Map Editor to be dragged mostly off screen. Users do th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15094). Further discussion may take place here.**
---
We want the Color Map Editor to be dragged mostly off screen. Users do this to move dialog boxes out of the way. Here is an example. Weird.
* Linux, 4.2.0, local server.
* Full screen the ParaView program (i.e., don't go to View/ Full Screen).
* can.exo. All vars on. Apply.
* Color by EQPS.
* Open Color Editor.
* Now, grab the Color Map Editor by the top bar (i.e., where it says Color Map Editor), and slide it DOWN. Without releasing it, notice that you can move most of the color editor off the screen. This is good. (Make sure you can't "loose" any dialogs, in an unrecoverable way). Now, set the Color Map Editor dialog down in the middle of ParaView (without docking). Now, try to move the editor off screen. It won't go! This is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/14283Color editor doesn't update - CAM data2018-02-15T05:44:43-05:00Kitware RobotColor editor doesn't update - CAM data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14283). Further discussion may take place here.**
---
Haven't been able to replicate this with any other data. Sorry. Utkarsh ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14283). Further discussion may take place here.**
---
Haven't been able to replicate this with any other data. Sorry. Utkarsh has all of the data for this bug.
Linux, master, remote server (8 servers).
Read in Sandia-CAM-Data-Alan1-Do-Not-Release.nc. CAM NetCDF (Unstructured) reader.
Use "Connectivity File Name" Sandia-CAM-latlon-Alan1-Do-Not-Release.nc.
Unclick Cell Layer Right. Click Single Level.
Apply.
Color by TMQ.
Open the Color Editor.
Make sure auto apply is OFF.
Select Enable opacity mapping for surfaces.
Update.
Now, drag the right control button for red vertically down, so the opacity control is basically horizontal, and zero.
Update.
Nothing happens. This is a bad bug.
Marking high since this is impacting me.
https://gitlab.kitware.com/paraview/paraview/-/issues/14288Color editor goes black2018-08-08T22:26:20-04:00Kitware RobotColor editor goes black**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14288). Further discussion may take place here.**
---
I have found a case where the color editor screen is showing black, and ch...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14288). Further discussion may take place here.**
---
I have found a case where the color editor screen is showing black, and changing the color table. This is bad - it is keeping me from working on weather simulations.
* Master, Linux, local server.
* Open Whipple_Shield.exo.4. All variables on. Apply.
* Cell Data to Point Data. Apply.
* Open a Color Editor. Enable opacity mapping for surfaces. Update.
* Add a calculator filter. Result array name: Pres2. Formula: PRESSURE. Apply.
*In the color editor window, use log scale when mapping data to colors. Enable opacity maping for surfaces. Click on the sloping line, in the middle - creating a point.
* Now, in the pipeline browser, turn CellDataToPointData visible.
* Highlight the calculator, then the cell data to point data filter, then the calculator, then the cell data.. Watch the Color Map Editor. It will randomly place points in the horizontal colorbar, and make the right side of the mapping data go black. This is a bug.
I am trying to get out of there before it rains - my directions above could be slightly wrong. If so, let me know and I will correct them.https://gitlab.kitware.com/paraview/paraview/-/issues/18707Color Editor is broken volume rendered, log scale2019-04-12T18:52:01-04:00W. Alan ScottColor Editor is broken volume rendered, log scaleThe color editor is broken for volume rendered, log scale. Here is how to replicate:
* Linux, master (v5.6.0-470-g9457eec), local server.
* Open disk_out_ref.exo. Turn on all variables. Apply.
* Paint with Temp.
* Volume.
* Open the...The color editor is broken for volume rendered, log scale. Here is how to replicate:
* Linux, master (v5.6.0-470-g9457eec), local server.
* Open disk_out_ref.exo. Turn on all variables. Apply.
* Paint with Temp.
* Volume.
* Open the Color Editor. "Use log scale when mapping data to colors". Notice the bottom color bar goes white. Now, unselect "Use log scale when mapping data to colors". Notice the bottom color bar remains white.
This is a bug, and must be fixed for 5.7.0.5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/14832Color editor isn't sized corretly.2018-08-08T22:25:47-04:00Kitware RobotColor editor isn't sized corretly.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14832). Further discussion may take place here.**
---
* Linux, master, local server.
* Sources/ Sphere.
* Color by Normals.
*...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14832). Further discussion may take place here.**
---
* Linux, master, local server.
* Sources/ Sphere.
* Color by Normals.
* Color editor.
<<bug>> - the color editor opens about 1/2 necessary width. Every time I need to widen it up. https://gitlab.kitware.com/paraview/paraview/-/issues/17920Color editor master bug2018-09-10T21:24:19-04:00W. Alan ScottColor editor master bugColor editor master bug.
- [x] #18131 Change base color editor presets
- [x] #17988 Allow interaction when preset window is up
- [x] #18129 Add an advanced button to the color editor presets
- [x] #17987 Customizable color map presets
-...Color editor master bug.
- [x] #18131 Change base color editor presets
- [x] #17988 Allow interaction when preset window is up
- [x] #18129 Add an advanced button to the color editor presets
- [x] #17987 Customizable color map presets
- [ ] #18130 Clean up advanced color editor presets (OK to slip this to spring of 2019)
5.6 (Fall 2018)Shawn WaldonShawn Waldon