Search NASA⌕ Search

SEARCH · Search NASA

Results for “command generation process”

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.

296 records · Page 17

MUSTANG: A Workhorse for NASA Spaceflight Avionics

The Modular Unified Space Technology Avionics for Next Generation (MUSTANG) is a small integrated Avionics system including Command and Data Handling (C&DH), Power System Electronics (PSE), Attitude Control System Interfaces (ACS), and Propulsion Electronics. The MUSTANG Avionics Architecture is built upon many years of knowledge capture and lessons learned at the Goddard Space Flight Center. With a motivation towards modularity and keeping board redesign costs to a minimum, MUSTANG offers flexibility in features with a backplane-less design and allows the user to choose the options (cards) needed for their system. It incorporates a distributed power system that provides secondary power to all its subcomponents reducing the number of primary services needed for an Avionics. MUSTANG can be integrated into one system or divided into several smaller components. MUSTANG supports redundancy and cross-strap ability for a more robust and reliable Avionics system. A variation of MUSTANG exists for Instrument Electronics called iMUSTANG and allows the user to select functionality applicable to the instrument electronics. MUSTANG is not meant to replace Avionics for all spacecraft. There are limitations due to its relatively compact size, but the MUSTANG design has proven broadly applicable on many spacecraft and instrument bus avionics architectures.

MUSTANG↗

Motor adaptation to Coriolis force perturbations of reaching movements: endpoint but not trajectory adaptation transfers to the nonexposed arm

1. Reaching movements made in a rotating room generate Coriolis forces that are directly proportional to the cross product of the room's angular velocity and the arm's linear velocity. Such Coriolis forces are inertial forces not involving mechanical contact with the arm. 2. We measured the trajectories of arm movements made in darkness to a visual target that was extinguished at the onset of each reach. Prerotation subjects pointed with both the right and left arms in alternating sets of eight movements. During rotation at 10 rpm, the subjects reached only with the right arm. Postrotation, the subjects pointed with the left and right arms, starting with the left, in alternating sets of eight movements. 3. The initial perrotary reaching movements of the right arm were highly deviated both in movement path and endpoint relative to the prerotation reaches of the right arm. With additional movements, subjects rapidly regained straight movement paths and accurate endpoints despite the absence of visual or tactile feedback about reaching accuracy. The initial postrotation reaches of the left arm followed straight paths to the wrong endpoint. The initial postrotation reaches of the right arm had paths with mirror image curvature to the initial perrotation reaches of the right arm but went to the correct endpoint. 4. These observations are inconsistent with current equilibrium point models of movement control. Such theories predict accurate reaches under our experimental conditions. Our observations further show independent implementation of movement and posture, as evidenced by transfer of endpoint adaptation to the nonexposed arm without transfer of path adaptation. Endpoint control may occur at a relatively central stage that represents general constraints such as gravitoinertial force background or egocentric direction relative to both arms, and control of path may occur at a more peripheral stage that represents moments of inertia and muscle dynamics unique to each limb. 5. Endpoint and path adaptation occur despite the absence both of mechanical contact cues about the perturbing force and visual or tactile cues about movement accuracy. These findings point to the importance of muscle spindle signals, monitoring of motor commands, and possibly joint and tendon receptors in a detailed trajectory monitoring process. Muscle spindle primary and secondary afferent signals may differentially influence adaptation of movement shape and endpoint, respectively.

Non-NASA Center↗

Joint Test Plan for Gas Dynamic Spray Technology Demonstration

Air Force Space Command (AFSPC) and NASA have similar missions, facilities, and structures located in similar harsh environments. Both are responsible for a number of facilities/structures with metallic structural and non-structural components in highly and moderately corrosive environments. Regardless of the corrosivity of the environment, all metals require periodic maintenance activity to guard against the insidious effects of corrosion and thus ensure that structures meet or exceed design or performance life. The standard practice for protecting metallic substrates in atmospheric environments is the use of an applied coating system. Current coating systems used across AFSPC and NASA contain volatile organic compounds (VOCs) and hazardous air pollutants (HAPs). These coatings are subject to environmental regulations at the Federal and State levels that limit their usage. In addition, these coatings often cannot withstand the high temperatures and exhaust that may be experienced by AFSPC and NASA structures. In response to these concerns, AFSPC and NASA have approved the use of thermal spray coatings (TSCs). Thermal spray coatings are extremely durable and environmentally friendly coating alternatives, but utilize large cumbersome equipment for application that make the coatings difficult and time consuming to repair. Other concerns include difficulties coating complex geometries and the cost of equipment, training, and materials. Gas Dynamic Spray (GDS) technology (also known as Cold Spray) will be evaluated as a smaller, more maneuverable repair method as well as for areas where thermal spray techniques are not as effective. The technology can result in reduced maintenance and thus reduced hazardous materials/wastes associated with current processes. Thermal spray and GDS coatings also have no VOCs and are environmentally preferable coatings. To achieve a condition suitable for the application of a coating system, including GDS coatings, the substrate must undergo some type of surface preparation and/or depainting operation to ensure adhesion of the new coating system. The GDS unit selected for demonstration has a powder feeding system that can be used for surface preparation or coating application. The surface preparation feature will also be examined. The primary objective of this effort is to demonstrate GDS technology as a repair method for TSCs. The project will also determine the optimal GDS coating thickness for acceptable performance. Successful completion of this project will result in approval of GDS technology as a repair method for TSCs at AFSPC and NASA installations and will improve corrosion protection at critical systems, facilitate easier maintenance activity, extend maintenance cycles, eliminate flight hardware contamination, and reduce the amount of hazardous waste generated.

Lewis, Pattie↗

Next Generation Flight Displays Using HTML5

The Human Integrated Vehicles and Environments (HIVE) lab at Johnson Space Center (JSC) is focused on bringing together inter-disciplinary talent to design and integrate innovative human interface technologies for next generation manned spacecraft. As part of this objective, my summer internship project centered on an ongoing investigation in to building flight displays using the HTML5 standard. Specifically, the goals of my project were to build and demo "flight-like" crew and wearable displays as well as create a webserver for live systems being developed by the Advanced Exploration Systems (AES) program. In parallel to my project, a LabVIEW application, called a display server, was created by the HIVE that uses an XTCE (XML (Extensible Markup Language) Telemetry and Command Exchange) parser and CCSDS (Consultative Committee for Space Data System) space packet decoder to translate telemetry items sent by the CFS (Core Flight Software) over User Datagram Protocol (UDP). It was the webserver's job to receive these UDP messages and send them to the displays. To accomplish this functionality, I utilized Node.js and the accompanying Express framework. On the display side, I was responsible for creating the power system (AMPS) displays. I did this by using HTML5, CSS and JavaScript to create web pages that could update and change dynamically based on the data they received from the webserver. At this point, I have not started on the commanding, being able to send back to the CFS, portion of the displays but hope to have this functionality working by the completion of my internship. I also created a way to test the webserver's functionality without the display server by making a JavaScript application that read in a comma-separate values (CSV) file and converted it to XML which was then sent over UDP. One of the major requirements of my project was to build everything using as little preexisting code as possible, which I accomplished by only using a handful of JavaScript libraries. As a side project, I created a model of the HIVE lab and Building 29 using SketchUp. I obtained the floorplans of the building from the JSC Geographic Information Systems (GIS), which were computer-aided design (CAD) files, and imported them into SketchUp. I then took those floorplans and created a 3D model of the building from them. Working in conjunction with the Hybrid Reality lab in Building 32, the SketchUp model was imported into Unreal Engine for use with the HTC Vive. Using the Vive, I was able to interact with the model I created in virtual reality (VR). The purpose of this side project was to be able to visualize potential lab layouts and mockup designs as they are in development in order to finalize design decisions. Pending approval, the model that I created will be used in the Build-As-You-Test: Can Hybrid Reality Improve the SE/HSI Design Process project in the fall. Getting the opportunity to work at NASA has been one of the most memorable experiences of my life. Over the course of my internship, I improved my programming and web development abilities substantially. I will take all the skills and experiences I have had while at NASA back to school with me in the fall and hope to pursue a career in the aerospace industry after graduating in the spring.

