Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operator 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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS2019

GOES I-M: A Retrospective Look at Image Navigation and Registration (INR), Jitter and Lessons Learned

The Geostationary Operational Environmental Satellite (GOES) I-M series of spacecraft was the second generation of United States meteorological observational platforms in geosynchronous orbit. They served as the principal Earth- viewing observational platforms for continuously monitoring dynamic weather events from the mid-1990s and into the 21st century. This paper will look back at the program framing key system attributes of the mission, which necessitated a multi-layered development approach to meet stringent meteorological instrument Line-of-Sight (LoS) pointing and pointing stability requirements. The overall approach involved understanding, correcting, and avoiding pointing errors across a broad frequency range including what would typically be called dynamic interaction and jitter. Background information will be provided covering the mission architecture and program drivers. The systems solution for man- aging and mitigating the deleterious influences of on-board disturbances in order to meet the challenging instrument LoS pointing and jitter requirements will be described, along with the ‘first of its kind’ Image Navigation and Registration system. A broad look back at the lessons learned that emerged from the GOES I- M experience will be presented, with the intent of capturing general and specific insights for developers of future missions having stringent payload instrument pointing requirements. These discussions will touch on such critical aspects as defining jitter and related pointing requirements, the importance of early system architectural decisions, understanding and reducing on-board disturbances, the balance of test and analysis, and the imperative for maximizing on-orbit operational flexibility in order to accommodate unexpected dynamic interactions.

Sudey, John↗
NASA NTRS2011

Science Operations Development for Field Analogs: Lessons Learned from the 2010 Desert RATS Test

Desert Research and Technology Studies (Desert RATS) is a multi-year series of hardware and operations tests carried out annually in the high desert of Arizona on the San Francisco Volcanic Field. Conducted since 1997, these activities are designed to exercise planetary surface hardware and operations in conditions where long-distance, multi-day roving is achievable. Such activities not only test vehicle subsystems through extended rough-terrain driving, they also stress communications and operations systems and allow testing of science operations approaches to advance human and robotic surface capabilities.

Eppler, D. B.↗
NASA NTRS2011

Transient Plume Model Testing Using LADEE Spacecraft Attitude Control System Operations

We have learned it is conceivable that the Neutral Mass Spectrometer on board the Lunarr Atmosphere Dust Environment Explorer (LADEE) could measure gases from surface-reflected Attitude Control System (ACS) thruster plume. At minimum altitude, the measurement would be maximized, and gravitational influence minimized ("short" time-of-flight (TOF) situation) Could use to verify aspects of thruster plume modeling Model the transient disturbance to NMS measurements due to ACS gases reflected from lunar surface Observe evolution of various model characteristics as measured by NMS Species magnitudes, TOF measurements, angular distribution, species separation effects

Woronowicz, Michael↗
NASA NTRS2005

Atmospheric/Space Environment Support Lessons Learned Regarding Aerospace Vehicle Design and Operations

In modern government and aerospace industry institutions the necessity of controlling current year costs often leads to high mobility in the technical workforce, "one-deep" technical capabilities, and minimal mentoring for young engineers. Thus, formal recording, use, and teaching of lessons learned are especially important in the maintenance and improvement of current knowledge and development of new technologies, regardless of the discipline area. Within the NASA Technical Standards Program Website http://standards.nasa.gov there is a menu item entitled "Lessons Learned/Best Practices". It contains links to a large number of engineering and technical disciplines related data sets that contain a wealth of lessons learned information based on past experiences. This paper has provided a small sample of lessons learned relative to the atmospheric and space environment. There are many more whose subsequent applications have improved our knowledge of the atmosphere and space environment, and the application of this knowledge to the engineering and operations for a variety of aerospace programs.

Vaughan, William W.↗
NASA NTRS2011

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.↗
NASA NTRSDate not supplied

NASA Delta Airlines Technical Interchange Meeting

The Digital Information Sub-project will hold a Technical Interchange Meeting (TIM) with Delta Airlines to discuss potential collaboration opportunities as well as discuss upcoming NASA-led demonstrations. This interchange meeting will solicit feedback from Delta for consideration of the sub-project in upcoming development and to encourage future participation and collaboration. Additionally, Delta will provide insight into airline operations to allow NASA to learn more about airline operations.

Digital Information Platform↗
NASA NTRS1992

SOCAP: Lessons learned in applying SIPE-2 to the military operations crisis action planning domain

This report describes work funded under the DARPA Planning and Scheduling Initiative that led to the development of SOCAP (System for Operations Crisis Action Planning). In particular, it describes lessons learned in applying SIPE-2, the underlying AI planning technology within SOCAP, to the domain of military operations deliberate and crisis action planning. SOCAP was demonstrated at the U.S. Central Command and at the Pentagon in early 1992. A more detailed report about the lessons learned is currently being prepared. This report was presented during one of the panel discussions on 'The Relevance of Scheduling to AI Planning Systems.'

Desimone, Roberto↗
NASA NTRS2010

Improving the Operations of the Earth Observing One Mission via Automated Mission Planning

