Club Expectations

What is Expected of our Student Members?

FEES

There is a $200 activity fee and a $50 club fee that accepted members are expected to pay.

All members are responsible for knowing the rules and strategies for the game.

MEETING DATES & ABSENCES

We meet every Tuesday & Thursday from 2:45PM - 5:00PM, unless otherwise noted. 

Please communicate any conflicts with us (ex: sports). We will try to find accommodations for your situation. However, depending on the situation and your performance in our club, it may impact your membership. 

Excused absences are permitted and will not impact your membership, but we still expect that members try to avoid absences. Only 3 unexcused absences are allowed during the season,

You can find the season schedule on our 2024-2025 calendar.

COMPETITIONS

VRC competitions consist of qualifying matches and playoffs, in which there are 2 teams of 2 alliances each. They are all day events, usually from 7:00 AM to 5:00 PM. At least 3 members of each team must be present at competitions, but it is highly recommended to have all members. 

There is also a skills competition where you are the only team on the field and try to score as many points as possible. At competitions, you must also submit a design notebook, filled with a detailed outline of your design process throughout the season at that point, as well as present it and your robot to a panel of judges.

This year, Neuqua Robotics is making an effort to attend more competitions if possible. We can’t register yet as most competitions are not set up on the RECF page until August - October.

COMMUNICATION

We will communicate through Google Classroom and Email. Please be vigilant and check both constantly to ensure you do not miss any important information. If we decide to add alternative forms of communication for ease of access, all members will be expected to join.

TRANSPORTATION

Robotics meetings will take place in H123 at BFC. We do not provide transportation from main to BFC. We are currently unsure if there will be school-provided transportation to and from competitions. As of now, teams will need to transport their robots to competitions, but we will make sure to update if there are any changes as we approach competitions.

ROLES & RESPONSIBILITIES

• Driver

  • The driver is responsible for maneuvering the robot at competitions. This implies that the driver must actively practice driving the robot throughout the season to be prepared for all competitions.

• Programmer

  • The primary language used is C++. However, we encourage anyone with programming experience (with any language) to apply. In this case, applicants are expected to learn the C++ skills needed. We do have resources to help with this. The programmer is responsible for coding the robot/user controls.

• Builder

  • The builder has to put the robot together. This role requires a lot of time and effort. The builder must work directly with the designer. It is preferred that applicants have some sort of engineering background.

• Designer

  • The designer is responsible for the blueprint and functionality of the robot. They are responsible for brainstorming designs, determining strategies, and planning accordingly. They must communicate their plans with the rest of the team, and acknowledge team members’ ideas.

• Notebooker

  • The notebooker is responsible for actively managing and updating the design notebook every meeting. This includes logging goals for the day, strategies, illustrations, and more. The notebooker must be actively involved in the overall robotic process.

If you have any questions, please feel free to reach out to Valeria Ramirez.