Account
Data and model processing
Choose workspace uploads separately from the model used for an investigation.
Two separate choices
Detection runs where you start TrialONE. Model interpretation sends the context needed for an investigation to the configured model endpoint. Workspace upload sends the report and selected history to your TrialONE account. Turning off one does not turn off the other.
| Choice | What it controls |
|---|---|
--no-explain on diagnose | Skips model interpretation for that diagnosis. |
--no-push | Skips posting the run to the TrialONE workspace. Model calls can still occur. |
| A model endpoint on your network | Keeps model requests at the address your team configured. Workspace uploads remain a separate choice. |
--no-camera on watch | Stops camera frames being used for live investigations on that run. |
What reaches your workspace
By default a signed-in run sends the finding and recipe, cited log and source excerpts, channel statistics and selected histories. With --project, it can also send commit metadata and the contents of supported parameter, launch and URDF files. The original recording is uploaded only when enabled for the machine or explicitly requested.
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 | No machine-state attachment. A recipe can still contain cited source or log excerpts. |
| code | Commit, branch, recent commit metadata and hashes of supported configuration files. No file contents in the state attachment. |
| 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
Set history, machine state and raw recording upload per machine under Settings, Robots, or per run with the corresponding CLI flags. A flag takes precedence over the stored setting. These settings control workspace uploads; they do not restrict which context the configured model can read.
Model context
An investigation can send measured values, logs, relevant source and configuration excerpts, and tool results to its model endpoint. The managed interpretation service currently uses external model providers. A model key of your own sends requests to that provider. To use an endpoint on your own network, see Model settings.
Live camera frames
Camera context is enabled by default in the current pilot watcher for supported topics. It keeps a limited recent buffer on the robot and can send selected frames to the configured model during an investigation. Frames are not separately stored or uploaded with the run by this camera feature. They may show people or your workspace. Disable them under Settings, Robots or with --no-camera when that context is not appropriate for your pilot. A separately enabled raw recording upload can still contain its own images.
How long it is kept
Uploaded histories are deleted after your workspace retention period, 90 days by default. Runs remain until deleted. Under Settings, Profile, Your data lets you export workspace records or request account deletion. Owners and admins can delete a run from its page together with its stored files. Contact hello@trialone.info if you need help.
See the Privacy notice for service providers and contact details. For a pilot with specific data requirements, agree the processing setup with us before connecting the robot.
Something missing or wrong here? Tell us.