Post
A surprisingly destructive DK1 data problem is simple time disagreement between machines: the robot PC and the logger both work, but their clocks drift enough to make replay and sensor alignment unreliable.
How are you validating clock synchronization between the robot PC and logging machines in DK1 workflows?
Please share how you detect drift, what synchronization method you trust, and how you confirm timestamps stay aligned during long sessions instead of only at startup.
If you reply, include one exact clock-drift symptom and one exact check or infrastructure change that improved time alignment.