Agenda

Prelimary Agenda - this page will be updated two weeks prior to the event.

Saturday:

7:00 AM - Check in Opens
7:30 AM - Technical Inspection Opens
8:30 AM - Check in Closes (All teams not checked in will be dropped from the schedule)
8:30 AM - Opening Ceremonies and Drivers Meeting
9:00 AM - 5:00 PM  Qualifying Matches and Skills runs

Sunday:

8:30 AM - Opening Ceremonies and Drivers Meeting
9:00 AM - 2:00 PM  Qualifying Matches and Skills runs
2:00 PM - Skills field closes
2:30 PM - Alliance Selection / Elimination Rounds
4:00 PM End of Awards

Volunteer

Please fill out our online volunteer sign up sheet once it is posted on this page.

https://www.signupgenius.com/go/60b084fadad23a5fc1-sneregional#/

We will contact you before the event with more details.

Emergency/Bad Weather Policy

If there is a building closure, it will be posted on the school website http://www.framingham.k12.ma.us/Domain/15

Our makeup date  is March 11-12, 2023.

Refund Policy

No refunds will be made after Registration closes  unless the event has been cancelled and can not be made up on the designated makeup date..

Teams with unpaid balances on RobotEvents.com will be placed on the waitlist one week prior to event, unless they have made payment arrangements with the Event Partner.

Refunds will be issued within two months after event date.

Health and Safety Policies

Health Advisory

• Please stay home if you are not feeling well;

• Wash your hands frequently;

• Maintain physical distance as much as possible.

Webcast

Event streams will be posted here: https://www.youtube.com/@walshbot9214/streams

Judging Format

Hi Teams,

My name is Greg Caswell and I am the Judge Advisor for the Southern New England High School VRC Championship. As we approach the event and the engineering notebook submission deadline (Tuesday, February 21st at 11:59 PM) I wanted to make few comments, suggestions, and requests about your teams' notebooks and a request about the THINK Award.

NOTEBOOKS
First, and perhaps most important, as the season has gone on we have been seeing more and more scanned copies of notebooks that haven't been updated since the fall. Having your notebook end in mid-December for an early January event is fine, but as we get further and further in time from that last entry, it's harder and harder to accurately assess a team's design process and to understand what has happened since that last entry. If a team has not done any more work on their robot, then that's all there should be, but I generally refuse to believe that most VRC teams are not working on their robots through January and February and that none of that work has been recorded. So, please make sure that the digital notebook file has all of the pages that the team has done and then make sure that the URL in RobotEvents is pointing to the most up-to-date version of the notebook.

Second, an organizational request, please have your team number as part of the filename of the document. And then again, somewhere on the first page, please list your team number - this is especially helpful for scanned notebooks.

Third, if you have a paper copy of your notebook, please bring it to the Regional Championship. While only notebooks that are digitally submitted will be scored on the Engineering Notebook rubric and only those teams and notebooks will be eligible for the Design, Innovate, and Excellence awards, we do appreciate the ability to look through notebooks at the event, during lunches, and deliberations. It can also help jog our memories for the many other awards at the event based on things we had read about or a team told us in person. We will also have the digital copies at the event, but sometimes the paper one is helpful. Bringing a physical copy of a notebook to the event is NOT a requirement for any award.

— —     

THINK AWARD
Like last year, we will be seeking a code submission and a write-up ahead of the event to help us judge the Think Award. This was successful last year and really helped the judge team get a sense of teams' programming and to identify teams for additional programming specific interviews at the event. Like the digital notebook submission, this allows the judges to spend more time with something that can be hard to judge at an event. These code submissions will also allow judges who have expertise in computer science to more thoroughly examine programming techniques and design.

What we would like you to submit:
Link to PDF of code - Please submit a link to a PDF that contains a _portion_ of the code for your robot. That PDF should also include a description of what it does. You may also want to check out the judge's guide to see what the criteria for this award are.
Code summary - We don't want to see every line of code for your robot, but are interested in parts that are interesting, well done, and/or play a large role in your success. So keep it concise.
File Name Format - The PDF you submit should have the team's number (WITH LETTER!) in its title. The PDF itself, should also state the team's number (WITH LETTER).
Do NOT submit the actual code file.
Please make sure that the PDF is publicly accessible, so that any of our judges may view it.
Due date - Please submit your PDF by 11:59PM Monday, February 27th. Submit here: https://forms.gle/MRuGczJaqqmC22Xr8

— —     

Thanks,
Greg Caswell