HomeSpecsDocsStore
Log inSign up
TwitterDiscordGitHub
Skip to documentation
Sourccey docs

Explore the documentation

Getting startedWelcome to SourcceyChoose your path from first setup to policy development.Getting startedBefore you beginPrepare your robot, workspace, computers, and network.Vulcan StudioDownload & installInstall the desktop application for Windows, macOS, or Linux.Developer guidesDeveloper quickstartSet up the controller and robot computers with Python and LeRobot.Developer guidesTeleoperate SourcceyVerify the network, leader arms, robot, keyboard, and cameras together before collecting data.Developer guidesRecord a datasetCollect a small, consistent set of demonstrations after teleoperation passes.Developer guidesReplay an episodeSend recorded actions back to Sourccey and validate the dataset before training.Developer guidesTrain a policyTrain an ACT policy from the dataset without connecting to the robot.Developer guidesRoll out a policyGive a trained policy supervised control of Sourccey for a short test.Developer guidesTroubleshootingWork from the top of the relevant section and run one diagnostic at a time.Hardware & referenceAssembly overviewNine build stages; detailed illustrated instructions are pending.AI agentsAgent quickstartCopy task context and read documentation as Markdown.
Tab to move between results Esc to close
Developer guides

Replay an episode

Send recorded actions back to Sourccey and validate the dataset before training.

01

Prepare for replay

Check that this guide matches your robot and software. Before moving the robot, clear its workspace, stay nearby, and confirm the stopping procedure for your unit with the team. Stop controls and what happens when you release the controls can vary; closing a terminal does not replace a physical emergency stop.

  • Clear the full robot workspace.
  • Keep the emergency stop within reach.
  • Start sourccey-host on the robot computer.
  • Restore the same physical setup used while recording.
02

Replay an episode

Run this on the controller. Episode numbers are zero-based, so 0 is the first recording.

Controller computer · terminal
uv run lerobot-replay --robot.type=sourccey_client --robot.id=sourccey --robot.remote_ip=192.168.1.243 --dataset.repo_id=vulcan-studio/sourccey-demo-1 --dataset.episode=0
03

Validate the episode

  • The action sequence is smooth and recognizable.
  • Arms, base, and lift move as recorded.
  • The robot stops when replay finishes.
  • There is no unexpected or unsafe motion.

Do not train if replay exposes incorrect feature mapping, unexpected lift behavior, or unsafe motion.

About these examples: checks against a specific software version and a full hands-on walkthrough are still in progress. The source documentation below can help you and the team confirm the right instructions for your setup.

View upstream documentation·Read as Markdown
Vulcan Robotics / SourcceyBuild. Learn. Iterate.