Results for “space programs” — Page 2

DOE OSTI2024

Assessing thermal comfort and participation in residential demand flexibility programs

Residential space-conditioning-based demand flexibility (DF) has become an increasingly sought-after method for demand-side load management to enhance grid reliability and facilitate integration of renewable energy generation. However, predicting the effectiveness and flexibility of residential DF resources is challenging due to the variability in household energy use behaviors. Current estimates show that only 50 % of projected savings from DF resources are actualized due to regulatory, technological, and social barriers. From a household perspective, concerns over thermal comfort during space conditioning-based DF events significantly impact participation decisions. Currently, there is a very limited understanding of how thermal comfort during space-conditioning-based DF events in real-world settings impacts household energy use behaviors and, consequently, the success of DF programs in achieving targeted savings. This paper proposes a method to comprehensively assess the thermal comfort implications of DF strategies and presents results of their impacts on DF event participation decisions and demand savings. Here, the proposed method was applied to a heat pump DF field study in Cordova, Alaska. The study’s key findings are: 1) DF event setpoint offsets that maintain indoor operative temperatures between 18 to 22 °C (65 to 71°F) may be preferred in Cordova, Alaska; 2) Household-level thermal comfort is more sensitive to the duration of the DF event than to the degree of temperature offset from baseline conditions; 3) The delayed impact of changes in indoor operative temperature in response to setpoint offsets, both during and after a DF event, influences occupants’ thermal comfort perceptions and willingness to persistently participate in events. The findings from application of the proposed method can help inform future larger-scale occupant-centric DF programs as it can capture information not readily available through utility and device-level energy use data. Thus, it can supplement these sources and help program administrators develop occupant-centric DF strategies, enabling more accurate predictions of participation rates and savings estimates for space-conditioning-based DF programs.

Demand side management↗

DOE OSTI2022

Gems of the Galaxy Zoos—A Wide-ranging Hubble Space Telescope Gap-filler Program*

We describe the Gems of the Galaxy Zoos (Zoo Gems) project, a gap-filler project using short windows in the Hubble Space Telescope's schedule. As with previous snapshot programs, targets are taken from a pool based on position; we combine objects selected by volunteers in both the Galaxy Zoo and Radio Galaxy Zoo citizen-science projects. Zoo Gems uses exposures with the Advanced Camera for Surveys to address a broad range of topics in galaxy morphology, interstellar-medium content, host galaxies of active galactic nuclei, and galaxy evolution. Science cases include studying galaxy interactions, backlit dust in galaxies, post-starburst systems, rings and peculiar spiral patterns, outliers from the usual color–morphology relation, Green Pea compact starburst systems, double radio sources with spiral host galaxies, and extended emission-line regions around active galactic nuclei. For many of these science categories, final selection of targets from a larger list used public input via a voting process. Highlights to date include the prevalence of tightly wound spiral structure in blue, apparently early-type galaxies, a nearly complete Einstein ring from a group lens, redder components at lower surface brightness surrounding compact Green Pea starbursts, and high-probability examples of spiral galaxies hosting large double radio sources.

79 ASTRONOMY AND ASTROPHYSICS↗

DOE OSTI2020

UPC++ v1.0 Programmer’s Guide, Revision 2020.10.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 constituent process 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 processes. 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 OSTI2020

UPC++ v1.0 Programmer’s Guide, Revision 2020.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 constituent process 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 processes. 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 OSTI2023

UPC++ v1.0 Programmer’s Guide (Rev. 2023.9.0)

UPC++ is a C++ library that supports Partitioned Global Address Space (PGAS) programming. It is designed for writing efficient, scalable parallel programs on distributed-memory parallel computers. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). The UPC++ control model is single program, multiple-data (SPMD), with each separate constituent process having access to local memory as it would in C++. The PGAS memory model additionally provides one-sided RMA communication to a global address space, which is allocated in shared segments that are distributed over the processes. UPC++ also features Remote Procedure Call (RPC) communication, making it easy to move computation to operate on data that resides on remote processes. UPC++ was designed to support exascale high-performance computing, and the library interfaces and implementation are focused on maximizing scalability. In UPC++, all communication operations are syntactically explicit, which encourages programmers to consider the costs associated with communication and data movement. Moreover, all communication operations are asynchronous by default, encouraging programmers to seek opportunities for overlapping communication latencies with other useful work. UPC++ provides expressive and composable abstractions designed for efficiently managing aggressive use of asynchrony in programs. Together, these design principles are intended to enable programmers to write applications using UPC++ that perform well even on hundreds of thousands of cores.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2022

UPC++ v1.0 Programmer’s Guide (Revision 2022.3.0)

UPC++ is a C++ library that supports Partitioned Global Address Space (PGAS) programming. It is designed for writing efficient, scalable parallel programs on distributed-memory parallel computers. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). The UPC++ control model is single program, multiple-data (SPMD), with each separate constituent process having access to local memory as it would in C++. The PGAS memory model additionally provides one-sided RMA communication to a global address space, which is allocated in shared segments that are distributed over the processes. UPC++ also features Remote Procedure Call (RPC) communication, making it easy to move computation to operate on data that resides on remote processes. UPC++ was designed to support exascale high-performance computing, and the library interfaces and implementation are focused on maximizing scalability. In UPC++, all communication operations are syntactically explicit, which encourages programmers to consider the costs associated with communication and data movement. Moreover, all communication operations are asynchronous by default, encouraging programmers to seek opportunities for overlapping communication latencies with other useful work. UPC++ provides expressive and composable abstractions designed for efficiently managing aggressive use of asynchrony in programs. Together, these design principles are intended to enable programmers to write applications using UPC++ that perform well even on hundreds of thousands of cores.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2023

UPC++ v1.0 Programmer’s Guide, Revision 2023.3.0

