Search NASA⌕ Search

SEARCH · Search NASA

Results for “Development Efforts”

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 343 records · Page 19

Verification and Validation of High Explosive Reactive Burn Models Implemented in LANL's EAP and LAP Code Base

Reactive burn models represent a significant leap in high explosive (HE) modeling capability. The first generation of engineering models of HE detonation are called programmed burn models and they are largely based on the distance between a prescribed detonation point and each zone in a simulation. There have been many advancements to programmed burn models over the years and when the assumptions upon which they are based are met, a properly tuned programmed burn model can be highly accurate but if any of their assumptions is not met, as is the case for corner turning or weakly initiated HE burn, they will give the wrong answer. Reactive burn models represent an entirely new way of modeling HE burn. They use the local conditions of a zone – e.g. temperature, pressure or density – as calculated by a hydrocode to determine if and when the zone is going to detonate and if so, how rapidly. This difference opens up an entirely new set of capabilities for HE modeling. It makes it possible to accurately and predictively model phenomena like the effect of confinement and the formation of dead zones. Reactive burn models have seen sustained development effort at LANL for at least the last decade but several recent developments make it timely to transition reactive burn models from a research topic to a production tool. The main goal of this milestone is to facilitate and accelerate the adoption of reactive burn as a commonly available modeling option, with recommendations on the resolution that will be required and uncertainties associated with their modeling choices. To achieve this, we have performed verification, validation, and uncertainty quantification (UQ) assessments of AWSD and SURF/SURFplus in xRage and FLAG on a variety of different problems.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗

Interim Report on FY22 ORNL A709 Welding Research and Testing of Production Welds in Support of Developing ASME A709 Code Case Data Package

As part of the Alloy 709 ASME Code Case development effort under the Advanced Reactor Technologies (ART) Program, this work covers the development of the technical basis for weld fabrication and weld qualification of Alloy 709. This report summarizes the Alloy 709 welding research conducted at Oak Ridge National Laboratory (ORNL) in FY 2022. Two new production welds were fabricated on two commercial heats of Alloy 709 of different phosphorus (P) levels using Alloy 709 filler metal with P content less than 20 wppm with gas tungsten arc welding (GTAW). Both production welds successfully passed ASME Section IX weld qualification tests, and this concludes the Alloy 709 welding procedure development to scale up to 2-in thick plates. In FY 2022, we also demonstrated the success in welding of high P commercial Alloy 709 plates with weld wires having higher P content at 30 wppm. A test weld fabricated with the 30 wppm weld wire on the first commercial heat (140 wppm P) passed all weld qualification tests without issues. Additionally, experiment setup and testing procedure of the circular patch weldability test has been developed, for evaluating the P effect in weld wire on solidification cracking susceptibility of Alloy 709 weld, with the preliminary results summarized in this report. Research on further relaxing the P level restriction beyond 30 wppm are planned in FY 2023. The preliminary cross-weld creep tests results continue to show little or no creep strength reduction relative to the base metal.

36 MATERIALS SCIENCE↗

Report on FY 2023 Welding R&D at ORNL in support of ASME Alloy 709 Code Case Development

As part of the Alloy 709 (A709) ASME Code Case development effort under the Advanced Reactor Technologies (ART) Program, this work covers the development of the technical basis for weld fabrication and weld qualification of A709. This report summarizes the A709 welding research conducted at Oak Ridge National Laboratory (ORNL) in FY 2023. One of the focuses of the A709 welding research at ORNL is to relax the restriction of the P content in the A709 filler metal weld wire. In this report, we show the success in welding of high phosphorus (P) commercial A709 plates using A709 weld wires with relaxed P content of 80 wppm. A test weld was fabricated with the 80 wppm weld wire on the first commercial heat A709 base metal with 140 wppm P content using gas tungsten arc welding (GTAW). The test weld passed all weld qualification tests without issues. This study concludes that A709 matching filler metal with moderate amount of P of less than 80 wppm could be used to produce code qualified A709 welds with standard welding process without special treatment. It is recommended that the P level in the weld wire to be kept low to avoid hot cracking. Cross-weld specimens were machined from the two A709 production welds.. Cross welding creep rupture Code Case testing on these two production welds was initiated . The preliminary cross-weld creep tests results continue to show little or no creep strength reduction relative to the base metal.