Greenwood, Brian↗

Modeling in the State Flow Environment to Support Launch Vehicle Verification Testing for Mission and Fault Management Algorithms in the NASA Space Launch System

Analysis methods and testing processes are essential activities in the engineering development and verification of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS). Central to mission success is reliable verification of the Mission and Fault Management (M&FM) algorithms for the SLS launch vehicle (LV) flight software. This is particularly difficult because M&FM algorithms integrate and operate LV subsystems, which consist of diverse forms of hardware and software themselves, with equally diverse integration from the engineering disciplines of LV subsystems. M&FM operation of SLS requires a changing mix of LV automation. During pre-launch the LV is primarily operated by the Kennedy Space Center (KSC) Ground Systems Development and Operations (GSDO) organization with some LV automation of time-critical functions, and much more autonomous LV operations during ascent that have crucial interactions with the Orion crew capsule, its astronauts, and with mission controllers at the Johnson Space Center. M&FM algorithms must perform all nominal mission commanding via the flight computer to control LV states from pre-launch through disposal and also address failure conditions by initiating autonomous or commanded aborts (crew capsule escape from the failing LV), redundancy management of failing subsystems and components, and safing actions to reduce or prevent threats to ground systems and crew. To address the criticality of the verification testing of these algorithms, the NASA M&FM team has utilized the State Flow environment6 (SFE) with its existing Vehicle Management End-to-End Testbed (VMET) platform which also hosts vendor-supplied physics-based LV subsystem models. The human-derived M&FM algorithms are designed and vetted in Integrated Development Teams composed of design and development disciplines such as Systems Engineering, Flight Software (FSW), Safety and Mission Assurance (S&MA) and major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GN&C), Thrust Vector Control (TVC), liquid engines, and the astronaut crew office. Since the algorithms are realized using model-based engineering (MBE) methods from a hybrid of the Unified Modeling Language (UML) and Systems Modeling Language (SysML), SFE methods are a natural fit to provide an in depth analysis of the interactive behavior of these algorithms with the SLS LV subsystem models. For this, the M&FM algorithms and the SLS LV subsystem models are modeled using constructs provided by Matlab which also enables modeling of the accompanying interfaces providing greater flexibility for integrated testing and analysis, which helps forecast expected behavior in forward VMET integrated testing activities. In VMET, the M&FM algorithms are prototyped and implemented using the same C++ programming language and similar state machine architectural concepts used by the FSW group. Due to the interactive complexity of the algorithms, VMET testing thus far has verified all the individual M&FM subsystem algorithms with select subsystem vendor models but is steadily progressing to assessing the interactive behavior of these algorithms with LV subsystems, as represented by subsystem models. The novel SFE applications has proven to be useful for quick look analysis into early integrated system behavior and assessment of the M&FM algorithms with the modeled LV subsystems. This early MBE analysis generates vital insight into the integrated system behaviors, algorithm sensitivities, design issues, and has aided in the debugging of the M&FM algorithms well before full testing can begin in more expensive, higher fidelity but more arduous environments such as VMET, FSW testing, and the Systems Integration Lab7 (SIL). SFE has exhibited both expected and unexpected behaviors in nominal and off nominal test cases prior to full VMET testing. In many findings, these behavioral characteristics were used to correct the M&FM algorithms, enable better test coverage, and develop more effective test cases for each of the LV subsystems. This has improved the fidelity of testing and planning for the next generation of M&FM algorithms as the SLS program evolves from non-crewed to crewed flight, impacting subsystem configurations and the M&FM algorithms that control them. SFE analysis has improved robustness and reliability of the M&FM algorithms by revealing implementation errors and documentation inconsistencies. It is also improving planning efficiency for future VMET testing of the M&FM algorithms hosted in the LV flight computers, further reducing risk for the SLS launch infrastructure, the SLS LV, and most importantly the crew.

