|
Re: IterativeRobot, CommandRobot, or SampleRobot for brand new programmers?
If your robot is going to do
one
thing
at
a
time,
Then yes, Sample robot is probably the easiest way to get those things working sequentially. Iterative and command based take a bit more work to get set up to do the first thing. However, robots generally are expected to drive, sense, and manipulate all at the same time, making it very easy to get into states that you did not expect. Unless you already have experience implementing real-time systems on sequential processors, and want to teach this to your new programmers, I cannot recommend this paradigm.
Iterative and Command based are a bit more work to start (though not if you start with a good template), and they are much easier to add additional, simultaneous functions which potentially operate on different time scales. Command based is really object-oriented (to the point where it's difficult to see where things start), so if you are not comfortable in that environment, I can certainly see why you would not want to use Command Based.
Iterative should give you a good bit of the real-time being behind the scenes without getting wrapped around object orientation too tightly - it's pretty much that someone else has written the high level main loops, and the low level hardware libraries, and you're writing subroutines do do a single pass of the different subtasks.
Disclosure: I did not set up our programming sub-team, but we use command-based, and intend to stick with it.
__________________
If you can't find time to do it right, how are you going to find time to do it over?
If you don't pass it on, it never happened.
Robots are great, but inspiration is the reason we're here.
Friends don't let friends use master links.
|