Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “actual”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 1,045 records · Page 58

Mars 2020 Perseverance trajectory reconstruction and performance from launch through landing

The Mars 2020 (M2020) Mission carrying Perseverance, the most advanced rover ever sent to Mars, successfully launched on an Atlas V 541 (AV-088) launch vehicle from the Eastern Test Range (ETR) at Cape Canaveral Air Force Station (CCAFS) in Florida at 11:50:00 UTC (T-Zero time) on July 30, 2020. After some station reconfiguration, carrier/telemetry were locked at both Deep Space Network (DSN) Canberra and Goldstone stations. Perseverance entered the Martian atmosphere at 20:36:50 Spacecraft Event Time (SCET) UTC, and landed inside Jezero Crater at 20:43:49 SCET UTC on February 18, 2021. Confirmation of nominal landing was received at the DSN Goldstone and Madrid tracking stations via the Mars Reconnaissance Orbiter at 20:55:11 Earth Received Time (ERT) UTC. This paper summarizes in detail the actual vs. predicted performance in terms of launch vehicle events, launch vehicle injection performance, actual DSN spacecraft lockup, trajectory correction maneuver performance, Entry, Descent, and Landing events, and overall trajectory and geometric characteristics.

Abilleira, Fernando↗

Historical “Duration of Use” Power Figure Research and Update

Compared to actual demonstrated mission usage, boundaries in recent historical figures were much higher than actual required levels, especially for primary batteries, fuel cells, and dynamic RPS. Boundaries for solar and static RPS architectures remained mostly unchanged. Beyond looking only at demonstrated mission performance, current funded programs that would change the boundaries further were also considered. Considering these programs, boundaries for primary batteries, solar, and dynamic RPS do increase modestly. The investigation of the power level versus distance (AU) revealed the most practical locations of use for each architecture. Fuel cell use has been concentrated around earth’s orbit as they provide high power levels for shorter duration. Solar has been demonstrated from very close to the Sun out to Jupiter as solar power generation levels begin to dissipate. Primary batteries have been demonstrated in numerous probes from Venus out to Saturn. Finally, static RPS systems have traveled from Venus out past 150 AU outside the solar system. Considering current funded programs, power levels for solar do increase at Earth and Jupiter. The investigation of the historical power level change over time revealed that early assumed chemical power levels were quite high compared to current projections. Solar power sources appear to have matured over time and seem to have increased as chemical decreased. Static RPS systems have remained relatively stable since their introduction.

Marc R Hayhurst↗

Predicting contamination accumulation in facilities with limited data

In preparation for the James Webb Space Telescope (JWST) launch at Centre Spatial Guyanias (CSG) in French Guiana, particulate contamination accumulation predictions were necessary for each facility in which the hardware would be exposed because the Telescope would be uncovered in each of the facilities and had strict particulate requirements. These included facilities for final integration and testing, fueling, transportation and encapsulation. Minimal heritage data existed from CSG and previous launch campaigns to use as a basis for contamination predictions. Data from the Automatic Transfer Vehicle and Herschel & Planck launch campaigns were used in conjunction with facility monitoring data provided by ESA and data collected during JWST working group visits to CSG. These campaigns were conducted at varying cleanliness levels that were typically less stringent than JWST requirements. Each facility was evaluated using the data provided and likely performance improvement with the addition of High Efficiency Particulate Air filter (HEPA) banks operating when possible. Once the launch campaign was completed, the predicted fallout was compared with actual data collected throughout the campaign. Based on the actual measurements, JWST’s primary and secondary mirrors turned out to be much cleaner than what was predicted.

James Webb Space Telescope, contamination, cleanro↗

Predicting contamination accumulation in facilities with limited data

"In preparation for the James Webb Space Telescope (JWST) launch at Centre Spatial Guyanias (CSG) in French Guiana, particulate contamination accumulation predictions were necessary for each facility in which the hardware would be exposed because the Telescope would be uncovered in each of the facilities and had strict particulate requirements. These included facilities for final integration and testing, fueling, transportation and encapsulation. Minimal heritage data existed from CSG and previous launch campaigns to use as a basis for contamination predictions. Data from the Automatic Transfer Vehicle and Herschel & Planck launch campaigns were used in conjunction with facility monitoring data provided by ESA and data collected during JWST working group visits to CSG. These campaigns were conducted at varying cleanliness levels that were typically less stringent than JWST requirements. Each facility was evaluated using the data provided and likely performance improvement with the addition of High Efficiency Particulate Air filter (HEPA) banks operating when possible. Once the launch campaign was completed, the predicted fallout was compared with actual data collected throughout the campaign. Based on the actual measurements, JWST’s primary and secondary mirrors are likely much cleaner than was expected with the predicted fallout in each facility. "

James Webb Space Telescope, contamination, cleanro↗

Spectral Evolution of Dark Asteroid Surfaces Induced by Space Weathering Over a Decade

The surfaces of airless bodies like asteroids in the solar system are known to be affected by space weathering. Experiments simulating space weathering are essential for studying the effects of this process on meteorite samples, but the problem is that the time spent to reproduce space weathering in these experiments is billions of times shorter than the actual phenomenon. In 2010 December, the T-type asteroid 596 Scheila underwent a collision with an impactor a few tens of meters in size. A decade later, there is an opportunity to study how the surface layer of this asteroid is being altered by space weathering after the impact. To do so, we performed visible spectrophotometric and near-infrared spectroscopic observations of 596 Scheila. The acquired spectrum is consistent with those observed shortly after the 2010 impact event within the observational uncertainty range. This indicates that the surface color of dark asteroids is not noticeably changed by space weathering over a 10 yr period. This study is the first to investigate color changes due to space weathering on an actual asteroid surface in the solar system. Considering that fresh layers are regularly created on asteroid surfaces by collisions, we suggest a genetic link between D/T-type and dark (low albedo) X-complex asteroids and very red objects such as 269 Justitia, 732 Tjilaki, and 203 Pompeja. New observations show that 203 Pompeja has an X-type-like surface, with some local surface areas exhibiting a very red spectrum.

Sunao Hasegawa↗

ETM Industry: Tabletop Defining Notions for Cooperative Operating Practices

This tabletop plans to cover 3 main topics in regards to the research that NASA has conducted for High-E Traffic Management (ETM), as well as implementing it to stand up an ETM system in the Airspace Operations Lab to invite industry participants to join us in a collaborative evaluation at the end of 2023. (Or earlier for system architectural connectivity). Working to define the notions that go into Cooperative Operating Practices for a collaborative traffic management process, we will be showing and training to some of our early prototype concepts and discussing: 1. Operational Intent: We have built an OI generation tool and would like to discuss specifics to the requirements of OI size, update rates, and duration. 2. Strategic Conflict Detection: We have built a concept to detect overlapping OI’s and would like to discuss the output information; time horizon, geometry and confidence level of intersection. In addition we are looking at a service that would provide all users with additional information in regards to the probability of your actual flight intent getting within a specified separation envelope. 3. Cooperative Operating Practices (COPS): Specifically looking at COPs for strategic deconfliction, we are looking to industry to build the actual COPS based on various criteria; vehicle-to-vehicle interactions, or company to company agreements. What is the strategy when OIs intersect; wait and see, take a pre-negotiated COPS action, or ad-hoc negotiation and discuss what that looks like.

High-E Traffic Management (ETM)↗

Conjunction Assessment and Deconfliction Paradigm for Co-Located Satellite Constellations With on-Spacecraft “Autonomous” Flight Dynamics Control

Satellite constellations that employ on-spacecraft flight dynamics and conjunction assessment (CA) approaches face particular challenges. First, they must arrange to obtain and upload to the constellation satellite close approach information, such as Conjunction Data Messages, so that their on-board systems will have the data they need to make informed CA decisions. Second, given current latencies in obtaining CA screening information, such systems often cannot obtain dedicated screenings of their proposed maneuvers before they are executed. Third, they usually cannot engage in real time with owner/operators (O/Os) with whom they may come into conjunction, relying instead on pre-arranged courses of action that may or may not fit a given situation well. Despite these difficulties, it is nonetheless possible, as operators such as SpaceX have demonstrated, to operate safely using on-board CA calculations, in the presence of a largely collaborative operating environment. The situation breaks down, however, when two constellations that operate with such a paradigm are placed in the same orbital region and will experience conjunctions with each other. Each may have a vague idea of where the other’s satellites are, or perhaps even a somewhat precise idea if they exchange O/O ephemerides, but neither will know the other’s more immediate maneuver intentions, especially for situations in which they are in a high-risk conjunction with each other and a mitigation maneuver is required. As there is no formalized way for these automated systems to ascertain each other’s intentions for this type of conjunction, it is quite possible that each spacecraft may choose a maneuver that results in the two objects’ colliding. An opportunity to develop a solution to this problem was presented by the NASA “Starling” project, a small experimental constellation developed to demonstrate autonomous satellite control and constellation reconfiguration and for which a launch was obtained that, serendipitously, will place this constellation close to the SpaceX Starlink constellation. Because the NASA constellation is experimental, an extended mission part of the mission has been negotiated to implement and test mechanisms for resolving the problem of co-located constellations with on-board flight dynamics control. For the last eighteen months, a consortium among NASA Ames (the Starling satellite providers), NASA CARA (the Agency organization responsible for conjunction assessment), Space X, and the Department of Commerce (in observer status) has met regularly to assemble a concept of operations for a robust solution to this problem and has developed a prototype ground node that will serve as a needed CA screening and information dispensary. The approach and methods, as well as the active employment of the developed ground node, will be tested both in simulation before actual use and then in actual spacecraft operations, which are anticipated to begin in January 2024. This paper will describe the co-located autonomously-controlled constellation problem and the developed solution in detail, outlining what ground node (i.e., government) infrastructure and features are required, what particular capabilities are needed by the constellations themselves in order to make use of this deconfliction paradigm, and the migration path forward to allow such a capability set to be incorporated by the Department of Commerce’s space traffic coordination system.

Conjunction Assessment↗

Should’ve Could’ve: Progress in the Systems Engineering of the Mars2020 On-Board Planner

Mars rover operations has traditionally controlled behavior using meticulously compiled, so-called “Master” sequences that enforce deterministic timing and ordering of activities. While the approach is effective at managing risk and complexity, it can also be inefficient. Extended operations of the Mars2020 rover envisions a fundamentally different scheduling and execution approach. Atomic activities are constrained by mission operators in time, resource usage, and a structure of dependencies. The rover flight software will create and re-create schedules, responding to available energy, data volume, actual activity durations and execution status, observed temperatures, and other on-board state. Schedules are expected to change substantially in the course of execution. The solution space is prohibitively large and probabilistic in nature. A range of emergent behavior is accessible depending on the interaction between actual on-board state and a given formulation of constraints. For years, the specification and implementation of this capability have been considered and refined, as testing and analysis have mapped the contours of the system. Many concepts that could have been adopted were rejected, and in some cases, emergent properties have been exposed and beaten back with approaches to steer the behavior. This paper discusses some of the design history and underlying reasoning in the systems engineering of the first autonomous activity planner on Mars.

Kuhn, Stephen R↗

Mars 2020 Perseverance Trajectory Reconstruction and Performance from Launch through Landing

The Mars 2020 (M2020) Mission carrying Perseverance, the most advanced rover ever sent to Mars, successfully launched on an Atlas V 541 (AV-088) launch vehicle from the Eastern Test Range (ETR) at Cape Canaveral Air Force Station (CCAFS) in Florida at 11:50:00 UTC (T-Zero time) on July 30, 2020. After some station reconfiguration, carrier/telemetry were locked at both Deep Space Network (DSN) Canberra and Goldstone stations. Perseverance entered the Martian atmosphere at 20:36:50 Spacecraft Event Time (SCET) UTC, and landed inside Jezero Crater at 20:43:49 SCET UTC on February 18, 2021. Confirmation of nominal landing was received at the DSN Goldstone and Madrid tracking stations via the Mars Reconnaissance Orbiter at 20:55:11 Earth Received Time (ERT) UTC. This paper summarizes in detail the actual vs. predicted performance in terms of launch vehicle events, launch vehicle injection performance, actual DSN spacecraft lockup, trajectory correction maneuver performance, Entry, Descent, and Landing events, and overall trajectory and geometric characteristics.

Wong, Mau↗

Initial Development of A Digital Twin Model for an Electrified Aircraft Propulsion Emulation Rig

