time unit on problems differs
You must be logged in to post a reply. If you don't have an account, you can register.
|ndbgo||On some problems, I get the message "last seen 3 days ago" while on others I see "last seen 74 hours ago." Why is there a difference? I have the impression that the problems where it says "74 hours ago" or similar, show up more often than they should when I keep hitting "good," but I haven't been able (yet) to verify that.|
|ndbgo||Darrell, just sent you an email with a screen shot to illustrate what I mean.|
|Darrell Malick||Hi Nichole,
Why is a hard question. :-) But here goes.
Originally I displayed the intervals fairly simply, such as "Last seen 1 day ago." But this had a problem. If you last saw it one day ago, the intervals for the Easy/Good/Hard buttons probably looked something like: See it again in 2 days/2 days/1 day. The resolution was too low to see that the different buttons were resulting in different intervals.
Next I scaled each number so that the resolution would be higher. I chose 5 as the switching point. So you would see "Last seen 24 hours ago" And "See it again in 40 hours". The units wouldn't switch from hours to days until you reached 5 days. Then you could always see the differences.
But then you frequently found yourself having to do math. How much difference is there between 110 hours and 5 days? Or 33 days vs 2 weeks? Or 21 weeks and 5 months? When the numbers were being displayed with different units, I just didn't like having to do mental math all the time.
So now the "Last seen" and "See it again in" numbers are all using the same units. (Excluding "forgotten = 10 minutes". So the display units chosen for the interval is now based on the smallest of the 4 relevant numbers - because the smallest determines the required resolution to ensure being able to see the differences.
|Darrell Malick||Sorry for misspelling your name. :-)
|ndbgo||Okay, that makes sense, but doesn't explain the situation I'm encountering a lot these days: last seen 71 hours (almost 3 days), hard 88 hours (3.7 days), good 126 hours (5.3 days), easy 167 hours (7 days). So which ever way you round it, you get different numbers for days, so why keep it in hours? I believe it is relevant for the moment I see a problem again, because it is my impression that anything in minutes will show up again after 10 minutes, anything in hours will show up again the next day, etc. Or am I mistaken there? I'm still trying to check if the problems where I see a different time unit than I expect come up (much) earlier than I want based on which button I click, but so far I've only managed to establish that when the units remain in minutes (like I wrote earlier this week), but those problems seem to have resolved themselves by hitting "forgotten" to start learning them over again.|
|Darrell Malick||I show the units in increments of hours or days so that you can see the difference the effect of pressing different buttons is having. Even if you had numbers like 14 hours and 21 hours - both would round to 1 day. But this is confusing for a (new) user. Also, the next scaling is based on 14 hours or 21 hours, not 1 day.
There is a hard limit on a forgotten problem to keep it from coming up again before 10 minutes expires. Other that this hard limit, the program will "look forward" and give you any problems that are due now or will become due today.
So, if you are studying at 10am, there might be a problem that will come due at 8pm today. The program will give you this problem today.
I can't speak to your other odd occurance because I haven't seen it and don't know what path caused it. Sorry.
|ndbgo||Hi Darrell, thanks for the elaborate reply, that definitely explains some of the behavior I'm seeing on when a problem comes up again. I'll keep an eye out for the other oddity I reported earlier.|
Post a reply