2010 Control System Getting Started

[Greg McKaskle]

I believe that is the normal procedure for things that WPI presents, and I believe they are assisting with the SW related presentations.

Greg McKaskle

[Kims Robot]

I just wanted to add that a lot of the results of the Beta test may not be in documentation format. How many teams that are implementing advanced traction control go out and use someone else's code? Its not cut & paste, and the differences between 2008 & 2009 coding style may not be that different.

I see the biggest benefit of the beta test being the experienced users that come out of it. Last year 1511 helped 340 Beta test, and consequently the two teams were able to get all of the Rochester area teams (20+) up and working on the system relatively quickly. Additionally 3 of the 1511 programming mentors (including a labview guy), instead of helping their own team make bigger and better and more perfect code, left the code to the kids at competition and went off and helped other teams with the control system at all 3 of our events, and traveled to a 4th that was in need of help. You can bet that is VERY likely to happen again... and honestly was much less likely to happen if they weren't part of the Beta test.

It is probably very hard to sit on the outside and see very little released to the public, but a lot of what is being done is working through tedious and annoying bugs... and what do you care about the bugs if they are going to be gone before you get there? Could there be more documentation released? Likely true, but there are some rules FIRST imposes, and there are the hours in the day limits (making something readable/useful for others is much harder than just posting up what you have done at the end of the day). 1511 had proposed a wiki-type setup for the 2008 Beta, but I think a lot of that was knocked down by FIRST trying to keep things under wraps.

I see both sides... but just try to look at what is useful coming out of this - teams that can help other teams, and maybe future Beta tests will start early enough that teams will have more time to document and get others up to speed.

[lynca]

Originally Posted by Kims Robot

It is probably very hard to sit on the outside and see very little released to the public, but a lot of what is being done is working through tedious and annoying bugs... and what do you care about the bugs if they are going to be gone before you get there?

Very well said, and YES it is difficult for me and many eager teams to sit by and watch.

Most open source models still publish a bug report to inform the other users of their development.

Originally Posted by Kims Robot

Could there be more documentation released? Likely true, but there are some rules FIRST imposes, and there are the hours in the day limits (making something readable/useful for others is much harder than just posting up what you have done at the end of the day).

The fact that FIRST imposes rules makes be very uneasy.... but that's another story.

I agree that documentation is very difficult, I just wish the Beta Organizers would have encouraged more team created tutorials. The community really needs Beta teams to put proper time into creating tutorials. The Java WPI page is a good clean web page tutorial, hopefully NI takes notes and organizes their pages into one cohesive page.

Here's my biased example of tutorials. http://mentorsearch.us/node/3

Originally Posted by Kims Robot

1511 had proposed a wiki-type setup for the 2008 Beta, but I think a lot of that was knocked down by FIRST trying to keep things under wraps.

"Knocked down by FIRST" sounds very discouraging for a community that should be encouraging creative ideas. I hope that you bring back your wiki idea because it sounds great !

Thanks for taking the time to talk about this important issue.