- changed status to resolved
scalar requests parsed as floats losing precision
Issue #365
resolved
For example, the Scalar ID parsed as a float 53161121647783268 gets converted to an int64 as 53161121647783264, i.e., off by 4! This is affecting all scalar data arriving via NetReceiver.
Comments (1)
-
reporter - Log in to comment
Fixed in https://bitbucket.org/ausocean/vidgrind/commits/0ba789e8b5a1589de5e6d2490fc412fc44871ee1