Search NASA⌕ Search

SEARCH · Search NASA

Results for “HITL”

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2019

Cyber Physical Security (CPS) Extension to Air Traffic Management (ATM) Testbed

The Air Traffic Management (ATM) Testbed is being developed at NASA to enable benefit, impact, safety and cost assessments for accelerating the deployment of Concept and Technologies (C&T) in the National Airspace System (NAS). Today, C&T introduction into the NAS takes decades. The primary reason for this is an inability to assess the operational impact of the interaction between the proposed C&T and operationally deployed systems (Realistic Technologies) in terms of NAS-wide safety, traffic flow efficiency, roles and workload of controllers and traffic managers, and impact on airline fleet operations. Transition of C&T to operations requires mathematical modeling and simulation, Human-in-the-Loop (HITL) testing and shadow-mode evaluation driven by operational data. Whereas interaction with the operational system during testing and stages of deployment is not permissible due to safety concerns, it is certainly possible to create a simulation environment that closely mimics the NAS using the same operational systems/hardware for enabling such assessments. This presentation focuses on a proposed Cyber Physical Security extension to the ATM Testbed for creating a modeling and simulation architecture to study how well the Air Traffic Management system will perform and analyze effectiveness of mitigating security measures against particular cyber-attack scenarios.

Datta, Koushik↗
NASA NTRS2019

A Detect and Avoid System in the Context of Multiple-Unmanned Aircraft Systems Operations

NASA's Unmanned Aircraft Systems Integration into the National Airspace System (UAS in the NAS) project examines the technical barriers associated with the operation of UAS in civil airspace. For UAS, the removal of the pilot from onboard the aircraft has eliminated the ability of the ground-based pilot in command (PIC) to use out-the-window visual information to make judgements about a potential threat of a loss of well clear with another aircraft. NASA's Phase 1 research supported the development of a Detect and Avoid (DAA) system that supports the ground-based pilot's ability to detect potential traffic conflicts and determine a resolution maneuver, but existing display/alerting requirements did not account for multiple UAS control (1:N). Demands for increased scalability of UAS in the NAS operations are expected to create a need for simultaneous control of UAs, and thus, a new DAA HMI design will likely be necessary. Previous research, however, has found performance degradations as the number of vehicles under operator control has increased. The purpose of the current human-in-the-loop (HITL) simulation was to examine the viability of 1:N operations with the Phase 1 DAA alerting and guidance. Sixteen UAS pilots flew three scenarios with varying number of UAs under their control (1:1, 1:3, 1:5). In addition to their supervisory and sensor mission responsibilities, pilots were to utilize the DAA system to remain DAA well clear (DWC) during scripted conflicts of mixed severity. Measured response times, separation performance, mission task data, and subjective feedback were collected to assess how the multi-UAS control configuration impacted pilots' ability to maintain DAA well clear and perform the mission tasks. Overall, the DAA system proved surprisingly adaptive to multi-UAS control for preventing losses of DAA well clear (LoDWC). The findings suggest that, while multi-UAS operators are able to maintain safe separation (DWC) from other traffic, their ability to efficiently perform missions drastically decreases with their number of controlled vehicles. Pilot feedback indicated that, for this context, the use of automation support tools for completing and managing mission tasks would be appropriate and desired, especially for ensuring efficient use of assets. Finally, human-machine interface (HMI) design considerations for multi-UAS operations are discussed.

Monk, Kevin J.↗
NASA NTRS2015

Assessing Resilience of Scheduled Performance-Based Navigation Arrival Operations

This paper assesses the resilience of scheduled Performance-Based Navigation (PBN) arrival operations. Resilience is defined as an ability to return to nominal operations following a schedule perturbation. Results from a Human-in-the- Loop (HITL) experiment that included off-nominal events to perturb the schedule are described. The schedule comes from a precision trajectory-based arrival manager. The experiment collected data regarding the response to perturbed schedules in three conditions, where: 1) a disturbance rejection algorithm made schedule adjustments automatically, 2) a Traffic Management Coordinator (TMC) participant made schedule adjustments manually, or 3) no schedule adjustments were made. Analyses showed that the simulation’s scheduled PBN operations have inherent resilience, recovering from more than half of the perturbed schedules even with no schedule adjustments. Resilience to the same off-nominal events improved with schedule adjustments; an increased proportion of perturbed schedules recovered within the length of operation run, and the average duration of the schedule’s perturbed state decreased. Compared to the manual schedule adjustments condition, a greater number of schedule adjustments occurred for the same off-nominal events in the automated condition. However, perturbed schedules were recovered more frequently and perturbations were less severe in the automated condition. Subjective and objective workload in the manual and the automated schedule adjustment conditions were similar to the no schedule adjustment condition.

