[FRCTop25.com] Week 1 Preview Show!

[barn34]

Originally Posted by JohnFogarty

This is definitely the year of the lower seed advantage I think. I'd like to hear some discussion on that though.

I actually think this is going to vary quite a bit by regional. One very big advantage a top seeded team could have is being able to start out with that perfect 75 point autonomous score (or very close to it) taken care of mostly between the two high ranked robots alone. That's something that may or may not be easily duplicated at the lower seeds depending on shooting capability and hot goal recognition. Again, this discrepancy will vary wildly by regional, I think.

After autonomous, there is quite a bit of variance on how things could play out depending on that third robot's capability to synergize well with the other high seed robots in just one facet of the game. That could be shooting, outlet passing, defense, etc. This will require the other two robots to be very versatile in their skill sets in order to accomodate the vast array of possibilities for that third alliance partner capability. If the top robots are too one dimensional or too hesitant to adjust their playstyle based on their partners, I think that's the recipe for top seeds getting upset.

[JohnFogarty]

Originally Posted by barn34

I actually think this is going to vary quite a bit by regional. One very big advantage a top seeded team could have is being able to start out with that perfect 75 point autonomous score (or very close to it) taken care of mostly between the two high ranked robots alone. That's something that may or may not be easily duplicated at the lower seeds depending on shooting capability and hot goal recognition. Again, this discrepancy will vary wildly by regional, I think.

After autonomous, there is quite a bit of variance on how things could play out depending on that third robot's capability to synergize well with the other high seed robots in just one facet of the game. That could be shooting, outlet passing, defense, etc. This will require the other two robots to be very versatile in their skill sets in order to accomodate the vast array of possibilities for that third alliance partner capability. If the top robots are too one dimensional or too hesitant to adjust their playstyle based on their partners, I think that's the recipe for top seeds getting upset.

Except Multi-ball auto isn't rare like multi-disk auto was last year.

[barn34]

Originally Posted by JohnFogarty

Except Multi-ball auto isn't rare like multi-disk auto was last year.

I'm thinking that while you've seen quite a few 2 ball autonomous modes in videos this year, you're not going to see very many regionals where that's an advantage the upper seeded teams won't have. For example, even if 2 ball is a skill that 8 to 10 teams could have at a regional, most of those teams would likely get paired up with each other. That still only covers teams seeded 1-4 or 5. Then, you also have to factor in hot goal recognition. I'm not thinking that's a skill you assume teams that make it down the pick list on the back end of the snake will have either.

I agree that 2 ball is not as rare as multi disc auto was last year...but that doesn't mean you can assume to see 1/3 of a regional roster to have that ability either.

[Woolly]

Originally Posted by JohnFogarty

Except Multi-ball auto isn't rare like multi-disk auto was last year.

The motions of a multi-ball auto will be more common, however I predict there will be many robots that take 2 shots and only hit 1. I predict that at maximum there will 4 robots at a regional with consistent 2 ball autonomous modes, and MAYBE 2 that have consistent 3 ball autonomous modes.

A lot of these reveal videos only show you the times it made it, not the failed attempts before and/or after.

However, I would say it would be a good idea for ALL teams to come up with an autonomous mode that will do nothing for about 7-9 seconds (depending on how fast you can get to the forward zone) and then drive forward, in order to be able to better take advantage of these multi-ball autonomous modes. Even if you think your robot is too good to not shoot it's own ball, mechanical failures happen. If you find your shooter broken going into the match and your alliance partner can cover for it in autonomous, you will be glad you were prepared.

[PayneTrain]

Originally Posted by wilsonmw04

some of us just got banned for saying "hi" to a team. Just sayin'

Could be worse, like getting banned for no reason and not even knowing.

[barn34]

will there be an archive of the show somewhere for anyone who may not be able to tune in live?

[Mike Starke]

Originally Posted by barn34

will there be an archive of the show somewhere for anyone who may not be able to tune in live?

Yes there will be!


This is also a great time to mention that we have moved one more final time. You can catch tonight's show at new.livestream.com/FRCTop25.

Can't wait to see you all tonight!

[Bill_B]

I agree multi-ball auto is featured in quite a few reveals. However, who is programming an auto mode that is "leave the ball and go for the colored zone?" I mean balls have to touch a robot and very few videos have shown that. They simply start with two balls in the vicinity of their machine.

[EricLeifermann]

Originally Posted by Bill_B

I agree multi-ball auto is featured in quite a few reveals. However, who is programming an auto mode that is "leave the ball and go for the colored zone?" I mean balls have to touch a robot and very few videos have shown that. They simply start with two balls in the vicinity of their machine.

Balls do not have to touch robots.

[XaulZan11]

Originally Posted by EricLeifermann

Balls do not have to touch robots.

They do if you want the 5 mobility points.

[Tem1514 Mentor]

Originally Posted by XaulZan11

They do if you want the 5 mobility points.

Please, please point me to the rule that says I MUST load a ball for Mobility points.

[barn34]

Originally Posted by EricLeifermann

Balls do not have to touch robots.

Actually, Eric, you may want to double check the wording of G5...



"G5



For ROBOTS starting in the white ZONE, the TEAM may preload one (1) of their ALLIANCE’s BALLS such that the BALL is touching their ROBOT.

For ROBOTS starting in their GOALIE ZONE the TEAM may decide if the BALL is: staged between the TRUSS and the ZONE LINE and not contacting an ALLIANCE partner, or removed from the FIELD for the MATCH.

If a ROBOT does not report to a MATCH, its ALLIANCE may decide if the BALL is: staged between the TRUSS and the ZONE LINE and not contacting an ALLIANCE partner, or removed from the FIELD for the MATCH.

Violation: If the situation is not corrected before the start of the MATCH, TECHNICAL FOUL per BALL improperly staged."


I've interpretted that as in order for a ball to be placed on the field in autonomous, it must be touching a robot to be considered 'loaded'. Exception, of course, is if you place that robot in the goalie zone.

That means, if you've already loaded your robot with a ball, you have to place a robot you may be 2 balling with such that it is in contact with that ball and you are not. Again, unless the robot that ball 'belongs' to is positioned in the goalie zone.

At least that how I've interpretted it. Did I interpret that wrong? If you were only referring to the goalie zone instance, then feel free to kick me when you see me in Milwaukee. lol

[EricLeifermann]

Originally Posted by barn34

Actually, Eric, you may want to double check the wording of G5...



"G5



For ROBOTS starting in the white ZONE, the TEAM may preload one (1) of their ALLIANCE’s BALLS such that the BALL is touching their ROBOT.

For ROBOTS starting in their GOALIE ZONE the TEAM may decide if the BALL is: staged between the TRUSS and the ZONE LINE and not contacting an ALLIANCE partner, or removed from the FIELD for the MATCH.

If a ROBOT does not report to a MATCH, its ALLIANCE may decide if the BALL is: staged between the TRUSS and the ZONE LINE and not contacting an ALLIANCE partner, or removed from the FIELD for the MATCH.

Violation: If the situation is not corrected before the start of the MATCH, TECHNICAL FOUL per BALL improperly staged."


I've interpretted that as in order for a ball to be placed on the field in autonomous, it must be touching a robot to be considered 'loaded'. Exception, of course, is if you place that robot in the goalie zone.

That means, if you've already loaded your robot with a ball, you have to place a robot you may be 2 balling with such that it is in contact with that ball and you are not. Again, unless the robot that ball 'belongs' to is positioned in the goalie zone.

At least that how I've interpretted it. Did I interpret that wrong?

You're correct, and I'm aware of that rule. It is the one in which I was referring to. I'm not going to just give people answers, I'm going to make them think about what I said and look into the rule book, that way they remember.

[XaulZan11]

Originally Posted by barn34

Did I interpret that wrong? If you were only referring to the goalie zone instance, then feel free to kick me when you see me in Milwaukee. lol

Or, if he referring to telling non-broken alliances partners to sit out a match so the autonomous ball doesn't need to be touching a robot. But, I think you are right.

[Abhishek R]

Originally Posted by Bill_B

I agree multi-ball auto is featured in quite a few reveals. However, who is programming an auto mode that is "leave the ball and go for the colored zone?" I mean balls have to touch a robot and very few videos have shown that. They simply start with two balls in the vicinity of their machine.

If a team is running a 2-ball autonomous mode, that likely means one robot on the alliance is not capable of scoring the ball themselves. If they can't score the ball, they will probably still get the mobility points, which the easiest way to accomplish is to just drive forward into your zone. So why not just have a corner of their bot touching the ball and then they can drive forward off to the side?