We describe the modeling and reasoning about operations constraints in an automated mission planning system for an earth observing satellite - EO-1. We first discuss the large number of elements that can be naturally represented in an expressive planning and scheduling framework. We then describe a number of constraints that challenge the current state of the art in automated planning systems and discuss how we modeled these constraints as well as discuss tradeoffs in representation versus efficiency. Finally we describe the challenges in efficiently generating operations plans for this mission. These discussions involve lessons learned from an operations model that has been in use since Fall 2004 (called R4) as well as a newer more accurate operations model operational since June 2009 (called R5). We present analysis of the R5 software documenting a significant (greater than 50%) increase in the number of weekly observations scheduled by the EO-1 mission. We also show that the R5 mission planning system produces schedules within 15% of an upper bound on optimal schedules. This operational enhancement has created value of millions of dollars US over the projected remaining lifetime of the EO-1 mission.

Chien, Steve A.↗
NASA NTRSDate not supplied

Operation of the Urine Collection and Pretreatment System in the ISS US Segment Waste & Hygiene Compartment (WHC)

The US Segment Waste & Hygiene Compartment (WHC)provides the capability to collect crew urine for subsequent delivery to the Urine Processor Assembly (UPA). Urine collection in the WHC is accomplished with the urine collection and pretreatment system designed by RSC “Energia” and NIICHIMMASH and integrated into the WHC by Boeing and NASA. The WHC was installed in the US Laboratory Module in November 2008 and later transferred to the Node 3 in February 2010.As of February 1st 2021, the WHC has collected 25855 liters of pretreated urine. The system collects urine from astronauts, adds required pretreatment chemicals to maintain chemical and microbial control of the urine, and delivers the pretreated urine to the Urine Processor Assembly. This paper will summarize the twelve years of operation of the WHC on ISS, significant anomalies, and lessons learned from its operation.

D Layne Carter↗
NASA NTRS2018

Toward Justifiable Trust in Autonomous Systems Incorporating Human Knowledge in Autonomous Systems through Machine Learning

Trust in Autonomous Systems is largely about humans trusting the decisions made by autonomous systems. This trust can be increased through learning from domain experts. In particular, autonomous systems can learn offline from past mission operations before conducting any operations of its own. Additionally, autonomous systems can learn online by obtaining human feedback during operations. We will discuss several classes of machine learning methods and our application of them to autonomous systems. The first class of methods is anomaly detection, which uses operations data to identify examples of anomalous operations. The second class of methods is inverse reinforcement learning, also known as apprenticeship learning, that takes past operations data as input and yields a controller that is able to duplicate the operations described by the data. The third class is active learning, which identifies examples on which the model is most uncertain and requests domain expert feedback.

Oza, Nikunj C.↗
NASA NTRS2010

Selected Lessons Learned over the ISS Design, Development, Assembly, and Operations: Applicability to International Cooperation for Standardization

This slide presentation reviews some of the lessons learned in the sphere of international cooperation during the development, assembly and operation of the International Space Station. From the begining all Partners shared a common objective to build, operate and utilize a crewed laboratory in low orbit as an international partnership. The importance of standards is emphasized.

Hirsch, David B.↗
NASA NTRS2014

A Curious Year on Mars - Long-Term Thermal Trends for Mars Science Laboratory Rover's First Martian Year

By the time of this writing, Curiosity, the Mars Science Laboratory (MSL) Rover, has weathered four seasons in Gale Crater, just south of and approaching the foothills of the 5-km high Aeolis Mons, known as "Mount Sharp," at 4.59 deg south latitude. The mission design included a much broader latitude range of 30 deg north to 30 deg south constraining some of the Rover environmental requirements and operations. To date, Curiosity has relayed over 150 MB of thermal telemetry. Curiosity has relayed over 150 MB of thermal telemetry through four seasons. The trends and idiosyncrasies revealed through four seasons of telemetry from Mars are discussed. The better-characterized thermal environment allows for less conservatism in operational models and increases the amount of science data collection. Examples include: the elimination of overheating concerns for some cameras and the use of the previous sol's temperature telemetry along with the conservative soak temperature curve from the winter thermal model, to produce a custom heating prescription for the upcoming weeks thus increasing operation time and reducing heating times. This paper discusses the lessons learned for Rover operation as well as general idiosyncrasies discovered about the local environment-such as the effect of orientation on subsystem temperature variation, a regular morning and afternoon wind, ground and air microclimates with distinct temperature differences from other terrain, and how the Rover affects the local environment. This paper further documents and explains some of the interesting highs and lows of the temperature telemetry data as well as offers explanations for sudden temperature changes on board the Rover.

HRS↗
NASA NTRS2012

EOS MLS Lessons Learned: Design Ideas for Safer and Lower Cost Operations

The Earth Observing System (EOS) Microwave Limb Sounder (MLS) is a complex instrument with a front end computer and 32 subsystem computers. MLS is one of four instruments on NASA's EOS Aura spacecraft With almost 8 years in orbit, MLS has a few lessons learned which can be applied during the design phase of future instruments to effect better longevity, more robust operations and a significant cost benefit during operations phase.

flight software design↗
NASA NTRS2001

Lessons Learned and Process Improvement for Payload Operations at the Launch Site

For every space mission, there are challenges with the launch site/field operations process that are addressed too late in the development cycle. This potentially causes schedule delays, cost overruns, and adds risk to the mission success. This paper will discuss how a single interface, representing the payload at the launch site in all phases of development, will mitigate risk, and minimize or even alleviate potential problems later on. Experience has shown that a single interface between the project and the launch site allows for issues to be worked in a timely manner and bridges the gap between two diverse cultures.

Catena, John↗