Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Off-Season Events (http://www.chiefdelphi.com/forums/forumdisplay.php?f=20)
-   -   2014 MN State Championship (http://www.chiefdelphi.com/forums/showthread.php?t=128604)

tstew 09-05-2014 00:05

Re: 2014 MN State Championship
 
Quote:

Originally Posted by Tom Ore (Post 1383925)
There are only six Iowa teams total. We (525) have never had a practice bot. 967 did have a practice bot this year, not sure about the others. (967 was the only team to bring a practice bot to our week 0 scrimmage and all six teams were there.)

Quote:

Originally Posted by inkling16 (Post 1383961)
I am aware that there are only 6 Iowa teams. I had assumed that 525, 967, and 3928 all built practice robots, and it turns out I was wrong on at least one count, still not sure about Neutrino. My point was that there are incredibly few MN teams that made practice robots.

But I lose my own bet.

Neutrino built a practice robot. We actually brought our practice bot to the scrimmage and left our comp bot at home. The practice bot was nice to have as we redesigned our arm for North Star.

Ginger Power 09-05-2014 12:05

Re: 2014 MN State Championship
 
I've entered data into the scouting database for teams who had no information. I put question marks by any of the data I wasn't absolutely sure of. There is still missing data and my school blocks TBA so I can't do any more research right now.

mjc49 09-05-2014 14:42

Re: 2014 MN State Championship
 
Quote:

Originally Posted by inkling16 (Post 1383890)
This makes me curious, how many MN teams build full practice bots? 2052 doesn't, or Dragonfish wouldn't exist, I'm pretty sure 2169, 3018, 2175, 2177, and 3313 didn't this year. 2512 maybe?

My bet would be that there are more Iowa teams with practice bots than MN teams with practice bots. :yikes:

3042 built a second bot this year. It was expensive from a time (labor) and budget standpoint, but we went into the build season knowing we had enough resources to do it. We were able to make improvements while the main bot was bagged and then bring the updated assembly with us to our tournaments. This was the first year we had the ability to build two bots.

Caleb Sykes 09-05-2014 15:26

Re: 2014 MN State Championship
 
Quote:

Originally Posted by mjc49 (Post 1384112)
3042 built a second bot this year. It was expensive from a time (labor) and budget standpoint, but we went into the build season knowing we had enough resources to do it. We were able to make improvements while the main bot was bagged and then bring the updated assembly with us to our tournaments. This was the first year we had the ability to build two bots.

That is awesome! Minnesota teams are doing more than I give them credit for. Too bad you guys won't be at the state championship, I would have loved to get a better look at your robot.

cadandcookies 09-05-2014 15:56

Re: 2014 MN State Championship
 
Quote:

Originally Posted by inkling16 (Post 1384119)
That is awesome! Minnesota teams are doing more than I give them credit for. Too bad you guys won't be at the state championship, I would have loved to get a better look at your robot.

They're one of at least 2 regional winning teams not attending the state championship.

Chief Hedgehog 09-05-2014 23:10

Re: 2014 MN State Championship
 
One of 4607's major concerns after last year's season was to make the next big leap and not just rest on the idea that we were 'just a second year team'.

The overwhelming response from the kids was that we needed to build a practice bot. It proved be very intensive and costly, but it really did push our team's talents and skills to the next level.

We had some issues right off at North Star (See the first few matches, but once we got the Superstructure correctly mounted on 'Gumdrop' (our competition Robot), we did pretty well.

No doubt that we will continue building practice bots in the upcoming years.


Quote:

Originally Posted by mjc49 (Post 1384112)
3042 built a second bot this year. It was expensive from a time (labor) and budget standpoint, but we went into the build season knowing we had enough resources to do it. We were able to make improvements while the main bot was bagged and then bring the updated assembly with us to our tournaments. This was the first year we had the ability to build two bots.


Chief Hedgehog 09-05-2014 23:23

Re: 2014 MN State Championship
 
I am not certain how 'limiting' the MSHSL has been with FIRST - at Becker we structured our team just as any other Athletic/Activity team would do.

However, BHS does not fund any part of 4607 CIS - we have to cover all of our expenses ourselves. The kids fundraise the crap out of the off-season and we knock on a lot of doors.

I agree with C&Cookies - MSHSL Tournament brought legitimacy to the sport. I remember leaving the Marriucci to go get some lunch and I found myself behind a kid form M&SA with a letter jacket on - and the patch on the back was "2013 State Champion -FIRST Robotics".

I thought that was pretty cool.

Quote:

Originally Posted by compwiztobe (Post 1383949)
Try two months... for some. Of course, many people feel that bagging is necessary between build and regular season (I am not among them). If this is the case, since people want to treat this as a regular season event (which it is not) to crown a MN state champion, bagging is still required.

But bagging and the build deadline really need to be ditched altogether. It's a broken system modeled off an outdated competition structure. We no longer have a logistical, real-life ship deadline to get all our machines to the same event. All other teams at our events necessarily have had the same time since kickoff to work on their machine, unless they've invented time travel. As it is, the higher resource teams will still be able to practice when their bot is in the bag, while those with less are out of luck. But all of this has been said before...

I'm sort of confused about the MSHSL sponsorship too. Schools already had complete freedom to award robotics letters, compensate coaches, and the whole deal (we did). I struggle to see how MSHSL involvement is anything but limiting, introducing a plethora of rules about funding, district association, student membership, transportation, and plenty of other nonsense that teams are far better off dealing with themselves. The event operation has also been rather closed off in the past, at times charging entry fees, as well as the exhorbitant prices one might expect for any photos, merchandise, and match recordings from the event.

I look forward to official district status, since this will make qualification for any state championship event make a lot more sense, and hopefully give us more freedom to run these events.


Boe 11-05-2014 01:02

Re: 2014 MN State Championship
 
In case anyone is still trying to figure out which MN teams build practice bots I just remembered that 2491, 3018 and 2502 all do.

That brings the count to 8 I believe, putting it above the total number of teams in Iowa.

Richie_Richter 11-05-2014 01:24

Re: 2014 MN State Championship
 
Yep, 2502 has built a practice bot for the last few years, and it is so, so nice to have. We have made a ton of modifications and improvements over our original design, and without a practice robot we would have gone into competition without any of those things tested.

If there are any teams out there who want to be more competitive in competition, you gotta find the time and money to build a practice bot.

Just today we made a modification to our shooter to lower the shot angle and increase our shooting range from about 2 feet to 10 feet! No joke, the simple addition of a few pegs at the back of our shooter made all the difference and now we're just a little disappointed we didn't think of it earlier. Expect high goals for days at state!

Plus building a practice robot is great for us because we have a pretty large team. It helps keep everyone busy thought the season with construction, testing, and mods.

In short. BUILD A PRACTICE ROBOT NEXT YEAR!

ehochstein 11-05-2014 14:42

Re: 2014 MN State Championship
 
2470 built a practice chassis this year. After bagging we used the practice chassis for sizing of new parts and creation of bumper mounts. Next year we will be building a full practice robot.

FRC3883FRC 11-05-2014 14:58

Re: 2014 MN State Championship
 
At the start of the build season 3883 had plans to make a second practice bot but never got around to actually doing it. Mainly becuae of the new kit chassis this year. The team still managed to build a great robot. Yes practice bots are very useful but does not mean teams cant build robots that work well.

Anyways back to the topic of state. With the 6 hour unbag period the team within 2.5 hours had a double ball auto working. Its really tight on time but is under 10 seconds. The Data Bits now have a 2 ball auto for state and wont be afraid to use it (hopefully). Here is the video of the testing. The first ball is 2 bag and tag bags stuffed inside. Had no second ball and it was more about picking up the second ball and getting that one shot. Hope to show it off at state.
2 ball auto working

pntbll1313 11-05-2014 15:17

Re: 2014 MN State Championship
 
Quote:

Originally Posted by FRC3883FRC (Post 1384465)
Anyways back to the topic of state. With the 6 hour unbag period the team within 2.5 hours had a double ball auto working. Its really tight on time but is under 10 seconds. The Data Bits now have a 2 ball auto for state and wont be afraid to use it (hopefully). Here is the video of the testing. The first ball is 2 bag and tag bags stuffed inside. Had no second ball and it was more about picking up the second ball and getting that one shot. Hope to show it off at state.
2 ball auto working

Great job guys! We've got a 2 ball auto now too :D https://www.youtube.com/watch?v=AxmvlomrtR0

We also increased our sweet spot quite a bit with a nice flat trajectory

Mr.Paulson 11-05-2014 16:47

Re: 2014 MN State Championship
 
Looks like some great improvements have been done on machines for the weekend. We have made some upgrades as well. At Lake Superior we had issues with the ball popping off our bot when hit from the front. That is fixed and the ball DOESNT come out now. Also the ball jostled around during auto because it was not secure. The fix solved this too.

We had robot displays for our sponsors and during this time realized our front bar on our chassis was cracked so we had to replace that too.

Finally our wings were too "floppy" and did not allow for easy and quick opening and closing because we used a window motor to open and close them. Now we replaced this with pneumatic cylinders and it opens and closes in a snap.

All this plus changing tread on wheels and replacing broken bumper boards and we are now ready! Should be a great time and we are looking forward to a fast paced weekend. Good luck to all!

Ginger Power 12-05-2014 00:01

Re: 2014 MN State Championship
 
Now that we are within a week of the competition does anybody have some bold predictions they want to share?

Here are mine:

- There will be >0 matches over 300 points

- The innovative strategies used in elims at Champs will be common throughout the tournament

- There will be few if any 2 assist cycle strategies going into a match

- The winning alliance will be the smarter alliance rather than the alliance with the best robots

- Fouls will not play a major role

- (Shot in the dark) 2052 will seed first and select 2175 as their first pick.

Shrub 12-05-2014 10:06

Re: 2014 MN State Championship
 
My bold predictions are as follows:

-There will be a mainly strategies involving HP in assists

-Finals matches will have score differences under 20

-Our driver won't be in a wheelchair (otherwise we'll need a booster seat)

-Free corndogs??? Free ice cream??? Free chipotle??? We just don't know.

-Robots will fall over. A lot. (SATURDAY SATURdAY SATURDAY ROBO CARNAGE AT WILLIAMS ARENA BE THERE BE THERE BE THERE)

Also, does anyone know if any teams declined? Rumour has it a few did.


All times are GMT -5. The time now is 08:32.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi