2022:Strategy: Difference between revisions

From 1511Wookiee
Jump to navigationJump to search
(Created page with "<div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-out...")
 
Tag: visualeditor
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output">
= <span style="font-size:smaller">[http://www.penfieldrobotics.com/wiki/images/5/5f/2020_Robot_Priority_List.pdf 2020_Robot_Priority_List.pdf]</span> =
<div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output">
= Scouting app and system - instructions and log of things I've done so far: =


#Make a list of all the things that can be scouted
== Kickoff ==
#Make a list of all of the things we will actually be scouting and lay out all of the pages on the scouting app. See [https://docs.google.com/spreadsheets/d/1RK33Qgm6S2DAe43CL9OW6Y78wghZ3IiQotxW2qC8Q1U/edit?usp=sharing here.]
#Go over the pages on the scouting app at the strategy meeting.
#You should be using laptop 7 at this point, it has all of the correct software pre-installed. If not, for now you need [https://developer.android.com/studio/archive Android Studio version 3.3]
#Move the old scouting folder to the new scouting folder in SVN under FRC20XX\trunk\Scouting. (You need to move scoutmaster, ThunderScout, and thunderscout-common)
#Run the app in the new folder to make sure it still works. Android Studio and Java will probably beg you to update them. If you do, make sure to record what version they are currently on so that you can revert to it when it doesn’t work. Version 3.3 of Android Studio works.
#If you are using the emulator to run it, virtualization is turned off in the bios on the laptops, so you will need to use an ARM system image. There should be one already installed on laptop 7.
#Start working on the UI of the app. It is under app\res\layout. You can fiddle with the graphical editor if you want to, but I’d use XML. Make sure you name things well, you will be using these names later. Images that you can use are in app\res\drawabe
#Start working on the Java, probably start in with the tabfragments as a starting point.


&nbsp;
=== 1/08/22 ===


<span style="font-size:large">2020 Auto Mode List:</span>
Following the game reveal and full-team rules reading, the strategy team split off and began work on a full list of possible robot actions. Once finished assembling the list, strategy went over the list point-by-point giving it a rough priority ranking on a scale of 1-10 (1 being low, 10 being essential robot actions/capabilities). Strategy then began working through estimates of various match schedules (various score estimates for matches, like the base requirement for a unicorn match or the average week 1 competition) to get a feel for scoring, estimated cycle times, and further enhance our priorities. Using the priority list and match schedules, strategy began work on a mind map to establish and clarify priorities and goals.


#Leave the Initiation Line - Either Direction (Guaranteed 5 points)
=== 1/09/22 ===
#Score balls from robot centered in outer port & leave initiation line (either direction if we are shooting from initiation line) (5 points for leaving initiation line + 12 points for 3 power cells in outer port)
#Score balls from robot not centered & leave initiation line in either direction (5 points for leaving initiation line + 12 points for 3 power cells in outer port)


Stretch Goal:
Strategy finished the mind map and presented progress to the rest of the team. Using established priorities, strategy reintegrated with the full team to begin work on brainstorming and prototyping.


#Score Balls, Pick up additional balls from Trench and under Control Panel and wait for teleop with 5 balls
== Weeks 1 and 2 ==
#Score Balls, Pick up additional balls from Rendez Vous, then score trench balls
The strategy subteam split up among other design subteams to work on robot design.


= LED Wish List =
== Week 3 ==


*Five horizontal strips on the back flat plate on the robot that light up according to the amount of balls we've intaked. Have LEDs flash when we have 4 balls, all five strips light up when we have five.
=== 1/29/22 ===
*Five strips that wrap the helix with the same code as the five horizontal strips. Wrap 1/2 or 2/3 of the helix depending on price on Amazon.&nbsp;
A small group of a few strategy students met to work out what scouting data will be collected. A list of all scoutable information was created and from that we decided which data we thought would be most beneficial to record. From this we split the data between whether the data would be recorded via tablet scouting or super scouting.  
</div> </div> </div> </div> </div> </div> </div>
 
= Strategy Archives =
=== 1/30/22 ===
Our old scouting tablets were taken out to compare the old UI and see if there was any important data we missed. The list of tablet scouting data was updated and better sorted.
 
== Strategy Archives ==


*[[2020:Strategy]]  
*[[2020:Strategy]]  
*[[2019:Strategy]]  
*[[2019:Strategy]]  
*[[2018:Strategy]]  
*[[2018:Strategy]]  
*[[2017:Strategy]]  
*[[2017:Strategy]]
</div> </div> </div> </div> </div> </div>

Latest revision as of 15:07, 30 January 2022

Kickoff

1/08/22

Following the game reveal and full-team rules reading, the strategy team split off and began work on a full list of possible robot actions. Once finished assembling the list, strategy went over the list point-by-point giving it a rough priority ranking on a scale of 1-10 (1 being low, 10 being essential robot actions/capabilities). Strategy then began working through estimates of various match schedules (various score estimates for matches, like the base requirement for a unicorn match or the average week 1 competition) to get a feel for scoring, estimated cycle times, and further enhance our priorities. Using the priority list and match schedules, strategy began work on a mind map to establish and clarify priorities and goals.

1/09/22

Strategy finished the mind map and presented progress to the rest of the team. Using established priorities, strategy reintegrated with the full team to begin work on brainstorming and prototyping.

Weeks 1 and 2

The strategy subteam split up among other design subteams to work on robot design.

Week 3

1/29/22

A small group of a few strategy students met to work out what scouting data will be collected. A list of all scoutable information was created and from that we decided which data we thought would be most beneficial to record. From this we split the data between whether the data would be recorded via tablet scouting or super scouting.

1/30/22

Our old scouting tablets were taken out to compare the old UI and see if there was any important data we missed. The list of tablet scouting data was updated and better sorted.

Strategy Archives