Your code runs on the lab's computer
You upload a script or policy, it runs next to the robot and you watch the result. Training platforms and the Robotarium work this way.2
Click each stop to see what it does and what to ask the lab about it. Then compare who offers remote access.
Books your slot, checks your code and applies the lab's speed and workspace limits.
Which limits will my code run under?
Uploading code is forgiving. Live control is not: every delay on the link shows up in the robot's motion.
You upload a script or policy, it runs next to the robot and you watch the result. Training platforms and the Robotarium work this way.2
Teleoperation for data collection or debugging. The robot follows your inputs, so the link has to be fast and steady.
On one training platform, real-robot time is booked as a slot from inside your project.1
Labs keep their own safety system, speed limits and a person who can stop the robot. Your code runs inside those limits.
Only if the hardware matches. Ask for the exact arm, gripper, cameras and controller version before booking.
Ask the lab where your code runs and what is deleted after the slot. If it runs on your machine and only sends commands, less of it leaves your side.
The robot should stop safely. Ask whether lost time is refunded or rebooked.
Tell us the robot and the task. We read every request and come back to you.