Search NASA⌕ Search

SEARCH · Search NASA

Results for “program architectures”

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,765 records · Page 98

Exploring the interoperability of remote GPGPU virtualization using rCUDA and directive-based programming models

Directive-based programming models, such as OpenMP, OpenACC, and OmpSs, enable users to accelerate applications by using coprocessors with little effort. These devices offer significant computing power, but their use can introduce two problems: an increase in the total cost of ownership and their underutilization because not all codes match their architecture. Remote accelerator virtualization frameworks address those problems. In particular, rCUDA provides transparent access to any graphic processor unit installed in a cluster, reducing the number of accelerators and increasing their utilization ratio. Joining these two technologies, directive-based programming models and rCUDA, is thus highly appealing. In this work, we study the integration of OmpSs and OpenACC with rCUDA, describing and analyzing several applications over three different hardware configurations that include two InfiniBand interconnections and three NVIDIA accelerators. Our evaluation reveals favorable performance results, showing low overhead and similar scaling factors when using remote accelerators instead of local devices.

97 MATHEMATICS AND COMPUTING↗

Synthesis Characterization and Electrospinning of Architecturally-Discrete Isotactic-Atactic-Isotactic Triblock Stereoblock Polypropene Elastomers

Stereochemically homogeneous and architecturally discrete isotactic-atactic-isotactic triblock stereoblock PP (sbPP) thermoplastic elastomers in which the block lengths for each domain type can be varied in programmed fashion while keeping total molecular weight and molecular weight polydispersity the same has been achieved for the first time. Five sbPP materials were prepared: sbPP-1 (6iso-88a-6iso), total isotactic content, 12%; sbPP-2 (12iso-76a-12iso), 24%; sbPP-3 (18iso-64a-18iso), 36%; sbPP-4 (24iso-50a-26iso), 50%; and sbPP-5 (20iso-64a-33iso), 53%. All five sbPP materials were successfully processed by solution-based electrospinning to provide fiberous mats with feature sizes on the nanometer to micrometer length scale. Extensive characterization by analytical (SEM, AFM, tensile testing, DSC,), spectroscopic (FT-IR, FT-Raman), and synchrotron X-ray diffraction techniques of bulk samples, electrospun fibers and solvent cast films of the sbPP samples revealed well-defined trends in elastic properties, morphologies and crystallinity that are associated with a higher degree of crystallinity that emerges with higher isotactic contents. The results of these investigations serve to provide an important foundation that can be used to potentially identify the best combination of stereoerror level incorporation within the isotactic domains and total isotactic content for these architecturally discrete sb-PP materials for maximizing desirable elastomeric traits and solution-based (electrospinning) processing methodology with the goal of achieving the best possible structural forms for potential product applications.

36 MATERIALS SCIENCE↗

Projected Urban Morphology of the Los Angeles Area by the Year 2100

This dataset provides projections of urban building morphologies for the Los Angeles urban area at 30-meter spatial resolution. It contains 192 raster files that detail two primary building attributes: building footprint fractions (ranging from 0 to 1) and average building heights (ranging from 0 to 75 meters). The projections account for a wide range of future pathways, covering two Shared Socioeconomic Pathway (SSP) scenarios (SSP3 and SSP5), two population scenarios, two developed land intensification scenarios, and four distinct levels of intensification. The dataset was created using dual Generative Adversarial Networks (GANs) trained on 2015 land cover and building properties from the National Land Cover Database (NLCD) and Model America datasets. Supporting information on the dataset has been described in the LAUrbanAreaMorphologyProjections2100_README.txt file.

Pandey, Bhartendu↗

Requirements analysis notebook for the flight data systems definition in the Real-Time Systems Engineering Laboratory (RSEL)

A hybrid requirements analysis methodology was developed, based on the practices actually used in developing a Space Generic Open Avionics Architecture. During the development of this avionics architecture, a method of analysis able to effectively define the requirements for this space avionics architecture was developed. In this methodology, external interfaces and relationships are defined, a static analysis resulting in a static avionics model was developed, operating concepts for simulating the requirements were put together, and a dynamic analysis of the execution needs for the dynamic model operation was planned. The systems engineering approach was used to perform a top down modified structured analysis of a generic space avionics system and to convert actual program results into generic requirements. CASE tools were used to model the analyzed system and automatically generate specifications describing the model's requirements. Lessons learned in the use of CASE tools, the architecture, and the design of the Space Generic Avionics model were established, and a methodology notebook was prepared for NASA. The weaknesses of standard real-time methodologies for practicing systems engineering, such as Structured Analysis and Object Oriented Analysis, were identified.

Wray, Richard B.↗

Exascale Hardware Architectures Working Group

The ASC Exascale Hardware Architecture working group is challenged to provide input on the following areas impacting the future use and usability of potential exascale computer systems: processor, memory, and interconnect architectures, as well as the power and resilience of these systems. Going forward, there are many challenging issues that will need to be addressed. First, power constraints in processor technologies will lead to steady increases in parallelism within a socket. Additionally, all cores may not be fully independent nor fully general purpose. Second, there is a clear trend toward less balanced machines, in terms of compute capability compared to memory and interconnect performance. In order to mitigate the memory issues, memory technologies will introduce 3D stacking, eventually moving on-socket and likely on-die, providing greatly increased bandwidth but unfortunately also likely providing smaller memory capacity per core. Off-socket memory, possibly in the form of non-volatile memory, will create a complex memory hierarchy. Third, communication energy will dominate the energy required to compute, such that interconnect power and bandwidth will have a significant impact. All of the above changes are driven by the need for greatly increased energy efficiency, as current technology will prove unsuitable for exascale, due to unsustainable power requirements of such a system. These changes will have the most significant impact on programming models and algorithms, but they will be felt across all layers of the machine. There is clear need to engage all ASC working groups in planning for how to deal with technological changes of this magnitude. The primary function of the Hardware Architecture Working Group is to facilitate codesign with hardware vendors to ensure future exascale platforms are capable of efficiently supporting the ASC applications, which in turn need to meet the mission needs of the NNSA Stockpile Stewardship Program. This issue is relatively immediate, as there is only a small window of opportunity to influence hardware design for 2018 machines. Given the short timeline a firm co-design methodology with vendors is of prime importance.

97 MATHEMATICS AND COMPUTING↗

On-demand Command and Control of ASTERIA with Cloud-based Ground Station Services

ASTERIA (Arcsecond Space Telescope Enabling Research in Astrophysics) was a 6-unit CubeSat technology demonstration mission that deployed from the International Space Station on November 20th, 2017. After successfully completing its 90-day primary mission that demonstrated arcsecond-level line-of-sight pointing and focal plane thermal stability for exoplanet detection, it entered an extended mission performing onboard software demonstrations to mature technology both in space and on the ground. One of the technologies was a completely cloud-based ground system leveraging Amazon Web Services (AWS) Ground Station service. Announced in December 2018 and launched in May 2019, AWS Ground Station is a fully managed ground station service that aims to reduce the overhead associated with developing and maintaining ground system infrastructure throughout the mission lifecycle. AWS Ground Station makes available the suite of features required for any ground system in support of low-Earth orbit (LEO) and medium-Earth Orbit (MEO) satellite operations on-demand and without setting up or maintaining long-term contracts. Charges are incurred on a per-minute basis for antenna usage during scheduled tracks. Support is available for S-band uplink and downlink, along with X-band narrowband and wideband downlink. Missions that use the service may reserve tracks with any licensed AWS Ground Station antennas located across each service region and have direct access to any AWS services in support of mission operations. The cloud-based architecture built around the AWS Ground Station service greatly enhanced ASTERIA mission operations by enabling end-to-end pass automation, on-demand contact scheduling and contingency planning, along with more efficient data downlink through station availability and station-tostation handovers. It incorporated open-source software, particularly NASA's AMMOS Instrument Toolkit (AIT) and Open Mission Control Technologies (OpenMCT), along with the AWS application programming interfaces (API) to the Ground Station, Elastic Compute Cloud (EC2) and Simple Storage Service (S3) services. After showcasing operability in August 2019, the team continued using and improving this novel ground system architecture until the end of mission in December 2019. This paper describes the cloud-based ground system, how it was designed, tested, and evaluated with an inorbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

