|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: What we learned from week 1
G30 is called very inconsistently.
In eliminations, a lot of matches turned into 6 robot scrums at midfield, with each side trying to get back to their feeder stations with 1 or 2 bots while the other(s) played D. The lower rung of the pyramid is a bit lower than everyone expected. Being 1/32" of an inch off the ground is as good as being 27" off the ground. The pyramid is FAR less rigid than I expected. Anyone attempting a 30 point climb, especially on the corner, better hold on tight. |
|
#2
|
||||
|
||||
|
Re: What we learned from week 1
This. Had to exit in the quarterfinals because G30 wasn't called at all. We also had some bad planning and poor strategy on our part, and I don't think we would've gotten past semis, but I was absolutely furious when we lost our last match and the 3 infractions of G30 weren't counted, but one accidental instance of G36 was counted. |
|
#3
|
|||||
|
|||||
|
Re: What we learned from week 1
For anyone competing in the coming weeks and planning on using the pyramid as a protected area, I suggest you keep the following handy:
Quote:
Quote:
Quote:
That being said, there was a certain degree of 'right of way' protection that was assumed to have been created by G30 - that being if you're touching/nearly touching the pyramid and attempting to play the game (score) you would more or less be allowed to do what was required to continue playing - which we were told was not the case. Whether or not this will be called uniformly across all events has yet to be seen... I guess the TLDR here is to go over G30 in detail with the head ref if it's relevant to your strategy, whether it be climbing or shooting, and make sure that if you're touching the pyramid, that it's CLEARLY visible from all/most angles on the field. A few teams had little flags and fiberglass sticks that would deform when they were in contact which seemed to make things a bit easier. Last edited by thefro526 : 04-03-2013 at 09:29. |
|
#4
|
||||
|
||||
|
Re: What we learned from week 1
Well after 1422 caught fire, I learned that Team 639 had the right idea in putting a smoke detector on their robot.
|
|
#5
|
||||
|
||||
|
Re: What we learned from week 1
It was also noticeable how the practice pyramid rigidity deteriotated as the regional progressed. By the end of qualifications it was significantly looser than the field pyramids. I suspect that absent some upgrades the field pyramids will become interestingly dynamic by Week 6 competitions.
|
|
#6
|
|||||
|
|||||
|
Re: What we learned from week 1
Do you have a specific measurement for the height of the first bar? Or at least a ballpark value?
|
|
#7
|
|||||
|
|||||
|
Re: What we learned from week 1
We measured ~28 1/4" from the floor to the bottom of the first bar (+/- 1/4" depending on which rung and which pyramid).
|
|
#8
|
||||
|
||||
|
Re: What we learned from week 1
How are they that far out of spec? That is completely unacceptable.
|
|
#9
|
||||
|
||||
|
Re: What we learned from week 1
Quote:
We believe it was from the 1/2" plywood base + carpet lining + carpet underneath the pyramid. So the 30" from the actual floor the bots drive around on is 30"...but then you need to take into account the 3/4" of base underneath the pyramid. The practice field didn't have the plywood base, so it threw my team all off until late Friday afternoon. Our hanger still didn't work as well as we would have hoped...but we didn't expect that curveball. Last edited by TD78 : 04-03-2013 at 10:10. |
|
#10
|
||||
|
||||
|
Re: What we learned from week 1
Quote:
Measuring the field and adjust-ability in your hanging mechanism are both mandatory this year, I'm afraid. |
|
#11
|
||||
|
||||
|
Re: What we learned from week 1
Quote:
|
|
#12
|
||||
|
||||
|
Re: What we learned from week 1
Quote:
|
|
#13
|
||||
|
||||
|
Re: What we learned from week 1
Also, on the subject of the pyramid, robots are standing up to falls better than anticipated. There was damage from falls, but I didn't see anything that really messed up a robot unless it flipped off the pyramid and landed directly on a mechanism.
|
|
#14
|
|||
|
|||
|
Re: What we learned from week 1
While the strategic value of shooting 5pt shots from the floor (with 50% accuracy) is questionable, it sure does get the crowd going.
Floor pick up is much more valuable than I personally expected. Autonomous points are very big this year; if you can reliably gather extra game pieces, your robot will really stand out. This game piece is pretty difficult to move around consistently. It's easy to shoot, but loading and collecting caused a few jams that crippled us for a match. Keep the practice field away from the screen with scoring displays. In Traverse City, the sheet behind the practice goals blocked the view of the scores for approximately 1/3 of the audience. Last edited by DjScribbles : 04-03-2013 at 10:14. |
|
#15
|
||||
|
||||
|
Re: What we learned from week 1
1). This Game is a lot harder than expected.
2.) Defense totally rewrites how the game is played. It makes it feel like it is played in turns. 3.) Full-court shooters are very successful in qualifications if not stopped, but may falter in Eliminations rounds. 4.) Auto is the most important part of this game. It is really hard to make a comeback if all hit and one side doesn't. (more so than other seasons) 5.)Defense is going to evolve even further as weeks go by teams shutting down main robots and teams being forced to rely on other partners. Overall week one impressions autonomous,autonomous,autonomous! This game runs on it IMO. I am hoping to see more 30pt climbs and how it can effect the game later on.Last edited by Blackphantom91 : 04-03-2013 at 10:25. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|