|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: [FRC Blog] FIRST Robotics Competition Registration Update
That's easily solvable by determining which event is a team's "local" regional ahead of time. The simplest way would be to determine which event is closest to each team and call that local. If, at that point, you have more teams than spots for that event, spots could be assigned randomly for every team that hadn't opted to try for a different event instead. The unlucky teams would then have to go to their second choice.
|
|
#2
|
||||
|
||||
|
Re: [FRC Blog] FIRST Robotics Competition Registration Update
Quote:
|
|
#3
|
||||
|
||||
|
Re: [FRC Blog] FIRST Robotics Competition Registration Update
Quote:
|
|
#4
|
||||
|
||||
|
Re: [FRC Blog] FIRST Robotics Competition Registration Update
Quote:
Due to the wonky way home events were chosen (by FIRST), the event we were listed as "home" for us was actually further away from us than the one we wanted to compete at. We opted out and then signed up for the closer event the 2nd registration. (FIRST chose home events based on zip codes or something and not by actual distance.... they would not change it when we requested it before registration) It worked out for us... it simply gives a team the best chance at the district event that is closest to them. They don't have to take it. In this way, a team is never frozen out of the local district event. |
|
#5
|
||||
|
||||
|
Re: [FRC Blog] FIRST Robotics Competition Registration Update
Quote:
Another curious thing is that the Alaskan team's home event is Wilsonville. While we'd love to see them in Wilsonville, it's about as far away from them as you can get without leaving the district. And I've heard a rumor that they've already made arrangements to stay in Seattle for a couple of weeks to compete, so if they choose to opt out it should not be a surprise to anyone. |
|
#6
|
|||
|
|||
|
Re: [FRC Blog] FIRST Robotics Competition Registration Update
Something interesting to note, 3 teams have somehow been signed up for events already.
https://www.thebluealliance.com/team/6319 https://www.thebluealliance.com/team/6320 https://www.thebluealliance.com/team/6321 I assume these are just for testing, but if you look on the firstinspires team list, a few rookie team numbers have been handed out as well. |
|
#7
|
||||
|
||||
|
Re: [FRC Blog] FIRST Robotics Competition Registration Update
Quote:
![]() |
|
#8
|
|||
|
|||
|
Re: [FRC Blog] FIRST Robotics Competition Registration Update
Quote:
Week 1: http://www.thebluealliance.com/team/4075/2017 - Palmetto http://www.thebluealliance.com/team/558/2017 - NE District - Waterbury http://www.thebluealliance.com/team/2363/2017 - CHS District - Northern Virginia Week 2: http://www.thebluealliance.com/team/648/2017 - St. Louis Regional http://www.thebluealliance.com/team/1288/2017 - St. Louis Regional Week 3: http://www.thebluealliance.com/team/1743/2017 - Greater Pittsburgh Regional http://www.thebluealliance.com/team/3492/2017 - Greater Pittsburgh Regional >a few rookie team numbers have been handed out I'm intrigued by the 4 rookies in the same town in Guam. Last edited by Christopher149 : 03-10-2016 at 11:38. |
|
#9
|
||||
|
||||
|
Re: [FRC Blog] FIRST Robotics Competition Registration Update
Quote:
My understanding is that there was a brief glitch where registration was open at the end of last week, a few curious people poked around the system, and FIRST re-closed registration and deleted all of their signups. |
|
#10
|
|||||
|
|||||
|
Re: [FRC Blog] FIRST Robotics Competition Registration Update
Great job once again GuamFIRST!
![]() Last edited by Nate Laverdure : 03-10-2016 at 12:44. |
|
#11
|
||||
|
||||
|
Re: [FRC Blog] FIRST Robotics Competition Registration Update
~I already signed up for Crowd Control~
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|