On-demand Command and Control of ASTERIA with Cloud-based Ground Station Services

ASTERIA (Arcsecond Space Telescope Enabling Research in Astrophysics) was a 6-unit CubeSat technology demonstration mission that deployed from the International Space Station on November 20th, 2017. After successfully completing its 90-day primary mission that demonstrated arcsecond-level line-of-sight pointing and focal plane thermal stability for exoplanet detection, it entered an extended mission performing onboard software demonstrations to mature technology both in space and on the ground. One of the technologies was a completely cloud-based ground system leveraging Amazon Web Services (AWS) Ground Station service.Announced in December 2018 and launched in May 2019, AWS Ground Station is a fully managed ground station service that aims to reduce the overhead associated with developing and maintaining ground system infrastructure throughout the mission lifecycle. AWS Ground Station makes available the suite of features required for any ground system in support of low-Earth orbit (LEO) and medium-Earth Orbit (MEO) satellite operations on-demand and without setting up or maintaining long-term contracts. Charges are incurred on a per-minute basis for antenna usage during scheduled tracks. Support is available for S-band uplink and downlink, along with X-band narrowband and wideband downlink. Missions that use the service may reserve tracks with any licensed AWS Ground Station antennas located across each service region and have direct access to any AWS services in support of mission operations.The cloud-based architecture built around the AWS Ground Station service greatly enhanced ASTERIA mission operations by enabling end-to-end pass automation, on-demand contact scheduling and contingency planning, along with more efficient data downlink through station availability and station-to-station handovers. It incorporated open-source software, particularly NASA's AMMOS Instrument Toolkit (AIT) and Open Mission Control Technologies (OpenMCT), along with the AWS application programming interfaces (API) to the Ground Station, Elastic Compute Cloud (EC2) and Simple Storage Service (S3) services. After showcasing operability in August 2019, the team continued using and improving this novel ground system architecture until the end of mission in December 2019. This paper describes the cloud-based ground system, how it was designed, tested, and evaluated with an in-orbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

Cooperative Data Sharing: Simple Support for Clusters of SMP Nodes

Libraries like PVM and MPI send typed messages to allow for heterogeneous cluster computing. Lower-level libraries, such as GAM, provide more efficient access to communication by removing the need to copy messages between the interface and user space in some cases. still lower-level interfaces, such as UNET, get right down to the hardware level to provide maximum performance. However, these are all still interfaces for passing messages from one process to another, and have limited utility in a shared-memory environment, due primarily to the fact that message passing is just another term for copying. This drawback is made more pertinent by today's hybrid architectures (e.g. clusters of SMPs), where it is difficult to know beforehand whether two communicating processes will share memory. As a result, even portable language tools (like HPF compilers) must either map all interprocess communication, into message passing with the accompanying performance degradation in shared memory environments, or they must check each communication at run-time and implement the shared-memory case separately for efficiency. Cooperative Data Sharing (CDS) is a single user-level API which abstracts all communication between processes into the sharing and access coordination of memory regions, in a model which might be described as "distributed shared messages" or "large-grain distributed shared memory". As a result, the user programs to a simple latency-tolerant abstract communication specification which can be mapped efficiently to either a shared-memory or message-passing based run-time system, depending upon the available architecture. Unlike some distributed shared memory interfaces, the user still has complete control over the assignment of data to processors, the forwarding of data to its next likely destination, and the queuing of data until it is needed, so even the relatively high latency present in clusters can be accomodated. CDS does not require special use of an MMU, which can add overhead to some DSM systems, and does not require an SPMD programming model. unlike some message-passing interfaces, CDS allows the user to implement efficient demand-driven applications where processes must "fight" over data, and does not perform copying if processes share memory and do not attempt concurrent writes. CDS also supports heterogeneous computing, dynamic process creation, handlers, and a very simple thread-arbitration mechanism. Additional support for array subsections is currently being considered. The CDS1 API, which forms the kernel of CDS, is built primarily upon only 2 communication primitives, one process initiation primitive, and some data translation (and marshalling) routines, memory allocation routines, and priority control routines. The entire current collection of 28 routines provides enough functionality to implement most (or all) of MPI 1 and 2, which has a much larger interface consisting of hundreds of routines. still, the API is small enough to consider integrating into standard os interfaces for handling inter-process communication in a network-independent way. This approach would also help to solve many of the problems plaguing other higher-level standards such as MPI and PVM which must, in some cases, "play OS" to adequately address progress and process control issues. The CDS2 API, a higher level of interface roughly equivalent in functionality to MPI and to be built entirely upon CDS1, is still being designed. It is intended to add support for the equivalent of communicators, reduction and other collective operations, process topologies, additional support for process creation, and some automatic memory management. CDS2 will not exactly match MPI, because the copy-free semantics of communication from CDS1 will be supported. CDS2 application programs will be free to carefully also use CDS1. CDS1 has been implemented on networks of workstations running unmodified Unix-based operating systems, using UDP/IP and vendor-supplied high- performance locks. Although its inter-node performance is currently unimpressive due to rudimentary implementation technique, it even now outperforms highly-optimized MPI implementation on intra-node communication due to its support for non-copy communication. The similarity of the CDS1 architecture to that of other projects such as UNET and TRAP suggests that the inter-node performance can be increased significantly to surpass MPI or PVM, and it may be possible to migrate some of its functionality to communication controllers.

DiNucci, David C.↗

Crew Health and Performance (CHP) Technology Roadmaps

The Environmental Control and Life Support System (ECLSS) – Crew Health and Performance (CHP) Systems Capability Leadership Team (SCLT) is a community of practice (not a funded program) sponsored by Headquarters to develop, retain, and infuse the ECLSS and CHP capabilities necessary to enable the human exploration of the Moon and Mars through the integration and empowerment of experts across NASA, other government agencies, commercial industry, and academia. The goals of the SCLT are as follows: Use the Architecture Definition Document use cases and functions to identify gaps in NASA’s current technological capabilities to meet Agency objectives and develop strategies and roadmaps for closing such gaps Make technical/strategic recommendations on ECLSS and CHP technology development efforts and investments for PPBE, acquisition strategies, and leveraging NASA’s critical capabilities Establish key performance parameters and participate in key program and project reviews Maintain cognizance of relevant ECLSS and CHP national and international technology activities in government, industry, and academia, specifically, emerging innovations and technologies, trends, and opportunities Coordinate with commercial and international partners to identify areas of mutual interest and cooperation Support future mission and system architecture studies for human exploration This document is intended to be a comprehensive overview of the strategic development plans, or Roadmaps, of key technologies and capabilities identified by the SCLT. Each Roadmap is organized by Capability Gap as the gap name and number appears in STARPort, follows a fiscal year timeline, and displays any additional information on milestones, decision points, or important details on the right-hand side of the page. The Roadmaps should be used to facilitate discussion, decision making, and planning for programs and development projects, but are not expected to accurately depict the details and statuses of the projects and tasks appearing within the plans.

Human Health and Performance↗

Neural network based architectures for aerospace applications

A brief history of the field of neural networks research is given and some simple concepts are described. In addition, some neural network based avionics research and development programs are reviewed. The need for the United States Air Force and NASA to assume a leadership role in supporting this technology is stressed.

Ricart, Richard↗

The Architecture of Mercury - Nevada's Atomic Boom Town: An Architectural Survey of Mercury, Area 23, Nevada National Security Site, Nye County, Nevada (Rev. 1)

The U.S. Department of Energy, National Nuclear Security Administration Nevada Field Office (NNSA/NFO) plans to modernize the Mercury town site at the Nevada National Security Site in Nye County, Nevada, to meet current and future National Weapons Science, Global and Homeland Security Programs, and Environmental Management mission requirements. These plans include anticipated demolitions, consolidations, and rebuilding at Mercury to be an undertaking subject to review under Title 54 U.S.C. § 306108, commonly known as Section 106 of the National Historic Preservation Act, Title 54 U.S.C. §300101, et seq., and its implementing regulations, 36 C.F.R. Part 800. Prior to the present survey, Mercury had not yet been systematically recorded, and therefore an area of approximately 364 hectares (900 acres) was surveyed for architectural resources by the Desert Research Institute. This effort resulted in the identification, recording, and evaluation of the Mercury Historic District (SHPO Resource No. D230), including the identification of its contributing components. This district is recommended eligible to the National Register of Historic Places under Criteria A and C. It is unevaluated under Criteria B and D at this time. The Mercury Historic District contains 154 individual landscapes, buildings, and structures. Of these resources, all except one are recommended as contributing elements of the historic district during its period of significance corresponding to nuclear testing from 1951 through 1992. During most of the Cold War, the land now called the Nevada National Security Site was named the Nevada Test Site.

54 ENVIRONMENTAL SCIENCES↗

Implementing and Evaluating Multithreaded Triad Census Algorithms on the Cray XMT

Commonly represented as directed graphs, social networks depict relationships and behaviors among social entities such as people, groups, and organizations. Social network analysis denotes a class of mathematical and statistical methods designed to study and measure social networks. Beyond sociolo-gy, social network analysis methods are being applied to other types of data in other domains such as bioinformatics, computer networks, national security, and economics. For particular problems, the size of a social network can grow to millions of nodes and tens of millions of edges or more. In such cases, researchers could benefit from the application of social network analysis algorithms on high-performance architectures and systems. The Cray XMT is a third generation multithreaded system based on the Cray XT-3/4 platform. Like most other multithreaded architectures, the Cray XMT is designed to tolerate memory access latencies by switching context between threads. The processors maintain multiple threads of execution and util-ize hardware-based context switching to overlap the memory latency incurred by any thread with the computations from other threads. Due to its memory latency tolerance, the Cray XMT has the poten-tial of significantly improving the execution speed of irregular data-intensive applications such as those found in social network analysis. In this paper, we describe our experiences in developing and optimizing three implementations of a social network analysis method known as triadic analysis to execute on the Cray XMT. The three im-plementations possess different execution complexities, qualities, and characteristics. We evaluate how the various attributes of the codes affect their performance on the Cray XMT. We also explore the effects of different compiler options and execution strategies on the different triadic analysis im-plementations and identify general XMT programming issues and lessons learned.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗

Novel functional and distributed approaches to data analysis available in ROOT

The bright future of particle physics at the Energy and Intensity frontiers poses exciting challenges to the scientific software community. The traditional strategies for processing and analyzing data are evolving in order to (i) offer higher-level programming model approaches and (ii) exploit parallelism to cope with the ever increasing complexity and size of the datasets. This contribution describes how the ROOT framework, a cornerstone of software stacks dedicated to particle physics, is preparing to provide adequate solutions for the analysis of large amount of scientific data on parallel architectures. The functional approach to parallel data analysis provided with the ROOT TDataFrame interface is then characterized. The design choices behind this new interface are described also comparing with other widely adopted tools such as Pandas and Apache Spark. The programming model is illustrated highlighting the reduction of boilerplate code, composability of the actions and data transformations as well as the capabilities of dealing with different data sources such as ROOT, JSON, CSV or databases. Details are given about how the functional approach allows transparent implicit parallelization of the chain of operations specified by the user. The progress done in the field of distributed analysis is examined. In particular, the power of the integration of ROOT with Apache Spark via the PyROOT interface is shown. In addition, the building blocks for the expression of parallelism in ROOT are briefly characterized together with the structural changes applied in the building and testing infrastructure which were necessary to put them in production.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗

Datascope to Enable Earth Independent Medical Operations (EIMO)

