Embedded Files
Author: Abriti Chatterjee & Yuga Patel
Witness: Ms. Maria Osoria and Ms. Manisha Shah
Date: 10/21/20
Duration: 5:00 - 6:30
TABLE OF CONTENTS
Attendance
Ahmed Mahmud
Manyata Arora
Amanpreet Dhah
Hooryah Raja
Murtaza Raja
Martin Soliman
Martina Soliman
Syed Shah
Benjamin Fitzgerald
Caitlyn Mei Roxas
Arleen Dhah
Atharva Khandelwal
Abrahim Mahmud
Abriti Chatterjee
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
Anirudh Chaturvedula
Astrid Salazar
Ehtesham Suhail
Lutfiyah Mohammed
Prajwal Khanal
Ria Gray
Shaurya Singh
Sivaditya Padmanabhan
Tvisha Doshi
Vanisha Rajlakshmi
Ved Borade
Venya Goyal
Yuga Patel
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
Team Planning
Agenda
The main task for the Hardware today is to attach the angled intake mechanism to the chassis design.
This process takes multiple attempts and group discussions since we have to find the best possible method.
Additionally, we need to design a funnel system for the intake mechanism.
The goal for the programming team today is to organize our code by adding comments to it.
This is so that it's simpler for anyone visiting our website to decode the programs.
We are supposed to try to describe all the lines of code so that the programs are easier to comprehend.
Reflection
Today the hardware team works on the intake system.
We successfully position the low u-channels of the intake in the correct orientation with the chassis.
Next, our task is to figure out a way to attach the complete intake mechanism to the channels. We try multiple different attempts in order to see which worked best for the problem.
The funnel for the rings at the intake have been modified. Multiple attempted designs for the funnel include different types of brackets and mounts.
OnShape is running very slowly today which causes complications in our work. Specifically, rendering takes a great amount long time. When trying to make a funnel using channels and mounts, we realize that it would cause problems in the future. Therefore, we decide not to implement this idea into our design. Additionally, one of our team members is experiencing technical difficulties which leads to a lack of communication among the team.
We are able to add all the comments.
The team divides the work such that one person would add the comments to all the "A" autonomous programs, and another would do so for all the autonomous "B" programs and so on.
Our explanations in the comments are fine. Everyone checks over his or her own comments to make sure that they are.
We all needed to make sure that our comments are detailed enough for anyone to understand our code.
We are also able to add screenshots of our programs to our website for everyone to see and possibly learn something.
The organized programs look very nice and we are proud of ourselves.
Hardware
Agenda
The main task for the Hardware today is to attach the angled intake mechanism to the chassis design.
This process takes multiple attempts and group discussion since we have to find the best possible method.
Additionally, we need to design a funnel system for the intake mechanism.
This funnel will help guide the ring inside the robot and into the big and small wheel assemblies.
Reflection
Today the hardware team mainly works on the intake system.
We successfully position the low u-channels of the intake in the correct orientation with the chassis.
Next, our task is to figure out a way to attach the complete intake mechanism to the channels. We try multiple different attempts in order to see which works best for the problem.
Benjamin and Astrid work on the square beam idea, while Tvisha, Vanisha, and Yuga work on expanding the triangular mount idea.
In the end we discover that the square beams is the best method, since they are very strong and durable. Therefore, on each side of on the chassis, a single square beam will be attached to the angle mount placed on top of the channels.
The funnel for the rings at the intake has been modified. Multiple attempted designs for the funnel include different types of brackets and mounts.
One of the high points of today is finding a ring on OnShape. This ring has the exact same measurements as the real ring that will be used at competitions. This is helpful earlier in the process to estimate our measurements better but nonetheless finding it will help us in the future.
OnShape is running very slowly today which caused complications in our work. Specifically, rendering takes a great amount long time. When trying to make a funnel using channels and mounts, we realize that it would cause problems in the future. Therefore, we decide not to implement this idea into our design. Additionally, one of our team members is experiencing technical difficulties which led to lack of communication among the team.
This is one of the ways that we try to attach mounts and channels in order to make a funnel. However, we find out that this will later cause complications when we add more parts to the design. Therefore, we decide to abandon the idea.
This is the intake mechanism from the side angle. On the bottom of this picture the ring is placed right below the intake mechanism. This allows us to see the ring in relation to the intake as a whole. This image also shows the different components that we plan on using later in our intake mechanism.
This shows the intake mechanism connecting to the channels on both sides. The intake attaches to the angled bracket by using the square beams.
Programming
Agenda
The main task for the progarmming team today is to organize our code by adding comments to it, as well as formatting it.
This is so that our code looks a bit more professional and pleasing to the eye.
This can also help us explain it better in the future.
We would have to describe all the lines of code so that anyone reading it can understand it.
This is essential because our code would be made public soon.
After we are done organizing the code, we are supposed to take screenshots of some parts of it and put it onto our website.
Reflection
We are able to add all the comments describing the different lines of several of our prgrams.
Abrahim works on all the Start 1 autonomous programs.
Ria works on all the Start 2 autonomous programs.
Abriti works on all the Start 3 autonomous programs.
Shaurya works on the rough draft of the TeleOp program that we have as of now.
Our explanations in the comments are descriptive and technical.
Everyone checks their own comments, as well as others' comments to make sure that everything is as good as it could be.
The comments make the program more understandable.
After we add the comments, Ria formats all of the programs to make sure everything looks professional in addition to being detailed.
At the end, Abrahim and Abriti make sure all the programs look similar in style.
Then Shaurya takes screenshots of a part of one of our autonomous programs and a completed portion of one of our TeleOp programs to put it on the website.
Seeing our code on the team website is a proud moment for all of us.
We want to continue adding detailed comments on to the future programs that we create.
We notice that the comments made the prgrams way more easy to follow through and understand.
We would also like to format our programs in a similar manner in the future.
We observe that the formatting makes the programs look very pleasing to the eye.
This is an example of one of the comments we write. This one explains one line of code seen in every program. The comment describes how we got the angle mentioned in the line of code and why the angle is important.
This is another example of a comment we write. This line is also seen in all of our programs. This comment simply says what this line of code does, which is that it saves the coordinates in another program, so that the robot can refer to them while running this program.
Google Sites
Report abuse