-
Notifications
You must be signed in to change notification settings - Fork 0
/
BOPD1
198 lines (155 loc) · 9.49 KB
/
BOPD1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
San Diego Region
Period One - Advances In Robotics (pdcmsbotball5 19-0343)
Goals and Tasks for Botball 2019
Game Goals and Tasks
Review the Game Rules and Game Documents
Make copies of game review and other Botball-related documents create a team binder: 16 January 2019
Add tabs in binder to present an organized front and add loose notebook to write notes and record when we complete goals: 17 January 2019
Have each team member watch Youtube videos on the Botball YouTube channel (Botguy12): 17 January 2019
Brainstorm strategies
Call meeting with all team members to discuss Botball 2019 game review: 17 January 2019
Devise strategies for Botball 2019 game: 17 January 2019
Calculate how many points our strategy will score and prepare arguments to defend scoring at competitions in case of incorrect scoring: 22 January 2019
Build Practice board
Secure the PVC build to the game table with tape to have temporary stability until we can drill it to the table: 8 March 2019
Check PVC measurements before drilling the PVC build to the game table: 11 March 2019
Drill PVC build to table: 11 March 2019
Robot Building Goals and Tasks
Prototype the Create
Find Basis/Common goal of build for Create: 1 March 2019
Research documentations and robots of previous botball tournaments for inspiration and visual education for ways to achieve scoring goals in Botball 2019: 1 March 2019
Share ideas as a team and decide on a final design for the Create: 4 March 2019
Prototype the Demobot/LEGO Robot
Find Basis/ Common goal of build for Demobot/LEGO robot: 22 January 2019
Call a meeting to show others to discuss ideas for sensor mounts discovered at Workshop: 19 February 2019
Research documentations and robots of previous botball tournaments for inspiration and visual education for ways to achieve scoring goals in Botball 2019: 1 March 2019
Share ideas as a team and decide on a final design for the Demobot/LEGO Robot: 4 March 2019
Complete Construction of Create
Gather pieces to build Create: 6 March 2019
Construct base of Create: 7 March 2019
Add mechanisms built with the purpose of capturing game pieces: 6 March 2019
Test servos for weight limits: 7 March 2019
Add required light sensor: 7 March 2019
Complete Construction of Demobot/LEGO Robot
Take Demobot/LEGO Robot from Workshop and take off pieces unnecessary in the pursuit of scoring in the game: 18 March 2019
Build a stand for the wallaby that sits on the Demobot/LEGO Robot vertically (this allows more room for building other mechanisms): 18 March 2019
Gather other pieces to build Demobot/LEGO Robot: 6 March 2019
Add mechanisms built with the purpose of capturing game pieces: 7 March 2019
Test servos for weight limits: 10 March 2019
Add required light sensor: 10 March 2019
Programming Goals and Tasks
Dividing the Programmers
Call team meeting and discuss final strategies: 17 January 2019
Have builders and coders intervene and decide which team members will be responsible for programming which robot: 11 March 2019
Have both teams start coding: 11 March 2019
Create Programming Goals
Program Create to line follow on black line: 15 March 2019
Program Create to drive on black line and capture the food, medical supplies, and water to move them out of the way: 19 March 2019
Program Create to drive back to the Starting Box/Disaster Relief Zone: 22 March 2019
Demobot/LEGO Robot Programming Goals
Program Demobot/LEGO Robot to line follow on the black line: 15 March 2019
Program Demobot/LEGO Robot to stop in front of the firefighter pole: 18 March 2019
Program Demobot/LEGO Robot to get firefighters out of the firefighter pole: 21 March 2019
Program Demobot/LEGO Robot to move firefighters into one of medical centers: 25 March 2019
Documentation Goals and Tasks
First Period Documentation
Open a document on which team will type first period documentation: 22 February 2019
Share document among team members and allow edit access: 22 February 2019
As a team, decide on specific goals and tasks that are attainable within the time period we’ve been given before 2nd Period Documentation is due: 25 February 2019
Write 1st Period Documentation: 27 February 2019
Submit 1st Period Documentation: 27 February 2019
Second Period Documentation
Record clips of our team working to achieve the aforementioned goals: 22 March 2019
Record clips of our team completing the aforementioned goals by their deadlines: 22 March 2019
Edit together clips into a nice, clean video of our team and our robots: 27 March 2019
Submit the video: 27 March 2019
Complete GitHub portion of the documentation (our team members already have an account thanks to the pre-conferences last year at GCER): 26 March 2019
Submit GitHub code project: 27 March 2019
Third Period Documentation
Meet as a team to discuss how we’ve succeeded and failed at working together and at reaching our goals and discuss the progress we’ve made over the season and what we want to write about in the documentation: 7 April 2019
Open a document in which team will type third period documentation: 8 April 2019
Share document among team members and allow edit access: 8 April 2019
Complete 3rd Period Documentation: 17 April 2019
Submit 3rd Period Documentation: 17 April 2019
Schedule Conflicts
21 January 2019 - Martin Luther King Day/no school
25 January 2019 - Staff Planning Day/no school
7 February 2019 - Career Day/classes were cancelled
11 February 2019 - Lincoln’s Birthday/no school
18 February 2019 - President’s Day/no school
22 February 2019 - One team member absent (sick)
26 February 2019 - One team member absent (reason unknown)
26 February 2019 - Field Trip/ two members will be absent
Team Organization
Schedule of Meeting Times
WORKSHOP: 16-17 February 2019
REGIONALS: San Diego Regional 20 April 2019
(We met on the days as a complete team colored in bright yellow/orange, weekends are excluded from the chart).
On Monday, Tuesday, Thursday, and Friday for 53 minutes as a class in school. On Wednesdays, we have a shorter class and meet for only 46 minutes.
Key:
Yellow: The entire team was here and we met for a full class period.
Orange: The entire team was here but our time was limited due to our school’s schedule.
Green: One or more team member(s) were absent but the rest of the team met.
Grey: Future.
January 2019
Monday Tuesday Wednesday Thursday Friday
1
2
3
4
7
8
9
10
11
14
15
16
17
18
21
22
23
24
25
28
29
30
31
February 2019
Monday Tuesday Wednesday Thursday Friday
1
4
5
6
7
8
11
12
13
14
15
18
19
20
21
22
25
26
27
28 (unknown)
Division of Labor
We have 6 members of our team labeled as 1, 2, 3, 4, 5, and 6 whose number is labeled next to the group or category they work with or manage. The Create builders and programmers will work together and the Demobot/LEGO Robot builders and programmers will work together. The strategizers and managers will work with both groups and keep them focused. Together, we will work for different goals and intervene to share new ideas and create smarter building and coding ideas.
Create Build Team: Team Members; 3, 5, 6
Demobot/LEGO Robot Build Team: Team Members; 3, 5, 6
Create Programming Team: Team Members; 1, 2, 5
Demobot/LEGO Robot Programming Team: Team Members; 1, 2, 4, 5
Documentation Team: Team Members; 5, 6
Team Managers: Team Members; 4
Strategizers: Team Members; 1, 2, 3, 4, 5, 6
Conflict Resolution
Our team has agreed that if one or more team members disagree with one or more other team members, our team will handle the matter the following fashion or fashions:
Team member with disagreeing points of view will first meet face to face. The two or more disagreeing team members will begin a peaceful and respectful discussion, occasionally with another team member that represents a neutral point of view/judge. Then one of the disagreeing team member will discuss the issue from their point of view. The other disagreeing teammate will then present the issue from their point of view. Then they will present solutions to the issue and try to agree on one or form a compromise. If the disagreeing team members do not agree on a solution or compromise the neutral team/judge member will form a solution or compromise.
If the two or more disagreeing team members do not agree on a solution or compromise, and the neutral/judge team member cannot decide on one of the solutions or compromises or come up with one of their own, the remaining team members will respond in a democratic way. A team meeting will be called by the neutral team member/judge and they will present the issue. Both sides of of the argument will present their solutions. The remaining team members will act as a jury and choose on of the suggested solutions or come up with their own compromise.
If in the extremely rare occasions solution or compromise still hasn’t been reached, the issue will be brought to our elected officers. Then the officers will either choose one of the presented solutions or compromises, or come up with one of their own.
If the officers happen to be absent, extremely busy, taking care of a more serious matter, or not wanting to be disturbed, we will not present the issue to them. During this instance, we will then present the issue to our adult supervisor/team leader. Our adult supervisor/team leader will then choose one of the suggested solutions or compromises or come up with their own.