Follow designs to build a system.
Create a program to meet requirements.
Hello!
To reflect on Friday, I came in with Adam M later the day and cracked on with building our robot. We encountered various issues with the build, became frustrated and decided to take everything apart -- including our beloved base of the robot. We wanted to stick to the original design and therefore we decided to spend longer building trial and error. At the end of the day, Adam left whereas I stayed an hour later and had John nice enough to help me! This was great and I watched how he built the robot, this helped me today and was a strength.
As starter, John did a warm up to let us remember the different factors for readability and quality. This was relatively easy as I understand what makes a code simple to understand. However, programming the robot is obviously the challenge and the difficult part.
Back to today, once again John wasted no time and allowed us to get on with work. I firstly built the robot with Adam M; all was left was to tidy the wires (cable management), add the sensors and make sure it was robust in terms of sturdiness. An hour or so later, this was a success. A strength was being able to build the robot as a pair. A weakness was struggling and stressing.
Next, John showed us examples of how to lay out a test table when we test our robots with our own codes. One in particular caught my attention and therefore I based my layout on that. There, I created a table for the different objectives I am testing, a tab for objectives as well as the marks/tasks and a version history. I did all of this on Google Excel Spreadsheets for a change.
I then began to code and dedicated my entire day on it. By the end, I have managed to complete 4 out of 7 objectives with three remaining - these ones are either uncompleted due to not having e.g. an obstacle and I have planned to work on this by coming in tomorrow. The biggest issues I have faced today would be on the programming side - such as forgetting a line or accidentally missing parenthesis... common issues.
As for reflection, Adam has been my inspiration because he has managed to get his robot and testing to a good standard -- I had to do more testing due to having more errors but nonetheless I have managed to catch up to him and get the robot working. Right now, it can follow a straight line, listen to a clap and spin 540 then follow the line, wait four seconds then continue and then complete tasks one after another.
No comments:
Post a Comment