Arm not moving using the Getting Started model
Teams report critical simulation failures where robot arms remain frozen despite correct setup.
The AI for Industry Challenge, a major robotics competition, is experiencing widespread technical issues with its foundational simulation environment. Multiple teams have reported that the Getting Started model—which serves as the baseline for all participants—is failing to execute basic robotic operations. Despite following Docker setup instructions precisely and successfully launching the evaluation system, teams are encountering a critical failure: the simulated robot arm remains completely frozen and unresponsive during Trial 1 executions. The system appears to start correctly but then enters a 16-minute timeout cycle before attempting retries, indicating a fundamental breakdown in the simulation pipeline.
Beyond the motion failure, teams are also reporting missing visual elements in the Gazebo simulation environment, particularly cables that should appear on the task board. The problem appears consistent across different team setups, suggesting it's not an isolated configuration error but rather a systemic issue with the competition's provided codebase or simulation parameters. Forum activity shows this isn't the first technical challenge participants have faced—previous topics include GPU utilization problems and controller issues—but the arm motion failure represents a more fundamental barrier to competition progress.
The competition organizers have yet to provide an official solution, leaving teams stuck at the initial implementation phase. This technical roadblock is particularly significant because the Getting Started model serves as the foundation upon which all subsequent AI development and policy improvements are built. Without a functioning baseline simulation, teams cannot proceed to develop, train, or test their reinforcement learning models for the industrial robotics tasks that form the core of the challenge.
- Robot arms remain completely frozen in Gazebo/ROS2 simulations despite correct Docker setup
- System enters 16-minute timeout cycles before retrying failed Trial 1 executions
- Multiple visual elements including task board cables fail to render properly in simulation
Why It Matters
This technical failure blocks hundreds of teams from advancing in a major industrial AI competition, highlighting simulation reliability challenges in robotics.