Re: Week 1 Analysis
 

-Scout to see if bots "play nice with others"

-Edxu is right, truss shots can easily sway a match

-Human Players can really screw up a match

-Alliance selection will decide (most of the time) if you win, so scouting programs have to be excellent this year.

-quick two assist cycles with one defense bot worked well.

Re: Week 1 Analysis
 

I was real happy with the Citrus Circuits streaming video also. The only tiny issue I noticed was the fade to black during camera angle changes. Sometimes they happened at just the wrong time. Maybe a cross-fade instead?

Thanks to 1678 for hosting the IE streaming video!

Re: Week 1 Analysis
 

Great stream, the full-field view is the best for webcasts because I feel like I'm up in the stands, and I'm not going to miss anything. My only complaint was that the score on your in-match overlay was often different from the one on the projector screen. I'd like to see the official score. Other than that, you guys did a great job with it and I'd love to see it for more events.

Re: Week 1 Analysis
 

I am fine with hard switches in sporting events personally. Cross fades are better than fade to black, but cross fades are generally unintelligible while both feeds are shown at once.

One thing to note (didn't watch any regional but Alamo). When the MC is announcing the teams should be the only time the alliance station cam should be used. Showing the drivers during a match is annoying, and useless. We want to see the robots. Generally speaking I also hate to see the view of one robot mega close to a camera, it is cool seeing them up close, but again, I want to see the match.

Re: Week 1 Analysis
 

Thanks!:)

Re: Week 1 Analysis
 

Thanks. Yes we're aware of the audio issue. We actually used Skype to send audio to avoid hardwires, but it had some reliability problems.

Re: Week 1 Analysis
 

Yes, I've asked the students to prepare a write up (in part because they are seniors!) and we'll share it on Chief Delphi.

Re: Week 1 Analysis
 

Loved the full field with the score overlay. It took my favorite part of the Michigan webcasts, the full field view, and improved it by putting the score up and removing the awkward fish-eye view.

Re: Week 1 Analysis
 

In the Southfield final 1 video -- https://www.youtube.com/watch?v=vPlx4MOkVck -- it looks as if the robots are disabled a second or two before the buzzer sounds the end of the match.

Any ideas why? Did the clock hit zero when the robot were disabled or when the buzzer sounded?

Re: Week 1 Analysis
 

I prefer the fish eye view to the stood back midfield view.

Re: Week 1 Analysis
 

I noticed the same thing in some (but not all) matches at GTRW.

Re: Week 1 Analysis
 

This occurred in several matches at Alamo too. The robot would suddenly stop moving and the buzzer was always delayed.

Since the autonomous lights and goals were sometimes delayed, and possibly the computation of assists, I think this may be connected to the other issues we have been seeing with the field systems.

Re: Week 1 Analysis
 

From what I have seen in the streams that I have watched fouls are huge in determining the outcome of the game, however defense is also important. There is no sense in sitting there after your alliance has shot or passed the ball when you could be obstructing another alliance from scoring. Beware G40 for it is always watching...

Re: Week 1 Analysis
 

There were oddities I dont remember from previous years. Sometimes at Alamo, the clock would hit zero, the lights would go out, the robots would stop, and the buzzer would sound. Those events drug out over the course of at least 2-3 seconds. Odd...

Re: Week 1 Analysis
 

This is probably going to come off as long, whiny, and un-GP, but bear with me. I would like the referees to LEARN the rules, or at least be consistent. I am only posting this now because I fact checked beforehand.

First, during eliminations, whenever someone from our team would go up to the question box, we would be told, "You need the alliance captain in the question box"
I will simply quote the Game Manual for this:
Second, in Q-24, 3667 (This is in NO way putting them down) got disabled with the ball between them and the opposing low goal. We ended up losing the match, due to that reason. Afterwards, we sent a team member to the question box to inquire if, during that match, we were allowed to hold up the dead ball sign to render the ball dead. The referee told us yes, that we could. Later, when we were at the practice field, a referee came up to our drive team, and told us they were wrong, and that what they told us was incorrect. Our drive team was okay with that, because we had not tried using it since then, and they had delivered the correct rule.

Fast forward to Finals Match 1 (we are blue). After autonomous, a missed ball is on the red side of the field, and it goes in front of the red low goal, and there is chaos (as usual) around the ball, and 453 (red, once again, NOT putting them down) gets disabled with the blue ball between them and the wall, and the red low goal behind them. Because of what we were told earlier, we did not hold up the dead ball sign (which is also reinforced by the Q&A here), yet no possession call was made on 453, which should have been a G12:D, a 50 point technical foul. After the match, the referees said that we needed to hold up the dead ball sign. This lost us F-1.

So, to add on to everyone's complaints about missed calls, G26 (sodizzle, Joseph, and Tom, I agree with you on those miscalls, I mean come on, BLUE BOX) and G40 (which actually isn't too hard to not get called on as long as you're careful and take a tad more time), if you are a referee, PLEASE read the rulebook.