Quote:
Originally Posted by Sperkowsky
We use github also. I'm not trying to offend the news people but to our team coding simple driving (tank mecanum omni ect) is something that take max 20 minutes and to program the lift another maybe 15. If that's not everyone I feel bad and we will help but it shouldn't be an issue for them to come back easily. I'd be more mad they just lost a 500-1000 piece of hardware.
|
It may be true that you could get driving code that quickly, but why would you want to leave yourself with no other option. In addition, for our team the level of sensor integration and other control systems that we have implemented would take days if not weeks to re-create from scratch. This is why we make backups on a flashdrive as well as using an SVN repository on SourceForge.
Quote:
Originally Posted by dtengineering
A USB key of "known good" software taped to the driver station.
Github, Dropbox, Google Drive... none of them will help if you drop your laptop half-way through re-programming your robot, while you're standing in the queueing line.
With a flash drive and a helpful alliance partner, you at least stand a chance to set things right.
Jason
|
Exactly! We use our SVN on SourceForge as a development platform for merging code between multiple programmers as well as a backup. But we also keep a backup on flashdrive especially at competition. At an event, whenever a change is made to the code our lead programmer (student) deploys and tests the change... then it is my job as the programming mentor to make a backup of the code which is now on the robot onto my flashdrive. This ensures that we are never in doubt as to what code is currently on the robot. And it gives us immediately available access to our source code since we rarely have internet access at the venue.
So sorry to hear that 1432 learned this the hard way... it is never an easy lesson. Please let us know if there is anything we can do to help out in your recovery process.
Good Luck!