Open
Conversation
…plits that use both in game and real time
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.
Overview
About a month ago, I pitched an idea in the Livesplit discord (my discord is IDW#1024) of a method to more accurately calculate the chance of PB. This method allows so-called "Skill Curves" to be merged rather than using a binary search to find the percentile that the run must maintain. I've created a Sub-Module in the
analysismodule calledstatistical_pb_chancethat computes the probability of getting a PB using the method I described. I considered removing the existingpb_chancemodule, but I thought that might cause chaos.Benchmarks & Tests
When I initially suggested the idea, there were concerns about the performance. In particular, it was desired that computations take less than a millisecond such that LSO's frame rate would not be affected. To ensure this, I've added two benchmarks in "statistical_pb_chance.rs." For my code and on my computer, both of them are well under a millisecond:
When rendering a frame, it is only necessary to compute the CDF. The merging of skill curves can be done on a separate thread if necessary, and results are not required until a run is reset.
I've also implemented tests for all my proposed code.
Next Steps