'Fix It Window' and Programming....

[Dave Flowerday]

Originally Posted by Kris Verdeyen

We'll have to wait and see what the response is on QA 1226.

I assume you meant question 1223, and it has been answered:

Originally Posted by FIRST Q&A

ID: 1223 Section: 5.3.3 Status: Answered Date Answered: 1/24/2005
Q: Does <R14>, particularly "cease all software development", preclude teams from changing code (variable values, PID gains, "broken" code, new functionality, etc.) after the Fix-It Window on our now-legal practice robot (per Q&A #1026).
A: You may do whatever on your practice robot but you must recreate your "fixes" onsite at a competition.

[Alan Anderson]

Originally Posted by FIRST Q&A

ID: 1223 Section: 5.3.3 Status: Answered Date Answered: 1/24/2005
Q: Does <R14>, particularly "cease all software development", preclude teams from changing code (variable values, PID gains, "broken" code, new functionality, etc.) after the Fix-It Window on our now-legal practice robot (per Q&A #1026).
A: You may do whatever on your practice robot but you must recreate your "fixes" onsite at a competition.

I think this was the only reasonable answer. I'm surprised that the question needed to be asked in the first place.

Originally Posted by Kris Verdeyen

The rub here is that the rules governing mechanical parts and software are different. You're trying to find analogues where they simply don't exist.

From my viewpoint as a software engineer, they are perfectly analogous.

[Joe Ross]

Does applying a patch cover recreating the code? Wouldn't that be analagous to bringing a complete set of drawings for an item for the onsite machine shop to create?

[Anthony Kesich]

I would see making a patch as making a part to put onto the robot since you just drop it onto the greater part of a whole. Bringing notes and papers would be like bringing drawings. It has everything you need to make the part, but it isn't the part itself.

[Astronouth7303]

That is kinda the problem with code: As soon as you get specific, it's plug/play.

My suggestion is to implement it in psuedo-code.