Go to Post This [Coach badge] means no-touchy the controllers. Even to save them from certain doom. - Kevin Sevcik [more]
Home
Go Back   Chief Delphi > FIRST > General Forum
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
Thread Tools Rate Thread Display Modes
  #16   Spotlight this post!  
Unread 27-04-2014, 01:51
Jaxom Jaxom is offline
Registered User
AKA: Michael Hartwig
FRC #1986 (Team Titanium)
Team Role: Mentor
 
Join Date: Apr 2010
Rookie Year: 2008
Location: Lee's Summit, MO
Posts: 379
Jaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant future
Re: Something FRC GDC could learn from VRC GDC

Quote:
Originally Posted by scca229 View Post
I think the biggest problem is that way too many teams have engineers and mentors doing most of the actual build to the point where during inspections, the kids kepp turning to the adults present because the kids didn't have a clue as to what the functions were of the various systems when asked by the inspector (me for one event this year). I personally think only students should be allowed in the inspection area just like the question box, but that is for another post.
Big Al taught me to start an inspection by asking for the various systems' student leads and asking everyone else - especially adults - to leave the pit. If you don't want to talk to the adults, don't. I suspect you'll be pleasantly surprised. In 5 years of inspecting I can only recall 2 inspections that turned into me talking significantly to adults.
__________________


Mentor http://www.teamtitanium.org/
Reply With Quote
  #17   Spotlight this post!  
Unread 30-04-2014, 01:31
dtengineering's Avatar
dtengineering dtengineering is offline
Teaching Teachers to Teach Tech
AKA: Jason Brett
no team (British Columbia FRC teams)
Team Role: Mentor
 
Join Date: Jan 2005
Rookie Year: 2004
Location: Vancouver, BC
Posts: 1,830
dtengineering has a reputation beyond reputedtengineering has a reputation beyond reputedtengineering has a reputation beyond reputedtengineering has a reputation beyond reputedtengineering has a reputation beyond reputedtengineering has a reputation beyond reputedtengineering has a reputation beyond reputedtengineering has a reputation beyond reputedtengineering has a reputation beyond reputedtengineering has a reputation beyond reputedtengineering has a reputation beyond repute
Re: Something FRC GDC could learn from VRC GDC

Quote:
Originally Posted by Jaxom View Post
Big Al taught me to start an inspection by asking for the various systems' student leads and asking everyone else - especially adults - to leave the pit. If you don't want to talk to the adults, don't. I suspect you'll be pleasantly surprised. In 5 years of inspecting I can only recall 2 inspections that turned into me talking significantly to adults.
I like the idea here... and I know what you are getting at. I agree that most of the discussion should be with students, but to ask the adults to leave the pit area is like saying to them "You aren't part of the team. This isn't your robot. Go away."

I know you don't mean it like that... but the adults are part of the team. They've got a little bit of their heart in that robot, too. More importantly, however, the adults are the team's brain trust and memory banks. Students graduate and move on... you're lucky to get three years of useful FRC experience from a student, and never more than five. The teachers and mentors, however, can stick around for a long time. If you can educate them about the inspection process, then they can educate their team members in future years.

Work with the students. Talk to the students. Don't let adults dominate the conversation, and keep the number of people in the pit down to a safe, managable level. But please include the teachers and mentors as part of the inspection process, particularly with newer teams. The adults, as much as anyone, need to know what is going on, what you are looking for, and why you are looking for it. After all, if it weren't for those adults that you suggest kicking out of the pit, there wouldn't be any kids or robot in the pit, either.

Jason
Reply With Quote
  #18   Spotlight this post!  
Unread 30-04-2014, 02:14
Tristan Lall's Avatar
Tristan Lall Tristan Lall is offline
Registered User
FRC #0188 (Woburn Robotics)
 
Join Date: Aug 2001
Rookie Year: 1999
Location: Toronto, ON
Posts: 2,484
Tristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond repute
Re: Something FRC GDC could learn from VRC GDC

Quote:
Originally Posted by scca229 View Post
Not to mention the thread count on CD was grow exponentially due to the complaining...
It would grow for a while...then drop precipitously as teams quit.


Quote:
Originally Posted by EricH View Post
One of my favorite rules in an engineering competition (this one courtesy of SAE Aero Design) is something to the effect of: "Violations of the spirit of a rule are counted as violations of the rule."
Quote:
Originally Posted by dtengineering View Post
Both VRC and FRC do an excellent job of writing rules and replying to questions. Unfortunately neither of them defines whose version of common sense or interpretation of the spirit of the rules is to be applied.
Unless the spirit of the rule is clearly articulated and minimally ambiguous, and unless common sense is demonstrably the best interpretation available under the circumstances, then I'm firmly with Jason on this one.


Quote:
Originally Posted by scca229 View Post
I think the biggest problem is that way too many teams have engineers and mentors doing most of the actual build to the point where during inspections, the kids kepp turning to the adults present because the kids didn't have a clue as to what the functions were of the various systems when asked by the inspector (me for one event this year). I personally think only students should be allowed in the inspection area just like the question box, but that is for another post.
Quote:
Originally Posted by dtengineering View Post
I like the idea here... and I know what you are getting at. I agree that most of the discussion should be with students, but to ask the adults to leave the pit area is like saying to them "You aren't part of the team. This isn't your robot. Go away."

