-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Memory states from SM-2 for incomplete review history #248
Memory states from SM-2 for incomplete review history #248
Conversation
Context: open-spaced-repetition/fsrs-rs#63 (comment) I think that I have added most of the code required to make it work. You will just need to do some final touches so that it can become functional. I hope that editing this PR requires less effort than writing all the code yourself.
Patch: fsrs4anki-helper.zip Could you help me test it? |
Patch: fsrs4anki-helper.zip I hope it solve the problem. |
It would be due to fuzz. |
Before merging this, I advise you to check how this affects cards with the first rating as "Manual". Examples: I can't test this case because I don't have such cards. |
Also, we should test for the case where first review kind is FILTERED and "reschedule cards based on my answers in this deck" is enabled & disabled (both cases separately). |
If you enable "reschedule cards based on my answers in this deck", the review kind is REVIEW instead of FILTERED.
The second review is treated as the first learning. |
Weird. I read the doc of Anki, it said that:
I need to ask @dae. |
That comment is wrong - it's also applied when a review card is answered early (eg not using is:due to create the filtered deck) |
Fine. Could I distinguish these two types of review via ease != 0? |
Yes, I think so - the v2 scheduler didn't write revlog entries when not rescheduling, and v3 uses ease 0 when not rescheduling. |
Context: open-spaced-repetition/fsrs-rs#63 (comment)
I think that I have added most of the code required to make it work. You will just need to do some final touches so that it can become functional. Specifically, you will need to edit line 391 and maybe minor changes to the other parts.
I hope that editing this PR requires less effort than writing all the code yourself.