36 MATERIALS SCIENCE↗

Where there is a wind, there is a way

A shift in USA energy policy from oil or natural gases to thermonuclear fission and solar energy is predicted. A massive diversified energy research and development effort to productively harness the energy in the winds is outlined to develop commercially feasible wind energy conversion systems - considered a form of solar energy - in the near future.

Mosher, C. A.↗

Concepts to Automate Fluid Transfer Capability of Low Impact Docking System (LIDS)

The capability to transfer mass between spacecraft is necessary for many mission scenarios. Docking and berthing operations have enabled fluid, electrical, crew and equipment transfers to some degree on all manned space operations since the Gemini program. The Apollo program performed some sophisticated docking maneuvers to land men on the moon and return them safely to Earth. These programs primarily transferred crew, equipment, and pressurized atmosphere between docked spacecraft. The International Space Station (ISS) U.S. modules are connected by Common Berthing Mechanism (CBM) portals. They provide many feed-through ports for electrical, and fluid transfer between modules, as well as a large diameter crew and equipment tunnel. Fluid and electrical jumpers are manually installed after the CBM sealing surfaces have been securely mated to maintain the pressurized cabin environment. CBM berthing and subsequent fluid transfer capability requires a lengthy manual process involving an active interface that mates with a passive half. The Androgynous Peripheral Attach System (MAS) a Russian technology that docked the Russian Zarya module to Unity, or Node 1, is a more complex system that also is capable of fuel transfer, enabling refueling of the Russian re-boost engines on ISS. For several years, a Low Impact Docking System (LIDS) has been under development at Johnson Space Center (JSC). This docking technology has a requirement to be androgynous in order to allow the fabrication of a single configuration that can dock with all other LIDS units. It is desired to make electrical and fluid coupling mating an automated process to enable routine docking and undocking operations to support future exploration missions. It is envisioned that modular design and vehicle assembly will require an efficient LIDS for fuel, electrical, crew, and equipment transfer. Marshall Space Flight Center (MSFC) has joined the LIDS development effort and plans to employ fluid transfer concepts and technology from previous development programs, such as the Automated Fluid Interface System (AFIS) and the Ohital Fluid Transfer System (OFTS) that were developed and tested by MSFC. Orbital Expressderived robotic satellite servicing technology is scheduled to fly soon to demonstrate fluid transfer technology developed for the Air Force. This paper will compare known technology against possible fluid transfer requirements for LIDS to develop design strategies for automated fluid transfer.

Miernik, Janie H.↗

Embedded Web Technology: Internet Technology Applied to Real-Time System Control

The NASA Lewis Research Center is developing software tools to bridge the gap between the traditionally non-real-time Internet technology and the real-time, embedded-controls environment for space applications. Internet technology has been expanding at a phenomenal rate. The simple World Wide Web browsers (such as earlier versions of Netscape, Mosaic, and Internet Explorer) that resided on personal computers just a few years ago only enabled users to log into and view a remote computer site. With current browsers, users not only view but also interact with remote sites. In addition, the technology now supports numerous computer platforms (PC's, MAC's, and Unix platforms), thereby providing platform independence.In contrast, the development of software to interact with a microprocessor (embedded controller) that is used to monitor and control a space experiment has generally been a unique development effort. For each experiment, a specific graphical user interface (GUI) has been developed. This procedure works well for a single-user environment. However, the interface for the International Space Station (ISS) Fluids and Combustion Facility will have to enable scientists throughout the world and astronauts onboard the ISS, using different computer platforms, to interact with their experiments in the Fluids and Combustion Facility. Developing a specific GUI for all these users would be cost prohibitive. An innovative solution to this requirement, developed at Lewis, is to use Internet technology, where the general problem of platform independence has already been partially solved, and to leverage this expanding technology as new products are developed. This approach led to the development of the Embedded Web Technology (EWT) program at Lewis, which has the potential to significantly reduce software development costs for both flight and ground software.

Daniele, Carl J.↗

Power Subsystem for Extravehicular Activities for Exploration Missions

The NASA Glenn Research Center has the responsibility to develop the next generation space suit power subsystem to support the Vision for Space Exploration. Various technology challenges exist in achieving extended duration missions as envisioned for future lunar and Mars mission scenarios. This paper presents an overview of ongoing development efforts undertaken at the Glenn Research Center in support of power subsystem development for future extravehicular activity systems.

Manzo, Michelle↗

Development of NASA's Models and Simulations Standard

From the Space Shuttle Columbia Accident Investigation, there were several NASA-wide actions that were initiated. One of these actions was to develop a standard for development, documentation, and operation of Models and Simulations. Over the course of two-and-a-half years, a team of NASA engineers, representing nine of the ten NASA Centers developed a Models and Simulation Standard to address this action. The standard consists of two parts. The first is the traditional requirements section addressing programmatics, development, documentation, verification, validation, and the reporting of results from both the M&S analysis and the examination of compliance with this standard. The second part is a scale for evaluating the credibility of model and simulation results using levels of merit associated with 8 key factors. This paper provides an historical account of the challenges faced by and the processes used in this committee-based development effort. This account provides insights into how other agencies might approach similar developments. Furthermore, we discuss some specific applications of models and simulations used to assess the impact of this standard on future model and simulation activities.

simulation↗

Mitigation Strategies for Space Radiation Health Risks

Astronauts embarking on missions beyond low Earth orbit (LEO) will be exposed to a radiation field that may increase the risks of developing cancer, cardiovascular diseases, central nervous system disorders, and immune decrements. Operational parameters will be the primary determinants of crew radiation exposure. NASA uses integrated design tools and risk models to optimize these parameters to minimize radiation exposure. NASA is also considering medical countermeasures (MCMs) to reduce radiation-associated health risks. MCMs for potential use in space-based applications can be developed from a variety of sources, including: a) population-based chemoprevention trials against targeted diseases b) drug development efforts focused on treating acute effects from accidental radiation exposures c) drug development to mitigate side effects of radiotherapy d) mechanistic studies of distinct damage caused by high charge (Z) and energy (HZE) radiation. Use of agents developed for other applications, or repurposed, is advantageous because long-term safety in humans is already established.

Huff, Janice L.↗

High Temperature Electronics for Venus Surface Applications: A Summary of Recent Technical Advances

This white paper has a technical focus meant to provide background to those unfamiliar with the challenges of high temperature electronics, and an understanding of why new surface mission concepts are now viable for Venus and other applications. It describes that, for the first time, high temperature electronics have been developed to enable a paradigm change in extended duration Venus surface exploration. This white paper concentrates on the advances made in Silicon Carbide (SiC) integrated circuit (IC) electronics that have matured to a state where a simple long-life scientific probe is feasible for Venus surface operations. These electronics have been demonstrated for more than a year at 500˚C, 60 days in high-fidelity simulated Venus surface conditions chamber, and have been integrated and demonstrated with prototype long-lived scientific observation sensor technology. Continued maturation of these needed high temperature electronics and sensors is ongoing in the Long-Lived In-Situ Solar System Explorer (LLISSE) project to provide an operational system including sensor control and operation, signal processing, power management, and communications in the early part of the 2020’s. A key focus of this work includes increasing the complexity and decreasing the power consumption of the ICs which will pave the way to enhanced capabilities, such as long-duration Venus seismic measurements. Other IC development efforts include high temperature memory, terrestrial based characterization of volcanic magma, and development of a simple microprocessor. This electronics has also shown to have exceptionally high radiation tolerance, and thus have relevance for a broad range of solar system exploration. Although presently at the level of complexity of 1970-1980 silicon-based electronics, such electronics can enable breakthroughs in Venus planetary exploration akin to 1970s-launched planetary exploration successes (such as Viking and Voyager).