Resilience↗
NASA NTRS2015

Human Factors Assessment of Disturbances to Scheduled Performance-Based Navigation Arrival Operations

The introduction of Performance-Based Navigation (PBN) specifications to air traffic management has resulted in many benefits during nominal operations, including shorter flight paths, reduced fuel costs, and improved terminal area arrival rates. However, these benefits become less noticeable during off-nominal operations where aircraft are routinely interrupted from staying on PBN procedures due to disturbances such as missed approaches. This human-in-the-loop (HITL) study used multiple types of disturbance events to perturb the arrival schedule. Perturbed schedules were managed with different types of schedule adjustments, including a condition with no adjustments. The study collected data on a host of dependent variables, including human factors measures on controller workload and system performance measures such as schedule nonconformance (nc). Initial analyses showed strong correlations between aggregated controller workload and aggregated nc, as well as benefits of both automatic and manual schedule adjustments for increasing system performance, such as reduced PBN procedure interruptions. The goal of this paper is to further test these initial findings. The results indicated that an increase in schedule nonconformance correlated with an increase in controller workload at specific time intervals, and automated schedule adjustments consistently reduced controller workload associated with nonconformance.

Human factors↗
NASA NTRS2019

Alternatives for Scheduling Departures for Efficient Surface Metering in ATD-2: Exploration in a Human-in-the-Loop Simulation

Human-in-the-Loop (HITL) simulation was conducted to explore the impacts of various surface metering goals on operations and Ramp Controllers at Charlotte Douglas International Airport (CLT). Three conditions were compared: Baseline, with no surface metering, instructions to meet advisory times at the gate only, and instructions to meet advisory times at the gate as well as the times at the scheduled taxiway spot, where aircraft are delivered to Air Traffic Control (ATC). Results showed increased compliance for taxiway spot times when compliance was first met for gate advisories. Instructing Ramp Controllers to meet advisory times at the gate improves spot time compliance and therefore surface scheduling predictability at CLT. Results also demonstrated there was increased compliance overall with gate and spot times in the second condition. This was likely due to higher Ramp Controller workload in the third condition.

Airport surface scheduling↗
NASA NTRS2019

Alternatives for Scheduling Departures for Efficient Surface Metering in ATD-2: Exploration in a Human-in-the-Loop Simulation

A Human-in-the-Loop (HITL) simulation was conducted to explore whether Ramp Controllers at Charlotte Douglas International Airport (CLT) could both release departing aircraft at an advised time at the gate and also meet an advised time at the spot, where Air Traffic Control (ATC) takes control. Three conditions were compared: (1) Baseline, with no scheduling advisories, (2) instructions to meet advisory times at the gate only, and (3) instructions to meet advisory times at both the gate and the spot. Surprisingly, results showed increased compliance with advisories at the spot in the second condition. This was likely due to increased ramp congestion in the third condition as well as higher Ramp Controller workload and lower situation awareness. Instructing Ramp Controllers to meet scheduling times at the spots, in addition to the gates, is therefore not likely to improve surface scheduling predictability at CLT and may indeed worsen it.

airport surface scheduling↗
NASA NTRS2019

Investigation of Communications Involved in Near-Term UAM Operations

The present research explored whether the implementation of a letter of agreement (LOA), or pre-established written terms of engagement, would reduce controller communication associated workload in a HITL study simulating a near-term UAM infrastructure with varying traffic levels. Current helicopter routes, including modified versions, and communication procedures were outlined in the LOA. Time spent communicating was reduced under both conditions featuring a LOA, for current and modified routes, compared to present day procedures without a LOA. Results suggest that utilizing current-day helicopter routes and implementing a LOA may prove beneficial for near-term low-density and low-tempo UAM operations.

Keeler, Jillian N.↗
NASA NTRS2019

Challenges Using Linux as a Real-Time Operating System

Human-in-the-loop (HITL) simulation groups at NASA and the Air Force Research Lab have been using Linux as a real-time operating system (RTOS) for over a decade. More recently, SpaceX has revealed that it is using Linux as an RTOS for its Falcon launch vehicles and Dragon capsules. As Linux makes its way from ground facilities to flight critical systems, it is necessary to recognize that the real-time capabilities in Linux are cobbled onto a kernel architecture designed for general purpose computing. The Linux kernel contain numerous design decisions that favor throughput over determinism and latency. These decisions often require workarounds in the application or customization of the kernel to restore a high probability that Linux will achieve deadlines.