Trevino, Luis↗

VERNE: Revealing the Mysteries and Histories of Venus

Introduction: The three Venus missions that were recently selected for upcoming flight (VERITAS, DAVINCI+, and EnVision) will be incredibly valuable to our understanding of Venus’ history, geology, and atmosphere. However, even once completed, key gaps in our knowledge of Venus, and more generally the formation and active processes on rocky, Earth-like planets, will still persist. Remaining questions include 1) how global intrinsic magnetic fields might be maintained on rocky worlds, and how they could then go extinct, and 2) what role atmospheric sulfur chemistry plays in climates of Earth-like planets, which is an increasingly timely subject as Earth’s own atmospheric sulfur content is climbing due to human activity. These questions require in-situ observations from Venus’ cloud deck, at the altitudes at which the UV absorber exists. The Venus Environment Research and Novel Exploration (VERNE) mission will address these questions with an aerial platform that will drift around the equatorial region of the planet for 9 days. VERNE will collect data to determine the identity of the mysterious UV absorber, while also taking magnetic field measurements over the tesserae, the regions on Venus that are most likely to retain remanent crustal magnetization, in order to understand the potential role of a past intrinsically-generated global magnetic field on Venus. Mission Objectives: The two major science objectives that drive the VERNE mission are: 1) Determine the identity of the Venusian unknown ultraviolet absorber(s). First observed approximately a century ago [1], the composition of Venus’ ultraviolet (UV) absorber is one of the oldest mysteries in Venus atmospheric chemistry [2,3]. While several candidate UV absorbers (mostly sulfur species) have been proposed, no consensus has been reached on its composition and its specific interactions with the atmosphere. Determining the identity of the UV absorber will aid climate models by showing how and where incident solar energy is absorbed by the atmosphere and make progress towards understanding the chemical and energetic processes taking place above Venus’ upper cloud deck [4]. 2) Determine if Venus retains evidence of a past, internally-generated magnetic field. While Venus does not currently have an intrinsically-generated magnetic field, evidence for the existence of a past field on Venus and a timeline of its decay will fill in a more holistic picture of the evolution of Venus’ geological record and atmosphere. As the oldest geologic units on the surface, Venus’ tesserae may still have remanent crustal magnetization signatures within the rocky composition [5]. In any case, the signatures detected will provide insight into Venus’ past geological and core dynamo activity. Mission Summary: VERNE includes a 3-part flight system made up of 1) an entry system with a HEEET (Heatshield for Extreme Entry Environment Technology) aeroshell, 2) an orbiter for data relay, and 3) an in-situ balloon and gondola. After entry into Venus’ atmosphere, the balloon will be deployed within the upper cloud deck, at an altitude of 62 km, over a tesserae region. The in-situ data collection will last for the duration of 2 full circumnavigations of the planet, which will take ~9 days. Instrumentation Suite: The four instruments that comprise VERNE’s instrument payload will enable the identification of the unknown UV absorber and the detection of remanent crustal magnetization if it exists in the tesserae. The proposed instrument suite cycle during mission operations is shown in Fig. 1. The four instruments are described below: 1) Adams (ion neutral mass spectrometer) has a range of 18-257 AMU and will detect and distinguish the mixing ratios of O₂, H₂O, H₂SO₄, S, S₂, S₃, S₄, S₅, S₆, S₇, S₈, SO, SO₂, OSSO, SO₃, Cl₂, FeCl₃ and other trace sulfur and organic species. The spatial (longitudinal) and temporal (day/night) variations will be observed throughout 2 circumnavigations with a sample cadence of 12 minutes. 2) Shelley (nephelometer) will determine the size distribution of the aerosols (0.4 to 36 um) in the atmosphere. With a size resolution of <0.7 um, it can determine which mode of H2SO4 is present and characterize the large (>30 um) organic particles previously detected by the Venera and Galileo missions [6,7]. 3) Herbert (UV imager) will measure UV radiance at 283 nm (the wavelength of SO2 absorption) and 365 nm (the unknown part of the absorber). UV images will be taken concurrently with the INMS and nephelometer to correlate UV absorption with abundances of the UV absorber species. 4) Vonnegut (magnetometer) has a range of >600 nT and a precision and accuracy of 1 nT. If magnetized by a past field, the crust may have retained a magnetization of up to 3 A/m2 [5]. With a noise floor of 10 nT, the magnetometer will be able to detect RCM from an altitude of 62 km, even if the thickness of the magnetized crust is just 1 km (Fig. 2). Mission Concept Design: VERNE will be launched with a mass of 3300 kg in an intermediate-high performance class vehicle with a 4-m fairing. The 475-day mission includes 466 days for the cruise, coasting, and orbit initialization phases before entry, descent, and balloon deployment. During the 9-day science phase, the aerial platform will make 2 circumnavigations of the planet at an altitude of 62 km. The INMS and the nephelometer will acquire data for 2 hours during the daytime and nighttime during each circumnavigation, while the UV imager will be on for the duration of the daytime, and the magnetometer will be operational throughout the entirety of the science phase. Data will be stored and processed with the JPL-designed Sphinx command and data handling system. Data will be sent from the balloon to the orbiter using an S-band relay link, stored on the orbiter, and then forwarded to Earth where it will be received by the DSN. Conclusion: VERNE will fill key gaps in our understanding of the history and ongoing processes related to the geology and atmosphere of Venus and rocky worlds in general. Even with adequate flight system contingencies and expected costs below the $900M New Frontiers cost cap, VERNE is not without its risks and challenges. Further trade spaces to explore include 1) using solely battery power vs. including solar panels to increase the mission duration and 2) investigating the use of lightweight materials and 3D-printed structures to reduce the gondola mass, among others. Acknowledgments: We would like to thank the JPL Planetary Science Summer School, especially our mentors Troy Hudson, Karl Mitchell, and Leslie Lowes, as well as our Team-X study lead Al Nash and the members of Team-X. We’d additionally like to thank our review panel for asking insightful questions and providing valuable feedback. References: [1] Ross, F. E. (1928) Astrophysical J., 68, 57-92. [2] Rossow, W. B. et al. (1980) J. Geophysical Research, 85, 8107-8128. [3] Pinto, J. P. et al. (2021) Nature Communications, 12, 175. [4] Titov, D. V. et al. (2007) Cosmic Research, 21, 401. [5] O’Rourke, J. et al. (2019) Geophysical Research Lett., 46, 5768–5777. [6] Limaye, S. S. et al. (2018) Astrobiology, 18(9), 1181-1198. [7] Grinspoon, D. H. et al. (2013) Planetary and Space Sci., 41(7), 515-542. [8] Parker, R. L. (2003) J. Geophysical Research, 108, 5006. *The cost information contained in this document is of a budgetary and planning nature and is intended for informational purposes only. It does not constitute a commitment on the part of JPL and/or Caltech.

