Sunday, July 5, 2015

The MAVTV 500 and the Trouble with ARP

Hey there Internet. I missed you. Did you miss me? I hope so. I really love writing this little IndyCar blog. This week, we'll talk about the black hole that ate June; a classic in Fontana; and what I'll be doing the rest of the year. Let's do it!


The June Black Hole

As you can tell by the .BlogSpot in the middle of my web address, I use Google tools almost exclusively to write this here blog. I don't know why, but there was a period in early June when my computers (one all-in-one and one laptop) refused to play nicely with Google's tools when using Chrome. That's weird. I still don't know why that happened. It still happens to a degree. I don't pretend to speak computer, so this will just go down as a mystery for the ages.

Anyway, that really slowed me up. Then the hard drive on my laptop died. It just gave out. Fortunately, the senior pastor at my parish (shout out to the Rev. David J. Glesne) speaks computer much more fluently than I do, and he was able to save most of my stuff, and with the help of an extremely skilled parishioner (shout out to Frank Neumann) was able to get me back up and running with an SSD replacing my old hard drive. Anyway, I was hoping to give you the backlog of scorecards, but with my computer out of commission for so long the backlog became insurmountable.

But, the rest of my sob story will have to wait, because I prefer to focus on the positive, so let's talk about:


A Classic in Fontana

Here is the scorecard for the MAVTV 500. If you didn't like this race, you don't like IndyCar racing.

FinishDriverGridLedCompletedScore






1Rahal191525092.13
2Kanaan62325061.12
3Andretti33125051.85
4Montoya5525046.65
5Karam10525053.17
6Dixon7725042.70
7Jakes23025071.74
8Kimball13025045.65
9Pagenaud1325015.82
10Hawksworth17025045.65
11Munoz111425031.06
12Coletti21025045.65
13Mann22025043.48
14Bourdais15025023.91
15Hunter-Reay14324918.00
16Briscoe16724918.79
17Vautier20024621.63
18Sato9312410.16
19Power862241-0.23
20Chaves1802374.57
21Newgarden120161-6.08
22Carpenter41157-20.10
23Castroneves243136-17.98


You will likely note two things about this scorecard:

1) It lacks a column for "Average Running Position"
2) Longtime readers will notice that there is a larger-than-normal "gap" between the high and low scores (92.13 to -20.10)

All of this has to do with why I haven't updated the backlog of scores from after the Indy 500, so let's talk about that now.


Going Forward

As I said at the top. I really like writing this blog. I know I'm a little erratic. I know that I'm not the most active guy on Twitter. The IndyCar Blogs (follow them @TheIndyCarBlogs, it's awesome) has me rated as a "Semi-Active Blog" and that's fair. But, I love it. I really love it. I think it's fun to try and figure out who had the best race. I find it fascinating to look "beyond the box score," as it were. I have no desire to hang it up any time soon.

Let me repeat. I have no desire to hang it up any time soon.

But (there's always a but, isn't there), I can't keep going the way I was. The formula that I like to use for Race Scores involves computing Average Running Position. To do that, I have to take the lap chart that IndyCar provides at indycar.com/stats and then I have to manually enter into a spreadsheet where each car is scored for each lap. I have found literally no other way to do this. This is a major problem for oval races. The shortest oval races on the schedule (in terms of laps) are Indy and Pocono at 200 laps a piece. I just can't enter that many laps in a week with the time I have available.

And, this brings us to the MAVTV 500 scores that you see above. These scores are computed using what I call my "Old Formula." This formula basically accounts for two things: finishing position and positions gained from green to checkers. They do a pretty good job of some things. For instance, it shows the relative strength of Sage Karam's day (whether or not Karam's skill / racecraft was as good as his performance on paper is up for debate). Also, the above scores reward drivers like Stefano Coletti and Pippa Mann for keeping their noses clean and finishing at the back end of the lead lap.

The problem with the formula used for scoring above is that it OVER emphasizes these distinctions. There is no universe in which the second best drive of the day was turned in by Buckshot Jakes, but that's what you get with this formula. Mann and Coletti (as I said above) deserve praise, but they didn't do better than Scott Dixon or Simon Pagenaud. So, I have to do something different. So, I'm going to do something different. Here's what the rest of the year will look like for me:

- Having lost so many races to the June Black Hole, I'm going to put the RSWC to bed for the year. It will be back.

- I will continue to score road/street events with the formula that includes Average Running Position. Those have few enough laps that I can manage.

- I will use the remaining oval races to try and figure out a new way to score ovals.


Oval Possibilities

This formula just doesn't work for ovals. I've thought that this was true since I started doing this back in the 2012 season. I made the change after the 2013 Indy 500 (my first season blogging about my little experiment), and I liked it so much better. So, I need a formula that more accurately matches the "eye test." Here are my off the top of the head ideas about how to do that:

- I could adjust the relative weight that I give to both of the terms in this formula (race finish and positions gained). Right now they are equal, and perhaps weighting finish more heavily would "normalize" the results somewhat.

- Insert a term as a replacement for Average Running Position. Something like percentage of laps run in the Top 5 might be good. I think I would be able to tabulate that more quickly than ARP.

Those are basically the two options, although the "introduce a new term" option is really a range of options. So: Milwaukee, Iowa, Pocono; you are my guinea pigs. Prepare to be experimented upon.


Stay Tuned

To my tens of readers, thank you for continuing to read this. I am glad to have you. I am glad that we all have this sport in our lives. Let me know what you want to see going forward. What do you like about my little corner of the internet? What would you like to see different? Got any ideas for how to score ovals? I want to hear from you, so you can leave a comment here or hit me up on Twitter (@ScoringIndy). I know I don't post much, but I look at it daily. Thanks again! I'll see you on Friday.

-- Guido

1 comment:

  1. Sorry to hear about your difficulties. That's no fun. As far as making tweaks to make things easier for you, I'm in favor of that. Things that kill the fun of being a fan are bad things. Might I make the suggestion of maybe using 5 or 10 lap intervals for calculating ARP (i.e. using just laps 5, 10, 15, 20, etc. or 10, 20, 30, 40, etc.)? That'd be a LOT better than doing all the laps, and it'd be a lot better than not using ARP at all, which leads to weirdo stuff like Jakes getting the second highest score for Fontana (when I think we saw him for 45 total seconds all day on TV).

    Anyway, welcome Back, Dom.

    ReplyDelete