Closed
Conversation
Current coverage is
|
Member
|
Don't spend time on this. The better option for testing RNGs is a collection of PDF functions, drawing tool, and log-likelihood. Plus articles!!! |
Member
|
And do not work on best API. It would be reworked, maybe few times |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Yesterday I realized that
mir.randomheavily depends onmir.statas it needs statistical tests to verify its random algorithsm.Well here is the WIP part for this - it includes already includes an online variance + mean report, moreover I plan to add one or two statistical tests in the first version. What else do you want to see in the initial version of
mir.stat(#49)?TODO: