Quote:
Originally Posted by davidthefat
Well, I would disagree. From the language of the descriptions, it seems as if the problems would arise from general use. Sure, you'll definitely have to try hard to get certain conditions, but debugging and profiling your usual usage conditions is enough IMHO. Like the 100% CPU usage should have easily been caught.
edit: perhaps, it's just me. I like spending time with my robot.
|
If you read the document carefully, it states:
Quote:
While this may have impacted the performance of the cRIO, it is unlikely that it was the source of 1114’s command response failures on Einstein.
[...]
No issues were found during these tests that could explain the connection problems seen on Einstein by 1114.
|
Later on, it states that the
likely cause of 1114's issues was FCA.
Also:
Quote:
|
It is unlikely that the code issues found on 4334’s robot relating to the 100% cRIO CPU usage would be able to cause a complete command response failure for the duration experienced in the initial playing of Semifinal 2-1.
|
The 100% CPU usage was not found to be the cause of their issues so debugging that issue probably would not have helped (much).
I really don't think many of the issues described in the document can be attributed to teams not debugging carefully enough.