Is your feature request related to a problem? Please describe.
Currently, the values emitted during testing are simple written to the log and later compared by eye to make sure they are within monte carlo error (~1/sqrt(N)) - this is falible
Proposed solution
Once the seeded RNG has been implemented and merged, the testing suite should take advantage of it to compare values - they should be exactly the same now, unless some new change modifies the number of RNG calls
Is your feature request related to a problem? Please describe.
Currently, the values emitted during testing are simple written to the log and later compared by eye to make sure they are within monte carlo error (~1/sqrt(N)) - this is falible
Proposed solution
Once the seeded RNG has been implemented and merged, the testing suite should take advantage of it to compare values - they should be exactly the same now, unless some new change modifies the number of RNG calls