Export and reproduce results
Choose the correct output scope, verify downloaded files, and preserve the inputs and settings needed for review.
Before exporting
Wait for a completed result and review its warnings. Select the intended fit or comparison view, then check the figure and parameter panel refer to the same dataset. If a run contains several fits, a single figure is not necessarily a complete export of the run.
Export availability follows the account entitlements shown in the app. Free accounts receive 20 free runs per calendar month (UTC) and can export PNG and basic CSV results. Additional formats require an entitled account; new paid plan purchases are currently marked coming soon.
Choose an output
PNG captures a figure for presentation. SVG provides a vector figure. The PDF report combines the current figure with its associated results; check its selected or comparison scope before sharing.
CSV and Excel are useful for reviewing numeric results across the run. Do not assume they are limited to the fit currently selected in the viewer. Inspect dataset labels and sheet names after downloading.
The Python export is the reproducibility script for the saved run. The audit bundle packages the available analysis record. Inspect the files in either output to confirm what inputs, settings, and results are included; retain the original source files separately.
Selected fit and comparison views
Use the fit selector to choose a dataset and verify its label before exporting. The parameter panel follows the selected fit. In comparison mode, compatible curves can appear together; a comparison may contain fewer curves than the total number of results.
Compatibility depends on axis labels, units, and scale. If a curve is absent, review those properties before requesting a comparison. A combined view does not itself convert units or establish that measurements should be pooled.
Download and verify
- Choose a format from Export and wait for the download feedback.
- Open the file from the browser downloads list; a download-started notice is not a review of the file contents.
- Check the dataset name, units, axes, legends, and visible result values against the workspace.
- For tables, confirm the expected datasets and rows are present. For reports, check that the figure and parameter table describe the same selection.
- Store the verified files with the run URL, export date, and original input.
Replay a saved analysis
When Python export is available, read its header and dependency instructions first. Use the input files and paths it specifies and install the packages it imports in a separate environment. The requirements can vary by analysis.
Compare the replayed numeric parameters and dataset labels with the saved results. Check that the script represents the selected analysis version, including exclusions and preprocessing. If a replay differs, preserve both outputs and report the run ID, script, dependency versions, and first differing result.
Maintain a review record
Keep the original input, the final analysis request, sample mapping, preprocessing, model or method settings, exclusions, and downloaded outputs together. Include the gate hierarchy and compensation or transform choices for flow results.
Export a baseline before refining or editing an analysis. The workspace can replace the current result, and a locally restored previous fit is not a durable server-side version history. A copied private run URL also does not grant another person access.
If an export fails
Check the workspace error and whether the chosen format is available to your account. Reload the saved run and confirm a completed result is present before retrying the download. If the problem persists, record the format, selected fit, run ID, and exact error for support.