Yeah.. all these system ideas are great, but...
But we're getting off topic a lil bit.
We shouldn't worry about the system right now. This is the programming thread
We should build the system around the program, not the other way around. As far as I'm concerned, the system isn't an issue, because we don't need a system yet as there is no program. As I see it, we should be doing the following:
1) Figuring out how we are going to detect stuff.
Is it radar? GPS? LORAN? Ultrasound? How are all these going to interface with the program(s)? Image processing was mentioned.. can we implement this? Can we implement any of this? Does somebody have experience that can help point the way for others?
2) Block diagrams/Outlines/etc
Ok, we need to come up with a basic guideline of how this system is going to work, communicate, and etc. As I said before, a layered approach seems to be best in my mind. What elements to the program do we need? What needs to be in the program for it to do its task? What exactly is it going to do anyways?
3) Development
How are we going to coordinate development? Who's going to be in charge? Where is the code going to be stored? I think we've pretty much established we're going to use Linux for the central command system because I dont see any arguments for anything else, so what programming languages are we going to allow development in? Coding guidlines. Other stuff. More coordination.
There are so many questions that need to be answered, so let's keep it simple for now. Lets figure out how we're going to make this beast and then let's make it.