Review saved results

Flightops can turn a supported saved JSON result into a desktop HTML report. Generating the report does not require ROS, a running robot, or AI.

Prerequisites

Install the Flightops beta and activate this device. Have a saved JSON result from a Flightops tool, or use the sample below.

1. Generate a report

Replace ./result.json with your saved result path:

flightops results ./result.json --open

The command prints the generated HTML path. --open asks the desktop browser to open it. If no browser is available, use the printed path to open the file manually. The report needs no web server.

A sample incident result ships with the offline documentation. flightops docs prints the path of the documentation's index.html; the sample is in assets/user-guide/evidence/incident.json next to it:

sample="$(dirname "$(flightops docs)")/assets/user-guide/evidence/incident.json"
demo_dir=$(mktemp -d /tmp/flightops-results-XXXXXX)
flightops results "$sample" -o "$demo_dir/results.html" --open

The sample shows a recorded callback incident with five passing workflow stages. It is demonstration evidence, not a check of your ROS system.

2. Keep the evidence

Keep the source JSON and its referenced artifacts if you need to inspect the details later. The HTML report embeds the JSON but may link to other artifacts. Without -o, each run regenerates the derived report next to the input, such as result.flightops.html. An explicit -o path is never overwritten, so use a new filename for another report.

Next steps

Follow the recording quickstart to create a result from the sample Nav2 recordings without ROS. The advanced user guide lists accepted JSON types and limits.