An automated system for processing and distributing SIRTF telemetry data
Explore the source record for details and available documents.
SEARCH · Search NASA
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Explore the source record for details and available documents.
The Science Activity Planner (SAP) is the primary science operations tool for the Mars Exploration Rover mission and NASA's Software of the Year for 2004. SAP utilizes a variety of visualization and planning capabilities to enable the mission operations team to direct the activities of the Spirit and Opportunity rovers. This paper outlines some of the challenging requirements that drove the design of SAP and discusses lessons learned from the development and use of SAP in mission operations.
Ensemble is an open architecture for the development, integration, and deployment of mission operations software. Fundamentally, it is an adaptation of the Eclipse Rich Client Platform (RCP), a widespread, stable, and supported framework for component-based application development. By capitalizing on the maturity and availability of the Eclipse RCP, Ensemble offers a low-risk, politically neutral path towards a tighter integration of operations tools. The Ensemble project is a highly successful, ongoing collaboration among NASA Centers. Since 2004, the Ensemble project has supported the development of mission operations software for NASA's Exploration Systems, Science, and Space Operations Directorates.
The Spaceport Command and Control System will be the National Aeronautics and Space Administration's newest system for launching commercial and government owned spacecraft. It's a large system with many parts all in need of testing. To improve upon testing already done by NASA engineers, the Engineering Directorate, Electrical Division (NE-E) of Kennedy Space Center has hired a group of interns each of the last few semesters to develop novel ways of improving the testing process.
Standards for Unmanned Aircraft System (UAS) Detect-and-Avoid (DAA) systems are currently being developed under the auspices of the RTCA Special Committee 228 (SC-228). To support the development of these standards, a series of flight tests has been conducted at NASAs Armstrong Flight Research Center (NASA-AFRC). The fourth in this series of flight test activities (Flight Test 4, or simply FT4) was conducted during the Spring and Summer of 2016. FT4 supported the objectives of numerous organizations working toward UAS DAA Minimum Operational Performance Standards (MOPS) and UAS DAA Radar MOPS. The summary provided herein is limited to the objectives, analysis and conclusions of the NASA Ames Research Center (NASA-ARC) SSI team toward the refinement of UAS DAA MOPS. This document provides a high-level overview of FT4 and the SSI-ARC objectives, a summary of the data analysis methodology and recommendations for UAS DAA MOPS refinements based on the data analysis results. A total of 72 encounters were flown to support SSI-ARC objectives. Test results were generally consistent with acceptable UAS DAA system performance and will be considered in broader SC-228 requirements validation efforts. Observed alert lead times indicated acceptable UAS DAA alerting performance. Effective interoperability between the UAS DAA system and the Traffic Alert and Collision Avoidance System (TCAS) was observed with one notable exception: TCAS Resolutions Advisories (RA) were observed in the absence of any DAA alert on two occasions, indicating the need for alert parameter refinement. Findings further indicated the need for continued work in the areas of DAA Well Clear Recovery logic and alert stability for Mode-C-only intruders. Finally, results demonstrated a high level of compliance with a set of evaluation criteria designed to provide anecdotal evidence of acceptable UAS DAA system performance.
Magic Draw is a tool currently being used by System Engineers to design model-based representations of the Resource Prospector (RP) Payload. Often, reports are needed to display and communicate the information and schematics within the MagicDraw model. Since constant changes are being made to the model, these reports also need to be maintained with each change. Because this is tedious and time consuming, I was assigned to implement MagicDraw Report Wizard Templates using Velocity Template Language (VTL) scripts. These report template scripts pull specific images, data, and elements directly from the MagicDraw model, allowing the user to have a report that is updated with the current state of the model upon its generation.