I know you don't mean it like that... but the adults are part of the team. They've got a little bit of their heart in that robot, too. More importantly, however, the adults are the team's brain trust and memory banks. Students graduate and move on... you're lucky to get three years of useful FRC experience from a student, and never more than five. The teachers and mentors, however, can stick around for a long time. If you can educate them about the inspection process, then they can educate their team members in future years.

Work with the students. Talk to the students. Don't let adults dominate the conversation, and keep the number of people in the pit down to a safe, managable level. But please include the teachers and mentors as part of the inspection process, particularly with newer teams. The adults, as much as anyone, need to know what is going on, what you are looking for, and why you are looking for it. After all, if it weren't for those adults that you suggest kicking out of the pit, there wouldn't be any kids or robot in the pit, either.
Once again, I agree with Jason. My inspection conversations are mainly with the students, but there are certainly occasions where speaking with the mentors appears to serve the greater good. Conversely, if the mentors appear to be driving the inspection in a direction that is counterproductive, the inspector has plenty of opportunity to employ tactics that drive the conversation back in the desired direction—for example positioning oneself conveniently and asking direct questions.

To the extent that a robot inspector is investigating possible wrongdoing, sometimes it's also appropriate to inquire in a manner that delays hearing from the people with prepared answers. (You'll get their side soon enough, but it's useful to hear multiple versions of a suspicious story to help establish veracity.)
Reply With Quote
  #19   Spotlight this post!  
Unread 30-04-2014, 02:23
DampRobot's Avatar
DampRobot DampRobot is offline
Physics Major
AKA: Roger Romani
FRC #0100 (The Wildhats) and FRC#971 (Spartan Robotics)
Team Role: College Student
 
Join Date: Jan 2012
Rookie Year: 2010
Location: Stanford University
Posts: 1,277
DampRobot has a reputation beyond reputeDampRobot has a reputation beyond reputeDampRobot has a reputation beyond reputeDampRobot has a reputation beyond reputeDampRobot has a reputation beyond reputeDampRobot has a reputation beyond reputeDampRobot has a reputation beyond reputeDampRobot has a reputation beyond reputeDampRobot has a reputation beyond reputeDampRobot has a reputation beyond reputeDampRobot has a reputation beyond repute
Re: Something FRC GDC could learn from VRC GDC

Quote:
Originally Posted by EricH View Post
To be fair, the rules were pretty clear (another thing certain folks need to work on), and if there was a question of intent/spirit, you asked the rules committee directly (and knew who they were!) and publicly, and got the same type of response back, usually within a day or so unless it was a particularly complicated one or you were being difficult. None of this "We cannot perform design reviews" non-answer (or "See the definition of possession"--which is what I just asked about!).
I really don't understand why the GDC still does this... It's ridiculous for a strategy/design you put a ton of work into to be ruled illegal at your first competition because no one bothered to clarify what the rule actually meant. And why the heck can't they say if a design as described is illegal or not? If someone's bothering to ask, it's probably because the rules aren't clear.

I get that FIRST doesn't want to answer questions in the Q and A that could be answered by just reading the manual (like we do on CD), but why not actually clarify what's said in the manual, rather than referring us to what we had a question about?
__________________
The mind is not a vessel to be filled, but a fire to be lighted.

-Plutarch
Reply With Quote
  #20   Spotlight this post!  
Unread 30-04-2014, 02:42
apalrd's Avatar
apalrd apalrd is offline
More Torque!
AKA: Andrew Palardy (Most people call me Palardy)
VRC #3333
Team Role: College Student
 
Join Date: Mar 2009
Rookie Year: 2009
Location: Auburn Hills, MI
Posts: 1,347
apalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond repute
Re: Something FRC GDC could learn from VRC GDC

Quote:
Originally Posted by EricH View Post
To be fair, the rules were pretty clear (another thing certain folks need to work on), and if there was a question of intent/spirit, you asked the rules committee directly (and knew who they were!) and publicly, and got the same type of response back, usually within a day or so unless it was a particularly complicated one or you were being difficult. None of this "We cannot perform design reviews" non-answer (or "See the definition of possession"--which is what I just asked about!).

I am not familiar with the SAE Aero series, but in Formula SAE, it is required for teams to submit a detailed analysis of their chassis design for safety and rules compliance review months before the competition. When the team arrives at competition, they just need to show the inspectors their approved SES and the inspectors only have to verify that the chassis is built to the SES for the team to pass the chassis safety section of the rules, and the team knows months ahead of time that their design will pass inspection (if they build it correctly). We are also encouraged to submit designs (including CAD images) when asking rules questions, when relevant, as we frequently have questions regarding the legality of a questionable design and it's just easier to directly ask if the design is legal and note which rules we are concerned with.
__________________
Kettering University - Computer Engineering
Kettering Motorsports
Williams International - Commercial Engines - Controls and Accessories
FRC 33 - The Killer Bees - 2009-2012 Student, 2013-2014 Advisor
VEX IQ 3333 - The Bumble Bees - 2014+ Mentor

"Sometimes, the elegant implementation is a function. Not a method. Not a class. Not a framework. Just a function." ~ John Carmack
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 01:15.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi