You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-Upload a dataset 25 subjects ranked 1-25 in 2017 and 2018, but in 2019 and 2020, have varying rankings that go beyond 25 (i.e. the ranked 25 fell down to 39th, but the subject remains 25 in number). So essentially, you have 25 subjects but by 2019 and 2020, the ranking is not 1st-25th but some subjects fell lower and the ranking of the 25 are no longer chronological (see attached file).
-Upload the data in long format.
-Select bump chart. Put the rankings in the rank tab. Leave size blank. Put years as date.
Project file
Additional context
So the y-axis in the screenshots stop at 25 even if the rankings go as high as 39 or even 60.
Appreciate the help!
The text was updated successfully, but these errors were encountered:
Not sure what the expected result is. A bump chart reorders streams according to their value, from the highest to the lowest. Therefore, if we have rankings of 1, 2, and 60, all three will be plotted with the same padding, regardless of the absolute value.
In which chart does the bug happen?
-Bump chart
RAWGraphs Version
Web browser and version
Chrome Version 110.0.5481.77.
Operating System
Macbook Pro
Steps to reproduce this
-Upload a dataset 25 subjects ranked 1-25 in 2017 and 2018, but in 2019 and 2020, have varying rankings that go beyond 25 (i.e. the ranked 25 fell down to 39th, but the subject remains 25 in number). So essentially, you have 25 subjects but by 2019 and 2020, the ranking is not 1st-25th but some subjects fell lower and the ranking of the 25 are no longer chronological (see attached file).
-Upload the data in long format.
-Select bump chart. Put the rankings in the rank tab. Leave size blank. Put years as date.
Project file
Additional context
So the y-axis in the screenshots stop at 25 even if the rankings go as high as 39 or even 60.
Appreciate the help!
The text was updated successfully, but these errors were encountered: