New progress in implement the custom algorithm

[L.M.Sherlock]

@kuroahna

I feel like there’s that optimal spot between the interval spacing and retention rate where you do the least amount of reviews.

It need the optimizer give an optimal request retention. In my paper, I implement it in C++ because it is too complicated and Python is too inefficent to do it. I will improve the performance of code in the future.

[biodecus]

Oh that’s interesting. With all the math libraries available, including ones written in CPython I had assumed Python would be more than up to number crunching tasks like this.

Is the Google Colab optimizer for fsrs4anki still behind the capability of your C++ one?

[L.M.Sherlock]

@biodecus

Is the Google Colab optimizer for fsrs4anki still behind the capability of your C++ one?

The Google Colab optimizer doesn’t include the module. You can see the module at:

maimemo/SSP-MMC/blob/main/algo/main.cpp

[Vitorvlv]

Hi! just wondering, it’s the correct solution for those of us doing reviews on ankidroid to do the reviews on the phone, and then once a day use the “Reschedule Cards” option from the FSRS4Anki Helper addon?

Would that work?

[L.M.Sherlock]

Yes it works, but they are not fully consistent.

[fcsing]

Are the results produced by fsrs.js similar to the outcomes of this Anki build? I have integrated the .js
module as part of a macro on a spreadsheet that I am using to run through bulk data.

I am guessing the .js module does not include the features of the optimizer here.

[L.M.Sherlock]

The default parameters generate result similar to the built-in schedule.

Here is a basic comparsion:

---

Rating sequence: 1,3,3,3,3,3,3,3,3,3

Anki’s intervals: 1,3,8,20,50,125,313,783,1958,4895

FSRS’s intervals: 1,3,8,19,44,98,207,421,822,1550

---

Rating sequence: 2,3,3,3,3,3,3,3,3,3

Anki’s intervals: 1,3,8,20,50,125,313,783,1958,4895

FSRS’s intervals: 2,5,13,32,73,159,331,659,1263,2338

---

Rating sequence: 3,3,3,3,3,3,3,3,3,3

Anki’s intervals: 1,3,8,20,50,125,313,783,1958,4895

FSRS’s intervals: 3,8,21,50,114,245,501,983,1854,3377

---

Rating sequence: 4,3,3,3,3,3,3,3,3,3

Anki’s intervals: 4,10,25,63,158,395,988,2470,6175,15438

FSRS’s intervals: 4,11,29,70,158,337,684,1329,2481,4471

[cjdduarte]

I use 18 different deck configurations.
Should the optimization be done in a universion way or for each 1 of the 18?

[L.M.Sherlock]

If your goals are significantly different in different decks, to optimize parameters for each one is better.

[fcsing]

This is very helpful, thank you. Just to be clear - you are comparing fsrs4anki to fsrs.js? Or anki to fsrs?

[AnkiQueen]

anki to fsrs

[L.M.Sherlock]

Anki and FSRS

You can view the new features in:

New features of FSRS4Anki from v3.0.0 to v3.6.0

Continuing the discussion from Big update in FSRS4Anki v3.0.0: This week, I updated FSRS4Anki from v3.0.0 to v3.6.0. Here is a summary of the new features. Scheduler Add fuzz to prevent cards introduced simultaneously and given the same ratings from sticking together and always coming up for review on the same day. Optimizer Add analysis of review logs to count the true retention more accurately. Add suggested retention to minimize the repetitions in each card. Simulator Add a comparis…