BACKGROUND: NASA has amassed sixty years of knowledge and experience relevant to maintenance of crew health and performance in low earth orbit. The Apollo Program introduced the importance of ensuring progressively autonomous operational capability. Earth Independent Medical Operations (EIMO) will require a gradual shift in the balance of medical responsibility, management, and authority from terrestrial to space-based assets. Terrestrial assets will continue to be essential for pre-mission screening and planning in addition to maintenance of crew health and performance. However, new capabilities are needed to enable EIMO and the amount of data required to support these systems, and mitigate the impacts of data transmission delays and reduced bandwidth coupled with lack of cloud-like resources and on-board computing capacity that is currently unclear or operationally insufficient. OVERVIEW: The overall goal of EIMO is to develop artificial intelligence (AI)-based solutions to analyze crew health and performance data utilizing a clinical decision support system (CDSS) to provide crew medical officers (CMO) with the equivalent of real-time, on-board medical consults. The EIMO ecosystem is envisioned as a “system of systems” where embedded reference databases and real-time data streams from multiple input vectors continuously and seamlessly assess crew health and performance. EIMO will be designed to make recommendations to the CMO using multi-modal AI-based natural language processing and machine learning methods with interoperability to push/pull data within and between multiple vehicle and habitat architectures. DISCUSSION: Data flows and storage/retrieval capacity are severely constrained during space missions and the challenges will become even greater during exploration missions. Just as each past program from Mercury to the International Space Station (ISS) required rethinking the interaction between ground-based controllers and space-based crew, so too will future missions to the Moon and Mars. While the NASA High-Performance Spaceflight Computing Processor project aims to increase computational capacity by 100 times over current spaceflight computers, the projected deliverable still lags considerably behind what will be needed to enable an AI-driven CDSS. Restrictions in processing speed and data storage capacity, coupled with transmission bottlenecks and delays, necessitate definition and optimization of an integrated data architecture to enable a progressively autonomous medical capability.

Medical operations↗

Architecture Robustness in NASA’s Moon to Mars Capability Development – FY23 Data Results

In preparation for humanity’s return to the Moon, it is important to advance technologies and capabilities that will allow for sustainability on the lunar surface and prepare for human missions to Mars. As charged in Space Policy Directive-1, NASA’s Artemis program will advance and develop technologies on the lunar surface that can be leveraged towards a safe and successful human round-trip mission to Mars. NASA’s Exploration Systems Development Mission Directorate Capabilities Integration Team (ESDMD CIT) is advancing a continuous effort to identify and map gaps between capabilities and anticipated human spaceflight architecture elements. As upcoming exploration missions approach, the architectural design tradespace increasingly narrows. This paper provides an updated exploration of certain architectural and element design choices for upcoming missions to the Moon and Mars, comparing and contrasting capability gaps and classes of capability gaps that are architecture robust with those that are not. In doing so, we identify certain capabilities as relevant, and therefore robust, across varying architectural possibilities while identifying other capabilities as only applicable to specific architectural pathways. Capabilities that are applicable to multiple elements across the architecture have more architectural breadth because of their increased likelihood of remaining relevant even if changes are made to some elements they are mapped to. Correspondingly, capabilities that are applicable to specific elements across the architecture but are necessary under almost any eventuality have more architectural depth because of their increased likelihood of remaining relevant even if architecture changes are made. One of the key analyses in this paper is an exploration of architecture robustness as a function of capability area, as defined by the NASA Technology Taxonomy. These results are then evaluated and analyzed across human spaceflight architecture elements to gain a greater understanding of the relationships between exploration capabilities and the systems that will eventually be implemented. Additional insights regarding investment strategies are also considered. General conclusions about these relationships are drawn.

Gaps↗

Ares V: Refining a New Heavy Lift Capability

The Ares V cargo launch vehicle represents a significant new national commitment to expand human space exploration beyond low Earth orbit. Viewed more broadly, this new heavy-lift rocket will be an advancement over the national strategic capability lost when the Saturn V program ended more than three decades ago. The Ares V is one of two new launch vehicles being designed by NASA to support U.S. Space Exploration Policy. NASA selected the Ares I crew launch vehicle and the Ares V (Figure 1) during extensive independent and internal architecture and vehicle trade studies to complete the International Space Station, retire the current Space Shuttle fleet, return to the Moon by 2020, and journey to destinations beyond. These vehicles share components derived from the Apollo-era Saturn, Space Shuttle, and contemporary launch vehicle programs to provide safe, affordable, reliable, versatile sustainable space transportation to support national space goals for decades to come.

