search

Mercury1089 / 2016-robot-code

Team Mercury 2016 FIRST Robotics season code for FIRST Stronghold
0 stars 0 forks source link

Investigate adding a chooser in the smart dashboard so that we can select the match number #22

Closed gartaud closed 8 years ago

gartaud commented 8 years ago

It will be easier to make sure a log is for a given match if we record the match number in the log itself. This could be done easily by adding a chooser in the smart dashboard so we can select the match (e.g. Q1, QF2, etc). Then after initializing the logger we would record the match number in the log. If time allows look into this... Thanks.

rpatel3001 commented 8 years ago

Might be prone to user error ie not updating the match number. The Driverstation class exposes the alliance and driver station number that could be used to correlate log files to match numbers. On Mar 22, 2016 7:16 AM, "Mr. A." notifications@github.com wrote:

It will be easier to make sure a log is for a given match if we record the match number in the log itself. This could be done easily by adding a chooser in the smart dashboard so we can select the match (e.g. Q1, QF2, etc). Then after initializing the logger we would record the match number in the log. If time allows look into this... Thanks.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/Mercury1089/2016-robot-code/issues/22

gartaud commented 8 years ago

Good thinking Raj! Let's go for getTeamNumber(), getLocation(), getAlliance() and if not null value and name

gartaud commented 8 years ago

Getting location and alliance as Raj suggested will suffice. Closing