3 ms·
I think the image recognition part is fairly impressive too. At 60 fps, unless you're streaming subframe data you're looking at around 160ms ms per frame, and
by matheweis 10y ago
I think the image recognition part is fairly impressive too.
At 60 fps, unless you're streaming subframe data you're looking at around 160ms ms per frame, and that's not counting any time for image processing.
(Presumably they could cheat by looking at the cube beforehand, but it sounds like a realtime thing)
- gohrt 10y agoRecognizing 48 colored dots in parallel in 160ms is not hard.
- wmf 10y agoYou mean 16 ms per frame?
- dogma1138 10y ago60fps is 16ms per frame.
- matheweis 10y agoGah yes, don't know where that extra zero came from!!
- mpclark 10y agoDoes it need to look at the cube again after it has observed the starting position?
- TheOtherHobbes 10y agoNo. More accurately - probably not. It depends how the actuators work and whether they include optical monitoring of the twist. If so, the solution won't need to monitor the colours, but it will need to make sure the actuators spin the sides accurately. Otherwise - cube explosion.
- paulftw 10y agoThey use stepper motors - same hardware that allows a budget 3D printer archive sub-mm movement without any feedback loops. Pretty sure they don't need to look at the cube again after scanning the starting position.
- taneq 10y agoIt wouldn't be doing any image processing during the solving phase. In fact, it's probably not doing any full stop, and just tracks the state of the cube (which starts in a known state) via dead reckoning.
- deleted 10y ago[deleted]