Madden, Michael M.↗
NASA NTRS2019

Challenges Using the Linux Network Stack for Real-Time Communication

Starting in the early 2000s, human-in-the-loop (HITL) simulation groups at NASA and the Air Force Research Lab began using the Linux network stack for some real-time communication. More recently, SpaceX has adopted Ethernet as the primary bus technology for its Falcon launch vehicles and Dragon capsules. As the Linux network stack makes its way from ground facilities to flight critical systems, it is necessary to recognize that the network stack is optimized for communication over the open Internet, which cannot provide latency guarantees. The Internet protocols and their implementation in the Linux network stack contain numerous design decisions that favor throughput over determinism and latency. These decisions often require workarounds in the application or customization of the stack to maintain a high probability of low latency on closed networks, especially if the network must be fault tolerant to single event upsets.

Madden, Michael M.↗
NASA NTRSDate not supplied

Demonstrating Early-Adopter Benefits of Submitting Multiple Trajectory Options for Airlines

A workshop at NASA Ames Research Center was held with airline industry stakeholders to demonstrate the impact of using Trajectory Options Sets (TOSs) during a Collaborative Trajectory Options Program (CTOP) for severe weather operations. The demonstration was conducted using apart-task Human-in-the-Loop (HITL) simulation of the Integrated Demand Management (IDM) concept, which is an air traffic management method that uses CTOP to deliver preconditioned traffic to the Time-Based Flow Management (TBFM) region. The demonstration addressed the following research objectives: first, determine who receives a greater benefit, TOS-participating or TOS-excluded airlines? Second, determine which method of trajectory selection yields a better solution, human/manual selection or automation? Finally, obtain feedback from stakeholders on their impression of the concept and recommendations for future work. The results showed that TOS-participating airlines received greater benefit in terms of total ground delay, ground delay savings, number of reroute options, and additional flight time, compared to TOS-excluded airlines. However, this result was dependent on the situational context, such as the number and location of flights. We found that all airlines benefitted when just a subset of airlines submitted TOS, but the greatest benefit went to the TOS-participating airlines. These benefits to the TOS-participating airlines were diminished as the number of TOS-participants in the system increased. Therefore, there was an “early-adopter” effect that suggested airlines could benefit by becoming the first to equip TOS without causing unfair disadvantages to those who do not equip TOS. In addition, we found that manual selection of trajectory options performed similarly to CTOP, but the CTOP solution was more efficient in terms of number of reroutes, additional flight time, and average ground delay for rerouted flights. Feedback from the stakeholders was solicited, and their overall impressions of the demonstrations were positive. They remarked that CTOP could do a better job than current day solutions, and they thought airlines could benefit from continuing to develop TOS capabilities.

Integrated Demand Management↗
NASA NTRS2020

An Evaluation of UAS Pilot Workload and Acceptability Ratings with Four Simulated Radar Declaration Ranges

Currently, minimum operating standards (MOPS) are being developed for a broader range of UAS types, including smaller UAS that will feature onboard sensors that are low in size, weight, and power (Low SWaP). These sensors will have limited declaration ranges compared to ones typically found on medium-to-large UAS used to detect non-cooperative aircraft. A human-in-the-loop (HITL) study was conducted examining four possible radar declaration ranges (i.e., 1.5 nm, 2 nm, 2.5 nm, and 3 nm) for a potential low SWaP sensor with a DAA system. Participants had lower workload, particularly workload associated with temporal demand and effort. Furthermore, participants reported better ability to remain DAA well clear within the larger declaration range conditions, such as the 2.5 nm and 3 nm.

UAS↗
NASA NTRSDate not supplied

A Human-in-the-Loop Evaluation of ACAS Xu

