Search NASA⌕ Search

SEARCH · Search NASA

Results for “Scheduled arrival operations”

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.

241 records · Page 14

Simple, Scalable, Script-Based Science Processor (S4P)

The development and deployment of data processing systems to process Earth Observing System (EOS) data has proven to be costly and prone to technical and schedule risk. Integration of science algorithms into a robust operational system has been difficult. The core processing system, based on commercial tools, has demonstrated limitations at the rates needed to produce the several terabytes per day for EOS, primarily due to job management overhead. This has motivated an evolution in the EOS Data Information System toward a more distributed one incorporating Science Investigator-led Processing Systems (SIPS). As part of this evolution, the Goddard Earth Sciences Distributed Active Archive Center (GES DAAC) has developed a simplified processing system to accommodate the increased load expected with the advent of reprocessing and launch of a second satellite. This system, the Simple, Scalable, Script-based Science Processor (S42) may also serve as a resource for future SIPS. The current EOSDIS Core System was designed to be general, resulting in a large, complex mix of commercial and custom software. In contrast, many simpler systems, such as the EROS Data Center AVHRR IKM system, rely on a simple directory structure to drive processing, with directories representing different stages of production. The system passes input data to a directory, and the output data is placed in a "downstream" directory. The GES DAAC's Simple Scalable Script-based Science Processing System is based on the latter concept, but with modifications to allow varied science algorithms and improve portability. It uses a factory assembly-line paradigm: when work orders arrive at a station, an executable is run, and output work orders are sent to downstream stations. The stations are implemented as UNIX directories, while work orders are simple ASCII files. The core S4P infrastructure consists of a Perl program called stationmaster, which detects newly arrived work orders and forks a job to run the appropriate executable (registered in a configuration file for that station). Although S4P is written in Perl, the executables associated with a station can be any program that can be run from the command line, i.e., non-interactively. An S4P instance is typically monitored using a simple Graphical User Interface. However, the reliance of S4P on UNIX files and directories also allows visibility into the state of stations and jobs using standard operating system commands, permitting remote monitor/control over low-bandwidth connections. S4P is being used as the foundation for several small- to medium-size systems for data mining, on-demand subsetting, processing of direct broadcast Moderate Resolution Imaging Spectroradiometer (MODIS) data, and Quick-Response MODIS processing. It has also been used to implement a large-scale system to process MODIS Level 1 and Level 2 Standard Products, which will ultimately process close to 2 TB/day.

Lynnes, Christopher↗

Orbit Determination of Spacecraft in Earth-Moon L1 and L2 Libration Point Orbits

