Round half_up

[aworker]

I tested too in Java and it is the same, the result is correct.

On top of what I just said, I did further research and found the following thread:

Incorrect rounding in KNIME?

Maybe that won't help with the workaround but just to give a bit of background on why this is happening. We are using a library to do the parsing and evaluation of the expression. The round function is using something called 'rint' and citing the documentation ([1] and [2]): "If two double values that are mathematical integers are equally close, the result is the integer value that is even." and "This has better statistical properties." (I am not sure what properties that are, though.)

RInt differs from the Round class in that it uses the Math.rint() method rather than Math.round(). Unlike Math.round(), in the case of a tie (e.g 1.5) Math.rint() prefers the nearest even integer (so rint(1.5) = 2). This has better statistical properties. For the two argument version you can consider it as a rounding method with a mode of round-half-even.

Apparently KNIME has adopted a -RInt- rounding scheme (or banking Scheme) to avoid “benefit or loss bias” in the long term when rounding. This is not intuitive and obvious to be understood.

Hope this clarifies possible issues or differences too.

Best

Ael