High temperature Electronics↗

Surveyor spacecraft automatic landing system

The Surveyor Project achieved five successful lunar landings between 1966 and 1968, following an intensive five-year development effort. One of the many significant accomplishments made by Surveyor was the development and validation of the first-ever automated soft-landing system. This paper provides a historical and control aspects of the spacecraft's terminal descent system. Driving requirements and other important design considerations are described, along with the configuration and operational sequence of the actual flight system.

Thurman, Sam W.↗

Flight Software Dictionary Development for the Mars2020 Rover

The Mars2020 project, developed and operated by the Jet Propulsion Laboratory (JPL), successfully landed the Perseverance rover and its flying companion Ingenuity on the surface of Mars on February 18th 2021. Perseverance combines heritage and cutting-edge flight software and hardware to accomplish crucial mission requirements related to Martian surface sampling. The design, development, and operation of NASA’s large strategic science missions require the ability to communicate spacecraft capabilities to hundreds of engineers across multiple disciplines. The interaction between flight and ground software development, Verification and Validation (V&V), Assembly, Test, and Launch Operations (ATLO), and management each demand quick understanding of unique slices of information for each discipline. This information includes the current capabilities of the flight system as well as future capabilities and their status as they are developed and tested. Despite the fundamental and critical nature of this information, the flight software dictionaries used to track it are a stumbling block for many projects. These dictionaries provide the cornerstone for the interpretation of data sent from the spacecraft, allowing for quick comprehension by engineers on the ground. During both spacecraft development and operations, flight software dictionary management includes significant challenges due to the large number of interfacing systems and the subtle yet distinct needs of each.The engineering of flight software dictionaries for Mars2020 had numerous challenges, most-notably: parallel dictionary development to support simultaneous separate flight software build campaigns for each mission phase (cruise and surface), managing requests for operations-enabling information without perturbing the heritage interface with the rover, and the introduction of new tools by the dictionary stakeholders that forced the dictionary team to innovate and redesign the heritage tool chain. These challenges generated guiding principles for the dictionary development effort: emphasize coding best practices and unit testing in the dictionary code development tool chain, use institutionally provided COTS (commercial-off-the-shelf) tools whenever possible, and maintain the heritage flight-ground interface all while advancing operations-enabling information via a loosely coupled interface.Throughout development and operations, the Mars2020 dictionary toolchain included IBM DOORS Next Generation, GitHub, Microsoft Excel, Docker, Jenkins, and a significant custom-built Python codebase. Significant interfaces included JPL’s command and control software, heritage flight software team tools and processes, and the many cloud-based ground tools developed for the mission.This paper will discuss the requirements for the Mars2020 dictionary development, the development team’s response to those requirements, lessons learned throughout the process, steps taken towards automated deliveries and continuous integration of stakeholder inputs, potential toolchain improvements for Mars2020, and key takeaways that could be applied to future missions.

Pyrzak, Guy↗

Dust Mitigation Technology to Enable Survive the Night Capabilities

