Week 1 Analysis

[EricLeifermann]

Originally Posted by Ronnie314

For later on I agree but after watching the level of some of these drivers...I wouldn't be confident they could honestly stop a decent bot. Not speaking for just our team. I believe that will be the case for almost all events after week 3 but prior to that I think it might be a viable strategy

The longer it takes you to get rid of your auto balls the less time you have to score assist/truss/catch points, no matter how much I slow you down that is a win every time in my book.

[Citrus Dad]

Originally Posted by nuggetsyl

We learned today people don't read the rules and have no clue how to score.

I would agree this is the fundamental issue this year. One alliance lost in the quarters because they weren't aware that they had never gotten the last auto ball off the field and played like they were in a cycle.

[dag0620]

Originally Posted by Citrus Dad

Do you have an opinion about webstreaming at Inland Empire? Our team ran that one, and we're hoping to run it at UCD.

Well I can personally comment on that.

It was a great webcast. I liked having the full field view separate from the production company, but still having the timer, scores, etc. I know doing that independent of the FMS must not have been easy, but it was great!

Keep up the good work!

[Jaxom]

Originally Posted by Ronnie314

If you have a 1 ball auton and neither of your partners has one, would it be worth it to still put all 3 balls on the field? You score your one and IF you have a decently fast pickup and scoring device then to me it makes sense to keep them out to get those quick 20 points before start the cycle.

No. Even if only one robot has to score all the points (which should never be the case) you lose points by taking the time to finish off the auto balls. If your robot can score in the high goal, you can do a truss shot & get 20 per cycle; that's more than the 10 you get with each auto ball. All a robot has to do to get a possession is trap it against the wall; that's reasonably quick.

Obviously, having to chase down a truss ball takes time, but it also scores immediately. ymmv, but I think what we saw in CIR says don't put auto balls on the field unless you can make them reliably.

[Citrus Dad]

Originally Posted by Ginger Power

I've seen 2 catches in around 30 matches watched. Whether or not this is a true indicator of what is happening I don't know.

We had two catches in our last finals match. I think there was one other catch at Inland Empire.

[BigJ]

Originally Posted by Citrus Dad

Do you have an opinion about webstreaming at Inland Empire? Our team ran that one, and we're hoping to run it at UCD.

I only watched for an hour or so yesterday, and it was mostly superb. If you are looking for small improvements, sometimes there seemed to be music from the venue and possibly music from your streaming computer playing at the same time.

[nlknauss]

Originally Posted by sammyjalex

I saw a lot of defense on the opponent's in the in-bounding zone. Several times, BLUEBALL got trapped between the REDBOT and the REDLOWGOAL while the BLUEBOT is hoping to get the first ASSIST.

I'd like to see that called as a G12. We had this happen to us in a scoring zone yesterday where 2 red robots had our alliance's blue ball cornered behind them next to our low goal. You'll see in the video below that it stopped our cycle for 30s. I don't blame the red alliance for employing this strategy because they weren't controlling the ball, they were just stopping us from getting to it. Definitely smart but I don't think it's a strategy that we'd want to see in this game and the rules should protect this from happening.

http://www.youtube.com/watch?v=VYMrE...are&t=4h56m44s

Nate

[Citrus Dad]

Originally Posted by Laaba 80

Something I've noticed is many teams inbound the ball to robot A, A passes to B, then B does a truss pass, but B never completely crossed into the white zone before passing so no assist is scored. The team took 20 points off the board for no reason.

Not trying to tell you what you saw, but I thought the same thing for a while until I noticed this. I've actually been pretty ok with the assist scoring so far, the slow cycle restarts are a different story though

Our driver was very deliberate about being sure to pick up those points during eliminations. Took me a moment to figure out what he was doing.

[Citrus Dad]

Originally Posted by Christopher149

-
- I hope elims has filtered us down to the competent, so that a match might be a bit more exciting/high scoring..

Turned out to not always be the case.

[Edxu]

Truss points are vital to the success of an alliance

Strong Defense can completely win a match for you if there is no response

Autonomous can make or break an alliance's match

Scouting the defensive capabilities of a robot are incredible for alliance selection, because of the two above points

running 21 point cycles is incredibly fast if you're able to have a robot that can truss shot.

[markmcgary]

Originally Posted by nlknauss

I'd like to see that called as a G12. We had this happen to us in a scoring zone yesterday where 2 red robots had our alliance's blue ball cornered behind them next to our low goal. You'll see in the video below that it stopped our cycle for 30s. I don't blame the red alliance for employing this strategy because they weren't controlling the ball, they were just stopping us from getting to it. Definitely smart but I don't think it's a strategy that we'd want to see in this game and the rules should protect this from happening.

http://www.youtube.com/watch?v=VYMrE...are&t=4h56m44s

Nate

I'd call it a G25 Blockade. It looks like RED ROBOTS stopped the flow of the match for 30 seconds. At least the BLUE alliance flow. I do not know the history of G25, so I may be way off.

3.2.5.8 G25
ROBOTS on the same ALLIANCE may not blockade the FIELD in an attempt to stop the flow of the MATCH. This rule has no effect on individual ROBOT-ROBOT interaction.
Violation: TECHNICAL FOUL

[Josh Fritsch]

Originally Posted by markmcgary

I'd call it a G25 Blockade. It looks like RED ROBOTS stopped the flow of the match for 30 seconds. At least the BLUE alliance flow. I do not know the history of G25, so I may be way off.

I disagree. Q&A has said that 2 robots playing defense is not "blockading".

However, it would be awfully close if not "possession" by the opponent according to G12:

G12
An ALLIANCE may not POSSESS their opponent’s BALLS. The following criteria define POSSESSION:

D. “trapping” (overt isolation or holding one or more BALLS against a FIELD element or ROBOT in an attempt to shield them).

[PayneTrain]

Originally Posted by Citrus Dad

Do you have an opinion about webstreaming at Inland Empire? Our team ran that one, and we're hoping to run it at UCD.

Are you all going to publish anything on how you ran yours? I really liked it in the offseason and now, and I can't be the only one curious to try it out myself.

[Citrus Dad]

Originally Posted by pfreivald

Because they'd be so busy scoring they wouldn't have time to get back into position!

...but yes, the less-than-perfect alliance will have to deal with the vagaries of life in robot-land.

We were very busy scoring (191 teleop in one match) but still played a lot of defense while our shooter was scoring, and our initiator was repositioning.

[markmcgary]

Originally Posted by Josh Fritsch

I disagree. Q&A has said that 2 robots playing defense is not "blockading".

However, it would be awfully close if not "possession" by the opponent according to G12:

I found Q189 stating: "Generally, ALLIANCE ROBOTS successfully trapping the entire opponent ALLIANCE into one area of the FIELD is considered "stopping the flow of the MATCH" and an example of a "blockade"."

So, it appears that a blockade does not apply.

But, I agree. I was also thinking G12-D. There are lots of subjective calls in this game.