Rounding of DynamicMap range causes bug

[philippjfr]

Currently due to precision differences in Python vs. Javascript we round values to 10 decimal places. This ensures that the values will match between Python and Javascript, however rounding can result in rounding down or up, which can cause problems. When the upper limit of a dimension is rounded up for example, the rounded value will be outside the limit defined by the dimension range. When moving the slider to the maximum position it will therefore request a frame from Python which falls outside of its defined range and will raise an exception. We should ensure that the rounded values sent to JS are within the original range defined on the dimension.

[basnijholt]

I am encountering this bug now. It took me a while to figure out it was not because I was doing something stupid.

Any recommended workarounds?

[philippjfr]

No I don't know of any workarounds, but this is a high priority issue and I will try to have it fixed asap.

[jlstevens]

I imagine this will be an issue if you have something like range=(0, np.pi) and after rounding the value goes up, outside that range? If so, I think the solution is to use one function to consistently keep the Python and JS values matching while staying within range. In other words, this issue is annoying but it also doesn't sound like it should be too hard to solve.

[philippjfr]

@basnijholt Could you confirm the bug is fixed for you?

[basnijholt]

Sorry, I didn't commit the nonworking code, so it's not easy for me to check.

If you like I'll try to reproduce on Monday :)

[philippjfr]

I'll close, please reraise the issue if needed.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.