Post by nwilliard on Aug 4, 2015 4:48:02 GMT
There were several teams who had incorrect timestamp formats. They have resubmitted their scores and below are the updated standings as of last week.
HINT!
A perfect score is 72870
I'm re-posting this example:
the real fault is
2011-11-19 17:44:00 2011-11-19 22:14:00 1,
if you predict
2011-11-19 18:00:00 2011-11-19 21:16:00 1,
that would be a true positive...
(10 points)
if you predict
2011-11-19 18:00:00 2011-11-19 21:16:00 2,
that would be a miss classification...
(-0.01 point)
if you predict
2011-11-19 18:00:00 2011-11-19 21:12:00 1,
that would be a false positive...
(-0.1 point)
if none of your alarms account for the real fault, it will be counted as a false negative (or a missed alarm)...(-0.1 point)
| Group | Submission date | Score |
| embminders | 14-Jul | -1162.41 |
| TNB | 22-Jul | -11.12 |
| embminders | 22-Jul | 2451.33 |
| NRC-TIGER | 23-Jul | -1008.9 |
| Maxtropy | 23-Jul | 3062.33 |
| Phantoms | 25-Jul | -740.85 |
| BUAARMS | 26-Jul | 4817.39 |
| Phantoms | 1-Aug | 1043.27 |
| NotOurFault | 1-Aug | 12177.96 |
HINT!
A perfect score is 72870
I'm re-posting this example:
the real fault is
2011-11-19 17:44:00 2011-11-19 22:14:00 1,
if you predict
2011-11-19 18:00:00 2011-11-19 21:16:00 1,
that would be a true positive...
(10 points)
if you predict
2011-11-19 18:00:00 2011-11-19 21:16:00 2,
that would be a miss classification...
(-0.01 point)
if you predict
2011-11-19 18:00:00 2011-11-19 21:12:00 1,
that would be a false positive...
(-0.1 point)
if none of your alarms account for the real fault, it will be counted as a false negative (or a missed alarm)...(-0.1 point)