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

Make axes ranges stay consistent when using a filter #14

Closed
brittsikora opened this issue Sep 23, 2016 · 2 comments
Closed

Make axes ranges stay consistent when using a filter #14

brittsikora opened this issue Sep 23, 2016 · 2 comments
Assignees

Comments

@brittsikora
Copy link

From Meagan Spychala on 9/19:

"It would be really useful if the axes’ ranges stayed consistent when using a filter. For example, we were looking at a longitudinal graphic of systolic blood pressure across several sites, but each site’s graphic had an updated vertical range to fit that site, it did the use aggregate of the data (i.e. if the SBP for the study as a whole was 70 to 160, but a site’s range was 90-120, the 90-120 would be the vertical axis range for that site only) . Because the range of the vertical (SBP) and horizontal (Visit) axes can change, it is harder to see if the sites were in line with each other or if there was an outlying site. I think it’s appropriate to have the range of the axes change depending on the measure (for example, SBP vs. DBP), but once you pick a measure, the axes’ range should be held constant based upon the overall data to be able to identify potential trends."

@jwildfire
Copy link
Contributor

Same issue captured and discussed here. probably addressed with a default changed.

@jwildfire jwildfire modified the milestones: v1.4.0, v1.3.0 Dec 17, 2016
@samussiah samussiah self-assigned this Feb 8, 2017
@jwildfire jwildfire modified the milestones: v2.1.0, v2.0.0 Feb 15, 2017
@samussiah samussiah removed this from the v2.1.0 milestone Jan 5, 2018
@samussiah
Copy link
Contributor

The y-axis range stays consistent when filters change. We addressed this back in v2.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants