Go to Post It sounds like "whirr" if you do it right, and "clack clack grunge snap @$@%^!!" if you don't. - dtengineering [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
  #1   Spotlight this post!  
Unread 27-01-2017, 21:05
s-neff's Avatar
s-neff s-neff is offline
Registered User
AKA: Sam
FRC #0841 (Biomechs)
Team Role: Mentor
 
Join Date: Apr 2016
Rookie Year: 2009
Location: California
Posts: 49
s-neff has much to be proud ofs-neff has much to be proud ofs-neff has much to be proud ofs-neff has much to be proud ofs-neff has much to be proud ofs-neff has much to be proud ofs-neff has much to be proud ofs-neff has much to be proud ofs-neff has much to be proud of
Re: Team Update 6

Quote:
Originally Posted by Kevin Sevcik View Post
Pretty sure there's no such thing as an out of order rotor penalty.
Accurate. No incentive != penalty, apologies for the misinformation.
There *is* a penalty H14 for starting a rotor by any method besides turning the crank, which covers most of the rest of the 'creative gear scoring'
Quote:
...The only reasonable case for placing gears out of order is a highly choreographed autonomous
Doesn't this get nope'd by the same logic? [must activate rotor 1 to start counting rotations on rotor 2...] Maybe I'm misunderstanding the proposed autonomous.
__________________
Fun:
Mentor - Team 841 (2015 - ? )
Mentor - Team 4 (2013 - 2014)
Student - Team 192 (2009 - 2010)
Work:
SunPower Systems, Product Engineering - Utility Power Plants (2015 - ? )
BSci, Mechanical Engineering, UCLA (2010-2015)
Reply With Quote
  #2   Spotlight this post!  
Unread 27-01-2017, 22:38
Kevin Sevcik's Avatar
Kevin Sevcik Kevin Sevcik is offline
(Insert witty comment here)
FRC #0057 (The Leopards)
Team Role: Mentor
 
Join Date: Jun 2001
Rookie Year: 1998
Location: Houston, Texas
Posts: 3,758
Kevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond repute
Send a message via AIM to Kevin Sevcik Send a message via Yahoo to Kevin Sevcik
Re: Team Update 6

Quote:
Originally Posted by s-neff View Post
Doesn't this get nope'd by the same logic? [must activate rotor 1 to start counting rotations on rotor 2...] Maybe I'm misunderstanding the proposed autonomous.
My personal 3 gear auton plan:
1. Fastest delivery to center peg, Pilot A lifts gear and hands to PB or sets near PB.
2. PB lifts and grabs gear with second fastest delivery. (You should know which this is.)
3. PB places both gears, finishing around 10-12s into match. And starts cranking for dear life.
4. At some point before (15 - 3 cranks) seconds, Pilot A has lifted last and slowest gear and slotted into Rotor 1.

The idea is that Rotor 2 is the slowest part of the process. If you can start it first and feed it the fastest two gears, you probably have the best chance at starting both Rotors.

Honestly, sans team this year I have nothing to ground my speculations, thus my musings about 3 gear autons and gear count deception potentially playing a role at very high levels.

Siri,
I'll admit that a completely literal reading of that section with new wording could mean that the 10 second timeout doesn't apply to any rotor past the next unengaged one. Which would make this possible, assuming no auton rotors:
1. Collect 5 gears + reserve.
2. Install on Rotor 4, spin thrice.
3. Remove, install on Rotor 3, spin thrice.
4. Install 2 leftover on Rotor 2, spin thrice.
5. Install next 6 gears on Rotor 4.
6. Install last, 12th gear on Rotor 1.
7. Rotors 2-4 engage instantly. Or within 3 PLC cycles.

That just seems ridiculous and would make the 10 second timeout pointless. So I'm assuming the GDC is just poor at fully defining the Rotor behavior in prose. It'd be easier for me if they just posted that segment of the FMS code, but that's probably not going to happen.
__________________
The difficult we do today; the impossible we do tomorrow. Miracles by appointment only.

Lone Star Regional Troubleshooter
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 03:06.

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