I was playing around with one of my bots today that uses the Play/Record block an unusual thought popped in my head. Let me see if I can explain it...
Let's say you have a competition where your bot must navigate a fixed-dimension field (let's say 10x10 feet). Let's also add in the fact that there are obstacles and objects to interact with on the field. (Can you tell I'm trying to avoid using a 3-letter acronym here?)
Finally, let's add in the fact that the bot will always start from the same exact position.
Okay, here's the question:
(Assuming memory isn't an issue, because it may very well be in the REAL WORLD)
What's to keep me from setting up a test field, putting in a Play/Record block configured for 5 minutes (300 seconds) and then recording my manually moving the bot around the field, interacting with objects, performing tasks, and then returning home?
If everything is in a fixed location, all I've got to do is drive the bot with my hand into the proper position for a task, use Motor A if required and move it to perform a task, and then move it on to the next task.
I realize that there might be subtle differences in measurements, but if we're dealing with a table of less than 10 feet, the bot probably won't encounter any major problems with playing back the recorded file. If I needed the bot to interact with objects with a degree of accuracy in the millimeters, I could see a problem, but I haven't seen too many competitions with that level of fine-tuned design.
Okay, thoughts? Is this allowed? Impossible with the current memory limits? What if memory isn't an issue by the time competition rolls around?
Let's say you have a competition where your bot must navigate a fixed-dimension field (let's say 10x10 feet). Let's also add in the fact that there are obstacles and objects to interact with on the field. (Can you tell I'm trying to avoid using a 3-letter acronym here?)
Finally, let's add in the fact that the bot will always start from the same exact position.
Okay, here's the question:
(Assuming memory isn't an issue, because it may very well be in the REAL WORLD)
What's to keep me from setting up a test field, putting in a Play/Record block configured for 5 minutes (300 seconds) and then recording my manually moving the bot around the field, interacting with objects, performing tasks, and then returning home?
If everything is in a fixed location, all I've got to do is drive the bot with my hand into the proper position for a task, use Motor A if required and move it to perform a task, and then move it on to the next task.
I realize that there might be subtle differences in measurements, but if we're dealing with a table of less than 10 feet, the bot probably won't encounter any major problems with playing back the recorded file. If I needed the bot to interact with objects with a degree of accuracy in the millimeters, I could see a problem, but I haven't seen too many competitions with that level of fine-tuned design.
Okay, thoughts? Is this allowed? Impossible with the current memory limits? What if memory isn't an issue by the time competition rolls around?