In support of aviation fuel burn and emission reduction goals, NASA is pursing high-payoff research investments that promise to transform aviation. This includes investments in Electrified Aircraft Propulsion (EAP), which relies on the generation, storage, transmission, and use of electrical power for producing thrust and optimizing propulsion system efficiency. Multiple technology challenges must be addressed to unlock the full potential of EAP. This includes advances in propulsion controls, which will be vital for ensuring coordinated efficient operation of the complex integrated subsystems that comprise EAP architectures. To support EAP controls research, the NASA Glenn Research Center has developed the Hybrid Propulsion Emulation Rig (HyPER). The HyPER laboratory hardware includes shaft-mounted electric machines, power converters, power supplies, power distribution cables, and an energy storage device that can be reconfigured to represent a variety of EAP architectures. It also includes an integrated real-time computer system that hosts developed EAP control software and turbomachinery simulations. This enables the electrical system and rotating shafts of EAP designs to be implemented in actual hardware and integrated with turbomachinery simulations and system-level EAP control logic implemented in software. In this form, the HyPER laboratory provides a partially simulated, partially hardware-in-the-loop test environment enabling the initial development and evaluation of EAP control technology. A prerequisite for the development of EAP control designs is the availability of a system model that accurately reflects the operation of the electrical system hardware. To support this need, a digital twin model of the HyPER electrical system hardware is under development. This model is being coded in the MATLAB Simulink environment and uses the NASA-developed Electrical Modeling and Thermal Analysis Toolbox (EMTAT) to construct a digital twin framework. EMTAT contains generic electrical component building blocks that are simulated at turbomachinery timescales. Associated inputs and outputs allow the blocks to be combined to model complete electrical systems. The EMTAT blocks also contain adjustable internal maps and parameters that can be set to reflect the operation of a specific electrical component. For the HyPER digital twin, the settings of these EMTAT block internal maps and parameters is determined through machine learning approaches applied to characterization run data collected from the laboratory. During characterization runs the laboratory electrical system hardware is subjected to a full range of torque, speed, and power settings. Acquired data is then used to estimate EMTAT block parameters using a variety of machine learning techniques. The resulting digital twin model is found to match the operation of actual HyPER hardware with an accuracy suitable for control development purposes. It also holds promise for other applications including modeling the performance of HyPER laboratory reconfigurations and model-based anomaly detection. Planned follow-on work to automate post-processing of acquired laboratory data to update the HyPER digital twin model will also be presented and discussed.

Electrified Aircraft Propulsion↗

Design for Reliability (DfR) in Space Life Support

The engineering process of Design for Reliability (DfR) is well established in the automotive and aerospace industries. DfR should be useful in the future development of space life support systems. DfR is a sequence of tasks that develop system requirements and plan reliability analysis and testing. First and fundamentally, the reliability requirement is defined. Next the system reliability model is developed, often using a reliability block diagram. The overall system reliability requirement is allocated to the subsystems and an estimate of the attainable reliability is made. This expected reliability can be improved by simplifying the design by removing components or by replacing less reliable components. Improving reliability can require difficult compromises, such as reducing performance requirements, increasing budget, or extending testing. The actual system reliability can be determined only by testing, which should continue long enough to provide the required confidence in the measured value. New systems often have unexpected design errors that cause failures in early testing. The usual reliability improvement process of testing, finding the failure modes, and redesigning to remove them reduces the failure rate and is referred to as “reliability growth.” After redesign has been completed, the system should be further tested to determine the actual achieved reliability more accurately. If the final system failure rate is too high, redundant systems can be used to improve overall operational reliability. Adding redundancy simply to increase the one- or two-fault tolerance metric may sometimes reduce reliability. Reliability can be improved in three ways: redesigning the system to include more reliable subsystems and components, reliability growth testing and failure mode removal, and by using parallel redundant systems. DfR should combine these approaches to achieve the required reliability while managing performance, cost, and schedule.

Reliability↗

Design for Reliability (DfR) in Space Life Support

