Aerial Assist Discussion Thread

[cbudrecki]

Originally Posted by jp1247

Neat game, interesting there's no endgame...

Though, it may just be me, it seems that there is no point to the lower goals. Every team (assumption, though a fairly good one I'd say) is going to at least AIM for getting the high goals.

With assists, the low goals can still be valuable. The 10 & 30 point bonuses also apply to the low goals.

[taschneide]

If you get a ball from your team stuck inside your robot, then tough luck, I guess. You can't use the ball, and you can't get another ball into play until your ball has been scored, which isn't going to happen, 'cause you can't use the ball.

If you get your opponents' ball stuck inside your robot, though... that's a technical foul, right? But is it just one technical foul, or do they add more on over time? The rules say "technical foul per instance"... I assume this is one thing they're going to change over the coming weeks, otherwise it might be worth it to steal your opponents' ball and sit on it for the whole match.

[Snapshot]

Has anyone seen anything that says it's okay to block passes by intentionally driving between two opponent robots or even pushing a ball out from in front of a robot that's pushing the ball along the field?

[Steve Horn]

Originally Posted by Jhultink

So if you can's score autonomous you get to become a goalie...

If you can't score in one of the goals in autonomous mode, you can also drive into your zone and get five points. If you can cross into your zone and score in the "hot" goal, you can get 25 points in autonomous mode.

[GaryVoshol]

Originally Posted by Chi Meson

Follow up to that,
Can the balls that begin in auto be used to score truss points before they score a goal?

I'm guessing not, based on 3.1.4:

Points are awarded once per CYCLE for BALLS SCORED by ROBOTS in the GOALS, BALLS SCORED by ROBOTS over the TRUSS, and for each ROBOT CATCH. Additional points are credited to an ALLIANCE upon each GOAL based on the number of ASSISTS earned by the ALLIANCE for that CYCLE.

The CYCLE doesn't start until after all the BALLS from AUTO have been SCORED. (3.1.2)

[Chi Meson]

Originally Posted by GaryVoshol

I'm guessing not, based on 3.1.4:


The CYCLE doesn't start until after all the BALLS from AUTO have been SCORED. (3.1.2)

But that logic would make the autonomous goals not count as well. I read that rule to limit the number of truss/catch points per cycle.

In 3.1.4 it says specifically for assist points:
"ASSISTS are earned when a unique ALLIANCE ROBOT POSSESSES the ALLIANCE’S BALL in a unique ZONE (i.e. red, white, or blue ZONE) during a CYCLE."

It does not say specifically that truss points "only count within a cycle."

[Yalib]

What do you guys say about G4, G5?

Auto setup - does setting up a robot in "thier goalie zone" mean he is placed on the opposite alliance's side and can block in auto? or does it mean he starts in the goalie zone of his color?

[GaryVoshol]

Originally Posted by Chi Meson

But that logic would make the autonomous goals not count as well. I read that rule to limit the number of truss/catch points per cycle.

It does create a Catch-22 situation if BALLS are SCORED only during AUTO or in a CYCLE. A CYCLE doesn't start until all the BALLS from AUTO have been SCORED. But they can't actually SCORE after AUTO ends.

And the following text in 3.1.4 that tells when BALLS are SCORED says nothing about being inside a CYCLE.

Something for the GDC to clarify.

[The_ShamWOW88]

Question regarding auto if anybody has any ideas. The robot is allowed to drive up to the 10pt goal and shoot/roll/layup the ball or does it have to be done from the white zone before the robot enters the red/blue zone?

[heisenburger]

I'm new to first and by looking quickly through the manual i didn't find any programming rules. so are there any programing rules?

[Chi Meson]

Originally Posted by GaryVoshol

It does create a Catch-22 situation if BALLS are SCORED only during AUTO or in a CYCLE. A CYCLE doesn't start until all the BALLS from AUTO have been SCORED. But they can't actually SCORE after AUTO ends.

And the following text in 3.1.4 that tells when BALLS are SCORED says nothing about being inside a CYCLE.

Something for the GDC to clarify.

That line you quote where the cycle doesn't begin until all auto balls are "scored"...
They obviously do not mean "truss" scored, but "goal" scored. A clarification is needed, although I do take it to mean that all balls must be scored in goals before a cycle begins. I still see it so far that truss/catch scores are valid using balls that begin in autonomous.

I would very much like to get that clarified.

[DaveFrederick]

What is the password for the encrypted data?

[Snapshot]

Originally Posted by heisenburger

I'm new to first and by looking quickly through the manual i didn't find any programming rules. so are there any programing rules?

FIRST is pretty lenient with the programming rules. You can choose between Labview, C++ (Winriver), or Java (Netbeans). When programming, you must make sure to implement watchdog, which is a function that automatically shuts down the robot to prevent safety hazards if it isn't "fed" within a certain amount of time. Of course, you also must be sure your code doesn't allow control while disabled or autonomous, of course.

I'm sure there's other rules, but those are the big ones.

[Snapshot]

Originally Posted by DaveFrederick

What is the password for the encrypted data?

3Zones2Goals1Alliance!

[ohrly?]

I'm really confused about the role of the human players, specifically these ones: http://min.us/i/bpK5KsFVN1YvK

G38 prevents player C from passing the ball to player A, and G39 prevents player A from getting the ball himself. Furthermore, player A is forbidden from inbounding a ball by G36. So what exactly do player A and B do?