Closed yuriy0 closed 7 years ago
This was fixed at some point before a681439. The offending call now evaluates to the correct result; and this test case no longer ends up manipulating precisely that expression (i.e. trying to build that KB), so the ASSERT does not fail (perhaps the correctly-generated NotAKB is handled by something further up; the details aren't clear).
The assertion in question is the one removed by 5227a4f. The discussion there would indicate that we don't really understand why this ASSERT fails. Currently the only affect test case is "Conjugacy between rolled Dirichlet and multinomial".
The failing call is
Recent versions of both master and pw_simp return
NotAKB
for this call, which causes the ASSERT to fail; what used to be returned isThat result doesn't look correct to me; clearly
i = -1 and i >= 0
isfalse
. If Loop was relying on getting that result, both Loop and KB were bugged. If this result is actually correct, then one or multiple changes made to KB were incorrect (if this is the case, I need to understand why this result is correct).