http://trcnet.asuscomm.com/mediawiki/api.php?action=feedcontributions&feedformat=atom&user=Will.Barber 2026-05-15T22:45:43Z User contributions MediaWiki 1.39.2 http://trcnet.asuscomm.com/mediawiki/index.php?title=Drive_Principles&diff=389 2024-04-28T03:49:45Z

<p>Will.Barber: Make more concise</p> <hr /> <div>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.<br /> <br /> == General ==<br /> * '''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.<br /> * '''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.<br /> * '''Avoid protected zones:''' This is important as a driver, getting fouls from protected zones is one of the easiest ways to get on a '''DO NOT PICK''' list. There are exceptions, and if there are no opposing robots nearby and it will benefit your alliance then maybe go for it, but this should be done sparingly.<br /> * '''Avoid spinning too much:''' While spinning is cool and a useful tool for avoiding defenders, it slows you down. Don't spin if you don't need to.<br /> * '''Avoid breaking the robot:''' Try not to break things. Given the nature of the sport it will sometimes happen on the field, but try to avoid excessive damage. The easiest way to do this is to use '''Turtle Mode.''' In many of our robots that extend outside of the frame perimeter, this mode is used to retract everything inside to avoid damage while traveling at high speed or cross-field. Note that while on the practice field it is okay to overcompensate to avoid damage, while playing make sure that you're overly cautious to the detriment of your cycle times.<br /> <br /> == Practicing ==<br /> * '''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.<br /> * '''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.<br /> * '''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.<br /> * '''Practice on every Alliance Driver Station:''' You should know how to score in all possible goals from every driver station, and practice doing so before competition. Not doing so will be detrimental to your performance because you don't get to choose driver stations until playoffs.<br /> * '''Prepare for the worst:''' You should be ready to fall back to the basics if part of your robot fails, whether that be your auto score software, a critical mechanism, pneumatic pressure, or anything else. You should know how to score manually and how to perform effective defense.<br /> * '''Practice the things you need to improve:''' Don't just keep practicing full matches or cycles. If you recognize a portion of a cycle you need practicing on, like intaking, traversing, or scoring, you should focus your practice on that section. Making effective use of your practice time will lead to the largest improvements in your driving.<br /> * '''Practice multiple paths:''' When practicing by yourself, it may be easy to just use the easiest path or scoring location. In real matches, you don't get that luxury. You're playing with 5 other robots using the same space, so try to vary your pathing when running cycles during practice.<br /> * '''Experiment:''' When practicing, your current strategy may not be the best for cycles. Make sure to try different ones and measure the results. Another great way to look for strategies is to go onto YouTube or Chief Delphi and look for analysis or strategy postings.<br /> <br /> == Competition ==<br /> * '''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 &quot;Do Not Pick&quot; list. Be careful when defending that you're only obstructing the opposing alliance!<br /> * '''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 &quot;Keep to yourself&quot; as well: work out pathing that is efficient and unobstructive.<br /> * '''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.<br /> <br /> == Playing With Others ==<br /> * '''Set Your Strategy:''' Someone on your drive/strategy team should be talking to your alliance partners at least 10 minutes before your match. Cover Auto strategies and make sure you don't interfere. Go over Teleop pathing and define everyone's roles. Make sure to also cover Endgame: where they should be for what tasks, and when they should be there. Good strategy can be the difference between a clear victory and a shattering defeat.<br /> <br /> == Anti-defense ==<br /> * '''Spin:''' When going against an opponent who’s defending against you, the main tool at your disposal spinning. Spin in the direction such that you are essentially trying to “spin around your opponent.” This reduces robot-to-robot contact and allows you to maneuver around them. Practice this before competition.<br /> * '''Use Protected Zones:''' Use the protected zones by trying to score and stay in them. However, make sure not to sacrifice cycle time for safety: still try to score outside of them if you're not at risk of defense from an opposing robot.<br /> <br /> == Defense ==<br /> * '''Identify Choke Points:''' Places where you know the robots will tend to funnel towards are your targets. These should be identified with the strategy head of your alliances before competitions.<br /> * '''Get Between Them:''' Stay between them and their goal, trying to copy their movements.<br /> * '''Spin V2:''' Anti-anti-defense is where you spin to counter their spinning: you spin in the opposite direction (like meshing gears) to counteract their spin. Practice this before competition.<br /> * '''Avoid Protected Zones:''' Arguably the most important part (and the part where so many teams mess up) is to make sure not to touch or enter zones that are protected. If you do, you '''WILL''' receive the respective foul.<br /> <br /> == Other ==<br /> * '''Visibility:''' When choosing which side of your alliance driver station, '''make sure that you have visibility of your targets'''. Priority is usually given to the driver, but it depends on who controls what and where.<br /> <br /> == Quotes ==<br /> * '''StormBots:''' ''The strategic truth is that when given a choice, drivers do not e-stop their bots. With an e-stop, you forfeit any chance to regain control, even at a diminished level. You also set your bot up for significant foul points should you get nudged into foul zones. If there are any actual safety concerns, the FTAs handle them. Drive teams are focusing on strategic concerns, and that’s “do literally anything but die on the field”''.<br /> '''[Titan]''' We agree, but with the exception that we remain GP and that the rules allow it.<br /> * '''Practice like you’ve never won. Perform like you’ve never lost:''' When practicing, nothing should be left to chance. If you think defensive robots will be present, practice anti-defense. If there are anticipated problems with the robot, make sure you know how to work around them. But on the field, be confident: the only thing you’re doing on the field is running cycles. Don’t worry about what the crowds doing, etc. Just focus and be confident in your abilities.</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Drive_Principles&diff=388 2024-04-28T03:48:36Z

<p>Will.Barber: Remove redundant entry</p> <hr /> <div>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.<br /> <br /> == General ==<br /> * '''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.<br /> * '''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.<br /> * '''Avoid protected zones:''' This is important as a driver, getting fouls from protected zones is one of the easiest ways to get on a '''DO NOT PICK''' list. There are exceptions, and if there are no opposing robots nearby and it will benefit your alliance then maybe go for it, but this should be done sparingly.<br /> * '''Avoid spinning too much:''' While spinning is cool and a useful tool for avoiding defenders, it slows you down. Don't spin if you don't need to.<br /> * '''Avoid breaking the robot:''' Try not to break things. Given the nature of the sport it will sometimes happen on the field, but try to avoid excessive damage. The easiest way to do this is to use '''Turtle Mode.''' In many of our robots that extend outside of the frame perimeter, this mode is used to retract everything inside to avoid damage while traveling at high speed or cross-field. Note that while on the practice field it is okay to overcompensate to avoid damage, while playing make sure that you're overly cautious to the detriment of your cycle times.<br /> <br /> == Practicing ==<br /> * '''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.<br /> * '''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.<br /> * '''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.<br /> * '''Practice on every Alliance Driver Station:''' You should know how to score in all possible goals from every driver station, and practice doing so before competition. Not doing so will be detrimental to your performance because you don't get to choose driver stations until playoffs.<br /> * '''Prepare for the worst:''' You should be ready to fall back to the basics if part of your robot fails, whether that be your auto score software, a critical mechanism, pneumatic pressure, or anything else. You should know how to score manually and how to perform effective defense.<br /> * '''Practice the things you need to improve:''' Don't just keep practicing full matches or cycles. If you recognize a portion of a cycle you need practicing on, like intaking, traversing, or scoring, you should focus your practice on that section. Making effective use of your practice time will lead to the largest improvements in your driving.<br /> * '''Practice multiple paths:''' When practicing by yourself, it may be easy to just use the easiest path or scoring location. In real matches, you don't get that luxury. You're playing with 5 other robots using the same space, so try to vary your pathing when running cycles during practice.<br /> * '''Experiment:''' When practicing, your current strategy may not be the best for cycles. Make sure to try different ones and measure the results. Another great way to look for strategies is to go onto YouTube or Chief Delphi and look for analysis or strategy postings.<br /> <br /> == Competition ==<br /> * '''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 &quot;Do Not Pick&quot; list. Be careful when defending that you're only obstructing the opposing alliance!<br /> * '''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 &quot;Keep to yourself&quot; as well: work out pathing that is efficient and unobstructive.<br /> * '''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.<br /> <br /> == Playing With Others ==<br /> * '''Set Your Strategy:''' Someone on your drive/strategy team should be talking to your alliance partners at least 10 minutes before your match. Cover Auto strategies and make sure you don't interfere. Go over Teleop pathing and define everyone's roles. Make sure to also cover Endgame: where they should be for what tasks, and when they should be there. Good strategy can be the difference between a clear victory and a shattering defeat.<br /> <br /> == Anti-defense ==<br /> * '''Spin:''' When going against an opponent who’s defending against you, the main tool at your disposal spinning. Spin in the direction such that you are essentially trying to “spin around your opponent.” This reduces robot-to-robot contact and allows you to maneuver around them. Practice this before competition.<br /> * '''Use Protected Zones:''' Use the protected zones by trying to score and stay in them. However, make sure not to sacrifice cycle time for safety: still try to score outside of them if you're not at risk of defense from an opposing robot.<br /> <br /> == Defense ==<br /> * '''Identify Choke Points:''' Places where you know the robots will tend to funnel towards are your targets. These should be identified with the strategy head of your alliances before competitions.<br /> * '''Get Between Them:''' Stay between them and their goal, trying to copy their movements.<br /> * '''Spin V2:''' Anti-anti-defense is where you spin to counter their spinning: you spin in the opposite direction (like meshing gears) to counteract their spin. Practice this before competition.<br /> * '''Avoid Protected Zones:''' Arguably the most important part (and the part where so many teams mess up) is to make sure not to touch or enter zones that are protected. If you do, you '''WILL''' receive the respective foul.<br /> <br /> == Other ==<br /> * '''Visibility:''' This might seem very nuanced, but when choosing which side of your alliance driver station, '''make sure that you have visibility of your targets'''. Priority is usually given to the driver, but it depends on who controls what and where.<br /> <br /> == Quotes ==<br /> * '''StormBots:''' ''The strategic truth is that when given a choice, drivers do not e-stop their bots. With an e-stop, you forfeit any chance to regain control, even at a diminished level. You also set your bot up for significant foul points should you get nudged into foul zones. If there are any actual safety concerns, the FTAs handle them. Drive teams are focusing on strategic concerns, and that’s “do literally anything but die on the field”''.<br /> '''[Titan]''' We agree, but with the exception that we remain GP and that the rules allow it.<br /> * '''Practice like you’ve never won. Perform like you’ve never lost:''' When practicing, nothing should be left to chance. If you think defensive robots will be present, practice anti-defense. If there are anticipated problems with the robot, make sure you know how to work around them. But on the field, be confident: the only thing you’re doing on the field is running cycles. Don’t worry about what the crowds doing, etc. Just focus and be confident in your abilities.</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Drive_Principles&diff=387 2024-04-28T03:47:59Z

<p>Will.Barber: Remove redundant entry</p> <hr /> <div>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.<br /> <br /> == General ==<br /> * '''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.<br /> * '''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.<br /> * '''Avoid protected zones:''' This is important as a driver, getting fouls from protected zones is one of the easiest ways to get on a '''DO NOT PICK''' list. There are exceptions, and if there are no opposing robots nearby and it will benefit your alliance then maybe go for it, but this should be done sparingly.<br /> * '''Avoid spinning too much:''' While spinning is cool and a useful tool for avoiding defenders, it slows you down. Don't spin if you don't need to.<br /> * '''Avoid breaking the robot:''' Try not to break things. Given the nature of the sport it will sometimes happen on the field, but try to avoid excessive damage. The easiest way to do this is to use '''Turtle Mode.''' In many of our robots that extend outside of the frame perimeter, this mode is used to retract everything inside to avoid damage while traveling at high speed or cross-field. Note that while on the practice field it is okay to overcompensate to avoid damage, while playing make sure that you're overly cautious to the detriment of your cycle times.<br /> <br /> == Practicing ==<br /> * '''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.<br /> * '''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.<br /> * '''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.<br /> * '''Practice on every Alliance Driver Station:''' You should know how to score in all possible goals from every driver station, and practice doing so before competition. Not doing so will be detrimental to your performance because you don't get to choose driver stations until playoffs.<br /> * '''Prepare for the worst:''' You should be ready to fall back to the basics if part of your robot fails, whether that be your auto score software, a critical mechanism, pneumatic pressure, or anything else. You should know how to score manually and how to perform effective defense.<br /> * '''Practice the things you need to improve:''' Don't just keep practicing full matches or cycles. If you recognize a portion of a cycle you need practicing on, like intaking, traversing, or scoring, you should focus your practice on that section. Making effective use of your practice time will lead to the largest improvements in your driving.<br /> * '''Practice multiple paths:''' When practicing by yourself, it may be easy to just use the easiest path or scoring location. In real matches, you don't get that luxury. You're playing with 5 other robots using the same space, so try to vary your pathing when running cycles during practice.<br /> * '''Experiment:''' When practicing, your current strategy may not be the best for cycles. Make sure to try different ones and measure the results. Another great way to look for strategies is to go onto YouTube or Chief Delphi and look for analysis or strategy postings.<br /> <br /> == Competition ==<br /> * '''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 &quot;Do Not Pick&quot; list. Be careful when defending that you're only obstructing the opposing alliance!<br /> * '''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 &quot;Keep to yourself&quot; as well: work out pathing that is efficient and unobstructive.<br /> * '''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.<br /> <br /> == Playing With Others ==<br /> * '''Don't Interfere:''' DO NOT--under any circumstances--interfere with your alliance partners. This is incredibly important. &quot;Interference&quot; means blocking incoming robots or slowing them down. Sometimes this is unavoidable, but try to make sure that this is incredibly rare. This usually comes down to having a preset path that you follow, and coordinating that with your alliance partners before the match.<br /> * '''Set Your Strategy:''' Someone on your drive/strategy team should be talking to your alliance partners at least 10 minutes before your match. Cover Auto strategies and make sure you don't interfere. Go over Teleop pathing and define everyone's roles. Make sure to also cover Endgame: where they should be for what tasks, and when they should be there. Good strategy can be the difference between a clear victory and a shattering defeat.<br /> <br /> == Anti-defense ==<br /> * '''Spin:''' When going against an opponent who’s defending against you, the main tool at your disposal spinning. Spin in the direction such that you are essentially trying to “spin around your opponent.” This reduces robot-to-robot contact and allows you to maneuver around them. Practice this before competition.<br /> * '''Use Protected Zones:''' Use the protected zones by trying to score and stay in them. However, make sure not to sacrifice cycle time for safety: still try to score outside of them if you're not at risk of defense from an opposing robot.<br /> <br /> == Defense ==<br /> * '''Identify Choke Points:''' Places where you know the robots will tend to funnel towards are your targets. These should be identified with the strategy head of your alliances before competitions.<br /> * '''Get Between Them:''' Stay between them and their goal, trying to copy their movements.<br /> * '''Spin V2:''' Anti-anti-defense is where you spin to counter their spinning: you spin in the opposite direction (like meshing gears) to counteract their spin. Practice this before competition.<br /> * '''Avoid Protected Zones:''' Arguably the most important part (and the part where so many teams mess up) is to make sure not to touch or enter zones that are protected. If you do, you '''WILL''' receive the respective foul.<br /> <br /> == Other ==<br /> * '''Visibility:''' This might seem very nuanced, but when choosing which side of your alliance driver station, '''make sure that you have visibility of your targets'''. Priority is usually given to the driver, but it depends on who controls what and where.<br /> <br /> == Quotes ==<br /> * '''StormBots:''' ''The strategic truth is that when given a choice, drivers do not e-stop their bots. With an e-stop, you forfeit any chance to regain control, even at a diminished level. You also set your bot up for significant foul points should you get nudged into foul zones. If there are any actual safety concerns, the FTAs handle them. Drive teams are focusing on strategic concerns, and that’s “do literally anything but die on the field”''.<br /> '''[Titan]''' We agree, but with the exception that we remain GP and that the rules allow it.<br /> * '''Practice like you’ve never won. Perform like you’ve never lost:''' When practicing, nothing should be left to chance. If you think defensive robots will be present, practice anti-defense. If there are anticipated problems with the robot, make sure you know how to work around them. But on the field, be confident: the only thing you’re doing on the field is running cycles. Don’t worry about what the crowds doing, etc. Just focus and be confident in your abilities.</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Drive_Principles&diff=386 2024-04-28T03:47:18Z

<p>Will.Barber: Consolidate redundant entry</p> <hr /> <div>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.<br /> <br /> == General ==<br /> * '''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.<br /> * '''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.<br /> * '''Avoid protected zones:''' This is important as a driver, getting fouls from protected zones is one of the easiest ways to get on a '''DO NOT PICK''' list. There are exceptions, and if there are no opposing robots nearby and it will benefit your alliance then maybe go for it, but this should be done sparingly.<br /> * '''Avoid spinning too much:''' While spinning is cool and a useful tool for avoiding defenders, it slows you down. Don't spin if you don't need to.<br /> * '''Avoid breaking the robot:''' Try not to break things. Given the nature of the sport it will sometimes happen on the field, but try to avoid excessive damage. The easiest way to do this is to use '''Turtle Mode.''' In many of our robots that extend outside of the frame perimeter, this mode is used to retract everything inside to avoid damage while traveling at high speed or cross-field. Note that while on the practice field it is okay to overcompensate to avoid damage, while playing make sure that you're overly cautious to the detriment of your cycle times.<br /> <br /> == Practicing ==<br /> * '''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.<br /> * '''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.<br /> * '''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.<br /> * '''Practice on every Alliance Driver Station:''' You should know how to score in all possible goals from every driver station, and practice doing so before competition. Not doing so will be detrimental to your performance because you don't get to choose driver stations until playoffs.<br /> * '''Prepare for the worst:''' You should be ready to fall back to the basics if part of your robot fails, whether that be your auto score software, a critical mechanism, pneumatic pressure, or anything else. You should know how to score manually and how to perform effective defense.<br /> * '''Practice the things you need to improve:''' Don't just keep practicing full matches or cycles. If you recognize a portion of a cycle you need practicing on, like intaking, traversing, or scoring, you should focus your practice on that section. Making effective use of your practice time will lead to the largest improvements in your driving.<br /> * '''Practice multiple paths:''' When practicing by yourself, it may be easy to just use the easiest path or scoring location. In real matches, you don't get that luxury. You're playing with 5 other robots using the same space, so try to vary your pathing when running cycles during practice.<br /> * '''Experiment:''' When practicing, your current strategy may not be the best for cycles. Make sure to try different ones and measure the results. Another great way to look for strategies is to go onto YouTube or Chief Delphi and look for analysis or strategy postings.<br /> <br /> == Competition ==<br /> * '''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 &quot;Do Not Pick&quot; list. Be careful when defending that you're only obstructing the opposing alliance!<br /> * '''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 &quot;Keep to yourself&quot; as well: work out pathing that is efficient and unobstructive.<br /> * '''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.<br /> <br /> == Playing With Others ==<br /> * '''Don't Interfere:''' DO NOT--under any circumstances--interfere with your alliance partners. This is incredibly important. &quot;Interference&quot; means blocking incoming robots or slowing them down. Sometimes this is unavoidable, but try to make sure that this is incredibly rare. This usually comes down to having a preset path that you follow, and coordinating that with your alliance partners before the match.<br /> * '''Set Your Strategy:''' Someone on your drive/strategy team should be talking to your alliance partners at least 10 minutes before your match. Cover Auto strategies and make sure you don't interfere. Go over Teleop pathing and define everyone's roles. Make sure to also cover Endgame: where they should be for what tasks, and when they should be there. Good strategy can be the difference between a clear victory and a shattering defeat.<br /> <br /> == Anti-defense ==<br /> * '''Spin:''' When going against an opponent who’s defending against you, the main tool at your disposal spinning. Spin in the direction such that you are essentially trying to “spin around your opponent.” This reduces robot-to-robot contact and allows you to maneuver around them. Practice this before competition.<br /> * '''Use Protected Zones:''' Use the protected zones by trying to score and stay in them. However, make sure not to sacrifice cycle time for safety: still try to score outside of them if you're not at risk of defense from an opposing robot.<br /> <br /> == Defense ==<br /> * '''Identify Choke Points:''' Places where you know the robots will tend to funnel towards are your targets. These should be identified with the strategy head of your alliances before competitions.<br /> * '''Get Between Them:''' Stay between them and their goal, trying to copy their movements.<br /> * '''Spin V2:''' Anti-anti-defense is where you spin to counter their spinning: you spin in the opposite direction (like meshing gears) to counteract their spin. Practice this before competition.<br /> * '''Avoid Protected Zones:''' Arguably the most important part (and the part where so many teams mess up) is to make sure not to touch or enter zones that are protected. If you do, you '''WILL''' receive the respective foul.<br /> <br /> == Other ==<br /> * '''Visibility:''' This might seem very nuanced, but when choosing which side of your alliance driver station, '''make sure that you have visibility of your targets'''. Priority is usually given to the driver, but it depends on who controls what and where.<br /> * '''Everybody Works For You:''' At the end of the day, you represent your alliance's work on the field. So, if something's off, TELL THEM. Nothing will get fixed if you don't, and it may get worse. This is also the case for any weird controls you don't like, mechanical inconveniences, or anything else. The control setup is supposed to adapt to you, not the other way around! Tell the relevant subteam what you want changed, and pester them until they fix it!<br /> <br /> == Quotes ==<br /> * '''StormBots:''' ''The strategic truth is that when given a choice, drivers do not e-stop their bots. With an e-stop, you forfeit any chance to regain control, even at a diminished level. You also set your bot up for significant foul points should you get nudged into foul zones. If there are any actual safety concerns, the FTAs handle them. Drive teams are focusing on strategic concerns, and that’s “do literally anything but die on the field”''.<br /> '''[Titan]''' We agree, but with the exception that we remain GP and that the rules allow it.<br /> * '''Practice like you’ve never won. Perform like you’ve never lost:''' When practicing, nothing should be left to chance. If you think defensive robots will be present, practice anti-defense. If there are anticipated problems with the robot, make sure you know how to work around them. But on the field, be confident: the only thing you’re doing on the field is running cycles. Don’t worry about what the crowds doing, etc. Just focus and be confident in your abilities.</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Drive_Principles&diff=385 2024-04-28T03:44:42Z

<p>Will.Barber: Consistent Formatting</p> <hr /> <div>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.<br /> <br /> == General ==<br /> * '''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.<br /> * '''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.<br /> * '''Avoid protected zones:''' This is important as a driver, getting fouls from protected zones is one of the easiest ways to get on a '''DO NOT PICK''' list. There are exceptions, and if there are no opposing robots nearby and it will benefit your alliance then maybe go for it, but this should be done sparingly.<br /> * '''Avoid spinning too much:''' While spinning is cool and a useful tool for avoiding defenders, it slows you down. Don't spin if you don't need to.<br /> * '''Avoid breaking the robot:''' Try not to break things. Given the nature of the sport it will sometimes happen on the field, but try to avoid excessive damage. The easiest way to do this is to use '''Turtle Mode.''' In many of our robots that extend outside of the frame perimeter, this mode is used to retract everything inside to avoid damage while traveling at high speed or cross-field. Note that while on the practice field it is okay to overcompensate to avoid damage, while playing make sure that you're overly cautious to the detriment of your cycle times.<br /> <br /> == Practicing ==<br /> * '''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.<br /> * '''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.<br /> * '''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.<br /> * '''Practice on every Alliance Driver Station:''' You should know how to score in all possible goals from every driver station, and practice doing so before competition. Not doing so will be detrimental to your performance because you don't get to choose driver stations until playoffs.<br /> * '''Prepare for the worst:''' You should be ready to fall back to the basics if part of your robot fails, whether that be your auto score software, a critical mechanism, pneumatic pressure, or anything else. You should know how to score manually and how to perform effective defense.<br /> * '''Practice the things you need to improve:''' Don't just keep practicing full matches or cycles. If you recognize a portion of a cycle you need practicing on, like intaking, traversing, or scoring, you should focus your practice on that section. Making effective use of your practice time will lead to the largest improvements in your driving.<br /> * '''Practice multiple paths:''' When practicing by yourself, it may be easy to just use the easiest path or scoring location. In real matches, you don't get that luxury. You're playing with 5 other robots using the same space, so try to vary your pathing when running cycles during practice.<br /> * '''Experiment:''' When practicing, your current strategy may not be the best for cycles. Make sure to try different ones and measure the results. Another great way to look for strategies is to go onto YouTube or Chief Delphi and look for analysis or strategy postings.<br /> <br /> == Competition ==<br /> * '''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 &quot;Do Not Pick&quot; list.<br /> * '''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 &quot;Keep to yourself&quot; as well: work out pathing that is efficient and unobstructive.<br /> * '''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.<br /> <br /> == Playing With Others ==<br /> * '''Don't Interfere:''' DO NOT--under any circumstances--interfere with your alliance partners. This is incredibly important. &quot;Interference&quot; means blocking incoming robots or slowing them down. Sometimes this is unavoidable, but try to make sure that this is incredibly rare. This usually comes down to having a preset path that you follow, and coordinating that with your alliance partners before the match.<br /> * '''Set Your Strategy:''' Someone on your drive/strategy team should be talking to your alliance partners at least 10 minutes before your match. Cover Auto strategies and make sure you don't interfere. Go over Teleop pathing and define everyone's roles. Make sure to also cover Endgame: where they should be for what tasks, and when they should be there. Good strategy can be the difference between a clear victory and a shattering defeat.<br /> <br /> == Anti-defense ==<br /> * '''Spin:''' When going against an opponent who’s defending against you, the main tool at your disposal spinning. Spin in the direction such that you are essentially trying to “spin around your opponent.” This reduces robot-to-robot contact and allows you to maneuver around them. Practice this before competition.<br /> * '''Use Protected Zones:''' Use the protected zones by trying to score and stay in them. However, make sure not to sacrifice cycle time for safety: still try to score outside of them if you're not at risk of defense from an opposing robot.<br /> <br /> == Defense ==<br /> * '''Identify Choke Points:''' Places where you know the robots will tend to funnel towards are your targets. These should be identified with the strategy head of your alliances before competitions.<br /> * '''Get Between Them:''' Stay between them and their goal, trying to copy their movements.<br /> * '''Spin V2:''' Anti-anti-defense is where you spin to counter their spinning: you spin in the opposite direction (like meshing gears) to counteract their spin. Practice this before competition.<br /> * '''Avoid Protected Zones:''' Arguably the most important part (and the part where so many teams mess up) is to make sure not to touch or enter zones that are protected. If you do, you '''WILL''' receive the respective foul.<br /> * '''Don't Defend Against Your Alliance Partners:''' This is one of the worst things that can happen. If you are playing defense, don't set it up in a way that you'll impede your own alliance partners. Doing this repeatedly is a sure-fire way to land on a '''DO NOT PICK''' list.<br /> <br /> == Other ==<br /> * '''Visibility:''' This might seem very nuanced, but when choosing which side of your alliance driver station, '''make sure that you have visibility of your targets'''. Priority is usually given to the driver, but it depends on who controls what and where.<br /> * '''Everybody Works For You:''' At the end of the day, you represent your alliance's work on the field. So, if something's off, TELL THEM. Nothing will get fixed if you don't, and it may get worse. This is also the case for any weird controls you don't like, mechanical inconveniences, or anything else. The control setup is supposed to adapt to you, not the other way around! Tell the relevant subteam what you want changed, and pester them until they fix it!<br /> <br /> == Quotes ==<br /> * '''StormBots:''' ''The strategic truth is that when given a choice, drivers do not e-stop their bots. With an e-stop, you forfeit any chance to regain control, even at a diminished level. You also set your bot up for significant foul points should you get nudged into foul zones. If there are any actual safety concerns, the FTAs handle them. Drive teams are focusing on strategic concerns, and that’s “do literally anything but die on the field”''.<br /> '''[Titan]''' We agree, but with the exception that we remain GP and that the rules allow it.<br /> * '''Practice like you’ve never won. Perform like you’ve never lost:''' When practicing, nothing should be left to chance. If you think defensive robots will be present, practice anti-defense. If there are anticipated problems with the robot, make sure you know how to work around them. But on the field, be confident: the only thing you’re doing on the field is running cycles. Don’t worry about what the crowds doing, etc. Just focus and be confident in your abilities.</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Club_Principles&diff=111 2024-04-20T02:00:39Z