The ARTEMIS mission, part of the THEMIS extended mission, is the first to fly spacecraft in the Earth-Moon Lissajous regions. In 2009, two of the five THEMIS spacecraft were redeployed from Earth-centered orbits to arrive in Earth-Moon Lissajous orbits in late 2010. Starting in August 2010, the ARTEMIS P1 spacecraft executed numerous stationkeeping maneuvers, initially maintaining a lunar L2 Lissajous orbit before transitioning into a lunar L1 orbit. The ARTEMIS P2 spacecraft entered a L1 Lissajous orbit in October 2010. In April 2011, both ARTEMIS spacecraft will suspend Lissajous stationkeeping and will be maneuvered into lunar orbits. The success of the ARTEMIS mission has allowed the science team to gather unprecedented magnetospheric measurements in the lunar Lissajous regions. In order to effectively perform lunar Lissajous stationkeeping maneuvers, the ARTEMIS operations team has provided orbit determination solutions with typical accuracies on the order of 0.1 km in position and 0.1 cm/s in velocity. The ARTEMIS team utilizes the Goddard Trajectory Determination System (GTDS), using a batch least squares method, to process range and Doppler tracking measurements from the NASA Deep Space Network (DSN), Berkeley Ground Station (BGS), Merritt Island (MILA) station, and United Space Network (USN). The team has also investigated processing of the same tracking data measurements using the Orbit Determination Tool Kit (ODTK) software, which uses an extended Kalman filter and recursive smoother to estimate the orbit. The orbit determination results from each of these methods will be presented and we will discuss the advantages and disadvantages associated with using each method in the lunar Lissajous regions. Orbit determination accuracy is dependent on both the quality and quantity of tracking measurements, fidelity of the orbit force models, and the estimation techniques used. Prior to Lissajous operations, the team determined the appropriate quantity of tracking measurements that would be needed to meet the required orbit determination accuracies. Analysts used the Orbit Determination Error Analysis System (ODEAS) to perform covariance analyses using various tracking data schedules. From this analysis, it was determined that 3.5 hours of DSN TRK-2-34 range and Doppler tracking data every other day would suffice to meet the predictive orbit knowledge accuracies in the Lissajous region. The results of this analysis are presented. Both GTDS and ODTK have high-fidelity environmental orbit force models that allow for very accurate orbit estimation in the lunar Lissajous regime. These models include solar radiation pressure, Earth and Moon gravity models, third body gravitational effects from the Sun, and to a lesser extent third body gravitational effects from Jupiter, Venus, Saturn, and Mars. Increased position and velocity uncertainties following each maneuver, due to small execution performance errors, requires that several days of post-maneuver tracking data be processed to converge on an accurate post-maneuver orbit solution. The effects of maneuvers on orbit determination accuracy will be presented, including a comparison of the batch least squares technique to the extended Kalman filter/smoother technique. We will present the maneuver calibration results derived from processing post-maneuver tracking data. A dominant error in the orbit estimation process is the uncertainty in solar radiation pressure and the resultant force on the spacecraft. An estimation of this value can include many related factors, such as the uncertainty in spacecraft reflectivity and surface area which is a function of spacecraft orientation (spin-axis attitude), uncertainty in spacecraft wet mass, and potential seasonal variability due to the changing direction of the Sun line relative to the Earth-Moon Lissajous reference frame. In addition, each spacecraft occasionally enters into Earth or Moon penumbra or umbra and these shadow crossings reduche solar radiation force for several hours. The effects of these events on orbit determination accuracy will be presented. In order to plan for upcoming stationkeeping maneuvers, the maneuver planning team must take the current orbit estimate, propagate it forward to the planned maneuver time, and determine the optimal maneuver to maintain the Lissajous orbit for one or more revolutions. The propagation is performed using a Runge-Kutta 7/8 integrator and typically the position and velocity uncertainty increases with propagation time, increasing the overall uncertainty of the orbit state at the maneuver execution time. The effect of orbit knowledge uncertainty on stationkeeping operations will be presented.

Woodard, Mark↗

An Integrated Gate Turnaround Management Concept Leveraging Big Data Analytics for NAS Performance Improvements

