That’s not true , the selection is based on some algorithms and statistics. Are these algorithms and statistics perfect, of course not, we need to improve them both of them to utilize better the whole network.
auto-scheduler is exactly what it says, it’s not a human behind it but only algorithms, this is why we use this user to separate it from other manual scheduling. Ideally and in the future the plan is to have these algorithms to run inside the network taking into account several needs, station owners preferences/priorities, the utilization factor of each station, satellite and station statistics etc.
Let me try to clear the confusion, auto-scheduler as a project is meant to be a tool for station owners to schedule with their preferences and priorities satellites in an automatic way to their stations. So you need to run it manually.
The algorithms that schedule with the
auto-scheduler user are running kind of centrally and use statistics for creating the priority list. It also tries to respect the utilization factor of each station, so this is probably a reason for not having any scheduled observation from it.
We created this user exactly because there was a confusion when the algorithms scheduled observations with the username of @BOCTOK-1, because there isn’t any person behind it. @BOCTOK-1 takes care of their continuous running and some tuning that is needed sometimes but is far from scheduling himself all these observations.
If you have any question, issue, request etc related to the auto-scheduler(as user), scheduling and other operations the best way is to open an issue in the Operations repo.