Closed ghost closed 6 years ago
@subutai Can you take a look at this issue please just to make sure it makes sense?
It makes sense but should be handled by someone who understands the Capn Proto implementation. I also agree with @kyle-sorensen that the Float32's should really be Float64's.
To prevent future occurrences, sounds like we need a test that writes and loads an anomaly model??
@rhyolight, @subutai I can take a look.
@rhyolight I've fixed the serialization test to include the distribution (See #3786). @kyle-sorensen PR #3784 fixes this issue, I ran this PR with the new test to validate.
When I log this method, I can see the following:
In the proto object the defined key is "distribution" too, not "distributionParams".
The capnproto schema also uses Float32 (a float) but the incoming python "float" is actually a double. (Should this be Float64?)