Search NASA⌕ Search

SEARCH · Search NASA

Results for “Use Cases”

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 91 records · Page 5

Test-Case Generation using an Explicit State Model Checker Final Report

In the project 'Test-Case Generation using an Explicit State Model Checker' we have extended an existing tools infrastructure for formal modeling to export Java code so that we can use the NASA Ames tool Java Pathfinder (JPF) for test case generation. We have completed a translator from our source language RSML(exp -e) to Java and conducted initial studies of how JPF can be used as a testing tool. In this final report, we provide a detailed description of the translation approach as implemented in our tools.

Heimdahl, Mats P. E.↗

Toward a New Generation of Agricultural System Data, Models, and Knowledge Products: State of Agricultural Systems Science

We review the current state of agricultural systems science, focusing in particular on the capabilities and limitations of agricultural systems models. We discuss the state of models relative to five different Use Cases spanning field, farm, landscape, regional, and global spatial scales and engaging questions in past, current, and future time periods. Contributions from multiple disciplines have made major advances relevant to a wide range of agricultural system model applications at various spatial and temporal scales. Although current agricultural systems models have features that are needed for the Use Cases, we found that all of them have limitations and need to be improved. We identified common limitations across all Use Cases, namely 1) a scarcity of data for developing, evaluating, and applying agricultural system models and 2) inadequate knowledge systems that effectively communicate model results to society. We argue that these limitations are greater obstacles to progress than gaps in conceptual theory or available methods for using system models. New initiatives on open data show promise for addressing the data problem, but there also needs to be a cultural change among agricultural researchers to ensure that data for addressing the range of Use Cases are available for future model improvements and applications. We conclude that multiple platforms and multiple models are needed for model applications for different purposes. The Use Cases provide a useful framework for considering capabilities and limitations of existing models and data.

Livestock models↗

Shadow Evaluation of the ATD-2 Phase 3Trajectory Option Set Reroute Capability in the North Texas Metroplex

This paper presents results of NASA’s Airspace Technology Demonstration 2 Phase 3 Trajectory Option Set reroute capability designed to resolve a demand capacity imbalance along the terminal airspace boundary. We focus on Candidate flights generated during the Stormy 2020 Shadow Evaluation which was the result of using the system to passively collect predictions for each flight at the OUT event. Benefit metrics associated with the predictions are defined for the individual rerouted flight and also the system-wide savings. Candidate flights are grouped into three distinct use cases and the benefit mechanism is explained for each use case along with illustrative data. Analysis of the different use cases shed light on the underlying causes of the reroute opportunities. Lessons learned from the Stormy 2020 Shadow Evaluation including the importance of reroutes during recovery from Severe Weather Avoidance Programs and also reroutes in the absence of terminal airspace constraints will be incorporated into the Phase 3 Field Evaluation in 2021 to maximize reroute opportunities.

Airspace Technology Demonstration 2↗

Preliminary Study of Alternative Propellant Performance for a CNTR

Centrifugal Nuclear Thermal Propulsion is an advanced propulsion concept engine which utilizes a bubble through nuclear reactor to directly heat the propellent, containing the liquid fuel in rotating cylinders using centrifugal force. Past studies have almost exclusively focused on hydrogen propellant configurations of the engine with a theoretical performance of 1800 seconds specific impulse. Recent interest in alternative propellants has created a use case for using storable propellants at the cost of lower performance. Most notably ammonia, methane, and propane. The object of this work is to down select viable alternative propellants for use in a CNTR.

Mitchell Schroll↗

Enabling Innovative Research on the International Space Station to Solve the Challenges of A Human Mission to Mars: Results of the ISS4Mars International Workshops 2020–2021

During the ISS4Mars workshops in 2020–2021, personnel from the International Space Station (ISS) partner agencies convened to reflect on scenarios for how the ISS could be used and its operations possibly modified to simulate aspects of a human mission to Mars. Scientific leaders, operations experts, crewmembers, managers, and flight surgeons discussed the five hazards of human spaceflight—gravity transitions, radiation, isolation and confinement, distance from Earth, and hostile closed environments—and considered how an ISS-based analog of Mars transit could benefit assessments and mitigations of these hazards. A focused writing team then discussed the advantages and disadvantages of each approach identified by the workshop participants before developing a set of eight use cases to consider the feasibility of implementing on the ISS. The writing team also identified the prerequisites needed, including ground analog studies simulating a mission to Mars required to verify measurements and procedures, before testing could begin on the ISS. Five of the use cases were considered feasible to assess in simulations using an ISS-based analog of Mars transit if some ground rules and assumptions were met. These five use cases were Earth-independent medical operations, Earth-independent integrated operations, life support and food for a one year duration, lower-body negative pressure as a countermeasure against the effects of exposure to microgravity, and fitness levels after landing. In addition, three more extensive interventions—extended Mars surface operations, a small-volume transit analog, and artificial gravity—were deemed unfeasible for testing on the ISS. Experience gained from the five use cases executed on the ISS may help answer some of the questions in the deferred scenarios, or it may be possible to complete them on another platform (e.g. commercial space station, lunar habitat). Simulating conditions during a Mars mission on the ISS will afford higher fidelity for assessing multiple integrated hazards of human spaceflight, however, ground analogs of Mars missions can be used to ensure effective measures and experimental design before testing begins on the ISS. The strategic concepts refined as part of these workshops were brought to a multilateral forum, Mulitlateral Human Research Planel for Exploration (MHRPE), where ISS partner agencies are now discussing implementation plans to provide new opportunities to use the ISS to prepare for deep space exploration over the coming decade. In this publication we present a summary of the international strategic plans for future research that will enable operations, software, and countermeasures to be developed that will reduce the risk to humans during future crewed missions to Mars.

Human space exploration↗

Transfer impedance measurements of the space shuttle Solid Rocket Motor (SRM) joints, wire meshes and a carbon graphite motor case

Using three different current injection methods and a simple voltage probe, transfer impedances for Solid Rocket Motor (SRM) joints, wire meshes, aluminum foil, Thorstrand and a graphite composite motor case were measured. In all cases, the surface current distribution for the particular current injection device was calculated analytically or by finite difference methods. The results of these calculations were used to generate a geometric factor which was the ratio of total injected current to surface current density. The results were validated in several ways. For wire mesh measurements, results showed good agreement with calculated results for a 14 by 18 Al screen. SRM joint impedances were independently verified. The filiment wound case measurement results were validated only to the extent that their curve shape agrees with the expected form of transfer impedance for a homogeneous slab excited by a plane wave source.

Papazian, Peter B.↗

Identification and Development of Coordination Procedures Between Upper Class E Traffic Management (ETM) and Surrounding Air Traffic Operations

A recent interest in novel, non-traditional vehicles / missions that plan to operate in Upper Class E (UCE) airspace at or above 60,000 ft has led to efforts by NASA, FAA and the stakeholder communities to research and develop a new concept called Upper Class E Traffic Management (ETM). ETM concept proposes to handle the influx of diverse traffic mix around FL600 and above, utilizing a new traffic management infrastructure, supported by federated service suppliers that are developed by the community stakeholders, for coordinating, monitoring, and executing vehicle operational intent in a designated airspace called ETM Cooperative Area (CA). ETM vehicles are generally expected to reach and operate in ETM CA by first transiting through Class A airspace and potentially through UCE airspace that sits outside of ETM CA. In this paper, a set of use cases have been identified and step-by-step procedures have been developed to handle nominal transitions of ETM vehicles between these operational areas, as well as additional use cases and procedures for authorization and termination of ETM CAs in Class A and/or UCE airspace. The overall research effort in this paper has revealed potential challenges and open questions related to these use cases, especially for the interactions between ETM CA and UCE in both vehicle transition and ETM CA authorization scenarios. The use cases and procedures developed in this paper will inform future ETM integration efforts, as well as research and development into decision support tools needed for the integration.

Upper Class E Traffic Management (ETM)↗

XTCE (XML Telemetric and Command Exchange) Standard Making It Work at NASA. Can It Work For You?

