Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow precomputed statistics input for box traces #1059

Open
etpinard opened this issue Oct 19, 2016 · 6 comments

Comments

Projects
None yet
7 participants
@etpinard
Copy link
Member

commented Oct 19, 2016

For example:

var trace = {
  type: 'box',
  q1: 1,
  q2: 2,
  q3: 3,
  q4: 10
}

See http://community.plot.ly/t/box-plots-manually-supply-median-and-quartiles-performance-for-alrge-sample-sizes/2459

@rsandler00

This comment has been minimized.

Copy link

commented Oct 20, 2017

Would also love this feature!

etpinard referenced this issue Oct 31, 2017

2nd cut violin calc/plot attributes + improve violin curve paths
- add 'kernel' enumerated
- implement 'scalegroup & 'scalemode' (instead of 'scaleby')
- implement 'spanmode' & 'span'
- make 'side' an enumerated w/ vals 'both', 'negative' and 'positive'
  to be general enough for horizontal and vertical violin
- 🔪 'line.smoothing'
@pditommaso

This comment has been minimized.

Copy link

commented Dec 7, 2017

Yes, this would be very useful.

@nicheath

This comment has been minimized.

Copy link

commented Feb 15, 2018

This would be incredibly helpful! I assume if this is implemented on the javascript side it'll be available on the Python side as well?

@fabiomolinar

This comment has been minimized.

Copy link

commented Dec 28, 2018

Waiting on this one as well!

@sylfel

This comment has been minimized.

Copy link

commented Jan 11, 2019

It would be very very usefull to have this functionnality !!

@ekalosak

This comment has been minimized.

Copy link

commented Feb 8, 2019

This is a vital feature for industrial readiness. If data needed to compute quantiles cannot fit in memory or are expensive to shuttle across a netowork, the aggregations must be computed near the data store (SQL: materialized views, Hadoop: Map-Reduce). If we need to compute quantiles near the data store, it would be convenient to pass those summary stats directly to the plotting routine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.