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.
The design and implementation of a computerized data base created to support the DSN Energy Conservation Project with data relating to energy use at Goldstone Deep Space Communications Complex are described. The results of development work to date, are presented along with work currently in progress or in the planning stage.
Dawn is a low-thrust interplanetary spacecraft currently orbiting the dwarf planet Ceres, to better understand the early creation of the solar system. Launched in September 2007, Dawn arrived at Vesta in July 2011. After a 16-month successful science campaign at Vesta, Dawn departed for Ceres, arriving in early 2015. The Dawn spacecraft uses both reaction wheel assemblies (RWA) and a reaction control system (RCS) to provide 3-axis attitude control for the spacecraft. Reaction wheels were designed to be the primary system for attitude control, however two wheels have shown high friction anomalies and have been removed from service. The project has implemented a hybrid control algorithm using two reaction wheels and RCS thrusters. This hybrid control capability enabled Dawn to achieve very high science return, while significantly conserving remaining hydrazine propellant. With only two remaining healthy RWA’s, hybrid control became part of the baseline plan for Ceres science operations. The Dawn team developed specific operational approaches in which sequences were developed with careful consideration of science versus resource trades. Commanding and sequence planning also incorporated contingency planning, in the event that another reaction wheel may fail. Despite the differences in operational approach between Vesta and Ceres, both campaigns achieved very rich scientific data return. This paper highlights Dawn’s recent flight experience with hybrid attitude control during Ceres orbit operations. The discussion includes the approaches utilized by the Dawn team to address unique operational challenges presented by the hybrid approach, and reviews spacecraft performance under hybrid control in low orbit at Ceres. Additionally, methods used to optimize hydrazine use and thereby extend the science campaign will be presented. Finally, a preliminary assessment of an orbit transfer with two reaction wheels, during extended mission operations, is discussed.
It is often the case in software projects that when schedule and budget resources are limited, the Verification and Validation (V&V) activities suffer. Fewer V&V activities can be afforded and moreover, short-term challenges can result in V&V activities being scaled back or dropped altogether. As a result, too often the default solution is to save activities for improving software quality until too late in the life-cycle, relying on late-term code inspections followed by thorough testing activities to reduce defect counts to acceptable levels. As many project managers realize, however, this is a resource-intensive way of achieving the required quality for software. The Full Life-cycle Defect Management Assessment Initiative, funded by NASA s Office of Safety and Mission Assurance under the Software Assurance Research Program, aims to address these problems by: Improving the effectiveness of early life-cycle V&V activities to make their benefits more attractive to team leads. Specifically, we focus on software inspection, a proven method that can be applied to any software work product, long before executable code has been developed; Better communicating this effectiveness to software development teams, along with suggestions for parameters to improve in the future to increase effectiveness; Analyzing the impact of early life-cycle V&V on the effectiveness and cost required for late life-cycle V&V activities, such as testing, in order to make the tradeoffs more apparent. This white paper reports on an initial milestone in this work, the development of a preliminary model of inspection effectiveness across multiple NASA Centers. This model contributes toward reaching our project goals by: Allowing an examination of inspection parameters, across different types of projects and different work products, for an analysis of factors that impact defect detection effectiveness. Allowing a comparison of this NASA-specific model to existing recommendations in the literature regarding how to plan effective inspections. Forming a baseline model which can be extended to incorporate factors describing: the numbers and types of defects that are missed by inspections; how such defects flow downstream through software development phases; how effectively they can be caught by testing activities in the late stages of development. The model has been implemented in a prototype web-enabled decision-support tool which allows developers to enter their inspection data and receive feedback based on a comparison against the model. The tool also allows users to access reusable materials (such as checklists) from projects included in the baseline. Both the tool itself and the model underlying it will continue to be extended throughout the remainder of this initiative. As results of analyzing inspection effectiveness for defect containment are determined, they can be shared via the tool and also via updates to existing training courses on metrics and software inspections. Moreover, the tool will help satisfy key CMMI requirements for the NASA Centers, as it will enable NASA to take a global view across peer review results for various types of projects to identify systemic problems. This analysis can result in continuous improvements to the approach to verification.
This paper discusses the efforts to create, using two NASA SP2 supercomputers, a 'Metacenter' which includes the capability to transparently and dynamically distribute the SP2 workload across the geographically separated systems. Functional components of the Phase 1 Metacenter are identified, outstanding issues are discussed, and the plan for the second phase of the project is outlined.
The NASA Communications (Nascom) System Development Plan (NSDP), reissued annually, describes the organization of Nascom, how it obtains communication services, its current systems, its relationship with other NASA centers and International Partner Agencies, some major spaceflight projects which generate significant operational communication support requirements, and major Nascom projects in various stages of development or implementation.
The Integrated Science Instrument Module (ISIM) of the James Webb Space Telescope will be integrated and tested at the Environmental Test Facilities at Goddard Space Flight Center (GSFC). The cryogenic thermal vacuum testing of the ISIM will be the most difficult and problematic portion of the GSFC Integration and Test flow. The test is to validate the coupled interface of the science instruments and the ISIM structure and to sufficiently stress that interface while validating image quality of the science instruments. The instruments and the structure are not made from the same materials and have different CTE. Test objectives and verification rationale are currently being evaluated in Phase B of the project plan. The test program will encounter engineering challenges and limitations, which are derived by cost and technology many of which can be mitigated by facility upgrades, creative GSE, and thorough forethought. The cryogenic testing of the ISIM will involve a number of risks such as the implementation of unique metrology techniques, mechanical, electrical and optical simulators housed within the cryogenic vacuum environment. These potential risks are investigated and possible solutions are proposed.
Producing multiple versions of the same data product for the same time frame with the same remotely sensed inputs can be a recipe for disaster. Yet, amidst the commotion of satellite launch and early operations (LEO), such data processing is needed. After LEO, the situation gets worse. Processing newly arriving data ("forward processing") is augmented with reprocessing and algorithm development, comparison, evaluation, and testing -- often happening all at the same time. The problem can be analyzed in three main parts -- maintaining multiple versions of algorithms and data so that end-product users are not overwhelmed,allocating computer resources efficiently, and simplifying production operations so that va st amounts of data can be processed with minimal staff and fewer errors. OMIDAPS provides a framework for execution of algorithms that transform lower level data acquired by OMI on NASA's Aura satellite into higher level science data products. In contrast to traditional science data processing systems, we address all parts of the problem with an innovative approach allowing multiple data processing to run within a single physical system. The data products, imports, exports, and execution planning are all segregated into distinct "ArchiveSets." This paper describes reasons for multiple concurrent productions on a typical satellite data processing project using OMI as an example. It describes the virtual data processing system concept and its advantages over separate physical processing strings. It explores the specific implementation of the virtual systems within OMIDAPS and discusses some of the implications of our approach and describes how virtual processing is used to accomplish the overall mission of OMI data processing.
MOPSS is a generic framework that can be configured on the fly to support a wide range of planning and scheduling applications. It is currently used to support seven missions at Goddard Space Flight Center (GSFC) in roles that include science planning, mission planning, and real-time control. Prior to MOPSS, each spacecraft project built its own planning and scheduling capability to plan satellite activities and communications and to create the commands to be uplinked to the spacecraft. This approach required creating a data repository for storing planning and scheduling information, building user interfaces to display data, generating needed scheduling algorithms, and implementing customized external interfaces. Complex scheduling problems that involved reacting to multiple variable situations were analyzed manually. Operators then used the results to add commands to the schedule. Each architecture was unique to specific satellite requirements. MOPSS is an expert system that automates mission operations and frees the flight operations team to concentrate on critical activities. It is easily reconfigured by the flight operations team as the mission evolves. The heart of the system is a custom object-oriented data layer mapped onto an Oracle relational database. The combination of these two technologies allows a user or system engineer to capture any type of scheduling or planning data in the system's generic data storage via a GUI.
The Behavioral Health and Performance discipline at NASA Johnson Space Center is organized into two distinct Divisions (Biomedical Research and Environmental Science Division and Space and Clinical Operations Division) but is integrated and interrelated in its day‐to‐day work. Ongoing operations supporting NASA's spaceflight goals benefit from the research portfolios that address risks to mission success. Similarly, these research portfolios are informed by operations to ensure investigations stay relevant given the dynamic environment of spaceflight. There are many success stories that can be presented where initial work begun as a BHP Research project, and funded through the Human Research Program, was fully implemented in operations or addressed an operational need. Examples include improving effectiveness of the debriefings used within Mission Control by the Mission Operations Directorate and countermeasures for fatigue management. There is also ongoing collaboration with research and operations for developing selection methods for future generation astronauts, and to enhance and inform the current family support function. The objective of this panel is to provide examples of recent success stories, describe areas where close collaboration is benefitting ongoing research and operations, and summarize how this will come together as NASA plans for the one year ISS mission - a unique opportunity for both BHP operations and research to learn more about preparing and supporting crewmembers for extended missions in space. The proposed panel will be comprised of six presentations, each describing a unique aspect of research or operations and the benefits to current and future spaceflight.
Once a "Troubled Project" threatened with cancellation, the Stratospheric Observatory for Infrared Astronomy (SOFIA) Program has overcome many difficult challenges and recently achieved its first light images. To achieve success, SOFIA had to overcome significant deficiencies in fundamental Systems Engineering identified during a major Program restructuring. This presentation will summarize the lessons learn in Systems Engineering on the SOFIA Program. After the Program was reformulated, an initial assessment of Systems Engineering established the scope of the problem and helped to set a list of priorities that needed to be work. A revised Systems Engineering Management Plan (SEMP) was written to address the new Program structure and requirements established in the approved NPR7123.1A. An important result of the "Technical Planning" effort was the decision by the Program and Technical Leadership team to re-phasing the lifecycle into increments. The reformed SOFIA Program Office had to quickly develop and establish several new System Engineering core processes including; Requirements Management, Risk Management, Configuration Management and Data Management. Implementing these processes had to consider the physical and cultural diversity of the SOFIA Program team which includes two Projects spanning two NASA Centers, a major German partnership, and sub-contractors located across the United States and Europe. The SOFIA Program experience represents a creative approach to doing "System Engineering in the middle" while a Program is well established. Many challenges were identified and overcome. The SOFIA example demonstrates it is never too late to benefit from fixing deficiencies in the System Engineering processes.
This presentation summarizes the Interagency Modeling and Analysis Group (IMAG) / Multiscale Modeling (MSM)'s Committee on Credible Practice in Modeling and Simulation in Healthcare's (CPMS) mid-term review of each MSM U01 project's progress toward fulfilling their Model Credibility plan. Generally, the model credibility reporting and update process utilized several pieces of information formatted to communicate to the uninformed reviewer/user an assessment of steps taken toward model credibility with respect to the intended use of each U01 model, as well as communicate where the more interested reviewer/user can go to find more information. The reviewers, consisting of the members of the CPMS Executive Committee, focused on the documentation and communication of each PI's credibility efforts and did not perform an assessment of the implemented credible practice given the evolving nature of the projects. In this inaugural activity, the CPMS members sought insight on how PIs may view the importance of communicating credibility, as well as how PIs interpret establishing evidence for credibility within the scope of CPMS Tens simple rules. To that end, reviewers provided feedback on documentation and communication adequacy, and, only in few rare cases, on the credible practice itself.
The Astrobee Project has completed three years operating inside the ISS. Three Astrobee Free Flyers reached the ISS in April 2019 and are currently hosting a variety of users. During this time, Astrobee has advanced the state of the art in free-flying robots on ISS, operated over 100 sessions, logged over 750 hours of free-flyer operation, and made several capability improvements. Astrobee’s primary objective is to provide a highly flexible and capable free-flying robotic research platform to enable future guest scientist investigations. However, Astrobee is also demonstrating the feasibility of intra-vehicular robots (IVR) for performing key caretaking functions within exploration vehicles as part of NASA’s Moon-to-Mars exploration strategy. IVR capabilities will be especially vital during uncrewed mission phases. For example, current plans call for the lunar Gateway to be uncrewed >85% of the time. Astrobee’s baseline implementation supports free-flying camera and sensor survey use cases. Astrobee guest scientists can deploy software updates and hardware payloads to extend its capabilities. Astrobee is continuously improving its navigation robustness, general flight software maturity, and ISS interior maps, both through the baseline Astrobee operations and with the help of the ISAAC project. Astrobee began with mapping, localization, and operations in the Japanese Experiment Module (JEM), and has expanded to mapping in Node 2 and the US Lab. Astrobee has improved localization and operational robustness through improved mapping processes, algorithm updates (Soussan 2022) that reduce the occurrences of lost localization as well as developed recovery techniques to return to a good localization fix when loss of localization does occur. Future guest science experiments currently in development could demonstrate cargo transfer, fault isolation, free flyer and stationary robot collaboration, microgravity fluid transfer, and new docking mechanisms, among others. This presentation will focus on 1) Astrobee technical capabilities 2) What Astrobee can provide to a guest science experiment 3) Astrobee’s recent improvements 4) Possibilities for using Astrobee for future investigations. Soussan, R., Kumar, V., Coltin, B. and Smith, T. (2022) AstroLoc: An Efficient and Robust Localizer for a Free-flying Robot, Proc. Int. Conf. Rob. Autom. (ICRA) [to appear]
The European Controlled Ecological Life Support System (CELSS) activities started in the late 1970's with system analysis and feasibility studies of Biological Life Support Systems (BLSS). The initiation for CELSS came from the industry side in Europe, but since then planning and hardware feasibility analyses have been initiated also from customer/agency side. Despite this, it is still too early to state that a CELSS program as a concerted effort has been agreed upon in Europe. However, the general CELSS objectives were accepted as planning and possible development goals for the European effort for manned space activities, and as experimental planning topics in the life sciences community for the next decades. It is expected that ecological life support systems can be tested and implemented on a space station towards the end of this century or early in the next. For the European activities a possible scenario can be projected based on ongoing life support system development activities and the present life sciences goals.
The plan is described for the integrated testing and benchmark of Phase Ada based ESBT Design Research Project. The integration testing is divided into two phases: (1) the modules that do not rely on the Ada code generated by the Ada Generator are tested before the Ada Generator is implemented; and (2) all modules are integrated and tested with the Ada code generated by the Ada Generator. Its performance and size as well as its functionality is verified in this phase. The target platform is a DEC Ada compiler on VAX mini-computers and VAX stations running the VMS operating system.
Airspace Technology Demonstration #3 (ATD-3) is part of NASA's Airspace Operations and Safety Program (AOSP) - specifically, its Airspace Technology Demonstrations (ATD) Project. ATD-3 is a multiyear research and development effort which proposes to develop and demonstrate automation technologies and operating concepts that enable air navigation service providers and airspace users to continuously assess weather, winds, traffic, and other information to identify, evaluate, and implement workable opportunities for flight plan route corrections that can result in significant flight time and fuel savings in en route airspace. In order to ensure that the products of this tech-transfer are relevant and useful, NASA has created strong partnerships with the FAA and key industry stakeholders. This summary document and accompanying technology artifacts satisfy the first of three Research Transition Products (RTPs) defined in the Applied Traffic Flow Management (ATFM) Research Transition Team (RTT) Plan. This transfer consists of NASA's legacy Dynamic Weather Routes (DWR) work for efficient routing for en-route weather avoidance. DWR is a ground-based trajectory automation system that continuously and automatically analyzes active airborne aircraft in en route airspace to identify opportunities for simple corrections to flight plan routes that can save significant flying time, at least five minutes wind-corrected, while avoiding weather and considering traffic conflicts, airspace sector congestion, special use airspace, and FAA routing restrictions. The key benefit of the DWR concept is to let automation continuously and automatically analyze active flights to find those where simple route corrections can save significant time and fuel. Operators are busy during weather events. It is more effective to let automation find the opportunities for high-value route corrections.
On the one hand, locating the right dataset, then figuring out how to use it, is a daunting task that is familiar to almost any scientist or graduate student in the fields of Earth system science. On the other hand, the ability to explore authentic Earth system science data, through inquiry-based education, is an important goal in US national education standards. Fortunately, in the digital age, tools are emerging that can make such data exploration commonplace at all educational levels. This paper describes the conception and development of one project that aims to bridge this gap: Mentoring and inquiry using NASA Data on Atmospheric and Earth science for Teachers and Amateurs (MY NASA DATA; mynasadata.larc.nasa.gov). With funding from NASA's Science Mission Directorate, this project was launched in early 2004 with the aim of developing microsets and identifying other enablers for making data accessible. A key feature of the project is a Live Access Server, the first educational implementation of this open source software, developed by NOAA, that makes it possible to explore multiple data formats through a single interface. This powerful tool is made more useful to the primary target audiences (K-12 and amateur scientists) through careful selection of the data offered, user-friendly explanations of the tool itself, and age-appropriate explanations of the parameters. However experience already shows that graduate students and even practicing scientists can also make use of this resource. The website also hosts teacher-contributed lesson plans, and seeks to feature reports of research projects that use the data.
The research and applications modules (RAM) system is discussed. The RAM is a family of payload carrier modules that can be delivered to and retrieved from earth orbit by the space shuttle. The RAM's capability for implementing a wide range of manned and man-tended missions is described. The rams have evolved into three types; (1) pressurized RAMs, (2) unpressurized RAMs, and (3) pressurizable free-flying RAMs. A reference experiment plan for use as a baseline in the derivation and planning of the RAM project is reported. The plan describes the number and frequency of shuttle flights dedicated to RAM missions and the RAM payloads for the identified flights.
An interactive computerized project management software package (RISKNET) is designed to analyze the effect of the risk involved in each specific activity on the results of the total SEASAT-A program. Both the time and the cost of each distinct activity can be modeled with an uncertainty interval so as to provide the project manager with not only the expected time and cost for the completion of the total program, but also with the expected range of costs corresponding to any desired level of significance. The nature of the SEASAT-A program is described. The capabilities of RISKNET and the implementation plan of a RISKNET analysis for the development of SEASAT-A are presented.