Testing robotics systems in fast-paced startups | Michael Jae-Yoon Chung
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
- The Final Offshoringfinaloffshoring.com
- Software Engineering at Googleabseil.io
- Six Things I Learned Watching a Robotics Startup Die from the Inside | Rui Xuruixu.us
- Android Dreamsandroid-dreams.ai
- When Will Robots Go Mainstream? - Colossusjoincolossus.com
- Isaac Sim - Robotics Simulation and Synthetic Data Generation | NVIDIA Developerdeveloper.nvidia.com
- The_Final_Offshoring.pdffinaloffshoring.com
- Convictionconviction.com
- Where Are All the Robots? | Blog | Chef Roboticschefrobotics.ai
- Bessemer Predicts: Robotics and physical AI - Bessemer Venture Partnersbvp.com
- Robotics Needs Fewer Roboticists* - by Jacob Zietek - a16za16z.news
- How do We Quantify Progress in Robotics? - by Chris Paxtonitcanthink.substack.com