|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Registration 2017
Has this been suggested already?
Why the heck can't we submit a ranked list, and have the machine choose who gets where based on their chosen priority and a random draw? You could even do it in multiple draws if you want to give teams the chance to adjust their second decision based on the results of their first result. We already do this for FIRST choice, and it works perfectly well. What use is forcing people to all click refresh at the same time when we already have an alternative system that is easier on mentors' time and server load? |
|
#2
|
||||
|
||||
|
Re: Registration 2017
Quote:
|
|
#3
|
|||
|
|||
|
Re: Registration 2017
fixed 1 event teams get first choice.
|
|
#4
|
||||
|
||||
|
Re: Registration 2017
Why? How is it more fair to give an event to teams that click on it quickest instead of randomly splitting the spots amongst the teams that prioritize it most?
Last edited by nuclearnerd : 22-09-2016 at 15:13. |
|
#5
|
||||
|
||||
|
Re: Registration 2017
Quote:
However, I am not sure submitting a ranked list is what I would want either. Getting an event you want involves so much preparation and planning weeks in advance and afterwards. It can also be quite costly not getting the event you want, especially for a team like us having to fly to events. If we sign up for an East Coast event Week 1, our next event choice priority would be to find something else as close as possible. Someone from our team asked why not do San Francisco Week 3 next? Biggest hurdle is an extra 3-4k shipping cost to get it there. FIRST donates 2 airbills per year to us. We use it to get our robot to the US mainland, and then back to Hawaii for our event later during competition season. Last edited by waialua359 : 22-09-2016 at 15:22. |
|
#6
|
||||
|
||||
|
Re: Registration 2017
Faith in FIRST restored (not)
|
|
#7
|
||||
|
||||
|
Re: Registration 2017
Quote:
Granted, any system is still going to need some leeway for the regional directors and reserve capacity slots. Hopefully reserve slots accommodate those single event teams, regardless of what system is used for registration. |
|
#8
|
||||
|
||||
|
Re: Registration 2017
Forgive me, but I don't understand the objection. Wouldn't ranking "East Coast Event" first, "close events" second through whatever capture your intent? You could adjust your priority list for the second draw after learning the results of the first.
|
|
#9
|
||||
|
||||
|
Re: Registration 2017
Quote:
Based on the current system in the past, it has allowed me to pick and choose what I want, cancel when I want, and then repick somewhere else. The suggested system puts everyone on the same time block for preferences vs. on the fly in trying to secure a spot at an event. Having the ability to choose, based on the number of remaining slots available is a strategy to try and ensure you get all of the package of events you want to participate in. |
|
#10
|
||||
|
||||
|
Re: Registration 2017
I would like to see a system where each team submitted a first and a second choice or just a first choice. Try to give as many teams as possible their first choices, using a lottery or auction model, whatever seems appropriate. This would allow regional directors to use some of the slots that are held back to place teams earlier. (Ex: If there are 10 slots held for late registering rookies and nearby teams, and four nearby teams were unlucky and didn't get one of the open slots, they could get one of the reserved slots.) Give teams their second choice if possible and they selected a second choice. This would allow teams to submit a ballot by the given date, and the system could spit out the results. A little work by the people at HQ and the regional directors and they publish a list of who got their slots where.
Then a few days later let all of the teams that have not yet registered for a competition resubmit a request for one of the still available slots. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|