Satellites plug-in: Mark satellites with out-of-date orbital elements
Display in the Satellites configuration window and/or in the upper-left corner information field a warning that the orbital elements for a given satellite have not been updated during the last update. This can happen:
- if the satellite has been defined by the user and its designation is not in the update lists,
- the satellite has decayed and is no longer in the update lists,
- the update lists have been re-structured and use new designations that don't match the ones in the embedded file.
See the attached bug report for an example why this is necessary.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Sprints
Whiteboard
There are lots of reasons that the elements are not updated - not all of them are problematic:
1. There just aren't any updated elements available (the update URL still has the previous data). This is not a problem.
2. The elements are missing from the update sources. This could be a temporary problem because one or more of the update URLs, like website maintenance.
3. The elements are missing from the update sources because the designation (ID) has changed. This is a huge pain in the butt.
4. The elements are missing from the update sources because the elements have been removed from the update source.
I suggest adding some new values to each satellite entry in the json file:
- lastUpdated - datestamp of the last update
- numNonUpdates - how many times the update has run but there was nothing for this satellire
- lastUpdateStaus - values: updated, notUpdated, notFound
Then we can have some rules to try to catch problematic satellites, like: "mark as a problem if the last three update attempts failed to update the satellite and the last update was more than 2 months ago OR mark as a problem if the elements were not found in the update data".
Work Items
Dependency tree
* Blueprints in grey have been implemented.