JavaScript is required to use Bungie.net

Forums

originally posted in: If you have a 1.0 kdr...
1/14/2016 12:35:20 PM
2
Think about it Rumble match. Player 1: 25 kills, 1 death. 25.0 kd Player 2: 15 kills: 3 deaths: 5.0 kd Player 3: 10 kills: 8 deaths: 1.25 kd Player 4: 5 kills: 10 deaths: 0.5 kd Player 5: 2 kills: 36 deaths: 0.05 kd Player 6: 0 kills: 7 deaths: 0 kd Average kd: 5.3
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Jesus. Your poor, poor Math teacher was just found swinging from a belt in his closet.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • You're actually stupid. You can't average the resulting ratios, you have divide the total deaths in the match into the total kills

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Averages don't work like that, you add every player's individual kd and then divide it by the total number of players. Slightly less than 1.0 would be the global kd, not the average kd.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • No, see my post to the main thread. The high K/D numbers skew the average a lot more than low K/Ds. So that 25 K/D is going to send the average through the roof. There is no equivalent "negative" K/D that can have that kind of influence, since increasing the number of deaths will never yield less than 0. So going 25/1 gives you 25 K/D, while going 1/25 gives you 0.04. 25 - 1.0 = 24.0 <--- huge difference! 1.0 - 0.04 = 0.96 <--- small difference!

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon