Hello there,
sometimes it is favourable to have a bit more control on what gets scheduled on one’s own station. This can have several reasons (all those happened already to me):
- Someone auto-schedules the complete network, but forgot about it and produces on your station observations that fail constantly
- A satellite-specific bug causes your station to crash on those observations
- Your station is very unlikely to pick up the signal of a specific satellite, e.g. due to physical limitations
- …
In all those cases, it would be fair to de-schedule an observation to make the observation time available to a more useful cause. This is, what satnogs-obs-deleter can do.
You can install the package via pip or clone the repo directly from codeberg:
$ python3 -m venv .venv
$ source .venv/bin/activate
$ pip install satnogs-obs-deleter
After that, you should create a config file (or copy it from the repository, If you checked that out). This block shows an example for a config:
#
# satnogs-obs-deleter configuration
#
station = [106, 4271] # Must be a list
api_token = "__YOUR_TOKEN_HERE__"
# Observations for these satellites will be blocked in general. Please consider
# using this sparsely.
blocked_satellites = [
"SomeSat", # schedules massively without ever checking results
"OtherSat", # crashes due to AX.100 bug
"ExampleSat",
]
# Block observations from specific observers. Also useful for maintenance-situations
blocked_observers = [
"someUserName",
"otherUserName",
]
# Block observations that are very likely to fail, e.g. because they failed on this station very often in the past
block_likely_failing = true
# Block transmitters if their success rate on the station is below this threshold
min_success_rate = 0.20 # percent
The script could be called periodically via a cronjob or a systemd-timer and systemd unit (examples may follow later).
Best wishes,
mhuebner