Tool for searching for matches affected by short autonomous glitch

[Joe Ross]

Based on several earlier reports and the replays of QF1-1 at the Michigan State Championship, I decided to create a tool that will measure the length of autonomous in matches connected to FMS. It will search through all logs in a specified directory (it defaults to the default directory for logs on Windows 7 C:\Users\Public\Documents\FRC\Log Files). It will determine which ones were FMS connected and then display the length of the Autonomous as commanded by the field.

For example, on a clean match it will display:

2014_04_05 14_38_16 Sat.dslog: 10.14

On a match that was affected by the glitch, it will display two outputs for the same log file:

2014_04_05 13_13_05 Sat.dslog: 1.50
2014_04_05 13_13_05 Sat.dslog: 8.28

To start, run the exe, select the path of your log files (if necessary), and press the start button. The output box will update as it scans through the matches. The tool requires both the .dslog and .dsevents files.

If you find a match that was affected, please post your log.

It is a LabVIEW program, and should be runnable by any computer that has the Driver Station installed (a full LabVIEW installation should not be necessary, but has not been tested).

[tStano]

This comes from the match in Milwaukee (Week 4) where we rammed our alliance partner.

[Joe Ross]

Originally Posted by tStano

This comes from the match in Milwaukee (Week 4) where we rammed our alliance partner.

This log doesn't look like it comes from a match. It doesn't show any autonomous period at all.

[BigJ]

I'll ping him about it, we definitely found one, but he may have attached the wrong file.

[tStano]

This log is definitely the only one the tool spits out as bad. If it isn't an actual match, we don't have a bad log to submit. Do you need the dsevents file as well? Sorry I'm so bad at this.

[Joe Ross]

Originally Posted by tStano

This log is definitely the only one the tool spits out as bad. If it isn't an actual match, we don't have a bad log to submit. Do you need the dsevents file as well?

Sure. Thanks.

[tStano]

Both the files are in this folder now. Hope it works this time.

[Joe Ross]

Originally Posted by tStano

Both the files are in this folder now. Hope it works this time.

Yes it did. The log file does show the issue.

I didn't realize that the .dsevents file was required for the log viewer to function properly.

[rrossbach]

Out of curiosity, has there been any word on the root cause determination and elimination?

[Joe Ross]

Originally Posted by rrossbach

Out of curiosity, has there been any word on the root cause determination and elimination?

I didn't hear anything, although I did hear that it affected such a tiny percentage of matches that the fact it happened twice in a row in Michigan was amazing.