ChartData2D Component Needs Property to Define Range of Y Axis

[bobparks]

Describe the bug ChartData2D generates the range of the Y axis from the data, but this can be problematic when visualizing two comparable datasets that differ in the range of Y. It creates a false comparison, as shown below.

For example, if you looked at the annual ice duration data of these two lakes, top and bottom, they would seem similar. The range of the top lake, however, starts around 70 instead of 0.

By changing the Y range to 0 for both (artificially adding a leading 0 to the data), the top graph shows a truer picture — that the top lake has less variation year-to-year than the bottom lake (it is more shallow and therefore a bit more resilient to climate change).

For kids to compare two datasets accurately, would be great to have a parameter in the ChartData2D properties panel to define this range.

@stezelMIT, @anqizzz8989

Affects

• [ x] Designer
• [ ] Blocks editor
• [ ] Companion
• [ ] Compiled apps
• [ ] Buildserver
• [ ] Debugging
• [ ] Other... (please describe)

Expected behavior

Steps to reproduce

[dhruvpatidar359]

This issue seems interesting to me , can anyone please guide me how i can track this issue in the code base , what steps i should follow ? -- i am beginner with this project , that's why i am asking .

[stezelMIT]

I believe @ewpatton already fixed that, correct Evan?

[dhruvpatidar359]

@stezelMIT ok , if ewpatton has not corrected it then , i think that it can be corrected by doing some changes in the file Chart2DDataModel.java , please correct me if i am wrong .

[dhruvpatidar359]

Hello @ewpatton sir ,is the issue resolved or i can work on this ?

[dhruvpatidar359]

I checked it , the problem is still there in the current version , here you can see

[dhruvpatidar359]

[stezelMIT]

I think the issue has been addressed and is now on the test servers, but not merged yet. Correct @ewpatton @bobparks ?

[ewpatton]

That's correct. The branch in question needs to be cleaned up a bit because I implemented some other changes to spreadsheets that in hindsight didn't work so I backed them out. From the end user's POV it won't make any different but in terms of keeping the code base clean it's better for me to do the work to fix up the branch before publishing the PR.