Go to Post 'We're back to square one! and while we're at it, let's redesign square one.' - Bethie42 [more]
Home
Go Back   Chief Delphi > Competition > Team Organization
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
 
Thread Tools Rating: Thread Rating: 2 votes, 5.00 average. Display Modes
  #1   Spotlight this post!  
Unread 16-12-2011, 22:41
Anupam Goli's Avatar
Anupam Goli Anupam Goli is offline
PCH Q&A co-founder/Scouting Mentor
AKA: noops
FRC #1648 (G3 Robotics)
Team Role: Mentor
 
Join Date: Dec 2010
Rookie Year: 2008
Location: Atlanta, Georgia
Posts: 1,242
Anupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond repute
Re: Team organization issues and Build Season Schedule

Quote:
Originally Posted by Ninja_Bait View Post
Sounds good, improvement is the way forward.



Setting up a strategy is wise; it's done by many top teams. Remember that physics is your friend and that every part of the game is important until actual experience tells you otherwise. Do some math and plan a super optimal strategy.



First off, prototyping is not the same as proof of concept. LEGO and VEX are proof of concept materials. They are an easy and quick way to show that an idea is sound and will probably work in reality. Prototyping goes beyond that by requiring careful work and allowing you to optimize dimensions and prove functionality in the real environment.

Second, you can sometimes eliminate ideas without building anything. Some ideas are clearly too expensive/complex/inane, and oftentimes logic and physics (or a proof of concept) will prove that only a handful are viable.



Decide what your team is here for - building an amazing robot or changing lives? What will be better for that goal - outsourcing or engaging?



If you can't pay for a second robot, you can't pay for custom machining. Also, you shouldn't make your second robot if it's not the same as the first. Even little nuances will drastically affect code, driving and strategy. Even though the practice is nice, it will feel like a waste of time and material as everyone adjusts from practice bot to competition bot.



Wrong. True inspiration is when students choose to be good engineers because of the example of mentors and peers. It doesn't come out of good engineering, it leads to it.

As a last note: I've often felt the same way you do, which is that the team is nose-diving into a dump. Encourage these changes, but also act upon them yourself first. Crabbiness doesn't solve problems; leadership by example does. You personally can demonstrate the value of following a good engineering thought process, and others will follow when they see the advantages. Try not to overstep your bounds, however, and remember that you're doing this for the team, not for winning. Good luck with your efforts!
I sometimes refer to proof of concept as prototyping, but you are correct. I think a proof of concept would be nice before we eliminate any ideas. of course, an idea of 25 wheels would probably be shot down if we were playing logo motion, or building two arms.

Our team's goal is kind of mixed. most of the students who join robotics are already part of the magnet program here at our high school. We have multiple competition teams that they go into. Our biggest goal as a robotics team would be to take these talented kids, and allow them to go through the engineering design process and engineer an amazing creation that provides an effective solution to the problem. In order to be effective, we have to be competitive. In 2010, our entire robot was made by manually milling parts with an inexperienced first year robotics student milling the kicker and the base was made of 1010 cut by an old slave and tapped by some students. By championships, the base was tilting at a 30 degree angle and would've completely been destroyed in another few matches.

I first got into robotics as a freshmen because I wanted to build a robot. I participated in the BEST competition, which does that. However, when I worked with FRC in 2009 (my rookie year), I was amazed at the clean cuts and CNC cut parts that were on our robot, and how it went from concept, prototype, CAD and finally to the robot. I didn't make many things other than prototype a battery mounting system that year, but i did not have any less feeling of satisfaction of creating something from when I fabricated all of the parts in the BEST robotics competition to getting everything fabricated by CNC or waterjetted by a sponsor.

I don't know how well a compromise would work on this, but I see people wanting to fabricate parts of the robot. For complex pieces, we could use the CNC or get it cut outside by one of our sponsors, but for putting the base together or creating an end effector, we could have students fabricate parts for that.


With the 2nd robot, i've heard that you will never have an exact copy of the robot, but if the drivetrain and simulated weight is similar, you can still use it to drive around the field, or if you are using an arm, you make one out of wood that goes the same speed as the one made before. For the past 2 years, we've only been putting out two drivers, me and another person (who is a senior this year). We've only been chosen because of our Rules knowledge and natural talent. natural talent only took us so far. In 2010, we had a good scoring robot. But because of a lack of practice, we couldn't go over the bump, and we couldn't score as effectively, because we didn't have aligning with the ball down to an art. We may not have had much experience still with getting over the bump with an inexact copy of the robot, but we could still practice lining up with the ball and running scenarios of other teams playing defense. Also, practice builds the relationship among our drivers. I personally don't have a good relationship with our other driver, but if we were to practice, form new strategies, and run plays, we can think alike and we don't have to disagree on how to approach the game piece

I don't want to cause internal strife within our club, but I also want to make sure the overall leader understands my arguments and why I think they are beneficial to the team as a whole and to ourselves.

Also, I agree with your modification of my inspiration definition. What was I thinking before?
__________________
Team 1002: 2008-2012
Team 1648: 2012-2016
Georgia Tech Class of 2016
Reply With Quote
  #2   Spotlight this post!  
Unread 16-12-2011, 23:37
Anupam Goli's Avatar
Anupam Goli Anupam Goli is offline
PCH Q&A co-founder/Scouting Mentor
AKA: noops
FRC #1648 (G3 Robotics)
Team Role: Mentor
 
Join Date: Dec 2010
Rookie Year: 2008
Location: Atlanta, Georgia
Posts: 1,242
Anupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond repute
Re: Team organization issues and Build Season Schedule

From the replies in this thread and talking to some of my mentors, I've gathered that

