(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.
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!
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!
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.
Beast Robotics, Team 2202’s code for Recycle Rush is available at:
Code is in C++/WPILib. It was the first year we used mecanum drive.
The team is also in the process of implementing token commands. Kind of like an interpreter. You provide a table of commands, and the program executes them.
In 2015, the team substantially modularized most of the functions which are called by the main process. In 2016, we hope to rewrite the main process to be a command interpreter that will then call each independent module at the appropriate time.
In that case, I would recommend getting additional people to help you, particularly if you made the list without planning on it growing to a substantial size. That or, ideally, using a wiki or something in The Blue Alliance instead (for ease of editing, and unity with other information, respectively)
I think the blue alliance would be the ideal place for this sort of thing. There’s a pull request that I saw that has inclusion for links to team’s github accounts, they might be open to this sort of thing too.
Having a single flat list will get unwieldly very quickly.
Nothing special. Tried introducing the NavX, but it was still in beta, so we decided not to use it at Worlds. We also implemented stops on our lift and a limit switch on the carriage so that it would know where it was (which “level”).
