Problems with "Reds", "Turbo", "Inferno" (...?) colorscales
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18.8k
- Forks
- 2.8k
- Avg merge
- 16h 26m
- Merged PRs (30d)
- 21
Description
There seems to be an issue with the "Reds" and "Turbo" colorscales. I couldn't find an existing issue about this, so here is how to reproduce: I just got this example from plotly page:
https://plotly.com/python/dropdowns/#update-several-data-attributes
And added the "Reds" and "Turbo" colorscales.
The "Reds" seem to work, but it is inverted when comparing to the "Blues" and "Greens":



The "Turbo", on the other hand, shows up like a "coolwarm" colorscale instead:

These two are different than the ones described on the documentation here: https://plotly.com/python/builtin-colorscales/#builtin-sequential-color-scales
I had similar issues when using "Plotly.update" with plotly.js to update the coloscales.
edit: Also the "Inferno" shows as the "coolwarm" one:

Probably there are others too.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Plotly Python dropdown example and the reported Plotly.update reproduction, then compare the Reds, Turbo, and Inferno results with the builtin sequential color-scale documentation. Trace where these colorscales are selected or transformed; done means they render with the documented palettes in both reported update paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100