-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Assigned memory state after 'set due date'+optimize incorrect #2998
Comments
Is this still valid after #3002 (comment)? |
I think so, yes. Pick a card with a long interval, use 'set due date' to give it '0!', and then make a minor change to the FSRS weights and save. The card has an interval of 1 day but a stability of the interval before 'set due date'. |
Is it expected? The |
My test result after 2b890b0 ![]() ![]() |
The key thing here is "!", which means that the user wants Anki to change the interval. If the user enters "0!", it means that they want to review the card today and decrease its interval to 1 day. In this case, my assumption would be that they forgot the card before it was due and thus, they wanted to decrease its interval so that they can learn it again. In other words, I would assume that this entry is equivalent to an "Again" entry. But, there may be other possible use cases. Thoughts? I would also like to add that distinguishing this entry from the entry added by "Reschedule cards on change" seems to be impossible. So, dealing with this case is going to be difficult. |
Fine. I just hope they can press https://supermemopedia.com/wiki/Ctrl%2BJ_vs._Ctrl%2BShift%2BR They can press something like |
Using a separate revlog entry to distinguish them is an option in the future, as is some action that will review a card from the browse screen. The latter will likely take some work, as the reviewing process is currently connected to the current review screen state. |
If this is planned, I think that doing this as early as possible would lead to the maximum benefit (by preventing the accumulation of "ambiguous" revlog entries in users' collections). Anyway, creating a separate revlog entry should not be a difficult task apart from deciding how exactly to distinguish them. |
Maybe we can integrate the feature |
Yes. But, I think there is a more pressing need to use separate revlog entries for "Set Due Date" and "Reschedule cards on change". |
I guess this can be closed after #3508 |
If the user uses an interval like '0!' to set a card's due date, then optimizes the deck to assign new memory state, the card will receive the wrong stability.
Reported on https://forums.ankiweb.net/t/old-reviews-before-forget-used-in-fsrs-optimisation/40819/17?u=dae
The text was updated successfully, but these errors were encountered: