Moved to 34f08d5e11952a80609169b7917d4172.
Last active
July 30, 2024 09:20
-
-
Save mbostock/1667367 to your computer and use it in GitHub Desktop.
Brush & Zoom Redirect [UNLISTED]
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| redirect: 34f08d5e11952a80609169b7917d4172 |
I'm right now trying to use this technique in combination with a mongodb and meteor. Don't expect too much, my javascript-skills are not that good but i have something buggy working here:
https://github.com/k9ert/meteor-deployments
Not sure how meteor is able to scale to that extent but i'm quite sure that they target now any bigdata-scenario you can think of ;-).
Anyhow, each time i revisit this GIST via Google again, i would like to have a link to other pages:
http://bl.ocks.org/mbostock/1667367 <-- see this code in action via iframe
http://bl.ocks.org/mbostock/raw/1667367/2a3dbad8170817e43d33b02988127631a1fcf31b/ <-- be able to start javascript debugger
For data that has a majority of smaller numbers and a maybe a couple of higher numbers, is there anyway to update y-axis scale as you brush?
@mbostock - This uses features that aren't available in version 3.0.8 (the version currently supported by r2d3). As such, it isn't renderable on IE8. Can someone offer any tips for how to render something this in r2d3?
@tjmaynes have you come up with a way to update Y-axis according to focused data?
Can I specify with a date in specific? I need to print for example "june 26, 56" pleasee!
Does anyone have an explanation as to why the fill doesn't always work? We are using this exact code, just using our own CSV data. Usually the fill isn't working until you've maybe hit refresh quite a few times on the screen, but if you hit it again the fill goes away
again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Awesome! Any best practices available / ideas on setting this (or similar) up with huge data sets (several days with hundreds of sensor data points per second)? Something like loading chunks of the detailed data "on pan"/"on zoom" rather than loading the full data upfront? Thanks!