<p>Will.Barber: Updated links: added link to Coopertition, changed FIRST link to &quot;about&quot; page (has info on GP and Coopertition)</p> <hr /> <div>This is intended to be a brief outline of some of the guiding principles that we should abide by throughout our tenure at TRC.<br /> <br /> == Why Are We Here? ==<br /> TRC is a place to learn, to find a community, and to build an epic robot. Although TRC is structured around building a robot to take to competition, the most important skills that we learn at TRC are about working as a team. Winning the competition is nice but not our primary goal, and that is reflected in how we treat both our fellow teammates and members of other teams. It is not a place for insults or patronization: it's a place for learning from each other and helping each other to succeed. Our success is measured by how much we learn and how much we grow as a team, not by how many Blue Banners we take home.<br /> <br /> == FIRST Principles ==<br /> TRC is a FIRST organization. This means that the FIRST principles of [https://www.firstinspires.org/node/20896 ''Coopertition''] and [https://www.youtube.com/watch?v=cl6JkPtDki4 ''Gracious Professionalism''] are core to its being. For more information on these, visit the [https://www.firstinspires.org/about FIRST website].<br /> <br /> ''Coopertition'' refers to the fact that while you are competing against other teams with the goal of winning the competition, you're still all members of the FIRST community and are willing to help other teams out when they need it. This means that we do not hesitate to lend parts or tools to other teams that need it (within reason). If a team asks for help or advice, we gladly offer it to them. Just like within our team itself, FIRST succeeds as a community when teams help boost each other up instead of tearing each other down.<br /> <br /> ''Gracious Professionalism'' (GP) is core to how we treat our fellow teammates, members of other teams, referees, judges, and everyone we interact with. We do NOT make derogatory remarks about other teams, nor do we make arrogant ones about ourselves. We are always respectful of those we compete with, and those we compete against. We are not sore losers or arrogant winners. It's also important to note that ''Gracious Professionalism'' is a 2-way street. Often times, we may be tempted to ask for other's help and expect people would grant it in the name of ''Gracious Professionalism''. It's okay to ask for help but ask yourself first if you can find alternatives to do what you want instead of inconvenient other teams. There is always a cost to the teams that lend you help, so be considerate if you can make do with other alternatives. It's also ''Gracious Professionalism'' to minimize unnecessary inconvenience to other teams. It's okay if the other teams said no. Don't hold a grudge against them just because they don't want to help. <br /> <br /> == What Should I Do? ==<br /> * Follow FIRST and TRC guidelines and principles: These make the club a welcoming and constructive place. This is the most important thing you can do.<br /> * Ask questions: If you're not sure about something, ask! You're here to learn, and no one came in knowing everything from the beginning. Mentors and veteran students don't bite.<br /> * Show up: TRC is high commitment, but you get out what you put in. If you don't show up, you won't understand what's happening, you won't learn, and you won't come away from this experience having gained anything valuable.<br /> * Make your voice heard: You have good ideas! Just because someone else hasn't pointed out what you've thought of doesn't mean that you're wrong, so don't be quiet!<br /> * Thank the mentors: They are volunteers, and they work incredibly hard to make this club run. Saying &quot;Thank you&quot; is the least that you can do.<br /> <br /> ----<br /> <br /> Club Constitution: https://www.titanrobotics.com/club-constitution</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=User:Will.Barber&diff=90 2024-04-17T13:57:01Z

