Search NASA⌕ Search

SEARCH · Search NASA

Results for “Space Program”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
DOE OSTI2024

Implementing an Objectives-Driven, Risk-Informed, and Case-Assured Approach to Safety and Mission Success at NASA

NASA is developing a “Standard for Assurance of Space Flight Safety and Mission Success” that implements an objectives-driven, risk-informed, and case-assured approach to safety and mission success (S&MS) for NASA space flight programs and projects. The standard aligns with the philosophy of risk leadership that has recently been established in NASA policy to assure acceptable levels of flight crew safety and mission success risk. It is consistent with existing NASA risk management requirements and is compatible with NASA program management and systems engineering requirements. The methodology described in the standard is presented in terms of an S&MS assurance framework that is designed to allow substantial flexibility in the specific means by which programs and projects achieve acceptable mission S&MS risk. Such flexibility is necessary to accommodate the increasingly broad range of acquisition strategies employed by NASA, including commercial transportation services, as well as to accommodate the increasingly rapid evolution of space flight-related technologies and practices. A key feature of the S&MS assurance framework is the specification of S&MS success criteria for each life-cycle review (LCR). The S&MS assurance case is structured around these criteria, the satisfaction of which indicates that the program/project is adhering to the S&MS risk posture. This enables the evolving S&MS assurance case to be used as a fundamental program/project submittal at each LCR, where its inherent structure of argument, supported by evidence, directly supports the evaluation of the program/project with respect to the S&MS success criteria, and by extension, the S&MS risk posture. As such, the S&MS assurance case is integral to program/project systems engineering, risk management, and S&MS oversight activities, and provides the principal basis for S&MS risk acceptance by the Decision Authority throughout the program/project life cycle.

42 ENGINEERING↗
DOE OSTI2017

UPC++ Programmer’s Guide (v1.0 2017.9)

UPC++ is a C++11 library that provides Asynchronous Partitioned Global Address Space (APGAS) programming. It is designed for writing parallel programs that run efficiently and scale well on distributed-memory parallel computers. The APGAS model is single program, multiple-data (SPMD), with each separate thread of execution (referred to as a rank, a term borrowed from MPI) having access to local memory as it would in C++. However, APGAS also provides access to a global address space, which is allocated in shared segments that are distributed over the ranks. UPC++ provides numerous methods for accessing and using global memory. In UPC++, all operations that access remote memory are explicit, which encourages programmers to be aware of the cost of communication and data movement. Moreover, all remote-memory access operations are by default asynchronous, to enable programmers to write code that scales well even on hundreds of thousands of cores.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2018

UPC++ Programmer’s Guide, v1.0-2018.3.0

UPC++ is a C++11 library that provides Partitioned Global Address Space (PGAS) programming. It is designed for writing parallel programs that run efficiently and scale well on distributed-memory parallel computers. The PGAS model is single program, multiple-data (SPMD), with each separate thread of execution (referred to as a rank, a term borrowed from MPI) having access to local memory as it would in C++. However, PGAS also provides access to a global address space, which is allocated in shared segments that are distributed over the ranks. UPC++ provides numerous methods for accessing and using global memory. In UPC++, all operations that access remote memory are explicit, which encourages programmers to be aware of the cost of communication and data movement. Moreover, all remote-memory access operations are by default asynchronous, to enable programmers to write code that scales well even on hundreds of thousands of cores.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2019

Preserving the Mound Laboratory Legacy-The Mound Cold War Discovery Center - 19550

