Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “RTC”

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 NTRS2017

Ramp Traffic Console (RTC) Ramp Manager Traffic Console (RMTC) Observer Mode User Manual

This document serves as a user manual for the Observer Mode Ramp Traffic Console (RTC) in Charlotte Douglas International Airport Ramp Control Tower. It describes the elements of the full RTC interface and provides explanations for how to interact with the RTC while managing ramp traffic using one of the four RTC sector displays. The RTC provides digitally updated data for all flights including Earliest Off Block Times (EOBT) and Traffic Management Initiatives. Use of the RTC in observer mode allows only for observer and reading of data provided on RTC. In Observer Mode, the RTC may not be used to make data entries. This includes pushback, holds, and proceed inputs as well as updates to a flights data using the flight menu. However, using the RTC in Observer Mode allows for real time observation of ramp operations including pushback and hold entries made by the ramp sector controllers. The pushback advisories and Traffic Management Initiative information is also provided in Observer Mode. The RTC also provides notifications, runway departure counts and lists and near arrival flight lists as additional sources of information for management of ramp traffic. There are also detailed instructions for how to manage traffic with Surface Time Based Metering (STBM) advisories provided on RTC if in STBM mode. This document also provides instructions for use of the Ramp Manager Traffic Console (RMTC) while performing ramp manager functions such as managing the priority flight list, setting ramp status, and setting the metering mode. The RTC and RMTC ramp tool are one component of a suite of ATD-2 Tools.

Stevens, Lindsay K.↗
NASA NTRS2018

Ramp Traffic Console (RTC) Ramp Manager Traffic Console (RMTC) User Manual

This document serves as a user manual for the Ramp Traffic Console (RTC) in the Ramp Control Tower. It describes the elements of the RTC interface and provides explanations for how to utilize the RTC to manage ramp traffic. The RTC provides live data for all flights including Earliest Off-Block Times (EOBT) and Traffic Management Initiatives (TMI). The RTC augments management of ramp traffic by providing notifications of runway configurations, and lists flight arrivals, near arrivals and departures as additional sources of information. If applicable, this document also provides instructions for use of the Ramp Manager Traffic Console (RMTC) for ramp manager functions of adjusting the priority flight list, and setting ramp status. The RTC/RMTC ramp tool are components of Airspace Technology Demonstration-2.

ATD-2 RMTC↗
NASA NTRS2019

Ramp Traffic Console (RTC) Ramp Manager Traffic Console (RMTC) User Manual

This document serves as a user manual for the Ramp Traffic Console (RTC) Version 4.6.0 in the Ramp Control Tower. It describes the elements of the RTC interface and provides explanations for how to utilize RTC to manage ramp traffic. RTC provides live data for all flights including Earliest Off-Block Times (EOBTs) and Traffic Management Initiatives (TMIs). RTC augments management of ramp traffic by providing notifications of runway configurations, and lists flight arrivals, near arrivals, and departures as additional sources of information. This document also provides instructions for use of the Ramp Manager Traffic Console (RMTC) for Ramp Manager functions, such as adjusting the priority flight list and setting the ramp status. The RTC/RMTC ramp tools are components of the NASA Airspace Technology Demonstration 2 (ATD-2) sub-project.

Airport surface decision support tool↗
NASA NTRS2020

Ramp Traffic Console (RTC) and Ramp Manager Traffic Console (RMTC) User Manual

This document serves as a user manual for the ATD-2 Ramp Traffic Console (RTC) (version 5.11) utilized by the Ramp Control Tower. It describes the elements of the RTC interface and provides step-by-step instructions for using the tool. RTC provides live flight information, including, flight state and location, departure/arrival schedules, gate conflicts, Traffic Management Initiative (TMI) restrictions, and gate advisories to support Surface Time-Based Metering (STBM). RTC facilitates information sharing with the Air Traffic Control (ATC) Tower. This document also provides instructions for use of the Ramp Manager Traffic Console (RMTC) for Ramp Manager functions, such as managing the priority flight list and setting the ramp status. The RTC/RMTC ramp tools are components of the NASA Airspace Technology Demonstration 2 (ATD-2) sub-project.

Deborah Lee Bakowski↗
NASA NTRS1985

Performance analysis of the DSN baseband assembly (Bba) Real-Time Combiner (RTC)

