[FEATURE]: Heatmap with custom colour for NaN values
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- data-visualization
Research direction
Start by tracing the heatmap rendering entry point in plotly.js and reviewing the prior implementation discussed in #1170. Confirm how NaN z-values are currently rendered, then define coverage showing that a supplied nancolor is applied without changing normal heatmap colors or behavior.
Written by the indexing model from the issue text.
Description
Description
Currently, z-values of NaN get rendered as transparent in heatmaps. Adding a new parameter nancolor to the heatmap would fix this by allowing users to set a specific colour for NaN values.
Why should this feature be added?
Biomedical data often contains missing values, visualising them explicitly within heatmaps (i.e. without imputation or defaulting to transparent which often visually clashes with the used colour scales) allows for proper communication of the data.
Mocks/Designs
See #1170
Notes
This feature has already been requested in in #975 and a PR with the necessary changes had previously been opened in #1170. While a workaround has been suggested, I believe this could hurt performance for large heatmaps and a new parameter would be more clean. Since the issue is still of concern, I created this new issue as requested here.
- Dominant language
- JavaScript
- Stars
- 18.4k
- Forks
- 2k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from plotly/plotly.js
-
chore P3 plotly-internal size: 3 task
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
plotly/plotly.js#8064 · 1 comment ·
Maintainers usually reply within 1 day
-
chore P1 plotly-internal size: 1 task
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
chore P3 plotly-internal size: 1 task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
plotly/plotly.js#7648 · 3 comments ·
Maintainers usually reply within 1 day
-
bug infrastructure P2
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
All issues in plotly/plotly.js
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
openlibhums/janeway#5604 ·
Maintainers usually reply within 1 day
-
[BUG] Generic OSC does not initialize OSC client on startup when "Listen for Feedback" is disabledOpen
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
area/statement-execution TS conversion
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
scylladb/nodejs-rs-driver#584 ·
Maintainers usually reply within 2 days
-
新讀者走讀回報，照著一篇文章實際操作Opendocumentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 3 days