Update to FSRS-rs v0.6.1

[L-M-Sherlock]

related update:

• Feat/add rules for returning parameters open-spaced-repetition/fsrs-rs#172
• Remove stratified kfold open-spaced-repetition/fsrs-rs#173

close #3094

@user1823, @Expertium, @RlzHi, please review this PR.

[RlzHi]

Looks good

[L-M-Sherlock]

These tooltips should also update. @Expertium, @user1823, any suggestion?

anki/ftl/core/deck-config.ftl

Lines 393 to 396 in 3cd8c57

	deck-config-weights-tooltip =
	FSRS parameters affect how cards are scheduled. Anki will start with default parameters. Once
	you've accumulated 1000+ reviews, you can use the option below to optimize the parameters to best
	match your performance in decks using this preset.

anki/ftl/core/deck-config.ftl

Lines 413 to 418 in 3cd8c57

	deck-config-compute-optimal-weights-tooltip =
	Once you've done 1000+ reviews in Anki, you can use the Optimize button to analyze your review history,
	and automatically generate parameters that are optimal for your memory and the content you're studying.
	If you have decks that vary wildly in difficulty, it is recommended to assign them separate presets, as
	the parameters for easy decks and hard decks will be different. There is no need to optimize your parameters
	frequently - once every few months is sufficient.

[Expertium]

I suggest just replacing 1000 with 8. Also, the same needs to be done with the "insufficient review history" error message.

[L-M-Sherlock]

I suggest just replacing 1000 with 8. Also, the same needs to be done with the "insufficient review history" error message.

The user still could click optimize to get the default parameters when the number of reviews is lower than 8. It's more important to explain which reviews are counted. Assuming a new user does 1000 reviews in a deck of new cards, the optimize button still pop up the insufficient data error because those reviews are the first review of each cards. The first four parameters are pretrained in the second review of each card, and the rest params are trained in the third and following reviews of each card.

[dae]

Maybe one option would be to stop showing an error, and just fall back on the default parameters instead?

[Expertium]

That would be quite simple, which is nice, but it could cause confusion. If the user clicks "Optimize" and parameters don't change, he will think that the optimizer is broken.

[dae]

If we don't change anything, we can keep showing the message that the parameters are currently optimal.

[brishtibheja]

Is there any specific reason why the parameters need to be shown to users? That section also looks quite cluttered in the Android app so one less thing there if it's not shown.

[dae]

Some power users like to be able to see and/or modify them.

[Expertium]

@dae, do you plan to release 24.04.1 after you merge this pull request?

[dae]

.1 will be a quick update with only some bugfixes, so I wasn't planning to include this. There may be a .2 if we have a longer testing period to try it out.

[dae]

Thanks @L-M-Sherlock. This will go into the main branch, but probably not into the 24.04.1 branch.