Go to Post The animation is just a pretty tool to help outsiders understand the game; the manual is for me, the animation is for my grandmother. - JVN [more]
Home
Go Back   Chief Delphi > Technical > Programming
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 06-11-2012, 20:21
jvriezen jvriezen is offline
Registered User
FRC #3184 (Burnsville Blaze)
Team Role: Mentor
 
Join Date: Jan 2010
Rookie Year: 2008
Location: Burnsville, MN
Posts: 643
jvriezen has a reputation beyond reputejvriezen has a reputation beyond reputejvriezen has a reputation beyond reputejvriezen has a reputation beyond reputejvriezen has a reputation beyond reputejvriezen has a reputation beyond reputejvriezen has a reputation beyond reputejvriezen has a reputation beyond reputejvriezen has a reputation beyond reputejvriezen has a reputation beyond reputejvriezen has a reputation beyond repute
Too many programmers ?

We had a team meeting tonight -- our team is having tremendous growth (approx 50-60 total) , and we are going from a handful of programmers last year to maybe 20 people expressing interest in programming this year. Not a lot of experience (either inside or outside FRC that we know of yet)

Any tips on how to keep so many programmers involved? I can't see how we can manage a programming team where everyone is going to contribute to the competition robot... We are having some LabView training classes/seminars once every two weeks thru the end of the year, but the Mentors are not very far ahead of most of the students. We have one student who is ahead of everyone and has been lead programmer for pretty much the last three years.
__________________
John Vriezen
FRC, Mentor, Inspector #3184 2016- #4859 2015, #2530 2010-2014 FTC Mentor, Inspector #7152 2013-14
  #2   Spotlight this post!  
Unread 06-11-2012, 20:29
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,756
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Too many programmers ?

It may be useful to have training, challenges, or competitions based on the new simulation features. More details are on the 1718 beta site.

Greg McKaskle
  #3   Spotlight this post!  
Unread 06-11-2012, 20:32
joelg236 joelg236 is offline
4334 Retired Mentor & Alumni
AKA: Joel Gallant
no team
Team Role: Mentor
 
Join Date: Dec 2011
Rookie Year: 2012
Location: Calgary
Posts: 733
joelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond repute
Re: Too many programmers ?

We are in a similar situation, although I can't say we have 20 people interested, we have far more than needed.

As the lead programmer, I am assuming that interest will slowly fade away, and it should end up being 3-5 people. It's definitely not doable to have 20 people contribute to the robot code.

Possibilities if they don't fade away:
- Make a core group for robot code, and let the others work on other projects (apps, website, etc.)
- Make the robot code a 'competition' of sorts. Have 2 groups that are competing to make better robot code, and at the end combine the best parts of the two.
- Although this is the least favorable, it's certainly possible to put a cap on how many programmers are allowed on the sub-team. If a lot of them have little experience, I'm sure they'd have just as much fun doing CAD or machining or anything else.
__________________
All opinions are my own.
  #4   Spotlight this post!  
Unread 06-11-2012, 20:37
Sean Raia's Avatar
Sean Raia Sean Raia is offline
Curious spectator & alumn
no team
 
Join Date: Oct 2008
Rookie Year: 2008
Location: PA
Posts: 436
Sean Raia has a reputation beyond reputeSean Raia has a reputation beyond reputeSean Raia has a reputation beyond reputeSean Raia has a reputation beyond reputeSean Raia has a reputation beyond reputeSean Raia has a reputation beyond reputeSean Raia has a reputation beyond reputeSean Raia has a reputation beyond reputeSean Raia has a reputation beyond reputeSean Raia has a reputation beyond reputeSean Raia has a reputation beyond repute
Re: Too many programmers ?

Our team had this exact problem in the 2011 season.
The fact of the matter is, having 30% of the team as programmers is overkill. You should try to engage students in other fields that may be of interest, (namely CAD, Website).
If you still find yourself with a large group of dedicated programmers then have some of the new guys pair up with the veterans and assign them a task, make sure they document everything they do (with a large group of students this is critical).
Either way, students will mingle in and out of groups throughout the season.
Good luck!
  #5   Spotlight this post!  
Unread 06-11-2012, 22:09
Joe Ross's Avatar Unsung FIRST Hero
Joe Ross Joe Ross is offline
Registered User
FRC #0330 (Beachbots)
Team Role: Engineer
 
Join Date: Jun 2001
Rookie Year: 1997
Location: Los Angeles, CA
Posts: 8,600
Joe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond repute
Re: Too many programmers ?

Writing a scouting system is another thing that extra programmers can work on.
  #6   Spotlight this post!  
Unread 06-11-2012, 22:12
Gregor's Avatar
Gregor Gregor is offline
#StickToTheStratisQuo
AKA: Gregor Browning
no team
Team Role: College Student
 