"Gate Turnaround" plays a key role in the National Air Space (NAS) gate-to-gate performance by receiving aircraft when they reach their destination airport, and delivering aircraft into the NAS upon departing from the gate and subsequent takeoff. The time spent at the gate in meeting the planned departure time is influenced by many factors and often with considerable uncertainties. Uncertainties such as weather, early or late arrivals, disembarking and boarding passengers, unloading/reloading cargo, aircraft logistics/maintenance services and ground handling, traffic in ramp and movement areas for taxi-in and taxi-out, and departure queue management for takeoff are likely encountered on the daily basis. The Integrated Gate Turnaround Management (IGTM) concept is leveraging relevant historical data to support optimization of the gate operations, which include arrival, at the gate, departure based on constraints (e.g., available gates at the arrival, ground crew and equipment for the gate turnaround, and over capacity demand upon departure), and collaborative decision-making. The IGTM concept provides effective information services and decision tools to the stakeholders, such as airline dispatchers, gate agents, airport operators, ramp controllers, and air traffic control (ATC) traffic managers and ground controllers to mitigate uncertainties arising from both nominal and off-nominal airport gate operations. IGTM will provide NAS stakeholders customized decision making tools through a User Interface (UI) by leveraging historical data (Big Data), net-enabled Air Traffic Management (ATM) live data, and analytics according to dependencies among NAS parameters for the stakeholders to manage and optimize the NAS performance in the gate turnaround domain. The application will give stakeholders predictable results based on the past and current NAS performance according to selected decision trees through the UI. The predictable results are generated based on analysis of the unique airport attributes (e.g., runway, taxiway, terminal, and gate configurations and tenants), and combined statistics from past data and live data based on a specific set of ATM concept-of-operations (ConOps) and operational parameters via systems analysis using an analytic network learning model. The IGTM tool will then bound the uncertainties that arise from nominal and off-nominal operational conditions with direct assessment of the gate turnaround status and the impact of a certain operational decision on the NAS performance, and provide a set of recommended actions to optimize the NAS performance by allowing stakeholders to take mitigation actions to reduce uncertainty and time deviation of planned operational events. An IGTM prototype was developed at NASA Ames Simulation Laboratories (SimLabs) to demonstrate the benefits and applicability of the concept. A data network, using the System Wide Information Management (SWIM)-like messaging application using the ActiveMQ message service, was connected to the simulated data warehouse, scheduled flight plans, a fast-time airport simulator, and a graphic UI. A fast-time simulation was integrated with the data warehouse or Big Data/Analytics (BAI), scheduled flight plans from Aeronautical Operational Control AOC, IGTM Controller, and a UI via a SWIM-like data messaging network using the ActiveMQ message service, illustrated in Figure 1, to demonstrate selected use-cases showing the benefits of the IGTM concept on the NAS performance.

Efficent ATM systems↗

Expedited Walkdowns and Preparation of Cost Estimates for Decontamination and Demolition of Excess Facilities - 20335

Lawrence Livermore National Security, LLC (LLNS) is the prime contractor responsible for managing and operating Lawrence Livermore National Laboratory (LLNL). The mission of the LLNL is to strengthen security of the United States through development and application of world-class science and technology to enhance the nation's defense, reduce the global threat from terrorism and weapons of mass destruction, and respond with vision, quality, integrity, and technical excellence to scientific issues of national importance. To accomplish its mission, LLNL must plan and manage its campus space and facilities to optimize use of its relatively small one-square-mile footprint. LLNL currently has numerous excess facilities that require decontamination and demolition (D and D). The LLNL Legacy Facility Program is responsible for stewardship and risk reduction programs to effectively manage these excess assets at LLNL. The Legacy Facility Program identified 10 excess facilities at LLNL that were candidates for demolition based on risks from further degradation of the facilities, potential exposure to hazardous materials, or need for removal to make way for new program facilities. The buildings range from a structure built in 1943 to serve as a US Navy drill hall during World War II, to a facility that provided neutrons to study material properties for the fusion energy program. The National Nuclear Security Administration (NNSA) appropriated FY19 funding for the development of Class 3 estimates for these 10 excess facilities that would be used to develop a Program Management Plan for funding consideration. Class 3 estimates are not conceptual, nor overly detailed, but adequate to be used for budget and appropriation purposes. Using existing strategic sourcing agreements, LLNL was able to organize a team of senior subject matter experts (SMEs) with diverse technical backgrounds across the Department of Energy (DOE) Complex to complete extensive process knowledge (PK) reviews and walk-downs of each excess facility and to deliver accurate and complete estimates under an expedited schedule (i.e., within eight weeks). To facilitate the expedited schedule, LLNL was fully prepared for the arrival of the JGMS team, which consisted of the following companies: J.G. Management Systems, Inc. (JGMS); Strata-G, LLC; and Michael Baker International. LLNL provided background and PK information on the excess facilities, pictures, supporting historical documentation, and radiological survey history as well as escorted access to the facilities. The JGMS team has previous experience supporting Program Management Plans for excess facilities at the Y-12 National Security Complex. The team mobilized to LLNL and performed the facility walk-downs from January 22-25, 2019. Using a methodical evaluation process, expertise, and experience, the team was able to deliver walk-down draft reports and estimates to LLNL before their February 8, 2019 deadline. LLNL then in turn reviewed, completed the estimates by adding waste management costs and other LLNL costs, and delivered the estimates to NNSA by February 15, 2019. The completed final reports, including draft D and D estimates, were delivered to LLNL before their March 6, 2019 deadline. The work was successfully completed ahead of the expedited schedule required by LLNL, resulting in a commendation from the client. This paper describes how the partnership and collaboration as a fully integrated team comprised of the prime contractor, LLNS, and the JGMS team successfully met the needs of the US government, resulting in the performance of expedited site walk-downs, the development of summary evaluation reports, and the preparation of draft Class 3 estimates and preliminary schedules for the D and D of 10 excess facilities at LLNL. The efforts of the team will enable the D and D of the first excess facility in the 2020-2021 time frame. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