Creech, Steve↗

Vista/F-16 Multi-Axis Thrust Vectoring (MATV) control law design and evaluation

For the Multi-Axis Thrust Vectoring (MATV) program, a new control law was developed using multi-axis thrust vectoring to augment the aircraft's aerodynamic control power to provide maneuverability above the normal F-16 angle of attack limit. The control law architecture was developed using Lockheed Fort Worth's offline and piloted simulation capabilities. The final flight control laws were used in flight test to demonstrate tactical benefits gained by using thrust vectoring in air-to-air combat. Differences between the simulator aerodynamics data base and the actual aircraft aerodynamics led to significantly different lateral-directional flying qualities during the flight test program than those identified during piloted simulation. A 'dial-a-gain' flight test control law update was performed in the middle of the flight test program. This approach allowed for inflight optimization of the aircraft's flying qualities. While this approach is not preferred over updating the simulator aerodynamic data base and then updating the control laws, the final selected gain set did provide adequate lateral-directional flying qualities over the MATV flight envelope. The resulting handling qualities and the departure resistance of the aircraft allowed the 422nd_squadron pilots to focus entirely on evaluating the aircraft's tactical utility.

Zwerneman, W. D.↗

Human Exploration of Phobos

This study developed, analyzed, and compared mission architectures for human exploration of Mars' Moons within the context of an Evolvable Mars Campaign. METHODS: All trades assumed conjunction class missions to Phobos (approximately 500 days in Mars system) as it was considered the driving case for the transportation architecture. All architectures assumed that the Mars Transit Habitat would remain in a High Mars Orbit with crewmembers transferring between HMO and Phobos in a small crew taxi vehicle. A reference science / exploration program was developed including performance of a standard set of tasks at 55 locations on the Phobos surface. Detailed EVA timelines were developed using realistic flight rules to accomplish the reference science tasks using exploration systems ranging from jetpacks to multi-person pressurized excursion vehicles combined with Phobos surface and orbital (L1, L4/L5, 20km Distant Retrograde Orbit) habitat options. Detailed models of propellant mass, crew time, science productivity, radiation exposure, systems and consumables masses, and other figures of merit were integrated to enable quantitative comparison of different architectural options. Options for pre-staging assets using solar electric propulsion (SEP) vs. delivering all systems with the crew were also evaluated. Seven discrete mission architectures were evaluated. RESULTS: The driving consideration for habitat location (Phobos surface vs. orbital) was radiation exposure, with an estimated reduction in cumulative mission radiation exposure of up to 34% (vs. Mars orbital mission) when the habitat is located on the Phobos surface, compared with only 3-6% reduction for a habitat in a 20km DRO. The exploration utility of lightweight unpressurized excursion vehicles was limited by the need to remain within 20 minutes of Solar Particle Event radiation protection combined with complex GN&C systems required by the non-intuitive and highly-variable gravitational environment. Two-person pressurized excursion vehicles as well as mobile surface habitats offer significant exploration capability and operational benefits compared with unpressurized EVA mobility systems at the cost of increased system and propellant mass. Mechanical surface translation modes (i.e. hopping) were modeled and offer potentially significant propellant savings and the possibility of extended exploration operations between crewed missions. Options for extending the utilization of the crew taxi vehicle were examined, including use as an exploration asset for Phobos surface exploration (when combined with an alternate mobility system) and as an EVA platform, both on Phobos and for contingency EVA on the Mars Transit Habitat. CONCLUSIONS: Human exploration of Phobos offers a scientifically meaningful first step towards human Mars surface missions that develops and validates transportation, habitation, and exploration systems and operations in advance of the Mars landing systems.

Abercromby, Andrew F. J.↗