Join Date: Jan 2012
Rookie Year: 2012
Location: Kingston, Ontario, Canada
Posts: 2,447
Gregor has a reputation beyond reputeGregor has a reputation beyond reputeGregor has a reputation beyond reputeGregor has a reputation beyond reputeGregor has a reputation beyond reputeGregor has a reputation beyond reputeGregor has a reputation beyond reputeGregor has a reputation beyond reputeGregor has a reputation beyond reputeGregor has a reputation beyond reputeGregor has a reputation beyond repute
Re: Too many programmers ?

Try and find out why they are interested in programming as opposed to another subteam. If someone wants to program because their friend wants to program, and their friend is only there because the first kid wants to program, look at that, you can already relocate 2 students to another subteam.
__________________
What are nationals? Sounds like a fun American party, can we Canadians come?
“For me, insanity is super sanity. The normal is psychotic. Normal means lack of imagination, lack of creativity.” -Jean Dubuffet
"Insanity is doing the same thing over and over again and expecting different results." -Albert Einstein
FLL 2011-2015 Glen Ames Robotics-Student, Mentor
FRC 2012-2013 Team 907-Scouting Lead, Strategy Lead, Human Player, Driver
FRC 2014-2015 Team 1310-Mechanical, Electrical, Drive Captain
FRC 2011-xxxx Volunteer
How I came to be a FIRSTer
<Since 2011
  #7   Spotlight this post!  
Unread 07-11-2012, 06:52
Jon Stratis's Avatar
Jon Stratis Jon Stratis is offline
Mentor, LRI, MN RPC
FRC #2177 (The Robettes)
Team Role: Mentor
 
Join Date: Feb 2007
Rookie Year: 2006
Location: Minnesota
Posts: 3,835
Jon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond repute
Re: Too many programmers ?

I would break them into 3 teams: robot, scouting, and website. That will let them all stay involved, while cutting down the number of people working on any single project.
__________________
2007 - Present: Mentor, 2177 The Robettes
LRI: North Star 2012-2016; Lake Superior 2013-2014; MN State Tournament 2013-2014, 2016; Galileo 2016; Iowa 2017
2015: North Star Regional Volunteer of the Year
2016: Lake Superior WFFA
  #8   Spotlight this post!  
Unread 07-11-2012, 08:20
AsianRookie AsianRookie is offline
Registered User
AKA: Steven/Tim
FRC #0321 (Robolancers)
Team Role: Programmer
 
Join Date: Oct 2012
Rookie Year: 2007
Location: Philadelphia
Posts: 31
AsianRookie is an unknown quantity at this point
Re: Too many programmers ?

Oh man you havent seen nothing yet. Our team has over 100 people and 27 of them are programmers. When I say programmers I mean only programming the robot. We already have a cad team, webdesign, videography and photography. Right now we are going FTC and we have 2 teams. I basically split up the programmers and told them to write their own pseudo-code. After that I would split them up into sub teams to write their part of the code, like 2-3 people would write the drive code. I still havent figured out a plan for FRC yet. I hope this helps.
  #9   Spotlight this post!  
Unread 07-11-2012, 09:29
ttldomination's Avatar
ttldomination ttldomination is offline
Sunny
no team
Team Role: Mentor
 
Join Date: Mar 2007
Rookie Year: 2007
Location: Roanoke, TX
Posts: 2,066
ttldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond repute
Re: Too many programmers ?

Quote:
Originally Posted by joelg236 View Post
As the lead programmer, I am assuming that interest will slowly fade away, and it should end up being 3-5 people. It's definitely not doable to have 20 people contribute to the robot code.
+1 to this. People generally like the 'idea' of programming, and not really programming itself. Which isn't to say that you won't have 20+ dedicated programmers, that's definitely a possibility. This is just to say that it probably won't go down that way.

- Sunny G.
  #10   Spotlight this post!  
Unread 07-11-2012, 09:39
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,125
Ether has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond repute
Re: Too many programmers ?

Quote:
Originally Posted by joelg236 View Post
It's definitely not doable to have 20 people contribute to the robot code.
http://en.wikipedia.org/wiki/The_Mythical_Man-Month


  #11   Spotlight this post!  
Unread 07-11-2012, 10:37
joelg236 joelg236 is offline
4334 Retired Mentor & Alumni
AKA: Joel Gallant
no team
Team Role: Mentor
 
Join Date: Dec 2011
Rookie Year: 2012
Location: Calgary
Posts: 733
joelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond reputejoelg236 has a reputation beyond repute
Re: Too many programmers ?

Quote:
Originally Posted by Ether View Post
Interesting read.
__________________
All opinions are my own.
  #12   Spotlight this post!  
Unread 08-11-2012, 09:17
EricS-Team180's Avatar
EricS-Team180 EricS-Team180 is offline
SPAM, the lunchmeat of superheroes!
AKA: Eric Schreffler
FRC #0180 (SPAM)
Team Role: Engineer
 
