Satellites and their properties¶
Satellites¶
satellite = client.assets.create("MYSAT-1", external_id="2026-001A")
client.assets.list() # your organisation's satellites
client.assets.get("MYSAT-1") # by name or id
client.assets.update(satellite, norad_id=39451, international_designator="2013-067A")
The name is the object name in your ephemeris files, external_id their object ID. The
NORAD number and the international designator go into the two-line elements
(Orbit products). Wherever the client asks for a satellite, it takes the
Asset, its id or its name.
Groups¶
A satellite may be kept in a group (a constellation, a mission), a name its satellites share. The dashboard lists the fleet by group.
client.assets.update(satellite, group="Polar ring")
print([a.name for a in client.assets.list() if a.group == "Polar ring"])
client.assets.update(satellite, group=None) # out of the group
Spacecraft properties¶
What the force model needs to know about the spacecraft, as versions in time:
client.properties.add(
satellite,
mass_kg=430,
drag_area_m2=1.0,
srp_area_m2=4.0,
antenna_offset_m={"along_track": 0.31},
)
client.properties.add(
satellite, mass_kg=425, drag_area_m2=1.0, srp_area_m2=4.0, valid_from="2026-12-01T00:00:00Z"
)
client.properties.list(satellite) # the versions
Field |
Meaning |
|---|---|
|
Mass of the spacecraft |
|
Cross-section facing the direction of flight |
|
Cross-section facing the Sun |
|
Optional starting value (2.2). It is estimated in every run |
|
Optional (1.3) |
|
Optional: where the GNSS antenna sits relative to the centre of mass, as |
|
Optional: from when these values hold |
Each run uses the version valid at the start of its arc. The mass after a manoeuvre needs no new version where the manoeuvre is reported with its mass change (Manoeuvres and plans).
Your organisation¶
me = client.me()
print(me.name, me.tier, me.features)
tier names your organisation’s tier (None: every feature and the default limits);
features the features it includes, such as od_diagnostics or od_custom_settings.