The Mound Cold War Discovery Center (MCWDC) opened at the former DOE Mound Laboratory in Miamisburg, Ohio, on April 23, 2018, approximately three years after the US Department of Energy (DOE) Office of Legacy Management, Dayton History, the Mound Science and EnergyMuseum Association (MSEMA), and the Mound Development Corporation signed the Mound Educational Center Memorandum of Agreement (MOA). This MOA designated each party's responsibilities for the facility and laid the groundwork for DOE to enter into a Cooperative Agreement with Dayton History to design, build, and perform initial operations of the educational center. Dayton History is a nonprofit organization that operates several historical facilities in Montgomery County, Ohio. The Mound Development Corporation is the nonprofit organization that operates the Mound Business Park, privately owned property previously associated with the former DOE Mound Laboratory. The US Atomic Energy Commission began operations at the Mound Laboratory in 1948 as an integrated research, development, and production facility that supported the nation's weapons and energy programs. In October 2015, DOE entered into a five-year Cooperative Agreement with Dayton History to preserve, protect, and make accessible legacy records and information about the history of the Mound site through the development of an educational center. Years One and Two were for design and construction, respectively. Years Three through Five were for operation of the new center. The new center, located in a building owned by the Mound Development Corporation, would carry on the mission started by the MSEMA, a nonprofit organization started by former Mound site employees more than 15 years ago after DOE mission work ended at the site. As part of the cooperative agreement, Dayton History is responsible for creating interactive displays and exhibits to draw, entertain, and educate the public on the Mound site's significant contributions to the protection of the nation; developing educational programs; and initiating marketing strategies for the long-term sustainability of the educational center. In 2016, parties to the MOA officially named the facility the Mound Cold War Discovery Center. The MCWDC was designed to preserve the history of the Mound site through effective, entertaining, and efficient communication of the history of the Mound Laboratory; the site's legacy to the US weapons production complex and space exploration program; and promote understanding of what has happened at the site since DOE mission work ended, including environmental cleanup under the Comprehensive Environmental Response, Compensation, and Liability Act and the regulator-approved end state of industrial/commercial land use with associated institutional controls. The cooperative agreement requires Dayton History to develop and implement marketing strategies to support the long-term sustainability of the MCWDC at the Mound site. Dayton History will submit a report after the first year of operation and every year thereafter during the period of the cooperative agreement. These reports will describe and status efforts to obtain sustainability and offer for consideration any operational changes, corrections, or suggestions that may improve the potential for sustainability. Prior to the end of the cooperative agreement, a sustainability assessment decision will be made by DOE to determine whether the MCWDC has enough community interest to financially sustain itself at the Mound site. The status of the MCWDC Legacy Fund established by Dayton History will be considered in DoE's assessment determination. If DOE determines that the MCWDC is not sustainable at the Mound site, the exhibits will be relocated to Carillon Historical Park in Dayton, with the five key exhibits that were predetermined in the MOA to be placed on permanent display, thereby maintaining the legacy of the Mound site. Dayton History is required to submit a final closeout report at the end of Year Five of the cooperative agreement. The report will describe all activities completed under the agreement, provide an assessment of how project goals were achieved or not achieved, and describe how the legacy of the site will be preserved. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
DOE OSTI2018

Real-space refinement in PHENIX for cryo-EM and crystallography

This article describes the implementation of real-space refinement in the phenix.real_space_refine program from the PHENIX suite. The use of a simplified refinement target function enables very fast calculation, which in turn makes it possible to identify optimal data-restraint weights as part of routine refinements with little runtime cost. Refinement of atomic models against low-resolution data benefits from the inclusion of as much additional information as is available. In addition to standard restraints on covalent geometry, phenix.real_space_refine makes use of extra information such as secondary-structure and rotamer-specific restraints, as well as restraints or constraints on internal molecular symmetry. The re-refinement of 385 cryo-EM-derived models available in the Protein Data Bank at resolutions of 6 Å or better shows significant improvement of the models and of the fit of these models to the target maps.

59 BASIC BIOLOGICAL SCIENCES↗
DOE OSTI2020

Calibration and Initial Results of Space Radiation Dosimetry Using the iMESA-R

The integrated Miniaturized Electrostatic Analyzer-Reflight (iMESA-R) is a space weather instrument designed to measure plasma density, temperature, and spacecraft charging, along with total ionizing dose and dose rate. A constellation consisting of five nearly identical instruments has been designed and developed to act as science payloads hosted on-board Department of Defense satellites operating in low-Earth orbit. To validate the dosimetry component of the iMESA-R, a radiation test study was performed to calibrate the dosimeter and ascertain the attenuation due to the instrument aluminum housing. An 80 curie Cobalt-60 radioisotope source emitting beta, X-ray, and gamma ray radiation decay products was used to calibrate the dosimeter response as a function of distance and instrument shielding. We present results of the calibration study along with initial on-orbit data presented from the first operational iMESA-R hosted on-board Space Test Program Satellite 5 in a polar Earth orbit. The initial on-orbit data demonstrate the ability to map the radiation environment, particularly the South Atlantic Anomaly and the auroral regions using total ionizing dose rate due to electrons of E > 1.5 MeV and protons of E > 25 MeV.

