Jump to content
Sign in to follow this  
Never

Let's talk about periodic stats, why they were broken, how they were fixed and why my Recent WN8 took a nosedive

Recommended Posts

Hello!

So all that I'm gonna talk about here happened last night over a period of around 4 hours. This post is VERY wordy and somewhat rambly, so be warned. First things first, I'm working on a new feature that will let you see a "Period Breakdown" of each period, so for the period of, say, 24 hours, you will be able to see all the tanks that are counting in that column, along with each tank's individual stats for that period.

But in creating this feature, I ran into a problem where there were massive discrepancies between the amount of battles that the Account Information method provided, and the sum of the battle count of your tanks. For instance, the difference between your overall battle count between the latest update and the one 24 hours ago might have been of 20 battles, but if took the battles played by each tank over this same period and added them up, the number would sometimes be different. Sometimes they were off by just a couple of battles, sometimes by 10 or more.

This is obviously a great issue for a website that is supposed to provide statistical accuracy. I believe that what causes this issue is that not all of the methods of the API are updated all at once, so when the system grabs your stats, your overall battle count updated, but not your individual tank statistics. Again, that's just me throwing a possibility out there, I'd have to talk to someone who has access to the API to know for sure, and I have no idea who that might be.

The way I fixed this was simple: We stopped relying on the overall numbers, and started deriving everything from the sum of each individual tank's statistics. That's what's used to calculate your WN8 already, so it's a logical step. As for potential issues, the only problem should arise in the fairly uncommon case where a tank takes a long time to be added to the API, so players would play several battles in a tank over a period of time that would all get lumped together under the "24 Hours" column once the tank's information got added to the API and WoTLabs could actually see what tank you were playing all along. But the thing is, this issue already happens! It's just masked because the numbers that were shown in the columns were based on those overall numbers which always get updated. The only place where you could see this issue happening was in your Average Tier and WN8 calculations, which several players have noticed and reported on this forum. WIth the now fully functioning system that automatically checks and updates tank information once a day and no longer relies on me checking for new tanks manually, this should be an even more uncommon case.

With that fixed, the feature that allows you to see a detailed list of the tanks played during a certain period will be released very soon!

Whew, that was a long one. Now, for the last topic of discussion: Why my Recent WN8 took a nosedive, and why yours (in very rare cases) might as well: Back in May 2016, we had to create a new table to hold all the detailed tank information (which is the data used to calculate WN8) since the original one could no longer perform its duty. The old table remained behind for historical queries, but as time went on and disk space became an issue, very old data started to be deleted, including those very old records that were no longer relevant... Or were they?

Drama aside, if you're like me and you played very few battles between May 2016 and now, your Recent WN8 might have taken a nosedive. Recent WN8, as you probably know, is based on your last 1000 battles. When the system checked for the update made 1000 (or close to 1000) battles ago, it would take the timestamp and look for the tank information so it could calculate the WN8 for this period. However, if this update happened before May 2016, then there are no more tank information stored! This means that the system was actually using your overall tanks to calculate your Recent WN8, making them look very similar to each other, as was my case.

The way this was fixed was to tell the system to ignore every update made before May 2016, and only look for those made after that point. If you played over 1000 battles between May 2016 and now, no problem at all! if not, then the closest update that has tank information available will be used. In my case it's my last 428 battles, which unfortunately encompasses the 370 battles that I've played in the past month since coming back to the game and sucking really, really bad. So yeah, RIP my Recent WN8, but at least it's not a lie anymore.

That is all for now! If you made it this far, sorry for all the words. I really, really like to write.

Cheers!

Share this post


Link to post
Share on other sites
28 minutes ago, Kolni said:

Does this mean I’ll not be #1 WN8 across all servers or not anymore 

asking for a friend who cares very much about internet schlong

tumblr_p79dg7VBOd1tize68o3_r1_500.gif

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...