<p>Will.Barber: /* Club History: */</p> <hr /> <div>==Will Barber==<br /> <br /> ===Current Role:===<br /> Part-time mentor 2024 - Present<br /> <br /> ===Club History:===<br /> TRC Student 2019 - 2023<br /> * FTC 2019 - 2023<br /> * FRC 2020 - 2023<br /> <br /> ===Subteams:===<br /> * Drive FTC<br /> * Mechanical FTC/FRC<br /> * Dabbled in software FTC<br /> <br /> ===Positions:===<br /> * FTC Driver 2021-2022<br /> * Mechanical Head 2022-2023<br /> <br /> ===Miscellaneous:===<br /> * TRC Discord name: Magic Ratchet<br /> * Currently an undergraduate at UC Davis with a major in Computer Science and Engineering</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Club_Principles&diff=84 2024-04-17T04:03:52Z

<p>Will.Barber: Fix accidentally deleted &quot;=&quot;</p> <hr /> <div>This is intended to be a brief outline of some of the guiding principles that we should abide by throughout our tenure at TRC.<br /> <br /> ==Why We're Here==<br /> TRC is a place to learn, to find a community, and to build an epic robot. Although TRC is structured around building a robot to take to competition, the most important skills that we learn at TRC are about working as a team. Our primary purpose is not to win, and that is reflected in how we treat both our fellow teammates and members of other teams. It is not a place for insults or patronization: it's a place for learning from each other and helping each other to succeed. Our success is measured by how much we learn and how much we grow as a team, not by how many Blue Banners we take home.<br /> <br /> ==FIRST Principles==<br /> TRC is a FIRST organization. This means that the FIRST principles of Coopertition and Gracious Professionalism are core to its being. For more information on these, visit the FIRST website.<br /> <br /> Coopertition refers to the fact that while you are competing against other teams with the goal of winning the competition, you're still all members of the FIRST community and are willing to help other teams out when they need it. This means that we do not hesitate to lend parts or tools to other teams that need it (within reason). If a team asks for help or advice, we gladly offer it to them. Just like within our team itself, FIRST succeeds as a community when teams help boost each other up instead of tearing each other down.<br /> <br /> Gracious Professionalism (GP) is core to how we treat our fellow teammates, members of other teams, referees, judges, and everyone we interact with. We do NOT make derogatory remarks about other teams, nor do we make arrogant ones about ourselves. We are always respectful of those we compete with, and those we compete against. We are not sore losers or arrogant winners.<br /> <br /> ==What Should I Do?==<br /> * Follow FIRST and TRC guidelines and principles: These make the club a welcoming and constructive place. This is the most important thing you can do.<br /> * Ask questions: If you're not sure about something, ask! You're here to learn, and no one came in knowing everything from the beginning. Mentors and veteran students don't bite.<br /> * Show up: TRC is high commitment, but you get out what you put in. If you don't show up, you won't understand what's happening, you won't learn, and you won't come away from this experience having gained anything valuable.<br /> * Make your voice heard: You have good ideas! Just because someone else hasn't pointed out what you've thought of doesn't mean that you're wrong, so don't be quiet!<br /> * Thank the mentors: They are volunteers, and they work incredibly hard to make this club run. Saying &quot;Thank you&quot; is the least that you can do.<br /> <br /> ----<br /> <br /> Club Constitution: https://www.titanrobotics.com/club-constitution</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Club_Principles&diff=83 2024-04-17T04:03:35Z

