Author: Lutfiyah Nawaz M. & Astrid S.
Witness: Ms. Maria Osoria and Ms. Manisha Shah
Date: 10/26/20
Duration: 5:00 - 6:30
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
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
The Hardware team is working on our first course during their training week.
The Programming Team is working on expanding their knowledge on Open CV.
In Hardware, everyone receives the same three courses but are to complete them individually. The courses include: "Introduction to Assembly Design," "OnShape Assemblies," and "Manage In-Context Design."
The hope is that these courses will aid them when working on the robot in the future.
In Programming, because the team members grasped the principles, everything worked out smoothly.
In the potential future, we would like to incorporate everything we're learning and evaluate it with the jersey bot. We currently are coming up with ideas to improve and fix flaws in the program. We'd like to combine it with the road racer, too. In addition, we are learning how to incorporate a road runner into a teleOP.
Today the Hardware Team started their training period.
One of their first tasks is to complete courses on OnShape. The first course they are doing is called "Introduction to Assembly Design."
Since our team does not feel as if we are working efficiently enough, we decide to take a week to learn more about OnShape. Hopefully, the process becomes faster and more efficient when working on the CAD.
In "Introduction to Assembly Design," we watch videos and complete activities which teach us how to utilize all the features on OnShape.
We learn about all the different mating options that are available to make certain designs.
These mating options include: the revolute mate, which are meant to be used with parts that spin in relation to others, and fastening which simply attach one part to the other with no freedom of movement.
So far, we have only used the fastening mates, but with the new knowledge our team has gained on revolute and rotate mates, we plan to implement such mating in our wheels and axel for our intake mechanism. Doing so will allow us to visually see the movement of the intake ourselves, as well as show others.
The course also reviews how to use different assemblies to our advantage. So far, we are working on only one assembly, and it becomes difficult to coordinate between six people, especially when the zoom is unresponsive for some of the members. The course includes several videos on the benefits of using separate assemblies, including better coordination, and most importantly, being able to track/find mates faster.
When you have only one assembly, chances are you will have about 200 mates or more if you are building a robot. If you have separate assemblies for different parts of the robot, in the case one part has an incorrect mating, you can easily view only the mates for that specific mechanism in its own assembly.
This is a picture of one of the comprehension checks along the course. If we had not understood anything, it would become evident during this assessment. If our answers are incorrect, we would be asked to try again until we reach the correct answer. These assessments were especially helpful because they include pictures of the actual CAD, allowing us to visually correlate our CAD assembly to what is being reviewed in the courses.
During the course, we are asked to build certain assemblies and when those assemblies are complete, we will be asked for the mass of the mechanism we created. Since there is no actual way for the instructor of the courses to check your answers, a Self-Check proved whether or not your mechanism was built correctly.
The agenda for today is to focus more on Open Cv and understand how to effectively use it in our code.
By using Open Cv, we want to fix the few flaws detected in our program.
Each team member gathered resources, material, or any information on Open Cv to share with the team. We also ask each other questions if there were any questions.
Discussing parts we didn't understand as a group helps us understand the concepts better as a team.
We are looking over each part as a group, having all the members take turns reading the material found on Open Cv.
Our goal is to have each member understand Open Cv, and luckily the goal is achieved.
Shaurya is a great help when it came to covering the topics on Open Cv because whenever we have the slightest of complications Shaurya answers our questions calmly and in simple terms.
In the future, we would like to implement what we learn and test it with the jersey bot we have coming.
We would also like to integrate it into the road runner.
We recently are learning how to integrate road runner into teleOP.
Shaurya, a fellow teammate, fortunately discovers FTC Library (FTCLib) which includes programming information our team can use. This is going to be a great help going forward with programming code using OpenCV. Shaurya shares the resource with the whole team. FTCLib has information on topics such as kinematics, pathing, command base, geometry, drive bases, computer vision, and more, to help teams in FTC program better robots.
This is part of what we are discussing today. These lines of code correspond to manipulating the input. It converts the red, green, and blue matrix color space to YCrCb. Y is for luminance, Cr (chrome red) is for the amount of red, and Cb (chrome blue) is for the amount of blue. Then we draw the 2 rectangles with a predetermined position. The top will be where the 3rd ring should be and the bottom rectangle is where the first ring will be. Then the value of Cb is extracted from the predetermined area and compared.