[FRC Blog] The 2016 Season, by the Numbers 2

[jtrv]

Originally Posted by Conor Ryan

Coolest thing I saw:

Lang	Count	Percentage
C#	1	0.03%
C++	435	13.97%
Java	1526	49.00%
LabVIEW	1116	35.84%
Python	33	1.06%
Unknown	3	0.10%
Total	3114	100.00%

C#? Who? What? When? Where? Why?

[virtuald]

I'm quite happy that there are 33 teams using Python. I would have guessed ~15 when the season started.

[virtuald]

Originally Posted by jtrv

C#? Who? What? When? Where? Why?

https://github.com/robotdotnet/WPILib

[Thad House]

Originally Posted by jtrv

C#? Who? What? When? Where? Why?

I created the port last summer as a personal project to get better at coding and building an end to end system. Plus it got me a good look into the wpilib system. It was fun, and I personally like the language much more then java. My own team didn't use it as they wanted to stay with Java, but I did talk with the team that did, and the only problems I heard about were with the dashboard, and I'm looking into that now.

As for the where, either check my Sig, or the post above.

[nickbrickmaster]

Originally Posted by virtuald

I'm quite happy that there are 33 teams using Python. I would have guessed ~15 when the season started.

From ChiefDelphi, I thought there would be more as well.

Proud to be part of the 1%. All the judges and teams we talked to were very surprised and interested to learn that we used a unique language for programming. I'd love to see it take off more.

[catmanjake]

Originally Posted by Conor Ryan

Coolest thing I saw:

Lang	Count	Percentage
C#	1	0.03%
C++	435	13.97%
Java	1526	49.00%
LabVIEW	1116	35.84%
Python	33	1.06%
Unknown	3	0.10%
Total	3114	100.00%

What does the 3114 total mean? Is that how many teams participated in an event this year?

[team-4480]

Originally Posted by nickbrickmaster

From ChiefDelphi, I thought there would be more as well.

Proud to be part of the 1%. All the judges and teams we talked to were very surprised and interested to learn that we used a unique language for programming. I'd love to see it take off more.

We actually forget to even mention that we use Python to the judges or anyone at North Star. This was our second year using it and I guess we just were used to using the language with little to no problems so it wasn't exactly on our minds at competition(fantastic job virtuald!).

[bobbysq]

Originally Posted by notmattlythgoe

Me too. I would love to be able to correlate this to teams to see what other teams are doing.

Here's some de-anonymized data from a survey I took on /r/FRC a while back.

[GeeTwo]

Originally Posted by catmanjake

What does the 3114 total mean? Is that how many teams participated in an event this year?

That sounds about right. The sad truth is that half of the FRC teams that ever existed do not exist any more. The good news is that the longer a team manages to continue, the better its chances are to continue to continue.

[ATannahill]

Originally Posted by GeeTwo

That sounds about right. The sad truth is that half of the FRC teams that ever existed do not exist any more. The good news is that the longer a team manages to continue, the better its chances are to continue to continue.

I wouldn't go quite with half, I'd guesstimate at a third. FIRST will usually leave a gap between the last rookie of year x and the first rookie of year x+1. I know one year they skipped every other number for a certain range. This allows for if a team splits or if there is another reason to use a number from a previous year without having two teams have had the same number at a different time.

[EricH]

Originally Posted by rtfgnow

I wouldn't go quite with half, I'd guesstimate at a third. FIRST will usually leave a gap between the last rookie of year x and the first rookie of year x+1. I know one year they skipped every other number for a certain range. This allows for if a team splits or if there is another reason to use a number from a previous year without having two teams have had the same number at a different time.

And of the teams that do fold, sometimes they'll come back under a rookie number. Or under their own number for a season or two (FRC23). That can drive the team numbers up with respect to teams that have competed.

[cue Mark McLeod with the real numbers... wait, CD doesn't work that way]

[notmattlythgoe]

2363 Triple Helix should be row 861.

[marshall]

Originally Posted by notmattlythgoe

2363 Triple Helix should be row 861.

900 The Zebracorns are highly likely to be row 355.

[Greg Needel]

As a Supplier we really appreciate that FIRST released this data.


There are a couple of insights that we can gain from looking at this, which help us to make some choices about our future products and their uses.


We had some interesting thoughts, specifically related to motor controllers

The number of total motor controllers reported used is probably lower than it actually is, mainly due to the number of teams that use Y cables to power their PWM motor controllers.

The types of PWM motor controllers reported likely has some errors in it, as the report out is based on library choice in code and all of them are the same (victor, talon, SPARK, etc). The total number of SPARK's used for example is considerably less than the number that are "in the wild" which means either people used different libraries in their code or a significant portion of them are used in practice bots or for testing ( I suspect a bit of both)

There are 8 teams that show having zero motor controllers.....

The average number of controllers per robot is 7.25



I am 99% sure line 1089 is 2848

[MechEng83]

I was slightly thrown off by the lack of "encoders" considering we had 6 incremental and 1 absolute encoder, but I'm 95% sure that line 592 is us.
Most of our encoders were plugged directly into the TalonSRXs.

Not a lot of 2006 Rookie year C++ teams with no pneumatics. We definitely had more than 7 Talons on our CAN interface, though I don't remember 10.