# Color Map Editor log scaling issues

**URL:** https://discourse.paraview.org/t/color-map-editor-log-scaling-issues/14493
**Category:** ParaView Support
**Created:** [April 25, 2024, 7:39pm UTC](https://discourse.paraview.org/t/color-map-editor-log-scaling-issues/14493 "2024-04-25T19:39:10Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Andy\_Bauer](https://discourse.paraview.org/user_avatar/discourse.paraview.org/andy_bauer/32/5442_2.png) [@Andy\_Bauer](https://discourse.paraview.org/u/Andy_Bauer)
#### Post date: [April 25, 2024, 7:39pm UTC](https://discourse.paraview.org/t/color-map-editor-log-scaling-issues/14493/1 "2024-04-25T19:39:10Z")

</div>

Hi,

There seems to be something off with the TF viewer in the `Color Map Editor` when the `Use Log Scale When mapping Data To Colors` is checked. I would expect the TF viewer to look similar to the 3D view legend but it doesn’t:

 ![colormapeditorlogscaleissue](https://discourse.paraview.org/uploads/default/original/2X/f/f32f4e4ccf036c461e11bbf53f202cd8545d137a.png)

Here’s the  
[state file](https://discourse.paraview.org/uploads/short-url/7N9DOFCHiXtqgljihkCWTYxOo94.pvsm) (335.1 KB)

This is with PV 5.12 on Linux using the downloaded installer.

Is this incorrect behavior or is this confusion on my end?

Thanks,  
Andy

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [April 26, 2024, 12:12am UTC](https://discourse.paraview.org/t/color-map-editor-log-scaling-issues/14493/2 "2024-04-26T00:12:36Z")

</div>

Hey Andy,

In the editor, the x-axis values are evenly spaced, not in a logarithmic space, hence the color legend is “squished” on the left and “stretched” on the right when using log scaling. In the color legend, the vertical axis is scaled logarithmically, so the color legend is not squished or stretched on either side - rather, the axis values change logarithmically. So I don’t think anything funny is happening here. We just seeing the color map drawn in two different coordinate spaces.

We see the same thing in 5.10.1 with the old color map editor

 ![image](https://discourse.paraview.org/uploads/default/original/2X/e/e1dead4d9804721d7730047ea0efcacbbcb1b7a8.jpeg)

There is a question of whether we should logarithmically scale the x-axis in the color map editor. That wouldn’t be unreasonable IMO.

---

<div class="post-metadata">

### Author: ![Andy\_Bauer](https://discourse.paraview.org/user_avatar/discourse.paraview.org/andy_bauer/32/5442_2.png) [@Andy\_Bauer](https://discourse.paraview.org/u/Andy_Bauer)
#### Post date: [April 26, 2024, 11:56am UTC](https://discourse.paraview.org/t/color-map-editor-log-scaling-issues/14493/3 "2024-04-26T11:56:01Z")

</div>

Yeah, I was guessing that the editor doesn’t have the x-axis in logarithmic space. I personally think that the editor’s x-axis should have the same scaling as the TF. Trying to modify the TF at the low end of the values in the editor seems to be a bit unwieldy.

If there isn’t any pushback to this idea then I can create a gitlab issue for this.

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [April 26, 2024, 1:52pm UTC](https://discourse.paraview.org/t/color-map-editor-log-scaling-issues/14493/4 "2024-04-26T13:52:42Z")

</div>

Yeah, I think it makes sense to log-scale the x-axis in the editor. At least I don’t see a reason not to.

---

<div class="post-metadata">

### Author: ![Andy\_Bauer](https://discourse.paraview.org/user_avatar/discourse.paraview.org/andy_bauer/32/5442_2.png) [@Andy\_Bauer](https://discourse.paraview.org/u/Andy_Bauer)
#### Post date: [April 26, 2024, 2:40pm UTC](https://discourse.paraview.org/t/color-map-editor-log-scaling-issues/14493/5 "2024-04-26T14:40:51Z")

</div>

Thanks for the info! I’ve made a GitLab issue at [https://gitlab.kitware.com/paraview/paraview/-/issues/22597](https://gitlab.kitware.com/paraview/paraview/-/issues/22597). I’ve initially assigned @cory.quammen to this issue. Feel free to reassign though. Also, I targeted PV 5.13 thinking that this is hopefully an easy fix but this isn’t an urgent fix so if it slips that should be ok.
