I’d like to restrict somewhat satellites that I schedule automatically to those I know yield the best results, current syntax for priorities list is following:
|NORAD priority UUID|
Would it be difficult to make the last part optional and allow autoscheduler to pick something itself?
for the auto-scheduler to be able to pick a transmitter for a selected satellite by itself it needs additional information, e.g. on the previous observation success rate in satnogs-network or a “default transmitter setting” in satnogs-db ([1]).
The satnogs-network API provides these statistics for each transmitter via the apiTransmittersList endpoint, e.g.
GET https://network.satnogs.org/api/transmitters/?uuid=ZJxCeQmih9zDfYNVrB4wRN
A (python) script could retrieve the list of all transmitters for a selected satellite from satnogs-db, then ask for transmitter stats from satnogs-network and then choose the best transmitter based on this data.
If there is interest in this, please open a feature request issue in the auto-scheduler issue tracker (you can also just link this thread there). In case you have other questions you can also chat with us on our matrix/IRC rooms.
Best wishes,
Fabian
footnotes:
[1]: Defining a default transmitter (overwriting the stats) is a long-standing feature request tracked in satnogs-network#604.
Thanks for the detailed answer, now I better understand why it is that way.
I’ll probably write a simple script that will pull observations from previous two days with any data associated, copy their norads and transmitter IDs and generated priority list that way. I just figured which signals I’m able to detect and want to focus on those.
Note that for the network, and for individual satellite operators, a negative observation can also be useful. That’s why I’ve let my station auto-schedule randomly. And because I’ve been too lazy to do what you suggest