Auto-scheduler suddenly stopped working

SatNOGS Software
1

Auto-scheduler suddenly stopped working.

40926 XgSfynx2reaDeFbFd2Ucen 0 1 2 GMSK TIANWANG-1C-TW-1C
 91%|█████████████████████████████████████████████████████████████▎     | 418/457 [00:07<00:00, 58.47it/s]
Traceback (most recent call last):
  File "./schedule_single_station.py", line 319, in <module>
    main()
  File "./schedule_single_station.py", line 245, in main
    min_pass_duration)
  File "/home/pi/satnogs-auto-scheduler/auto_scheduler/pass_predictor.py", line 69, in find_passes
    sat_ephem.compute(observer)
ValueError: TLE elements are valid for a few weeks around their epoch, but you are asking about a date 365 days from the epoch

So with a couple of print statements, I tracked it down to the TLEs for 40926 being over 365 days out of date.

I deleted these from the /tmp/cache/transmitters_1376.txt file and now all is well again.

What can be done to prevent this happening in future?

5 Likes
2

For now the best way to avoid this is to keep SatNOGS DB updated, so a suggestion that the satellite is decayed will help. Suggestions can be done by logging in in DB and going to the satellite page and at the top right corner hit the edit button.

In the development front, there is a plan for having a kind of alert for satellites that don’t have new TLE sets or they are near decaying, so we can watch and update them as soon as possible.

3 Likes
3

The satellites status is changed in the db, remove the /tmp/cache/* files and run the schedular, this will solve the issue.

6 Likes
4

Thank you for the info. Scheduler is working well now. Well appreciated.

2 Likes