The operation of the BBA Real Time Combiner (RTC) is discussed and its performance investigated in detail. It is shown that each channel of the RTC can be modelled by a simple block diagram in the z-transform domain from which all pertinent transient and steady state behavioral characteristics can be determined. In particular, the characteristic equation of the tracking loop and its equivalent noise bandwidth are found and used to evaluate the closed loop transient response and steady-state mean squared timing jitter. The impact of the totality of these loop jitter contributions on the combiner output SNR is evaluated and illustrated numerically. These results show that for parameters of interest to various space missions, the RTC is capable of providing significant SNR improvement relative to a single receiving antenna.

Simon, M. K.↗
NASA NTRS1984

Performance analysis of the DSN baseband assembly (Bba) Real-Time Combiner (RTC)

The operation of the BBA Real Time Combiner (RTC) is discussed and its performance investigated in detail. It is shown that each channel of the RTC can be modelled by a simple block diagram in the z-transform domain from which all pertinent transient and steady state behavioral characteristics can be determined. In particular, the characteristic equation of the tracking loop and its equivalent noise bandwidth are found and used to evaluate the closed loop transient response and steady state mean squared timing jitter. The impact of the totality of these loop jitter contributions on the combiner output SNR is evaluated and illustrated numerically. These results show that for parameters of interest to various space missions, the RTC is capable of providing significant SNR improvement relative to a single receiving antenna.

Simon, M. K.↗
NASA NTRS2002

RTC: a distributed realtime control system toolkit

The Jet Propulsion Laboratory (JPL) has built several optical interferometers using a common software framework developed for this purpose. The heart of this framework is the Realtime Control (RTC) software product. RTC has evolved from its initial implementation to include a powerful dynamic configuration capability and to use Common Object Request Broker Architecture (CORBA) technology for commanding and telemetry. This paper describes the current implementation of this toolkit.

RTC↗
NASA NTRS2018

Analysis of Impact of RTC Errors on CTOP Performance

Adoption of CTOPs in airspace has been hampered by a lack of willingness of a majority of airlines to participate in CTOP as there is significant cost in changing workflows and upgrading technology. No commercial vendors are currently offering TOS generation capability. Simpler, cheaper TOS generators may have more errors in RTC specification as compared to sophisticated TOS generators. This study investigates the impact of RTC errors on CTOP performance.

CTOP↗
NASA NTRS2019

Ramp Traffic Console (RTC) Capabilities and Use in Operational Environment (Part 1)

This presentation provides an overview of ramp traffic control (RTC) and ramp manager traffic console (RMTC) features of ATD-2 Integrated Arrival, Departure, and Surface (IADS) system and will discuss operational use cases that cover surface metering, notification and optional hold of APREQ (approval request/call for release), EDCT (expected departure clearance time), and ground stops.

Airline Ramp Decision Support↗
NASA NTRS2019

Ramp Traffic Console (RTC) Lessons Learned

This presentation provides lessons learned for use of ramp traffic control (RTC) and ramp manager traffic console (RMTC) features of the ATD-2 (Airspace Technology Demonstration 2) Integrated Arrival, Departure, and Surface (IADS) system in an operational environment.

Jung, Yoon↗
NASA NTRS2018

Evaluation of Usability and Workload with Paper Strips as Compared to Virtual Flight Strips Used for Ramp Operations

This paper describes an experiment designed to compare the use of paper strips with the use of a new user interface, the Ramp Traffic Console (RTC), designed for use by ramp controllers to be used in place of paper strips. A Human-In-the-Loop (HITL) experiment was performed as the fifth study in a series of six HITL simulation experiments designed to evaluate a concept that provided advisories to the users. The RTC was designed to be used as a Decision Support Tool (DST) that provided advisories to ramp controllers regarding metering or pushback such that most of the delay was taken at the gate to save fuel and emissions. In addition to being a DST, an added benefit of the RTC is that it can provide real-time updates of flight data, airport and airspace status to the controller including Traffic Management Initiatives (TMI). The RTC was designed as new user interface that displays virtual strips on a terminal map drawn on a 27-inch touch screen monitor. The RTC was used in some conditions of the experiment by ramp controllers in place of paper strips and paper maps in the HITL environment. In other conditions the controllers were given paper strips and paper maps similar to what they currently use at Charlotte Douglas International Airport (CLT). The study described here, evaluated the use of the virtual strips displayed on the RTC as compared to the use of paper strips and paper map, using current ramp tower controllers at CLT as participants. The research question being asked was - How does management of ramp traffic affect user workload and usability ratings while using RTC to manage traffic in the ramp verses using paper strips? Workload for our purposes is defined by four components of the NASA-TLX (Task Load Index). Usability was assessed with two sets of usability questions - One set of usability questions addressed traffic management performance and the other set addressed issues of resources and efficiency. Both Post Run and Post Study questionnaire responses were gathered and the results were analyzed to assess controller workload and usability ratings under both conditions, virtual strips shown on RTC and Paper Strips. The results indicate that controllers perceived lower workload while using virtual strips displayed on RTC to manage ramp traffic. Usability ratings for Traffic management performance questions are lower in the virtual strip/RTC condition than in the paper strip condition showing a preference for RTC over Paper. Usability ratings for Resources and efficiency questions show mixed results. Additionally, the Post Study Questions show preference for RTC over paper strips. Results of this data analysis will be presented in this paper. This DST evaluation was an important step in researching and improving the tool, which was planned to be deployed in the field.

Aviation Decision Support Tools↗
NASA NTRSDate not supplied

Evaluating SAR Radiometric Terrain Correction products: Optimal products for applied users

Operational applications for Synthetic Aperture Radar (SAR) are under development around the world, driven by the free-and-open access of SAR C-band observations that Sentinel-1 of Copernicus has been providing since 2014. Groups like SERVIR, a joint initiative between NASA and USAID, are at the forefront of remote sensing applied uses, and have made many significant contributions to lower the barrier to access, process, and apply SAR for ecosystem services. A takeaway from the SERVIR experience in using SAR is the need to use the appropriate SAR polarimetric product. Radiometric Terrain Correction (RTC) is a key entry-level product for multiple applications that range from ecosystems to hazards. Many software packages exist to create RTC products from SLC or GRD-type Level-1 SAR data, some of which were released only recently, e.g. Interferometric SAR Computing Environment (ISCE) added an RTC module in April 2020. In addition, new versions of open source softwares are expected to address known issues from previous versions, such as Sentinel-1 Toolbox from the European Space Agency (SNAP-7). Despite the growing availability of RTC software solutions, little work has been done to identify differences between RTC products from different softwares. And to address the question, which open-source software produces the most accurate RTC product? This work evaluates Sentinel-1 RTC products created with three different softwares and approaches, including SNAP-7, ISCE-2, and a pseudo RTC product derived from GEE. The GAMMA-derived RTC product, a known optimal RTC and implemented by Alaska Satellite Facility (ASF), is used as a reference. Time series stacks over ten different sites representing varied terrain and ecosystems are evaluated. Products are evaluated for geolocation quality, absolute radiometric calibration, and for the fidelity of the radiometric terrain flattening. The results provide direct guidance and recommendations about the quality of the RTC products obtained from open source methods. This understanding is key to develop operational applications that rely on SAR Sentinel-1 data that need affordable and scalable solutions.

Africa Flores-Anderson↗
NASA NTRSDate not supplied

Display and Automation Considerations for the Airborne Collision Avoidance System Xu

In this paper we examine several display and automation considerations of a collision avoidance system that is currently under development: the Airborne Collision Avoidance System (ACAS) Xu. This study builds on previous work conducted as part of NASA’s Unmanned Aircraft Systems (UAS) Integration into the National Airspace System (NAS) project. ACAS Xu represents the next-generation successor to the Traffic Alert and Collision Avoidance System (TCAS II), wherein the Xu variant is intended for UAS applications. Whereas TCAS II exclusively issues RAs in the vertical dimension, a major distinction between ACAS Xu and previous collision avoidance (CA) systems is the introduction of horizontal and “blended” RAs (i.e., RAs with both horizontal and vertical components). This present work was conducted as an engineering analysis involving two parts. In Part 1, a two-by-two, within-subjects study was performed that manipulated how RAs were presented to a pilot situated at a UAS ground control station. Five participants experienced four experimental trials in which text and aural alerting characteristics were manipulated. In Part 2, another five participants experienced four trials in which the levels of automation were manipulated with regard to the CA and return-to-course (RTC) tasks. The results for Part 1 found no effect of display or alerting configuration on pilot performance. However, it was discovered that pilot response time to RAs greatly depended on the RA type. In particular, pilots were quicker to respond to vertical RAs (M = 4.52 seconds) than horizontal (M = 7.42 seconds) and blended (M = 9.68 seconds) RAs in which both dimensions were issued simultaneously. For Part 2 of the study, pilots found both auto-CA and auto-RTC functions equally useful. Most pilots were comfortable with the automation, however responses were mixed. Three of five participants indicated high levels of comfort with the auto-CA function, while two rated their comfort as low. Pilots’ comfort for the auto-RTC functionality was slightly higher: four out of five pilots gave high ratings, while one pilot gave a low rating. Overall, pilots ordinally ranked their preference for automated functions as auto-CA together with auto-RTC (when an aural alert announces a change between CA and RTC states), auto-CA, and auto-CA and RTC (without the aural state-change announcement). Recommendations for improving the display of automation are also discussed.