First Results from NASA's Lunar Atmosphere and Dust Environment Explorer (LADEE)

As of early August, 2013, the Lunar Atmosphere and Dust Environment Explorer (LADEE) mission is scheduled for launch on a Minotaur V rocket from Wallops Flight Facility during a five-day launch period that opens on Sept. 6, 2013 (early Sept. 7 UTC). LADEE will address 40 year-old mysteries of the lunar atmosphere and the question of levitated lunar dust. It will also pioneer the next generation of optical space communications. LADEE will assess the composition of the lunar atmosphere and investigate the processes that control its distribution and variability, including sources, sinks, and surface interactions. LADEE will also determine whether dust is present in the lunar exosphere, and reveal its sources and variability. These investigations are relevant to our understanding of surface boundary exospheres and dust processes occurring at many objects throughout the solar system, address questions regarding the origin and evolution of lunar volatiles, and have potential implications for future exploration activities. Following a successful launch, LADEE will enter a series of phasing orbits, which allows the spacecraft to arrive at the Moon at the proper time and phase. This approach accommodates any dispersion in the Minotaur V launch injection. LADEE's arrival at the moon in early October. The spacecraft will approach the moon from its leading edge, travel behind the Moon out of sight of the Earth, and then re-emerge and execute a three-minute Lunar Orbit Insertion maneuver. This will place LADEE in an elliptical retrograde equatorial orbit with an orbital period of approximately 24 hours. A series of maneuvers is then performed to reduce the orbit to become nearly circular with a 156-mile (250- kilometer) altitude. Spacecraft checkout and science instrument commissioning will commence in early-October and will nominally span 30 days but can be extended for an additional 30 days in the event of contingencies. Following commissioning, the 100-day Science Phase is performed at an orbit with periapsis between 20-60 km. This orbit must be constantly managed due to the Moon's highly inhomogeneous gravity field. During the Science Phase, the moon will rotate more than three times underneath the LADEE orbit. LADEE employs a high heritage instrument payload: a Neutral Mass Spectrometer (NMS) from Goddard Space Flight Center, an Ultraviolet/Visible Spectrometer (UVS) from Ames Research Center, and a dust detection experiment (LDEX) from the University of Colorado/LASP. It will also carry the Lunar Laser Communications Demonstration (LLCD) as a technology demonstration. The LLCD is funded by the Human Exploration Operations Mission Directorate (HEOMD), managed by GSFC, and built by the MIT Lincoln Lab. Contingent upon LADEE's successful lunar orbit insertion and checkout, we will report the early results from the science investigations.

Moon↗

Verification of the Solar Dynamics Observatory High Gain Antenna Pointing Algorithm Using Flight Data

