Just curious what other teams using Java are at. We have about ~1800 at the moment.
Wow!!!
we have about 140! Why is your code so complex?
oh btw we havent included our autonomy and deployment yet!::ouch::
We made wrapper classes for most of our sensors and control devices so we can get the most use out of the information they provide, we have field oriented swerve drive with several driving modes, many automated processes to make the driver’s job more straightforward and less concerned with details, and quite a few extra features that we are very excited about, but are not to be named until our first regional. 
All our code put together is ~700 lines. But the main robot class is only ~120.
Drive programming is about 500 of those lines. 
Now the question here is: what are you more proud of? A ton of complex code, or a very streamline one? Now I am not saying a project that consists of thousands of lines are not efficient, but chances are at this level, it is not efficient…
We currently have about 1500. I probably have to go back and streamline everything.
Edit: I would compare that to being big and slow or being a petite sprinter. Which one will you really be proud of?
Our 2010 robot had about ~3500 lines of code spread across ~20 Java source files. It’s interesting to note that the files SwerveModule.java and Config.java each had a total of 228 lines, the same as our team number.
This season is still a work in progress, but when it’s all done I’d expect only around half of that.
I’m proud of elegant code, that successfully, consistently, and effectively completes the job it was made to do. I’m not encouraging over-complex, or bloated code, but I strongly believe in code that gets the job done, regardless of how many lines it takes.
So to answer your question, I’d be proud of whoever wins the race 
Well you and I have totally different mentalities then. I am going to use inline assembly next year to squeeze out more juice and performance from the cRio. :eek: I know I sound crazy, but I love the low level. I kind of regret using Java. I had to because no one knew C++. I’ll go with my wishes before I graduate.
2010 season we had 11,358 lines. 3,036 of those were comments. EDIT: 96 Framework source files, 7 Robot specific files.
2011 season uses the same core codebase of 9,571 lines, 2,749 of which are comments.
Sounds like a lot of bloat, but its not. All together it makes for a really elegant system with abstraction and events and so on–
http://code.google.com/p/grtframework/
I have only 600 lines of code including my various wrappers.
The Reason why is that i use this formatting for eveything
type some_function(type var) {
do_funky_crap();
}
Woah, how did you manage to find the time to code that? Pretty impressed.
are any of you guys using CAN?
heh, time… well actually it didn’t take that long in that you can generate some of the code, and then also it carries over year to year so once you have the framework you only add a few hundred/thousand onto it specific for each year.
btw, grtframework has/uses CAN, complete with the neat jag closed loop mode.
Some interesting stats about our code.
Java.
6 Coders.
1,721 Lines of code total.
Average of 286.8333333 lines per coder
8 Packages
Average of 2.625 files per package
Average of 215.125 lines per package
21 files total
Average of 3.5 files per coder
Average of 81.95238095 lines per file
Interesting facts:
Our neatest code to date
Our first year with our code online
Our Highest number of programmers this year(up 3 from last year)
Our Highest number of source files and packages
Our code: (Will be revised up until our last match!)
http://code.google.com/p/frc399-2011-code-james-bot/
Wow, I’m surprised at how many lines of code you all have. I suspect that there is some amount of bias here (i.e. the teams with the most code are the most likely to be hanging out on CD after ship…)
We decided to use Java as all our development computers are on Linux (personal computers) (next year, we might use the new universal C++ development system).
I knew from a previous development experience that with Java, if you aren’t extremely careful, you’ll end up with so-called “spaghetti and meatball” code (i.e. an object-oriented mess). Therefore, I took the time to carefully lay out our classes, which probably added a few lines to the code.
In comparison to those with swerve drives, however, we do have a very simple bot (but a swerve drive doesn’t use up that much code relative to a tank drive – my lego swerve drive has 238 lines total).
We have 513 lines total this year (at the moment). One coder contributed 11 lines of code, the other (me) contributed the other 502 (I’m the only experienced coder on my team, and the other coder rarely came to build meetings).
Good luck to everyone at regionals.
I contributed a line of code when I visited my team a week or so ago, but deleted it after because it didn’t do anything.
Actually, “spaghetti code” usually refers to unstructured code that uses things like gotos, which doesn’t exist in Java. It’s harder to write spaghetti code in java than in languages such as C++ (at least for some people, I guess).
After a quick number crunch, we’re up to 757 lines of code. 
This is the first time I’ve been in our workshop since the robot shipped. It seems empty…
Actually, “spaghetti code” usually refers to unstructured code that uses things like gotos, which doesn’t exist in Java. It’s harder to write spaghetti code in java than in languages such as C++ (at least for some people, I guess).
Yeah, I had trouble understanding the various phrases. My understanding is that “spaghetti and meatball” code is messy object-oriented code.
Maybe “ravioli code” is the term I was looking for.
our team has around 1000 with approximately >75% of that commented out.
thats an average of around 1000 per programmer
and about 15% of the comments are actually useful code while the rest is mainly failed experiments and debugs