Introduction: As we return to the Moon, the lunar regolith (i.e. lunar dust) covering the surface will be an obstacle to nominal operations. Accounts from Apollo astronauts and analysis of hardware returned from the surface illustrate just how deleterious the dust can be [1]. During Apollo missions, the lunar dust adhered to hardware mechanically and electrostatically [2]. Surviving the Night: Mitigating the lunar dust will be critical to surviving the night. Going hand-in-hand with other extreme environment considerations, dust mitigation is critical to mission success. Dust Impacts on Other Systems: The lunar dust can have negative implications for power, thermal, mechanisms, and several other systems or sub-systems. For example, Apollo encountered marked degradation of performance in heat rejection systems for the lunar roving vehicle, science packages, and other components because of the lunar dust [1]. For power alone, dust can cause internal clogging for power connectors, heat rejection issues, excessive dust on reflective surfaces, reduced power output for solar arrays, and so on. Dust Mitigation Strategy: In addition to considering technology solutions, it is important for hardware, systems, and or components to have a dust mitigation strategy. At a high level, hardware that will encounter the lunar dust should consider these things when defining a dust mitigation strategy: • Understand Natural Environment • Understand Induced Environment • Understand Tolerance to Dust • Write Dust Requirements • Select Dust Mitigation Solutions • Test Hardware in Dusty Environment More information on each of these can be provided to hardware owners. Dust Mitigation Technology Development: NASA has a series of technologies that may be available for hardware that needs to survive the lunar night. Many of these solutions are leveraging dust mitigation technology development efforts from NASA’s Space Technology Mission Directorate (STMD), as well as efforts from ESDMD programs, industry, and academia. Through a series of STMD programs (both internal to NASA and through partnerships), there are several technologies in development as considerations as dust mitigation solutions for hardware. Within STMD, the Game Changing Development Program (GCD) has funded several internal dust mitigation projects including low to mid TRL development, demonstrations on CLPS landers of high TRL solutions, and creating standards and best practices for dust mitigation. STMD dust mitigation efforts also include a series of partnerships for developing technologies and advancing the state of dust mitigation at NASA. This includes the Lunar Surface Innovation Consortium (LSIC), Small Business Innovation Research, Early Stage Innovations (ESI), Space Technology Research Grants (STRG), Announcement of Collaboration Opportunities (ACOs) and Tipping Points (TPs), and Challenges and Crowdsourcing, among others. There are also a series of dust mitigation solutions that have been widely used terrestrially, or during Apollo. In recent years, several studies have produced more data on the efficacy of these potential solutions in the lunar environment. Dust Mitigation Solutions: Dust mitigation solutions generally fall into four categories: • Dust Tolerant Mechanisms • Passive Dust Mitigation Capabilities • Active Dust Mitigation Capabilities • Dust Measurement Capabilities There are a series of solutions that may prove beneficial for hardware that needs to survive the lunar night, including new technology development as well as proven, terrestrial solutions. This presentation will discuss in more detail what some of these solutions are for payloads going to the surface. References: [1] J. R. Gaier, NASA/TM—2005-213610, The Effects of Lunar Dust on EVA Systems During the Apollo Missions [2] T. J. Stubbs, et al. Impact of Dust on Lunar Exploration, 2005

dust mitigation↗

Survive the Dust: Dust Mitigation Technology to Enable Survive the Night Capabilities

