Hello,
I’d like to understand why we have a 2 days limit for scheduling observations in advance (at least from the web interface)?
Is it a matter of computations needed to be berformed on the backend or we simply don’t want to schedule the same satellite observations in bulk?
I’d like to observe ISS, for example, whole next month whenever it is available at my location.
Currently I need to hunt for the occasion by checking if it is possible every 2 days.
The main reason is that TLE don’t describe the orbit well after some days. Especially in satellites (not many in DB right now) that change their orbit actively, for example ISS.
So, let’s say that you schedule a satellite for the next week, the scheduling happens with the current TLE elements, as we update TLE elements all the observations are going to be update with the latest ones that will describe a different orbit. This will have as a result, depending on the orbit change, to have start/end times different from the actual pass start/end times.
For now the best way to avoid scheduling manually every 2 days is to use auto-scheduler which eventually will become part of the network code.
@fredy thanks for explanation.
I am using auto-scheduler on my pi - just need to figure how to prioritize ISS beside any other satellites - but there was something on priorities in the documentation.
If I remember well you can set priorities by adding transmitter uuids in a file… maybe someone that uses auto-scheduler actively can help you with that.
create a text file with NORAD ID, priority and UUID of transmitters and
assign 1.0 (highest) for priority to transmitter. An example favorites.txt file might look like:
Hi satcolintel5,
I am looking for a way to list the satellites I still want to observe from my ground station.
It is possible to let me know how you do it ?