Search NASA⌕ Search

SEARCH · Search NASA

Results for “Copilot”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2020

Copilot 3

Ultra-critical systems require high-level assurance, which cannot always be guaranteed in compile time. The use of runtime verification (RV) enables monitoring these systems in runtime, to detect property violations early and limit their potential consequences. The introduction of monitors in ultra-critical systems poses a challenge, as failures and delays in the RV subsystem could affect other subsystems and threaten the mission as a whole. This paper presents Copilot 3, a runtime verification framework for real-time embedded systems. Copilot monitors are written in a compositional, stream-based language with support for a variety of Temporal Logics (TL), which results in robust, high-level specifications that are easier to understand than their traditional counterparts. The framework translates monitor specifications into C code with static memory requirements, which can be compiled to run on embedded hardware. This paper presents version 3 of the Copilot language, demonstrates its suitability with a number of examples, and discusses its use in larger applications. Additionally, it describes the framework?s architecture, its implementation as a Domain Specific Language (DSL) embedded in Haskell, and the progress of the project over the years.

Ivan Perez↗
NASA NTRS2022

Integrating FRET with Copilot: Automated Translation of Natural Language Requirements to Runtime Monitors

Runtime verification (RV) enables monitoring systems at runtime, to detect property violations early and limit their potential consequences. To provide the level of assurance required for ultra-critical systems, monitor specifications must faithfully reflect the original mission requirements, which are often written in ambiguous natural language. This paper presents an end-to-end framework to capture requirements in structured natural language and generate monitors that capture their semantics faithfully. We leverage NASA’s Formal Requirement Elicitation Tool (FRET), and the RV system Copilot. We extend FRET with mechanisms to capture additional information needed to generate monitors, and introduce OGMA, a new tool to bridge the gap between FRET and Copilot. With this framework, users can write requirements in an intuitive format and obtain real-time C monitors suitable for use in embedded systems. Our tool chain is available as open source.

FRET↗
NASA NTRS2026

Hydrology Copilot: A Cloud-Native Ai System for Hydrological Data Analysis

The emergence of AI-driven Earth observation systems promises to broaden access to petabyte-scale geospatial data beyond domain specialists. However, translating this vision into operational scientific infrastructure requires addressing fundamental challenges in data virtualization, code transparency, and domain-specific reasoning. We present Hydrology Copilot, a cloud-native AI framework for natural-language-driven analysis of Earth observation data. To demonstrate operational capabilities at scale, we implement the system using NASA's North American Land Data Assimilation System version 3 (NLDAS-3), which provides surface meteorological forcing and land-surface model output across North and Central America at 1-km resolution, from which drought diagnostics are derived. The system integrates five core contributions: (1) scalable data virtualization using Kerchunk-based cloud optimized access, achieving a 1.5 to 4.6 times improvement in I/O latency across benchmark queries spanning regional single-day extractions (4.6 times speedup) to continental monthly aggregations (1.5 times speedup); (2) transparent code generation through Microsoft Azure AI Foundry agents that expose executable Python workflows for scientific verification; (3) persistent conversational memory enabling multi-turn analytical discourse across sessions; (4) intelligent query validation that enforces dataset boundaries and resolves ambiguous requests before execution; and (5) a multi-agent architecture coordinating query parsing, code generation, and visualization. We evaluate the system through drought-monitoring workflows, demonstrating reliable code generation, accurate results validated against reference computations and the operational U.S. Drought Monitor, and efficient operation across increasingly complex tasks. By bridging natural-language interfaces with rigorous hydrological analysis, Hydrology Copilot advances beyond proof-of-concept demonstrations to provide a deployable framework for operational Earth science applications.

Data virtualization↗
NASA NTRS1983

The effectiveness of an oculometer training tape on pilot and copilot trainees in a commercial flight training program

