flâneur — a map of the web's best reading

Testing robotics systems in fast-paced startups | Michael Jae-Yoon Chung

mjyc.github.io · 3,224 words · saved by 6 readers

Testing robotics systems is hard. Based on my experience working at startups with fewer than 200 employees and fewer than 100 robots providing RaaS using fleets of indoor mobile robots or lines of robot manipulators, the main reasons for the difficulty were as follows:

Starcraft II, Photo by Zach Tirrell on flickr Testing robotics systems is hard. Based on my experience working at startups with fewer than 200 employees and fewer than 100 robots providing RaaS using fleets of indoor mobile robots or lines of robot manipulators, the main reasons for the difficulty were as follows: Edge cases and corner cases in production environments. The difficulty of using simulation. Challenges with adopting automation. Why is Testing Robotics Systems Hard? In production , I’ve encountered various edge cases and corner cases : Edge cases for robotics algorithms. Input spac

Explore this link on the map →

saved by

related reading