79 ASTRONOMY AND ASTROPHYSICS↗
DOE OSTI2020

The integrated miniaturized electrostatic analyzer: A space plasma environment sensor

The integrated Miniaturized Electrostatic Analyzer (iMESA) was a satellite-based ionospheric sensor that operated on NASA’s Space Test Program Satellite (STPSat-3) from December 2013 to July 2019. The instrument’s scientific objective was to (1) measure the plasma density in low Earth orbit, (2) measure the plasma temperature in low Earth orbit, and (3) quantify the spacecraft potential with respect to the ambient plasma potential in the ionosphere. iMESA sampled the ionosphere every 10 s by measuring the ion current density through the ESA as a result of the motion of the spacecraft through the plasma. Current density spectra were transmitted to the ground where they were post-processed into ion density spectra and then analyzed numerically to determine the ion density, ion temperature, and spacecraft potential. This article discusses the instrument design and simulation, the determination of a geometric factor, and data processing procedures and evaluates the final data product with regard to the mission success criteria. Here, the ion density and ion temperature captured by the iMESA instrument are on the same order and range as the values predicted in the literature. The spacecraft potential was also quantified. The conclusion after the evaluation of the instrument’s data product is that the scientific mission is successful on all three points.

47 OTHER INSTRUMENTATION↗
DOE OSTI2025

Radio Frequency Transients Correlated with Electron Flux Measured On-Board the STP-Sat6

We analyzed transient electromagnetic signatures, referred to as spacecraft environment discharges (SEDs) or on-board discharges (OBDs), and the in-situ particle environment simultaneously measured by the Radio Frequency Sensor (RFS) and the Space and Atmospheric Burst Reporting System Z-plasma spectrometer (SABRS-ZPS), respectively. These sensors are on-board the U.S. Department of Defense Space Test Program Satellite 6 (STP-Sat6) in geostationary orbit. Radio frequency signatures of SEDs on STP-Sat6 have relatively high peak amplitudes; they often caused amplitude-saturation in the so-called high band (120–140 MHz frequency range) of the RFS likely due to the proximity of their source to the RFS’s dipole antennas. We examined the occurrence rate of SEDs reported by the RFS and its temporal relationship to electron flux in the 7.9–12.2 keV range. Peaks in SED count rates were time-correlated with peaks in electron flux. The electron-flux peaks appeared to lead the SED count rate peaks by 24–45 min for the 7.9–12.2 keV energies. This indicates that incidence of electrons at this relatively low-energy range likely resulted in ramping up of the charging of the spacecraft leading to periods of high occurrence rates of discharges in and around the spacecraft.

54 ENVIRONMENTAL SCIENCES↗
DOE OSTI2017

Project AMIGA: A Minimal Covering Factor for Optically Thick Circumgalactic Gas around the Andromeda Galaxy

We present a deep search for H I 21 cm emission from the gaseous halo of Messier 31 as part of Project AMIGA, a large Hubble Space Telescope program to study the circumgalactic medium of the Andromeda galaxy. Our observations with the Robert C. Byrd Green Bank Telescope target sight lines to 48 background AGNs, more than half of which have been observed in the ultraviolet with the Cosmic Origins Spectrograph, with impact parameters 25≲ρ≲340 kpc (0.1≲ρ/R{sub vir}≲1.1). We do not detect any 21 cm emission toward these AGNs to limits of N(H I)≈4×10{sup 17} cm{sup −2} (5σ; per 2 kpc-diameter beam). This column density corresponds to an optical depth of ∼2.5 at the Lyman limit; thus, our observations overlap with absorption line studies of Lyman limit systems at higher redshift. Our non-detections place a limit on the covering factor of such optically thick gas around M31 to f{sub c}<0.051 (at 90% confidence) for ρ⩽R{sub vir}. Although individual clouds have previously been found in the region between M31 and M33, the covering factor of strongly optically thick gas is quite small. Our upper limits on the covering factor are consistent with expectations from recent cosmological “zoom” simulations. Recent COS-Halos ultraviolet measurements of H I absorption about an ensemble of galaxies at z≈0.2 show significantly higher covering factors within ρ≲0.5R{sub vir} at the same N(H I), although the metal ion-to-H I ratios appear to be consistent with those seen in M31.

