-
Notifications
You must be signed in to change notification settings - Fork 0
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
Number sequences over time bar chart #332
Number sequences over time bar chart #332
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This is a preview of the changelog of the next release: 0.5.5 (2024-07-15)Features
|
e1ee0bc
to
981b4da
Compare
981b4da
to
3fdd1de
Compare
39f923d
to
83b0868
Compare
3fdd1de
to
1cef69d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
There are currently no errorbars, and I didn't find a related ticket. We might want to add one.
83b0868
to
61a27d5
Compare
We decided that we don't implement error bars in this diagram (yet). |
@JonasKellerer, how would you envision an error bar? :) |
61a27d5
to
42388e8
Compare
1cef69d
to
a5651bf
Compare
42388e8
to
160bf86
Compare
a5651bf
to
c19e131
Compare
The errorbar depends on what we want to display. If we want to display a "measurement" we should include one, since all measurements are bound to have uncertainties. In this case I think of statistical uncertainty, so the user knows that there are only few measurements, but due to statistical fluctuations there could also be different values. This is important to see trends in the data and not mistake some outlier for "real". I think this is what we have done in prevalence over time. However, if we only want to provide the raw data, then no errorbar is needed. |
c19e131
to
4c416c5
Compare
resolves #316
Summary
Add the bar chart. We'll add the logarithmic scale in #333
Screenshot
PR Checklist