Max value for right y-axis doesn't seem to work

[AdamNowaczyk]

Hi,

I'm having strange problem. I'm using Graph2d to plot line charts with two y-axis (left and right). However I have problem with setting the max value for the right axis, please see this example:
http://jsbin.com/zolewoqaxa/edit?js,output

Additionally, I don't know how to 'reset' max value to original approach. The reason for doing this is that for some small values, I want predefined max value (so axis is scaled nicely), but after some threshold I'd like to use default approach.

Thanks,
Adam

[mojoaxel]

@AdamNowaczyk Thanks for reporting this. And special thanks for the example, that helps a lot!

Looks like a bug to me...

[AdamNowaczyk]

@mojoaxel, not a problem. Definitely a bug. If you're changing the max value for the right axis, it's totally underterministic what value will be displayed. Everything seems to be working fine for the left axis.

This is quite blocking for us as we are displaying CPU and Memory graph that way where left axis shows CPU/Memory % usage and right axis shows GB of RAM. We need both axis to be 'aligned', so max GB is at the same level as 100%. We cannot do that without possiblity to set max for right axis.

P.S.
Do you have any idea how to 'reset' the max setting once it's defined? Setting it back to undefined triggers console log error as Number is expected. Documentation states that undefined is default value. I assume there an issue with 'max' attribute not being set at all and having it set to undefined... However there is no way to remove the options once it's set as setOptions leaves options not listed in the update :(.

P.S.2
When 4.17 is expected to be release? There are couple of important bugs we are waiting for.

[mojoaxel]

Do you have any idea how to 'reset' the max setting once it's defined?

Setting max: null should work in my opinion. It doesn't! Some improvements needed here also!
At the moment is is just not possible to reset a max value.

When 4.17 is expected to be release? There are couple of important bugs we are waiting for.

To be honest: It doesn't look good! If you need bugs to be fixed you'll have to do it yourself of find/pay somebody to do it. Here is not much going on here and I'm just helping out.

[Stexxen]

Problem is caused by FollowScale Function here -
https://github.com/almende/vis/blob/develop/lib/timeline/component/DataScale.js#L134

Its job is to align the minor/major gridlines to appropriate values so that they line up correctly on both right and left sides.

I have a partial fix, working within these hardcoded parameters - https://github.com/almende/vis/blob/develop/lib/timeline/component/DataScale.js#L6-L7
but I think a full fix would require a lot of work.

@AdamNowaczyk In your case, if you were to set right.range.max = 52.5 your example would work correctly. see http://jsbin.com/nihucivole/1/edit?js,output

[mojoaxel]

The problem only exists if two axes are enabled. Than one axes becomes the "master" and defines how many (major and minor) steps are in the y-axis-grid. The second axis has to fitted to this pre-defined grid. This "fitting" of this axis to the other one is done in the function followScale, as already mentions before by @Stexxen

Maybe @ludost can help, who wrote this function!?

[Tooa]

@AdamNowaczyk

Do you have any idea how to 'reset' the max setting once it's defined? Setting it back to undefined triggers console log error as Number is expected. Documentation states that undefined is default value.

I've fixed this issue in #2634. We will release a new version this weekend. I try to look also in the issue mentioned here.