Physical value encoder rounding

[c4deszes]

Brief

• Previously the physical values used int(x) to round the values, which rounds down
• The new one should be more consistent across input ranges

Checklist

• Add relevant labels to the Pull Request
• Review test results and code coverage
  • Review snapshot test results for deviations
• Review code changes
  • Create relevant test scenarios
  • Update examples
  • Update JSON schema
• Update documentation
  • Update examples in README
• Update changelog
• Update version number

Resolves

(Issue filed externally)

Evidence

• This change might break user code where users have not fully made sure to limit the input and output ranges, for example a signal intended to be encoded into 0-254 range if the user input could be as high 254.8 then this could lead to an error of the signal overflowing into 255. But at least the encoder will catch cases if that would go outside it's range

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.31%. Comparing base (fbf34fe) to head (801a7e6).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #142   +/-   ##
=======================================
  Coverage   96.31%   96.31%           
=======================================
  Files          13       13           
  Lines        1467     1467           
=======================================
  Hits         1413     1413           
  Misses         54       54           

Flag	Coverage Δ
3.10	96.31% <100.00%> (ø)
3.11	96.31% <100.00%> (ø)
3.12	?
3.6	96.31% <100.00%> (ø)
3.7	96.31% <100.00%> (ø)
3.8	96.31% <100.00%> (ø)
3.9	96.31% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.