UPC++ is a C++ library that supports Partitioned Global Address Space (PGAS) programming. It is designed for writing efficient, scalable parallel programs on distributed-memory parallel computers. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). The UPC++ control model is single program, multiple-data (SPMD), with each separate constituent process having access to local memory as it would in C++. The PGAS memory model additionally provides one-sided RMA communication to a global address space, which is allocated in shared segments that are distributed over the processes. UPC++ also features Remote Procedure Call (RPC) communication, making it easy to move computation to operate on data that resides on remote processes. UPC++ was designed to support exascale high-performance computing, and the library interfaces and implementation are focused on maximizing scalability. In UPC++, all communication operations are syntactically explicit, which encourages programmers to consider the costs associated with communication and data movement. Moreover, all communication operations are asynchronous by default, encouraging programmers to seek opportunities for overlapping communication latencies with other useful work. UPC++ provides expressive and composable abstractions designed for efficiently managing aggressive use of asynchrony in programs. Together, these design principles are intended to enable programmers to write applications using UPC++ that perform well even on hundreds of thousands of cores.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2022

UPC++ v1.0 Programmer’s Guide, Revision 2022.9.0

UPC++ is a C++ library that supports Partitioned Global Address Space (PGAS) programming. It is designed for writing efficient, scalable parallel programs on distributed-memory parallel computers. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). The UPC++ control model is single program, multiple-data (SPMD), with each separate constituent process having access to local memory as it would in C++. The PGAS memory model additionally provides one-sided RMA communication to a global address space, which is allocated in shared segments that are distributed over the processes. UPC++ also features Remote Procedure Call (RPC) communication, making it easy to move computation to operate on data that resides on remote processes. UPC++ was designed to support exascale high-performance computing, and the library interfaces and implementation are focused on maximizing scalability. In UPC++, all communication operations are syntactically explicit, which encourages programmers to consider the costs associated with communication and data movement. Moreover, all communication operations are asynchronous by default, encouraging programmers to seek opportunities for overlapping communication latencies with other useful work. UPC++ provides expressive and composable abstractions designed for efficiently managing aggressive use of asynchrony in programs. Together, these design principles are intended to enable programmers to write applications using UPC++ that perform well even on hundreds of thousands of cores.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2021

UPC++ v1.0 Programmer’s Guide, Revision 2021.9.0

UPC++ is a C++ 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 constituent process having access to local memory as it would in C++. PGAS additionally provides one-sided Remote Memory Access (RMA) to a global address space, which is allocated in shared segments that are distributed over the processes. UPC++ also features Remote Procedure Call (RPC) communication, making it easy to move computation to operate on data that resides on remote processes. In UPC++, all communication operations are explicit, which encourages programmers to be aware of the cost of communication and data movement. Moreover, all communication operations are asynchronous by default, to enable programmers to write code that scales well even on hundreds of thousands of cores.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

DOE OSTI2025

Speeding-up fuzzing through directional seeds

Abstract Fuzzing is an automated process for discovering inputs in a program that may trigger unexpected behavior. Today, fuzzing has become a standard practice for the discovery of bugs and security vulnerabilities. However, the main issue with such practices is that the exploration of the input space of programs can often be prohibitively expensive. Therefore, several alternative fuzzing strategies have been introduced during the last few years. Some fuzzing techniques rely on human expertise to provide a plausible set of initial input examples, namely, seeds. However, the process of handcrafting seeds for fuzzing purposes often becomes strenuous for humans as it requires a deeper understanding of the Program-Under-Test (PUT). Also, the use of known inputs to programs often does not trigger vulnerable program behavior or may not reach potentially vulnerable code locations. To address those issues, we propose a seed generation framework that enables Human-In-The-Loop (HITL) directed fuzzing where the human assumes a more active role in the creation of seeds that can penetrate and assess desired locations of the PUT. Our proposed framework uses Symbolic Execution (SE) to generate seeds that exercise paths to target program locations. Moreover, our framework enables the visualization of the explored execution paths in the binary of the PUT for the generated seeds. We evaluated our approach on a set of 12 carefully designed C programs with diverse characteristics that mimic real-world programs. The experimental results show the effectiveness of the proposed approach in improving the performance of standard fuzzing tools such as the American Fuzzy Lop ("Image missing" <#comment/> ). Specifically, our solution can generate seeds that substantially enhance the performance of the fuzzer, achieving speedups ranging from $$1.46\times $$ 1.46 × to $$68.53\times $$ 68.53 × for branch conditions, $$1.39\times $$ 1.39 × to $$254.62\times $$ 254.62 × for branch depths, $$14,879.59\times $$ 14 , 879.59 × to $$30,295.88\times $$ 30 , 295.88 × for branch widths over traditional seeds. Additionally, the speedup increases with the number of target function ranging from $$12,260\times $$ 12 , 260 × to $$22,856.07\times $$ 22 , 856.07 × over traditional seeds while only requiring less than 15 seconds on average for the seed generation step.

97 MATHEMATICS AND COMPUTING↗

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 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 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 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↗

DOE OSTI2021

Radiation Hardening – Test Capabilities (LANSCE) [Slides]

The Los Alamos Neutron Science Center (LANSCE) has exceptional facilities for research and testing of radiation effects in electronics. We have the best terrestrial neutron source for sea-level and airplane-altitude environments. We have a thermal neutron test capability at the Lujan Center and a proton beam test capability at the “Blue Room”. LANL has the programmatic mission to develop this radiation-effects program, namely space and satellite environments, high-performance computing (silent data corruption), and weapons delivery systems. We have a strong connection to industry which continues to grow.

42 ENGINEERING↗

DOE OSTI2021

UPC++ v1.0 Specification, Revision 2021.9.0

UPC++ is a C++ 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.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