A study was designed to evaluate the effectiveness of a video tape detailing the various aspects of instrument scanning by experienced pilots on performance by pilots and copilots undergoing flight training in a Boeing 737 flight simulator. The performance ratings by instructor pilots (IP's) and self-reported instrument scan behavior by trainees were compared with those of a control group. The results indicated that the training tape had little or no effect on performance by trainees in the experimental group. Feedback from the IP's and trainees suggested that a feedback strategy providing each trainee's individual instrument scan behavior might be more beneficial in flight training than the general instructional strategy of the oculometer training tape. Flight training personnel and trainees' reports of performance decrements on or around the third day of flight simulator training were investigated. The IP's performance ratings of 27 pilot and copilot trainees failed to reveal a systematic performance decrement; however, feedback from the trainees revealed that their own attribution of performance decrements was associated with the order in which their training occurred within a session. Further research was suggested.

Jones, D. H.↗
NASA NTRS2012

Copilot: Monitoring Embedded Systems

Runtime verification (RV) is a natural fit for ultra-critical systems, where correctness is imperative. In ultra-critical systems, even if the software is fault-free, because of the inherent unreliability of commodity hardware and the adversity of operational environments, processing units (and their hosted software) are replicated, and fault-tolerant algorithms are used to compare the outputs. We investigate both software monitoring in distributed fault-tolerant systems, as well as implementing fault-tolerance mechanisms using RV techniques. We describe the Copilot language and compiler, specifically designed for generating monitors for distributed, hard real-time systems. We also describe two case-studies in which we generated Copilot monitors in avionics systems.

Pike, Lee↗
NASA NTRS2024

Runtime Verification of Hard Realtime Systems With Copilot: A Tutorial

This presentation is a tutorial on RV using Copilot, a runtime verification framework for real-time embedded systems. Copilot monitors are written in a compositional, stream-based language with support for a variety of Temporal Logics (TL), which results in robust, high-level specifications that are easier to understand than their traditional counterparts. The framework translates monitor specifications into C code with static memory requirements, which can be compiled to run on embedded hardware.

runtime monitoring↗
NASA NTRS2021

Ground-based Automated Scheduling for Operations of the Mars 2020 Rover Mission

The National Aeronautics and Space Administration’s (NASA) Mars 2020 Rover, named Perseverance, landed on the surface of Mars in Jezero Crater on February 18, 2021. Since the landing, the rover’s activities have been planned with the aid of a ground-based automated scheduling system called Copilot. Automated scheduling is very rare for planetary rover missions. Historically humans have created a schedule manually and ensured that the schedule satisfied all constraints. Higher levels of automation in the system allows science planners to produce schedules for the rover more quickly. In addition to scheduling user-provided activities, Copilot generates and schedules two types of support activities: sleep activities and heating activities. Some activities require the CPU to be on as they execute, so Copilot schedules wakeups and shutdowns of the CPU at the appropriate times. Some activities require areas of the rover to be heated before they can execute, and that heating must be maintained throughout the duration of the activity. Copilot schedules the preheat and maintenance heating activities for the user-provided activities that require them. To facilitate Copilot usage, the Crosscheck tool shows the science planners how Copilot constructed a schedule. For activities that fail to be scheduled, Crosscheck gives information on the constraints that the activity would have violated. This gives the users insight into how to change the input activities and constraints in order to achieve a schedule that satisfies their goals.

Towey, Shannon↗
NASA NTRS1987

Inflight application of three pilot workload measurement techniques

Three inflight techniques for workload measurement were tested in nine pilots flying the NASA Kuiper Airborne Observatory: subjective ratings, heart rate, and communication performance. The activities that contributed to the crew-member workload varied; the commander was responsible for aircraft control and navigation whereas the copilot handled communications. The three workload measures were found to provide different information. Pilot ratings of workload, effort, and stress were sensitive to variations in flight-related task demands across flight segments but did not reflect specific differences in the type of demands imposed on the commander and the copilot. The heart rate was sensitive to the differential impact of duties, being higher for the commander than for the copilot. The rate of communications per minute of flight proved to be the most sensitive indicator. It was related to workload, stress, effort rating, and average heart rate across flight segments.

Hart, Sandra G.↗
NASA NTRS1983

The effectiveness of incorporating a real-time oculometer system in a commercial flight training program

The effectiveness of incroporating a real-time oculometer system into a Boeing 737 commercial flight training program was studied. The study combined a specialized oculometer system with sophisticated video equipment that would allow instructor pilots (IPs) to monitor pilot and copilot trainees' instrument scan behavior in real-time, and provide each trainee with video tapes of his/her instrument scanning behavior for each training session. The IPs' performance ratings and trainees' self-ratings were compared to the performance ratings by IPs and trainees in a control group. The results indicate no difference in IP ratings or trainees' self-ratings for the control and experimental groups. The results indicated that the major beneficial role of a real-time oculometer system for pilots and copilots having a significant amount of flight experience would be for problem solving or refinement of instrument scanning behavior rather than a general instructional scheme. It is suggested that this line of research be continued with the incorporation of objective data (e.g., state of the aircraft data), measures of cost effectiveness and with trainees having less flight experience.

Jones, D. H.↗
NASA NTRSDate not supplied

From Requirements to Autonomous Flight: An Overview of the Monitoring ICAROUS Project

The Independent Configurable Architecture for Reliable Operations of Unmanned Systems(ICAROUS) is a software architecture incorporating a set of algorithms to enable autonomous operations of unmanned aircraft applications. This paper provides an overview of Monitoring ICAROUS, a project whose objective is to provide a formal approach to generating runtime monitors for autonomous systems from requirements written in a structured natural language. This approach integrates FRET, a formal requirement elicitation and authoring tool, and Copilot, a runtime verification framework. FRET is used to specify formal requirements in structured natural language. These requirements are translated into temporal logic formulae. Copilot is then used to generate executable runtime monitors from these temporal logic specifications. The generated monitors are directly integrated into ICAROUS to perform runtime verification during flight.

Formal Methods↗
NASA NTRSDate not supplied

Monitoring ICAROUS: From Requirements to Autonomous Flight

The Independent Configurable Architecture for Reliable Operations of Unmanned Systems (ICAROUS) is a software architecture incorporating a set of algorithms to enable autonomous operations of unmanned aircraft applications. This paper provides an overview of Monitoring ICAROUS, a project whose objective is to provide a formal approach to generating runtime monitors for autonomous systems from requirements written in a structured natural language. This approach integrates FRET, a formal requirement elicitation and authoring tool, and Copilot, a runtime verification framework. FRET is used to specify formal requirements in structured natural language. These requirements are translated into temporal logic formulae. Copilot is then used to generate executable runtime monitors from these temporal logic specifications. The generated monitors are directly integrated into ICAROUS to perform runtime verification during flight.

Formal Methods↗
NASA NTRS2023

Towards Streamlining Auditing for Compliance With Requirements in Open-Source Software at NASA

Context: NASA requires all software to meet several requirements (NPR 7150.2) depending on software criticality. The instantiation of these requirements may vary per project; however, once decided upon, projects must undergo audits to evaluate compliance with these requirements. Aim: We propose that audit effort can be reduced when requirements are realized by leveraging commonly used open-source infrastructure for version control, issue tracking and continuous integration, and the generated records are analyzed using a repository mining software tool to quantify process compliance. Method: We perform a case study in the NASA-funded Copilot project, utilizing Kaiaulu, a repository mining software tool. We define four software compliance metrics based on the Copilot’s requirements, and analyze their impact on source code quality. Results: Our work demonstrates how it is possible to leverage existing open source tools and platforms to facilitate software certification and qualification, and to streamline the auditing process required even when stringent requirements must be enforced. Conclusion: Together, both project and tool can be utilized to visualize project compliance, and metrics can be defined to more easily identify process irregularities to minimize auditing efforts. Project Repository: github.com/Copilot-Language/copilot Tool Repository: github.com/sailuh/kaiaulu

code-quality↗
NASA NTRSDate not supplied

Runtime Verification with Ogma

Ultra-critical systems require high-level assurance, which cannot always be guaranteed in compile time. The use of runtime verification (RV) enable monitoring these systems in runtime, to detect property violations early and limit their potential consequences. However, the introduction of monitors in ultra-critical systems poses a challenge, as failures and delays in the RV subsystem could affect other subsystems and threaten the mission as a whole. In this talk we discuss two systems: NASA's Ogma, a tool to transform high-level specifications into monitoring code, and Copilot, a runtime verification framework for real-time embedded systems. The toolchain can be used to translate structured natural language requirements into C code with static memory requirements, which can be compiled to run on embedded hardware.

Ogma↗
NASA NTRSDate not supplied

Runtime Verification with Ogma

Ultra-critical systems require high-level assurance, which cannot always be guaranteed in compile time. The use of runtime verification (RV) enable monitoring these systems in runtime, to detect property violations early and limit their potential consequences. However, the introduction of monitors in ultra-critical systems poses a challenge, as failures and delays in the RV subsystem could affect other subsystems and threaten the mission as a whole. In this talk we discuss two systems: NASA's Ogma, a tool to transform high-level specifications into monitoring code, and Copilot, a runtime verification framework for real-time embedded systems. The toolchain can be used to translate structured natural language requirements into C code with static memory requirements, which can be compiled to run on embedded hardware.

Ogma↗
NASA NTRS1971

Virtual-image display system for flight simulators

Dual TV monitor and collimated lens system in windscreens of standard aircraft cockpit simulator permits both pilot and copilot to simultaneously view three dimensional presentation. Proper design of complete system permits depth and viewpoint of visual displays to be accurately presented.

Chase, W. D.↗
NASA NTRS1974

ASSESS program: Shuttle Spacelab simulation using a Lear jet aircraft (mission no. 2)

The second shuttle Spacelab simulation mission of the ASSESS program was conducted at Ames Research Center by the Airborne Science Office (ASO) using a Lear jet aircraft based at a site remote from normal flight operations. Two experimenters and the copilot were confined to quarters on the site during the mission, departing only to do in-flight research in infrared astronomy. A total of seven flights were made in a period of 4 days. Results show that experimenters with relatively little flight experience can plan and carry out a successful research effort under isolated and physically rigorous conditions, much as would more experienced scientists. Perhaps the margin of success is not as great, but the primary goal of sustained acquisition of significant data over a 5-day period can be achieved.

Reller, J. O., Jr.↗