Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Learning”

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.

At least 1,171 records · Page 65

Operational Lessons Learned from NASA Analog Missions

National Aeronautics and Space Administration s (NASA) efforts in human space flight are currently focused on the Space Shuttle and International Space Station (ISS) programs, with efforts beginning on the future exploration opportunities. Both the Space Shuttle and ISS programs are important to the development of a capability for human exploration beyond Low Earth Orbit (LEO). The ISS provides extensive research capabilities to determine how the human body reacts to long duration stays in space. Also, the ISS and Shuttle can serve as a limited testbed for equipment or entire systems that may be used on missions to the Moon, Mars, or to a near-Earth asteroid. It has been nearly 35 years since the Apollo astronauts visited the Moon. Future space explorers will have to re-learn how to work and live on planetary surfaces, and how to do that for extended periods of time. Exploration crews will perform a wide assortment of scientific tasks, including material sampling and emplacement of automated instruments. Surface mission operations include the activities of the crew living and working, mission support from the Earth, and the operation of robotic and other remotely commanded equipment on the surface and in planetary orbit. Other surface activities will include the following: exploring areas surrounding a habitat; using rovers to collect rock and soil samples; setting up experiments on the surface to monitor the radiation environment and any seismic or thermal activity; and conducting scientific analyses and experiments inside a habitat laboratory. Of course, the astronauts will also have to spend some of their surface time "doing chores" and maintaining their habitat and other systems. In preparation for future planetary exploration, NASA must design the answers to many operational questions. What will the astronauts do on the surface? How will they accomplish this? What tools will they require for their tasks? How will robots and astronauts work together? What vehicle and system capabilities are required to support the activities? How will the crew and the Earth-based mission control team interact? During the initial phases of manned planetary exploration, one challenge in particular is virtually the same as during the Apollo program: How can scientific return be maximized during a relatively short surface mission? Today, NASA is investigating solutions to these challenges by conducting analog missions. These Earth-based missions possess characteristics that are analogous to missions on the Moon or Mars. These missions are excellent for testing operational concepts, and the design, configuration, and functionality of spacesuits, robots, rovers, and habitats. Analog mission crews test specific techniques and procedures for surface field geology, biological sample collection, and planetary protection. The process of actually working an analog mission reveals a myriad of small details, which either contribute to or impede efficient operations, many of which would never have been thought about otherwise. It also helps to define the suite of tools, containers, and other small equipment that surface explorers will use. This paper focuses on how analog missions have addressed selected operational considerations for future planetary missions.

Arnold, Larissa S.↗

Flight Planning Branch Space Shuttle Lessons Learned

Planning products and procedures that allow the mission flight control teams and the astronaut crews to plan, train and fly every Space Shuttle mission have been developed by the Flight Planning Branch at the NASA Johnson Space Center. As the Space Shuttle Program ends, lessons learned have been collected from each phase of the successful execution of these Shuttle missions. Specific examples of how roles and responsibilities of console positions that develop the crew and vehicle attitude timelines will be discussed, as well as techniques and methods used to solve complex spacecraft and instrument orientation problems. Additionally, the relationships and procedural hurdles experienced through international collaboration have molded operations. These facets will be explored and related to current and future operations with the International Space Station and future vehicles. Along with these important aspects, the evolution of technology and continual improvement of data transfer tools between the shuttle and ground team has also defined specific lessons used in the improving the control teams effectiveness. Methodologies to communicate and transmit messages, images, and files from Mission Control to the Orbiter evolved over several years. These lessons have been vital in shaping the effectiveness of safe and successful mission planning that have been applied to current mission planning work in addition to being incorporated into future space flight planning. The critical lessons from all aspects of previous plan, train, and fly phases of shuttle flight missions are not only documented in this paper, but are also discussed as how they pertain to changes in process and consideration for future space flight planning.

Price, Jennifer B.↗

Lessons Learned from Three Recent Sample Return Missions

