Search NASA⌕ Search

SEARCH · Search NASA

Results for “emergent constraint”

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 253 records · Page 14

Orion Optical Navigation Progress Toward Exploration: Mission 1

Optical navigation of human spacecraft was proposed on Gemini and implemented successfully on Apollo as a means of autonomously operating the vehicle in the event of lost communication with controllers on Earth. It shares a history with the "method of lunar distances" that was used in the 18th century and gained some notoriety after its use by Captain James Cook during his 1768 Pacific voyage of the HMS Endeavor. The Orion emergency return system utilizing optical navigation has matured in design over the last several years, and is currently undergoing the final implementation and test phase in preparation for Exploration Mission 1 (EM-1) in 2019. The software development is being worked as a Government Furnished Equipment (GFE) project delivered as an application within the Core Flight Software of the Orion camera controller module. The mathematical formulation behind the initial ellipse fit in the image processing is detailed in Christian. The non-linear least squares refinement then follows the technique of Mortari as an estimation process of the planetary limb using the sigmoid function. The Orion optical navigation system uses a body fixed camera, a decision that was driven by mass and mechanism constraints. The general concept of operations involves a 2-hour pass once every 24 hours, with passes specifically placed before all maneuvers to supply accurate navigation information to guidance and targeting. The pass lengths are limited by thermal constraints on the vehicle since the OpNav attitude generally deviates from the thermally stable tail-to-sun attitude maintained during the rest of the orbit coast phase. Calibration is scheduled prior to every pass due to the unknown nature of thermal effects on the lens distortion and the mounting platform deformations between the camera and star trackers. The calibration technique is described in detail by Christian, et al. and simultaneously estimates the Brown-Conrady coefficients and the Star Tracker/Camera interlock angles. Accurate attitude information is provided by the star trackers during each pass. Figure 1 shows the various phases of lunar return navigation when the vehicle is in autonomous operation with lost ground communication. The midcourse maneuvers are placed to control the entry interface conditions to the desired corridor for safe landing. The general form of optical navigation on Orion is where still images of the Moon or Earth are processed to find the apparent angular diameter and centroid in the camera focal plane. This raw data is transformed into range and bearing angle measurements using planetary data and precise star tracker inertial attitude. The measurements are then sent to the main flight computer's Kalman filter to update the onboard state vector. The images are, of course, collected over an arc to converge the state and estimate velocity. The same basic technique was used by Apollo to satisfy loss-of-comm, but Apollo used manual crew sightings with a vehicle-integral sextant instead of autonomously processing optical imagery. The software development is past its Critical Design Review, and is progressing through test and certification for human rating. In support of this, a hardware-in-the-loop test rig was developed in the Johnson Space Center Electro-Optics Lab to exercise the OpNav system prior to integrated testing on the Orion vehicle. Figure 2 shows the rig, which the test team has dubbed OCILOT (Orion Camera In the Loop Optical Testbed). Analysis performed to date shows a delivery that satisfies an allowable entry corridor as shown in Figure 3.

Holt, Greg N.↗

Internal Variability and Disequilibrium Confound Estimates of Climate Sensitivity from Observations

An emerging literature suggests that estimates of equilibrium climate sensitivity (ECS) derived from recent observations and energy balance models are biased low because models project more positive climate feedback in the far future. Here we use simulations from the Coupled Model Intercomparison Project Phase 5 (CMIP5) to show that across models, ECS inferred from the recent historical period (1979-2005) is indeed almost uniformly lower than that inferred from simulations subject to abrupt increases in CO2-radiative forcing. However, ECS inferred from simulations in which sea surface temperatures are prescribed according to observations is lower still. ECS inferred from simulations with prescribed sea surface temperatures is strongly linked to changes to tropical marine low clouds. However, feedbacks from these clouds are a weak constraint on long-term model ECS. One interpretation is that observations of recent climate changes constitute a poor direct proxy for long-term sensitivity.

Marvel, Kate↗

Theoretical constraints on oxygen and carbon dioxide concentrations in the Precambrian atmosphere

Simple (one-dimensional) climate models suggest that carbon dioxide concentrations during the Archean must have been at least 100-1000 times the present level to keep the Earth's surface temperature above freezing in the face of decreased solar luminosity. Such models provide only lower bounds on CO2, so it is possible that CO2 levels were substantially higher than this and that the Archean climate was much warmer than today. Periods of extensive glaciation during the early and late Proterozoic, on the other hand, indicate that the climate at these times was relatively cool. To be consistent with climate models CO2 partial pressures must have declined from approximately 0.03 to 0.3 bar around 2.5 Ga ago to between 10(-3) and 10(-2) bar at 0.8 Ga ago. This steep decrease in carbon dioxide concentrations may be inconsistent with paleosol data, which implies that pCO2 did not change appreciably during that time. Oxygen was essentially absent from the Earth's atmosphere and oceans prior to the emergence of a photosynthetic source, probably during the late Archean. During the early Proterozoic the atmosphere and surface ocean were apparently oxidizing, while the deep ocean remained reducing. An upper limit of 6 x 10(-3) bar for pO2 at this time can be derived by balancing the burial rate of organic carbon with the rate of oxidation of ferrous iron in the deep ocean. The establishment of oxidizing conditions in the deep ocean, marked by the disappearance of banded iron formations approximately 1.7 Ga ago, permitted atmospheric oxygen to climb to its present level. O2 concentrations may have remained substantially lower than today, however, until well into the Phanerozoic.

Review, Tutorial↗

More / All Electric Vertical Take-Off and Landing (VTOL) Vehicle Sensitivities to Propulsion and Power Performance

Battery power and energy density are important parameters for the emerging concepts for more / all-electric vehicles. Electric propulsion and power system performance is also important. To better understand how electric propulsion and power systems component performance influences overall vehicle design, a sensitivity assessment was performed noting changes in vehicle gross weight and energy usage. Updated versions of the Revolutionary Vertical lift Technology (RVLT) Project vertical take-off and landing (VTOL) urban air mobility (UAM) reference vehicles and missions were used. NASA electric vehicle studies are discussed which were used to help select the range of electric propulsion and power system performance parameters used in this assessment. Thermal management systems (TMS) considerations are also important; new and innovative power management and distribution systems can reduce electric system weight and losses, reducing thermal management constraints often imposed by electric systems modest maximum use temperatures. Vehicles with higher disk loadings (smaller rotors) require higher power levels per unit weight for VTOL operations, which make them more sensitive to electric system weights and efficiencies. Battery, all-electric vehicles show different sensitivities to component performance than turboelectric or hybrids systems. Battery, all-electric propulsion systems may increase vehicle weight and size, but still results in lower mission energy usage than their hydrocarbon-fueled versions. Significant vehicle weight growth to electric propulsion and power system power-to-weight reductions also occurs at different levels among the various concepts. From these results, one can more readily identify required component performance levels, potential component choices or, research and development paths.

Electric Propulsion Systems (Aircraft)↗

More / All Electric Vertical Take-Off and Landing (VTOL) Vehicle Sensitivities to Propulsion and Power Performance

Battery power and energy density are important parameters for the emerging concepts for more / all-electric vehicles. Electric propulsion and power system performance is also important. To better understand how electric propulsion and power systems component performance influences overall vehicle design, a sensitivity assessment was performed noting changes in vehicle gross weight and energy usage. Updated versions of the Revolutionary Vertical lift Technology (RVLT) Project vertical take-off and landing (VTOL) urban air mobility (UAM) reference vehicles and missions were used. NASA electric vehicle studies are discussed which were used to help select the range of electric propulsion and power system performance parameters used in this assessment. Thermal management systems (TMS) considerations are also important; new and innovative power management and distribution systems can reduce electric system weight and losses, reducing thermal management constraints often imposed by electric systems modest maximum use temperatures. Vehicles with higher disk loadings (smaller rotors) require higher power levels per unit weight for VTOL operations, which make them more sensitive to electric system weights and efficiencies. Battery, all-electric vehicles show different sensitivities to component performance than turboelectric or hybrids systems. Battery, all-electric propulsion systems may increase vehicle weight and size, but still results in lower mission energy usage than their hydrocarbon-fueled versions. Significant vehicle weight growth to electric propulsion and power system power-to-weight reductions also occurs at different levels among the various concepts. From these results, one can more readily identify required component performance levels, potential component choices or, research and development paths.

electric propulsion systems (aircraft) mission ana↗

Designing a Propylene-Glycol Coolant Servicer System for Gateway’s Internal Active Thermal Control System

A human spacecraft ATCS—especially one using single-phase coolant loops exposed to cabin atmospheric conditions—requires periodic degassing and refilling to support long-duration missions of 15 to 30 years. During initial fill operations, system maintenance, gas permeation, and quick-disconnect mating or de-mating, small amounts of gas can gradually enter the coolant system over time. This can lead to degraded heat transfer performance, pump cavitation, and potentially pump vapor lock if a significant gas volume accumulates over time. Additionally, system leaks and routine fluid sampling can gradually reduce accumulator volumes to unacceptable levels, requiring periodic refills. In more severe cases, catastrophic changes in fluid composition may necessitate emergency draining, refilling, and degassing to ensure continued system functionality. These risks were identified and mitigated on the ISS ITCS through the development of a dual-membrane degasser ORU and a Fluid Servicer System ORU for coolant refilling. These systems were developed for the fully water-based ISS ITCS Coolant[1]. The Gateway space station, the first permanent human habitat in lunar orbit, uses a propylene-glycol/water coolant mixture, which has significantly different fluid properties compared to pure water. Because microgravity degassing technologies are sensitive to fluid surface tension and viscosity, existing ISS hardware is not suitable for servicing a propylene-glycol-based TCS. Unlike the ISS, the Gateway will operate in a higher-radiation environment and must meet stricter mass constraints due to its location outside of low earth orbit. This Government Furnished Equipment (GFE) flight hardware project aims to develop a lightweight, radiation-resistant Coolant Servicer System (CSS) capable of degassing and refilling Gateway’s propylene-glycol water-based IATCS.

Propylene Glycol Water↗

Designing a Propylene-Glycol Coolant Servicer System for Gateway’s Internal Active Thermal Control System

A human spacecraft ATCS—especially one using single-phase coolant loops exposed to cabin atmospheric conditions—requires periodic degassing and refilling to support long-duration missions of 15 to 30 years. During initial fill operations, system maintenance, gas permeation, and quick-disconnect mating or de-mating, small amounts of gas can gradually enter the coolant system over time. This can lead to degraded heat transfer performance, pump cavitation, and potentially pump vapor lock if a significant gas volume accumulates over time. Additionally, system leaks and routine fluid sampling can gradually reduce accumulator volumes to unacceptable levels, requiring periodic refills. In more severe cases, catastrophic changes in fluid composition may necessitate emergency draining, refilling, and degassing to ensure continued system functionality. These risks were identified and mitigated on the ISS ITCS through the development of a dual-membrane degasser ORU and a Fluid Servicer System ORU for coolant refilling. These systems were developed for the fully water-based ISS ITCS Coolant[1]. The Gateway space station, the first permanent human habitat in lunar orbit, uses a propylene-glycol/water coolant mixture, which has significantly different fluid properties compared to pure water. Because microgravity degassing technologies are sensitive to fluid surface tension and viscosity, existing ISS hardware is not suitable for servicing a propylene-glycol-based TCS. Unlike the ISS, the Gateway will operate in a higher-radiation environment and must meet stricter mass constraints due to its location outside of low earth orbit. This Government Furnished Equipment (GFE) flight hardware project aims to develop a lightweight, radiation-resistant Coolant Servicer System (CSS) capable of degassing and refilling Gateway’s propylene-glycol water-based IATCS.

Propylene Glycol Water↗

NASA Near Earth Network (NEN), Deep Space Network (DSN) and Space Network (SN) Support of CubeSat Communications

There has been a historical trend to increase capability and drive down the Size, Weight and Power (SWAP) of satellites and that trend continues today. Small satellites, including systems conforming to the CubeSat specification, because of their low launch and development costs, are enabling new concepts and capabilities for science investigations across multiple fields of interest to NASA. NASA scientists and engineers across many of NASAs Mission Directorates and Centers are developing exciting CubeSat concepts and welcome potential partnerships for CubeSat endeavors. From a communications and tracking point of view, small satellites including CubeSats are a challenge to coordinate because of existing small spacecraft constraints, such as limited SWAP and attitude control, low power, and the potential for high numbers of operational spacecraft. The NASA Space Communications and Navigation (SCaN) Programs Near Earth Network (NEN), Deep Space Network (DSN) and the Space Network (SN) are customer driven organizations that provide comprehensive communications services for space assets including data transport between a missions orbiting satellite and its Mission Operations Center (MOC). The NASA NEN consists of multiple ground antennas. The SN consists of a constellation of geosynchronous (Earth orbiting) relay satellites, named the Tracking and Data Relay Satellite System (TDRSS). The DSN currently makes available 13 antennas at its three tracking stations located around the world for interplanetary communication. The presentation will analyze how well these space communication networks are positioned to support the emerging small satellite and CubeSat market. Recognizing the potential support, the presentation will review the basic capabilities of the NEN, DSN and SN in the context of small satellites and will present information about NEN, DSN and SN-compatible flight radios and antenna development activities at the Goddard Space Flight Center (GSFC) and across industry. The presentation will review concepts on how the SN multiple access capability could help locate CubeSats and provide a low-latency early warning system. The presentation will also present how the DSN is evolving to maximize use of its assets for interplanetary CubeSats. The critical spectrum-related topics of available and appropriate frequency bands, licensing, and coordination will be reviewed. Other key considerations, such as standardization of radio frequency interfaces and flight and ground communications hardware systems, will be addressed as such standardization may reduce the amount of time and cost required to obtain frequency authorization and perform compatibility and end-to-end testing. Examples of standardization that exist today are the NASA NEN, DSN and SN systems which have published users guides and defined frequency bands for high data rate communication, as well as conformance to CCSDS standards. The workshop session will also seek input from the workshop participants to better understand the needs of small satellite systems and to identify key development activities and operational approaches necessary to enhance communication and navigation support using NASA's NEN, DSN and SN.

Telecommunication↗

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

systems engineering↗

Precise Point Positioning for the Efficient and Robust Analysis of GPS Data From Large Networks

Networks of dozens to hundreds of permanently operating precision Global Positioning System (GPS) receivers are emerging at spatial scales that range from 10(exp 0) to 10(exp 3) km. To keep the computational burden associated with the analysis of such data economically feasible, one approach is to first determine precise GPS satellite positions and clock corrections from a globally distributed network of GPS receivers. Then, data from the local network are analyzed by estimating receiver specific parameters with receiver-specific data; satellite parameters are held fixed at their values determined in the global solution. This "precise point positioning" allows analysis of data from hundreds to thousands of sites every day with 40 Mflop computers, with results comparable in quality to the simultaneous analysis of all data. The reference frames for the global and network solutions can be free of distortion imposed by erroneous fiducial constraints on any sites.

Zumberge, J. F.↗

Precise Point Positioning for the Efficient and Robust Analysis of GPS Data from Large Networks

Networks of dozens to hundreds of permanently operating precision Global Positioning System (GPS) receivers are emerging at spatial scales that range from 10(exp 0) to 10(exp 3) km. To keep the computational burden associated with the analysis of such data economically feasible, one approach is to first determine precise GPS satellite positions and clock corrections from a globally distributed network of GPS receivers. Their, data from the local network are analyzed by estimating receiver- specific parameters with receiver-specific data satellite parameters are held fixed at their values determined in the global solution. This "precise point positioning" allows analysis of data from hundreds to thousands of sites every (lay with 40-Mflop computers, with results comparable in quality to the simultaneous analysis of all data. The reference frames for the global and network solutions can be free of distortion imposed by erroneous fiducial constraints on any sites.

Zumberge, J. F.↗

A Self-Stabilizing Distributed Clock Synchronization Protocol for Arbitrary Digraphs

This report presents a self-stabilizing distributed clock synchronization protocol in the absence of faults in the system. It is focused on the distributed clock synchronization of an arbitrary, non-partitioned digraph ranging from fully connected to 1-connected networks of nodes while allowing for differences in the network elements. This protocol does not rely on assumptions about the initial state of the system, other than the presence of at least one node, and no central clock or a centrally generated signal, pulse, or message is used. Nodes are anonymous, i.e., they do not have unique identities. There is no theoretical limit on the maximum number of participating nodes. The only constraint on the behavior of the node is that the interactions with other nodes are restricted to defined links and interfaces. We present an outline of a deductive proof of the correctness of the protocol. A model of the protocol was mechanically verified using the Symbolic Model Verifier (SMV) for a variety of topologies. Results of the mechanical proof of the correctness of the protocol are provided. The model checking results have verified the correctness of the protocol as they apply to the networks with unidirectional and bidirectional links. In addition, the results confirm the claims of determinism and linear convergence. As a result, we conjecture that the protocol solves the general case of this problem. We also present several variations of the protocol and discuss that this synchronization protocol is indeed an emergent system.

Malekpour, Mahyar R.↗

Advancing Autonomy in Distributed Space Systems: Insights From on-Orbit Testing with the Starling 1.0 Mission

Autonomous decision-making is crucial for enhancing mission effectiveness in Distributed Space Systems (DSS), particularly in multi-spacecraft operations where communication constraints and mission complexity pose challenges. The Distributed Spacecraft Autonomy (DSA) team at NASA’s Ames Research Center is advancing autonomy in DSS through five key technical areas: distributed resource and task management, reactive operations, system modeling and simulation, human-swarm interaction, and ad hoc network communications. The DSA experiment onboard the Starling 1.0 Mission showcases collaborative resource allocation for multi-point science data collection with four small spacecraft. Autonomy in decision-making is highlighted as a crucial factor for multi-spacecraft missions, enabling spacecraft to operate independently, reducing reliance on ground control. This capability is particularly significant for future deep-space missions, where communication delays and limited data transmission capacity make traditional command and control approaches impractical. This demonstration focuses on a GPS Channel Selection Experiment, leveraging emergent capabilities like "shared sampling" and "simultaneous sampling" to optimize channel selection across the spacecraft swarm. The experiment aims to capture ionospheric phenomena such as the Equatorial Ionization Anomaly and Polar Patches. The DSA system's autonomous reconfiguration ability is showcased, emphasizing its adaptability to natural phenomena without significant integration efforts. The GPS Channel Selection Experiment utilizes a dual-band GPS receiver to estimate plasma density in the ionosphere. Explorative and exploitative channel selections are employed based on the nature of observed phenomena. The performance of DSA algorithms is evaluated in terms of optimal channel allocations and responsiveness to changes in observed features. The DSA Flight Software utilizes the Core Flight System (cFS) framework, ensuring compatibility with the Starling 1.0 flight mission software. DSA showcases results from RTI’s Connext DDS Micro communication middleware, enabling message routing over the Ad-Hoc Network of Starling 1.0. This paper provides a comprehensive overview of the DSA experiment's initial results, emphasizing the advancements in autonomy for Distributed Space Systems and the successful collaboration with the Starling 1.0 mission.

Caleb Ashmore Adams↗

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↗

The role of optimization in the next generation of computer-based design tools

There is a close relationship between design optimization and the emerging new generation of computer-based tools for engineering design. With some notable exceptions, the development of these new tools has not taken full advantage of recent advances in numerical design optimization theory and practice. Recent work in the field of design process architecture has included an assessment of the impact of next-generation computer-based design tools on the design process. These results are summarized, and insights into the role of optimization in a design process based on these next-generation tools are presented. An example problem has been worked out to illustrate the application of this technique. The example problem - layout of an aircraft main landing gear - is one that is simple enough to be solved by many other techniques. Although the mathematical relationships describing the objective function and constraints for the landing gear layout problem can be written explicitly and are quite straightforward, an approximation technique has been used in the solution of this problem that can just as easily be applied to integrate supportability or producibility assessments using theory of measurement techniques into the design decision-making process.

Rogan, J. Edward↗

Next Generation Thermal Protection System for Outer Planet Probes and Orbiter

Saturn Probe and Ice Giant Orbiter along with in-situ Probe Missions continue to be very high priority mis-sions. A result of the advocacy by OPAG and other Analysis Groups, the 3D Woven, Dual-Layer HEEET thermal protection system, mature at TRL 6, has closed the TPS gap for extreme environment missions. A mid density follow on to DL HEEET, developed to meet earth entry requirements, is a Single Layer vari-ant of the 3D woven TPS, which provides a mass effi-cient single layer 3D Mid-Density TPS (3MDCP) that has been baselined as the heatshield for MSR EEV. Continued development of 3MDCP will elevate it to TRL 6 by 2025. Conformal-PICA (C-PICA) devel-opment was pursued to establish a more efficient and robust alternate to PICA, and it is at TRL 4+. Our rationale for the next generation of TPS de-velopment is based on the on the missions needs of the next decade Outer Planet missions that are unique and more demanding than any other destinations. Taking advantage of the recent planned development of sev-eral materials, the next generation of TPS offers a much more mass efficient option for small, medium, and large class Outer Planet missions. Saturn Probes: While mission designers are gen-erally interested in shallow entry to maintain the g-load during entry around 50g, the heat-load for shallow entry can range between (100 kJ/cm2 – 300 kJ/cm2), two orders of magnitude higher than Venus or Sample Return missions. TPS must not only offer protection but must be mass efficient to perform reasonable sci-ence. TPS mass can quickly become 50% or more of the mass of the entire entry system. Recent analysis performed shows Saturn Probe missions could signifi-cantly benefit from the single layer HEEET (SL-HEEET/3MDCP). A DL-HEEET based heatshield mass could be ~ (40% -50%), SL-HEEET can provide additional (30% - 50%) mass savings. At the same time, C-PICA can provide (30% - 50%) mass savings on the backshell. The combined mass savings can be significant enough to carry an additional probe, if de-sired. Ice Giant Aerocapture Missions: Aerocapture mission architectures can provide significant ad-vantage over traditional propulsive insertion missions in multiple ways. 1) Reduced trip time ~ (4- 6) years (30% -40%), 2) Enables placing the orbiter, probe, and lander, all together and 3) Allows for greater science mass (probes and landers) due to mass efficiency. The delivery of a probe from orbit makes it easier and eliminates mission design constraints by HEEET for direct entry [4] of probes and allows for more targeted in-situ science once the Orbiter is able to collect data. In the past 20 years, progress made in GN&C for lift-guided entry missions (MSL, Orion EFT1, Mars 2020) and the expertise in blunt body aerodynamics at large scale (~ 5m) has led the EDL community to conclude that aerocapture is a “go do” engineering activity. An aerocapture mission that will deplete the excess energy of a fast arrival mission will require a mass efficient TPS that can handle extreme heat-load, ~ (100 kJ/cm2 – 500 kJ/cm2). Hence TPS, feasibility as well as mass efficiency requires assessment. Utilizing the recent developments, a comprehensive, bounding analysis was done to establish the potential for SOA (HEEET) system as well as emerging new TPS such as SL-HEEET and C-PICA. In this proposed poster, we will outline the process by which we establish bounding aerocapture trajecto-ries for hyperbolic excess velocities ranging from 27 km/s to 35 km/s, for low L/D (~ 0.4) configurations and determine conservative/bounding estimate of aer-othermal environment by using a combination of CFD simulations and stagnation point heating estimates [7]. This engineering approach allows us to assess the TPS need vs. TPS capability and determine the applicability of existing TPS. Once an applicable suite of TPS is determined, the TPS thickness and mass are comput-ed. We show that the TPS mass fraction can be as low as 5% to as high as 20%, depending on the use of ad-vanced TPS, while HEEET is sufficient but will require 50% of the entry mass.

