Index of Robot Code Releases

[Cel Skeggs]

I've put together a list on GitHub of all of the robot code releases I could find: https://github.com/flamingchickens15...tware-releases

(See this thread for the short conversation about creating it.)

I've tried to add all of the Chief Delphi posts I can find, but I've probably missed a few. You can either post additions here or pull-request them directly into the GitHub repository - just make sure to follow the conventions used by the other entries on the list!

If you don't like how I summarized your team's release (I spent about 30 seconds on each), just send a pull-request to fix it!

A couple of teams have added themselves to the list on GitHub without posting anywhere else - I'm not entirely certain that's sufficient to meet R13, at least in the spirit of the rule. I'd recommend creating a Chief Delphi thread if you don't already have one, and then pull-request your team onto the list.

Thoughts or additions?

[virtuald]

RobotPy teams are encouraged to add themselves to our community list, which includes links to code as well.

http://robotpy.github.io/community/

[jojoguy10]

Would it be possible to note which language they're in? That would be awesome!

[Christopher149]

Here is 857's code for 2015. Java.

I don't really have an interesting descriptive label like most of the others.

[z_beeblebrox]

Our 2015 Java robot code can be found here.

[Jalerre]

Here is our team's (4965) Github page. Java

[Cel Skeggs]

Originally Posted by jojoguy10

Would it be possible to note which language they're in? That would be awesome!

Done!

Also, everyone else: please send me the link to your Chief Delphi threads! I'm not convinced that my listing is sufficient in spirit to count as publicly releasing your code, and it doesn't give people a chance to ask questions, so creating a Chief Delphi thread as well would be great!

[Tom Bottiglieri]

This is really cool! Thanks for putting this together.

[kyle_hamblett]

Here is 1073's robot code for 2015 in Java.

[Cel Skeggs]

Originally Posted by Tom Bottiglieri

This is really cool! Thanks for putting this together.

Of course!

Some quick statistics on the languages used:

LabVIEW:             8 ========
C++/WPILib:          3 ===
C++/Command-Based:   5 =====
Java/WPILib:         3 ===
Java/Command-Based: 14 ==============
Java/CCRE:           1 =
Python:              2 ==

[Danimal!]

Here is 4118's repository. The primary contribution is a completely student-designed teach and play program written in C++.

https://github.com/ironmig/RiptideRecorder

[page2067]

So this is great - Really cool to see the teams adding to this database -

If anyone has questions on how to comply to the rule?
I think it is clear that posting here would comply - maybe with a separate CD post for extra measure.
We can have questions or misgivings over the rule, but once the decision is to comply, well comply all the way!

So we should, I would think, expect maybe 1000 out of ~3000 teams (is 1/3 too high?), that re-use some of their code, or use it as a starting point, to post here?
Or just to post some cool code, that otherwise will never be fully appreciated.
How cool will it be to have that to scroll through and learn from!

[AWoL]

Thanks for reminding me to finally get to this four days before build season!
I posted the code release on CD here and the code is on GitHub here. If you could summarize my description of the notable features, or just include them in whole, that would be great.

[feverittm]

OK Team 997 will just the club. You can find our code for our 2015 robot "Atlas"

https://github.com/Team997Coders/2015GC

Nothing special here. It does include our changes to support the 2016 Beta code. Only minor changes to our main code we used during the season.

Hope some will find it useful.

[Cel Skeggs]

Originally Posted by page2067

So this is great - Really cool to see the teams adding to this database -

If anyone has questions on how to comply to the rule?
I think it is clear that posting here would comply - maybe with a separate CD post for extra measure.
We can have questions or misgivings over the rule, but once the decision is to comply, well comply all the way!

So we should, I would think, expect maybe 1000 out of ~3000 teams (is 1/3 too high?), that re-use some of their code, or use it as a starting point, to post here?
Or just to post some cool code, that otherwise will never be fully appreciated.
How cool will it be to have that to scroll through and learn from!

Good thoughts, but as the single person maintaining this repository, I'm not certain I want to have to process 1000 entries manually.