Re: Week 3 analysis
 

Unless an opponent robot veers into the ground pass before it reaches your intended robot and a referee slaps you with a G32, or G31:( ...game over Glenn.

Re: Week 3 analysis
 

Joe,
sorry about the SD finals.

If you have a chance to watch our Dallas SF and Finals, we adjusted from the QF to do very effective, quick passing WITH defense. It also allowed us to transition very quickly back to defense.
If balls are being transferred via air, an opponent flying into your robot will definitely affect the attempted assist.

Re: Week 3 analysis
 

Glenn,
We are unfortunately used to "things happening"...all part of the game sometimes. Agreed that air passing has risks for sure. We found "kiss passes" to be effective and generally safe and speedy too;)

Re: Week 3 analysis
 

There's a 3rd way to pass. Find a robot that can pull a ball out of a partner robot. Don't have to worry about loosing possession that way. ;)

Re: Week 3 analysis
 

A version of the kiss pass...direct robot to robot interaction.

Re: Week 3 analysis
 

I can vouch for this mainly because we were the team that would came and "flying" into you. In all honesty we came in like a wrecking ball (couldn't resist :D)

Re: Week 3 analysis
 

Since I wasn't very clear, here is a recap of the conversation I had with Josh. I have a feeling Dr Bot's thoughts were along these lines when he posted:

Background: Josh and I were discussing the LookingForward preview that predicted 67 and 469 would get together at Howell, at which point I said something like:

"This game is different from past games in that you have to try not to get too enamored with picking the best offensive team available. If you're a good shooter, you don't need another shooter because you can shoot and there's only one ball. You need someone who can inbound well, has a fast floor pick up, can pass well, doesn't foul, etc. The only criteria for shooting is if they can make their autonomous shot and maybe shoot in a pinch in case the defense has you tied up, or make a truss pass if you want to do that. There's no reason for an alliance captain that's a good shooter to need another good high-volume shooter. With that being said, if you're afraid that the best shooter on the board can beat you, then you should pick them just to get them off the board."

Re: Week 3 analysis
 

The things that our team (3701, Royal Robotics) learned from the NC regional is...

- Make sure to have someone on your alliance who can help get robots off of you. We had multiple matchs were two robots would be on us because we had the ball and couldn't move.

- One point goals are just as valuable as the 10 point goal

- Make sure coaches dont touch anything. We had one match, and one of our alliance members human player was MIA and the coach started to grab the ball before the match and I told him coaches aren't aloud to touch game pieces, but he did anyway and we were fouled.

- This was my first year programming. I started three days before bag and tag, and I wasn't sure how to make a mecanum drive in LabView, so I used the arcade drive in the program and it over loaded and maxed out the CPU in the cRio in the last match, we had two teams come by and talk about alliances and because our program was messed up we weren't picked. So make sure you dont have any extra things not need in your program!!

Re: Week 3 analysis
 

I have a question on this and I can't find the answer when I searched. Is the (student) coach allowed to carry the robot on the field? I thought the answer was NO- coaches aren't allowed to interact with the robot, controls or game pieces. But I can't find that written and I questioned our team on it this past weekend. I am now wondering where I got that idea in my head. Can someone clarify this for me? Thanks.

Re: Week 3 analysis
 

Me and our coach are the ones that always carry the robot on the field and we have never been told it was not allowed. From what i understand, coaches are not allowed to touch anything after the match has started.

Re: Week 3 analysis
 

Sharon,

There are no rules restricting the coach from carrying or interacting with the robot, while positioning it on the field pre-match.

The only rules for coach-robot interaction would be during the match, the coach can't touch the controls. Unfortunately, I could not find the specific rule in the game manual to determine if that applys to student coaches or not.

I did find these rules:

G33

The COACH must wear the designated “COACH” button while in the ARENA.

Violation: MATCH will not start until the situation is corrected.

G34

COACHES may not touch BALLS. Inadvertent or inconsequential contact will not be penalized.

Violation: FOUL

Can anyone find the rule that restricts the coach from touching the controls?

The best I could find is the definition for DRIVER and COACH, stating that the DRIVER: a pre-college student TEAM member responsible for operating and controlling the ROBOT.

Re: Week 3 analysis
 

I also don't see anything about an extended penalty, so for 50 points, you can drive :).

Re: Week 3 analysis
 

It's in G42:

Re: Week 3 analysis
 

Yes! Thanks. I was scrolling past the graphics for G40 to fast, and missed G41 and G42.

I assumed it was in there and I was just blind.

Re: Week 3 analysis
 

Thanks for the clarification.
Sorry for hacking the thread. Now back to week three analysis....