-
Notifications
You must be signed in to change notification settings - Fork 3
[Question] Is the offline version ofFSRS in this repo different? #36
Comments
Which metrics are poorer than the benchmark? |
I use 20 bins for calibration graph. How many bins did you use in the benchmark? |
https://colab.research.google.com/github/open-spaced-repetition/fsrs-vs-sm15/blob/main/compare.ipynb |
My fault. I used 40 bins. It would increase the RMSE and MAE. |
By the way, it is good news that the online version's performance approachs the offline version. Because I plan to implement the online version in Anki. The offline version only shows that ceiling of FSRS's capacity of fitting. It is trained in the evaluation data, so the evaluation result of offline version doesn't measure the model's generalization ability. |
What about a hybrid approach?
|
We can also allow user to triggle the experience replay manually. |
That's not a good idea. Most users will have no clue what it means and how to use it. I think that user should control only their retention and max. interval. |
OK. Maybe we can set periods for experience replay. Per day/week/month/season or per hundred/thousand reviews. |
Now that I think about it, maybe you should add the option to enable FSRS both globally and for a specific deck individually (that deck will have it's own parameters). |
Here is the design by dae: ankitects/anki#2443 (comment) |
Yeah, but he doesn't specify whether users will be able to only have one set of parameters (global), or whether there will be an option have different sets for different decks. |
I guess the parameters are bound to the deck options? Like |
You can share your suggestion with dae in that issue. |
I noticed that the difference in performance between FSRS offline and online is quite small. Moreover, FSRS offline performs quite poorly, compare to what we saw in the benchmark.
That made me wonder: is the current version of FSRS, the one that is actually used in paractice, different from FSRS offline in this repo?
The text was updated successfully, but these errors were encountered: