Skip to content
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

Fix FSRS easy interval being same as good interval in relearning cards #3256

Merged
merged 5 commits into from
Jun 28, 2024

Conversation

user1823
Copy link
Contributor

@user1823 user1823 commented Jun 25, 2024

#3236 (comment)

Before #3236, the Easy interval for relearning cards was Good interval + 1. This PR restores that behaviour.

This is intended to be a temporary change. When FSRS will consider short-term reviews (in V5), the Easy interval will automatically become larger than the Good interval.

@user1823
Copy link
Contributor Author

@L-M-Sherlock, please review the PR.

@user1823
Copy link
Contributor Author

Reason for second commit:
Adding 1 to states.easy.interval won't work because fuzz is applied after that.

Copy link
Contributor

@L-M-Sherlock L-M-Sherlock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@user1823 user1823 requested a review from L-M-Sherlock June 26, 2024 05:42
@user1823
Copy link
Contributor Author

The code is now future-proof. In FSRS v5, this code will prevent the fuzz from causing the Easy interval to become equal to or less than the Good interval (when the non-fuzzed intervals are close enough).

With a maximum interval set, it would be possible to confuse with_review_fuzz()
by passing min > max.
@dae
Copy link
Member

dae commented Jun 28, 2024

Thank you both!

@dae dae merged commit 8d11a90 into ankitects:main Jun 28, 2024
1 check was pending
@user1823 user1823 deleted the patch-1 branch June 28, 2024 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants