Team 1717 2011 pre-season code

[moowiz]

This is the code we have before the season starts. Reposting for various reasons. It will most likely not compile as is.

[steinra]

Thank you for sharing! Along this lines though, did anyone else see this in the call out on page 14 in the Robot section?

"
Example: A TEAM developed an omni-directional drive system for the 2010 competition. Over the summer of 2010 they refined and improved the control software (written in C) to add more precision and capabilities. They decided to use a similar system for the 2011 competition. They copied large sections of unmodified code over into the control software of the new ROBOT (also written in C). This would be a violation of the schedule constraint, and would not be allowed.
"

This seems to be different from past years. From what I read into this, it is required we start from scratch for the programming. Now we don't have anything we are going to reuse, due to language change, but would the way to be in compliance is to publish and share reused code with everyone?

So if we build a java library this year and want to use it next year, should it be shared so we are in compliance with the spirit of this rule? Put everyone on the same level of "COTS" libraries?

Thanks!

Randy

[jross]

Thank you for sharing! Along this lines though, did anyone else see this in the call out on page 14 in the Robot section?

"
Example: A TEAM developed an omni-directional drive system for the 2010 competition. Over the summer of 2010 they refined and improved the control software (written in C) to add more precision and capabilities. They decided to use a similar system for the 2011 competition. They copied large sections of unmodified code over into the control software of the new ROBOT (also written in C). This would be a violation of the schedule constraint, and would not be allowed.
"

This seems to be different from past years. From what I read into this, it is required we start from scratch for the programming. Now we don't have anything we are going to reuse, due to language change, but would the way to be in compliance is to publish and share reused code with everyone?

So if we build a java library this year and want to use it next year, should it be shared so we are in compliance with the spirit of this rule? Put everyone on the same level of "COTS" libraries?

Thanks!

Randy

There is an almost identical example in last year's rules, this isn't new.

You are correct that by releasing their old code on a public forum, team 1717 is now allowed to use the old code as COTS. See the definition of COTS in section 1 of the manual. Team 1717 gets an advantage by re-using code, and we get an advantage by learning from them.