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

[Cothron Theiss]

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%

I am very curious as to what the three unknown's are. Also, I had completely assumed that LabVIEW would comprise the majority, or at least be the most commonly used.

[feverittm]

Another interesting statistic is the number of PID controllers.

There is some team out there with a reported 100 PID Controllers. I really don't believe this, but it is interesting. Also it shows there are 31 teams with more than 10 PID Controllers.

As was already said... interesting

[Andrew Schreiber]

Originally Posted by feverittm

Another interesting statistic is the number of PID controllers.

There is some team out there with a reported 100 PID Controllers. I really don't believe this, but it is interesting. Also it shows there are 31 teams with more than 10 PID Controllers.

As was already said... interesting

I'd be willing to bet that team is doing something funky with creating it and then (hopefully) tearing it down rather than disabling it.


I'd be interested to know if they just took the state of the robot in the last match or if they aggregated it over the season.

[Jon Stratis]

Originally Posted by Cothron Theiss

I am very curious as to what the three unknown's are. Also, I had completely assumed that LabVIEW would comprise the majority, or at least be the most commonly used.

This actually doesn't surprise me very much. Java is the language used for the AP Computer Science exam, and thus the option that is probably taught in schools the most. I'm sure many teams made the decision to go with Java for just that reason!

[BigJ]

Originally Posted by notmattlythgoe

How did you figure that out? Did I miss the "Flipped back over to secure the win" column?

I was able to find mine (forgot the row number now) by process of elimination using Rookie year (2005) -> Command-based -> No robotdrive class -> yes smartdashboard -> 2 Joystick classes -> No solenoids. At that point there was 3 or 4 left and I could pick the correct one based on number of digital ins and motor controllers.

[Jon Stratis]

Originally Posted by BigJ

I was able to find mine (forgot the row number now) by process of elimination using Rookie year (2005) -> Command-based -> No robotdrive class -> yes smartdashboard -> 2 Joystick classes -> No solenoids. At that point there was 3 or 4 left and I could pick the correct one based on number of digital ins and motor controllers.

I tried something similar to identify my team... and came up with 0 rows. I started with year and language, then filtered out by motor controllers and pneumatics I can't find any row for 2007 rookies using Java that really looks like it could even be close to ours!

[BigJ]

I tried to identify by numbers of objects as little as possible (except for things I know there was 0% chance anything was different, like Joysticks and solenoids) as I think there are some quirks with their tool. Our row had way more PIDController objects that I thought we should have, but it could have been a weird thing with a robot resetting midmatch, or etc (I don't think we were ever remaking our controllers).

[notmattlythgoe]

Originally Posted by BigJ

I was able to find mine (forgot the row number now) by process of elimination using Rookie year (2005) -> Command-based -> No robotdrive class -> yes smartdashboard -> 2 Joystick classes -> No solenoids. At that point there was 3 or 4 left and I could pick the correct one based on number of digital ins and motor controllers.

I must be having an off day. Nobody is getting my humor.

[Pault]

Originally Posted by Andrew Schreiber

I'd be interested to know if they just took the state of the robot in the last match or if they aggregated it over the season.

- Counted objects and TRUE/FALSE show the largest number of any given object used in any one match (i.e. if a Robot had 2 Encoders in match 1 and 3 Encoders in match 7, 3 will be reported). Language and Framework report what was used in the last recorded match.

Also, I am pretty surprised by the Language numbers. Unfortunately I don't have a source, but I clearly remember hearing a few years ago that the split was about 50% Labview, 30% Java, 20% C++, and a small handful of Python users.

[FlamingSpork]

Originally Posted by notmattlythgoe

I must be having an off day. Nobody is getting my humor.

I found my team's code by filtering on "Got stuck on moat" and making sure it was exactly once.

[GeeTwo]

Originally Posted by Pault

Also, I am pretty surprised by the Language numbers. Unfortunately I don't have a source, but I clearly remember hearing a few years ago that the split was about 50% Labview, 30% Java, 20% C++, and a small handful of Python users.

Many teams shift languages over the years. We helped two local teams switch from to Java (IIRC both from LabView) this year, as well as two rookie teams to start on Java. I'm sure there are teams going other directions as well.

Originally Posted by notmattlythgoe

I must be having an off day. Nobody is getting my humor.

Me too. Lythgoe says I'm nobody .

Edit -finding 3946:
with Rookie Year, Language, Framework, and minimal numbers for CANTalons,Talon SRs, and solenoids, down to 2. Several further points indicate that we're record 1603 in the table. A few interesting things learned there, most of which are confirmed as I view our source code.

[Andrew Schreiber]

Originally Posted by Pault

Answer to my question in a quote...

Ah thanks, that's what I get for skimming article.

Seems like a sub-par way to collect data as "oh we had a victor on hand for this quick fix then swap it back out to a talon when it gets in" I'd almost like to see the final state numbers for teams.


Edit: Also - I really wish this wasn't anonymized data.

[notmattlythgoe]

Originally Posted by Andrew Schreiber

Ah thanks, that's what I get for skimming article.

Seems like a sub-par way to collect data as "oh we had a victor on hand for this quick fix then swap it back out to a talon when it gets in" I'd almost like to see the final state numbers for teams.


Edit: Also - I really wish this wasn't anonymized data.

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

[PayneTrain]

Originally Posted by notmattlythgoe

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

I don't know if they didn't release it because maybe this is data we as teams never actually consented to release? I wish we knew because personally

A) Let's not pretend I read that form

B) I don't really care whether or not people know which of the 8 2000RYs that used C++ we are...

[Jared Russell]

95% sure that row 130 is 254.