We share lessons learned from participation on the Science Teams and Recovery/Preliminary Examination/Curation teams for three recent sample return missions: (1) the Long Duration Exposure Facility (LDEF), which returned to Earth with interplanetary dust and spacecraft debris particles in 1990, (2) the Stardust Mission, which returned grains from comet Wild-2 and fresh interstellar dust to Earth in 2006, and (3) the Hayabusa Mission, which returned regolith grains from asteroid Itokawa in 2010.

Zolensky, Michael E.↗

Hayabusa Recovery, Curation and Preliminary Sample Analysis: Lessons Learned from Recent Sample Return Mission

I describe lessons learned from my participation on the Hayabusa Mission, which returned regolith grains from asteroid Itokawa in 2010 [1], comparing this with the recently returned Stardust Spacecraft, which sampled the Jupiter Family comet Wild 2. Spacecraft Recovery Operations: The mission Science and Curation teams must actively participate in planning, testing and implementing spacecraft recovery operations. The crash of the Genesis spacecraft underscored the importance of thinking through multiple contingency scenarios and practicing field recovery for these potential circumstances. Having the contingency supplies on-hand was critical, and at least one full year of planning for Stardust and Hayabusa recovery operations was necessary. Care must be taken to coordinate recovery operations with local organizations and inform relevant government bodies well in advance. Recovery plans for both Stardust and Hayabusa had to be adjusted for unexpectedly wet landing site conditions. Documentation of every step of spacecraft recovery and deintegration was necessary, and collection and analysis of launch and landing site soils was critical. We found the operation of the Woomera Text Range (South Australia) to be excellent in the case of Hayabusa, and in many respects this site is superior to the Utah Test and Training Range (used for Stardust) in the USA. Recovery operations for all recovered spacecraft suffered from the lack of a hermetic seal for the samples. Mission engineers should be pushed to provide hermetic seals for returned samples. Sample Curation Issues: More than two full years were required to prepare curation facilities for Stardust and Hayabusa. Despite this seemingly adequate lead time, major changes to curation procedures were required once the actual state of the returned samples became apparent. Sample databases must be fully implemented before sample return for Stardust we did not adequately think through all of the possible sub sampling and analytical activities before settling on a database design - Hayabusa has done a better job of this. Also, analysis teams must not be permitted to devise their own sample naming schemes. The sample handling and storage facilities for Hayabusa are the finest that exist, and we are now modifying Stardust curation to take advantage of the Hayabusa facilities. Remote storage of a sample subset is desirable. Preliminary Examination (PE) of Samples: There must be some determination of the state and quantity of the returned samples, to provide a necessary guide to persons requesting samples and oversight committees tasked with sample curation oversight. Hayabusa s sample PE, which is called HASPET, was designed so that late additions to the analysis protocols were possible, as new analytical techniques became available. A small but representative number of recovered grains are being subjected to in-depth characterization. The bulk of the recovered samples are being left untouched, to limit contamination. The HASPET plan takes maximum advantage of the unique strengths of sample return missions

Zolensky, Michael E.↗

Constellation Lessons Learned Executive Summary

This slide presentation reviews the lessons learned from the Constellation Program (CxP) and identified several factors that contributed to the inability of the CxP to meet the cost and schedule commitments. The review includes a significant section on the context in which the CxP operated since new programs are likely to experience the same constraints.

Thomas, L. Dale↗

Safety and Mission Assurance for In-House Design Lessons Learned from Ares I Upper Stage

