# data[].attributes.headline
How did you and your group decide on how to approach creating programs?

# data[].attributes.subject
How did you and your group decide on how to approach creating programs?

# data[].attributes.body
We first tried to map out how far the robot could go in one turn, and then just repeated that until we got to the shape. (Nicole, Hayley, Morola, and Angeline)

# data[].attributes.headline
What was most complicated about this assignment for you and your group?

# data[].attributes.subject
What was most complicated about this assignment for you and your group?

# data[].attributes.body
The most complicated thing was when our robot didn't have a wire attached to the port we put on the program, so we were confused. Another thing was when the robot was dead. (Nicole, Hayley, Morola, and Angeline)

# data[].attributes.body
how we decided to approach it was to immediately start coding the robot and make to changes as needed.

# data[].attributes.body
This is our final video for straight line speed and return.

# data[].attributes.body
How we approached making the programs was Brynlee made most of the programs, Ben timed it, and Briah positioned the robot and videoed it. We did switch jobs around sometimes, but those were the main jobs.

# data[].attributes.body
On our first attempt, we went towards the obstacle, turned 4 times, and came back (it took 10 seconds). On our second attempt, we used a little bit of an angle going forward and backward so that we could reduce the amount of turns (it took 10.5 seconds). On our last attempt, we went straight, had three big turns, and went back at an angle (it took 9 seconds).

# data[].attributes.body
On our first attempt, we went forward, turned around the first obstacle (strawberry), came halfway back, turned around the second obstacle (blueberry), and came back (it took 11 seconds). On our second attempt, we turned 90 degrees around the blueberry, went forward at an angle toward the strawberry, turned around the strawberry, and came back at an angle (like a figure eight). It took 10.5 seconds. The third attempt was the same as the last.

# data[].attributes.body
On our first run, we tried to turn the robot around and then push our object (the strawberry, 5 secs). Then, on our second run, we added arms to the bot and changed the code to go forward, grab the strawberry then go backwards.

# data[].attributes.body
On our first attempt, we went forward, and then backward (it took 9 seconds). On our second attempt, we sped up the program when going forward (it took 7 seconds). On our last attempt, we went forward (with speed), turned 1 rotation, and came back with speed (it took 6 seconds).

# data[].attributes.body
We explored the block choices until we found the ones that we thought would be the most effective. At the beginning, we would spend a lot of time making a program and not testing it, but later on we discovered that we should test it as often as possible even though you know that parts will work/will not work so you know what you need to fix.

# data[].attributes.body
We think that the most complicated thing for our group is thinking of ideas to make the program run more efficiently. If we come up with a way to make the program as efficient as possible at the start, it is challenging to create more ideas that will make it run more smoothly/effectively.

# data[].attributes.body
How did you and your group decide on how to approach creating programs?
We decided to start with the easier block codes so we could learn what they do and then try the harder ones.

# data[].attributes.body
1. Which mission task was most complicated? Explain.

We found the multiple obstacle navigation to be the hardest, we had to create a complex code to navigate around.

1. Which mission task was easiest?

The Straight Line Speed & Return was the easiest.

1. What are some program changes you and your group made to decrease the amount of time it took to accomplish any of the mission obstacles or tasks?

We increased the motor speed, and changed the code to make the robot turn corners sharper.

1. What adjustments/alterations did you have to make to the program?

We had to change the code multiple times and redirect a few things.

1. How did you decide on the start position? (where to start the robot)

We didn't really decide, we just put a general starting area.

# data[].attributes.body
What was most complicated about this assignment for you and your group?

1. Which mission task was most complicated? Explain.

The most complicated assignment was the multiple obstacle navigation, because it required some slight movements and lots of code

1. Which mission task was easiest?

The straight line speed and return, because you only needed to make it go forward and back

# data[].attributes.body
Our approach to creating programs was to first simply do it one code block at a time and then make sure that everything works. Then do it several times to make sure it works.

# data[].attributes.headline
Alex and Ashlyn single obstacle replacement

# data[].attributes.subject
Alex and Ashlyn single obstacle replacement

# data[].attributes.body
It takes about 12 seconds to finish

# data[].attributes.headline
Ashlyn & Alex straight line speed and return

# data[].attributes.subject
Ashlyn & Alex straight line speed and return

# data[].attributes.body
It takes about 6.52 seconds to run

# data[].attributes.headline
Alex & Ashlyn single obstacle navigation

# data[].attributes.subject
Alex & Ashlyn single obstacle navigation

# data[].attributes.body
Takes about 9-13 seconds to run

# data[].attributes.headline
Single Obstacle Navigation Diego & Trent

# data[].attributes.subject
Single Obstacle Navigation Diego & Trent

# data[].attributes.headline
Trent and Diego's single obstacle retrieval 

# data[].attributes.subject
Trent and Diego's single obstacle retrieval 

# data[].attributes.body
Me and my group simply took our time and used one code at a time. If something went wrong we would be able to diagnose the problem.

# data[].attributes.body
We approached problems by thinking what happened and how we had to fix it, for example, we had the car turn too much and go too far, so we changed the numbers to fix it.

# data[].attributes.body
The most complicated about this assignment was that you had to get the angles right and sometimes it was inconsistent for the amount it turned.

# data[].attributes.body
First we would check which motors were the movement motors, and set the movement motors on the program. Then, we would build on to the program, trying to complete little parts of the mission. Finally, we tweak the program until it works.

# data[].attributes.body
The most complicated thing was probably figuring out what was wrong with programs.

