-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chore/fix confidence api #2
Chore/fix confidence api #2
Conversation
RN only one function uses numba ... Line 172 in d4d3e8c
it could be replaced by:
but its 10x slower (from fractions of miliseconds to low 10s of ms) Edit:
seems to give nearly identical results and its 10x faster. Looking at the code it would seem Results are very similar when there is a good distribution of fdrs Looks a lot weirder when nothing is significant Edit 2Replacing the function passes all unit tests despite the difference in plotted behavior. Some system tests fail due to small numeric differences. |
|
Note: I think right now there is a pretty rough edge where the user can very easily over-write the confidence location without a major warning. I could hash the output and make sure that flags an error if a read is done on a file that does not have the same hash after the writer is finalized. |
I want to re-enable this API (or equivalent), since those functions were removed:
Also ...
assign_confidence
is a very messy function right now, so I am refactoring so I can actually understand what it is doind.What is not going to happen: