Impedance-Loaded SAW Reflective Delay Lines for Monitoring Corrosion in Pipelines
For presentation at the 2023 ISAF-ISIF-PFM Joint Conference, Cleveland, OH, July 23-27, 2023.
Devkota, Jagannath↗
SEARCH · Engineering Papers
Results for “delays”
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.
Apparatus and method for facilitating planar delayering of integrated circuit die
An apparatus and method for facilitating the removal of layers from a die for an integrated circuit while maintaining the planarity of the surface of the die by avoiding rounding the corners and other edges of the die. A pocket is created in a sacrificial material, such that when the die is inserted into the pocket the edges of the die are contiguous with the walls of the pocket and a top surface of the die is coplanar with a top surface of the pocket. The sacrificial material may be the same material as the die. An adhesive substance is placed in the pocket, and the die is inserted into the pocket and against the adhesive substance which aids in retaining the die in the pocket. The layers may then be removed from the die and the sacrificial material around the die without rounding the edges of the die.
Trujillo, Joshua Joseph↗
Shell Model Methods, Statistical Nuclear Reactions, and Beta-delayed Neutron Emission
Explore the source record for details and available documents.
Physics - Nuclear physics and radiation physics↗
Hold-off and Nanosecond-Scale Delay Times of C4F7N Electric Breakdown compared to other Insulating Gases at up to 3 atm Pressure
Explore the source record for details and available documents.
Physics - Plasma physics↗
Development of Chemical-Encapsulating Microparticles for Delayed Flow Diverter Formation in EGS Reservoirs Away from Wells
Explore the source record for details and available documents.
Chang, Chun↗
Multilevel Bayesian Calibration of Fission Gas Diffusivity in Nuclear Fuels using Multilevel Delayed Acceptance MCMC
Explore the source record for details and available documents.
Robbe, Pieterjan Magda M↗
Self regulating body bias generator
The back bias voltage on a functional circuit is controlled through a closed loop process. A delay element receives a clock pulse and produces a delay output. The delay element is advantageously constructed of the same materials as the functional circuit so that the aging and degradation of the delay element parallels the degradation of the functional circuit. As the delay element degrades, the transistor switching time increases, increasing the time delay of the delay output. An AND gate compares a clock pulse to an output pulse of the delay element, the AND output forming a control pulse. A duty cycle of the control pulse is determined by the delay time between the clock pulse and the delay element output. The control pulse is received at the input of a charge pump. The charge pump produces a back bias voltage which is then applied to the delay element and to the functional circuit. If the time delay produced by the delay element exceeds the optimal delay, the duty cycle of the control pulse is shortened, and the back bias voltage is lowered, thereby increasing the switching speed of the transistors in the delay element and reducing the time delay. If the throughput of the delay element is too fast, the duty cycle of the control pulse is lengthened, raising the back bias voltage produced by the charge pump. This, in turn, lowers the switching speed of the transistors in both the delay element and the functional circuit. The slower switching speed in the delay element increases time delay. In this manner, the switching speed of the delay element, and of the functional circuit, is maintained at a constant level over the life of the circuit.
Hass, Kenneth↗
Characterization of Days Based On Analysis of National Airspace System Performance Metrics
Days of operations in the National Airspace System can be described in term of traffic demand, runway conditions, equipment outages, and surface and enroute weather conditions. These causes manifest themselves in terms of departure delays, arrival delays, enroute delays and traffic flow management delays, Traffic flow management initiatives such as, ground stops, ground delay programs, miles-in-trail restrictions, rerouting and airborne holding are imposed to balance the air traffic demand with respect to the available capacity, In order to maintain operational efficiency of the National Airspace System, the Federal Aviation Administration (FAA) maintains delay sad other statistics in the Air Traffic Operations Network (OPSNET) and the Aviation System Performance Metrics (ASPM) databases. OPSNET data includes reportable delays of fifteen minutes ox more experienced by Instrument Flight Rule (IFR) flights. Numbers of aircraft affected by departure delays, enroute delays, arrival delays and traffic flow delays are recorded in the OPSNET data. ASPM data consist of number of actual departures, number of canceled departures, percentage of on time departures, percentage of on time gate arrivals, taxi-out delays. taxi-in delays, gate delays, arrival delays and block delays. Surface conditions at the major U.S. airports are classified in terms of Instrument Meteorological Condition (IMC) and Visual Meteorological Condition (VMC) as a function of the time of the day in the ASPM data. The main objective of this paper is to use OPSNET and ASPM data to classify the days in the datasets into few distinct groups, where each group is separated from the other groups in terms of a distance metric. The motivations for classifying the days are two-fold, 1) to enable selection of days of traffic with particular operational characteristics for concept evaluation using system-wide simulation systems such as the National Aeronautics and Space Administration's Airspace Concepts Evaluation Tool (ACES) and 2) to enable evaluation of a given day with respect to the characteristics of the classified groups. The first part of the paper is devoted to the analysis of major trends seen in the OPSNET and ASPM data. The second part of the paper is devoted to describing features or measures derived from the OPSNET and ASPM data that are suitable for characterizing days, and the classification algorithm used for grouping the days. Finally, the method for evaluating the characteristics of a given day with respect to the properties of the groups is described.
Chatterji, Gano B.↗
Interaction Between Strategic and Local Traffic Flow Controls
The loosely coordinated sets of traffic flow management initiatives that are operationally implemented at the national- and local-levels have the potential to under, over, and inconsistently control flights. This study is designed to explore these interactions through fast-time simulations with an emphasis on identifying inequitable situations in which flights receive multiple uncoordinated delays. Two operationally derived scenarios were considered in which flights arriving into the Dallas/Fort Worth International Airport were first controlled at the national-level, either with a Ground Delay Program or a playbook reroute. These flights were subsequently controlled at the local level. The Traffic Management Advisor assigned them arrival scheduling delays. For the Ground Delay Program scenarios, between 51% and 53% of all arrivals experience both pre-departure delays from the Ground Delay Program and arrival scheduling delays from the Traffic Management Advisor. Of the subset of flights that received multiple delays, between 5.7% and 6.4% of the internal departures were first assigned a pre-departure delay by the Ground Delay Program, followed by a second pre-departure delay as a result of the arrival scheduling. For the playbook reroute scenario, Dallas/Fort Worth International Airport arrivals were first assigned pre-departure reroutes based on the MW_2_DALLAS playbook plan, and were subsequently assigned arrival scheduling delays by the Traffic Management Advisor. Since the airport was operating well below capacity when the playbook reroute was in effect, only 7% of the arrivals were observed to receive both rerouting and arrival scheduling delays. Findings from these initial experiments confirm field observations that Ground Delay Programs operated in conjunction with arrival scheduling can result in inequitable situations in which flights receive multiple uncoordinated delays.
Grabbe, Son↗
Centering a DDR Strobe in the Middle of a Data Packet
The Orion CEV Northstar ASIC (application- specific integrated circuit) project required a DDR (double data rate) memory bus driver/receiver (DDR PHY block) to interface with external DDR memory. The DDR interface (JESD79C) is based on a source synchronous strobe (DQS\) that is sent along with each packet of data (DQ). New data is provided concurrently with each edge of strobe and is sent irregularly. In order to capture this data, the strobe needs to be delayed and used to latch the data into a register. A circuit solves the need for training a DDR PRY block by incorporating a PVT-compensated delay element in the strobe path. This circuit takes an external reference clock signal and uses the regular clock to calibrate a known delay through a data path. The compensated delay DQS signal is then used to capture the DQ data in a normal register. This register structure can be configured as a FIFO (first in first out), in order to transfer data from the DDR domain to the system clock domain. This design is different in that it does not rely upon the need for training the system response, nor does it use a PLL (phase locked loop) or a DLL (delay locked loop) to provide an offset of the strobe signal. The circuit is created using standard ASIC building blocks, plus the PVT (process, voltage, and temperature) compensated delay line. The design uses a globally available system clock as a reference, alleviating the need to operate synchronously with the remote memory. The reference clock conditions the PVT compensated delay line to provide a pre-determined amount of delay to any data signal that passes through this delay line. The delay line is programmed in degrees of offset, so that one could think of the clock period representing 360deg of delay. In an ideal environment, delaying the strobe 1/4 of a clock cycle (90deg) would place the strobe in the middle of the data packet. This delayed strobe can then be used to clock the data into a register, satisfying setup and hold requirements of the system.
Johnson, Michael↗
A Machine Learning Approach to Improve Air Traffic Management Initiatives
Collaborating closely with commercial air carriers and related organizations, the Federal Aviation Administration(FAA) regulates air traffic and ensures the safety and efficiency of air operations. Air traffic controllers make strategic decisions, such as delaying, rerouting, or canceling flights, partly based on guidance provided by the FAA’s Air TrafficControl System Command Center (ATCSCC). The guidance includes, among other things, control measures known asTraffic Management Initiatives (TMIs) designed to enhance safety and improve operational efficiency. TMIs play a crucial role in managing the demand and capacity within the U.S. National Airspace System (NAS). Two major TMIs that are routinely used (primarily to mitigate the adverse effects of bad weather) are Ground Delay Programs (GDPs) andGround Stops (GSs). In a GDP, flights destined for airports facing thunderstorm activity experience delays at their origin airports. This proactive approach minimizes the risk of routing aircraft through hazardous weather conditions and also replaces (fuel burning) airborne delays with ground delays. In a GS, a temporary restriction is imposed on the departure or arrival of aircraft at a specific airport or within a designated airspace. Although other TMIs (e.g., miles-in-trail) are also implemented as part of (air) traffic flow management in the NAS, the focus of this work is on GDPs and GSs. Since TMIs, by design, lead to flight delays or cancellations, it is crucial to put in place the right set of parameters(e.g., scope and duration of the GDP). For example, when the end time of a GDP extends beyond what is necessary, it imposes unnecessary delays on departing flights. This situation could occur as a result of inaccurate prediction of the(required) duration of the GDP based on the weather forecast. On the other hand, if a GDP ends prematurely before the underlying capacity constraints are resolved at the destination airport, it may result in airborne holding. The delicate balance lies in matching the termination of the GDP precisely with the resolution of capacity constraints, avoiding both the imposition of unnecessary ground delays and the need for airborne holding due to premature program termination.Failing to specify the right parameters for TMIs also leads to flight delays, creating a significant obstacle in managing the increasing traffic volumes causing increased work load for the controllers. To address this issue, we propose the integration of Machine Learning (ML) models in the traffic flow management(TFM) pipeline. In current operations, decisions are made by human experts based on extensive training, historical patterns, available traffic and weather data. Since we have an abundance of data from past events that tell us the likely impact of various TMIs, by ingesting historical data, properly trained ML models can offer valuable insights and aid human decision-making. With the FAA increasingly exploring advanced analytics, ML emerges as a focal point for enhancing TFM within the National Airspace System (NAS). As a first step, this study aims to provide traffic controllers with decision-making support for the issuance and adjustment of TMIs. Data analytics and machine learning have been previously employed to address some of the challenges associated with TMIs. Numerous studies have concentrated on various facets of TMI issuance, exploring factors influencing TMI parameters, including arrival rate, airport capacity, and delay prediction. For example, using weather forecasts, several statistical methods were used to produce probabilistic capacity profiles which in conjunction with deterministic models provided insights into the GDP planning process [1–4]. The downside of using deterministic models is that they rely on fixed inputs and predetermined rules, which lack the ability to account for the inherent uncertainty and variability present in real-world scenarios. In a separate series of studies, researchers aimed to predict the occurrences of GDPs and GSs. The majority of these studies utilized various supervised learning methods, including Decision Trees, Naive Bayes, Support VectorMachines, and Random Forests to analyze the influence of weather conditions and arrival demand on TMI incidents[5–8]. However, these studies primarily focused on predicting the incidence of TMIs without explicitly addressing the scope of TMIs, including their duration and their geographical coverage. Furthermore, the emphasis of these studies was largely on GDPs, given their higher frequency and longer duration when compared to GSs. A limited number of studies focused on predicting the parameters of TMIs, specifically addressing their duration and extent. In one such study focusing on optimizing the TMI parameters at San Francisco International Airport (SFO),the authors utilized a probabilistic forecast of fog [9]. They simulated various capacity scenarios based on the (fog)burn-off forecasts, selecting GDP parameters that minimized airborne and overall ground delays. However, this approach exclusively emphasizes stratus (fog) burn-off as the primary determinant of GDP and GS, neglecting other influential factors like severe weather events, runway closures, lower capacity than traffic demand, and other important variables. Given the complexity of predicting the TMI and determining its scope, we seek a more holistic approach. We aim to consider all significant factors that could impact TMIs and their parameters. What sets this research apart is the fusion of all data sources relevant to the issuance and adjustment of TMIs and it represents the first comprehensive attempt to optimize TMIs in this manner. Since this comprehensive solution involves various aspects, we break down the problem into smaller components and input all parameters into a unified model called the “TMI Adjuster”. Figure 1 shows the overall framework and the list of datasets used in each model. The objective of the TMI Adjuster module is to deliver reliable, consistent and expedited recommendations for the progression, adjustment, and termination of TMIs. The ML solution entails developing a pipeline capable of predicting the necessity of a TMI (e.g., GS or GDP) along with its various parameters. For example, in the case of a GS, this includes the scope of the GS either in terms of distance from the destination airport or based on pre-defined airspace sectors. Here, scope refers to those regions and departing airports that are subject to the GS. In this paper, we concentrate on the issuance of GSs in the three major airports in the New York area — LaGuardia(LGA), John F. Kennedy International (JFK), and Newark Liberty International (EWR). We fuse traffic, weather and other relevant aviation data from years 2017 to 2019 to train and validate the ML models. In particular, we use the following datasets: •Terminal Aerodrome Forecast (TAF): meteorological forecasts specific to each airport, issued four times a day, covering predefined time periods. •TMI data: includes all GSs and GDPs along with their respective parameters. •Aviation System Performance Metrics (ASPM): includes traffic related data such as aircraft delays, arrival, and departure rates. •Notices to Airmen (NOTAMs): utilized to extract runway closure data and manage interdependencies between terminals in close proximity. •Flight cancellation data •Airspace Flow Programs (AFP): includes information on flight airborne holdings caused by TMIs. The data preprocessing entails transforming ASPM, TMI, AFP, NOTAMs, and weather data into an hourly format and consolidating all datasets by merging them based on date and time as the primary key. The TMI Adjuster framework comprises two parallel models: one dedicated to GS and a second model focused on GDP. As previously mentioned, our specific focus is on the GS model as a multi-classification problem. In this framework, each data point of the GS model input summarizes ten hours of data. Specifically, the data loader for the GS model generates the input and output of the model as follows: at a given time step, the input includes the actual traffic, weather, and TMI data from the two-hour window before the time step, alongside the weather forecast and scheduled traffic for the next 8 hours starting from the time step. Based on this information, the output of the GS model for each time interval consists of three dimensions. The first dimension represents a binary decision on whether there should be a GS in place for the next hour or not. The second dimension is related to the scope of the GS in the United States, and the third dimension is related to the scope of the GS in Canada (i.e., to determine if the GS impacts airports in Canada).One of the challenges with TMI modeling is the sparsity of TMI events, particularly regarding its scope. To address this challenge in the scope of the GS model output, we implement grouping. The GS scope for the US region is defined based on a list of centers that should be included when the GS is in place. With 20 centers in the US, we utilized historical data to group them into 4 categories. In particular, we summarized our historical data in a graph format where nodes represent centers, and link weights are defined based on the co-occurrence of centers in the scope parameter ofTMIs. By identified strongly connected components in this graph, we were able to partition the centers into four groups. We consider two model structures for the GS Model. Firstly, a hierarchical classification model [10], where the human decision-making for a GS is of hierarchical nature. The decision-maker first decides whether there is a need fora GS, and if the answer is yes, determines the scope. A hierarchical classification model organizes the problem into a class hierarchy, typically a tree or a Directed Acyclic Graph (DAG) structure, and considers the dependency of the decision in the previous step to the next component [10]. Here, we employ the local classifier per level approach, which involves training one multi-class classifier for each level of the class hierarchy. The second structure is the independent structure. In this setting, as the name suggests, we do not consider the dependency of the decisions in the different dimensions of the output of the model. Instead, for each dimension, we train a multi-class classifier independently. Table 1 summarizes GS model statistics for training, validation and testing. The table documents the effect of limiting data to the time steps when there was actually a TMI in place or when a TMI had just terminated. This resulted in a more balanced distribution of the GS class(GS positive class)versus “No GS”(GS negative class), which might help the training process. While JFK and LGA follow very similar distributions, with 40% and 42% GS positive class respectively, EWR has proportionally fewer GS incidents at 28%. Our subsequent phase involves evaluating the performance of both hierarchical structure and independent structure using different state-of-the-art multi-class classifier models such as Random Forest, Decision Trees, K-nearest Neighbors, and Logistic Regression and forecast the duration and scope of the GSs.
Farzan Masrour Shalmani↗
Radio Interferometric Determination of Source Positions, Intercontinental Baselines, and Earth Orientation with Deep Space Network Antennas: 1971 to 1980
Approximately 2400 observations of extragalactic radio sources were made between August 1971 and February 1980 during 48 separate sessions. These consisted of 259 delay rate observations at 2.3 GHz (S-band), 796 delay and delay rate observations at either S-band of 8.3 GHz (X-band) and 1325 delay and delay rate observations recorded simultaneously at both S- and X-band. A single multiparameter fit has been applied to the observed values of delay and delay rate to extract astrometric and geophysical parameters from this decade-long sequence. The fit produced estimates of 784 parameters, including station locations, radio source positions, polar motion, Universal Time, the precession constant, and solid earth tides. The a priori model included gravitational bending, the 1980 IAU nutation series, the 1976 IAU expressions for Greenwich mean sidereal time and precession, BIH estimates of Universal Time and polar motion, and monthly mean values for zenith troposphere delay. The rms residuals were 0.52 nsec for delay and 0.30 psec/sec for delay rate. Intercontinental baseline lengths were determined with formal uncertainties of 5 to 10 cm. Universal Time and polar motion were measured at 49 epochs, with formal uncertainties (for the more recent data) of 0.5 msec for UT1 and 6 and 2 mas, respectively, for the X and Y components of polar motion.
Thomas, J. B.↗
Radio interferometric determination of source positions utilizing deep space network antennas - 1971 to 1980
Approximately 2400 observations of extragalactic radio sources were made between August 1971 and February 1980 during 48 separate sessions. These consisted of 259 delay rate observations at 2.3 GHz (S-band), 796 delay and delay rate observations at either S-band of 8.3 GHz (X-band) and 1325 delay and delay rate observations recorded simultaneously at both S- and X-band. A single multiparameter fit has been applied to the observed values of delay and delay rate to extract astrometric and geophysical parameters from this decade-long sequence. The fit produced estimates of 784 parameters, including station locations, radio source positions, polar motion, Universal Time, the precession constant, and solid earth tides. The a priori model included gravitational bending, the 1980 IAU nutation series, the 1976 IAU expressions for Greenwich mean sidereal time and precession, BIH estimates of Universal Time and polar motion, and monthly mean values for zenith troposphere delay. The rms residuals were 0.52 nsec for delay and 0.30 psec/sec for delay rate. Intercontinental baseline lengths were determined with formal uncertainties of 5 to 10 cm. Universal Time and polar motion were measured at 49 epochs, with formal uncertainties (for the more recent data) of 0.5 msec for UT1 and 6 and 2 mas, respectively, for the X and Y components of polar motion. Previously announced in STAR as N83-28038
Fanselow, J. L.↗
Atmospheric limitations to clock synchronization at microwave frequencies
Clock synchronization schemes utilizing microwave signals that pass through the Earth's atmosphere are ultimately limited by our ability to correct for the variable delay imposed by the atmosphere. The atmosphere is non-dispersive at microwave frequencies and imposes a delay of roughly 8 nanosec times the cosecant of the elevation angle. This delay is composed of two parts, the delay due to water vapor molecules (i.e., the wet delay), and the delay due to all other atmospheric constituents (i.e., the dry delay). Water vapor contributes approximately 5 to 10% of the total atmospheric delay but is highly variable, not well mixed, and difficult to estimate from surface air measurements. However, the techniques of passive remote sensing using microwave radiometry can be used to estimate the line of sight delay due to water vapor with potential accuracies of 10 to 20 picosec. The devices that are used are called water vapor radiometers and simply measure the power emitted by the water vapor molecule at the 22.2 GHz spectral line. An additional power measurement is usually included at 31.4 GHz in order to compensate for the effect of liquid water (e.g., clouds). The dry atmosphere is generally in something close to hydrostatic equilibrium and its delay contribution at zenith can be estimated quite well from a simple barometric measurement. At low elevation angles one must compensate for refractive bending and possible variations in the vertical refractivity profile. With care these effects can be estimated with accuracies on the order of 30 picosec down to elevation angles of 10 degree.
Resch, G. M.↗
Analysis of picosecond coherent anti-Stokes Raman spectra for gas-phase diagnostics
We present a hybrid frequency- and time-domain solution, applicable to the case of picosecond coherent anti-Stokes Raman scattering (CARS), for gas-phase diagnostics. A solution has been derived based on both physical arguments and four-wave mixing equations for picosecond CARS, with pulse durations that are comparable to the dephasing time scale for gas-phase Raman coherence—a regime where commonly employed solutions for impulsive (femtosecond) or cw (nanosecond) pump/Stokes forcing are not strictly valid. We present the ps-CARS spectrum in the form of incoherent sums of CARS intensity spectra, calculated from the fundamental solution for impulsive pump/Stokes Raman preparation. The solution was examined for temperatures from 1000–3000 K, for four plausible experimental configurations, with laser pulse durations of 50–150 ps, and probe pulse delays from −20 to 240 ps. Approximations based on cw and impulsive pump/Stokes preparation to fit picosecond CARS spectra at atmospheric pressure were examined and the relative thermometric accuracy and computational cost of these approximations were quantified for the case of a zero nonresonant CARS contribution, and a nonresonant susceptibility equal to 10% of the Raman-resonant value at the N 2 bandhead. The nanosecond CARS approximation can result in large fitting errors when the probe pulse time delay is less than the probe pulse duration. Errors as large as 10–20% are observed in the fit temperatures for a zero picosecond probe pulse delay, when the nonresonant background is neglected, largely due to an inability of the time-independent cw model to capture transient frequency spread dephasing effects at the Q -branch bandhead. The inclusion of a nonresonant background results in 40–60% thermometry errors with a nanosecond model at a zero-probe delay. Time-dependent impulsive calculations used for femtosecond CARS better approximate the structure of the N 2 bandhead, reducing temperature fitting errors to 5–10% at a short probe pulse delay. The impulsive approximation results in errors up to 10% at intermediate probe pulse delays, where the coherence of the pump and probe pulses leads to multiple terms in the picosecond CARS solution. Both approximations improve as the probe pulse delay exceeds the probe duration. The nanosecond approximation results in a 2–3% error, while the impulsive model results in differences of less than 1% in some cases. Fits to experimental data obtained using short, ∼60ps pulses at a zero probe time delay and longer 100 ps pulses at a substantial 200 ps delay are presented with accuracies of 1–3% in the fit temperature.
Kearney, Sean P.↗
Benefit Assessment of the Precision Departure Release Capability Concept
A Precision Departure Release Capability concept is being evaluated by both the National Aeronautics and Space Administration and the Federal Aviation Administration as part of a larger goal of improving throughput, efficiency and capacity in integrated departure, arrival and surface operations. The concept is believed to have the potential of increasing flight efficiency and throughput by avoiding missing assigned slots and minimizing speed increase or path stretch to recover the slot. The main thrust of the paper is determining the impact of early and late departures from the departure runway when an aircraft has a slot assigned either at a meter fix or at the arrival airport. Results reported in the paper are for two scenarios. The first scenario considers flights out of Dallas/Fort Worth destined for Hartsfield-Jackson International Airport in Atlanta flying through the Meridian meter-fix in the Memphis Center with miles-in-trail constraints. The second scenario considers flights destined to George Bush Intercontinental/Houston Airport with specified airport arrival rate constraint. Results show that delay reduction can be achieved by allowing reasonable speed changes in scheduling. It was determined that the traffic volume between Dallas/Fort Worth and Atlanta via the Meridian fix is low and the departures times are spread enough that large departure schedule uncertainty can be tolerated. Flights can depart early or late within 90 minutes without accruing much more delay due to miles-in-trail constraint at the Meridian fix. In the Houston scenario, 808 arrivals from 174 airports were considered. Results show that delay experienced by the 16 Dallas/Fort Worth departures is higher if initial schedules of the remaining 792 flights are kept unaltered while they are rescheduled. Analysis shows that the probability of getting the initially assigned slot back after perturbation and rescheduling decreases with increasing standard deviation of the departure delay distributions. Results show that most Houston arrivals can be expected to be on time based on the assumed zero-mean Normal departure delay distributions achievable by Precision Departure Release Capability. In the current system, airport-departure delay, which is the sum of gate-departure delay and taxi-out delay, is observed at the airports. This delay acts as a bias, which can be reduced by Precision Departure Release Capability.
Palopo, Kee↗
Lunar Terrain Vehicle (LTV) Remote Teleoperation Studies Under Four Lunar Communication Latencies
Remotely operating a lunar rover from Earth while subject to an Earth-Moon time delay of multiple seconds could result in a dangerous state where the roving vehicle is either damaged or lost, thereby potentially compromising an entire mission or series of missions. Providing the right capabilities to the remote operator to manage inherent communication latencies will be important for remote driving to be successful. NASA conducted two studies to investigate the average speed and number of kilometers per day that an operator on Earth could teleoperate a notional Artemis unpressurized rover with minimal remote operator capabilities under 0- and 4-second communication delays (April 2023 study) and 6- and 8-second delays (August 2023 study). A primary goal of these studies was to understand if an Artemis Lunar Terrain Vehicle (LTV) could cover 6 kilometers (km) in 24 hours when operated remotely. During the April 2023 evaluation, eight test operators used an in-house simulation of the lunar surface South Pole to teleoperate a NASA government reference LTV. Each operator received approximately 30 minutes of remote driving familiarization/training prior to their test run. Operators viewed the surrounding terrain via a single, rover mast-mounted, high-resolution camera with pan/tilt/zoom capabilities; continuous communication was provided throughout all testing. In the August 2023 evaluation, remote operators received approximately 3 hours of familiarization training in each latency, and the simulation environment provided remote operators with an operator-selected rate limiter to enable finer sensitivity in the hand controller and a predictive circle function to better assist operators with predicting the path the vehicle could take. All test operators were able to successfully navigate and drive through six different types of terrain and five planned traverse scenarios using natural lighting under all communication delays. Results for average speeds for each communication delay, computed by averaging the data from all test conditions for that latency and all operators, are shown in the table below. The average speed data was then used to derive the total time needed to cover 6 km, 8 km, and 20 km (distances relevant to LTV-SYS071 and -029 requirements). Remote operators drove slower and used the brake more frequently when subject to a communication latency as opposed to no communication latency. Subjective workload assessments revealed that while operating in a latency the overall workload significantly increased when compared to a 0-s delay with mental demand, frustration, and performance being the primary contributing factors. Driving strategies in the 0-s delay did not vary significantly among subjects; however, in the 4-s delay condition, three different driving strategies were identified. In the 6-s and 8-s latency conditions the operator’s use of the cruise control to maintain speed was more apparent. Additionally, over the course of the August study, the operator took advantage of the predictive circle indicator on the navigation display and over 95% of the operator’s navigation used the mast camera 180-degree panning function for ground truthing in terms of boulders and craters. Operators started to define more specific parameters in driving strategies for general operations. This consisted of setting the vehicle into a low-speed cruise mode of approximately 11.5 kph and noticing driving performance of the vehicle seemed to be much harder at slower speeds 0.4–0.8 kph; however, the vehicle was more responsive at speeds of 2.9–3.6 kph. Regardless of communication delay, operators used both the horizontal translation rails and the vehicle fenders as guides to predict a path for the vehicle through heavily concentrated terrain features. Test operators acknowledged that the teleoperations training for this study was substantially less than what an actual LTV remote operator will ultimately receive. They estimated a minimum of 20 to 100 hours spread across multiple days and weeks (e.g., strategies included immersion training over a 3-day period, to a short 8-week starter program) would be needed to get an operator ~ 60% proficient (i.e., able to complete a subset of remote driving tasks), to a yearlong program for full proficiency in remote driving tasks under all terrain types and natural lighting conditions. Remotely operating a vehicle on another planetary body while subject to communication latency is a complex task. Speed, distance covered, time spent driving, time spent navigating, brake usage and rock contacts are all affected by operator workload, driving strategies, workstation ergonomics and training. These studies provided a “first-look” answer to a potential system requirement (namely if a remote operator could cover a given distance in a given amount of time); however, considerable general knowledge was gained to begin to understand what it will take to make a successful lunar rover teleoperator.
LTV↗
Lunar Terrain Vehicle (LTV) Remote Teleoperation Studies Under Four Lunar Communication Latencies
Remotely operating a lunar rover from Earth while subject to an Earth-Moon time delay of multiple seconds could result in a dangerous state where the roving vehicle is either damaged or lost, thereby potentially compromising an entire mission or series of missions. Providing the right capabilities to the remote operator to manage inherent communication latencies will be important for remote driving to be successful. The National Aeronautics and Space Administration (NASA) conducted two studies to investigate the average speed and number of kilometers per day that an operator on Earth could teleoperate a notional Artemis unpressurized rover with minimal remote operator capabilities under 0- and 4-second communication delays (April 2023 study) and 6- and 8-second delays (August 2023 study). A primary goal of these studies was to understand if an Artemis Lunar Terrain Vehicle (LTV) could cover 6 kilometers (km) in 24 hours when operated remotely. During the April 2023 evaluation, eight test operators used an in-house simulation of the lunar surface South Pole to teleoperate a NASA government reference LTV. Each operator received approximately 30 minutes of remote driving familiarization/training prior to their test run. Operators viewed the surrounding terrain via a single, rover mast-mounted, high-resolution camera with pan/tilt/zoom capabilities; continuous communication was provided throughout all testing. In the August 2023 evaluation, remote operators received approximately 3 hours of familiarization training in each latency, and the simulation environment provided remote operators with an operator-selected rate limiter to enable finer sensitivity in the hand controller and a predictive circle function to better assist operators with predicting the path the vehicle could take. All test operators were able to successfully navigate and drive through six different types of terrain and five planned traverse scenarios using natural lighting under all communication delays. Results for average speeds for each communication delay, computed by averaging the data from all test conditions for that latency and all operators, are shown in the table below. The average speed data was then used to derive the total time needed to cover 6 km, 8 km, and 20 km. Remote operators drove slower and used the brake more frequently when subject to a communication latency as opposed to no communication latency. Subjective workload assessments revealed that while operating in a latency the overall workload significantly increased when compared to a 0-s delay with mental demand, frustration, and performance being the primary contributing factors. Driving strategies in the 0-s delay did not vary significantly among subjects; however, in the 4-s delay condition, three different driving strategies were identified. In the 6-s and 8-s latency conditions the operator’s use of the cruise control to maintain speed was more apparent. Additionally, over the course of the August study, the operator took advantage of the predictive circle indicator on the navigation display and over 95% of the operator’s navigation used the mast camera 180-degree panning function for ground truthing in terms of boulders and craters. Operators started to define more specific parameters in driving strategies for general operations. This consisted of setting the vehicle into a low-speed cruise mode of approximately 1–1.5 kph and noticing driving performance of the vehicle seemed to be much harder at slower speeds 0.4–0.8 kph; however, the vehicle was more responsive at speeds of 2.9–3.6 kph. Regardless of communication delay, operators used both the horizontal translation rails and the vehicle fenders as guides to predict a path for the vehicle through heavily concentrated terrain features. Test operators acknowledged that the teleoperations training for this study was substantially less than what an actual LTV remote operator will ultimately receive. They estimated a minimum of 20 to 100 hours spread across multiple days and weeks (e.g., strategies included immersion training over a 3-day period, to a short 8-week starter program) would be needed to get an operator ~ 60% proficient (i.e., able to complete a subset of remote driving tasks), to a yearlong program for full proficiency in remote driving tasks under all terrain types and natural lighting conditions. Remotely operating a vehicle on another planetary body while subject to communication latency is a complex task. Speed, distance covered, time spent driving, time spent navigating, brake usage and rock contacts are all affected by operator workload, driving strategies, workstation ergonomics and training. These studies provided a “firstlook” answer to a potential system requirement (namely if a remote operator could cover a given distance in a given amount of time); however, considerable general knowledge was gained to begin to understand what it will take to make a successful lunar rover teleoperator.
LTV↗