This viewgraph presentation identifies lessons learned in the course of the Ares I Upper Stage design and in-house development effort. The contents include: 1) Constellation Organization; 2) Upper Stage Organization; 3) Presentation Structure; 4) Lesson-Importance of Systems Engineering/Integration; 5) Lesson-Importance of Early S&MA Involvement; 6) Lesson-Importance of Appropriate Staffing Levels; 7) Lesson-Importance S&MA Team Deployment; 8) Lesson-Understanding of S&MA In-Line Engineering versus Assurance; 9) Lesson-Importance of Close Coordination between Supportability and Reliability/Maintainability; 10) Lesson-Importance of Engineering Data Systems; 11) Lesson-Importance of Early Development of Supporting Databases; 12) Lesson-Importance of Coordination with Safety Assessment/Review Panels; 13) Lesson-Implementation of Software Reliability; 14) Lesson-Implementation of S&MA Technical Authority/Chief S&MA Officer; 15) Lesson-Importance of S&MA Evaluation of Project Risks; 16) Lesson-Implementation of Critical Items List and Government Mandatory Inspections; 17) Lesson-Implementation of Critical Items List Mandatory Inspections; 18) Lesson-Implementation of Test Article Safety Analysis; and 19) Lesson-Importance of Procurement Quality.

Anderson, Joel M.↗

SOFIA Program SE and I Lessons Learned

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.

Ray, Ronald J.↗

Lessons Learned from CFD Validation Study of Protuberance Heating

The objectives of this presentation are: (1) Share lessons learned from a recent exercise in CFD validation of protuberance heating (2) Impact of experimental data reduction assumptions and techniques on validation activity (3) Advanced data reduction techniques may provide useful data from non-typical test methods (4) Significance of the recovery factor for high-speed flows (5) Show typical results of the Lag turbulence model on protuberances (6) Introduce and inform the listener of a protuberance heating dataset which will soon be available for comparison

Oliver, Brandon↗

A Summary of the Rendezvous, Proximity Operations, Docking, and Undocking (RPODU) Lessons Learned from the Defense Advanced Research Project Agency (DARPA) Orbital Express (OE) Demonstration System Mission

The Guidance, Navigation, and Control (GN&C) Technical Discipline Team (TDT) sponsored Dr. J. Russell Carpenter, a Navigation and Rendezvous Subject Matter Expert (SME) from NASA's Goddard Space Flight Center (GSFC), to provide support to the Defense Advanced Research Project Agency (DARPA) Orbital Express (OE) rendezvous and docking flight test that was conducted in 2007. When that DARPA OE mission was completed, Mr. Neil Dennehy, NASA Technical Fellow for GN&C, requested Dr. Carpenter document his findings (lessons learned) and recommendations for future rendezvous missions resulting from his OE support experience. This report captures lessons specifically from anomalies that occurred during one of OE's unmated operations.

Dennehy, Cornelius J.↗

Digi Island: A Serious Game for Teaching and Learning Digital Circuit Optimization

Karnaugh maps, also known as K-maps, are a tool used to optimize or simplify digital logic circuits. A K-map is a graphical display of a logic circuit. K-map optimization is essentially the process of finding a minimum number of maximal aggregations of K-map cells. with values of 1 according to a set of rules. The Digi Island is a serious game designed for aiding students to learn K-map optimization. The game takes place on an exotic island (called Digi Island) in the Pacific Ocean . The player is an adventurer to the Digi Island and will transform it into a tourist attraction by developing real estates, such as amusement parks.and hotels. The Digi Island game elegantly converts boring 1s and Os in digital circuits into usable and unusable spaces on a beautiful island and transforms K-map optimization into real estate development, an activity with which many students are familiar and also interested in. This paper discusses the design, development, and some preliminary results of the Digi Island game.

Harper, Michael↗

Markov Chain Monte Carlo Bayesian Learning for Neural Networks

Conventional training methods for neural networks involve starting al a random location in the solution space of the network weights, navigating an error hyper surface to reach a minimum, and sometime stochastic based techniques (e.g., genetic algorithms) to avoid entrapment in a local minimum. It is further typically necessary to preprocess the data (e.g., normalization) to keep the training algorithm on course. Conversely, Bayesian based learning is an epistemological approach concerned with formally updating the plausibility of competing candidate hypotheses thereby obtaining a posterior distribution for the network weights conditioned on the available data and a prior distribution. In this paper, we developed a powerful methodology for estimating the full residual uncertainty in network weights and therefore network predictions by using a modified Jeffery's prior combined with a Metropolis Markov Chain Monte Carlo method.

Goodrich, Michael S.↗

The Story Behind the Numbers: Lessons Learned from the Integration of Monitoring Resources in Addressing an ISS Water Quality Anomaly

Beginning in June of 2010 an environmental mystery was unfolding on the International Space Station (ISS). The U.S. Water Processor Assembly (WPA) began to produce water with increasing levels of total organic carbon (TOC). A surprisingly consistent upward TOC trend was observed through weekly in-flight total organic carbon analyzer (TOCA) monitoring. As TOC is a general organics indicator, return of water archive samples was needed to make better-informed crew health decisions and to aid in WPA troubleshooting. TOCA-measured TOC was more than halfway to its health-based screening limit before archive samples could be returned on Soyuz 22 and analyzed. Although TOC was confirmed to be elevated, somewhat surprisingly, none of the typical target compounds were the source. After some solid detective work, it was confirmed that the TOC was associated with a compound known as dimethylsilanediol (DMSD). DMSD is believed to be a breakdown product of silicon-containing compounds present on ISS. A toxicological limit was set for DMSD and a forward plan developed for operations given this new understanding of the source of the TOC. This required extensive coordination with ISS stakeholders and innovative use of available in-flight and archive monitoring resources. Behind the numbers and scientific detail surrounding this anomaly, there exists a compelling story of multi-disciplinary awareness, teamwork, and important environmental lessons learned.

McCoy, Torin↗

Lessons Learned from the Space Shuttle Engine Hydrogen Flow Control Valve Poppet Breakage

The Main Propulsion System (MPS) uses three Flow Control Valves (FCV) to modulate the flow of pressurant hydrogen gas from the Space Shuttle Main Engines (SSME) to the hydrogen External Tank (ET). This maintains pressure in the ullage volume as the liquid level drops, preserving ET structural integrity and assuring the engines receive a sufficient amount of head pressure. On Space Transportation System (STS)-126 (2009), with only a handful of International Space Station (ISS) assembly flights from the end of the Shuttle program, a portion of a single FCV?s poppet head broke off at about a minute and a half after liftoff. The risk of the poppet head failure is that the increased flow area through the FCV could result in excessive gaseous hydrogen flow back to the external tank, which could result in overboard venting of hydrogen ullage pressure. If the hydrogen venting were to occur in first stage (i.e., lower atmosphere), a flammability hazard exists that could lead to catastrophic loss of crew and vehicle. Other failure risks included particle impact damage to MPS downstream hardware. Although the FCV design had been plagued by contamination-related sluggish valve response problems prior to a redesign at STS-80 (1996), contamination was ruled out as the cause of the STS-126 failure. Employing a combination of enhanced hardware inspection and a better understanding of the consequences of a poppet failure, safe flight rationale for subsequent flights (STS-119 and later) was achieved. This paper deals with the technical lessons learned during the investigation and mitigation of this problem at a time when assembly flights were each in the critical path to Space Station success.

Martinez, Hugo E.↗

Microbiological Lessons Learned from the Space Shuttle

After 30 years of being the centerpiece of NASA s human spacecraft, the Space Shuttle will retire. This highly successful program provided many valuable lessons for the International Space Station (ISS) and future spacecraft. Major microbiological risks to crewmembers include food, water, air, surfaces, payloads, animals, other crewmembers, and ground support personnel. Adverse effects of microorganisms are varied and can jeopardize crew health and safety, spacecraft systems, and mission objectives. Engineering practices and operational procedures can minimize the negative effects of microorganisms. To minimize problems associated with microorganisms, appropriate steps must begin in the design phase of new spacecraft or space habitats. Spacecraft design must include requirements to control accumulation of water including humidity, leaks, and condensate on surfaces. Materials used in habitable volumes must not contribute to microbial growth. Use of appropriate materials and the implementation of robust housekeeping that utilizes periodic cleaning and disinfection will prevent high levels of microbial growth on surfaces. Air filtration can ensure low levels of bioaerosols and particulates in the breathing air. The use of physical and chemical steps to disinfect drinking water coupled with filtration can provide safe drinking water. Thorough preflight examination of flight crews, consumables, and the environment can greatly reduce pathogens in spacecraft. The advances in knowledge of living and working onboard the Space Shuttle formed the foundation for environmental microbiology requirements and operations for the International Space Station (ISS) and future spacecraft. Research conducted during the Space Shuttle Program resulted in an improved understanding of the effects of spaceflight on human physiology, microbial properties, and specifically the host-microbe interactions. Host-microbe interactions are substantially affected by spaceflight. Astronaut immune functions were found to be altered. Selected microorganisms were found to become more virulent during spaceflight. The increased knowledge gained on the Space Shuttle resulted in further studies of the host-microbe interactions on the ISS to determine if countermeasures were necessary. Lessons learned from the Space Shuttle Program were integrated into the ISS resulting in the safest space habitat to date.

Pierson, Duane L.↗

International Space Station Passive Thermal Control System Analysis, Top Ten Lessons-Learned

The International Space Station (ISS) has been on-orbit for over 10 years, and there have been numerous technical challenges along the way from design to assembly to on-orbit anomalies and repairs. The Passive Thermal Control System (PTCS) management team has been a key player in successfully dealing with these challenges. The PTCS team performs thermal analysis in support of design and verification, launch and assembly constraints, integration, sustaining engineering, failure response, and model validation. This analysis is a significant body of work and provides a unique opportunity to compile a wealth of real world engineering and analysis knowledge and the corresponding lessons-learned. The analysis lessons encompass the full life cycle of flight hardware from design to on-orbit performance and sustaining engineering. These lessons can provide significant insight for new projects and programs. Key areas to be presented include thermal model fidelity, verification methods, analysis uncertainty, and operations support.

Iovine, John↗

Software for Secondary-School Learning About Robotics

The ROVer Ranch is an interactive computer program designed to help secondary-school students learn about space-program robotics and related basic scientific concepts by involving the students in simplified design and programming tasks that exercise skills in mathematics and science. The tasks involve building simulated robots and then observing how they behave. The program furnishes (1) programming tools that a student can use to assemble and program a simulated robot and (2) a virtual three-dimensional mission simulator for testing the robot. First, the ROVer Ranch presents fundamental information about robotics, mission goals, and facts about the mission environment. On the basis of this information, and using the aforementioned tools, the student assembles a robot by selecting parts from such subsystems as propulsion, navigation, and scientific tools, the student builds a simulated robot to accomplish its mission. Once the robot is built, it is programmed and then placed in a three-dimensional simulated environment. Success or failure in the simulation depends on the planning and design of the robot. Data and results of the mission are available in a summary log once the mission is concluded.

Shelton, Robert O.↗

Constellation Program Lessons Learned in the Quantification and Use of Aerodynamic Uncertainty

The NASA Constellation Program has worked for the past five years to develop a re- placement for the current Space Transportation System. Of the elements that form the Constellation Program, only two require databases that define aerodynamic environments and their respective uncertainty: the Ares launch vehicles and the Orion crew and launch abort vehicles. Teams were established within the Ares and Orion projects to provide repre- sentative aerodynamic models including both baseline values and quantified uncertainties. A technical team was also formed within the Constellation Program to facilitate integra- tion among the project elements. This paper is a summary of the collective experience of the three teams working with the quantification and use of uncertainty in aerodynamic environments: the Ares and Orion project teams as well as the Constellation integration team. Not all of the lessons learned discussed in this paper could be applied during the course of the program, but they are included in the hope of benefiting future projects.

Walker, Eric L.↗