I've got an input that I put through a y=mx+c type transformation courtesy of the great choice of operators available in the pull-down menu for inputs. After multiplying it by a number with a lot of significant digits and adding a number with a lot of significant digits, I log it to a feed. A dial then displays that feed (with no scale option).
I just happened to capture an instant now where the dial was displaying 100, but the feed (on the feed page) was displaying 101. I manually did the maths on my calculator, using the last input value posted (from the inputs page), and the answer came out at an incredibly unlucky 100.498089238. It seems the dial correctly rounded that down to 100, but the feed display decided to round it up to 101. Do they use different rounding algorithms for some reason?
I know it sounds picky, but when you see your dial displaying a different number from the feed page, you tend to panic because you think the dial isn't being updated.
emoncms Feed Vs Dial rounding
Submitted by dBC on Wed, 27/02/2013 - 02:55I've got an input that I put through a y=mx+c type transformation courtesy of the great choice of operators available in the pull-down menu for inputs. After multiplying it by a number with a lot of significant digits and adding a number with a lot of significant digits, I log it to a feed. A dial then displays that feed (with no scale option).
I just happened to capture an instant now where the dial was displaying 100, but the feed (on the feed page) was displaying 101. I manually did the maths on my calculator, using the last input value posted (from the inputs page), and the answer came out at an incredibly unlucky 100.498089238. It seems the dial correctly rounded that down to 100, but the feed display decided to round it up to 101. Do they use different rounding algorithms for some reason?
I know it sounds picky, but when you see your dial displaying a different number from the feed page, you tend to panic because you think the dial isn't being updated.