79 ASTRONOMY AND ASTROPHYSICS↗
DOE OSTI2017

Parallelizing Single Source Shortest Path with OpenSHMEM

Single Source Shortest Path (SSSP) is one of the widely occurring graph problems where the paths are discovered from an origin vertex to all other vertices in the graph. In this paper, we discuss our experience parallelizing SSSP using OpenSHMEM. We start with the serial Dijkstra and Bellman-Ford algorithms, parallelize these algorithms, and adapt them to the Partitioned Global Address Space (PGAS) programming model. We implement the parallel algorithms using OpenSHMEM and introduce a series of optimizations to achieve higher scaling and performance characteristics. The implementation is evaluated on Titan with various graphs including synthetic Recursive Matrix (R-MAT) and small-world network graphs as well as real-world graphs from Facebook, Twitter, LiveJournal, and the road maps of California and Texas.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2020

Calibration of the Falcon Solid-state Energetic Electron Detector (SEED)

The Falcon Solid-state Energetic Electron Detector (FalconSEED) is an energetic charged particle sensor that has been developed and tested at the United States Air Force Academy in an effort to monitor electron flux across the energy range of 14 to 145 keV in geosynchronous orbit. This sensor has been developed to complement ongoing efforts by the Air Force Research Laboratory to advance a comprehensive space environment sensor suite, Compact Environmental Anomaly Sensor (CEASE3), for anomaly resolution. In addition, FalconSEED is intended to demonstrate the ability to operate a radiation sensor based on predominantly commercial off the shelf components in the geosynchronous environment. This paper describes the design, development, and calibration of FalconSEED. The electron energy spectrum of interest for the FalconSEED sensor is 14 to 145 keV, and is intended to supplement data acquired from the CEASE3 instrument for anomaly resolution. The calibrations at the Space Atmospheric Research Center at the United States Air Force Academy and Kirtland Air Force Base were used to first establish the conversion between histogram bin number and deposited energy in the sensor, and second have been used to determine the geometric factor as a function of energy. The FalconSEED will be integrated as a science payload on the Space Test Program Satellite-6 which also includes the first flight of the CEASE3 instrument and is scheduled to launch in 2021.

47 OTHER INSTRUMENTATION↗
DOE OSTI2019

Graph Algorithms in PGAS: Chapel and UPC++

The Partitioned Global Address Space (PGAS) programming model can be implemented «««< HEAD either with programming language features or with runtime library APIs, each implementation favoring different aspects (e.g., productivity, abstraction, flexibility, or performance). Certain language and runtime features, such as collectives, explicit and asynchronous communication primitives, and constructs facilitating overlap of communication and computation (such as futures and conjoined futures) can enable better performance and scaling for irregular applications, in particular for distributed graph analytics. We compare graph algorithms in one of each of these environments: the Chapel PGAS programming language and the UPC++ PGAS runtime library. We implement algorithms for breadth-first search and triangle counting graph kernels in both environments. We discuss the code in each of the environments, and compile performance data on a Cray Aries and an Infiniband platform. Our results show that the library-based approach of UPC++ currently provides strong performance while Chapel provides a high-level abstraction that, harder to optimize, still provides comparable performance. We argue that various language primitives and runtime library features should be considered in conjunction with each other to design future graph analytics libraries so as to incorporate the best of both worlds.

Distributed Algorithms, Graph algorithms, HPC↗
DOE OSTI2018

UPC++ V1.0

UPC++ is a C++11 library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. We are revising the library under the auspices of the DOE's Exascale Computing Project, to meet the needs of applications requiring PGAS support. UPC++ is intended for implementing elaborate distributed data structures where communication is irregular or fine-grained. The UPC++ interfaces for moving non-contiguous data and handling memories with different optimal access methods are composable and similar to those used in conventional C++. The UPC++ programmer can expect communication to run at close to hardware speeds. The key facilities in UPC++ are global pointers, that enable the programmer to express ownership information for improving locality, one-sided communication, both put/get and RPC, futures and continuations. Futures capture data readiness state, which is useful in making scheduling decisions, and continuations provide for completion handling via callbacks. Together, these enable the programmer to chain together a DAG of operations to execute asynchronously as high-latency dependencies become satisfied.

