28 03 FTC @ Shropshire - Brighton-FTC/FTC-2023 GitHub Wiki

Please read these tips thoroughly for the Shropshire Trip on Tuesday 28/03. I've tried to keep them brief, and I hope they will help.

• Don't have multiple programmers working on the same code at once
• Test your code on the robot whenever you can. If a feature hasn't been tested, you can assume it doesn't work. There should be a practise pitch available to test the robot on, and before the matches start you can probably test on the playing fields.
• Test early in the day; tell engineers potential issues with the code early.
  • The lift motor may be too stiff for Team 1 - please test this early.

• Talk to strategists and prioritise tasks with low chances of failure and high rewards.
• Don't create new features on the day of the competition.
• One exception - If you are free of any tasks (including programming and testing), you may take safe gambles with new features, as long as you are not too committed to them and will readily switch to a more important task if needed.
• Have a simple plan B in case your ideal plans run into bugs.
  • If you can't identify the signal sleeve in autonomous, always go to the same zone (probably 2) as it will earn us 33% of the points on average.
  • If you can't estimate your position on the pitch, it is fine to set your motor powers for a set amount of time manually in an autonomous OpMode (using set powers + sleep). This technique is also valid for the arm, etc.

• Read and complete these before the competition so you don't have to take up valuable time on the day:
  • Game Summary - please refresh yourself on the general layout of the game.
  • Git merging between branches - please keep in your workspaces before the day, then merge them to main and switch GitHub desktop to the main branch on the day of the competition. If you don't know how to switch branches on GitHub desktop, a description link is here.

• Unfortunately, @la-reine-c is in hospital at the moment, so will not be able to complete any tasks. I have reassigned his tasks to others, so please check on the Project to see if you need to complete any more tasks.
• I (@WebCoder49) will be present but will let you manage and program the robot unless there is an emergency. Otherwise, I will be completing revision.

To let me know that you have read this, please write a comment to this issue. Please also use this to give any questions you may have.