Final Mission Journal Entry #4
Project Details
Date:
Club:
Team:
Team Members:
Mission Team Roles:
Attempt #:
Goal:
Which part of the mission:
What steps will we take:
What will each member do:
What were the results:
Assess and analyze mistakes:
What did we learn:
What are our next steps:
th
January 26 , 2017
Gallimore Elementary Robotics Club
Fire Breathing Rubber Duckies
Jacob Rider, Noah Short, Keshav Nair, Jack Elwell
Keshav and Jack are the programmers. Noah and Jacob are the platform
builders. Everyone helps with videotaping, map control, and other
related activities.
First attempt at developing the program.
Defined Goal
Develop the logic to move Dash to sense Dot, at one position at a time
and then we will combine them in the end. This will not include ping-
pong ball delivery method. Initially, we will use a placeholder for
delivery method, which will eventually be replaced by the actual code.
In this part of the mission, we are trying to get Dash to its precise
location to deliver the balls. We will try to sense Dot and if not
detected; the ball dropping sequence will be initiated.
Plan
We will take the following steps:
1. Write down the steps to approach and detect Dot.
2. Draw a flow chart to visualize logic.
3. Do a walkthrough of the chart to make sure no steps were missed.
4. Develop the program.
5. Test the program to make any adjustments.
Keshav Nair did the flow chart and the walkthrough. Jack did the initial
step layout and programming.
Results
With minor adjustments to the distance travelled, the program mostly
worked in first few tries. We still need to integrate this with the code for
the ball drop sequence Jacob and Noah are working on.
We did not have any mistakes other than adjusting the initial distance
set to travel on each move, which was expected.
Conclusion
One of the biggest advantages was that, by creating the flow chart we
were able to identify most of the logical issues with the design upfront.
At first, we were going to sense Dot starting from the center cup, but
that made the flow complicated. We changed the design to always start
sensing Dot from the left cup first, which made the flow much simpler.
Once we transferred our design to code, all we had to do was fine-tune
the distances.
We see repeating patterns in the code diagram so our next step is to
optimize the code so that it works with less code. The final step is to add
the ball dropping sequence.