I have a question. When I press Forget and choose “Reset repetition and lapse counts”, does it mean that those past reviews will not be used by the Optimizer anymore? I would assume so.
1 Like
yes, since the optimizer will see that card as a new one, there won’t be past reviews
1 Like
Are you able to provide me with the collection & apkg files privately so I can try to reproduce the issue? (or just the apkg if it occurs in an import into a fresh profile)
Thanks, I’ll fix the translations.
No, it only alters the counts shown in the card info screen. The review history is preserved.
1 Like
rc3 is now available:
2 Likes
Will translate again first thing Monday morning, hope this is early enough.
Sure. One more thought on this for later: I guess simply adding a number and increasing it until you get a name that hasn’t been taken would also work, like so: note type (4)
Currently (at least in RC2) the English help text for “update note types” says that:
for schema changes (e.g. the number or order of fields has changed), the ‘Merge notetypes’ option will also need to be enabled.
“also” implies that the “merge note types” option is only relevant depending on what you choose under “update note types”. If that is not the case, I would suggest the text be changed as this is what the average user will understand from this help text, just like I did.
It’s the opposite: Update notetypes is irrelevant if there is a conflict and Merge notetypes is disabled. The quoted sentence seems to correctly convey this meaning (not saying it could not be improved in any way, though).
And again, note that this is only taking into account a single notetype. In this scenario, Update notetypes will still be relevant for other notetypes.
I think it makes more sense to exclude all reviews that happened before pressing “Forget” from the optimization.
2 Likes
Yes. I sometimes change the card content to such a degree that it becomes a completely new card, so I click forget on it. I never knew that FSRS doesn’t actually exclude the past reviews if you hit forget so this is quite troubling.
Sorry, my answer was misleading. What I meant was that review logs are not deleted, but FSRS has its own logic to account for manual rescheduling.
2 Likes
Btw, @dae, how does the Ankidroid version of FSRS (in the new alpha of Ankidroid) work compared to the PC version?
I mean, if someone is using FSRS on Ankidroid and in the desktop version, it will be fine, right?
Also, I previously mentioned that it would be great to have an option to reschedule cards using the old algorithm, in other words, revert FSRS scheduling. Will the final release have that option, or is it something that will be added later?
Now that FSRS is natively supported and there is no need to copy into the custom scheduling field, is there a way to see the FSRS stats during review? Previously I just set const display_memory_state = true;
3 Likes
Maybe “Compute optimal retention” should say how many cards it could fit in the days. Does it use the configured new card limit or something else?
It uses the same code the computer version uses (well, it’s about 2 weeks behind at the moment, but that will be fixed in the next alpha).
I don’t see it as a big priority, as we advise against rescheduling all cards when starting to use FSRS.
The card info screen will show them.
I believe it infers the limit based on the number of days and number of cards.
2 Likes
Unfortunately, I’ve seen several people not willing to give FSRS a try purely because rescheduling is irreversible. IMO, that and the lack of an option to periodically optimize parameters without the user doing it manually are the two biggest problems right now. Those 2 features make a huge difference in terms of how convenient FSRS is to use.
Visuals are broken on macOS, I am using Ventura 13.6 (22G120).
With 23.10 rc3, when choosing “Metal” as video driver result is as in the attached screenshot. It can become normal after moving mouse across the window, but then often cards are not loaded correctly at all.
When choosing “OpenGL” as video driver the whole window is just pure black.
EDIT:
After few changes back and forth between Metal and OpenGL it started working correctly on Metal driver. I will try to test more.
What happens if we use Ankidroid without FSRS, and then use Anki Desktop with it?
It will not crash, but review intervals will be inaccurate.
For such situation it is advised to use FSRS helper add-on, that will work just like until now with FSRS on desktop + Ankidroid setup: you can use FSRS helper add-on, to reschedule cards, that were reviewed on the Ankidroid. This option can be set to automatic, so every time you open desktop Anki it will check if any cards were reviewed on a different device and reschedule them using FSRS.
1 Like
@dae, could you export get_fuzz_factor of card to python lib? My add-on also reschedules cards based on the memory states, but the fuzz factor is inconsistent with Anki built-in fuzz factor. I hope my add-on could provide the same result of rescheduling.
Related to this, this is the second time I suddenly get the “processing” dialog, and the program gets completely irresponsive, forcing me to shut it down from the Windows task manager.
This has never happened before on my system. I have not been able to figure out what may be causing the problem, I will keep trying.