FRC2023-2024: Crescendo: Difference between revisions

From TrcWiki
Jump to navigation Jump to search
(Created page with "= Lessons Learned = == Drive Team == === Driver: Noah Fang === ==== DISCLAIMER ==== Nothing in this book is set in stone, FRC is constantly evolving and there are so many cases on the field where you can't follow this. Just use your best judgment. ==== General ==== # '''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 of course, if there are no o...")
 
No edit summary
 
(31 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Lessons Learned =
== Game Resources ==
== Drive Team ==
* [[Media:Frc2023-2024GameManual.pdf|Game Manual]]
=== Driver: Noah Fang ===
* [https://github.com/trc492/Frc2024Crescendo Code Repository]
==== DISCLAIMER ====
* [[Media:Frc2023-2024ImpactAward.pdf|Impact Award Essay]]
Nothing in this book is set in stone, FRC is constantly evolving and there are so many cases on the field where you can't follow this. Just use your best judgment.
* [[Media:Frc2023-2024_DCMPAwardsFlyers.pdf|Flyers]]
==== General ====
# '''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 of course, if there are no opposing robots nearby and it can help your alliance maybe go for it, but it is a case-by-case event.  
# '''AVOID SPINNING TOO MUCH:''' While spinning is cool and helps you avoid defenders; it slows down your velocity so don't spin if you don't need to.
# '''AVOID BREAKING WHAT DOESN'T NEED TO GET BROKEN:''' Try not to break things... It will 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, we have this to retract everything inside to avoid damage while traveling at high speed or cross-field. '''WHILE ON THE PRACTICE FIELD IT IS OK TO OVERCOMPENSATE TO AVOID DAMAGE BUT WHEN PLAYING MAKE SURE THIS IS NOT TOO DETRIMENTAL TO YOUR CYCLE TIMES.'''
==== Practicing ====
# '''EVERY ALLIANCE DRIVER STATION:''' You should know how to score in all possible goals from every driver station, not doing so will be detrimental to your performance as you don't get to choose driver stations until playoffs.
# '''PREPARE FOR THE WORST:''' You should be ready to fall back to the basics if your auto score fails or mechanism fails. You should know how to score manually or perform defense well.
# '''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. Practice that section. It will lead to the largest payoff during practice.
# '''PRACTICE MULTIPLE PATHS:''' When practicing by yourself, while it may be easy to just use the easiest path or scoring location, you don't get that luxury on the field. You're playing with 5 other robots using the same space, so try to vary pathing when running cycles.
# '''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.
==== Playing With Others ====
# '''DON'T INTERFERE:''' DO NOT, and I mean it, interfere with your alliance partners. This means blocking incoming robots or slowing them down. Sometimes this is unavoidable but try to make sure it rarely happens. This usually comes down to having a preset path that you follow.
# '''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. Vover Teleop pathing and define people's roles. And cover Endgame which means where they should be for what and when. GOOD STRATEGY CAN WIN MATCHES
==== Anti-defense ====
# '''SPIN:''' When going against an opponent who’s defending against you, the main thing is spin. Spin in the direction where you are essentially trying to “spin around your opponent” This reduces robot-to-robot contact and allows you to maneuver around them.
# '''USE PROTECTED ZONES:''' Use the protected zones, try to score and keep in them. But make sure not to sacrifice cycle time for safety, still try to score outside of them.


==== Defense ====
== Season Videos ==
# '''IDENTIFY CHOKE POINTS:''' Places where you know the robots will tend to funnel towards are your targets, these should be identified with the strategy person of your alliances before competitions.
=== Impact Award Video Submission ===
# '''GET BETWEEN THEM:''' Stay between them and their goal, try to copy movements.
<youtube>yo399jWPOkc</youtube>
# '''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.
 
# '''AVOID PROTECTED ZONES:''' Arguably the most important part where I see so many teams mess up, is not to touch or enter zones that are protected since you '''WILL''' receive the respective foul.
=== Pit Interview ===
# '''DON'T DEFEND AGAINST YOUR ALLIANCE PARTNERS:''' This is one of the worst things I've seen, if you are playing defense don't set it up in a way that you'll impede your owner alliance partners. Doing this repeatedly is a sure-fire way to land on a '''DO NOT PICK''' list.
<youtube>62sKZA0hP38&list=PLwES-SbpsnxwdIUbTTTtnTQixvvBjSe_w&index=40</youtube>
==== Other ====
 
# '''VISIBILITY:''' This might seem very nuanced but when choosing which side of your alliance driver station, MAKE SURE YOU HAVE VISIBILITY OF YOUR TARGETS. Priority is usually given to the driver, but it depends on who controls what and where.
== Season Recap ==
# '''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.
=== What Went Well? ===
==== Quotes ====
* Better team spirit
* '''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”''.
** We had signs, cheers, stickers/buttons/pokemon cards
  '''[Titan]''' We agree with the exception that we remain GP and the rules allow it.
** Better social media presence
* '''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.
* We had a strong summer (good training with lots of kids)
== Electrical Team ==
* Our participation in 2 off-season competitions gave lots of members good drive practice
=== Electrical Lead: Jackson Blunt ===
* We were able to kick off quickly into prototyping phase
== Mechanical Team ==
* Good mechanism ideas
=== Mechanical Lead: Noah Fang ===
** Implementation of amp thing went well
== Programming Team ==
** Our ability to do redesign is very good
=== Programming Lead: Anand Krishnan ===
* Our auto-assists were very organized
* We had good cross sub-team communication
* We finished a lot of our priorities list
* Match strategy went well
* Good setup for how we were going to play each match
* Better alliances this year
* Pit scouting setup was effective and detailed
* We had ASB window fundraising this year
* We applied for Impact Award which we haven’t done in a long time
* Handles for the robot were nice
* Rounded corners were helpful before robot inspection
* Open alliance was used more this year
=== What Did Not Go Well? ===
=== Mechanical ===
{| class="wikitable" style="margin:left"
|-
! style="text-align:left;"| Problems
! style="text-align:left;"| Solutions
|-
| '''Battery issues:''' Our battery got unplugged twice when we got hit. || Protect the battery from strenuous movement against hard hit.
|-
| '''Wires are too taut:''' Wires or connectors may pull out or break when robot got hit hard.
|
* Leave enough slack when wiring and strain relief the wire at the connectors.
* Secure connectors by screwing them down or hot gluing them.
|-
| '''Wiring maintainability:''' Connectors access may be blocked by fixtures. || Carefully plan the placement of the component and orientation so that the connectors are easily accessible.
|-
| '''Shooter Tilter is fragile:''' Shooter Tilter is often damaged when hit.
|
* Design a mechanism such that it is protected by the perimeter and within the robot bumpers.
* It's okay for a mechanism to extend outside the perimeter but ''Turtle Mode'' should bring it back inside the protective perimeter.
|-
| '''Shooter Tilter maintainability:''' Tilter was designed such that it's not easy to maintain. If the pulley breaks or skipped a tooth, it is not easy to fix. || Components should be design with maintainability in mind.
|-
| '''Radio/Ethernet Switch is not accessible:''' Radio/Ethernet switch block are placed and wired such that it's not easy to fix their wiring. || If it is unavoidable that a component is placed in a hard to access location, it should be designed so that it can be "taken out" easily to fix the wiring and put back.
|}

Latest revision as of 20:10, 28 April 2024

Game Resources

Season Videos

Impact Award Video Submission

Pit Interview

Season Recap

What Went Well?

  • Better team spirit
    • We had signs, cheers, stickers/buttons/pokemon cards
    • Better social media presence
  • We had a strong summer (good training with lots of kids)
  • Our participation in 2 off-season competitions gave lots of members good drive practice
  • We were able to kick off quickly into prototyping phase
  • Good mechanism ideas
    • Implementation of amp thing went well
    • Our ability to do redesign is very good
  • Our auto-assists were very organized
  • We had good cross sub-team communication
  • We finished a lot of our priorities list
  • Match strategy went well
  • Good setup for how we were going to play each match
  • Better alliances this year
  • Pit scouting setup was effective and detailed
  • We had ASB window fundraising this year
  • We applied for Impact Award which we haven’t done in a long time
  • Handles for the robot were nice
  • Rounded corners were helpful before robot inspection
  • Open alliance was used more this year

What Did Not Go Well?

Mechanical

Problems Solutions
Battery issues: Our battery got unplugged twice when we got hit. Protect the battery from strenuous movement against hard hit.
Wires are too taut: Wires or connectors may pull out or break when robot got hit hard.
  • Leave enough slack when wiring and strain relief the wire at the connectors.
  • Secure connectors by screwing them down or hot gluing them.
Wiring maintainability: Connectors access may be blocked by fixtures. Carefully plan the placement of the component and orientation so that the connectors are easily accessible.
Shooter Tilter is fragile: Shooter Tilter is often damaged when hit.
  • Design a mechanism such that it is protected by the perimeter and within the robot bumpers.
  • It's okay for a mechanism to extend outside the perimeter but Turtle Mode should bring it back inside the protective perimeter.
Shooter Tilter maintainability: Tilter was designed such that it's not easy to maintain. If the pulley breaks or skipped a tooth, it is not easy to fix. Components should be design with maintainability in mind.
Radio/Ethernet Switch is not accessible: Radio/Ethernet switch block are placed and wired such that it's not easy to fix their wiring. If it is unavoidable that a component is placed in a hard to access location, it should be designed so that it can be "taken out" easily to fix the wiring and put back.
Retrieved from "http://trcnet.asuscomm.com/mediawiki/index.php?title=FRC2023-2024:_Crescendo&oldid=400"