The start with 0 isn’t implemented for the accuracy info yet. And the 150 days average is a running average, meaning on each day it is the average of itself and the 149 previous days. And because the accuracy changes, so does the averaged graph.
Edit: so the number you were looking for is at the last value of the graph on the right, which looks like about 93%.
Also this accuracy is not the same as the WK stats accuracy. WK stats shows the accuracy that you would see while doing the reviews:
Mine is the one you would see when you finish the reviews:
Thank you for trying out the website. I’m glad you like it!
I actually have not implemented a time out. Sometimes it has to wait for the next batch because the API is throttled and it freezes for 10-20 secs. Maybe it was that? Otherwise there might be some other problem.
Anyway, I hope you keep enjoying the WK History website
As you can see the time frame can be set in number of days and months. Then a table with reviews, accuracy, and lessons - divided into radical, kanji, and vocab - is displayed. You can look at the development of those criteria in the intervals you specified (and can go back as far as you want with the arrows at the top). The current day is never counted.
I hope you like it!
Also, this is currently not the WK stats accuracy, but the one at the end of reviews. I’ll implement the other one in the future if you like it more.
Done that! It looks way better. I tried to imitate the wanikani-community-style of blurring the furigana until you hover over it. I hope it isn’t patented
Added it, great suggestion!
I also added a “Started” and “Finished” info to each level which I thought would be interesting to know in absolute time:
And now finally, @UInt2048 I would really like to work together with you to implement your projections userscript for wk stats in, for example, the level chart. I.e. I would like to let people see visually how long they are going to take to finish; like a level chart that automatically has a projection up to level 60 and maybe a slider where you can set “fastest”, “median”, “average”, or “off”. If that is what you had in mind?
I don’t know if Sully22 wanted to create something similar? It would probably be pointless to create the same thing twice. But from what I have read he wanted to implement it as a table. Then we would have two different ways to view the data which is good in my opinion.
I also really like how Nihongo Stats looks and works. It is a really great idea to have data from multiple Japanese learning services combined into one overview. Now I’m kind of depressed haha
Yeah, I think so, too. I can’t picture what you suggested, but I’m imagining a line chart of some sort where one axis is level and the other is time, and we could visually see the difference between projections…
It’s a good idea, but I don’t use any of the other stuff, so only the WK portion is relevant for me anyways.
There’s always going to be alternatives… I made a projections userscript only to later discover that someone else had already built a projections site!
As I mentioned in Sully22’s thread, the userscript’s 1.3.5 created a nice array of objects containing all the real projections (not past levels that you have already taken care of) where the indices are the level being projected for.
How do you get your API data to your site? As previously stated, my userscript assumes the Open Framework handles this, which your website does not appear to use, although it does try to imitate its loading screen with the slider dialog…
I do still like the wkstats accuracy info more, since it tells me what I’m struggling with in terms of reading or meaning. You can see that for me readings are harder than meanings:
Acually, whether the total accuracy score is the wkstats one or the end of session one isn’t that important to me. I’d like to see both, but I think if I had to choose I’d stick with the end of session stats as those are most relevant for item progression.
Reading these and then confirming that I was right feels really good
Either that, or what I was trying to say, just adding the “projected levels” to the current level chart. But that would probably not be that interesting because there is no real time reference in the chart itself so one would have to hover over the levels to see when they are going to be finished.
Oh, I didn’t even know about the WK open framework. This is the one you are referring to, right?
I just programmed an API-data-and-cache-handler myself with IndexedDB but if I would have known that someone already did all this and made it publicly available I would have gladly used it.
Maybe I should change to that? Because it seems quite nice and your code would probably be implemented more easily.
Yes, that’s what I meant. It would make it extremely easy for me, since I could continue to use the Open Framework already there on your site – this is actually what I do on my projections userscript on WKStats. I could even make a PR to add it to the site myself if you did that.
However, you’re of course under no obligation to do that.
Apparently when averaging over 50 days the graph seems to be treating my hiatus (in which I did zero reviews) as relevant data points, which creates the above slope artifact. Could you add an option to only include data after a certain date (e.g. one’s reset date)?
For some later levels you get more than 90% of all the level’s kanji (which is what is required to level up) as soon as you unlock the level, so you don’t technically need to guru any radicals to unlock enough kanji to level up. As such those levels can be completed twice as fast as normal levels, since you only need to guru the kanji you get from the start of the level