-
Asked by jamesygamesy to Iulia, Katie, Mateusz, Ollie, Siobhan on 9 Mar 2017. This question was also asked by I_can't_think_of_one, SomebodyOnceToldMe.
-
anon answered on 9 Mar 2017:
We usually call it a bug, when robots don’t do what they are supposed to do. We then look through the commands we’ve given the robot to see where it all went wrong. Then we have to fix what went wrong and try again 🙂
It’s hard to get it to work perfectly on the first try, so in my experience, it’s totally expected for robots not to cooperate for some time, before all the details are figured out. In fact, you’d want to give your robot some strange commands to see, if it can cope. That’s (stress) testing – a vital part to ensure that robots don’t go wrong once you give them to people.
-
-
Iulia Motoc answered on 9 Mar 2017:
That happens all the time. You can’t get something right from the first try. When this happens, you have to go back in your code and check to see where did you go wrong.
-
Siobhan Duncan answered on 13 Mar 2017:
This is a really good questions.
This actually happens a lot. Engineers are just people, so we make mistakes. And this usually means that the first time we try and run our software on the robot things don’t work as you would like.
These are called bugs. This is because in the old days, bugs used to literally crawl into the computers and cause problems. But now they are mostly caused by people making mistakes 🙂
But this is ok, because a big part of being an engineers is finding these mistakes and correcting them and you do this until your robot works the way you would like it to 🙂
Comments