Join Date: Apr 2002
Rookie Year: 2001
Location: Stuart, Florida
Posts: 561
EricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond repute
Re: Too many programmers ?

Quote:
Originally Posted by Jon Stratis View Post
I would break them into 3 teams: robot, scouting, and website. That will let them all stay involved, while cutting down the number of people working on any single project.

This year I expect up to 8 returning, 2nd year programmers and at least 1 rookie (we had all rookies last year). I am planning on a multiple project approach similar to Jon's.

Eric
__________________

Don't PANIC!
S. P. A. M.
  #13   Spotlight this post!  
Unread 08-11-2012, 13:54
Doug G's Avatar
Doug G Doug G is offline
Coach / Teacher
FRC #0701 (Robovikes)
Team Role: Coach
 
Join Date: Dec 2002
Rookie Year: 2001
Location: Fairfield, CA
Posts: 880
Doug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond repute
Re: Too many programmers ?

We typically have 9-10 interested programmers each year on a team of about 32. So we usually split 3-4 of them into programming the scouting system, 3-4 basic robot code, 3-4 of them specialized code for vision, dashboard, autonomous. It usually ends up as one student in each of those three areas doing most of the coding, while the others learn and help diagnose/troubleshoot.
__________________
Work Hard, Have Fun, Make a Difference!

  #14   Spotlight this post!  
Unread 08-11-2012, 23:47
SuperS_5's Avatar
SuperS_5 SuperS_5 is offline
[Certified LabVIEW Developer]
FRC #1219
 
Join Date: Dec 2010
Rookie Year: 2010
Location: Canada
Posts: 140
SuperS_5 will become famous soon enoughSuperS_5 will become famous soon enough
Re: Too many programmers ?

I too expect some, if not many of that initial group to drift into other sub-groups, or just milling about. Large numbers of programmers can, and do work on single projects regularly. Although it is less common for LabVIEW enviornments compared to the other languages, I worked on one LabVIEW project where it would have been very easy to have 30+ people working on it. The biggest challenge will be to separate the various tasks very discretely, and with very clear chains of communication.
Source control will be of interest to you, and I highly recommend it to all teams anyways. With GitHub just allowing special help to FRC teams, I would highly recommend you take a look. Reference

I would suggest these modules as a starting point:
  • Vision
    • recognition
    • targeting
    • tracking/PID
  • Drive systems (This will include acceleration controls, etc.)
  • Various sensors (May be to small to split up, but any processing you would do with these)
  • Dashboard
    • Probably the easiest to split up into smaller tasks if you decide on advanced driver controls.
  • Practice field testing procedures
    • Just like a checklist for the mechanical side, you will want to test various features. You will have to come up with ways to test and validate these features. (Re-testing for bugs is critical, as a small change can always introduce errors in code that was working before.) I would personally put several people here if you can afford too. Have these people watch the other coders, and figure out what needs to be tested, then actually design these tests.)
  • documentation (for the mentors, drivers, and the following year's team)
    • (This could probably be the same checklist people)
  • non-competition code, and features. (Things that you would want to do for advertising your robot in your community.)
    • Website
    • Mobile phone stuff to communicate to the robot. (This is eye-candy like, but very effective)
  • I'm sure you will think of many more largish modules.

I also like the suggestion of giving a bit of a mini competition to the programmers. This will get their productive juices going, and weed out the non-programmers. (IE. The ones that are just tagging along. Identifying these kids will let you know who will need help to figure out their roles in the team. Ideally keeping them in the team instead of them drifting away.)

Good Luck!
__________________
Mike B
  #15   Spotlight this post!  
Unread 10-11-2012, 16:38
MAldridge's Avatar
MAldridge MAldridge is offline
Lead Programmer
AKA: Rube #1
FRC #0418 (LASA Robotics)
Team Role: Programmer
 
Join Date: Jan 2011
Rookie Year: 2010
Location: Austin
Posts: 117
MAldridge will become famous soon enoughMAldridge will become famous soon enough
Re: Too many programmers ?

I would suggest that if you have one person who has programmed the robot before, keep them on it. Then take the top 3 from the rest, and have them 'shadow' the programmer so that they can see how it all works, and the lead can hand off small projects to them, such as compressor code or the like (assembla has free perforce hosting which makes this easy).

I would say that if they haven't programmed before, you will see at least 50% drop off the programming group, as it has what a friend once described as a 'vertical learning curve.'

Also: put people at work learning with some of the new robot simulator code, but only if you have full mechanical teams already. I am one of the lead programmers for my team, and I am speak from experience that labview is difficult to learn if you haven't programmed before, but I will always try and steer programmers in training towards mechanical during build season if it will get the robot to me faster for debugging.
__________________
'Why are you a programer?' --Team Captain
'Because the robot isn't complicated enough!' --Me
Closed Thread


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 02:26.

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