GOES I-M: A Retrospective Look at Image Navigation and Registration (INR), Jitter and Lessons Learned
The Geostationary Operational Environmental Satellite (GOES) I-M series of spacecraft was the second generation of United States meteorological observational platforms in geosynchronous orbit. They served as the principal Earth- viewing observational platforms for continuously monitoring dynamic wea...
Gespeichert in:
Hauptverfasser: | , , |
---|---|
Format: | Tagungsbericht |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | The Geostationary Operational Environmental Satellite (GOES) I-M series of spacecraft was the second generation of United States meteorological observational platforms in geosynchronous orbit. They served as the principal Earth- viewing observational platforms for continuously monitoring dynamic weather events from the mid-1990s and into the 21st century. This paper will look back at the program framing key system attributes of the mission, which necessitated a multi-layered development approach to meet stringent meteorological instrument Line-of-Sight (LoS) pointing and pointing stability requirements. The overall approach involved understanding, correcting, and avoiding pointing errors across a broad frequency range including what would typically be called dynamic interaction and jitter. Background information will be provided covering the mission architecture and program drivers. The systems solution for man- aging and mitigating the deleterious influences of on-board disturbances in order to meet the challenging instrument LoS pointing and jitter requirements will be described, along with the ‘first of its kind’ Image Navigation and Registration system. A broad look back at the lessons learned that emerged from the GOES I- M experience will be presented, with the intent of capturing general and specific insights for developers of future missions having stringent payload instrument pointing requirements. These discussions will touch on such critical aspects as defining jitter and related pointing requirements, the importance of early system architectural decisions, understanding and reducing on-board disturbances, the balance of test and analysis, and the imperative for maximizing on-orbit operational flexibility in order to accommodate unexpected dynamic interactions. |
---|