Fix incorrect rounding of Module effect percentages. #99
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Due to the JSON having 32-bit IEEE-754 float values, numbers such as 0.04 are encoded as 0.0399999... which subsequently requires adjusting to the nearest decimal. Previously, we were multiplying up by 100, but in the case of the above number, this results in obtaining 3.99999 and then truncating it to 3. Now, we multiply by 1000 and use the Math.Round feature to round up and eliminate any decimals, followed by restoring it to a double precision representation. fixes DanielKote#95
|
Sounds good. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to the JSON having 32-bit IEEE-754 float values, numbers such as 0.04 are encoded as 0.0399999... which subsequently requires adjusting to the nearest decimal.
Previously, we were multiplying up by 100, but in the case of the above number, this results in obtaining 3.99999 and then truncating it to 3.
Now, we multiply by 1000 and use the Math.Round feature to round up and eliminate any decimals, followed by restoring it to a double precision representation.
fixes #95