ECP↗
DOE OSTI2017

UPC++ Specification v1.0, Draft 4

UPC++ is a C++11 library providing classes and functions that support Asynchronous Partitioned Global Address Space (APGAS) programming. We are revising the library under the auspices of the DOE’s Exascale Computing Project, to meet the needs of applications requiring PGAS support. UPC++ is intended for implementing elaborate distributed data structures where communication is irregular or fine-grained. The UPC++ interfaces for moving non-contiguous data and handling memories with different optimal access methods are composable and similar to those used in conventional C++. The UPC++ programmer can expect communication to run at close to hardware speeds. The key facilities in UPC++ are global pointers, that enable the programmer to express ownership information for improving locality, one-sided communication, both put/get and RPC, futures and continuations. Futures capture data readiness state, which is useful in making scheduling decisions, and continuations provide for completion handling via callbacks. Together, these enable the programmer to chain together a DAG of operations to execute asynchronously as high-latency dependencies become satisfied.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2018

UPC++ Specification v1.0, Draft 6

UPC++ is a C++11 library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. We are revising the library under the auspices of the DOE’s Exascale Computing Project, to meet the needs of applications requiring PGAS support. UPC++ is intended for implementing elaborate distributed data structures where communication is irregular or fine-grained. The UPC++ interfaces for moving non-contiguous data and handling memories with different optimal access methods are composable and similar to those used in conventional C++. The UPC++ programmer can expect communication to run at close to hardware speeds. The key facilities in UPC++ are global pointers, that enable the programmer to express ownership information for improving locality, one-sided communication, both put/get and RPC, futures and continuations. Futures capture data readiness state, which is useful in making scheduling decisions, and continuations provide for completion handling via callbacks. Together, these enable the programmer to chain together a DAG of operations to execute asynchronously as high-latency dependencies become satisfied.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2019

UPC++ Specification v1.0, Draft 10

UPC++ is a C++11 library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. We are revising the library under the auspices of the DOE’s Exascale Computing Project, to meet the needs of applications requiring PGAS support. UPC++ is intended for implementing elaborate distributed data structures where communication is irregular or fine-grained. The UPC++ interfaces for moving non-contiguous data and handling memories with different optimal access methods are composable and similar to those used in conventional C++. The UPC++ programmer can expect communication to run at close to hardware speeds. The key facilities in UPC++ are global pointers, that enable the programmer to express ownership information for improving locality, one-sided communication, both put/get and RPC, futures and continuations. Futures capture data readiness state, which is useful in making scheduling decisions, and continuations provide for completion handling via callbacks. Together, these enable the programmer to chain together a DAG of operations to execute asynchronously as high-latency dependencies become satisfied.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2019

UPC++ v1.0 Specification (Revision 2019.9.0)

UPC++ is a C++11 library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. We are revising the library under the auspices of the DOE’s Exascale Computing Project, to meet the needs of applications requiring PGAS support. UPC++ is intended for implementing elaborate distributed data structures where communication is irregular or fine-grained. The UPC++ interfaces for moving non-contiguous data and handling memories with different optimal access methods are composable and similar to those used in conventional C++. The UPC++ programmer can expect communication to run at close to hardware speeds. The key facilities in UPC++ are global pointers, that enable the programmer to express ownership information for improving locality, one-sided communication, both put/get and RPC, futures and continuations. Futures capture data readiness state, which is useful in making scheduling decisions, and continuations provide for completion handling via callbacks. Together, these enable the programmer to chain together a DAG of operations to execute asynchronously as high-latency dependencies become satisfied.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2020

UPC++ v1.0 Specification, Revision 2020.10.0

UPC++ is a C++11 library providing classes and functions that support Partitioned Global Address Space (PGAS) programming. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). All communication operations are syntactically explicit and default to non-blocking; asynchrony is managed through the use of futures, promises and continuation callbacks, enabling the programmer to construct a graph of operations to execute asynchronously as high-latency dependencies are satisfied. A global pointer abstraction provides system-wide addressability of shared memory, including host and accelerator memories. The parallelism model is primarily process-based, but the interface is thread-safe and designed to allow efficient and expressive use in multi-threaded applications. The interface is designed for extreme scalability throughout, and deliberately avoids design features that could inhibit scalability.

97 MATHEMATICS AND COMPUTING↗