The lean, headless worker
THE IDEA
A worker, not a console
The Workstation is the operator's own machine, the one you sit at and run Mission Control on. The compute node keeps the same services and drops the interface: a machine that does the heavy math and hands the answer back.
NAMING
Workstation vs compute node
Both profiles start the same services and install the World Engine by default. The difference is intent: the Workstation is the operator's whole machine and typically the master, the compute node is a stripped-down box that exists to add capacity.
| Workstation | Compute node | |
|---|---|---|
| Intended box | Operator's own machine | Headless box on the LAN |
| World Engine compute service | ✓ | ✓ |
| Mission Control on the same box | ✓ | |
| Flight controller, radio, camera | ||
| Cluster position | Master (typical) | Worker, in development |
Intended box
World Engine compute service
Mission Control on the same box
Flight controller, radio, camera
Cluster position
SET ONE UP
Install, then point drones at it
The installer turns the World Engine on for the compute profile. Drones find the node on mDNS, or you pin its address on networks where multicast does not reach.
One install command
Install the agent with the compute profile on Linux. Reconstruction calls COLMAP and a splat trainer on the host, and perception offload needs ffmpeg.
curl -sSL https://raw.githubusercontent.com/altnautica/ADOSDroneAgent/main/scripts/install.sh \ | sudo bash -s -- --profile compute
Defaults
Set through environment variables on the node service.
- Worker slots1
- Job API0.0.0.0:8092
- Finished jobs kept24 hours
- mDNS advert_ados-compute._tcp


A compute node sits on the LAN and takes the heavy jobs.
EXPLORE
Related
Scale reconstruction across many machines
Compute nodes are designed to join a master and add throughput. Read how the cluster schedules work.
See the cluster