[STATS] Statistics site

[crabigator4508]

Oh my bad I was not aware. I thought it would be fine since all the information is already available for free even without the API

[morteASD]

I can’t find anything like that. Where is that said exactly? Not sure that would make sense since the data is available publicly, anyway. Surely they could just restrict the data with the API key.

[prouleau]

There is a whole section on this in the API reference documentation. See here WaniKani API Reference

In particular this text:

you need to respect the limitations put in place by the subscriptions

and this text:

• max_level_granted defines the maximum level of content that’s available to the user. It has two possible values: 3 and 60. The user shouldn’t be able to access subjects above those levels. Lessons and reviews above those levels shouldn’t be available at all and will be rejected if you try and submit them to us.

[UInt2048]

@morteASD

Not sure that would make sense since the data is available publicly, anyway.

It wasn’t always available publicly. That requirement was there before it was.

[Cattongue]

wkstats.com doesn’t work for me.
If I click “login” nothing happens, the console throws a long list of errors.
If I choose anything else, I can try to login, but it always throws an error: “Uncaught TypeError: wkof.Apiv2 is undefined”
I’m using Firefox.
I’ve checked my cache and there doesn’t seem to be any cookie or data linked to that site.
Thanks for the help.

[Cattongue]

Up. Retried today. Nothing changed. Is wkstats obsolete?

[MrInnerPeace]

I dont have this error, maybe generate a new key or try in another browser

[Joeni]

I don’t see any errors, as @MrInnerPeace said - try another browser?

[Cattongue]

I don’t have other browsers on Windows, but I tried Firefox on Linux, and it works Thanks for the suggestion!
It was really rewarding seeing all these stats

[Lahoje]

For some reason my chart has an issue @ level 19. The bar for that level is thin and going downwards, and when I click on it to include it my average changes to minus 28 days.

It’s been like this for a quite a few weeks now, and I’m also not the only one encountering this issue:

How long do you guys take to finish a level?

[image] Either you did this on purpose with very careful timing, or the chart generator has an issue [image] Hmm now mine has an issue on levels 41 and 42. Definitely didn’t have that last time I used it

Console

[Hubbit200]

@rfindley the wkstats /settings page is giving me a 404 Not Found, is this a known bug or…? Everything else on the page works and I’ve tested it in Brave, Edge, and Opera, and it happens in all of them.
Sorry if you already know about it, just thought I should mention it!

Also… any idea if you’ll have any time for the projections page sometime soon?

Thanks!

[rfindley]

If I remember correctly, ‘Settings’ is a placeholder for being able to configure the dashboard. The plan is to be able to select which pieces of the site you want on your dashboard.

Unfortunately, I don’t know when I’ll be able to work on the projections page. I keep thinking I’ll have time coming up, but then Things Happen™. But I’m finally back to working on Japanese stuff, so we’ll see what happens.

[VegasVed]

@rfindley

we’ll see what happens

Things Will Happen™

[UInt2048]

I’m excited to announce that there’s now a userscript that adds a provisional projections page to WKStats.

[Userscript] WKStats Projections Page

^^ Install using the big Greasyfork URL right above! ^^ GitHub to propose changes and such This script adds a provisional projections page to WKStats, since it’s been “under construction” for so long… Because of this, you have to go to the WKStats projections URL to see it. Thanks to @rfindley for the site and I hope this is helpful! Are you unable or would prefer not to use this userscript? You can still get projections with @bagusprabangkoro’s site.

Screenshot of Userscript Projection…

[sumsum]

I don’t know why, but somehow my level statistics broke?

A few days ago it still looked like this:

And I think this is closer to the truth…

I tried to “Refresh Data” but that remains the same.

edit: I found some more Info
The console output looks like this:

--[ APIv2 /resets ]----------------
Count: 0

--[ APIv2 /level_progressions ]----------------
Level 19: (2016-08-28 - 2019-01-11)
Level 20: (2019-01-11 -    now    )

