Account
What leaves the robot
You decide per machine how much of a run reaches the website.
By default a run sends the recipe (with the log lines and the few source lines around each file and line it cites), statistics per channel, a trend and a 10 Hz history of every channel, the minute around each finding, and, with --project, the commit data and the contents of your parameter, launch and URDF files. The recording itself stays on the machine unless you switch its upload on.
History
| Level | What leaves the machine |
|---|---|
| off | The recipe and statistics per channel. |
| incident | Also the minute around each finding: 30 seconds before to 30 seconds after, at 10 points per second. |
| full (default) | Also a trend of every channel and a 10 Hz history of every channel that moved. |
Machine state
| Level | What leaves the machine |
|---|---|
| off | Nothing about the code or the files. |
| code | The commit, the branch, and the hash, date and subject of the last 50 commits. No source code, no diff, no credentials. |
| full (default) | Also the parameter, launch and URDF files next to it, each content sent once per hash. |
The recording itself
Off until you switch it on for a machine, or pass --upload-raw. A recording can hold more than numbers (camera frames, point clouds, anything the robot published), and it can be large, so the switch names both.
Where to change it
Per machine under Settings, Robots, or per run with --history and --state. A flag wins over the setting, and the terminal says which one applied. --no-push keeps a run entirely on the machine.
How long it is kept
Trends and histories are deleted after 90 days by default. Runs stay, because issues and verifications refer to them. To have a workspace or a run removed, write to hello@trialone.info.
Something missing or wrong here? Tell us.