Quote:
Originally Posted by MatthewC529
You think of this as a game in code because it is a game. It's why I use iterative. Reminiscent of a game loop. But unlike a game it's a lot more difficult to handle AI and ML in reality, let alone competition.
|
Why would it be difficult to handle AI? I guess AI should have more clarity as it's a real generic term. When I say AI especially in terms of gaming I'm really saying what is written in this
book. I loved this book as our code uses a very similar model of goal driven classes... the context of AI written here is really a way to manage events in real-time.
Given this context... the AI foundation for our
game code we wrote , and the robot code are 100% identical.
I think your context of AI includes the details of the goals themselves... assuming this to be true, it should be abstracted away to not be a part of the AI... so let's take 2011 logomotion as an example, and only just the autonomous part as an example to illustrate my point:
goals
drive forward 10 feet
raise arm to 9 foot mark
drive forward one more foot
open raptor claw
lower arm 6 inches
drive backwards a few feet
In this example these are high level goals that I could have used in the game, the details of how to do the goals would have been different, and FWIW... driving forward *straight* is not as easy as it sounds.