As part of the Phase 2 UAS DAA MOPS, a Class 3 DAA system has been under development with the potential to resolve many of the limitations of Class 1 and 2 systems. A Class 3 system would combine the DAA and CA functions into a single, unified system, and would also extend the CA capabilities relative to TCAS II. Class 3 is enabled by the Airborne Collision Avoidance System (ACAS) XU, a next generation CA system developed specifically for UAS operations. Unlike Class 2 systems, ACAS XU provides CA protection against both cooperative and non-cooperative traffic. Class 3 systems also expand the CA logic to allow horizontal RAs in addition to vertical RAs. The purpose of the current study was to evaluate ACAS XU in a real-time, HITL simulation. The latest version of ACAS XU was implemented and pilots were tasked with responding to scripted traffic conflicts over the course of four experimental trials. Variables included the location of the ACAS XU guidance information (standalone vs. integrated) and traffic conflict type (DAA or CA threat). Sixteen active UAS pilots participated in the study, with ATC and ‘pseudo’ pilots acting as airspace confederates. Results showed that pilots were able to maintain DWC with ACAS XU at a rate comparable to previous research (~5%). Compliance rates to initial RAs were high (~90%) but dropped significantly when the target heading value issued during horizontal RAs were updated over the course of an encounter (30-70%). The implications of these findings on the display, alerting, and guidance requirements for Class 3 systems will be discussed.

unmanned aircraft systems↗
NASA NTRSDate not supplied

A Human-in-the-Loop Evaluation of ACAS Xu

As part of the Phase 2 UAS DAA MOPS, a Class 3 DAA system has been under development with the potential to resolve many of the limitations of Class 1 and 2 systems. A Class 3 system would combine the DAA and CA functions into a single, unified system, and would also extend the CA capabilities relative to TCAS II. Class 3 is enabled by the Airborne Collision Avoidance System (ACAS) XU, a next generation CA system developed specifically for UAS operations. Unlike Class 2 systems, ACAS XU provides CA protection against both cooperative and non-cooperative traffic. Class 3 systems also expand the CA logic to allow horizontal RAs in addition to vertical RAs. The purpose of the current study was to evaluate ACAS XU in a real-time, HITL simulation. The latest version of ACAS XU was implemented and pilots were tasked with responding to scripted traffic conflicts over the course of four experimental trials. Variables included the location of the ACAS XU guidance information (standalone vs. integrated) and traffic conflict type (DAA or CA threat). Sixteen active UAS pilots participated in the study, with ATC and ‘pseudo’ pilots acting as airspace confederates. Results showed that pilots were able to maintain DWC with ACAS XU at a rate comparable to previous research (~5%). Compliance rates to initial RAs were high (~90%) but dropped significantly when the target heading value issued during horizontal RAs were updated over the course of an encounter (30-70%). The implications of these findings on the display, alerting, and guidance requirements for Class 3 systems will be discussed.

unmanned aircraft systems↗
NASA NTRS2020

A Human-in-theLoop Evaluation of ACAS Xu

As part of the Phase 2 UAS DAA MOPS, a Class 3 DAA system has been under development with the potential to resolve many of the limitations of Class 1 and 2 systems. A Class 3 system would combine the DAA and CA functions into a single, unified system, and would also extend the CA capabilities relative to TCAS II. Class 3 is enabled by the Airborne Collision Avoidance System (ACAS) XU, a next generation CA system developed specifically for UAS operations. Unlike Class 2 systems, ACAS XU provides CA protection against both cooperative and non-cooperative traffic. Class 3 systems also expand the CA logic to allow horizontal RAs in addition to vertical RAs. The purpose of the current study was to evaluate ACAS XU in a real-time, HITL simulation. The latest version of ACAS XU was implemented and pilots were tasked with responding to scripted traffic conflicts over the course of four experimental trials. Variables included the location of the ACAS XU guidance information (standalone vs. integrated) and traffic conflict type (DAA or CA threat). Sixteen active UAS pilots participated in the study, with ATC and ‘pseudo’ pilots acting as airspace confederates. Results showed that pilots were able to maintain DWC with ACAS XU at a rate comparable to previous research (~5%). Compliance rates to initial RAs were high (~90%) but dropped significantly when the target heading value issued during horizontal RAs were updated over the course of an encounter (30-70%). The implications of these findings on the display, alerting, and guidance requirements for Class 3 systems will be discussed.

unmanned aircraft systems↗
NASA NTRSDate not supplied

When the Eyes Don't Have It: Autonomous Control of Deep Space Vehicles for Human Spaceflight

NASA has been charged with expanding human presence into the solar system. The next phase of exploration will focus on learning how to develop and sustain habitats on the moon for eventual missions to Mars. The Gateway Lunar Orbiting Platform (G-LOP) is a modular spacecraft being built for cis-lunar orbit and offers a true deep space environment for gaining experience for human missions to Mars. The mission concept for Gateway involves long uncrewed periods between missions; therefore, Gateway requires increased self-reliance to separate the spacecraft from Earth-bound control and oversight. This complicates the human-in-the-loop (HITL) concept and requires major adjustments to the traditional automation human-computer interaction paradigm. This paper discusses the design, development, and verification of complex human-computer interactions with the autonomous systems managers which will control the Gateway spacecraft.

