Check these, or just search CMRR here or in github.
Especially when paired with FSRS-6, CMRR is practically useless. It almost always gives 70% as output and users can’t choose DR below 70% anyway. @Expertium has tried various methods to produce higher values, without much success.
However, a more important issue is that it gives just a single value, which isn’t helpful for users who want to decide what DR value will give them the best compromise between retention and workload based on their priorities. Some users may want high retention despite…
main ← L-M-Sherlock:Feat/FSRS-6
@Luc-Mcgrady once this is merged, hopefully you can work on reimplementing CMRR … as I described
EDIT: maybe Jarrett was right. Seems like after the FSRS-6 update, CMRR is just stuck at 70% or close to 70% pretty much all the time. "Best I can do is 70%" (c) CMRR. Perhaps we should remove it after all, like Jarrett originally intended
I said that because what you asked about didn’t sound like you would be interested in a low-retention solution. But you can continue using the exact same DR you were using with FSRS-5, and it should work out similarly with FSRS-6.
1 Like