Quote:
Originally Posted by ToddF
So instead of just complaining about balls bouncing out of the high goals, let's work together as a community to solve this problem for FIRST. Does anyone have any proposals for how to solve this problem? Things to consider in your answer:
- effectiveness
- ease of installation and removal during field setup and teardown
- cost
- time to implement. If it can't be implemented by week 2 competitions, it doesn't help.
- aesthetics. Should blend in with the high tech look of the field and not look like something that was duct taped on at the last minute.
OK, go...
|
Quote:
Originally Posted by Bochek
just cover the openings behind the goals and above the drivers heads. a piece of polycarbonate would do.
|
I think Bochek has it. It meets all of ToddF's criterion.
Quote:
Originally Posted by Daniel_LaFleur
Can we add: Leave it as is.
It's not changed since kickoff.
|
I'm willing to wager that if this happened to your team, you'd be the first one to call foul. It's easy to hold such a potentially hypocritical position when you have yet to play a match.
===
Ultimately, it'll come down to the intent of the rails and how FIRST had intended for the goals to perform.
As per the rules (3.1.4.A), FIRST has no obligation to fix this. They are fine by how the rule is defined and how the field was built.
However, currently, it seems that the rail is there to protect drivers, and not to kick the ball back out. If this is correct, and FIRST wants to keep it that way, they ought to implement a change.
- Sunny G.
3.1.4.A - A BALL is considered SCORED in an ALLIANCE’S GOAL if a ROBOT causes one (1) of their ALLIANCE’S BALLS to cross completely and remain completely through the opening(s) of one (1) of their ALLIANCE’S GOALS without intervening TEAM member contact