Description of problem: UARS satellite still showing with negative altitude values. Version-Release number of selected component (if applicable): 1.3 How reproducible: Add UARS check values after selecting UARS. Actual results: Shows negative values with no foot print. Expected results: Should show that the satellite is none existent/crashed. With N/A values. Additional info: N/A
Ticket opened upstream: https://sourceforge.net/tracker/?func=detail&aid=3414666&group_id=213550&atid=1026162
Howdy, Just bopping down from up stream. I want to make sure that I address all the concerns in this bug. As of the most recent SVN version, UARS does not appear on the satellite map but it does still show up in the single user view. It would seem that many of these fields should be marked as DECAYED. Were there other view that may have been missed? Polar, List, Event List are the possibilities that come to mind.
Created attachment 525886 [details] Proposed Fix There will be two images attached, one is the before and one is the after. I believe this is inline.
Created attachment 525887 [details] Original showing the problem
I think marking what should happen is, that if it hits altitude of 0, then it shows everything as decayed. I cannot see a better way to do this, unless the tracking data is fully updated upstream from tracking station.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug is still active upstream. I'll keep this ticket open as a reminder. It is scheduled to be fixed but a release has not been determined, yet.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Not sure when upstream is going to address this. Please follow their ticket. https://sourceforge.net/tracker/?func=detail&aid=3414666&group_id=213550&atid=1026162