<p>Will.Barber: Change whitespace of subheading to match Mike's</p> <hr /> <div>This is intended to be a brief outline of some of the guiding principles that we should abide by throughout our tenure at TRC.<br /> <br /> =Why We're Here==<br /> TRC is a place to learn, to find a community, and to build an epic robot. Although TRC is structured around building a robot to take to competition, the most important skills that we learn at TRC are about working as a team. Our primary purpose is not to win, and that is reflected in how we treat both our fellow teammates and members of other teams. It is not a place for insults or patronization: it's a place for learning from each other and helping each other to succeed. Our success is measured by how much we learn and how much we grow as a team, not by how many Blue Banners we take home.<br /> <br /> ==FIRST Principles==<br /> TRC is a FIRST organization. This means that the FIRST principles of Coopertition and Gracious Professionalism are core to its being. For more information on these, visit the FIRST website.<br /> <br /> Coopertition refers to the fact that while you are competing against other teams with the goal of winning the competition, you're still all members of the FIRST community and are willing to help other teams out when they need it. This means that we do not hesitate to lend parts or tools to other teams that need it (within reason). If a team asks for help or advice, we gladly offer it to them. Just like within our team itself, FIRST succeeds as a community when teams help boost each other up instead of tearing each other down.<br /> <br /> Gracious Professionalism (GP) is core to how we treat our fellow teammates, members of other teams, referees, judges, and everyone we interact with. We do NOT make derogatory remarks about other teams, nor do we make arrogant ones about ourselves. We are always respectful of those we compete with, and those we compete against. We are not sore losers or arrogant winners.<br /> <br /> ==What Should I Do?==<br /> * Follow FIRST and TRC guidelines and principles: These make the club a welcoming and constructive place. This is the most important thing you can do.<br /> * Ask questions: If you're not sure about something, ask! You're here to learn, and no one came in knowing everything from the beginning. Mentors and veteran students don't bite.<br /> * Show up: TRC is high commitment, but you get out what you put in. If you don't show up, you won't understand what's happening, you won't learn, and you won't come away from this experience having gained anything valuable.<br /> * Make your voice heard: You have good ideas! Just because someone else hasn't pointed out what you've thought of doesn't mean that you're wrong, so don't be quiet!<br /> * Thank the mentors: They are volunteers, and they work incredibly hard to make this club run. Saying &quot;Thank you&quot; is the least that you can do.<br /> <br /> ----<br /> <br /> Club Constitution: https://www.titanrobotics.com/club-constitution</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Drive_Principles&diff=82 2024-04-17T04:03:12Z

