[STATS] Statistics site

Things Will Happen™

3 Likes

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

3 Likes

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:
image

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 :sheep:

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.

7 Likes

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)

Screenshot 2022-08-09 at 22.38.12

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 :slight_smile:

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

1 Like

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 ?

3 Likes

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

1 Like

@Saimin @svenkevs @Kazzeon

The charts are working for non-subscribers now.

9 Likes

It works great in showing all the chart info now, thanks!

However, it stopped indicating on which level I am at (like how with the attached image in my previous post, it showed that I was at level 3). It’s not an important feature that I miss or anything, but I don’t know where else to report such minor bugs.

1 Like

I just checked and I don’t have that problem. Did you log back in with your API token?

Yeah, I am logged in, I properly see other data, but I am not seeing my level indicated on the chart anymore (see attached picture).

Perhaps showing the level is now a feature for subscribing users, and free users get the same code as people that are not logged in, an accidental feature perhaps :slight_smile: . I think that is fine and would be fair. I just reported it in case the dev doesn’t want it this way.

3 Likes

Ahh, that makes sense based on the fix I used for non-subscribers. I’ll add it to the “to-do” list, but it’ll be at least a few weeks before I have a chance to work on it.

But in the meantime, the level-highlight will start working as soon as you subscribe anyway.

6 Likes

There is an issue with wkstats.com, do you know why like 90% of the Kanji on the “Items” tab are shown as green (not on WaniKani)? Is there a fix for that? Kinda annoying, I’d like to see when those Kanji are taught among other things

The site won’t show you any items from the non-free levels if you don’t have an active subscription. They become available once you have a subscription active.

3 Likes

Thanks for answering that one. I always forget about non-subscribers (most are subscribed by the time they find wkstats), so I was totally at a loss to understand what they were experiencing, :joy:

3 Likes

Ah that makes sense thanks!

1 Like

The certificate expired and it has HSTS enabled so i’m unable to use it right now :frowning:

Any chance to get it fixed?

2 Likes

If you’re desperate for a temporary solution, setting your computer clock back a day worked for me. That said, I can’t wholeheartedly recommend this as it could be insecure and is probably more of a pain than it’s worth. (ETA: and might mess with any licenced programs on your machine)

It’s fixed. The certificate did auto-renew, but for some reason it failed to instruct the web server to reload with the new certificate.

2 Likes