Skip to content

Trace Formats

Argus evaluates declared command traces. The input format is part of the evaluation boundary and should be recorded with the resulting report.

Format Extension Notes
JSON trace .json Supported for declared command traces.
ROS 2 SQLite bag .db3 Requires topics compatible with the selected profile.
MCAP .mcap Requires the optional MCAP reader in an approved developer environment.

Native JSON example

{
  "manifest": {
    "schema_version": "1.0",
    "session_id": "example-session",
    "producer_id": "controller",
    "receiver_id": "receiver"
  },
  "commands": [
    {
      "sequence_number": 0,
      "timestamp_us": 1000000,
      "event_type": "command",
      "payload": {"velocity_lin_mps": 0.5, "velocity_ang_rads": 0.1}
    }
  ]
}

Run an evaluation

argus regression-eval --trace recording.db3 --profile your_profile.json --out out/evaluation

Format acceptance does not validate the operational safety of the source system. See Evidence Classes.