Add Robots 101 series

Author: raccube

_data/sidebar_tree.yaml

@@ -3,6 +3,19 @@
 tree:
   - url: /
     title: Introduction
+  - url: /robots_101
+    title: Robots 101
+    tree:
+      - url: /robots_101/post_kickstart
+        title: After Kickstart
+      - url: /robots_101/design
+        title: Design
+      - url: /robots_101/code
+        title: Code
+      - url: /robots_101/theming
+        title: Theming
+      - url: /robots_101/team_supervisor
+        title: Running a team
   - url: /kit/
     title: Kit
     tree:

robots_101/code.md

@@ -0,0 +1,74 @@
+---
+layout: page
+title: Robots 101 - The Code
+---
+
+Welcome to another blog post in our 101 series! Today, we're going to delve into
+the brains of your robot - its code.
+
+## Teamwork Makes The Code Work
+
+First and foremost, your robot's code should never be a one-person show. Make
+sure more than one person has access to the codebase and understands it. This is
+crucial for two reasons: First, if the primary coder is unavailable for any
+reason, others can step in and keep things moving. Second, multiple perspectives
+can identify potential issues and generate creative solutions that a single mind
+might overlook. Think of it as having a built-in code review process!
+
+## The Pulse of Your Robot - The Control Loop
+
+Your robot interacts with the environment in a continuous cycle of sensing and
+acting. It's essential to have a solid control loop in your code where your
+robot senses its environment and then decides what to do next based on that
+information. This loop should be at the core of your robot's operation, allowing
+it to adapt and react to its surroundings.
+
+## Backup Your Code: The Magic of Version Control Systems
+
+Mistakes and accidents happen, files get lost, and computers crash. To protect
+your work from these unpredictable events, ensure you regularly back up your
+code. Better yet, use a Version Control System (VCS) like Git with GitHub. A VCS not only
+provides a backup of your code but also tracks changes, making it easy to
+identify when and where things might have gone wrong or right!
+
+## The Six T's: Test, Test, Test, Test, Test, Test!
+
+If there's one golden rule in the world of coding, it's this: test your code.
+Then, test it again, and keep testing! You can utilise our web interface to help
+you quickly iterate on your robot, by live streaming the logs and viewing
+the last captured image. You can also use the web interface to stop and
+restart the execution of your code. The more robust your testing, the
+more reliable your robot will be when it counts!
+
+## The Benefits of Friendly Competition
+
+If you have a large enough team, consider developing competing implementations
+of certain features or systems. This can be an effective way to explore
+different solutions and spark innovation. You can then choose the best elements
+from each, or select the most efficient solution overall.
+
+## Embrace Imperfections: Sensor Noise
+
+It's crucial to remember that real-world data is often noisy and imperfect.
+Your sensors may pick up interference, or there could be slight variations in
+readings. Your code should be robust enough to handle this noise and still make
+effective decisions. Techniques such as sensor fusion or filtering (like
+taking an average of multiple readings) can be highly beneficial here.
+
+## The Power of Documentation
+
+Our [Docs](https://studentrobotics.org/docs) are a goldmine of knowledge and
+should be your first port of call whenever you're unsure about something. Much
+like a good textbook or reference guide, our Docs are designed to support you in
+understanding your robot better. From getting started with your robot kit, to
+understanding the APIs, to troubleshooting common issues; the Docs cover a broad
+spectrum of topics you may encounter.
+
+<br/>
+
+Coding your robot can be a challenging yet rewarding experience. It's where the
+magic happens, where the inert pieces of metal, wood, and circuitry come to life
+and engage with the world. We hope these tips and strategies will help you avoid
+common pitfalls and pave the way for your success in the Student Robotics
+competition. Remember, every stumble is an opportunity to learn and improve.
+Keep coding, keep testing, and most importantly, have fun!

robots_101/design.md

@@ -0,0 +1,38 @@
+---
+layout: page
+title: Robots 101 - Robot Design
+---
+
+Welcome back to our Robots 101 series! This time we will be looking at what you need to consider when designing a robot that is both practical for the game’s task and one that would fit our safety regulations.
+
+The aim of this post is to give you a jumping off point rather than prescribe the best way to tackle Student Robotics. There will be things we've missed and may even be things that are not relevant to your specific team. Over the years teams have tackled the competition in all sorts of ways we never imagined. Please do experiment and come up with the best way for your team to work.
+
+## Strategy
+
+Before settling on a final design, it’s a good idea to devise several different strategies. Making a scale plan or model of the arena, tokens, and robots is a very good way to start thinking about these and can aid discussion. Be sure to document the pros and cons of each strategy. Include point scoring, ease of implementation, additional items required to implement the strategy, and possible interactions with other robots.
+
+Narrow the list and prototype some hardware (can be simple) to assess feasibility. The most complex, technologically advanced strategy is not necessarily the best. A simple (and elegant) strategy is more straightforward, quicker to implement and less likely to fail. On many occasions, a simple strategy has won the day.
+
+## Movement
+
+How your robot will move is a key decision to make. Many options are available, and all have pros and cons: wheels, tracks, or legs, 2, 3 or 4-wheel drive, omniwheels etc. Types of motor: DC, geared, stepper motors, built-in or add-on encoders. You should research these methods and decide what will be best for your strategy. The ability to move a defined distance and/or rotate a specified number of degrees can be helpful.
+
+## Construction
+
+The construction of your robot will be strongly influenced by the movement system you have decided upon. When planning the construction of your robot, a few things would be good to think about: the strength of your robot, how heavy it will be, the ease of modification or repairs, do you have sufficient ground clearance, is the robot protected from impacts, etc.
+
+Note that the maximum dimensions of the robot are clearly defined in the rules. These are strictly adhered to and robots must comply or will not be allowed to compete.
+
+## Location of components
+
+The power board has an ON/OFF and a START button. Both of these can be wired to remote switches if desired. The ON/OFF switch (remote or on the power board) must be easily accessible, clearly marked and visible. All the boards have LEDs on them that can provide valuable information for debugging.
+
+The battery must be protected from mechanical damage on all sides. Failure to comply will result in disqualification. Having your battery easily accessible will make your life easier.
+
+Two USB ports must be easily accessible to allow insertion of your code USB stick and the competition USB stick that will be provided by us for competition matches. Keep all wiring neat, tidy, well secured and away from all moving parts. Clearly labelling your components and wires is advisable. Ensure that you comply with the rules and safety regulations concerning wire colours.
+
+## Implementation
+
+The process of building a robot is an iterative one. You may need to rethink and refine your strategies and return to earlier points in the process. Prototype and test to assess the feasibility of mechanical and software strategies. Test, test, test, test, test, test, test.
+
+If something occasionally doesn’t perform as expected, be wary of ignoring it on the basis that it was a “glitch”, “one-off”, “it hasn’t happened again”. Often it will happen again and probably during the knockout stages of the competition! Investigate, identify and rectify.

robots_101/post_kickstart.md

@@ -0,0 +1,25 @@
+---
+layout: page
+title: Robots 101 - Kickstarted, now what?
+---
+
+Welcome to the start of Robot 101, our series where we guide you through the competition and give some advice on your next steps.
+
+So, you attended our kickstart event and are now ready to build your robot! But where should you start? We’re here to help!
+
+We’ve found that most teams split up the different parts of the robot between them. It’s a good idea to meet up and discuss which tasks each person wants to accomplish and give each other roles inside the team. Of course, these can change throughout the time between kickstart and competition, but make sure everyone has a job to do. It’s important to make sure there's always at least two or three people that can do each task type. Don’t forget tasks outside the robot itself either, like project management, running the social media, or theming.
+
+Take some time together to plan your strategy for the game: how are you going to tackle the problem? What equipment would you want to experiment with? Remember to consider all areas of the robot - design, code, and mechanics. For some ideas, have a look on our [YouTube channel][youtube] to see some robots from previous competitions.
+
+Each member should also spend some time getting to know the docs on our website. This contains important information about the game’s rules, an introduction to your kit, as well as tips on how to program your robot. Your team supervisor will have been sent your invite link and password for our [Discord Server][discord-docs] - this is the best place to ask questions to the Blueshirts. Don’t be afraid to ask for help! Our volunteers have years of experience and are there to help you. You can also get your team supervisor to contact us through our email if you prefer.
+
+Remember, you’re not just aiming to win First, Second, or Third! There are plenty of other awards in place for you to achieve throughout the year. For example, our “Teams on the Web” runs from now until the end of the competition - make sure you’re posting your progress on social media to be in the running! Check out the Rules for a full list of all the awards on offer.
+
+As part of your team, you’ll have a trusted adult who is acting as supervisor - their job is to guide you through the process of building your robot, not build it for you! We have a separate [blog post on the role of a supervisor][one-oh-one-supervisor].
+
+Hopefully this has given you some jumping off points to begin your journey to the competition. Check back soon for our next entry in this series, all about how to design your robot!
+
+[youtube]: https://youtube.com/user/StudentRobotics
+[discord-docs]: https://studentrobotics.org/docs/team_admin/discord
+<!-- cspell:disable-next-line -->
+[one-oh-one-supervisor]: {{ '/blog/2022-10-07-101-so-youre-a-team-supervisor' | prepend: site.baseurl }}

robots_101/team_supervisor.md

@@ -0,0 +1,38 @@
+---
+layout: page
+title: Robots 101 - So you're running a team
+---
+
+So, you’re running a team. Here’s a little bit of info on what to expect from Student Robotics, and your responsibilities as a team supervisor.
+
+As a team supervisor, your role is to guide the competitors through the journey of building a robot. You’ll be there to point them in the right direction when they get stuck and resolve any issues they run into. We encourage team supervisors to limit their involvement with the robot design/building process so that the finished contraptions are 100% student-built which competitors find very rewarding.
+
+You’ll be our point of contact with the team. If you have any questions during the year, just email [[email protected]](mailto:[email protected]). We’ll also be sending you emails every month or so with important information such as:
+- Details of Tech Days where we provide a space for teams to come together and get direct help from our dedicated volunteers
+- Software updates for our kit
+- Information about the competition in April
+
+We aim to host our Kickstart event and Tech Days in multiple locations to make it more convenient for you to travel. However, you will still need to arrange to travel to these places.
+This is especially important to book for the competition, as you will likely need to arrange to stay overnight near the venue.
+
+Our kit includes a battery and a few boards to get your robot started. However, your team will need additional components and materials from which to build their robot. For the chassis, your team has several options. Teams often use cardboard, MDF, Aluminium, and/or Acrylic. In terms of electronic components, teams often make use of:
+- At least two 12v motors (our kit supports four)
+- A few servo motors
+- A few microswitches for detecting if you bump into something
+- Ultrasound sensor
+- Wheels & bearings
+
+Be sure to plan with your team what your robot will need before you make any purchases as depending on your robot design you may need more or less of these components.
+
+Popular suppliers of these components are:
+- [Robot Shop](https://www.robotshop.com/)
+- [RS](https://uk.rs-online.com/web/)
+- [Farnell](https://uk.farnell.com/)
+- [Amazon](https://www.amazon.co.uk/)
+- [eBay](https://www.ebay.co.uk/)
+
+To allow you and your team to ask us questions directly, as well as share what they’re working on with other teams, we provide a Discord server. You will receive a unique link to share with your team so that you can all join with your own Discord accounts. Each team gets a private text channel for direct support from us which can be used to discuss your robot without worrying about giving other teams your strategy. We also have a team-supervisor only channel for any questions you may have. There are also some text channels where teams can communicate with each other (and us!) for more general topics. If you’d like a voice channel for your team, just email us! You can find more information in [our docs](https://studentrobotics.org/docs/team_admin/discord).
+
+If you’d like additional support throughout the year, we have dedicated mentors who can regularly join your team meetings either in-person or remotely. Your mentor will help guide your team towards good solutions for their robot, provide assistance where they might need it as well as help them understand the kit, the rules and the competition as a whole. We *strongly* encourage new teams to sign up for mentoring. If this sounds like something you’d like, look out for our email shortly after Kickstart.
+
+Best of luck this year, and don’t forget we’re always happy to help!

robots_101/theming.md

@@ -0,0 +1,48 @@
+---
+layout: page
+title: Robots 101 - Theming
+---
+
+Welcome (back) to the Robots 101 series! This time, we’re addressing theming
+your robot.
+
+Theming your robot might not seem important at first, but having consistency
+between your robot, your team and social media goes a long way to delivering a
+strong message that your team is fully committed to the competition. Plus, those
+who may want to get involved in the team, but don’t want to build or code, still
+have an opportunity to leave a mark on your robot. Having a solid design for the
+outside of your robot before starting the rest of the process may even help your
+decision on how to tackle the event!
+
+Step one is the planning phase. Get your team together to discuss general titles
+for your theme. Whether it’s cyberpunk or gothic, nothing should be written off
+immediately in this process. Give everyone the chance to share their ideas
+before deciding on a few “final” ideas. At this point, you could start finding
+images that visualise your theme and begin collating them. You may find the most
+popular theme may not work at this point - and that’s ok!
+
+Next, you could try and create some concepts of how your robot and team mates
+would look at the competition. This is done best when each visualisation is
+unique, so that merging parts of each design together to create a final product
+is easier down the line. You could try using materials that your team already
+has on hand to make a prototype shell of your robot, or using basic wardrobe
+items to block out clothing choices.
+
+Remember, your team’s theme will likely develop throughout the building process
+as you come up with new ways to tackle the competition. Let this happen! Being
+rigid in your design process will almost certainly cause issues later down the
+line. By the time your team gets to the final competition you’ll have a unique
+style to your robot, your competitors and your socials.
+
+To give you some ideas, we've included some photos of teams we think did
+particularly well at previous competitions.
+
+<img src="/images/content/blog/robots-101/sr2022-hrs-team-photo.png" alt="2022 - HRS: Hills Road's “Ducktor Who” As well as theming their robot, small rubber ducks were placed around the event, as well as given to other teams." />
+
+<img src="/images/content/blog/robots-101/sr2019-hab-team-photo.png" alt=" 2019 - HAB: Haberdashers’ Aske’s Boys’ School won the Robot and Team Image award with their Hawaiian theme. This was complimented with inflatable palm trees and a 3D paper pineapple on top of their robot." />
+
+<img src="/images/content/blog/robots-101/sr2016-mai-team-photo.png" alt="2016 - MAI: ‘Measure, Analyze, Improve’ from Gymnasium Markt Indersdorf, who came all the way from Germany looking very Frankenstein-esque, wearing their bio-hazard suits and zombie face paints. Their robot was a rotten-fleshy-green colour with a brain exposed." />
+
+<img src="/images/content/blog/robots-101/sr2015-mai-team-photo.png" alt="2015 - MAI: “42 * 2 - Double Vision” from Gymnasium Markt Indersdorf, came dressed as monks in hooded brown robes, laced with glowing LED strips." />
+
+<img src="/images/content/blog/robots-101/sr2014-hrs-team-photo.png" alt="2014 - HRS: Systemetric (HRS) impressed the judges with their steampunk costumes and brass and mahogany robot (pictured)." />