Comparing settings¶
To find out whether a setting suits your satellite better, let the service run several over the same arc and compare them:
comparison = client.comparisons.request(
satellite, "2026-10-01T00:00:00Z", "2026-10-02T00:00:00Z"
).wait()
print(comparison.recommended, comparison.recommended_reason)
for row in comparison.settings:
print(row.setting, row.status, row.gate_passed, row.weighted_rms, row.drag_coefficient)
Without settings it runs the few the profile marks as compared by default; name others, up
to 16, to compare more. Each is a run of its own. Some settings only a comparison has: a
shorter and a longer arc ending at the same moment (arc-12h, arc-48h) and runs that
continue your satellite’s accepted run before the arc (continued, prior-covariance).
For each setting the comparison shows how its run went (its acceptance check, the fit, the
fixes left out, the drag coefficient) and how far its orbit lies from the default’s: over
the hours both fitted, and in the prediction 1, 6, 12 and 24 hours after the arc.
recommended names the setting the comparison would take: the default when it passes its
acceptance check, otherwise the first that does.
A comparison changes nothing. Its runs are for comparison: none becomes the satellite’s orbit, and the schedule goes on as it is. To use a setting, set it in the schedule or name it in your runs.
One comparison at a time per organisation, at most 16 settings; its runs do not count against your limits.
client.runs.list(satellite, comparisons=True)lists them with the others.