The XML Telemetric and Command Exchange (XTCE) standard is intended as a way to describe telemetry and command databases to be exchanged across centers and space agencies. XTCE usage has the potential to lead to consolidation of the Mission Operations Center (MOC) Monitor and Control displays for mission cross-support, reducing equipment and configuration costs, as well as a decrease in the turnaround time for telemetry and command modifications during all the mission phases. The adoption of XTCE will reduce software maintenance costs by reducing the variation between our existing mission dictionaries. The main objective of this poster is to show how powerful XTCE is in terms of interoperability across centers and missions. We will provide results for a use case where two centers can use their local tools to process and display the same mission telemetry in their MOC independently of one another. In our use case we have first quantified the ability for XTCE to capture the telemetry definitions of the mission by use of our suite of support tools (Conversion, Validation, and Compliance measurement). The next step was to show processing and monitoring of the same telemetry in two mission centers. Once the database was converted to XTCE using our tool, the XTCE file became our primary database and was shared among the various tool chains through their XTCE importers and ultimately configured to ingest the telemetry stream and display or capture the telemetered information in similar ways.Summary results include the ability to take a real mission database and real mission telemetry and display them on various tools from two centers, as well as using commercially free COTS.

CCSDS↗

CLINICAL DECISION SUPPORT: PATH TO FUNCTIONAL REQUIREMENTS

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data and crew time), limited options for evacuation and those associated with delayed or constrained communications, all of which demand greater crew autonomy. Specifically, as the communication delays intensify the further we explore space, the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will be key to mission continuation and success. To augment the requisite knowledge, skills and abilities (KSAs) of a time-constrained crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution that would facilitate, guide and inform Earth-independent medical operations, while assisting crewmembers through various clinical presentations. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit. ExMC is actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses gap Medical-701 within the Inflight Medical Conditions risk: “Enhance medical capabilities within an exploration medical system.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology continues to advance this decade and beyond. Hence, data, software and computational resources will play an essential and synergistic role in maintaining crew health, wellness and performance in deep space missions. The focus of the CDS project is to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance and medical care during exploration missions. The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/databases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that incorporate work from collaborators yet maintain a flexible platform for integrating new technology in the future. In fiscal year 2021 (FY21), the CDS project identified requirements through two primary mechanisms: (i) the development of software implementation prototypes and (ii) the application of systems engineering processes. The CDS project developed and tested a series of increasingly complex system prototypes that were based on use cases derived from the CDSS concept of operations (ConOps). These software implementations yielded insights on CDSS functionality as well as lessons learned that provided the initial requirements for CDSS capability. By applying a systems engineering (SE) approach, medical scenarios provided in the ConOps and the use cases for software implementation underwent functional decomposition to identify CDSS functionality. Also, systems-based modeling language (SysML) tools such as activity diagrams were developed from the same ConOps and use cases to identify CDSS functionality. The lessons learned from software implementation defined both specific requirements and broad areas of requirements. Within these defined broad requirement areas, further analysis of the SE products identified specific capability that resulted in the final functional requirements. In summary, the software prototypes, functional decomposition of the ConOps and use cases, and SysML diagrams provided the basis for the CDSS requirements developed in FY21. In the upcoming year, these requirements will be refined for their final ExMC baseline review in latter FY22.

clinical decision support↗

Clinical Decision Support: Path to Functional Requirements

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data and crew time), limited options for evacuation and those associated with delayed or constrained communications, all of which demand greater crew autonomy. Specifically, as the communication delays intensify the further we explore space, the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will be key to mission continuation and success. To augment the requisite knowledge, skills and abilities (KSAs) of a time-constrained crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution that would facilitate, guide and inform Earth-independent medical operations, while assisting crewmembers through various clinical presentations. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit. ExMC is actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses gap Medical-701 within the Inflight Medical Conditions risk: “Enhance medical capabilities within an exploration medical system.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology continues to advance this decade and beyond. Hence, data, software and computational resources will play an essential and synergistic role in maintaining crew health, wellness and performance in deep space missions. The focus of the CDS project is to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance and medical care during exploration missions. The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/databases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that incorporate work from collaborators yet maintain a flexible platform for integrating new technology in the future. In fiscal year 2021 (FY21), the CDS project identified requirements through two primary mechanisms: (i) the development of software implementation prototypes and (ii) the application of systems engineering processes. The CDS project developed and tested a series of increasingly complex system prototypes that were based on use cases derived from the CDSS concept of operations (ConOps). These software implementations yielded insights on CDSS functionality as well as lessons learned that provided the initial requirements for CDSS capability. By applying a systems engineering (SE) approach, medical scenarios provided in the ConOps and the use cases for software implementation underwent functional decomposition to identify CDSS functionality. Also, systems-based modeling language (SysML) tools such as activity diagrams were developed from the same ConOps and use cases to identify CDSS functionality. The lessons learned from software implementation defined both specific requirements and broad areas of requirements. Within these defined broad requirement areas, further analysis of the SE products identified specific capability that resulted in the final functional requirements. In summary, the software prototypes, functional decomposition of the ConOps and use cases, and SysML diagrams provided the basis for the CDSS requirements developed in FY21. In the upcoming year, these requirements will be refined for their final ExMC baseline review in latter FY22.

Clinical decision support↗

The AIRNOISE-UAM Tool and its Application to ATM-X

The noise disruption caused by Urban Air Mobility (UAM) vehicles will be a major factor in public acceptance of UAM. The noise exposure caused by fixed-wing aircraft and helicopters is predicted using Aviation Environment and Design Tool (AEDT) software at the airport. The base noise is calculated by interpolation or extrapolation of Noise-Power-Distance (NPD) database in the AEDT. In this presentation, a new noise prediction tool "AIRNOISE-UAM" is developed with a new NPD database for eVTOL vehciles in collaboration with a RVLT team. The noise exposure results have been verified with those from AEDT. Lastly, we demonstrate two use cases of AIRNOISE-UAM to the ATM-X project. The first use case is to develop noise exposure maps for FAA UAM compliance planning. The sceond use case is to develop noise-aware flight route planning algorithm.

Urban Air Mobility↗

Deriving Earth Science Data Analytics Requirements

Data Analytics applications have made successful strides in the business world where co-analyzing extremely large sets of independent variables have proven profitable. Today, most data analytics tools and techniques, sometimes applicable to Earth science, have targeted the business industry. In fact, the literature is nearly absent of discussion about Earth science data analytics. Earth science data analytics (ESDA) is the process of examining large amounts of data from a variety of sources to uncover hidden patterns, unknown correlations, and other useful information. ESDA is most often applied to data preparation, data reduction, and data analysis. Co-analysis of increasing number and volume of Earth science data has become more prevalent ushered by the plethora of Earth science data sources generated by US programs, international programs, field experiments, ground stations, and citizen scientists.Through work associated with the Earth Science Information Partners (ESIP) Federation, ESDA types have been defined in terms of data analytics end goals. Goals of which are very different than those in business, requiring different tools and techniques. A sampling of use cases have been collected and analyzed in terms of data analytics end goal types, volume, specialized processing, and other attributes. The goal of collecting these use cases is to be able to better understand and specify requirements for data analytics tools and techniques yet to be implemented. This presentation will describe the attributes and preliminary findings of ESDA use cases, as well as provide early analysis of data analytics toolstechniques requirements that would support specific ESDA type goals. Representative existing data analytics toolstechniques relevant to ESDA will also be addressed.

data analytics↗

Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions

To achieve NASA’s Artemis program mission objectives a high level of autonomy and ubiquitous autonomy throughout the systems that are being developed will be necessary. The autonomous systems of Artemis will require a distributed autonomy capability, with autonomous systems organized functionally in a hierarchical architecture, where systems at higher levels of the hierarchy have authority over systems at lower levels. The challenge of developing autonomy technologies and concepts of operations for Artemis has been undertaken by the NASA Gateway Working Group. This group has developed requirements, architectures, concepts of operations, and interface control documents, in the context of a hierarchical distributed architecture that includes the following: a Vehicle System Manager (VSM) that autonomously manages the entire Gateway; Module System Managers (MSMs) that autonomously manage each module; and System Managers (SMs) that autonomously manage systems within a module(i.e. ECLSS).A substantially high level of autonomy needs to be achieved by each element of the hierarchy (VSM, MSM, SM)to meet requirements for uncrewed operations; this includes conditions that will have minimal and/or delayed ground intervention (i.e. requirements for sustainability for months of operation without crew or ground support). To advance an implementation of this autonomy design (Gateway Autonomy Design –GAD), a collaboration was established between the Autonomous Systems Laboratory (ASL) at NASA Stennis Space Center and Lockheed Martin. The objectives of this partnership were the following: (1)to implement autonomy at the VSM, MSM, and SM levels;(2) to implement communications among a VSM, 2 MSMs, ORION (a visiting vehicle somewhat equivalent to a module) and 1 SM (a power system), and (3) test autonomous operations with representative use cases. A SM backed by a high-fidelity simulation was created to facilitate demonstrations of use cases that originated in a system of a module. Communication between the VSM and MSMs was implemented according to Concepts of Operations and Interface Control Documents (ICDs). Demonstrations were conducted to address nominal and off-nominal operations and multi-module interactions with VSM. Additionally, user interfaces were created to provide awareness about ongoing processes and results while enhancing the demonstration. Demonstrations included the following use cases: (1)Orion as visiting vehicle registers with VSM;(2) VSM reschedules a module’s timelines when another module’s MSM task fails; and (3) a module’s Power System Manager (PSM) standalone demonstration that included component failure diagnostics, tracing component failure to effected components, which in turn, reports failure information up to the VSM for acknowledgement and display. This paper will describe the detailed technology and autonomous systems developed, and the integrated multi-module demonstrations conducted. Also, challenges that must be met to fully implement the GAD defined by Gateway will be addressed.

Autonomous Systems↗

Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions

To achieve NASA’s Artemis program mission objectives a high level of autonomy that is ubiquitous throughout the systems that are being developed will be necessary. The autonomous systems of Artemis will require a distributed autonomy capability, with autonomous systems organized functionally in a hierarchical architecture, where systems at higher levels of the hierarchy have authority over systems at lower levels. The challenge of developing autonomy technologies and Concepts of Operations (ConOps) for Artemis has been undertaken by the NASA Gateway Working Group. This group has developed requirements, architectures, ConOps, and interface control documents (ICDs), in the context of a hierarchical distributed architecture that includes the following: a Vehicle System Manager (VSM) that autonomously manages the entire Gateway; Module System Managers (MSMs) that autonomously manage each module; and System Managers (SMs) that autonomously manage systems within a module (i.e. ECLSS). A substantially high level of autonomy needs to be achieved by each element of the hierarchy (VSM, MSM, SM) to meet requirements for uncrewed operations; this includes conditions that will have minimal and/or delayed ground intervention (i.e. requirements for sustainability for months of operation without crew or ground support). To advance an implementation of this autonomy design (Gateway Autonomy Design – GAD), a collaboration was established between the Autonomous Systems Laboratory (ASL) at NASA Stennis Space Center and Lockheed Martin. The objectives of this partnership were the following: (1) to implement autonomy at the VSM, MSM, and SM levels; (2) to implement communications among a VSM, 2 MSMs, ORION (a visiting vehicle somewhat equivalent to a module) and 1 SM (a power system), and (3) test autonomous operations with representative use cases. A SM backed by a high-fidelity simulation was created to facilitate demonstrations of use cases that originated in a system of a module. Communication between the VSM and MSMs was implemented according to Concepts of Operations and Interface Control Documents (ICDs). Demonstrations were conducted to address nominal and off-nominal operations and multi-module interactions with the VSM. Additionally, user interfaces were created to provide awareness about ongoing processes and results while enhancing the demonstration. Demonstrations included the following use cases: (1) Orion as visiting vehicle registers with VSM; (2) VSM reschedules a module’s timelines when another module’s MSM task fails; and (3) a module’s Power System Manager (PSM) demonstration that included component failure diagnostics, tracing component failure to effected components, which in turn, reports failure information up to the VSM for acknowledgement and display. This paper will describe the detailed technology and autonomous systems developed, and the integrated multi-module demonstrations conducted. Also, challenges that must be met to fully implement the GAD defined by Gateway will be addressed.

Fernando Figueroa↗