Introduction: As we return to the Moon, the lunar regolith (i.e. lunar dust) covering the surface will be an obstacle to nominal operations. Accounts from Apollo astronauts and analysis of hardware returned from the surface illustrate just how deleterious the dust can be [1]. During Apollo missions, the lunar dust adhered to hardware mechanically and electrostatically [2]. Surviving the Night: Mitigating the lunar dust will be critical to surviving the night. Going hand-in-hand with other extreme environment considerations, dust mitigation is critical to mission success. Dust Impacts on Other Systems: The lunar dust can have negative implications for power, thermal, mechanisms, and several other systems or sub-systems. For example, Apollo encountered marked degradation of performance in heat rejection systems for the lunar roving vehicle, science packages, and other components because of the lunar dust [1]. For power alone, dust can cause internal clogging for power connectors, heat rejection issues, excessive dust on reflective surfaces, reduced power output for solar arrays, and so on. Dust Mitigation Strategy: In addition to considering technology solutions, it is important for hardware, systems, and or components to have a dust mitigation strategy. At a high level, hardware that will encounter the lunar dust should consider these things when defining a dust mitigation strategy: • Understand Natural Environment • Understand Induced Environment • Understand Tolerance to Dust • Write Dust Requirements • Select Dust Mitigation Solutions • Test Hardware in Dusty Environment More information on each of these can be provided to hardware owners. Dust Mitigation Technology Development: NASA has a series of technologies that may be available for hardware that needs to survive the lunar night. Many of these solutions are leveraging dust mitigation technology development efforts from NASA’s Space Technology Mission Directorate (STMD), as well as efforts from ESDMD programs, industry, and academia. Through a series of STMD programs (both internal to NASA and through partnerships), there are several technologies in development as considerations as dust mitigation solutions for hardware. Within STMD, the Game Changing Development Program (GCD) has funded several internal dust mitigation projects including low to mid TRL development, demonstrations on CLPS landers of high TRL solutions, and creating standards and best practices for dust mitigation. STMD dust mitigation efforts also include a series of partnerships for developing technologies and advancing the state of dust mitigation at NASA. This includes the Lunar Surface Innovation Consortium (LSIC), Small Business Innovation Research, Early Stage Innovations (ESI), Space Technology Research Grants (STRG), Announcement of Collaboration Opportunities (ACOs) and Tipping Points (TPs), and Challenges and Crowdsourcing, among others. There are also a series of dust mitigation solutions that have been widely used terrestrially, or during Apollo. In recent years, several studies have produced more data on the efficacy of these potential solutions in the lunar environment. Dust Mitigation Solutions: Dust mitigation solutions generally fall into four categories: • Dust Tolerant Mechanisms • Passive Dust Mitigation Capabilities • Active Dust Mitigation Capabilities • Dust Measurement Capabilities There are a series of solutions that may prove beneficial for hardware that needs to survive the lunar night, including new technology development as well as proven, terrestrial solutions. This presentation will discuss in more detail what some of these solutions are for payloads going to the surface. References: [1] J. R. Gaier, NASA/TM—2005-213610, The Effects of Lunar Dust on EVA Systems During the Apollo Missions [2] T. J. Stubbs, et al. Impact of Dust on Lunar Exploration, 2005

dust mitigation↗

Support for Systematic Code Reviews with the SCRUB Tool

SCRUB is a code review tool that supports both large, team-based software development efforts (e.g., for mission software) as well as individual tasks. The tool was developed at JPL to support a new, streamlined code review process that combines human-generated review reports with program-generated review reports from a customizable range of state-of-the-art source code analyzers. The leading commercial tools include Codesonar, Coverity, and Klocwork, each of which can achieve a reasonably low rate of false-positives in the warnings that they generate. The time required to analyze code with these tools can vary greatly. In each case, however, the tools produce results that would be difficult to realize with human code inspections alone. There is little overlap in the results produced by the different analyzers, and each analyzer used generally increases the effectiveness of the overall effort. The SCRUB tool allows all reports to be accessed through a single, uniform interface (see figure) that facilitates brows ing code and reports. Improvements over existing software include significant simplification, and leveraging of a range of commercial, static source code analyzers in a single, uniform framework. The tool runs as a small stand-alone application, avoiding the security problems related to tools based on Web browsers. A developer or reviewer, for instance, must have already obtained access rights to a code base before that code can be browsed and reviewed with the SCRUB tool. The tool cannot open any files or folders to which the user does not already have access. This means that the tool does not need to enforce or administer any additional security policies. The analysis results presented through the SCRUB tool s user interface are always computed off-line, given that, especially for larger projects, this computation can take longer than appropriate for interactive tool use. The recommended code review process that is supported by the SCRUB tool consists of three phases: Code Review, Developer Response, and Closeout Resolution. In the Code Review phase, all tool-based analysis reports are generated, and specific comments from expert code reviewers are entered into the SCRUB tool. In the second phase, Developer Response, the developer is asked to respond to each comment and tool-report that was produced, either agreeing or disagreeing to provide a fix that addresses the issue that was raised. In the third phase, Closeout Resolution, all disagreements are discussed in a meeting of all parties involved, and a resolution is made for all disagreements. The first two phases generally take one week each, and the third phase is concluded in a single closeout meeting.

