Drive Principles: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Will.Barber (talk | contribs) m (Change whitespace of subheading to match Mike's) |
||
| Line 1: | Line 1: | ||
This is intended to be a brief outline of some of the drive team principles that we should keep in mind when practicing and driving at competition. | This is intended to be a brief outline of some of the drive team principles that we should keep in mind when practicing and driving at competition. | ||
== General == | ==General== | ||
* You are the boss: If you want a different control setup or a mechanism to work a different way, tell this to the appropriate technical sub team! It's their job to make the robot adapt to you, not the other way around. | * You are the boss: If you want a different control setup or a mechanism to work a different way, tell this to the appropriate technical sub team! It's their job to make the robot adapt to you, not the other way around. | ||
* Work as a team: Make sure that you practice as a full drive team. Communicate and provide suggestions to each other. You're all on the same team, and you need to function like a well-oiled machine so that the robot can do the same. | * Work as a team: Make sure that you practice as a full drive team. Communicate and provide suggestions to each other. You're all on the same team, and you need to function like a well-oiled machine so that the robot can do the same. | ||
== Practicing == | ==Practicing== | ||
* See something, say something: If you see unexpected behavior from the robot (like the code crashing or a mechanism failing to work properly), tell the appropriate sub team! Even if it's uncommon for the failure to occur or if you found a workaround for it, it's still important to inform the technical sub team about it. If the sub team is not aware of the issue, we will never learn our design mistake and fix it. It's vital to get these problems fixed before competition so that they do not occur during a match, crippling our gameplay. | * See something, say something: If you see unexpected behavior from the robot (like the code crashing or a mechanism failing to work properly), tell the appropriate sub team! Even if it's uncommon for the failure to occur or if you found a workaround for it, it's still important to inform the technical sub team about it. If the sub team is not aware of the issue, we will never learn our design mistake and fix it. It's vital to get these problems fixed before competition so that they do not occur during a match, crippling our gameplay. | ||
* Practice how you play: during a match, you'll experience defense from other robots, obscured visibility, robot failures, and more. Prepare for all of these during your practice. | * Practice how you play: during a match, you'll experience defense from other robots, obscured visibility, robot failures, and more. Prepare for all of these during your practice. | ||
* Practice what's difficult: Practice what you struggle with, not what you're good at. That's how you'll improve the most, and what will give you the best chance of success at competition. | * Practice what's difficult: Practice what you struggle with, not what you're good at. That's how you'll improve the most, and what will give you the best chance of success at competition. | ||
== Competition == | ==Competition== | ||
* Keep to yourself: Do NOT interfere with your alliance partners! Stay out of their way whenever possible. Being an annoying and obstructive alliance partner is an easy way to get on a "Do Not Pick" list. | * Keep to yourself: Do NOT interfere with your alliance partners! Stay out of their way whenever possible. Being an annoying and obstructive alliance partner is an easy way to get on a "Do Not Pick" list. | ||
* Work as an alliance: Make sure that you and your alliance partners have a strategy and have worked out a way to play to the best of all your abilities. This should help with "Keep to yourself" as well: work out pathing that is efficient and unobstructive. | * Work as an alliance: Make sure that you and your alliance partners have a strategy and have worked out a way to play to the best of all your abilities. This should help with "Keep to yourself" as well: work out pathing that is efficient and unobstructive. | ||
* Don't give up: Keep fighting hard until the end. A strong showing can catch the eyes of potential alliance partners, even if you have a bad match. If the robot breaks, go on defense. Don't E-Stop unless doing so is necessary to maintain GP or follow the rules of the game--in general, the FTA will handle E-Stop if it's needed. | * Don't give up: Keep fighting hard until the end. A strong showing can catch the eyes of potential alliance partners, even if you have a bad match. If the robot breaks, go on defense. Don't E-Stop unless doing so is necessary to maintain GP or follow the rules of the game--in general, the FTA will handle E-Stop if it's needed. | ||
Revision as of 20:03, 16 April 2024
This is intended to be a brief outline of some of the drive team principles that we should keep in mind when practicing and driving at competition.
General
- You are the boss: If you want a different control setup or a mechanism to work a different way, tell this to the appropriate technical sub team! It's their job to make the robot adapt to you, not the other way around.
- Work as a team: Make sure that you practice as a full drive team. Communicate and provide suggestions to each other. You're all on the same team, and you need to function like a well-oiled machine so that the robot can do the same.
Practicing
- See something, say something: If you see unexpected behavior from the robot (like the code crashing or a mechanism failing to work properly), tell the appropriate sub team! Even if it's uncommon for the failure to occur or if you found a workaround for it, it's still important to inform the technical sub team about it. If the sub team is not aware of the issue, we will never learn our design mistake and fix it. It's vital to get these problems fixed before competition so that they do not occur during a match, crippling our gameplay.
- Practice how you play: during a match, you'll experience defense from other robots, obscured visibility, robot failures, and more. Prepare for all of these during your practice.
- Practice what's difficult: Practice what you struggle with, not what you're good at. That's how you'll improve the most, and what will give you the best chance of success at competition.
Competition
- Keep to yourself: Do NOT interfere with your alliance partners! Stay out of their way whenever possible. Being an annoying and obstructive alliance partner is an easy way to get on a "Do Not Pick" list.
- Work as an alliance: Make sure that you and your alliance partners have a strategy and have worked out a way to play to the best of all your abilities. This should help with "Keep to yourself" as well: work out pathing that is efficient and unobstructive.
- Don't give up: Keep fighting hard until the end. A strong showing can catch the eyes of potential alliance partners, even if you have a bad match. If the robot breaks, go on defense. Don't E-Stop unless doing so is necessary to maintain GP or follow the rules of the game--in general, the FTA will handle E-Stop if it's needed.