You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is room for improvement with our data. It would be good if we could develop a logging system which could be used to analyze the robot's behavior. If we could log several data types ( messages, controller inputs, motor outputs, power distribution board channels, vision inputs, etc.) and have a record of everything vs time, and a way to easily export this data, it would likely pay dividends.
some ideas:
Easily store data throughout the various classes. Easily create logger instances?
Low operational impact, separate thread? remove in production builds?
Ability to export to CSV?
The text was updated successfully, but these errors were encountered:
WPILIB has someone working on something like this, but said it won't be ready until a little after kickoff. Not sure if the best path forward is to use our own stuff or if we should wait for them
There is room for improvement with our data. It would be good if we could develop a logging system which could be used to analyze the robot's behavior. If we could log several data types ( messages, controller inputs, motor outputs, power distribution board channels, vision inputs, etc.) and have a record of everything vs time, and a way to easily export this data, it would likely pay dividends.
some ideas:
The text was updated successfully, but these errors were encountered: