I managed to complete all of the troubleshooting steps on 23.12 beta 3 (macOS 14.2 arm).
You can recreate the error by starting anki (shift being pressed makes no difference), and pressing the browse button from the top bar.
I tried compiling anki from GitHub and this behaviour gives the following log:
No, quite the opposite: it should be done completely behind the scenes. Anki already has a bajillion buttons and settings, and this is something that doesnāt need extra user control. It will only make users even more confused.
Remember, the average FSRS user doesnāt even realize that the number of due cards per day depends on the choice of desired retention (Iām saying this based on r/Anki posts), let alone anything more intricate than that. The only way to make people use FSRS is to have as few settings as humanly possible, which is also why Iām against the āSM-2 retentionā thingy.
@dae Iāll compile my suggestions into one comment:
Deck size, Days to simulate and Minutes study/day should be remembered on a per-preset basis. Itās much more likely that the user will want to re-compute desired retention with the same values of these parameters than with the default values.
If the user moves a card from deck A with preset A* to deck B with preset B*, DSR values must be recalculated automatically.
to ensure that users cannot end up with worse performance after optimization, do the following: run the optimizer to obtain new parameters, run evaluation with the old parameters, run evaluation with the new parameters and choose whichever parameters result in lower RMSE. Btw, LMSherlock has endorsed this idea too.
ā-is:suspendedā should be the default. If a user has suspended a card, then that card is no longer representative of what kind of material the user is learning. And itās also confusing if you suspended a card, yet itās reviews still matter to the optimizer. A lot of users, myself included, think that suspended cards shouldnāt affect the optimizer.
EDIT: and after giving it some thought, I agree that āReschedule cards on changeā not being saved is very counter-intuitive. I would suggest a community poll, but I doubt that anyone is going to vote for the current implementation.
EDIT 2: I noticed that in the Stats window, graphs related to DSR also include suspended cards. For example, I have 2 cards with retrievability between 20% and 25%, and they both are suspended. I donāt think suspended cards should be included in the stats OR in the optimization. If the user suspended them, that means he decided to exclude them from the learning process. And Anki should treat them accordingly.
EDIT 3: āYou can optimize all presets at once by using the button at the top.ā I think itās not very clear where that ābutton at the topā is, this should be more clear.
Evaluation of parameters obtained using preset:"my preset" -is:suspended: Log loss: 0.3152, RMSE(bins): 5.87%
Evaluation of parameters obtained using the same preset, but without excluding suspended cards (preset:"my preset"): Log loss: 0.3140, RMSE(bins): 4.64%
I also typically choose not to include suspended cards, but today, after testing, I obtained these results and I am a bit confused.
Could it be that including suspended cards, in my particular case, leads to better optimization? Or is there more likely some sort of error in the Evaluation function (or in the way I am interpreting its results)?
If the user triggers it manually, it should at least say if it improved or not and how much, so the user has an idea of whether it had to be done.
The mention of a separate button was a mistake caused by the complexity of how the filter field works and some cards fitting optimizations from other cards better than their own.
They are discussing whether optimizing every two weeks instead of every month is acceptable. If they donāt understand that the numbers should become smaller, and the more the change, the better, itās a problem with the documentation. For one, the numbers are described in the manual, but not in Anki itself.
What about including them when you want to? Maybe ā(is:suspended or -is:suspendedā)? Or is it just about the default value?
What about the stats of card counts and reviews? Or do you mean the Evaluate stats?
However, personally, I would prefer if the default were set to either āDiscardā or āCancel.ā
IMHO, if the user opts to click āCancelā when closing the card layout window, it is relatively safe to assume they know what they are doing and actually donāt want to save any changes they made to the template. Defaulting to āSaveā on the confirmation pop-up feels a bit counterintuitive and unwieldy.
Also, I suspect it might confuse people who are used to the previous behavior, leading them to, for example, press Esc ā Enter out of muscle memory, ending up saving unwanted changes.
In this light, it seems like defaulting to āCancelā could be the safest option, as it would force the user to stop and think about what they actually want to do.
