I don’t know if the judges would care whether or not it’s CAD or a physical build that you take pictures of. I would personally just document in a way that is easy to follow and allows the reader to build the robot.
1 Like
Hi Jobe,
I really hate to revive a 23 day old thread, but I remembered this thread and was thinking about what you said about “complete software documentation”. Could you care to elaborate exactly what you mean? Is it, for example, documentation of how a team uses a program? Or is it as simple as comparing software/platforms or both?
Thank you for your time.
1 Like
I encouraged teams that I used to coach to do a full publication of their code for every major iteration, with a change log of significant changes. As far as day-to-day here’s an example; If a team was working on tuning an auto, I’d encourage to copy the portion of the code and highlight the lines they were making tuning adjustments to in addition to their documentation of who was doing what that day and their goals for the session.
My mantra is “If you didn’t write it down, it didn’t happen”
2 Likes