<p>Will.Barber: Change whitespace of subheading to match Mike's</p> <hr /> <div>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.<br /> <br /> ==General==<br /> * 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.<br /> * 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.<br /> <br /> ==Practicing==<br /> * 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.<br /> * 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.<br /> * 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.<br /> <br /> ==Competition==<br /> * 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 &quot;Do Not Pick&quot; list.<br /> * 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 &quot;Keep to yourself&quot; as well: work out pathing that is efficient and unobstructive.<br /> * 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.</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Titan_Robotics_Club_Wiki&diff=79 2024-04-17T02:58:16Z

<p>Will.Barber: Added short intro.</p> <hr /> <div>Welcome to the Titan Robotics Club (TRC) Wiki! Here you can find some of the club's guiding principles, our records of the lessons we've learned from previous competitions, and other information useful for mitigating loss of knowledge as club members graduate.<br /> <br /> ==General Robotics==<br /> ===[[Club Principles]]===<br /> ===[[Technical Principles]]===<br /> ===[[Drive Principles]]===<br /> ==Robotics Seasons==<br /> ===[[FRC2023-2024: Crescendo]]===<br /> ===[[FTC2023-2024: CenterStage]]===<br /> <br /> ==MediaWiki Help==<br /> * [https://www.mediawiki.org/wiki/Help:Formatting Format text by Wiki Markup]<br /> * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br /> * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]<br /> * [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]<br /> * [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]<br /> * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Club_Principles&diff=78 2024-04-17T02:50:32Z

<p>Will.Barber: Change tense</p> <hr /> <div>This is intended to be a brief outline of some of the guiding principles that we should abide by throughout our tenure at TRC.<br /> <br /> == Why We're Here ==<br /> TRC is a place to learn, to find a community, and to build an epic robot. Although TRC is structured around building a robot to take to competition, the most important skills that we learn at TRC are about working as a team. Our primary purpose is not to win, and that is reflected in how we treat both our fellow teammates and members of other teams. It is not a place for insults or patronization: it's a place for learning from each other and helping each other to succeed. Our success is measured by how much we learn and how much we grow as a team, not by how many Blue Banners we take home.<br /> <br /> == FIRST Principles ==<br /> TRC is a FIRST organization. This means that the FIRST principles of Coopertition and Gracious Professionalism are core to its being. For more information on these, visit the FIRST website.<br /> <br /> Coopertition refers to the fact that while you are competing against other teams with the goal of winning the competition, you're still all members of the FIRST community and are willing to help other teams out when they need it. This means that we do not hesitate to lend parts or tools to other teams that need it (within reason). If a team asks for help or advice, we gladly offer it to them. Just like within our team itself, FIRST succeeds as a community when teams help boost each other up instead of tearing each other down.<br /> <br /> Gracious Professionalism (GP) is core to how we treat our fellow teammates, members of other teams, referees, judges, and everyone we interact with. We do NOT make derogatory remarks about other teams, nor do we make arrogant ones about ourselves. We are always respectful of those we compete with, and those we compete against. We are not sore losers or arrogant winners.<br /> <br /> == What Should I Do? ==<br /> * Follow FIRST and TRC guidelines and principles: These make the club a welcoming and constructive place. This is the most important thing you can do.<br /> * Ask questions: If you're not sure about something, ask! You're here to learn, and no one came in knowing everything from the beginning. Mentors and veteran students don't bite.<br /> * Show up: TRC is high commitment, but you get out what you put in. If you don't show up, you won't understand what's happening, you won't learn, and you won't come away from this experience having gained anything valuable.<br /> * Make your voice heard: You have good ideas! Just because someone else hasn't pointed out what you've thought of doesn't mean that you're wrong, so don't be quiet!<br /> * Thank the mentors: They are volunteers, and they work incredibly hard to make this club run. Saying &quot;Thank you&quot; is the least that you can do.<br /> <br /> ----<br /> <br /> Club Constitution: https://www.titanrobotics.com/club-constitution</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Club_Principles&diff=77 2024-04-17T02:49:08Z

<p>Will.Barber: Rephrased to sound less passive-aggressive</p> <hr /> <div>This is intended to be a brief outline of some of the guiding principles that we should abide by throughout our tenure at TRC.<br /> <br /> == Why We're Here ==<br /> TRC is a place to learn, to find a community, and to build an epic robot. Although TRC is structured around building a robot to take to competition, the most important skills that you'll learn at TRC are about working as a team. Our primary purpose is not to win, and that is reflected in how we treat both our fellow teammates and members of other teams. It is not a place for insults or patronization: it's a place for learning from each other and helping each other to succeed. Our success is measured by how much we learn and how much we grow as a team, not by how many Blue Banners we take home.<br /> <br /> == FIRST Principles ==<br /> TRC is a FIRST organization. This means that the FIRST principles of Coopertition and Gracious Professionalism are core to its being. For more information on these, visit the FIRST website.<br /> <br /> Coopertition refers to the fact that while you are competing against other teams with the goal of winning the competition, you're still all members of the FIRST community and are willing to help other teams out when they need it. This means that we do not hesitate to lend parts or tools to other teams that need it (within reason). If a team asks for help or advice, we gladly offer it to them. Just like within our team itself, FIRST succeeds as a community when teams help boost each other up instead of tearing each other down.<br /> <br /> Gracious Professionalism (GP) is core to how we treat our fellow teammates, members of other teams, referees, judges, and everyone we interact with. We do NOT make derogatory remarks about other teams, nor do we make arrogant ones about ourselves. We are always respectful of those we compete with, and those we compete against. We are not sore losers or arrogant winners.<br /> <br /> == What Should I Do? ==<br /> * Follow FIRST and TRC guidelines and principles: These make the club a welcoming and constructive place. This is the most important thing you can do.<br /> * Ask questions: If you're not sure about something, ask! You're here to learn, and no one came in knowing everything from the beginning. Mentors and veteran students don't bite.<br /> * Show up: TRC is high commitment, but you get out what you put in. If you don't show up, you won't understand what's happening, you won't learn, and you won't come away from this experience having gained anything valuable.<br /> * Make your voice heard: You have good ideas! Just because someone else hasn't pointed out what you've thought of doesn't mean that you're wrong, so don't be quiet!<br /> * Thank the mentors: They are volunteers, and they work incredibly hard to make this club run. Saying &quot;Thank you&quot; is the least that you can do.<br /> <br /> ----<br /> <br /> Club Constitution: https://www.titanrobotics.com/club-constitution</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Club_Principles&diff=76 2024-04-17T02:48:25Z

<p>Will.Barber: + they</p> <hr /> <div>This is intended to be a brief outline of some of the guiding principles that we should abide by throughout our tenure at TRC.<br /> <br /> == Why We're Here ==<br /> TRC is a place to learn, to find a community, and to build an epic robot. Although TRC is structured around building a robot to take to competition, the most important skills that you'll learn at TRC are about working as a team. Our primary purpose is not to win, and that is reflected in how we treat both our fellow teammates and members of other teams. It is not a place for insults or patronization: it's a place for learning from each other and helping each other to succeed. Our success is measured by how much we learn and how much we grow as a team, not by how many Blue Banners we take home.<br /> <br /> == FIRST Principles ==<br /> TRC is a FIRST organization. This means that the FIRST principles of Coopertition and Gracious Professionalism are core to its being. For more information on these, visit the FIRST website.<br /> <br /> Coopertition refers to the fact that while you are competing against other teams with the goal of winning the competition, you're still all members of the FIRST community and are willing to help other teams out when they need it. This means that we do not hesitate to lend parts or tools to other teams that need it (within reason). If a team asks for help or advice, we gladly offer it to them. Just like within our team itself, FIRST succeeds as a community when teams help boost each other up instead of tearing each other down.<br /> <br /> Gracious Professionalism (GP) is core to how we treat our fellow teammates, members of other teams, referees, judges, and everyone we interact with. We do NOT make derogatory remarks about other teams, nor do we make arrogant ones about ourselves. We are always respectful of those we compete with, and those we compete against. We are not sore losers or arrogant winners.<br /> <br /> == What Should I Do? ==<br /> * Follow FIRST and TRC guidelines and principles: These make the club a welcoming and constructive place. This is the most important thing you can do.<br /> * Ask questions: If you're not sure about something, ask! You're here to learn, and no one came in knowing everything from the beginning. Mentors and veteran students don't bite.<br /> * Show up: TRC is high commitment, but you get out what you put in. If you don't show up, you won't understand what's happening, you won't learn, and you won't come away from this experience having gained anything valuable.<br /> * Make your voice heard: You have good ideas! Just because someone else hasn't pointed out what you've thought of doesn't mean that you're wrong, so don't be quiet!<br /> * Thank the mentors: They are volunteers, and they work incredibly hard to make this club run. Saying &quot;Thank you&quot; is the least that they deserve.<br /> <br /> ----<br /> <br /> Club Constitution: https://www.titanrobotics.com/club-constitution</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Titan_Robotics_Club_Wiki&diff=75 2024-04-17T02:45:35Z

<p>Will.Barber: Added links to other Principles pages</p> <hr /> <div>==General Robotics==<br /> ===[[Club Principles]]===<br /> ===[[Technical Principles]]===<br /> ===[[Drive Principles]]===<br /> ==Robotics Seasons==<br /> ===[[FRC2023-2024: Crescendo]]===<br /> ===[[FTC2023-2024: CenterStage]]===<br /> <br /> ==MediaWiki Help==<br /> * [https://www.mediawiki.org/wiki/Help:Formatting Format text by Wiki Markup]<br /> * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br /> * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]<br /> * [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]<br /> * [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]<br /> * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Club_Principles&diff=74 2024-04-17T02:41:26Z

<p>Will.Barber: Created Club Principles page. This is supposed to be kind of like an ethics code for the club.</p> <hr /> <div>This is intended to be a brief outline of some of the guiding principles that we should abide by throughout our tenure at TRC.<br /> <br /> == Why We're Here ==<br /> TRC is a place to learn, to find a community, and to build an epic robot. Although TRC is structured around building a robot to take to competition, the most important skills that you'll learn at TRC are about working as a team. Our primary purpose is not to win, and that is reflected in how we treat both our fellow teammates and members of other teams. It is not a place for insults or patronization: it's a place for learning from each other and helping each other to succeed. Our success is measured by how much we learn and how much we grow as a team, not by how many Blue Banners we take home.<br /> <br /> == FIRST Principles ==<br /> TRC is a FIRST organization. This means that the FIRST principles of Coopertition and Gracious Professionalism are core to its being. For more information on these, visit the FIRST website.<br /> <br /> Coopertition refers to the fact that while you are competing against other teams with the goal of winning the competition, you're still all members of the FIRST community and are willing to help other teams out when they need it. This means that we do not hesitate to lend parts or tools to other teams that need it (within reason). If a team asks for help or advice, we gladly offer it to them. Just like within our team itself, FIRST succeeds as a community when teams help boost each other up instead of tearing each other down.<br /> <br /> Gracious Professionalism (GP) is core to how we treat our fellow teammates, members of other teams, referees, judges, and everyone we interact with. We do NOT make derogatory remarks about other teams, nor do we make arrogant ones about ourselves. We are always respectful of those we compete with, and those we compete against. We are not sore losers or arrogant winners.<br /> <br /> == What Should I Do? ==<br /> * Follow FIRST and TRC guidelines and principles: These make the club a welcoming and constructive place. This is the most important thing you can do.<br /> * Ask questions: If you're not sure about something, ask! You're here to learn, and no one came in knowing everything from the beginning. Mentors and veteran students don't bite.<br /> * Show up: TRC is high commitment, but you get out what you put in. If you don't show up, you won't understand what's happening, you won't learn, and you won't come away from this experience having gained anything valuable.<br /> * Make your voice heard: You have good ideas! Just because someone else hasn't pointed out what you've thought of doesn't mean that you're wrong, so don't be quiet!<br /> * Thank the mentors: They are volunteers, and work incredibly hard to make this club run. Saying &quot;Thank you&quot; is the least that they deserve.<br /> <br /> ----<br /> <br /> Club Constitution: https://www.titanrobotics.com/club-constitution</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=Drive_Principles&diff=73 2024-04-17T02:15:34Z

<p>Will.Barber: Created Driving Principles page. This is not intended to be all-encompassing, and rather to be a basic foundation. It might be a good idea to eventually have wikilinks in here to more detailed pages (maybe one about offense, defense, off-field, etc.)</p> <hr /> <div>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.<br /> <br /> == General ==<br /> * 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 subteam! It's their job to make the robot adapt to you, not the other way around.<br /> * 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.<br /> <br /> == Practicing ==<br /> * 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 subteam! Even if it's uncommon for the failure to occur, it's still important to inform the technical subteam about it. It's vital to get these problems fixed before competition so that they do not occur during a match, crippling our gameplay.<br /> * 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.<br /> * 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.<br /> <br /> == Competition ==<br /> * 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 &quot;Do Not Pick&quot; list.<br /> * 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 &quot;Keep to yourself&quot; as well: work out pathing that is efficient and unobstructive.<br /> * 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.</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=FRC2023-2024:_Crescendo&diff=61 2024-04-17T00:41:13Z

<p>Will.Barber: book -&gt; guide</p> <hr /> <div>= Lessons Learned =<br /> == Drive Team ==<br /> === Driver: Noah Fang ===<br /> ==== DISCLAIMER ====<br /> Nothing in this guide is set in stone. FRC is constantly evolving and there are many cases on the field where you can't follow this. At the end of the day, use your best judgment.<br /> ==== General ====<br /> # '''AVOID PROTECTED ZONES:''' This is important as a driver: getting fouls from protected zones is one of the easiest ways to get on a '''DO NOT PICK''' list. There are exceptions, and if there are no opposing robots nearby and it will benefit your alliance then maybe go for it, but this should be done sparingly.<br /> # '''AVOID SPINNING TOO MUCH:''' While spinning is cool and a useful tool for avoiding defenders, it slows you down. Don't spin if you don't need to.<br /> # '''AVOID BREAKING WHAT DOESN'T NEED TO GET BROKEN:''' Try not to break things. Given the nature of the sport it will sometimes happen on the field, but try to avoid excessive damage. The easiest way to do this is to use '''Turtle Mode.''' In many of our robots that extend outside of the frame perimeter, this mode is used to retract everything inside to avoid damage while traveling at high speed or cross-field. Note that while on the practice field it is okay to overcompensate to avoid damage, while playing make sure that you're overly cautious to the detriment of your cycle times.<br /> ==== Practicing ====<br /> # '''EVERY ALLIANCE DRIVER STATION:''' You should know how to score in all possible goals from every driver station, and practice doing so before competition. Not doing so will be detrimental to your performance because you don't get to choose driver stations until playoffs.<br /> # '''PREPARE FOR THE WORST:''' You should be ready to fall back to the basics if part of your robot fails, whether that be your auto score software, a critical mechanism, pneumatic pressure, or anything else. You should know how to score manually and how to perform effective defense.<br /> # '''PRACTICE THE THINGS YOU NEED TO IMPROVE:''' Don't just keep practicing full matches or cycles. If you recognize a portion of a cycle you need practicing on, like intaking, traversing, or scoring, you should focus your practice on that section. Making effective use of your practice time will lead to the largest improvements in your driving.<br /> # '''PRACTICE MULTIPLE PATHS:''' When practicing by yourself, it may be easy to just use the easiest path or scoring location. In real matches, you don't get that luxury. You're playing with 5 other robots using the same space, so try to vary your pathing when running cycles during practice.<br /> # '''EXPERIMENT:''' When practicing, your current strategy may not be the best for cycles. Make sure to try different ones and measure the results. Another great way to look for strategies is to go onto YouTube or Chief Delphi and look for analysis or strategy postings.<br /> ==== Playing With Others ====<br /> # '''DON'T INTERFERE:''' DO NOT--under any circumstances--interfere with your alliance partners. This is incredibly important. &quot;Interference&quot; means blocking incoming robots or slowing them down. Sometimes this is unavoidable, but try to make sure that this is incredibly rare. This usually comes down to having a preset path that you follow, and coordinating that with your alliance partners before the match.<br /> # '''SET YOUR STRATEGY:''' Someone on your drive/strategy team should be talking to your alliance partners at least 10 minutes before your match. Cover Auto strategies and make sure you don't interfere. Go over Teleop pathing and define everyone's roles. Make sure to also cover Endgame: where they should be for what tasks, and when they should be there. Good strategy can be the difference between a clear victory and a shattering defeat.<br /> ==== Anti-defense ====<br /> # '''SPIN:''' When going against an opponent who’s defending against you, the main tool at your disposal spinning. Spin in the direction such that you are essentially trying to “spin around your opponent.” This reduces robot-to-robot contact and allows you to maneuver around them. Practice this before competition.<br /> # '''USE PROTECTED ZONES:''' Use the protected zones by trying to score and stay in them. However, make sure not to sacrifice cycle time for safety: still try to score outside of them if you're not at risk of defense from an opposing robot.<br /> <br /> ==== Defense ====<br /> # '''IDENTIFY CHOKE POINTS:''' Places where you know the robots will tend to funnel towards are your targets. These should be identified with the strategy head of your alliances before competitions.<br /> # '''GET BETWEEN THEM:''' Stay between them and their goal, trying to copy their movements.<br /> # '''SPIN V2:''' Anti-anti-defense is where you spin to counter their spinning: you spin in the opposite direction (like meshing gears) to counteract their spin. Practice this before competition.<br /> # '''AVOID PROTECTED ZONES:''' Arguably the most important part (and the part where so many teams mess up) is to make sure not to touch or enter zones that are protected. If you do, you '''WILL''' receive the respective foul.<br /> # '''DON'T DEFEND AGAINST YOUR ALLIANCE PARTNERS:''' This is one of the worst things that can happen. If you are playing defense, don't set it up in a way that you'll impede your own alliance partners. Doing this repeatedly is a sure-fire way to land on a '''DO NOT PICK''' list.<br /> ==== Other ====<br /> # '''VISIBILITY:''' This might seem very nuanced, but when choosing which side of your alliance driver station, '''make sure that you have visibility of your targets'''. Priority is usually given to the driver, but it depends on who controls what and where.<br /> # '''EVERYBODY WORKS FOR YOU:''' At the end of the day, you represent your alliance's work on the field. So, if something's off, TELL THEM. Nothing will get fixed if you don't, and it may get worse. This is also the case for any weird controls you don't like, mechanical inconveniences, or anything else. The control setup is supposed to adapt to you, not the other way around! Tell the relevant subteam what you want changed, and pester them until they fix it!<br /> ==== Quotes ====<br /> * '''StormBots:''' ''The strategic truth is that when given a choice, drivers do not e-stop their bots. With an e-stop, you forfeit any chance to regain control, even at a diminished level. You also set your bot up for significant foul points should you get nudged into foul zones. If there are any actual safety concerns, the FTAs handle them. Drive teams are focusing on strategic concerns, and that’s “do literally anything but die on the field”''.<br /> '''[Titan]''' We agree, but with the exception that we remain GP and that the rules allow it.<br /> * '''Practice like you’ve never won. Perform like you’ve never lost:''' When practicing, nothing should be left to chance. If you think defensive robots will be present, practice anti-defense. If there are anticipated problems with the robot, make sure you know how to work around them. But on the field, be confident: the only thing you’re doing on the field is running cycles. Don’t worry about what the crowds doing, etc. Just focus and be confident in your abilities.<br /> == Electrical Team ==<br /> === Electrical Lead: Jackson Blunt ===<br /> == Mechanical Team ==<br /> === Mechanical Lead: Noah Fang ===<br /> == Programming Team ==<br /> === Programming Lead: Anand Krishnan ===<br /> === Programmer: Nathan Sun ===</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=FRC2023-2024:_Crescendo&diff=60 2024-04-17T00:37:34Z

<p>Will.Barber: Edits for grammar, clarity, and minor formatting changes</p> <hr /> <div>= Lessons Learned =<br /> == Drive Team ==<br /> === Driver: Noah Fang ===<br /> ==== DISCLAIMER ====<br /> Nothing in this book is set in stone. FRC is constantly evolving and there are many cases on the field where you can't follow this. At the end of the day, use your best judgment.<br /> ==== General ====<br /> # '''AVOID PROTECTED ZONES:''' This is important as a driver: getting fouls from protected zones is one of the easiest ways to get on a '''DO NOT PICK''' list. There are exceptions, and if there are no opposing robots nearby and it will benefit your alliance then maybe go for it, but this should be done sparingly.<br /> # '''AVOID SPINNING TOO MUCH:''' While spinning is cool and a useful tool for avoiding defenders, it slows you down. Don't spin if you don't need to.<br /> # '''AVOID BREAKING WHAT DOESN'T NEED TO GET BROKEN:''' Try not to break things. Given the nature of the sport it will sometimes happen on the field, but try to avoid excessive damage. The easiest way to do this is to use '''Turtle Mode.''' In many of our robots that extend outside of the frame perimeter, this mode is used to retract everything inside to avoid damage while traveling at high speed or cross-field. Note that while on the practice field it is okay to overcompensate to avoid damage, while playing make sure that you're overly cautious to the detriment of your cycle times.<br /> ==== Practicing ====<br /> # '''EVERY ALLIANCE DRIVER STATION:''' You should know how to score in all possible goals from every driver station, and practice doing so before competition. Not doing so will be detrimental to your performance because you don't get to choose driver stations until playoffs.<br /> # '''PREPARE FOR THE WORST:''' You should be ready to fall back to the basics if part of your robot fails, whether that be your auto score software, a critical mechanism, pneumatic pressure, or anything else. You should know how to score manually and how to perform effective defense.<br /> # '''PRACTICE THE THINGS YOU NEED TO IMPROVE:''' Don't just keep practicing full matches or cycles. If you recognize a portion of a cycle you need practicing on, like intaking, traversing, or scoring, you should focus your practice on that section. Making effective use of your practice time will lead to the largest improvements in your driving.<br /> # '''PRACTICE MULTIPLE PATHS:''' When practicing by yourself, it may be easy to just use the easiest path or scoring location. In real matches, you don't get that luxury. You're playing with 5 other robots using the same space, so try to vary your pathing when running cycles during practice.<br /> # '''EXPERIMENT:''' When practicing, your current strategy may not be the best for cycles. Make sure to try different ones and measure the results. Another great way to look for strategies is to go onto YouTube or Chief Delphi and look for analysis or strategy postings.<br /> ==== Playing With Others ====<br /> # '''DON'T INTERFERE:''' DO NOT--under any circumstances--interfere with your alliance partners. This is incredibly important. &quot;Interference&quot; means blocking incoming robots or slowing them down. Sometimes this is unavoidable, but try to make sure that this is incredibly rare. This usually comes down to having a preset path that you follow, and coordinating that with your alliance partners before the match.<br /> # '''SET YOUR STRATEGY:''' Someone on your drive/strategy team should be talking to your alliance partners at least 10 minutes before your match. Cover Auto strategies and make sure you don't interfere. Go over Teleop pathing and define everyone's roles. Make sure to also cover Endgame: where they should be for what tasks, and when they should be there. Good strategy can be the difference between a clear victory and a shattering defeat.<br /> ==== Anti-defense ====<br /> # '''SPIN:''' When going against an opponent who’s defending against you, the main tool at your disposal spinning. Spin in the direction such that you are essentially trying to “spin around your opponent.” This reduces robot-to-robot contact and allows you to maneuver around them. Practice this before competition.<br /> # '''USE PROTECTED ZONES:''' Use the protected zones by trying to score and stay in them. However, make sure not to sacrifice cycle time for safety: still try to score outside of them if you're not at risk of defense from an opposing robot.<br /> <br /> ==== Defense ====<br /> # '''IDENTIFY CHOKE POINTS:''' Places where you know the robots will tend to funnel towards are your targets. These should be identified with the strategy head of your alliances before competitions.<br /> # '''GET BETWEEN THEM:''' Stay between them and their goal, trying to copy their movements.<br /> # '''SPIN V2:''' Anti-anti-defense is where you spin to counter their spinning: you spin in the opposite direction (like meshing gears) to counteract their spin. Practice this before competition.<br /> # '''AVOID PROTECTED ZONES:''' Arguably the most important part (and the part where so many teams mess up) is to make sure not to touch or enter zones that are protected. If you do, you '''WILL''' receive the respective foul.<br /> # '''DON'T DEFEND AGAINST YOUR ALLIANCE PARTNERS:''' This is one of the worst things that can happen. If you are playing defense, don't set it up in a way that you'll impede your own alliance partners. Doing this repeatedly is a sure-fire way to land on a '''DO NOT PICK''' list.<br /> ==== Other ====<br /> # '''VISIBILITY:''' This might seem very nuanced, but when choosing which side of your alliance driver station, '''make sure that you have visibility of your targets'''. Priority is usually given to the driver, but it depends on who controls what and where.<br /> # '''EVERYBODY WORKS FOR YOU:''' At the end of the day, you represent your alliance's work on the field. So, if something's off, TELL THEM. Nothing will get fixed if you don't, and it may get worse. This is also the case for any weird controls you don't like, mechanical inconveniences, or anything else. The control setup is supposed to adapt to you, not the other way around! Tell the relevant subteam what you want changed, and pester them until they fix it!<br /> ==== Quotes ====<br /> * '''StormBots:''' ''The strategic truth is that when given a choice, drivers do not e-stop their bots. With an e-stop, you forfeit any chance to regain control, even at a diminished level. You also set your bot up for significant foul points should you get nudged into foul zones. If there are any actual safety concerns, the FTAs handle them. Drive teams are focusing on strategic concerns, and that’s “do literally anything but die on the field”''.<br /> '''[Titan]''' We agree, but with the exception that we remain GP and that the rules allow it.<br /> * '''Practice like you’ve never won. Perform like you’ve never lost:''' When practicing, nothing should be left to chance. If you think defensive robots will be present, practice anti-defense. If there are anticipated problems with the robot, make sure you know how to work around them. But on the field, be confident: the only thing you’re doing on the field is running cycles. Don’t worry about what the crowds doing, etc. Just focus and be confident in your abilities.<br /> == Electrical Team ==<br /> === Electrical Lead: Jackson Blunt ===<br /> == Mechanical Team ==<br /> === Mechanical Lead: Noah Fang ===<br /> == Programming Team ==<br /> === Programming Lead: Anand Krishnan ===<br /> === Programmer: Nathan Sun ===</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=User:Will.Barber&diff=59 2024-04-17T00:08:06Z

<p>Will.Barber: Improved formatting</p> <hr /> <div>==Will Barber==<br /> <br /> ===Current Role:===<br /> Part-time mentor 2024 - Present<br /> <br /> ===Club History:===<br /> TRC 2019 - 2023<br /> * FTC 2019 - 2023<br /> * FRC 2020 - 2023<br /> <br /> ===Subteams:===<br /> * Drive FTC<br /> * Mechanical FTC/FRC<br /> * Dabbled in software FTC<br /> <br /> ===Positions:===<br /> * FTC Driver 2021-2022<br /> * Mechanical Head 2022-2023<br /> <br /> ===Miscellaneous:===<br /> * TRC Discord name: Magic Ratchet<br /> * Currently an undergraduate at UC Davis with a major in Computer Science and Engineering</div>

Will.Barber http://trcnet.asuscomm.com/mediawiki/index.php?title=User:Will.Barber&diff=57 2024-04-16T23:58:17Z

<p>Will.Barber: Mechanical member from 2019-2023, and current part-time mentor.</p> <hr /> <div>Will Barber<br /> <br /> Part-time mentor 2024-Present<br /> <br /> TRC 2019 - 2023<br /> FTC 2019 - 2023<br /> FRC 2020 - 2023<br /> <br /> Mechanical FTC/FRC<br /> Dabbled in software FTC<br /> <br /> FTC Driver 2021-2022<br /> Mechanical Head 2022-2023<br /> <br /> TRC Discord name: Magic Ratchet<br /> <br /> Currently an undergraduate at UC Davis with a major in Computer Science and Engineering</div>

Will.Barber