Development of an Airspace Simulation and Modeling Tool for Enhanced Spectrum Management

The emergence of new aerial vehicles into the National Airspace System creates an increased demand for aeronautical communications to support aviation operations. However, the issue of spectrum scarcity remains an ever-present concern, and the growing demand cannot be supported using existing spectrum allocation strategies. As a result, a new spectrum management approach is required, and the National Aeronautics and Space Administration (NASA) is investigating advanced concepts to modernize the management and use of aviation spectrum by leveraging the latest advancements in wireless communications, big data and machine learning. This research proposes an autonomous spectrum allocation concept, which allocates communications resources, such as spectrum and power, based on the predicted communications and air traffic demands throughout the airspace, as opposed to the use of fixed allocations as is done today. This approach will result in improved spectrum utilization efficiency and enhanced airspace capacity. The autonomous spectrum allocation concept decomposes into three research areas: demand prediction, resource allocation, and use case evaluation. As part of the use case evaluation effort, a modeling and simulation capability is currently under development. This simulation capability includes the implementation of various features, including visualization of both live or virtually-generated airspace traffic, simulation scenario development, simulation management with data collection, and flight plan creation with corresponding trajectory generation. This modeling and simulation capability will continue to evolve as new and advanced airspace applications are introduced into existing and emerging operational environments.

Eric J. Knoblock↗

Vertical wind velocities from superpressure balloons - A case study using Eole data

A method for determining vertical wind velocities using the pressure- and temperature-change data from superpressure (constant-density) balloons was proposed in an earlier paper (1975). In this paper, we present a case study using actual balloon data to test the method. Data from the Eole balloon experiment were used to estimate the sign of vertical wind velocities, as well as the horizontal velocity field, near 200 mb over Australia. The resulting patterns of vertical velocity compare favorably with satellite pictures and with current models of flow near jet-stream maxima. Additionally, this study provides evidence that areas of vertical motion in the troposphere extend upward into the lower stratosphere without changing sign.

Banta, R. M.↗

Innovative Approaches to Using the International Space Station as a Mars Transit Analog

Human research on the International Space Station (ISS) crew has made significant advances in understanding of the effects of physiology on human health in space missions. However, ISS has not been as suitable for research on other hazards of human spaceflight such as isolation and communications delay. NASA recently completed a special assessment of whether modifications could be made to operations or facilities so that ISS could be used more effectively as an analog to simulate long-duration crew missions beyond low earth orbit. A cross-disciplinary team met to identify concept of operations, trade spaces, challenges, and opportunities to making ISS more operationally relevant as a Mars transit mission analog, and the results and implementation plans are summarized in this manuscript. In addition to the use case of 12-month missions (already in planning by the NASA ISS Program to bound expected Mars transit durations), three new use cases where ISS could provide valuable high-fidelity experience were identified. (1) Testing of operations procedures and medical care could be enhanced by demonstrating crew handling a simulated medical event in microgravity, autonomously, and with significant communications delay. (2) Isolation and confinement effects of deep space transit could be studied on ISS to validate current habitable volume requirements for Mars transit as well as provide context for evaluating the results of the extensive ground-based simulations in HERA and NEK. A trade study of possible operational and hardware changes that would make ISS applicable to these use cases was completed. (3) Surface operations after the physiological deconditioning of a long transit could be conducted to validate crew ability to perform critical ground tasks after 6-month Mars transit and aid in conceptual design of Mars surface element architectures. Each of the case studies includes a trade space between operational impacts on nominal ISS activities and degree of fidelity. A phased approach to implementation means that several "quick start" activities can be done in 2019-2020 at the same time as planning continues for more complex exploration analog options beginning as early as 2022. The team determined that many of these quick-start tasks could be done with available assets, entirely independent of other exploration system development timelines (such as Orion, Space Launch System). The consideration of the full suite of human spaceflight capabilities in the lunar vicinity can also be included as each step in human exploration serves as a simulation opportunity for some aspect of subsequent missions. Further discussions of options with the international community are critical for considering the benefits as well as impacts of simulation activities on ISS, as well as to better formulate future mission architectures.

Robinson, Julie A.↗