Quote:
Originally Posted by apalrd
Why not "script" in the native language, C/C++?
You could run the code procedurally, call functions that do stuff, sequence them, etc. and run them in their own threads.
|
There are about 4 more posts that discuss this in greater detail but this was the easiest to quote.
In 2007 I was working with team 1493. We had two programmers, I focused on the autonomous code, and the other programmer focused on the tele-op. I developed code for the first 4 weeks, before we got a Chassis to program, in the manner described by other posters. To the extent where some one with no knowledge of C could read our autonomous mode and tell exactly what it did, more importantly some one with no knowledge of how the underlying control algorithms worked, could, with little to no direction write autonomous modes. The 5th week I tuned all of the control loops.
That weekend (between the 5th and 6th weeks) my mother passed away, I had to go home, and for a while robotics was at the bottom of my priorities. However because of the way I wrote the code, our other programmer, as well as non programming control team members were able to script the autonomous routines. When I got to the regional all that I had to do was fine tune control loops.
I highly recommend developing in this manner.