The engineering process of Design for Reliability (DfR) is well established in the automotive and aerospace industries. DfR should be useful in the future development of space life support systems. DfR is a sequence of tasks that develop system requirements and plan reliability analysis and testing. First and fundamentally, the reliability requirement is defined. Next the system reliability model is developed, often using a reliability block diagram. The overall system reliability requirement is allocated to the subsystems and an estimate of the attainable reliability is made. This expected reliability can be improved by simplifying the design by removing components or by replacing less reliable components. Improving reliability can require difficult compromises, such as reducing performance requirements, increasing budget, or extending testing. The actual system reliability can be determined only by testing, which should continue long enough to provide the required confidence in the measured value. New systems often have unexpected design errors that cause failures in early testing. The usual reliability improvement process of testing, finding the failure modes, and redesigning to remove them reduces the failure rate and is referred to as “reliability growth.” After redesign has been completed, the system should be further tested to determine the actual achieved reliability more accurately. If the final system failure rate is too high, redundant systems can be used to improve overall operational reliability. Adding redundancy simply to increase the one- or two-fault tolerance metric may sometimes reduce reliability. Reliability can be improved in three ways: redesigning the system to include more reliable subsystems and components, reliability growth testing and failure mode removal, and by using parallel redundant systems. DfR should combine these approaches to achieve the required reliability while managing performance, cost, and schedule.

Reliability↗

Blind Validation Study of PRICE TruePlanning and SEER-H

Two of the primary parametric costing tools used to estimate the development and production cost of future spacecraft hardware are PRICE TruePlanning by PRICE Systems, and System Estimation and Evaluation of Resources-Hardware (SEER-H) by Galorath. These are standard tools used by NASA and industry to estimate the cost of new aerospace hardware. This study is an independent verification of the accuracy of these tools and was originally published in 2018. The purpose of this presentation is to circulate the findings of that study among the NASA cost community. Both PRICE Systems and Galorath have completed internal validation studies of their parametric cost estimating tools; however, they only provided the results of the studies and did not detail the exact methods used to perform the validation. In the present study, cost estimators used PRICE TruePlanning and SEER-H to estimate the cost of twelve different past NASA science missions. The estimators were prevented from knowing the actual cost of the missions in an effort to minimize cognitive biases. In the present study, SEER-H had an average error of 23%, median error of -0.3%, with a standard deviation of 43%. PRICE had an average error of 52%, median error of 50%, and standard deviation of 45%. Nine of the twelve mission's actual costs fell within the 80% confidence interval of SEER's probabilistic estimates; however, none of the missions fell within PRICE’s confidence intervals. There were several factors independent of PRICE and SEER-H which may have affected the accuracy of the results in the present study including: uncertainty in the technical data used for the estimates, the methods used to estimate uncertainty in spacecraft component mass and numbers of prototypes, and the experience of the estimators.

SEER↗

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↗

Flight Mechanics Modeling and Simulation of the Earth Entry System

Introduction: The Mars Sample Return (MSR) Campaign being planned by NASA and ESA has the ambitious goal to return Mars samples back to Earth. This international collaboration had developed a concept of operations that included a ESA-designed Earth Return Orbiter (ERO) and NASA-designed Capture, Containment, and Return System (CCRS). The Earth Entry System (EES), consisting of a protective aeroshell that houses the samples as well as sample containment vessels, would conduct entry, descent, and landing (EDL) on a direct Earth trajectory. The EES would enter on a spin-stabilized ballistic trajectory with the goal to passively achieve aerodynamic stability throughout all regions of flight. The EDL sequence would end with the EES impacting the soft playa soil of the Utah Test and Training Range (UTTR). As of the submission of this abstract, the MSR campaign is undergoing a re-architecture leading to a pause in EES development. However, the novel approaches developed in flight mechanics modeling and simulation can significantly benefit the greater IPPW community in the development of Earth return vehicles. This paper will present the latest state of EES flight mechanics modeling and simulation. The paper will highlight the simulation architecture developed and key lessons learned from understanding of EDL trajectory sensitivities. Modeling and Simulation: Figure 1 provides a high-level concept of operations for the approach, entry, descent, and landing (AEDL) phase of the CCRS-portion of MSR. The objective of EES flight mechanics is to model and simulate the EES trajectory from ERO separation to ground impact at UTTR. A variety of flight mechanics simulation models were utilized to model both exo-atmopsheric and atmospheric portions of flight. 42, a 6-DOF simulation developed at Goddard Space Flight Center, is utilized for propagating the attitude of EES during exo-atmospheric flight. 42 allows for a variety of spin eject mechanism scenarios to be simulated for analysis. 10 minutes prior to entry, the 42 states are handed off to the EDL sims. The prime EDL sim utilized by EES is the Program to Optimize Simulated Trajectories II (POST2), a 6-DOF sim developed at Langley Research Center, and the independent verification and validation EDL sim utilized is DSENDS, a 6-DOF sim developed at Jet Propulsion Laboratory. Figure 2 provides a visualization of the flight mechanics simulation model flow through various points in the AEDL phase. Due to the existence of a variety of sim models, the EES flight mechanics team developed processes for data hand-off. These processes included the development of a centralized coordinate frame document, utilization of a single, centralized simulation input document for all sims to reference, and hand-off files containing both the technical data to be ingested by other flight mechanics sims as well as annotations of modeling assumptions utilized to generate the data. Figure~\ref{fig:post2simarchitecture} provides an overview of the POST2 sim architecture wherein POST2 ingests numerous subsystem models and input files. The dispersed state file generated by MONTE provides the position/velocity state of the trajectory while the 42 Handoff file provides the attitude. The aerodynamics database, delivered by the EES aeroscience team, is utilized to simulate the aerodynamic forces and moments experienced during EDL. A custom atmosphere model, developed by EES atmosphere team, is utilized to simulate the anticipated atmosphere environment around the region of Earth through which the EES trajectory flys. These inputs and subsystem models can be varied depending on the AEDL flight mechanics scenario being simulated. Monte Carlo simulations are utilized to generate statistical AEDL performance metrics in the form of scorecards and violin plots. Furthermore, outputs from the POST2 simulation are utilized for follow-on analyses including aerothermal and landing performance. \section{Flight Mechanics Lessons Learned} Though the EES flight mechanics team uncovered a variety of lessons learned through the analysis conducted to support CCRS through preliminary design review, this paper will highlight the most important lessons. A key AEDL performance goal is to ensure the landing footprint of EES remains on the UTTR south range. A common modeling strategy used in EDL analysis is One-Variable-At-a-Time (OVAT). OVAT analysis provides insight into the key drivers that affect AEDL performance metrics. Figure 3 shows the landing ellipses for single dispersion sources as compared to the baseline aggregate of all dispersions. The figure shows that atmosphere winds alone dominate the size of the footprint ellipse (note: EES does not use a parachute unlike previous Earth-return missions and is in wind-driven free fall for ~5min). The significance of the wind led the EES flight mechanics team to pursue the development of a Custom Atmosphere Model [4], in lieu of EarthGRAM [1], built on actual radiosonde wind measurements around the UTTR-region. This decision was driven by the realism in the generated footprint ellipses and lessons-learned from Stardust [5]. These findings will be invaluable for future Earth-return missions in providing an early understanding of the key drivers affecting footprint size and modeling considerations for which to account. Another lesson learned is tied to the AEDL performance goal of achieving passive stability throughout all regions of flight. It is well understood that blunt-body aeroshells are less stable as they transition from supersonic to subsonic. Eliminating a backshell does help improvestability; however, other phenomena such as roll-induced instability during terminal descent can still arise. The EES flight mechanics team developed stability metrics as tools to better understand the causes of and better predict the onset of dynamic instability. These tools were built upon analytical models developed by Jaffe [3] and Murphy [2]. The tools were shown to both be very accurate in correlation with actual unstable cases and useful in developing stability margin policies based on the vehicle design and simulation considerations (e.g. sphere-cone angle change, mass change, wind turbulence). These tools allowed for the current EES design to demonstrate the ability to achieve passive stability and can be an invaluable tool for consideration in the design of parachute-less Earth-return vehicles.

Rohan Deshmukh↗

South Africa Ecological Conservation: Identifying and Mapping Riparian Areas in South Africa with Earth Observations