The Solar Dynamics Observatory (SDO) is a NASA spacecraft designed to study the Sun. It was launched on February 11, 2010 into a geosynchronous orbit, and uses a suite of attitude sensors and actuators to finely point the spacecraft at the Sun. SDO has three science instruments: the Atmospheric Imaging Assembly (AIA), the Helioseismic and Magnetic Imager (HMI), and the Extreme Ultraviolet Variability Experiment (EVE). SDO uses two High Gain Antennas (HGAs) to send science data to a dedicated ground station in White Sands, New Mexico. In order to meet the science data capture budget, the HGAs must be able to transmit data to the ground for a very large percentage of the time. Each HGA is a dual-axis antenna driven by stepper motors. Both antennas transmit data at all times, but only a single antenna is required in order to meet the transmission rate requirement. For portions of the year, one antenna or the other has an unobstructed view of the White Sands ground station. During other periods, however, the view from both antennas to the Earth is blocked for different portions of the day. During these times of blockage, the two HGAs take turns pointing to White Sands, with the other antenna pointing out to space. The HGAs handover White Sands transmission responsibilities to the unblocked antenna. There are two handover seasons per year, each lasting about 72 days, where the antennas hand off control every twelve hours. The non-tracking antenna slews back to the ground station by following a ground commanded trajectory and arrives approximately 5 minutes before the formerly tracking antenna slews away to point out into space. The SDO Attitude Control System (ACS) runs at 5 Hz, and the HGA Gimbal Control Electronics (GCE) run at 200 Hz. There are 40 opportunities for the gimbals to step each ACS cycle, with a hardware limitation of no more than one step every three GCE cycles. The ACS calculates the desired gimbal motion for tracking the ground station or for slewing, and sends the command to the GCE at 5 Hz. This command contains the number of gimbals steps for that ACS cycle, the direction of motion, the spacing of the steps, and the delay before taking the first step. The AIA and HMI instruments are sensitive to spacecraft jitter. Pre-flight analysis showed that jitter from the motion of the HGAs was a cause of concern. Three jitter mitigation techniques were developed to overcome the effects of jitter from different sources. The first method is the random step delay, which avoids gimbal steps hitting a cadence on a jitter-critical mode by pseudo-randomly delaying the first gimbal step in an ACS cycle. The second method of jitter mitigation is stagger stepping, which forbids the two antennas from taking steps during the same ACS cycle in order to avoid constructively adding jitter from two antennas. The third method is the inclusion of an instrument No Step Request (NSR), which allows the instruments to request a stoppage in gimbal stepping during the times when they are taking images. During the commissioning phase of the mission, a jitter test was performed onboard the spacecraft. Various sources of jitter, such as the reaction wheels, the High Gain Antenna motors, and the motion of the instrument filter wheels, were examined to determine the level of their effect on the instruments. During the HGA portion of the test, the jitter amplitudes from the single step of a gimbal were examined, as well as the amplitudes due to the execution of various gimbal rates. These jitter levels are compared with the gimbal jitter allocations for each instrument. Additionally, the jitter test provided insight into a readback delay that exists with the GCE. Pre-flight analysis suggested that gimbal steps scheduled to occur during the later portion of an ACS cycle would not be read during that cycle, resulting in a delay in the telemetered current gimbal position. Flight data from the jitter test confirmed this expectation. Analysis is presentehat shows the readback delay does not have a negative impact on gimbal control. The decision was made to consider implementing two of the jitter mitigation techniques on board the spacecraft: stagger stepping and the NSR. Flight data from two sets of handovers, one set without jitter mitigation and the other with mitigation enabled, were examined. The trajectory of the predicted handover was compared with the measured trajectory for the two cases, showing that tracking was not negatively impacted with the addition of the jitter mitigation techniques. Additionally, the individual gimbal steps were examined, and it was confirmed that the stagger stepping and NSRs worked as designed. An Image Quality Test was performed to determine the amount of cumulative jitter from the reaction wheels, HGAs, and instruments during various combinations of typical operations. In this paper, the flight results are examined from a test where the HGAs are following the path of a nominal handover with stagger stepping on and HMI NSRs enabled. In this case, the reaction wheels are moving at low speed and the instruments are taking pictures in their standard sequence. The flight data shows the level of jitter that the instruments see when their shutters are open. The HGA-induced jitter is well within the jitter requirement when the stagger step and NSR mitigation options are enabled. The SDO HGA pointing algorithm was designed to achieve nominal antenna pointing at the ground station, perform slews during handover season, and provide three HGA-induced jitter mitigation options without compromising pointing objectives. During the commissioning phase, flight data sets were collected to verify the HGA pointing algorithm and demonstrate its jitter mitigation capabilities.

Bourkland, Kristin L.↗

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↗