search

la1k / flyby

A satellite tracking program
GNU General Public License v2.0
39 stars 8 forks source link

Transponder schedule #29

Closed bjorgan closed 7 years ago

bjorgan commented 8 years ago

Transponder schedule was never implemented in Predict, and subsequently not in Flyby. The only indication that this was supposed to be implemented is that you always have to enter "No weekly schedule\nNo orbital schedule\n" in each transponder entry of the transponder database, and that these are read into "unsigned char dayofweek" and "int phase_start, int phase_end". The values are never used.

Some satellites have transponders that are turned on only at specific times or days. Does it make sense to try to implement this? Is it useful? How should it be displayed? How should it be used?

I've removed the physical variables for now in the branch dealing with issue #17 (though the fields are still required to be present in the files, at least for now). The complexity of the scheduling probably requires something more than the initial implementation indicated in Predict (more than just an unsigned char describing the day).

bjorgan commented 7 years ago

Don't really see the usefulness right now. We can extend the transponder database with useful information when we need it, but focusing on this specifically seems to be a bit pointless. Closing this for now.