Julia M. Badger↗
NASA NTRSDate not supplied

An Evaluation of UAS Pilot Workload and Acceptability Ratings with Four Simulated Radar Declaration Ranges

Currently, minimum operational performance standards (MOPS) are being developed for a broader range of unmanned aircraft system (UAS) platforms, including smaller UAS that will feature onboard sensors that are low in size, weight, and power, otherwise known as low SWaP. The low SWaP sensors used to detect non-cooperative traffic will have limited declaration ranges compared to those designed for medium-to-large UAS. A human-in-the-loop (HITL) study was conducted examining four possible radar declaration ranges (i.e., 1.5 NM, 2 NM, 2.5 NM, and 3 NM) for a potential low SWaP sensor with a detect and avoid (DAA) system encountering various non-cooperative encounters in Oakland Center airspace. Participants had lower workload, particularly workload associated with temporal demand and effort, in scenarios that featured larger declaration ranges. Furthermore, participants reported better ability to remain DAA well clear within the larger declaration range conditions, specifically with the 2.5 NM and 3 NM conditions.

UAS↗
NASA NTRS2020

An Evaluation of UAS Pilot Workload and Acceptability Ratings with Four Simulated Radar Declaration Ranges

Currently, minimum operational performance standards (MOPS) are being developed for a broader range of unmanned aircraft system (UAS) platforms, including smaller UAS that will feature onboard sensors that are low in size, weight, and power, otherwise known as low SWaP. The low SWaP sensors used to detect non-cooperative traffic will have limited declaration ranges compared to those designed for medium-to-large UAS. A human-in-the-loop (HITL) study was conducted examining four possible radar declaration ranges (i.e., 1.5 NM, 2 NM, 2.5 NM, and 3 NM) for a potential low SWaP sensor with a detect and avoid (DAA) system encountering various non-cooperative encounters in Oakland Center airspace. Participants had lower workload, particularly workload associated with temporal demand and effort, in scenarios that featured larger declaration ranges. Furthermore, participants reported better ability to remain DAA well clear within the larger declaration range conditions, specifically with the 2.5 NM and 3 NM conditions.

UAS↗
NASA NTRS2021

UAS Integration in the NAS Flight Test 6: Full Mission Results

Recent standards development efforts for the integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS) such as those in RTCA Inc. Special Committee 228 (SC-228) have focused on relatively large UAS transitioning to and from Class A airspace. In an effort to expand the range of vehicle classes that can access the NAS, the NASA UAS Integration in the NAS project has investigated Low Size, Weight, and Power (Low SWaP) technologies that would allow smaller UAS to detect-and-avoid (DAA) traffic. Through batch and human in the loop (HITL) simulation studies, the UAS Integration in the NAS DAA subproject have identified candidate performance standards that would contribute to enabling extended Low SWaP, UAS operations under 10,000 feet. These candidate performance standards include minimum field of regard (FOR) values for Low SWaP air surveillance sensors as well as a DAA well-clear (DWC) definition which can be applied to non-cooperative traffic to reduce the required maneuver initiation range. To test the assumptions of the project’s simulation studies and validate the candidate performance standards, a live flight research event was executed at NASA Armstrong Flight Research Center. The UAS Integration in the NAS Project Flight Test 6 Full Mission sought to characterize UAS pilot responses to traffic conflicts using a representative Low SWAP DAA system in an operational NAS environment. To achieve this, live, virtual and constructive distributed environment (LVC-DE) elements were combined to simulate a sector of Oakland center airspace and induce encounters with a live, manned aircraft. A Navmar Applied Sciences Tigershark XP was used as the UAS ownship and was integrated into the test architecture to enable it to be controlled from a Vigilant Spirit Control Station (VSCS) research ground control station. Qualified UAS pilots were recruited to act as subject pilots under test (SPUT) to control the Tigershark XP in a simulated mission while coordinating with a participating air traffic controller in simulated airspace. The intruder speed, intruder equipage and encounter geometry were varied between six scripted encounters per SPUT. Various metrics were collected including pilot reaction time from the onset of DAA alert, ATC coordination rate, probability and severity of losses of DAA well clear, and subjective ratings of system acceptability. The implications of these results on the development of standards for Low SWAP DAA systems will be discussed.

UAV↗