--[ Level-ups ]----------------
Started: 2015-03-13
Level 1: (2015-03-13 - 2015-03-20) -    7 days,  1 hour , 34 minutes (source: Wanikani start)
Level 2: (2015-03-20 - 2015-04-02) -   12 days, 17 hours, 40 minutes (source: kanji estimated from vocab)
Level 3: (2015-04-02 - 2015-04-13) -   11 days,  0 hours, 42 minutes (source: kanji estimated from vocab)
Level 4: (2015-04-13 - 2015-04-26) -   13 days, 10 hours, 43 minutes (source: kanji estimated from vocab)
Level 5: (2015-04-26 - 2015-05-09) -   12 days, 17 hours, 22 minutes (source: kanji estimated from vocab)
Level 6: (2015-05-09 - 2015-06-11) -   32 days,  8 hours, 54 minutes (source: kanji estimated from vocab)
Level 7: (2015-06-11 - 2015-09-15) -   96 days, 12 hours, 29 minutes (source: kanji estimated from vocab)
Level 8: (2015-09-15 - 2015-09-26) -   11 days, 11 hours, 11 minutes (source: kanji estimated from vocab)
Level 9: (2015-09-26 - 2015-10-27) -   30 days, 15 hours, 13 minutes (source: kanji estimated from vocab)
Level 10: (2015-10-27 - 2015-11-02) -    6 days,  6 hours, 18 minutes (source: kanji estimated from vocab)
Level 11: (2015-11-02 - 2015-11-18) -   15 days, 18 hours, 52 minutes (source: kanji estimated from vocab)
Level 12: (2015-11-18 - 2015-12-05) -   16 days, 20 hours, 39 minutes (source: kanji estimated from vocab)
Level 13: (2015-12-05 - 2016-03-21) -  107 days,  7 hours, 11 minutes (source: kanji estimated from vocab)
Level 14: (2016-03-21 - 2016-04-05) -   14 days, 13 hours, 24 minutes (source: kanji estimated from vocab)
Level 15: (2016-04-05 - 2016-04-13) -    8 days, 13 hours, 40 minutes (source: kanji estimated from vocab)
Level 16: (2016-04-13 - 2016-04-26) -   12 days, 11 hours, 20 minutes (source: kanji estimated from vocab)
Level 17: (2016-04-26 - 2016-05-13) -   17 days, 13 hours, 11 minutes (source: kanji estimated from vocab)
###################
Level 18: (2016-05-13 - 2022-01-21) - 2078 days, 15 hours, 10 minutes (source: kanji estimated from vocab)
###################
Level 19: (2022-01-21 - 2019-01-11) - 1107 days, 21 hours, 40 minutes (source: APIv2 level_progressions)
Level 20: (2019-01-11 - 2022-01-26) - 1110 days, 14 hours, 11 minutes (source: APIv2 level_progressions)

Which then causes this error:

I recently did some of the “newly” added items and vocab and also might have guru’d a few odd kanji that were still missing anyway, which apparently did strange things to the level 18 end / level 19 start?

edit 2: copied more stuff in. The dates from APIv2 seems fine(?), but apparently for the level 18 end / level 19 start the “estimate” wins and somehow I broke that

[rfindley]

This is an issue with old data. In the past, Wanikani didn’t record exactly when a user leveled up, so I have to ‘guess’ based on things like when 90% of the kanji on that level were ‘passed’ (i.e. reached Guru). To make things worse, there was a period of time around 2014 or 2015 where the time that certain things leveled up got recorded incorrectly (i.e. bad data). Also, occasionally Wanikani moves items to other levels, and it breaks the guessing algorithm. So in the case you’re experiencing, you end up with a negative number.

I actually have the same problem with my own data. Fixing the ‘guess’ algorithm to account for one situation always seems to break it for another situation. It’s a much more difficult issue than it seems like it should be.

[svenkevs]

It makes a lot of sense that the information for kanji/radicals/vocab above level 3 is not displayed if you don’t pay for a subscription.

But I wonder why the charts just fill in every level with the values for level 3 (see image)

While it does show higher level kanji as locked in all the items overviews (except for the Wanikani overview):

In my case I am now reaching a point where I should soon decide if I want to purchase a subscription, and seeing what level could get me how far in reading things like wikipedia or the news could provide very convincing arguments to pay for the subscription, without giving info on individual kanji/vocab provided by Wanikani?

Either way I am likely to buy a subscription when I finish level 3, but some extra stats on what I can do with the next levels would make for a more convincing case.

Considering that free users can actually see which radicals/kanji/vocab are in which level for all levels on Wanikani, just not do the lessons/reviews etc., it seems weird that this is still hidden on wkstats.

Either way it’s a great site, so thanks to (all) the author(s)! It’s already very useful if you are just going through the first three level

[Kazzeon]

There are other people who have posted this image in case you really wanna know.

Wkstats displays incorrect JLPT kanji percentages

[Screenshot_20211125-200911_Brave]

What level does Wanikani start being less useful at?

Indeed a pretty good suggestion, level 45 is actually pretty much when this graph flattens out a lot (wkstats Reading Coverage, turned into a graph by @chaswrig) [image]

Reading Levels

WKstats (https://www.wkstats.com/) has a page that shows your wk level against different sources of text: [Screen Shot 2020-09-03 at 4.11.09 pm]

[svenkevs]

Thanks!

I found out that you can actually see the charts in full if you are not logged in:

It seems like the limitation to level three is in place ONLY if you are logged in (on a free account with the api key linked). As the opening post states that these charts are supposed to be readable even without api key, can I assume it is a bug that for logged in free users these tables are limited to level 3 @rfindley ?

[Saimin]

I think there’s no harm in making these very general stats public anyways.