collision avoidance↗
NASA NTRSDate not supplied

Display and Automation Considerations for the Airborne Collision Avoidance System Xu

In this presentation we examine several display and automation considerations of a collision avoidance system that is currently under development: the Airborne Collision Avoidance System (ACAS) Xu. This study builds on previous work conducted as part of NASA’s Unmanned Aircraft Systems (UAS) Integration into the National Airspace System (NAS) project. ACAS Xu represents the next-generation successor to the Traffic Alert and Collision Avoidance System (TCAS II), wherein the Xu variant is intended for UAS applications. Whereas TCAS II exclusively issues RAs in the vertical dimension, a major distinction between ACAS Xu and previous collision avoidance (CA) systems is the introduction of horizontal and “blended” RAs (i.e., RAs with both horizontal and vertical components). This present work was conducted as an engineering analysis involving two parts. In Part 1, a two-by-two, within-subjects study was performed that manipulated how RAs were presented to a pilot situated at a UAS ground control station. Five participants experienced four experimental trials in which text and aural alerting characteristics were manipulated. In Part 2, another five participants experienced four trials in which the levels of automation were manipulated with regard to the CA and return-to-course (RTC) tasks. The results for Part 1 found no effect of display or alerting configuration on pilot performance. However, it was discovered that pilot response time to RAs greatly depended on the RA type. In particular, pilots were quicker to respond to vertical RAs (M = 4.52 seconds) than horizontal (M = 7.42 seconds) and blended (M = 9.68 seconds) RAs in which both dimensions were issued simultaneously. For Part 2 of the study, pilots found both auto-CA and auto-RTC functions equally useful. Most pilots were comfortable with the automation, however responses were mixed. Three of five participants indicated high levels of comfort with the auto-CA function, while two rated their comfort as low. Pilots’ comfort for the auto-RTC functionality was slightly higher: four out of five pilots gave high ratings, while one pilot gave a low rating. Overall, pilots ordinally ranked their preference for automated functions as auto-CA together with auto-RTC (when an aural alert announces a change between CA and RTC states), auto-CA, and auto-CA and RTC (without the aural state-change announcement). Recommendations for improving the display of automation are also discussed.

collision avoidance↗
NASA NTRS1974

Effects of angular acceleration on man - Choice reaction time using visual and rotary motion information

This experiment was concerned with the effects of rotary acceleration on choice reaction time (RTc) to the motion of a luminous line on a cathode-ray tube. Specifically, it compared the (RTc) to rotary acceleration alone, visual acceleration alone, and simultaneous, double stimulation by both rotary and visual acceleration. Thirteen airline pilots were rotated about an earth-vertical axis in a precision rotation device while they observed a vertical line. The stimuli were 7 rotary and visual accelerations which were matched for rise time. The pilot responded as quickly as possible by displacing a vertical controller to the right or left. The results showed a decreasing (RTc) with increasing acceleration for all conditions, while the (RTc) to rotary motion alone was substantially longer than for all other conditions. The (RTc) to the double stimulation was significantly longer than that for visual acceleration alone.

Clark, B.↗
NASA NTRS2004

Framework for Development of Object-Oriented Software

The Real-Time Control (RTC) Application Framework is a high-level software framework written in C++ that supports the rapid design and implementation of object-oriented application programs. This framework provides built-in functionality that solves common software development problems within distributed client-server, multi-threaded, and embedded programming environments. When using the RTC Framework to develop software for a specific domain, designers and implementers can focus entirely on the details of the domain-specific software rather than on creating custom solutions, utilities, and frameworks for the complexities of the programming environment. The RTC Framework was originally developed as part of a Space Shuttle Launch Processing System (LPS) replacement project called Checkout and Launch Control System (CLCS). As a result of the framework s development, CLCS software development time was reduced by 66 percent. The framework is generic enough for developing applications outside of the launch-processing system domain. Other applicable high-level domains include command and control systems and simulation/ training systems.

Perez-Poveda, Gus↗