Add powers-of-two 'exponent base' support to axes about plotly.js HOT 13 OPEN

still interest in implementing it?

Yep, we still have interest (that's why we keep the issue opened), but it's not part of any short-term plans for plotly.js team members.

from plotly.js.

👍
(right, SI and B are only different in how they show 10^9 - G or B)

Binary vs decimal might need to be a separate item from exponentformat though - because even in binary mode, you might want to use exponentformat of 'none' (512, 1024, 2048...), 'power' (2^9, 2^10, 2^11...), or 'SI' (512, 1K, 2K... that's not technically SI but it seems like the logical extension?). And if we're putting in binary, we might as well allow for other bases too.

So I'm thinking of exponentbase, which would default to 10 but you could set it to 2, 8, 16, and if we're feeling energetic 'e' or an arbitrary (positive) number. But then only some exponentformats would be allowed - 'none' and 'power' are always good, 'SI' is only good for powers of 2 or 10, and 'e', 'E', and 'B' are only valid for 10. The default is 'B' for base 10, seems like 'SI' would be a good default for powers of 2, and 'power' for other bases.

@iustin @etpinard thoughts?

from plotly.js.

I like the sound of exponentbase

+1

from plotly.js.

+1, exponentbase makes more sense than my original proposal. Thanks for considering!

from plotly.js.

@etpinard @alexcjohnson how should we handle if users use SI and an exponentbase other than 2 or 10, or use B, e, E with bases other than 10? Throw an error, or should we just fallback to defaults?

from plotly.js.

Fallback to default.

This logic should be implemented at the defaults step here.

from plotly.js.

I'm interested in coding this up and making a pull request. Since anything but base 2 and base 10 is definitely a corner case, and it doesn't really make sense to say base-2-SI, my suggestion is to add new options power2 (2^1, 2^2, ..., 2^n) and IEC (the binary equivalent to SI). What do you think?

from plotly.js.

@jonashaag thanks for interest.

@mdtusz made a PR (see #116) back in December about this.

We noticed a few inconsistency with the approach (see comments in #116), the PR stalled and we moved on to more important things.

Feel free to give this a shot!

from plotly.js.

Wow, that PR looks like a lot of work, and changes many things in many places. It would take me too many hours to rewrite/conflict-resolve this.

from plotly.js.

That's part of the reason that the branch went stale. I wouldn't try to rebase if you do decide to work on it - it's probably easier to just start from scratch based on the diffs - too much has changed in the plotly.js structure since when the PR was opened.

from plotly.js.

See https://github.com/plotly/plotly.js/tree/exponent-base for some WIP work.

from plotly.js.

I agree with the decision to close #116, but I'd still love to see this feature. Is there still interest in implementing it?

from plotly.js.

This issue has been tagged with NEEDS SPON$OR

A community PR for this feature would certainly be welcome, but our experience is deeper features like this are difficult to complete without the Plotly maintainers leading the effort.

Sponsorship range: $10k-$15k

What Sponsorship includes:

• Completion of this feature to the Sponsor's satisfaction, in a manner coherent with the rest of the Plotly.js library and API
• Tests for this feature
• Long-term support (continued support of this feature in the latest version of Plotly.js)
• Documentation at plotly.com/javascript
• Possibility of integrating this feature with Plotly Graphing Libraries (Python, R, F#, Julia, MATLAB, etc)
• Possibility of integrating this feature with Dash
• Feature announcement on community.plotly.com with shout out to Sponsor (or can remain anonymous)
• Gratification of advancing the world's most downloaded, interactive scientific graphing libraries (>50M downloads across supported languages)

Please include the link to this issue when contacting us to discuss.

from plotly.js.