H Alpert↗

The Utilization Profiles of the CCSDS Unified Space Link Protocol (USLP)

The purpose of this paper is to identify the utilization profiles for interfacing the Data Protocol Sublayer using the Unified Space Link Protocols (USLP) (reference 1) with the space link coding procedures as specified in the CCSDS Coding & Synchronization Blue Books (references 2 through 5), used in both telecommand and telemetry applications. This paper describes how the USLP Protocol utilizes the coding and synchronization sublayer to support: a. Direct to Earth (DTE) telemetry links for engineering and science data b. Direct to Earth (DTE) telemetry links for very high rate science data c. Direct from Earth (DFE) command, sequencing and flight software loads d. Space to Space Links (Proximity) utilized by orbiters for data exchange to/from surface bound assets. The CCSDS has divided the functions of the Data Link Layer into two sublayers: the Data Link Protocol Sublayer (DLP-SL) and the Coding and Synchronization Sublayer (CS-SL). The Data Link Protocol Sublayer (DLP-SL) interfaces to the users, accepting the data that is to be transported, on the sending side of the link, and delivering that data on the receiving end. The Transfer Frame is the data unit that is transferred across the Data Link Protocol Sublayer and the Coding and Synchronization Sublayer boundary. The Coding and Synchronization Sublayer (CS-SL) provides the encoding, randomization, and frame synchronization functions that prepares the USLP Transfer Frame for transport across the space link. The CS-SL is divided into 2 processes: 1) The Frame Interface Processes (FIP) performs the interface functions required to prepare the data for delivery to the Coding/Decoding Process (CDP). This process includes prepending a Frame Start Marker to the provided frame, when management has designated that the frame is not to be aligned to the codeblock or when there is no block code used. 2) The Coding/Decoding Process (CDP) performs the forward error correction processes that are used to optimize the performance of the link and minimize the error rate. The CDP creates the symbol stream that is delivered to the Physical Layer. The transfer of the USLP transfer frames across different types of space links is the focus of this paper. The Protocol Data Unit (PDU) that is passed in both directions between the Data Link Protocol Sublayer (DLP-SL) and Coding and Synchronization Sublayer (CS-SL) is the transfer frame. The USLP frame structure provides flexibility that can be constrained by the functions utilized within the CS-SL that prepare the transfer frame for transit. For example, the USLP transfer frame contains a length field that enables the frame to be of variable length but CS-SL under certain conditions may constrain the frame to be fixed in length. This paper describes 5 operational modes available for use by the Data Link Layer to provide data exchange across the USLP space link. These modes are different because different operational requirements apply to vastly different types of space links and thus the communications implementation requirements differ. The environmental issues include the power or energy available, the distance between the end points of the link, the complexity of the equipment available at those end points, the atmospheric conditions and radiometric frequency selection. The CS-SL utilizes different forward error correcting codes supported by specific operational modes to configure the data for transit. This paper describes all of the operational modes in a series of data models which decompose the functionality between the Data Link Protocol Sublayer and the Coding and Synchronization sublayer. The operational modes described are: 1. Uncoded Mode: has been used for short links that contain significant available power to provide an acceptable frame error rate. The frames in this mode can be variable in length and typically use an error detection algorithm (i.e., CRC) to determine if there are errors in the received frame. 2. Convolutional Only Mode: is currently the prime forward error correction coding used for the proximity links. The frames in this mode can be variable in length and typically use an error detection algorithm (i.e., CRC) to determine if there are errors in the received frame. 3. Variable Length Frame Aligned to Variable Length Codeblock (TC): is used for Direct from Earth links were power levels are high and the simple, least complex code i.e., the BCH code is used. This mode has been in use since the early 1970s. The BCH code is a short code and the decoder is easy to implement. 4. Fixed Length Frame Aligned to Fixed Length Codeblock (AOS/TM): was introduced when the concatenated Convolutional and Reed-Solomon Code was formulated to provide significant reduction in link data error rate and the ability to determine if there was an error in the decoded codeblock. The frame is aligned to the codeblock so that there is a one to one relationship of frame errors to codeblock errors without additional error detection coding being added. This mode requires the protocol frames to be the exact size of the message portion of the codeblock. 5. Frames Unaligned to Fixed Length Codeblocks (Currently used for very high rates and space to space links): This mode is currently used for missions that have a very high data rate that can be controlled adaptively as the environment changes and as the next generation operating mode for the proximity link. This mode from a coded data stream point of view is exactly like that described in 4. above, except that the frame need not be aligned to the codeblock. There is no requirement on frame length when using this mode. Thus when using USLP it can be used to support links that require short or long frames. There is also no mandatory requirement that frames cannot be separated by idle data reducing the tight data rate connection requirements between the data link protocol sublayer and the coding & synchronization sublayer. In conclusion, how these operational modes can be put to use in mission operational scenarios is described for Direct from Earth links (DFE), Direct to Earth links (DTE), and Proximity links.

Greenberg, E.↗

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↗