Holzmann, Gerald J.↗

Collaborative Research and Development Program on Explosive Detection Technology

In September 2013, at the 6th Permanent Coordinating Group Meeting between the U.S Department of Energy (DOE) and the French Institut de Radioprotection et de Sureté Nucléaire (IRSN), France expressed an interest in bilateral cooperation with the United States because its newly revised regulations that require enhanced explosives detection capabilities at nuclear and radiological facilities. In the ensuing years, PNNL (DOE/NNSA) and IRSN sought to identify an area of collaboration within explosives detection that would leverage the specific technical strengths of each organization. Based upon awareness of each other’s technical acumen gleaned from the scientific literature on explosives detection, it was clear that specific organizations within each nation could provide the needed expertise to enable enhancement of explosives detection through a collaborative development effort. The French lnstitut Saint-Louis was determined to be an optimal partner for IRSN to develop a collaboration with DOE/NNSA using PNNL’s detection team in this effort. Thus, the dialog was started between the technical experts at each organization to define where complementary expertise in explosives detection could be best leveraged. The technical plans and objectives of this project were sound with promising results. In the end, the joint action sheet was not implemented. The challenge with executing the project was in the complexity of getting a signed agreement between DOE, IRSN and ISL. Most of the obstacles surrounded the ability to protect intellectual property and obtain an agreement which included all of the parties. At a high level, this report documents the interactions and attempt to develop a cooperative framework for explosives detection development from FY 2014 through FY 2020.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

Creating Continuous Integration Infrastructure for Software Development on U.S. Department of Energy High-Performance Computing Systems

The Exascale Computing Project (ECP) software deployment effort developed and advanced DevOps capabilities. One goal was to enable robust continuous integration (CI) workflows that span the protected high performance computing (HPC) environments found within many of the Department of Energy’s (DOE) national laboratories. This article highlights several challenges encountered with enabling automation, such as charging models for CI jobs, and meeting individualized security requirements that revolve around strongly associating running code with a human identity. Here, it also describes how the Jacamar CI tool evolved to meet latter requirements and became a key aspect of the solutions currently offered. Derived from this experience, we offer a conceptual framework for understanding current and future CI challenges at DOE facilities and offer suggestions for long-term solutions.

97 MATHEMATICS AND COMPUTING↗

NASA Solar Sail Propulsion Technology Development

NASA's In-Space Propulsion Technology Program has developed the first generation of solar sail propulsion systems sufficient to accomplish inner solar system science and exploration missions. These first generation solar sails, when operational, will range in size from 40 meters to well over 100 meters in diameter and have an areal density of less than 13 grams per square meter. A rigorous, multi-year technology development effort culminated in 2005 with the testing of two different 20-m solar sail systems under thermal vacuum conditions. The first system, developed by ATK Space Systems of Goleta, California, uses rigid booms to deploy and stabilize the sail. In the second approach, L'Garde, Inc. of Tustin, California uses inflatable booms that rigidize in the coldness of space to accomplish sail deployment. This effort provided a number of significant insights into the optimal design and expected performance of solar sails as well as an understanding of the methods and costs of building and using them. In a separate effort, solar sail orbital analysis tools for mission design were developed and tested. Laboratory simulations of the effects of long-term space radiation exposure were also conducted on two candidate solar sail materials. Detailed radiation and charging environments were defined for mission trajectories outside the protection of the earth's magnetosphere, in the solar wind environment. These were used in other analytical tools to prove the adequacy of sail design features for accommodating the harsh space environment. Preceding and in conjunction with these technology efforts, NASA sponsored several mission application studies for solar sails. Potential missions include those that would be flown in the near term to study the sun and be used in space weather prediction to one that would use an evolved sail capability to support humanity's first mission into nearby interstellar space. This paper will describe the status of solar sail propulsion within NASA, nearterm solar sail mission applications, and near-term plans for further development.

Johnson, Les↗