|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#16
|
|||||
|
|||||
|
Re: Boiler Bot Battle Sept 2016
Current Team List as of 8/31
45 Technokats Kokomo, IN 135 Penn Robotics Mishawaka, IN 234 Cyber Blue Indianapolis, IN 292 PantherTech Russiaville, IN 461 Westside Boiler Invasion West Lafayette, IN 1646 Precision Guessworks Lafayette, IN 1739 Chicago Knights Chicago, IL 1747 Harrison Boiler Robotics West Lafayette, IN 2781 RoboPride Burbank, IL 4926 GalacTech Columbus, IN I know a few of our local teams are still planning on signing up as well. Last edited by Peyton Yeung : 08-31-2016 at 10:50 AM. |
|
#17
|
|||||
|
|||||
|
Re: Boiler Bot Battle Sept 2016
The registration date cutoff for Boiler Bot Battle is officially 11:59 pm on Saturday, September 10th. We have travel grant funding available for teams and the information for that is at our website under the travel tab.
Teams may also bring and compete with practice robots if they like at no extra cost. |
|
#18
|
||||
|
||||
|
Re: Boiler Bot Battle Sept 2016
Could I ask that we get an updated list of teams?
|
|
#19
|
||||
|
||||
|
Re: Boiler Bot Battle Sept 2016
Any idea on how many teams will be there? Will we be running 3 team alliances no matter what(even if there are only 14 teams)? Thanks.
|
|
#20
|
|||||
|
|||||
|
Re: Boiler Bot Battle Sept 2016
Current Team List as of 9/8/16
1.) 45 2.) 45b(Practice bot) I believe 3.) 135 4.) 234 5.) 9234(Practice bot) 7.) 292 8.) 461 9.) 4611(New Robot) 10.) 1646 11.) 1739 12.) 1747 13.) 2781 14.) 3940 15.) 4103 16.) 4272 17.) 4926 Practice/2nd bots are still okay since we haven't hit the event maximum yet. Last edited by Peyton Yeung : 09-15-2016 at 09:38 AM. |
|
#21
|
||||
|
||||
|
Re: Boiler Bot Battle Sept 2016
So how will eliminations work with some teams with a second bot? Would there be two 45's?
|
|
#22
|
|||||
|
|||||
|
Re: Boiler Bot Battle Sept 2016
Typically at events where a team has 2 robots, one will be driven under a different team number so as not to confuse the FMS. Example 461 and 4611 for the two 461 machines.
|
|
#23
|
|||||
|
|||||
|
Re: Boiler Bot Battle Sept 2016
We will have 234 and 9234 competing.
|
|
#24
|
||||
|
||||
|
Re: Boiler Bot Battle Sept 2016
Yup. Pick an unused number, I'll punch it in.
|
|
#25
|
||||
|
||||
|
Re: Boiler Bot Battle Sept 2016
The stream for the event can be found here: https://www.youtube.com/watch?v=xF0JVaIbxco
|
|
#26
|
|||||
|
|||||
|
Re: Boiler Bot Battle Sept 2016
The PurdueFIRST crew did a great job with this event.
Good crews, relaxed cycle times, plenty of seating and pit space. It was nice to be on campus when students were there (Regionals were always during Spring Break) and our team got to have lunch at one of the dining service food courts and see a little of the campus. |
|
#27
|
|||||
|
|||||
|
Re: Boiler Bot Battle Sept 2016
Quote:
|
|
#28
|
||||
|
||||
|
Re: Boiler Bot Battle Sept 2016
I enjoyed this event and I'm looking forward to coming back. Hopefully either FIRST eases up a bit on District/Regional crossover or WI moves to Districts soon so we can come down more during the season!
Some of that long cycle time was by design. I think the goal was 12 minute match cycles because of the low robot count. |
|
#29
|
||||
|
||||
|
Re: Boiler Bot Battle Sept 2016
As walk-up spectators on Saturday, we enjoyed the event. We felt safe and comfortable with our young children there (8,5,1). The armory is a neat place for an offseason event.
Our two pieces of constructive criticism would be with the sound system - we couldn't really understand - or even hear - the Master of Ceremonies or Game Announcer. Also, if the event was later in the year (like November), I think that could have increased the team count and made for a more comfortable environment. I understand the dates that Purdue allows their resources to be available are limited at best. Like Billfred said, this was solid for a first-time event. We were impressed by the volunteer staff. Hopefully we can attend next year - a lot of students wanted to go, but we just couldn't get transportation in time. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|