2012 MAR Rutgers University District

[Gizmo4]

Originally Posted by Mike8519

I have not heard anything about this, perhaps there is some slight confusion.
You get 6 hours per event, but those 6 hours must be used in the 7 days preceding each event. So while you do get 12 hours total, they are separate time blocks.

I tried to tell my coach that, but he said he got some sort of (team update?) e-mail 'that some teams complained about the length of build time during 2 day events' and it was extended to 12 hours of Robot access time during the week of the competition. Has anyone else heard of this email? I dont want our team to get disqualified just for having an extra 6 hours on our robot bag and tag form.

[George A.]

Originally Posted by Gizmo4

I tried to tell my coach that, but he said he got some sort of (team update?) e-mail 'that some teams complained about the length of build time during 2 day events' and it was extended to 12 hours of Robot access time during the week of the competition. Has anyone else heard of this email? I dont want our team to get disqualified just for having an extra 6 hours on our robot bag and tag form.

While I haven't heard one way or the other about the email your mentor is referencing, politely (and respectfully) ask him to print it out. If he can't remember where he saw it or can't find it again, I would STRONGLY suggest erring on the side of caution and NOT working on it for more than 6 hours. LIke you said, you would hate to be ruled ineligible because you worked on it for more than 6 hours.

Another route would be the FIRST Q&A forum and see if you can get an official response there.

Either way best of luck!

[Gizmo4]

He showed me the e-mail, and it basically was reminding teams about everything in 5.7 , 5.71, and 5.72 in the Robot Transportation section of the manual. Have ANY other MAR (Mid Atlantic Robotics) teams heard of or can confirm that we get an additional 6 hours after using the already given 6 hours in the week prior to a single event? Which would be 12 hours of taking the robot out of the bag.
Will our rookie team get disqualified and not allowed to compete if it turns out those extra 6 hours of taking the robot out of the bag were not allowed? Would hate it if we were kicked out because of that.

[George A.]

Originally Posted by Gizmo4

He showed me the e-mail, and it basically was reminding teams about everything in 5.7 , 5.71, and 5.72 in the Robot Transportation section of the manual. Have ANY other MAR (Mid Atlantic Robotics) teams heard of or can confirm that we get an additional 6 hours after using the already given 6 hours in the week prior to a single event? Which would be 12 hours of taking the robot out of the bag.
Will our rookie team get disqualified and not allowed to compete if it turns out those extra 6 hours of taking the robot out of the bag were not allowed? Would hate it if we were kicked out because of that.

Your best bet? Call FIRST on Monday morning and ask them directly. They would be able to definitively give you an answer. Up until then I would recommend not doing any more than your 6 hours. I can't confirm that you'll be DQ'ed, but I can guarantee that if you did more than your allotted hours, there WILL be ramifications that won't be too pleasant.

[Dad1279]

5.7.2 'Robot Access Period' - Schedule

Teams may unlock their robot for a total of 6 hours during the 7-day period preceding any two-day event in which their team will be competing with their robot. The 6 hours may be broken up in any way the team wishes, with the exception that no single access period may be shorter than two hours. The robot must be locked up in between sessions and this must be documented on the Robot Lock-Up Form each time.


You only get 6 hours. Don't open it for 12.

[kinganu123]

We just came back from Hatboro-Horsham.
You have the 6 hours to open the robot at your school or where ever you usually work in two hour blocks. After that, when you go to Rutgers (I believe Thursday afternoon for inspections and practice matches), you'll be allowed to open it up once again and keep it open for the remainder of the competition.

[Deetman]

A few tips from Hatboro-Horsham:

• Get inspected as early as you can on Day 0 (Thursday). This makes the "compressed" district time schedule much less stressful the morning of Day 1. This weekend I do not believe they were letting teams go to scheduled practice matches Friday morning unless they were fully inspected. Thursday practice matches required the first "practice" to be a safety inspection and subsequent practices required full inspection. If for whatever reason you can't get completely inspected Thursday, get as much of a partial inspection done to save yourself and the inspectors time Friday morning.
• If at all possible arrive on Day 0 at or before the opening time. This gives you quite a bit of time with the robot unbagged for work, inspection, and practice. For Hatboro-Horsham the pits were open from 4PM to 10PM.
• There will probably be a small practice field at the event. Utilize it early and often to calibrate, check functionality, etc. Hatboro-Horsham had a real bridge and a real barrier. There are significant differences in both of these that the low cost wood versions do not accurately represent. In general, the bridge is more difficult to tip and the barrier is at the proper height and the corners have a radius. We had difficulty with the wood barrier, but had absolutely no problems with the field barrier.
• VERY IMPORTANT: MAKE SURE AN INSPECTOR IS PRESENT WHEN YOU UNBAG AFTER ARRIVAL!
• Ask for help if you need it. Teams are super helpful and day 0 seemed to be slightly lower stress than day 1 at the older regional formats.

[DonRotolo]

Originally Posted by kinganu123

when you go to Rutgers (I believe Thursday afternoon

Originally Posted by Deetman

Get inspected as early as you can on Day 0 (Thursday).

Minor correction: FRIDAY is load-in, pit setup and inspection at Rutgers, and Saturday & Sunday are competition days.

Show up on Thursday and you'll be disappointed

[thedries]

For anyone attending the Rutgers district:

Have an old iPod sitting around, collecting dust? Get a fancy new phone and don't use your iPod anymore? Well put it to good use!

The non-profit organization Music and Memory needs donations of new or used iPods for the treatment of Alzheimer's patients. They personalize each playlist to the individual, finding out about their history and family to develop a mix of music to connect to their past. The results are astounding; patients light up and come back to life.

Team 11, MORT, has partnered with Music and Memory to spread the success to even further. We will be collecting iPods at all of the competitions we're attending, including Rutgers, and hope to teach Music and Memory what Gracious Professionalism is all about. Please see us in our pits if you wish to donate.

For more information please visit http://mort11.org/music and http://musicandmemory.org for more information, including videos showing this amazing transformation.

[Horsegirrl]

Can't wait to see everyone at my lovely university Rutgers!


Katie Stevens

[flyingcrayons]

ah i'm mad that this event takes place right as spring break starts.. i live at Rutgers so normally i could just take a bus but now i'm gonna have to drive up from my house.

oh well it'll be worth it

[Dripto]

A couple of us 694 guys will be coming down to watch on Sunday, looks like it's gonna be a fun time!

[rdlevy1215]

Webcast Info:
I will be providing the webcast for this MAR event, on behalf of Team 1676. The webcast will be viewable starting Friday afternoon at www.team1676.com

[Hallry]

The webcast is now live at team1676.com!

[TD912]

Hi guys! I was watching the webcast today. Seemed a bit stuttery at first, but worked fine later on.

Anybody know where I can get match scores and rankings so far? It seems FIRST's website is giving me a 404 error, and The Blue Alliance isn't updated, probably because they gather data from FIRST's site.

https://my.usfirst.org/myarea/index....CA1CpIyj183FBF
Click Match Results/Standings/Awards on the above page, and you get an error.