inspirationrobotics / inspiration_ftc Goto Github PK

We need to make sure that we have an organized SCRUM system and inform all the members how to use it.

While the board will be maintained by Pahel + Shruti, all members will actively use it!

Plan this.

• design
• review

Make sure everyone has a hotel room booked:

• @amavalankar
• @rveerepalli
• @NoahTang
• @mabeltree and @kolinbilly
• @pahels
• @shrutinatala
• @RainaShapur
• @Dat-Bois
• Shreyas

We need to make the foundation mover more reliable

@kolinbilly What are the individual tasks for completing this?

• insert photos
• [email protected] please provide input why we took this screenshot with coach Mike
• [email protected] need parameter screenshot to shwo the growth of the team in CAD capabilities for drivetrian
• [email protected] need calcualtions for speed calculations, comaprring the linakge speed verse the spools attached ontot he servos
• [email protected] need to insert sensor holder images for documentation
• [email protected] need pictures for the sensor holders
• [email protected] please place your lessons learned in attempting to reassemble the auto arm
• [email protected] please provide a description and lessons learned for cutting the ocrner off auto arm plate to allow for interface witht eh phone holder
• [email protected] need to add in renders for final robto here

• plan
• review

Everyone should give feedback on the presentation and determine what our goal for the presentation is for the Worlds competition (what point are we trying to put across).

• Team members give feedback on the presentation (presenting issues and literal presentation)
• Determine goal for the next presentation; what award are we aiming for?

• @Dat-Bois need to update outreach hours document: https://tinyurl.com/tue87v7

• @Dat-Bois add documentation about turret design

• @ colin add documentation about drivetrian design

• @ noah add documentation abotu capstoen design

• @ mabel add photos about MegiLion Outreach: https://tinyurl.com/wte5dfz

• fix/fill in the notebook pages that coach Teresa did.
  -[ ] make outreach minute for vist to ForeCast 3d

This is just an example. You can do things like mention people like @amavalankar

• design
• build
• install

Is this a duplicate of #7

Test (and fix, if needed) park. Make sure to test all possible scenarios. Collect data such as initial and final position, runtime, etc.

Milestones will organize our repository and help get a schedule for tasks

• Work with @aktang to set milestones (week to specify when task should be complete)

• Also make labels (mechanical, P1, P2, P3, etc.) Some may already exist, so just update them.

• Click here to add milestones

This is to organize the batteries and chargers better. It will be made of Plexiglas or poly carbonate.

• design
• build

Test (and fix, if needed) gyroTurn.

Tape Measure

• Design
• Curation of Components
• Assemble
• Test

Test (and fix, if needed) multipleStones. Make sure to test all possible scenarios. Collect data such as distance and runtime.

Test how vision works in different lighting conditions.

• update script
• film different parts
• send to eesh to edit
• review

SUBMISSION DEADLINE 3/23/2020

better organized way to scout

@rveerepalli Please add a subtask with description and due date and make sure you assign someone to the issue.

• DATE in format 3/10 Subtask description

Test (and fix, if needed) gyro drive. Collect data such as heading and distance driven, as well as initial and final position.

Test (and fix, if needed) moveFoundation. Make sure to test all possible scenarios. Collect data such as runtime, initial and final position, angle turned, etc.

• Finish writeups

• Add pictures

• get documentation for official enrollment to the competition

• get documentation for tax exemption

• design
• collect materials
• assemble
• test
• integrate

• Read through it here

• Take the GM 0 Quiz

Test (and fix, if needed) encoder drive. Collect data such as distance driven.

p3 to ensure the drivers cna make more mistakes (more forgiving design)

Need milestone and subtasks

• Subtask 1
• Subtask 2

-[ ] Consult team members (mechanical specifically) to determine placement of materials
-[ ] Create Bill of Materials
-[ ] Design a display (CAD or Google Drawing)

to make the wheels strafe better

• []

Test (and fix, if needed) MoveToSkystone. Make sure to test all possible scenarios. Collect data such as distance strafed, horizontal divergence from target, vertical divergence from target, etc.

Dependencies:

• Fix encoder strafing first -- https://github.com/orgs/InspirationRobotics/projects/1#card-34401013

• 3/10: Research
• 3/12: design
• 3/14: assemble
• 3/14: test

Needs to coordinate with lift and grabber parts to integrate the piece correctly

• fix 3-d printers
• think of method to replace parts

• plan
• test
• design

Currently, the driver station always disconnects the phones- we need a new one.

• coordinate with programmers
• create document
• review document

We need order pins at 2-3 weeks in advance.

• Find a place to order them
• Order them

Shruti proposed the idea of us hosting a conference at Houston. Since we really specialize in having a far-reaching, impactful local and global outreach program, we think we could share with other teams how to do the same!

It would look very good for judging both at Houston and the year to follow!

• Aditya

• Get Isabelle's GitHub Username
• Set up GitHub if she doesn't have it

• Hardware

• Software

• design
• assemble
• integrate

• receive parts
• assemble
• test

• add outreach document
• add in photos
• update the outreach hours spreadsheet

• plan out the pit design first to see if we have space
• finish collecting the photos from Jr. FLL - FRC

-[ ]Consult team members (mechanical specifically) to determine placement of materials
-[ ]Create Bill of Materials
-[ ]Design a display (CAD or Google Drawing)

• Consult team members (mechanical specifically) to determine placement of materials
• Create Bill of Materials
• Design a display (CAD or Google Drawing)

Test (and fix, if needed) MoveToFoundation. Make sure to test all possible scenarios. Collect data such as distance moved forward, and distance relative to the foundation, runtime, and so on.