Closed BenjaminTran closed 4 years ago
This is great, very detailed info.
Basically it's trying to figure out the deck settings for initial ease factor. Filtered decks don't have any settings, so it gets confused, and fails back to 250, the default ease if you don't change anything for a new deck.
The good news is as soon as you study outside the filtered deck, it should calculate the ease off of the total history, and ignore that it was at 250 for a minute.
I just pushed a new version that will fix the error message, but... still trying to confirm it's rescheduling correctly.
This looks right to me:
It's not calling the last review "filtered," but it really was a filtered review with rescheduling enabled. Does v2 scheduler not distinguish reviews from filtered reviews?
Also note, if you're testing this, the algorithm only looks at previous reviews, so ease factors are really off by one row.
Here's one I failed during filter. 가볍다 (to be light)
Ease is static that last round, which is surprising. But I'm not sure what will happen after I have another regularly scheduled review with that card, I need to hit the normal relearning step to double check.
And weirdly it used to call out filtered reviews explicitly for me, but doesn't anymore. The two most recent reviews on that image are actually from a filtered session.
Still testing this one, thanks for the info.
Ease is static that last round, which is surprising.
Please see my "edit 2" here. I am not quite sure if we mean the same thing. I think that you expect that the review on 2020-08-06 at 10:36 should have lowered the ease?
Intuitively, I would expect an ease decrease, too – but with the review at 10:01.
The latest patch should address this.
Here it correctly calculates and applies a new ease factor on graduation from a filtered deck (but the factor decreases because it hits the ceiling specified by the leash, which prior reviews weren't bound by):
Here's one that's pretty close to target, so it gets a slight adjustment:
Keep an eye out and let me know how it works. Thanks for all the help so far.
First, sorry, I have never reported a bug on GitHub before so not sure if this is the proper place to put it. Also, thanks for your work with this addon.
Bug description
Ever since the update where the initial ease factor is taken from the deck options, I have been getting an error (see below) when I open any filtered deck for the first time after starting up Anki.
This error only appears when I begin to review from a filtered deck and it is not card dependent as I get the same results with different cards. If I review from a non-filtered deck then I don't get an error and the add-on calculates the ease factor as it should.
Debugging attempts
In the two images below, the top row is the most relevant row (date is 08/05). In this example I used the same card. The relevant steps are below.
For the non-filtered deck image, the ease appears to be calculated appropriately as far as I can tell and any subsequent cards are calculated correctly as well.
In the filtered deck image the ease is set to 250% and any subsequent card after that is set to 250% regardless of past answer history. This is also the case if I subsequently go to a non-filtered deck and begin to do reviews there without restarting Anki first. As far as I can tell, the ease factor that it sets the cards is either
I have reverted back to the version (95c42b2) right before the commit to the update and everything is working as expected. Hopefully all of this info here is clear and is helpful.