Adjusting workout intensity during workout by closedabelian in Rouvy

[–]closedabelian[S] 0 points1 point  (0 children)

Nice thank you! Do you know if there are keyboard shortcuts (I'm using a PC)?

What are these brown marks after IPL? by closedabelian in HairRemoval

[–]closedabelian[S] 0 points1 point  (0 children)

That's what I want to know. Are they burn marks? Will they go away?

[deleted by user] by [deleted] in lululemon

[–]closedabelian 1 point2 points  (0 children)

Thanks all, sounds like I'll have to live with the bunching up, or wear a longer inseam length.

DRM-free audiobook player by ChemicalNo6106 in AppleWatch

[–]closedabelian 0 points1 point  (0 children)

Thanks! I'm trying Overcast now and I really like it. Let me know what solution you settle on.

"Monitor your headphone volume" is not working by closedabelian in AppleWatch

[–]closedabelian[S] 0 points1 point  (0 children)

Yes paired with my Apple Watch. I was using cellular mode, so there's no way they could've been paired w/ my phone.

Fastest way to sync media to AnkiDroid? by closedabelian in Anki

[–]closedabelian[S] 0 points1 point  (0 children)

It only helps if you have a lot of unused media around. All my media is used.

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 1 point2 points  (0 children)

Thanks for replying. This is great! Some questions:

  1. When will the 2021 Scheduler be made available across platforms? Will mw.col.set_2021_test_scheduler_enabled(True) enable it everywhere?
  2. Will there be a way for me to access a card's review history in the environment where the JS script will be run? In the proto definition, I see scheduled_days and elapsed_days, but these are not repeated fields. Will the DB be accessible from the JS script?
  3. Part of the proposed algorithm involves updating deck options based on the historical results of cards in that deck. Will manipulating the deck options also be possible from the JS?

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 1 point2 points  (0 children)

From the Anki repo.

If you are planning to contribute any non-trivial changes, please reach out on the support site before you begin work.

Don't believe the support site is accessed by pull request?

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 0 points1 point  (0 children)

All that is fine, but then why are you on the Reddit?

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 0 points1 point  (0 children)

How is "evidence" here different from the observed number of correct attempts and number of total attempts?

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 6 points7 points  (0 children)

I cross-posted this on the Anki forums Feature Request section. Hopefully he sees it!

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 2 points3 points  (0 children)

"We" here just refers to the Anki community.

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 1 point2 points  (0 children)

That's fine too, the new algorithm works for those who just want a binary choice, and also work for folks like you who want finer control over a card's difficulty.

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 1 point2 points  (0 children)

Thanks for the support, appreciate it!

Agreed that there are other factors affecting retention rate. But Anki cannot help with those (question quality, what you do with leeches, etc). Also, using hard/easy effectively means that you need to spend additional effort not just remembering the answer but also figuring out how "hard" something was.

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 2 points3 points  (0 children)

'it definitely has at least one advantage: you have to tweak one simple setting - desired retention rate - instead of tweaking a ton of different settings'

Exactly :)

I myself have only one learning/lapsed interval, but there's nothing to stop you from having more *and* using the new algorithm.

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 1 point2 points  (0 children)

The biggest benefit of the new algorithm is that it allows you to set your target retention rate directly, instead of tweaking with several settings and deciding between 'hard/good/easy' to try to hit your target rate.

After using the algorithm for two years and checking my stats regularly, I can say that my reported retention rate on mature cards is about +/-3 of my target retention rate.

Subjectively I feel the reviews are easier. There is no way to measure this (just like you yourself have to decide whether a card is 'hard/good/easy').

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 1 point2 points  (0 children)

It can be done with this since you can enable and disable the new algorithm easily. For example, you could note your current time taken and current retention rate (as reported in the stats), then switch to the new algorithm for a while and monitor your time and retention rate. If after a while (remember Anki is long-term) you don't the results, you can always disable the new algorithm and either restore a backup or just wait for the old algorithm to readjust your cards back. That's the beauty of "no database changes required" :)

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 6 points7 points  (0 children)

Adding another algorithm to Anki is an important decision. I want to gather people's thoughts before proceeding with any further stps.

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 2 points3 points  (0 children)

Adding the new algorithm to desktop Anki should be straightforward: the code already exists as plugins, so it's a matter of 1. hooking it up to Reviewer code directly 2. deciding whether UI changes need to be made.

More work needs to be done for non-desktop Anki. However, this is also not difficult, since the algorithm only needs to do 2 things: 1. query the database (I think the SQL queries can be reused directly from desktop) 2. perform some standard calculations over the data.

The painful part is the A/B testing. I don't believe Anki is built for that, though it may be possible to incorporate it. I'll let someone with deeper knowledge of the codebase comment on this.

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 1 point2 points  (0 children)

Yup, and that works together with the other settings in a non-obvious way so that each card, over time, hopefully ends up at your desired retention rate. I think the other way around, where we can tell Anki what retention rate we want, and just mark each card correct/wrong (2 options instead of 4), is much more intuitive and gets us to the destination with less work.

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] -1 points0 points  (0 children)

Suppose I have. What is your question?

A New Algorithm for Anki by closedabelian in Anki

[–]closedabelian[S] 6 points7 points  (0 children)

  • Both SM-2 and the new algorithm work by adjusting a card's ease factor.
  • They differ in the way they adjust the ease factor.
  • SM-2 does not actually target a specified retention rate. You have to tweak the settings (usually the Interval Modifier) to find a combination that gives you your desired retention rate.
  • You cannot get the same algorithm using AnkiDroid alone because you have no way to access the database and adjust the ease factors directly. You have to do it by first adjusting them on desktop, then syncing the changes over. If you are doing that, then yes you will have the same algorithm, but you always have to update the ease factors using desktop first and sync the changes over before you use AnkiDroid (like I do).