Only compute step loss on non-same-day reviews #84
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.
Previously, the optimizer would only compute step loss on review-state cards. For example:
However, it makes more sense to more generally compute step loss on non-same-day (long term) reviews rather than depending on the specific learning state of the card. Technically, in the past, a user could review a review-state card multiple times in one day and this fix simply accounts for that case.
Now, step loss is computed on all non-same-day reviews, not just review-state cards.
I also adjusted one of the unit tests as the optimal computed parameters are now slightly different.
Let me know if you have any questions 👍