E Venkatapathy↗

NASA CEV Reference Entry GN&C System and Analysis

As part of its overall objectives, the Orion spacecraft will be required to perform entry and Earth landing functions for Low Earth Orbit (LEO) and Lunar missions. Both of these entry scenarios will begin with separation of the Service Module (SM), making them unique from other Orion mission phases in that only the Command Module (CM) portion of the Crew Exploration Vehicle (CEV) will be involved, requiring a CM specific Guidance, Navigation and Control (GN&C) system. Also common to these mission scenarios will be the need for GN&C to safely return crew (or cargo) to earth within the dynamic thermal and structural constraints of entry and within acceptable accelerations on the crew, utilizing the limited aerodynamic performance of the CM capsule. The lunar return mission could additionally require an initial atmospheric entry designed to support a precision skip and second entry, all to maximize downrange performance and ensure landing in the United States. This paper describes the Entry GN&C reference design, developed by the NASA-led team, that supports these entry scenarios and that was used to validate the Orion System requirements. Description of the reference design will include an overview of the GN&C functions, avionics, and effectors and will relate these to the specific design drivers of the entry scenarios, as well as the desire for commonality in vehicle systems to support the different missions. The discussion will also include the requirement for an Emergency Entry capability beyond that of the nominal performance of the multi-string GNC system, intended to return the crew to the earth in a survivable but unguided manner. Finally, various analyses will be discussed, including those completed to support validation efforts of the current CEV requirements, along with those on-going and planned with the intention to further refine the requirements and to support design development work in conjunction with the prime contractor. Some of these ongoing analyses will include work to size effectors (jets) and fuel budgets, to refine skip entry concepts, to characterize navigation performance and uncertainties, to provide for SM disposal offshore and to identify requirements to support target site selection.

Munday, S.↗

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