# data[].attributes.body
Me and my group first approached making our programs by deciding where we need to go and then what we need to do.

# data[].attributes.body
we created our programs by testing out which code would work and do trial and error

# data[].attributes.body
I think the hardest thing about this assignment was getting the same robot and mat everytime because if we didn't we had to restart our code.

# data[].attributes.body
We all would alternate who did what program so each person would have an opportunity to.

# data[].attributes.body
We had the most trouble on multiple obstacle navigation because we had to restart twice.

# data[].attributes.body
The hardest part was trying to figure out how to navigate multiple obstacles

# data[].attributes.body
The most complicated thing about this assignment was getting the angle right.

# data[].attributes.body
This is our final one for the single obstacle retrieval. It doesn't work great, but it's a start.

# data[].attributes.body
My group (Aaron, Curtis, Liam, and I) tried to make the most efficient program possible that used the least amount of lines.

# data[].attributes.headline
We thought it through like a sentence. We were trying to read the code and understand what we were having to do. - LINA REESE MAGGIE

# data[].attributes.subject
We thought it through like a sentence. We were trying to read the code and understand what we were having to do. - LINA REESE MAGGIE

# data[].attributes.body
My group (Aaron, Curtis, Liam, and I) had to make sure the code was as efficient as possible and eliminate unnecessary code which took a lot of time and effort.

# data[].attributes.headline
I think the most complicated part of this assignment was not seeing the code work and that was super disappointing. - LINA REESE MAGGIE

# data[].attributes.subject
I think the most complicated part of this assignment was not seeing the code work and that was super disappointing. - LINA REESE MAGGIE

# data[].attributes.body
To decide what to do for the programs we started off with basic movements and pieced it together part by part. Each time we added something new we made sure to play it before making it final.

# data[].attributes.headline
How did you and your group decide on how to approach creating programs?

# data[].attributes.subject
How did you and your group decide on how to approach creating programs?

# data[].attributes.body
We just figured out what might work, and then edited it until it worked.

# data[].attributes.headline
What was most complicated about this assignment for you and your group?

# data[].attributes.subject
What was most complicated about this assignment for you and your group?

# data[].attributes.body
Starting to try the retrieval task with a armless robot.

# data[].attributes.body
The hardest part of this assignment is when me and Brandon have to do the Single optical retrieval.

# data[].attributes.body
We decided to make part of a program, test if it works, then add on to and test it again, and repeat that until we can complete the task.

# data[].attributes.headline
What was most complicated about this assignment for your group?

# data[].attributes.subject
What was most complicated about this assignment for your group?

# data[].attributes.body
I believe that the most complicated part of the Robotics programming was getting the distance right. We measured in seconds, and we had to adjust multiple times in order to get it perfect. It was difficult to scale out the distance, since you can't really count seconds as distance.

# data[].attributes.body
The most complicated thing about this was how to align the robot so it would go the right was we had to restart many times because it went the wrong way.

# data[].attributes.headline
We approached by testing and seeing what the robot will do.

# data[].attributes.subject
We approached by testing and seeing what the robot will do.

# data[].attributes.body
the most difficult part of the project so far is working on the code together and using the turns

# data[].attributes.body
We decided to make a starter program and adjust it to its best.

# data[].attributes.headline
The hardest part about this was when the code didn’t work and we had too keep retrying.

# data[].attributes.subject
The hardest part about this was when the code didn’t work and we had too keep retrying.

# data[].attributes.body
We decided to make a starter program and adjusted it to its best.

# data[].attributes.body
we approached it by having one person time it having one person record one person putting everything back in place and two people coding and it has worked so far

# data[].attributes.headline
Team Artemis-Alyssa, Saniah, Harseerat, Samantha, Kailey

# data[].attributes.subject
Team Artemis-Alyssa, Saniah, Harseerat, Samantha, Kailey

# data[].attributes.body
We think that the most complicated thing we had to overcome was listening to each other’s ideas. It was hard to communicate thoroughly, and be open to all ideas.

# data[].attributes.headline
Maddie, Adelaide, Daniyal, Isabella, Gracie

# data[].attributes.subject
Maddie, Adelaide, Daniyal, Isabella, Gracie

# data[].attributes.body
The most difficult part of this assignment was that completing one mission took quite a long time and it was really easy to get off task.

# data[].attributes.body
I think the most complicating thing was trying to get the robot perfectly lined up.

# data[].attributes.body
We split the program into separate parts and kept trying until it worked

# data[].attributes.headline
Team Artemis- Alyssa, Samantha, Saniah, Kailey, Harseeraat

# data[].attributes.subject
Team Artemis- Alyssa, Samantha, Saniah, Kailey, Harseeraat

# data[].attributes.body
We split up the work, and when we had trouble finding a part, we all looked for it.

# data[].attributes.body
What was most complicated was when we had to line the motor up in the right way.

# data[].attributes.body
I decided to do it from memory because I remember some of the coding from robotics.

# data[].attributes.body
Some of our team members were not cooperating correctly and the programming was kind of difficult

# data[].attributes.body
We thought about what we needed done and looked for a block that could accomplish our tasks.

# data[].attributes.headline
How did you and your group decide on how to approach creating programs?

# data[].attributes.subject
How did you and your group decide on how to approach creating programs?

# data[].attributes.body
We approached it step by step and we would list the movements we would have to do first, next, and last. By: mohammad, Tyler, and Lane.

# data[].attributes.body
We tested different speeds to see what worked

# data[].attributes.body
The most complicated was single obstacle retrieval because we had to make an attachment.