ALBERT

Description: The space mission design and operations community already recognizes the value of cloud computing and virtualization. However, natural and valid concerns, like security, privacy, up-time, and vendor lock-in, have prevented a more widespread and expedited adoption into official workflows. In the interest of alleviating these concerns, we propose a series of guidelines for internally deploying a resource-oriented hub of data and algorithms. These guidelines provide a roadmap for implementing an architecture inspired in the cloud computing model: associative, elastic, semantical, interconnected, and adaptive. The architecture can be summarized as exposing data and algorithms as resource-oriented Web services, coordinated via messaging, and running on virtual machines; it is simple, and based on widely adopted standards, protocols, and tools. The architecture may help reduce common sources of complexity intrinsic to data-driven, collaborative interactions and, most importantly, it may provide the means for teams and agencies to evaluate the cloud computing model in their specific context, with minimal infrastructure changes, and before committing to a specific cloud services provider.

Description: The successful delivery of the Mars Exploration Rover (MER) landers to well within the boundaries of their surface target areas in January of 2004 was the culmination of years of orbit determination analysis. The process began with a careful consideration of the filter parameters used for pre-launch covariance studies, and continued with the refinement of the filter after launch based on operational experience. At the same time, tools were developed to run a plethora of variations around the nominal filter and analyze the results in ways that had never been previously attempted for an interplanetary mission. In addition to achieving sub-kilometer Mars-relative orbit determination knowledge, the filter strategy and process detected unexpected error sources, while at the same time proving robust by indicating thecorrect solution. Consequently, MER orbit determination set a new standard for interplanetary navigation.

Description: The successful delivery of the Mars Exploration Rover (MER) landers to well with in the boundaries of their surface target areas in January of 2004 was the culmination of years of orbit determination analysis. The process began with a careful consideration of the filter parameters used for pre-launch covariance studies, and continued with the refinement of the filter after launch based on operational experience. At the same time, tools were developed to run a plethora of variations around the nominal filter and anlyze the results in ways that had never been previously attempted for an interplanetary mission. In addition to the achieved sub-kilometer Mars B plane orbit determination knowledge, the filter strategy and process responded to unexpected error sources by both detecting them and proving robust. All these facets of the MER orbit determination filter strategy are described in this paper.

Description: Many times during the Cassini-Huygens mission to Saturn, propulsive maneuvers must be spaced so closely together that there isn't enough time or workforce to execute the maneuver-related software manually, one subsystem at a time. Automation is required. Automating the maneuver design process has involved close cooperation between teams. We present the contribution from the Navigation system. In scope, this includes trajectory propagation and search, generation of ephemerides, general tasks such as email notification and file transfer, and presentation materials. The software has been used to help understand maneuver optimization results, Huygens probe delivery statistics, and Saturn ring-plane crossing geometry. The Maneuver Automation Software (MAS), developed for the Cassini-Huygens program enables frequent maneuvers by handling mundane tasks such as creation of deliverable files, file delivery, generation and transmission of email announcements, generation of presentation material and other supporting documentation. By hand, these tasks took up hours, if not days, of work for each maneuver. Automated, these tasks may be completed in under an hour. During the cruise trajectory the spacing of maneuvers was such that development of a maneuver design could span about a month, involving several other processes in addition to that described, above. Often, about the last five days of this process covered the generation of a final design using an updated orbit-determination estimate. To support the tour trajectory, the orbit determination data cut-off of five days before the maneuver needed to be reduced to approximately one day and the whole maneuver development process needed to be reduced to less than a week..