You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not mentioned anywhere in the spec, but there is no distinction between which division algorithm is used. By default, golang uses truncating division for integers and the big.Int library that is used does Euclidean division.
There was a discrepancy when calculating the AlphaBetaFilter estimate in the reward actor with this test vector during the first update network KPI call which updates the filter estimate. The division happened at this line if it helps.
This behaviour, especially since both division algorithms are used in the protocol, should at least be written in the spec
The text was updated successfully, but these errors were encountered:
It is not mentioned anywhere in the spec, but there is no distinction between which division algorithm is used. By default, golang uses truncating division for integers and the big.Int library that is used does Euclidean division.
An example of where the difference can be seen:
There was a discrepancy when calculating the
AlphaBetaFilter
estimate in the reward actor with this test vector during the first update network KPI call which updates the filter estimate. The division happened at this line if it helps.This behaviour, especially since both division algorithms are used in the protocol, should at least be written in the spec
The text was updated successfully, but these errors were encountered: