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,117 records · Page 62

Digital Learning Network Education Events for the Desert Research and Technology Studies

NASA s Digital Learning Network (DLN) reaches out to thousands of students each year through video conferencing and webcasting. As part of NASA s Strategic Plan to reach the next generation of space explorers, the DLN develops and delivers educational programs that reinforce principles in the areas of science, technology, engineering and mathematics. The DLN has created a series of live education videoconferences connecting the Desert Research and Technology Studies (RATS) field test to students across the United States. The programs are also extended to students around the world via live webcasting. The primary focus of the events is the Vision for Space Exploration. During the programs, Desert RATS engineers and scientists inform and inspire students about the importance of exploration and share the importance of the field test as it correlates with plans to return to the Moon and explore Mars. This paper describes the events that took place in September 2006.

Paul, Heather L.↗

Lessons Learned from Daily Uplink Operations during the Deep Impact Mission

The Deep Impact mission to comet Tempel-1 produced some of the more spectacular science results ever collected by a spacecraft. On July 4, 2005 the Deep Impact Flyby vehicle observed the Deep Impact Impactor vehicle's collision with the comet. 24 hours earlier the Flyby vehicle released the Impactor vehicle into the path of comet Tempel-1. The process to command the spacecraft was a challenge to the entire flight operations team. This paper presents an overview of the process used prepare command products for uplink and the lessons that were learned from this process.

mission operations↗

International Space Station Materials: Selected Lessons Learned

The International Space Station (ISS) program is of such complexity and scale that there have been numerous issues addressed regarding safety of materials: from design to manufacturing, test, launch, assembly on-orbit, and operations. A selection of lessons learned from the ISS materials perspective will be provided. Topics of discussion are: flammability evaluation of materials with connection to on-orbit operations; toxicity findings for foams; compatibility testing for materials in fluid systems; and contamination control in precision clean systems and critical space vehicle surfaces.

Golden, Johnny L.↗

Staffing the ISS Control Centers: Lessons Learned from Long-Duration Human Space Flight

The International Space Station (ISS) has been in operation with a permanent human presence in space for over five years, and plans for continued operations stretch ten years into the future. Ground control and support operations are, likewise, a 15-year enterprise. This long-term, 24-hour per day, 7 day per week support has presented numerous challenges in the areas of ground crew training, initial and continued certification, and console staffing. The Mission Control Center in Houston, Texas and the Payload Operations Center in Huntsville, Alabama have both tackled these challenges, with similar, yet distinct, approaches. This paper describes the evolution of the staffing and training policies of both control centers in a chronological progression. The relative merits and shortcomings of the various policies employed are discussed and a summary of "lessons learned" is presented. Finally, recommendations are made as best practices for future long-term space missions.

Olsen, Carrie D.↗

Lessons Learned from the Node 1 Sample Delivery Subsystem Design

This paper will provide an overview of the International Space Station (ISS) Environmental Control and Life Support (ECLS) design of the Node 1 Sample Delivery Subsystem (SDS) and it will document some of the lessons that have been learned to date for this part of the subsystem.

Williams, David E.↗

Spitzer Space Telescope Sequencing Operations Software, Strategies, and Lessons Learned

The Space Infrared Telescope Facility (SIRTF) was launched in August, 2003, and renamed to the Spitzer Space Telescope in 2004. Two years of observing the universe in the wavelength range from 3 to 180 microns has yielded enormous scientific discoveries. Since this magnificent observatory has a limited lifetime, maximizing science viewing efficiency (ie, maximizing time spent executing activities directly related to science observations) was the key operational objective. The strategy employed for maximizing science viewing efficiency was to optimize spacecraft flexibility, adaptability, and use of observation time. The selected approach involved implementation of a multi-engine sequencing architecture coupled with nondeterministic spacecraft and science execution times. This approach, though effective, added much complexity to uplink operations and sequence development. The Jet Propulsion Laboratory (JPL) manages Spitzer s operations. As part of the uplink process, Spitzer s Mission Sequence Team (MST) was tasked with processing observatory inputs from the Spitzer Science Center (SSC) into efficiently integrated, constraint-checked, and modeled review and command products which accommodated the complexity of non-deterministic spacecraft and science event executions without increasing operations costs. The MST developed processes, scripts, and participated in the adaptation of multi-mission core software to enable rapid processing of complex sequences. The MST was also tasked with developing a Downlink Keyword File (DKF) which could instruct Deep Space Network (DSN) stations on how and when to configure themselves to receive Spitzer science data. As MST and uplink operations developed, important lessons were learned that should be applied to future missions, especially those missions which employ command-intensive operations via a multi-engine sequence architecture.

missions operations↗

Technical Findings, Lessons Learned, and Recommendations Resulting from the Helios Prototype Vehicle Mishap

The Helios Prototype was originally planned to be two separate vehicles, but because of resource limitations only one vehicle was developed to demonstrate two missions. The vehicle consisted of two configurations, one for each mission. One configuration, designated HP01, was designed to operate at extremely high altitudes using batteries and high-efficiency solar cells spread across the upper surface of its 247-foot wingspan. On August 13, 2001, the HP01 configuration reached an altitude of 96,863 feet, a world record for sustained horizontal flight by a winged aircraft. The other configuration, designated HP03, was designed for long-duration flight. The plan was to use the solar cells to power the vehicle's electric motors and subsystems during the day and to use a modified commercial hydrogen-air fuel cell system for use during the night. The aircraft design used wing dihedral, engine power, elevator control surfaces, and a stability augmentation and control system to provide aerodynamic stability and control. At about 30 minutes into the second flight of HP03, the aircraft encountered a disturbance in the way of turbulence and morphed into an unexpected, persistent, high dihedral configuration. As a result of the persistent high dihedral, the aircraft became unstable in a very divergent pitch mode in which the airspeed excursions from the nominal flight speed about doubled every cycle of the oscillation. The aircraft s design airspeed was subsequently exceeded and the resulting high dynamic pressures caused the wing leading edge secondary structure on the outer wing panels to fail and the solar cells and skin on the upper surface of the wing to rip away. As a result, the vehicle lost its ability to maintain lift, fell into the Pacific Ocean within the confines of the U.S. Navy's Pacific Missile Range Facility, and was destroyed. This paper describes the mishap and its causes, and presents the technical recommendations and lessons learned for improving the design, analysis, and testing methods and techniques required for this class of vehicle.

Noll, Thomas E.↗

Three Years of Hyperspectral Data from AIRS: What Have We Learned

This viewgraph presentation reviews the Atmospheric Infrared Sounder (AIRS) that is on the Aqua satellite. The expectations that were had about AIRS have been exceeded. The lessons learned from AIRS are reviewed. These lessons are used to enhance the next generation hyperspectral sounder, being planned.

accuracy↗

Development of a State Machine Sequencer for the Keck Interferometer: Evolution, Development and Lessons Learned using a CASE Tool Approach

This paper presents a discussion of the evolution of a sequencer from a simple EPICS (Experimental Physics and Industrial Control System) based sequencer into a complex implementation designed utilizing UML (Unified Modeling Language) methodologies and a CASE (Computer Aided Software Engineering) tool approach. The main purpose of the sequencer (called the IF Sequencer) is to provide overall control of the Keck Interferometer to enable science operations be carried out by a single operator (and/or observer). The interferometer links the two 10m telescopes of the W. M. Keck Observatory at Mauna Kea, Hawaii. The IF Sequencer is a high-level, multi-threaded, Hare1 finite state machine, software program designed to orchestrate several lower-level hardware and software hard real time subsystems that must perform their work in a specific and sequential order. The sequencing need not be done in hard real-time. Each state machine thread commands either a high-speed real-time multiple mode embedded controller via CORB A, or slower controllers via EPICS Channel Access interfaces. The overall operation of the system is simplified by the automation. The UML is discussed and our use of it to implement the sequencer is presented. The decision to use the Rhapsody product as our CASE tool is explained and reflected upon. Most importantly, a section on lessons learned is presented and the difficulty of integrating CASE tool automatically generated C++ code into a large control system consisting of multiple infrastructures is presented.

interferometer↗

Lessons Learned from the Wide Field Camera 3 TV1 Test Campaign and Correlation Effort

In January 2004, shortly after the Columbia accident, future servicing missions to the Hubble Space Telescope (HST) were cancelled. In response to this, further work on the Wide Field Camera 3 instrument was ceased. Given the maturity level of the design, a characterization thermal test (TV1) was completed in case the mission was re-instated or an alternate mission found on which to fly the instrument. This thermal test yielded some valuable lessons learned with respect to testing configurations and modeling/correlation practices, including: 1. Ensure that the thermal design can be tested 2. Ensure that the model has sufficient detail for accurate predictions 3. Ensure that the power associated with all active control devices is predicted 4. Avoid unit changes for existing models. This paper documents the difficulties presented when these recommendations were not followed.

Peabody, Hume↗

Lessons Learned from Deploying an Analytical Task Management Database

Defining requirements, missions, technologies, and concepts for space exploration involves multiple levels of organizations, teams of people with complementary skills, and analytical models and simulations. Analytical activities range from filling a To-Be-Determined (TBD) in a requirement to creating animations and simulations of exploration missions. In a program as large as returning to the Moon, there are hundreds of simultaneous analysis activities. A way to manage and integrate efforts of this magnitude is to deploy a centralized database that provides the capability to define tasks, identify resources, describe products, schedule deliveries, and generate a variety of reports. This paper describes a web-accessible task management system and explains the lessons learned during the development and deployment of the database. Through the database, managers and team leaders can define tasks, establish review schedules, assign teams, link tasks to specific requirements, identify products, and link the task data records to external repositories that contain the products. Data filters and spreadsheet export utilities provide a powerful capability to create custom reports. Import utilities provide a means to populate the database from previously filled form files. Within a four month period, a small team analyzed requirements, developed a prototype, conducted multiple system demonstrations, and deployed a working system supporting hundreds of users across the aeros pace community. Open-source technologies and agile software development techniques, applied by a skilled team enabled this impressive achievement. Topics in the paper cover the web application technologies, agile software development, an overview of the system's functions and features, dealing with increasing scope, and deploying new versions of the system.

O'Neil, Daniel A.↗

What can be Learned from X-ray Spectroscopy Concerning Hot Gas in Local Bubble and Charge Exchange Processes?

What can be learned from x-ray spectroscopy in observing hot gas in local bubble and charge exchange processes depends on spectral resolution, instrumental grasp, instrumental energy band, signal-to-nose, field of view, angular resolution and observatory location. Early attempts at x-ray spectroscopy include ROSAT; more recently, astronomers have used diffuse x-ray spectrometers, XMM Newton, sounding rocket calorimeters, and Suzaku. Future observations are expected with calorimeters on the Spectrum Roentgen Gamma mission, and the Solar Wind Charge Exchange (SWCX). The Geospheric SWCX may provide remote sensing of the solar wind and magnetosheath and remote observations of solar CMEs moving outward from the sun.

Snowden, Steve↗

Implementation Challenges for Multivariable Control: What You Did Not Learn in School

Multivariable control allows controller designs that can provide decoupled command tracking and robust performance in the presence of modeling uncertainties. Although the last two decades have seen extensive development of multivariable control theory and example applications to complex systems in software/hardware simulations, there are no production flying systems aircraft or spacecraft, that use multivariable control. This is because of the tremendous challenges associated with implementation of such multivariable control designs. Unfortunately, the curriculum in schools does not provide sufficient time to be able to provide an exposure to the students in such implementation challenges. The objective of this paper is to share the lessons learned by a practitioner of multivariable control in the process of applying some of the modern control theory to the Integrated Flight Propulsion Control (IFPC) design for an advanced Short Take-Off Vertical Landing (STOVL) aircraft simulation.

Garg, Sanjay↗

Learning and Prediction of Slip from Visual Information

This paper presents an approach for slip prediction from a distance for wheeled ground robots using visual information as input. Large amounts of slippage which can occur on certain surfaces, such as sandy slopes, will negatively affect rover mobility. Therefore, obtaining information about slip before entering such terrain can be very useful for better planning and avoiding these areas. To address this problem, terrain appearance and geometry information about map cells are correlated to the slip measured by the rover while traversing each cell. This relationship is learned from previous experience, so slip can be predicted remotely from visual information only. The proposed method consists of terrain type recognition and nonlinear regression modeling. The method has been implemented and tested offline on several off-road terrains including: soil, sand, gravel, and woodchips. The final slip prediction error is about 20%. The system is intended for improved navigation on steep slopes and rough terrain for Mars rovers.

rover↗

NASA's In Space Propulsion Technology Program Accomplishments and Lessons Learned

NASA's In-Space Propulsion Technology (ISPT) Program was managed for 5 years at the NASA MSFC and significant strides were made in the advancement of key transportation technologies that will enable or enhance future robotic science and deep space exploration missions. At the program's inception, a set of technology investment priorities were established using an NASA-wide, mission-driven prioritization process and, for the most part, these priorities changed little - thus allowing a consistent framework in which to fund and manage technology development. Technologies in the portfolio included aerocapture, advanced chemical propulsion, solar electric propulsion, solar sail propulsion, electrodynamic and momentum transfer tethers, and various very advanced propulsion technologies with significantly lower technology readiness. The program invested in technologies that have the potential to revolutionize the robotic exploration of deep space. For robotic exploration and science missions, increased efficiencies of future propulsion systems are critical to reduce overall life-cycle costs and, in some cases, enable missions previously considered impossible. Continued reliance on conventional chemical propulsion alone will not enable the robust exploration of deep space - the maximum theoretical efficiencies have almost been reached and they are insufficient to meet needs for many ambitious science missions currently being considered. By developing the capability to support mid-term robotic mission needs, the program was to lay the technological foundation for travel to nearby interstellar space. The ambitious goals of the program at its inception included supporting the development of technologies that could support all of NASA's missions, both human and robotic. As time went on and budgets were never as high as planned, the scope of the program was reduced almost every year, forcing the elimination of not only the broader goals of the initial program, but also of funding for over half of the technologies in the original portfolio. In addition, the frequency at which the application requirements for the program changed exceeded the development time required to mature technologies: forcing sometimes radical rescoping of research efforts already halfway (or more) to completion. At the end of its fifth year, both the scope and funding of the program were at a minimum despite the program successfully meeting all of it's initial high priority objectives. This paper will describe the program, its requirements, technology portfolio, and technology maturation processes. Also discussed will be the major technology milestones achieved and the lessons learned from managing a $100M+ technology program.

Johnson, Les C.↗