Riparian zones are thin strips of wetland that occur along the edges of rivers, lakes, and other water bodies. They provide many ecosystem and societal benefits such as stream bank stabilization, flood control, and habitat stability, making these zones very important areas to preserve and protect. Recognizing the need to accurately map these ecosystems in a cost-effective way, we partnered with the South African National Biodiversity Institute (SANBI) and the Biodiversity Survey of the Cape(BioSCape) to develop a GI methodology using Esri's ArcGIS Pro and data from Landsat 9 Operational Land Imager-2, Sentinel-2 Multispectral Instrument, and the Shuttle Radar Topography Mission to identify potential riparian zones (PRZ) and observed riparian vegetation(ORV) in the Southern Cape and the North West Province of South Africa to estimate the actual riparian vegetation (ARV) within those areas. Potential riparian ecosystems were calculated by utilizing a Topographic Wetness Index (TWI) and a water feature layer, while observed riparian vegetation were calculated by overlaying a Normalized Difference Vegetation Index (NDVI) and TWI. Actual Riparian Vegetation is determined by the overlap of ORV with PRZ and is done with conditional statements; ORV within PRZ is ARV. This method significantly improved a current riparian land cover classification since it combined high resolution optical imagery and topographic data. We anticipate such maps will be used by conservationists and practitioners interested in riparian monitoring and management.

Remote Sensing↗

Determining Simulation Fidelity Necessary for Evaluating Onboard Vehicle Capabilities and Crew Roles on Long Duration Exploration Missions Beyond Low-Earth Orbit

Identification of onboard vehicle capabilities and crew roles and responsibilities necessary for achieving effective human-systems collaboration will require iterative cycles of concept development and empirical evaluation of human performance in complex operations. This report presents the results of an effort to lay the groundwork for determining the level of fidelity of simulated environments most suitable for validating concepts and evaluating implementations of a new Human Systems Integration Architecture (HSIA) that will support the flight crew on long duration exploration missions beyond low-Earth orbit. To do that, we conducted a literature review on simulation fidelity and surveyed simulation capabilities inside and outside of NASA used in NASA-sponsored research. We also analyzed two International Space Station (ISS) vehicle anomalies to identify the types of scenario events and crew activities that may need to be simulated. Our survey findings reveal that most NASA simulation facilities are designed to achieve high physical fidelity while HSIA risk mitigation requires simulation emphasizing task and functional fidelity aspects. A trade analysis shows that, for standard and requirement development, evaluation conducted using synthetic task environments with inexperienced participants will support testing a wide variety of conditions and yield findings robust enough to be generalized to a wide variety of designs on which developed standards and requirements might be levied while allowing human performance standard measures to be collected using consistent methods across tasks and conditions. For technology/tool development, because findings will only need to be generalized to the actual target environment in which the technology/tool will be used, it is more suitable to evaluate the prototypes in a scaled world that preserves functional relationships present in the actual target environment with intended user populations. To wrap up, we give an overview of a well-known synthetical task environment in the space domain and discuss what it takes to construct a synthetic task environment.

simulation fidelity↗

Summary and Annotated Bibliography of Measurement Error Corrections with Potential Application in Future Quesst Mission Community Noise Studies

This document is motivated by likely needs of the Quesst mission community response tests, which will culminate in data collection and estimation of dose-response regression relationships for consideration by domestic and international aviation regulators. Furthermore, basic research questions evaluating interactions between rates of community annoyance, dose levels, and indicators of the presence of rattle, vibration, and startle hinge on hypothesis testing in the context of regression models. For a variety of reasons, noise doses may be known only imprecisely and may not reflect the actual level experienced by responding subjects. These differences between true dose and estimated dose, be they systematic or random, constitute covariate measurement error. Available statistics literature speaks to the impacts of measurement error on regression models, both in terms of bias in estimated coefficients and predicted values, and in terms of the loss of statistical power for hypothesis testing. Given the particulars of a categorical annoyance response variable and a continuous noise dose predictor variable subject to measurement error during testing, the emphasis of this report is on findings and methods pertinent to generalized linear (and mixed) models likely to be employed during the Quesst mission community tests. We reach the following conclusions: 1. Of four reviewed methods, structural Bayesian measurement error models and simulation extrapolation (SIMEX) may be the most readily applicable to Quesst mission community noise study objectives. 2. If warranted, a linear measurement model can help model systematic sources of measurement error that the classical measurement error does not. 3. For its ready implementation and small additional input requirements, simulation extrapolation may be ideally suited for addressing secondary research questions involving interactions between annoyance, noise dose, and other factors through hypothesis testing. 4. For their flexibility and ability to propagate uncertainty, structural Bayesian hierarchical models have great appeal for mission purposes; some care may be needed in developing appropriate probability models describing actual noise exposure during testing. An annotated bibliography logs additional papers and resources that may be of value to analysts in other projects and disciplines.

Dose-Response Model↗