#Robotc wiki how to#

You have to describe the game? Doesn't everyone already all know what the game is? Well, the judges would like to see that a team not only understands the game, but that they have done some sort of systematic analysis of it: how to score points, how to de-score (if applicable), design restrictions, etc. The Design Award rubric states explicitly that it wants roles assigned in the вЂњResourcesвЂќ line-item:Дescribes the challenge at the beginning of the notebook with words and pictures and states the team's goals toward accomplishing that challenge Leaving some room for expansion at the bottom of each person's bio half-page is helpful. Having some fun here is allowed, and it is expected that team members will have multiple roles. This author's team uses regal titles-Building Queen, Cutting King, Programming Peon, etc. Teams can invent their own roles there's no pre-set list that must be used (вЂњbattery boyвЂќ wasВ one role mentioned by a Worlds Excellence Award winner). Judges want to see specific roles identified as a sign of project management capabilities and the team's use of its human resources. Even for very small teams, where every member is involved in most aspects of the robot, should have specified roles identified somewhere in the book. While not specified in the award criteria, many teams include some introduction pages introduction right at the start, with a group photo and description, followed by 1/2 page team-member bio-with-photo sections (age, school, interests).ДЄt the bottom of each team member's half-page, specify the team member's role(s). Teams using the REC-provided notebook, which is 3-hole punched, can put the engineering notebook in the 3-ring binder and submit it all that way. However, for some teams a bound book is not useful or doable given their meeting schedule or the number of people needing to work on the book at once.Д«ut what about stuff that doesn't really fit into a bound notebook, like computer code? Some teams also maintain a small 3-ring binder with that other stuff (including outreach efforts, code, and anything else that's many pages and/or not directly related to the design/build process) and rubber-band it to their notebook and submit both at tournaments. Why does the bound book get bonus points? It shows that the work was done by students over time printed materials in a 3-ring binder could be done by an вЂњover-helpingвЂќ adultВ for all the judges know, and could include retroactive additions which negates the spirit of a laboratory notebook recording daily work and observations.

As of 2017, the Design Award rubric can be found on the last 2 pages of the Awards Appendix. Some teams still find that the binder approach works better for their team, and will continue doing things that way, with the understanding that they will not get the 3 bonus points. In 2017 that phrase remains unchanged, but the Design Award Rubric now gives a 3-point bonus for a bound notebook in lieu of a 3-ring binder. The notebook should never be edited.вЂќ In the past, the вЂњpreferred formatвЂќ wording resulted in inconsistent interpretation by judges at different tournaments. The REC website says, вЂњA bound quad-ruled notebook is the preferred format. Veteran teams and coaches generally recommend using some sort of bound composition book. You are unlikely to beat out another team for one of these awards sans engineering notebook judges want to see your team's thought process, project management, testing, iterations, etc. The most obvious award relying on the notebook is the Design Award, but the Build, Create, Innovate, Amaze, and Think awards all rely on the notebook as well. If a team works hard and has some luck on their side, they can rack up tournament champion and skills champion bling however, all judged awards will expect to see a high-quality engineering notebook for your team to really even be in the running. For a robotics team, it also serves as a way to transfer information between team members if Person A did something last week, but isn't here today, and Person B is picking it up now.ДЇrom a trophy shelf-perspective, it's hard to win any trophies for saidВ shelf without an engineering notebook. It offers real-time debugging and a relatively simple set of internal libraries mostly based on the use of (real or virtual) arrays.Why do VEX teams need one? First, it's just a good idea that's why scientists and inventors throughout the ages have used them. RobotC is an interpreted C-like programming language available for the VEX PIC and VEX Cortex.

Robot C is for the older VEX Cortex which is no longer supported.