Pass/Fail Grading as Default

Oh true. You’re right. So probably “better” knowledge acquisition rate.

Edit: Haha this is the 100th reply under this topic.

Edit2: Actually, the reaction times probably will be much lesser for two button users than for 4 button users.

@dae sorry I’m pinging you again and again but what do you think of this suggestion. This has gotten very long I think so let me quote your initial argument against this,

but this might not be true anymore.

Hey @Expertium of DASH doesn’t differentiate between Hard/Good/Easy how is RMSE different for 2 button users/4 button users? Am I missing something?

That’s a good question. I guess because the intervals of 4 button users are more heterogeneous.

1 Like

I think I forgot the fact that you were doing the analysis on SM2 users’ data. Thus the confusion :sweat_smile:

Also, if you have time, and you don’t think this is redundant, can you actually find the answer to this question from L.M.Sherlock,

Do 2-button users spend less time to remember more cards than 4-button users?

Preferably for users with at least a year of data, or two years like last time albeit 6K users would be a very small sample size. Let me know if that would that be possible for you.

I’m not sure how to measure it

Can you calculate the total time spent?

Is not knowledge:workload ratio a viable way of doing that? AFAIK knowledge is just total stuff learnt and workload is total time spent. The average 2-button users will have higher ratio than the average 4-button user if 2 button actually is better.

Edit: It was workload:knowledge.

Yes, but that would be difficult to do. @L.M.Sherlock help would be appreciated

Don’t cards just introduced have smaller workload than old cards?

2-button users could have lots of 4444 cards technically indistinguishable from 2222 cards.
And then they’ll switch between the two modes, and FSRS will be confused about Hard and Easy?

Yes. We will be looking at total workload though.

2=Hard? 4=Easy? But even then I don’t get what you are trying to say. Can you rephrase sorry.

A card always rated Easy will be reviewed maybe 4 times. A card always rated Hard will be reviewed much more. With two buttons, the only difference will be a Fail or two.
In a way, an extremely easy card is a waste of time, and rating it Easy removes it. But can you trust yourself to decide to remove an overly easy card?
Although an easy card will probably be rated Good more often.

Because ‘Easy’ rapidly increases the delay, it’s best used for only the easiest of cards. Usually you should find yourself answering ‘Good’ instead.

It seems to me that the Easy button adds less decision and Undo overhead than the Hard button, because I don’t think about pressing it often, unless the card is annoyingly easy. Otherwise I think of using it after I encountered the knowledge outside the review process.

What you said initially describes 4 button users. 2-button users refer to people who use Hard+Easy buttons less than a certain threshold. That was the original definition.

The reaction times are also similar. Easy has the lowest average reaction time, followed by Good, then Hard. Hard is hard-to-press it seems.

I actually expect the average reaction time for 4 button users to be more than 2 button users because they’re dithering about which one among Easy/Good/Hard to use while our 2-button user has already moved on.

As far as I’m aware, the graphs above are only attempting to answer the question “Is FSRS less accurately able to predict the recall of a 4 button user?”. That’s only part of the puzzle, and what would be more interesting to show is if hinting that some cards are hard or easy to the scheduler is worth the downsides of slower reviews, reduced RMSE, etc.

1 Like

If it doesn’t make the scheduler do better retrievability prediction then I’m not sure Hard and Easy are doing anything beneficial here. I am only countering what you said - that it would hamper the scheduler’s performance. Is there anything else a scheduler does other than showing you the cards at the correct time (in this case, when R falls to a particular value). Also to quote you,

This is from 2020 by the way.

In any case, I saw L.M.Sherlock creating a repo called Anki button usage so he might be working on something here.

(@Expertium I think I misquoted but here you go. I wanted to reply to this)

1 Like