Thoughts on a smugprickness rating
Inspired by an article shared on a certain parkrun discussion group on Facebook entitled “98% Of Couples Who Go Jogging Together Are Smug Pricks, Finds Study” I decided to attempt to quantify a smugprickness rating.
I originally posted “I think that running the same parkrun should get an higher score, but finishing far apart should diminish it, but I’m not sure what other factors should be involved?”
Parkruns run together could be calculated with just one extra field, added to my database, as could the difference in finishing positions (in fact both could be served by the same field as the presence of a difference score could be counted?)
A1214775 and A2329944 have run together 22 times, with the total difference in finishing positions being 3225. Whilst this data alone would allow a mean difference to be calculated ( 147 for those keeping count) this is not satisfactory as a rating.
I did consider using the total number of runs as a factor, but short of replicating the entire results database of each party it would be impossible to create a bi-directional rating, which as this is referring to couples is quite an important feature. It is however quite easy to count the number of Saturdays since the first time the same parkrun was run.
For A1214775 and A2329944 their first parkrun together was on 2016-04-02, 254 weeks ago, some simple maths produces a runtogether rating of 12 .
An ideal mean difference would be 1 (I guess it would be 0 but parkrun does not condone that sort of togetherness at parkruns), an ideal runtogether rating would also be 1, that is to say that every possible run was run together.
For want of any better ideas I divided 10 by each of these numbers, and then multiplied them together to produce a number between #DIV/0! and several thousand, but typically between 0.00 and 100.
For A1214775 and A2329944 this results in a score of 0.02 %, which seems about right for me.
I now place this at the mercy of the community, who I am sure will be able to find within many faults.
List of events run together
Event | Date | A1214775 | A2329944 | Field Size | |
---|---|---|---|---|---|
22 | Coventry | 2019-11-23 | 217 | 463 | 482 |
21 | Bushy parkrun | 2019-11-09 | 998 | 1245 | 1331 |
20 | Bedworth | 2019-09-07 | 215 | 195 | 215 |
19 | Bramley | 2019-08-31 | 083 | 225 | 227 |
18 | Worcester Pi. | 2019-08-24 | 089 | 363 | 278 |
17 | Bevendean Do. | 2019-07-13 | 024 | 058 | 060 |
16 | Ludlow | 2019-06-15 | 036 | 079 | 081 |
15 | Alvaston | 2019-06-08 | 044 | 142 | 153 |
14 | Burnham and . | 2019-05-18 | 078 | 403 | 428 |
13 | Pontypridd | 2019-05-04 | 288 | 407 | 439 |
12 | Isabel Trail | 2019-04-27 | 047 | 180 | 210 |
11 | Perry Hall | 2019-04-06 | 051 | 159 | 202 |
10 | Bedworth | 2019-02-16 | 042 | 300 | 329 |
9 | Woodhouse Mo. | 2019-01-12 | 285 | 686 | 721 |
8 | Perry Hall | 2019-01-01 | 477 | 554 | 561 |
7 | Walsall Arbo. | 2018-12-01 | 312 | 311 | 312 |
6 | Pontypridd | 2018-09-15 | 234 | 244 | 274 |
5 | Pontypridd | 2018-09-08 | 048 | 242 | 256 |
4 | Bevendean Do. | 2018-08-18 | 022 | 042 | 043 |
3 | Riverfront | 2018-01-01 | 125 | 375 | 392 |
2 | Pontypridd | 2017-10-28 | 045 | 211 | 219 |
1 | Pontypridd | 2016-04-02 | 079 | 128 | 134 |
I stoped tracking this at the end of 2019.