3 ms·
It seems like the issue wasn’t that there was a dropped frame, it’s that the time slot for that frame got filled by the next frame, then every subsequent frame
by jcims 5y ago
It seems like the issue wasn’t that there was a dropped frame, it’s that the time slot for that frame got filled by the next frame, then every subsequent frame was off by one resulting in a persistent timestamp offset of the vision data from reality for the remainder of the flight.
I didn’t read into it too much so I may not have all the details right, but I think this is the gist of it.
- ealloc 5y agoThat would be a straight-up, avoidable software/hardware bug: The incoming timestamp is incorrect, and garbage in is garbage out. That would make me curious how the timestamp error occurred: software, hardware? Camera or Navigation code? I assume they have very high standards, what was the process failure point?
- cm2187 5y agoOr timezone bug! Always hard to test.