-Spending more time on the game plan will be beneficial
-Proof of concept for ideas not explored before would be great to aid in the presentation
-do the math and physics calculations behind the design for the presentation
-Prototype once a design is chosen. Determine correct gear ratios, the exact way the system will be powered

I've decided to promote the idea that with large laborious parts, we can use our sponsors to machine. For precise slots and holes, we can use the CNC. For cutting pieces of 1010, and creating a housing for electronics, panels, and housing for end effectors, we can have students precisely cut and assemble the parts. Measure Twice, cut once! This allows the students to experience both professional engineering, and allows them to experience the fabrication process.

Also, with the 2nd robot, I'll try to ask our sponsors for any spare materials they may have, but if we do not have much, We'll try to use the kitbot frame (We have spares lying around), and we'll recreate our drive train and add weight and if we can, build our manipulator out of wood. This will not be for heavy practice, but for the drive team to work on strategies and grow the trust in eachother. The drive team has to be a single entity.

Are there any comments on these?
__________________
Team 1002: 2008-2012
Team 1648: 2012-2016
Georgia Tech Class of 2016

Last edited by Anupam Goli : 16-12-2011 at 23:39.
Reply With Quote
  #3   Spotlight this post!  
Unread 16-12-2011, 23:52
ghostmachine360's Avatar
ghostmachine360 ghostmachine360 is offline
Kyle J. Fender
AKA: Kyle J. Fender
FRC #1002 (CircuitRunners Robotics)
Team Role: Mentor
 
Join Date: Dec 2010
Rookie Year: 2007
Location: Marietta, Georgia
Posts: 372
ghostmachine360 has a reputation beyond reputeghostmachine360 has a reputation beyond reputeghostmachine360 has a reputation beyond reputeghostmachine360 has a reputation beyond reputeghostmachine360 has a reputation beyond reputeghostmachine360 has a reputation beyond reputeghostmachine360 has a reputation beyond reputeghostmachine360 has a reputation beyond reputeghostmachine360 has a reputation beyond reputeghostmachine360 has a reputation beyond reputeghostmachine360 has a reputation beyond repute
Re: Team organization issues and Build Season Schedule

Quote:
In 2010, our entire robot was made by manually milling parts with an inexperienced first year robotics student milling the kicker and the base was made of 1010 cut by an old slave and tapped by some students. By championships, the base was tilting at a 30 degree angle and would've completely been destroyed in another few matches.
We use a vertical bandsaw, not an old slave. Because slavery is illegal, and immoral.

But seriously, these are good points and a good direction to head towards for the upcoming season.
__________________
Member of the Rotten Fruit Alliance
2013, 2015, & 2016 Fantasy FIRST Elgin Clock Award Winners [RFA]
2015 & 2016 Fantasy FIRST Champions [RFA]
GeorgiaFIRST Advisory Board & District Planning Commitee Member
SPSU Class of 2016: Robotics Engineering Major
GeorgiaFIRST FRC/FTC Emcee, FTC Head Referee, & FRC Referee
2010 CMP FRC Dean's List & 2010 Peachtree DLA Finalist
Reply With Quote
  #4   Spotlight this post!  
Unread 17-12-2011, 00:25
akoscielski3's Avatar
akoscielski3 akoscielski3 is offline
Mentor (1114), Alumni (772)
AKA: Aaron Koscielski
FRC #1114 (Simbotics)
Team Role: Mentor
 
Join Date: Jul 2010
Rookie Year: 2006
Location: LaSalle, Ontario, Canada
Posts: 1,066
akoscielski3 has a reputation beyond reputeakoscielski3 has a reputation beyond reputeakoscielski3 has a reputation beyond reputeakoscielski3 has a reputation beyond reputeakoscielski3 has a reputation beyond reputeakoscielski3 has a reputation beyond reputeakoscielski3 has a reputation beyond reputeakoscielski3 has a reputation beyond reputeakoscielski3 has a reputation beyond reputeakoscielski3 has a reputation beyond reputeakoscielski3 has a reputation beyond repute
Re: Team organization issues and Build Season Schedule

I have to agree that sending out parts to some companies, and making some less complicated parts (or easy to machine) yourself, would be very beneficial. This will also help them understand how much time/effort you have to put into making a single part (or an assembly).

Being "gentle" about bringing these ideas up is a HUGE factor. It is hard not to offend people sometime's, even if you don't try to. People may think that you didn't like how they ran the team or how they machined parts if you are outsourcing them.

Though i have never built a second robot I believe it is a really good idea. As being a driver i understand how long it takes to get use to the controls of the robot. Usually it takes about 1 competition and lots of nights of thinking you are driving to understand the controls as if it was natural. But if i had a second robot i wouldn't need that 1 competition, i would already know the controls almost perfectly, I might need the practice day to fully get use to the field though.

Regarding your Communication between you and your fellow driver, it needs to be almost perfect. Me and my fellow driver are good friends now, and we know exactly what the other person's next move is, without even talking usually. There are a few times that we had conflict of decisions, but that may be because we developed slightly different strategies. Ex. in last 30 seconds last year i wanted to raise the elevator for top row and put circle on triangle spot, he wanted to put the circle on middle where circle goes. In the end we purposely dropped the tube to go deploy the minibot. Either way nothing would have changed, just another judgement call.

My team is also in the same boat you are. I have tried to push the designing for 2 years now and i think i finally got them to notice how important it is. What i did was design a full chassis, present it to them, and built it, proving that Design is VERY beneficial to the team.

Good luck this year and hope this helps
__________________
Hall of Fame Team 1114 Simbotics
2013-Present
Host of Simbot Solidworks Series
Team 772 Sabre Bytes
2010-2013

Dean's List Finalist 2013 Waterloo Regional
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 10:38.

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