Search NASA⌕ Search

SEARCH · Search NASA

Results for “Program processors”

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.

1,510 records · Page 84

A PENELOPE-based system for the automated Monte Carlo simulation of clinacs and voxelized geometries - application to far-from-axis fields

Purpose: Two new codes, PENEASY and PENEASYLINAC, which automate the Monte Carlo simulation of Varian Clinacs of the 600, 1800, 2100, and 2300 series, together with their electron applicators and multileaf collimators, are introduced. The challenging case of a relatively small and far-from-axis field has been studied with these tools. Methods: PENEASY is a modular, general-purpose main program for the PENELOPE Monte Carlo system that includes various source models, tallies and variance-reduction techniques (VRT). The code includes a new geometry model that allows the superposition of voxels and objects limited by quadric surfaces. A variant of the VRT known as particle splitting, called fan splitting, is also introduced. PENEASYLINAC, in turn, automatically generates detailed geometry and configuration files to simulate linacs with PENEASY. These tools are applied to the generation of phase-space files, and of the corresponding absorbed dose distributions in water, for two 6 MV photon beams from a Varian Clinac 2100 C/D: a 40 x 40 cm{sup 2} centered field; and a 3 x 5 cm{sup 2} field centered at (4.5, -11.5) cm from the beam central axis. This latter configuration implies the largest possible over-traveling values of two of the jaws. Simulation results for the depth dose and lateral profiles at various depths are compared, by using the gamma index, with experimental values obtained with a PTW 31002 ionization chamber. The contribution of several VRTs to the computing speed of the more demanding off-axis case is analyzed. Results: For the 40 x 40 cm{sup 2} field, the percentages {gamma}{sub 1} and {gamma}{sub 1.2} of voxels with gamma indices (using 0.2 cm and 2% criteria) larger than unity and larger than 1.2 are 0.2% and 0%, respectively. For the 3 x 5 cm{sup 2} field, {gamma}{sub 1} = 0%. These figures indicate an excellent agreement between simulation and experiment. The dose distribution for the off-axis case with voxels of 2.5 x 2.5 x 2.5 mm{sup 3} and an average standard statistical uncertainty of 2% (1{sigma}) is computed in 3.1 h on a single core of a 2.8 GHz Intel Core 2 Duo processor. This result is obtained with the optimal combination of the tested VRTs. In particular, fan splitting for the off-axis case accelerates execution by a factor of 240 with respect to standard particle splitting. Conclusions: PENEASY and PENEASYLINAC can simulate the considered Varian Clinacs both in an accurate and efficient manner. Fan splitting is crucial to achieve simulation results for the off-axis field in an affordable amount of CPU time. Work to include Elekta linacs and to develop a graphical interface that will facilitate user input is underway.

62 RADIOLOGY AND NUCLEAR MEDICINE↗

The NASA-JPL advanced propulsion program

The NASA Advanced Propulsion Concepts (APC) program at the Jet Propulsion Laboratory (JPL) consists of two main areas: The first involves cooperative modeling and research activities between JPL and various universities and industry; the second involves research at universities and industry that is directly supported by JPL. The cooperative research program consists of mission studies, research and development of ion engine technology using C-60 (Buckminsterfullerene) propellant, and research and development of lithium-propellant Lorentz-force accelerator (LFA) engine technology. The university/industry- supported research includes research (modeling and proof-of-concept experiments) in advanced, long-life electric propulsion, and in fusion propulsion. These propulsion concepts were selected primarily to cover a range of applications from near-term to far-term missions. For example, the long-lived pulsed-xenon thruster research that JPL is supporting at Princeton University addresses the near-term need for efficient, long-life attitude control and station-keeping propulsion for Earth-orbiting spacecraft. The C-60-propellant ion engine has the potential for good efficiency in a relatively low specific impulse (Isp) range (10,000 - 30,000 m/s) that is optimum for relatively fast (less than 100 day) cis-lunar (LEO/GEO/Lunar) missions employing near-term, high-specific mass electric propulsion vehicles. Research and modeling on the C-60-ion engine are currently being performed by JPL (engine demonstration), Caltech (C-60 properties), MIT (plume modeling), and USC (diagnostics). The Li-propellant LFA engine also has good efficiency in the modest Isp range (40,000 - 50,000 m/s) that is optimum for near-to-mid-term megawatt-class solar- and nuclear-electric propulsion vehicles used for Mars missions transporting cargo (in support of a piloted mission). Research and modeling on the Li-LFA engine are currently being performed by JPL (cathode development), Moscow Aviation Institute (engine testing), Thermacore (electrode development), as well as at MIT (plume modeling), and USC (diagnostics). Also, the mission performance of a nuclear-electric propulsion (NEP) Li-LFA Mars cargo vehicle is being modeled by JPL (mission analysis; thruster and power processor modeling) and the Rocketdyne Energy Technology and Engineering Center (ETEC) (power system modeling). Finally, the fusion propulsion research activities that JPL is supporting at Pennsylvania State University (PSU) and at Lawrenceville Plasma Physics (LPP) are aimed at far-term fast (less than 100 day round trip) piloted Mars missions and, in the very far term, interstellar missions.

Frisbee, Robert H.↗

CUDA Computation of the Feynman Distribution

In 2006, NVIDIA Corporation introduced the Computer Unified Device Architecture (CUDA) for C, C++, and Fortran programming languages. The CUDA parallel computing platform uses the Graphics Processing Unit (GPU) of NVIDIA graphics card, and it is designed for parallel computations. In these computations, the same algorithms are executed on the data in parallel. The GPU contains many Streaming Multiprocessors (SM) that can independently execute blocks of threads. A thread is a sequence of serial programmed instructions. The SM executes threads in groups of 32 and a group of 32 threads is called warp. The threads within a block can be synchronized and have access to a shared memory that is visible only to them. Conversely, blocks of threads cannot be synchronized and have access only to the global memory of the graphics card. This memory is called device memory and is independent of the host memory controlled by the Central Processing Unit (CPU). A single thread has access to a local memory (register) that is not visible to any other thread. The part of the program that is executed on the graphics card is called kernel. Each thread of the kernel has a unique identification index that is accessible by the in-built variable threadIdx; the latter is a 3-component vector. A threads block can contain up to 1024 threads. Blocks of threads have a unique identification index that is accessible by the in-built variable blockIdx; the latter is a 3-component vector. The in-built variable blockDim contains the number of threads per block; this variable is a 3-component vector. Threads and blocks represent different levels of parallelism; a kernel is executed as a grid of blocks of threads. Figure 1 illustrates a grid of thread blocks for a GPU with 2 SM. A SM can execute multiple blocks of threads in parallel; a block of threads is executed on a single SM. A GPU can execute multiple kernels concurrently. This work has used the Quadro M5000 graphics card with the following technical specifications: - 2048 cores with 861 MHz frequency, - 16 streaming multiprocessors, - 5.2 trillion transistors, - 8.2 Gb device memory, - 64 kb register memory (per thread), - 48 kb shared memory (per block) - 211.6 GB/s memory bandwidth, and - 3.5 GFLOPS floating point performance.

97 MATHEMATICS AND COMPUTING↗

Managing Waste Inventory and License Limits at the Perma-Fix Northwest Facility to Meet CH2M Hill Plateau Remediation Company (CHPRC) American Recovery and Reinvestment Act (ARRA) Deliverables - 12335

CH2M Hill Plateau Remediation Company (CHRPC) is a prime contractor to the U.S. Department of Energy (DOE) focused on the largest ongoing environmental remediation project in the world at the DOE Hanford Site Central Plateau, i.e. the DOE Hanford Plateau Remediation Contract. The East Tennessee Materials and Energy Corporation (M and EC); a wholly owned subsidiary of Perma-Fix Environmental Services, Inc. (PESI), is a small business team member to CHPRC. Our scope includes project management; operation and maintenance of on-site storage, repackaging, treatment, and disposal facilities; and on-site waste management including waste receipt from generators and delivery to on-site and off-site treatment, storage, and disposal facilities. As part of this scope, M and EC staffs the centralized Waste Support Services organization responsible for all waste characterization and acceptance required to support CHPRC and waste generators across the Hanford Site. At the time of the CHPRC contract award (August 2008) slightly more than 9,000 cubic meters (m{sup 3}) of legacy waste was defined as 'no-path-forward waste'. A significant portion of this waste (7,650 m{sup 3}) comprised wastes with up to 50 grams of special nuclear materials (SNM) in oversized packages recovered during retrieval operations and large glove boxes removed from the Plutonium Finishing Plant (PFP). Through a collaborative effort between the DOE, CHPRC, and Perma-Fix Environmental Services, Inc. (PESI), pathways for these problematic wastes were developed that took advantage of commercial treatment capabilities at a nearby vendor facility, Perma-Fix Northwest (PFNW). In the spring of 2009, CHPRC initiated a pilot program under which they began shipping large package, low gram suspect TRU (<15 g SNM per container), and large package contact and remote handled MLLW to the off-site PFNW facility for treatment. PFNW is restricted by the SNM limits set for the total quantity of SNM allowed at the facility in accordance with the facility's radioactive materials license(s) (RML). While both CHPRC and PFNW maintain waste databases to track all waste movements, it became evident early in the process that a tool was needed that married the two systems to better track SNM inventories and sequence waste from the point of generation, through the PFNW facility, and back to the Hanford site for final disposition. This tool, known as the Treatment Integration and Planning Tool (TIPT), has become a robust planning tool that provides real-time data to support compliant and efficient waste generation, transportation, treatment, and disposition. TIPT is developing into the next generation tool that will change the way in which legacy wastes, retrieval wastes and decontamination and decommissioning operations are conducted on the Plateau Remediation Contract (PRC). The real value of the TIPT is its predictive capability. It allows the W and FMP to map out optimal windows for processing waste through the PFNW facility, or through any process that is in some way resource limited. It allows project managers to identify and focus on problem areas before shipments are affected. It has been modified for use in broader applications to predict turnaround times and identify windows of opportunity for processing higher gram wastes through PFNW and to allow waste generators, site-wide, to accurately predict scope, cost, and schedule for waste generation to optimize processing and eliminate storage, double handling, and related costs and unnecessary safety risks. The TIPT addresses the years old problem of how to effectively predict not only what needs to be done, but when. 'When' is the key planning parameter that has been ignored by the generator and processor for many years, but has proven to be the most important parameter for both parties. While further refinement is a natural part of any development process, the current improvements on the TIPT have shown that prediction is a powerful consideration. Even in lean times expected for the foreseeable future, the improved TIPT continues to play a central role in managing our way through those times to assure facilities remain viable and available. It is recommended that other major remediation projects and waste processing facilities incorporate a tool such as TIPT to improve customer-commercial supplier communications and better optimization of resources. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Multi-Zone Liquid Thrust Chamber Performance Code with Domain Decomposition for Parallel Processing

Computational Fluid Dynamics (CFD) has considerably evolved in the last decade. There are many computer programs that can perform computations on viscous internal or external flows with chemical reactions. CFD has become a commonly used tool in the design and analysis of gas turbines, ramjet combustors, turbo-machinery, inlet ducts, rocket engines, jet interaction, missile, and ramjet nozzles. One of the problems of interest to NASA has always been the performance prediction for rocket and air-breathing engines. Due to the complexity of flow in these engines it is necessary to resolve the flowfield into a fine mesh to capture quantities like turbulence and heat transfer. However, calculation on a high-resolution grid is associated with a prohibitively increasing computational time that can downgrade the value of the CFD for practical engineering calculations. The Liquid Thrust Chamber Performance (LTCP) code was developed for NASA/MSFC (Marshall Space Flight Center) to perform liquid rocket engine performance calculations. This code is a 2D/axisymmetric full Navier-Stokes (NS) solver with fully coupled finite rate chemistry and Eulerian treatment of liquid fuel and/or oxidizer droplets. One of the advantages of this code has been the resemblance of its input file to the JANNAF (Joint Army Navy NASA Air Force Interagency Propulsion Committee) standard TDK code, and its automatic grid generation for JANNAF defined combustion chamber wall geometry. These options minimize the learning effort for TDK users, and make the code a good candidate for performing engineering calculations. Although the LTCP code was developed for liquid rocket engines, it is a general-purpose code and has been used for solving many engineering problems. However, the single zone formulation of the LTCP has limited the code to be applicable to problems with complex geometry. Furthermore, the computational time becomes prohibitively large for high-resolution problems with chemistry, two-equation turbulence model, and two-phase flow. To overcome these limitations, the LTCP code is rewritten to include the multi-zone capability with domain decomposition that makes it suitable for parallel processing, i.e., enabling the code to run every zone or sub-domain on a separate processor. This can reduce the run time by a factor of 6 to 8, depending on the problem.

Homayun K. Navaz↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASAs Space Launch System

The engineering development of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS) requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The nominal and off-nominal characteristics of SLS's elements and subsystems must be understood and matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex systems engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model-based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model-based algorithms and their development lifecycle from inception through FSW certification are an important focus of SLS's development effort to further ensure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. To test and validate these M&FM algorithms a dedicated test-bed was developed for full Vehicle Management End-to-End Testing (VMET). For addressing fault management (FM) early in the development lifecycle for the SLS program, NASA formed the M&FM team as part of the Integrated Systems Health Management and Automation Branch under the Spacecraft Vehicle Systems Department at the Marshall Space Flight Center (MSFC). To support the development of the FM algorithms, the VMET developed by the M&FM team provides the ability to integrate the algorithms, perform test cases, and integrate vendor-supplied physics-based launch vehicle (LV) subsystem models. Additionally, the team has developed processes for implementing and validating the M&FM algorithms for concept validation and risk reduction. The flexibility of the VMET capabilities enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS, GNC, and others. One of the principal functions of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software test and validation processes. In any software development process there is inherent risk in the interpretation and implementation of concepts from requirements and test cases into flight software compounded with potential human errors throughout the development and regression testing lifecycle. Risk reduction is addressed by the M&FM group but in particular by the Analysis Team working with other organizations such as S&MA, Structures and Environments, GNC, Orion, Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission (LOM) and Loss of Crew (LOC) probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses to be tested in VMET to ensure reliable failure detection, and confirm responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - the ARINC 6535-partitioned Operating System, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by FSW. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure their effectiveness and performance in the exterior FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗

The Genesis Non-flight Implant Sample Archive

Introduction: For the past 20 years the Genesis science community has been analyzing solar wind captured in sample collectors now curated at Johnson Space Center (JSC). Non-flown flight like collector materials (non-flight) considered reference material was always allocated by the JSC Genesis team for testing experimental procedures. However, to expedite Genesis science, distribution of non-flown reference materials were also provided by, D. S. Burnett (Genesis PI, Caltech) and A. J. G. Jurewicz (ASU) who were funded to aid all Genesis PIs by providing engineering test materials archived at Caltech pre-flight as well as ion implants into these materials [1]. Implanted materials (non-flight reference, flight-like semiconductor materials, and NIST SRM glass) received from the Caltech collection during a pilot project are being used to develop an accession procedure for the purpose of making these materials available to researchers in the future. These implant samples are important because they can be utilized as measurement standards [2]. This is a work in progress and this work reports progress in documentation and imaging. The pilot program received 63 implanted reference materials with known implanted ions. Genesis Non-Flight Database: The existing non-flight material database was modified to allow for the description of implant sessions and to allow correlation of the implant information to individual specimens. An implant session has three main components: a known ion, a known dose (ion/cm2), and a known energy (keV). Procedure: Laboratory Procedure. Upon receiving non-flight analytical standards (independently calibrated implants), or implant samples (nominally calibrated implants), they will be imaged in their current containers to capture any information written before being brought into the Genesis Sample Laboratory. Documentation is provided by the donor and used for correlating the data between the implant sessions and implant samples. This information is not verified by Genesis Curation. The microscope used to image samples in the laboratory has an automated stage with a stainless-steel plate to hold samples and a camera that utilizes the software Surveyor to take photomosaic images of the implant samples. The camera attached to the microscope is a QICAM High Performance IEEE 1394 FireWire Digital CCD Camera. This setup, shown in Fig. 1, allows for photomosaics of small-scale samples with a 10x objective or 25x objective. Examples of images taken with this microscope setup are shown in Fig.2 and Fig. 3. After imaging, samples get stored in a clean fluoroware container or polypropylene vial depending on sample size for long term storage. Database Procedure. The Genesis Non-Flight Database currently allows for the addition of implant sessions. The required fields for adding an implant session are the implant session ion, the implant session dose, and the implant session energy. There are also fields for the date and vendor of the sessions as well as a field for if the session was calibrated or not. Once an implant session has been inserted into the database, additional documentation from the session can be attached. The database will automatically assign an Implant Session Number. After inserting an implant session, the implanted samples can be inserted. The fields required for an implant sample are the material of the sample and the size of the sample. The Generic name for the implant sample with be automatically generated by the database once it has been inserted. Implant sample numbers begin with 3X to distinguish from flown Genesis sample numbers. There are also fields for processors to add the location (room, cabinet, tray) and container type (fluoroware, polypropylene vial). Once an implant session and an associated sample(s) have been inserted into the database the sample can be then tied to all associated implant sessions. An implant sample can be tied to multiple implant sessions. Future work: For curation, future work consists of creating an online catalogue for implant samples as well as updating the database with more samples as we receive them. For the scientific community these implant samples have many potential uses. For Genesis research, they are directly applicable for testing and, in some cases, as analytical standards. For non-Genesis research, implants (especially calibrated implants) could be used for calibrating other, unique planetary materials [1].

C D Calva↗

Inclusion of Scatter in HADES: Final Report

Covert nuclear attack is one of the foremost threats facing the United States and is a primary focus of the War on Terror. The Domestic Nuclear Detection Office (DNDO), within the Department of Homeland Security (DHS), is chartered to develop, and improve domestic systems to detect and interdict smuggling for the illicit use of a nuclear explosive device, fissile material or radiologica1 material. The CAARS (Cargo Advanced Automated Radiography System) program is a major part of the DHS effort to enhance US security by harnessing cutting-edge technologies to detect radiological and nuclear threats at points of entry to the United States. DNDO has selected vendors to develop complete radiographic systems. It is crucial that the initial design and testing concepts for the systems be validated and compared prior to the substantial efforts to build and deploy prototypes and subsequent large-scale production. An important aspect of these systems is the scatter which interferes with imaging. Monte Carlo codes, such as MCNP (X-5 Monte Carlo Team, 2005 Revision) allow scatter to be calculatied, but these calculations are very time consuming. It would be useful to have a fast scatter estimation algorithm in a fast ray tracing code. We have been extending the HADES ray-tracing radiographic simulation code to model vendor systems in a flexible and quick fashion and to use this tool to study a variety of questions involving system performance and the comparative value of surrogates. To enable this work, HADES has been linked to the BRL-CAD library (BRL-CAD Open Source Project, 2010), in order to enable the inclusion of complex CAD geometries in simulations, scanner geometries have been implemented in HADES, and the novel detector responses have been included in HADES. A major extension of HADES which has been required by this effort is the inclusion of scatter in these radiographic simulations. Ray tracing codes generally do not easily allow the inclusion of scatter, because these codes define a source and a grid of detector pixels and only compute the attenuation along rays between these points. Scatter is an extremely complex set of processes which can involve rays which change directions many times between the source and detector. Scatter from outside the field of view of the imaging system, as well as within the field of view, can have an important role in image formation. In this report, we will describe how we implemented a treatment of scatter in HADES. We begin with a discussion of how we define scatter in Section 2, followed by a description of how single Compton scatter is now included in HADES in Section 3. In Section 4 we report a set of verification tests against MCNP and tests of how the technique scales with image size, number of scatters allowed and number of processors used in the calculations. In Section 5, we describe how we plan to extend this approach to other forms of scatter and conclude in Section 6. It should be emphasized that the purpose of this report is to show that a form of scatter has been implemented in HADES and has been verified against MCNP. Validation, the process of comparing simulation and experiment, is a future task.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

Preface to the Special Issue on TOUGH Symposium 2015

The TOUGH Symposium 2015 was held in Berkeley, California, September 28-30, 2015. The TOUGH family of codes, developed at the Energy Geosciences Division of Lawrence Berkeley National Laboratory (LBNL), is a suite of computer programs for the simulation of multiphase and multicomponent fluid and heat flows in porous and fractured media with applications in many geosciences fields, such as geothermal reservoir engineering, nuclear waste disposal, geological carbon sequestration, oil and gas reservoirs, gas hydrate research, vadose zone hydrology and environmental remediation. Since the first release in the 1980s, many modifications and enhancements have been continuously made to TOUGH and its various descendants (iTOUGH2, TOUGH+, TOUGH-MP, TOUGHREACT, TOUGH+HYDRATE, TMVOC...), at LBNL and elsewhere. Today, these codes are used worldwide in academia, government organizations and private companies in problems involving coupled hydrological, thermal, biogeochemical and geomechanical processes. The Symposia, organized every 2-3 years, bring together developers and users for an open exchange on recent code enhancements and applications. In 2015, the Symposium was attended by one hundred participants, representing thirty-four nationalities. This Special Issue in Computers & Geosciences gathers extended versions of selected Symposium proceedings related to (i) recent enhancements to the TOUGH family of codes and (ii) coupled flow and geomechanics processes modeling. In this special issue, a paper by Jung et al. provides a new base version of TOUGH, TOUGH3. This latest version addresses the computational robustness and efficiency needed for the increasing complexity of the simulated processes and the growing size of model domains. Moreover, it consolidates the serial and parallel versions into a single code, hence, inconsistencies between different versions are less likely to occur, and code maintenance and development become more efficient. Finsterle et al. present a review of the capabilities of iTOUGH2 and illustrate the workflow of an integrated simulation-optimization framework. Liu et al. present an approach to reduce the computational cost of performing Bayesian inverse modeling and demonstrate their approach using a synthetic experiment simulated with TOUGH2. Regarding the mesh generation process, the paper by Doughty presents a generalization of the grid-generation algorithm embedded in TOUGH2 (MESHMAKER) to create one-column grids with fractal dimension, useful for representing flow through fractures or highly heterogeneous media with fractal geometry, and also for inverse methods. Sentís and Gable present a module to interface the open source code Lagrit with TOUGH2, that assists in the processes of mesh generation and model setup, and that can be particularly useful for complex geometries and large models. Bonduà et al. present a pre-processing tool (VORO2MESH) that features a full 3D Voronoi approach for structured and unstructured grids, and an enhanced post-processor (TOUGH2Viewer) for the visualization of 3D Voronoi grids. The literature review shows that coupled fluid flow and geomechanics has gained increasing attention in the last years in many geosciences fields. In this context, several codes of the TOUGH family have been successfully coupled with geomechanics software. The paper by Rutqvist presents a review of some of these TOUGH-based geomechanics models, of which the TOUGH-FLAC simulator – presented for the first time in the TOUGH Symposium 2003 – is well-known worldwide and has been used in a large variety of applications, encompassing the application domains of the TOUGH codes. Blanco-Martín et al. present an extension of TOUGH-FLAC to the finite strain framework, motivated by the existence of large strains associated with rock salt deformation in the context of heat-generating nuclear waste disposal. Following a paper published in the Special Issue of the TOUGH Symposium 2012 in this journal, Kim et al. present the current status of the TOUGH-RSBN simulator for coupled hydro-mechanical modeling of hydraulic fracturing using a discrete fracture network approach, and present some validation and demonstration cases. Rinaldi and Nespoli present TOUGH-SEED, an injection-induced seismicity modeling approach using TOUGH2 and a geomechanics stochastic model, and apply it to the Basel EGS project. Finally, Rinaldi et al. use the PEST protocol implemented in iTOUGH2, combined with TOUGH-FLAC as the forward model, to perform inverse modeling for the In Salah CO2 demonstration site in Algeria. Using pore pressures and InSAR displacements as observations, this approach allows for a multi-physics joint inversion and takes advantage of the inverse capabilities of iTOUGH2 (parameter estimation, sensitivity analysis, uncertainty estimation …), applied to coupled fluid flow and geomechanics. On behalf of the members of the TOUGH Symposium 2015 Organizing Committee, I hope that this collection of papers will provide the readers of Computers & Geosciences with a recent view of the capabilities of the TOUGH family of codes, as well as with current modeling research domains in the geosciences. Last but not least, I would like to express my gratitude to all the reviewers who kindly contributed to this Special Issue, as well as the Journal staff who have made this publication possible.

99 GENERAL AND MISCELLANEOUS↗

Evaluation of Graph Analytics Frameworks Using the GAP Benchmark Suite

The analysis of connected data is an increasingly important application in high-performance computing. Such analyses can reveal fraudulent patterns in financial transactions, optimize telecommunications networks, predict information flow in social networks, etc. However, the landscape of graph analytics is highly diverse. Graph algorithms stress processor architectures differently, and no one graph can represent all topologies. Consequently, no single approach or framework is expected to be optimal for all graph analytics problems. To help make sense of this diverse landscape, we evaluated four approaches to graph analytics: GraphBLAS, Galois, BGL17, GraphIt; and compare them against hand-tuned implementations that take advantage of hardware features on our test platform. Graph- BLAS formulates graph analytics as sparse linear algebra. Galois provides syntactic constructs for data parallelism over irregular data structures. BGL17 is a generic C++ template library for implementing graph algorithms. GraphIt provides a domain- specific language to describe and optimize graph algorithms. We use the GAP Benchmark Suite to establish baseline performance and guide the side-by-side evaluation of each framework. GAP consists of 30 tests: six graph analytics algorithms (breadth- first search, single-source shortest path, PageRank, betweenness centrality, connected components, and triangle counting) run on five graphs, each with different topological characteristics (e.g., high diameter, skewed degree distribution, high average degree). High-performance reference implementations are included for each benchmark algorithm. Because a graph can be loaded into memory a number of ways (e.g., flat file on disk, compressed sparse format, data frames, retrieved from SQL or NoSQL databases), our evaluation focused on computational performance rather than I/O. Our results show the relative strengths of each framework.

Graph algorithms, Benchmarking, shared-memory prog↗

Skel: Generative Software for Producing Skeletal I/O Applications

Massively parallel computations consist of a mixture of computation, communication, and I/O. As part of the co-design for the inevitable progress towards exascale computing, we must apply lessons learned from past work to succeed in this new age of computing. Of the three components listed above, implementing an effective parallel I/O solution has often been overlooked by application scientists and was usually added to large scale simulations only when existing serial techniques had failed. As scientists teams scaled their codes to run on hundreds of processors, it was common to call on an I/O expert to implement a set of more scalable I/O routines. These routines were easily separated from the calculations and communication, and in many cases, an I/O kernel was derived from the application which could be used for testing I/O performance independent of the application. These I/O kernels developed a life of their own used as a broad measure for comparing different I/O techniques. Unfortunately, as years passed and computation and communication changes required changes to the I/O, the separate I/O kernel used for benchmarking remained static no longer providing an accurate indicator of the I/O performance of the simulation making I/O research less relevant for the application scientists. In this paper we describe a new approach to this problem where I/O kernels are replaced with skeletal I/O applications automatically generated from an abstract set of simulation I/O parameters. We realize this abstraction by leveraging the ADIOS middleware's XML I/O specification with additional runtime parameters. Skeletal applications offer all of the benefits of I/O kernels including allowing I/O optimizations to focus on useful I/O patterns. Moreover, since they are automatically generated, it is easy to produce an updated I/O skeleton whenever the simulation's I/O changes. In this paper we analyze the performance of automatically generated I/O skeletal applications for the S3D and GTS codes. We show that these skeletal applications achieve performance comparable to that of the production applications. We wrap up the paper with a discussion of future changes to make the skeletal application better approximate the actual I/O performed in the simulation.

99 GENERAL AND MISCELLANEOUS↗

pyRMG: A framework for high-throughput, large-cell DFT calculations on supercomputers

Exascale computing delivers the raw power to simulate ever larger and more chemically realistic systems, but realizing this potential requires codes that can efficiently use thousands of processors. Our real-space multigrid (RMG) density functional theory (DFT) code’s grid-decomposition approach scales nearly linearly with the number of graphics processing units (GPUs), even for simulations exceeding thousands of atoms. This scalability makes RMG a compelling tool for high-throughput DFT studies of materials that would otherwise be bottlenecked in other codes (for example, by global fast Fourier transforms in plane-wave DFT). However, the limited workflow infrastructure for RMG has thus far constrained its adoption to a small user community. In this work, we present pyRMG, a Python package designed to streamline the setup and execution of RMG DFT calculations. Built on the pymatgen and ASE (Atomic Simulation Environment) computational materials science Python packages, pyRMG automates input generation and convergence checking, and it integrates with modern job schedulers (e.g., Flux) on leadership-class platforms such as Frontier and Perlmutter. Here, we demonstrate pyRMG for a high-throughput study of strain effects in 2D 2L-Bi 2 Se 3 /2L-NbSe 2 heterostructures, which offers chemical insights into this system and shows that RMG-based workflows can converge with limited user intervention.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

Development of a GPU-based high-performance radiative transfer model for the Infrared Atmospheric Sounding Interferometer (IASI)

Satellite-observed radiance is a nonlinear functional of surface properties and atmospheric temperature and absorbing gas profiles as described by the radiative transfer equation (RTE). In the era of hyperspectral sounders with thousands of high-resolution channels, the computation of the radiative transfer model becomes more time-consuming. The radiative transfer model performance in operational numerical weather prediction systems still limits the number of channels we can use in hyperspectral sounders to only a few hundreds. To take the full advantage of such high-resolution infrared observations, a computationally efficient radiative transfer model is needed to facilitate satellite data assimilation. In recent years the programmable commodity graphics processing unit (GPU) has evolved into a highly parallel, multi-threaded, many-core processor with tremendous computational speed and very high memory bandwidth. The radiative transfer model is very suitable for the GPU implementation to take advantage of the hardware's efficiency and parallelism where radiances of many channels can be calculated in parallel in GPUs. In this paper, we develop a GPU-based high-performance radiative transfer model for the Infrared Atmospheric Sounding Interferometer (IASI) launched in 2006 onboard the first European meteorological polar-orbiting satellites, METOP-A. Each IASI spectrum has 8461 spectral channels. The IASI radiative transfer model consists of three modules. The first module for computing the regression predictors takes less than 0.004% of CPU time, while the second module for transmittance computation and the third module for radiance computation take approximately 92.5% and 7.5%, respectively. Our GPU-based IASI radiative transfer model is developed to run on a low-cost personal supercomputer with four GPUs with total 960 compute cores, delivering near 4 TFlops theoretical peak performance. By massively parallelizing the second and third modules, we reached 364x speedup for 1 GPU and 1455x speedup for all 4 GPUs, both with respect to the original CPU-based single-threaded Fortran code with the -O{sub 2} compiling optimization. The significant 1455x speedup using a computer with four GPUs means that the proposed GPU-based high-performance forward model is able to compute one day's amount of 1,296,000 IASI spectra within nearly 10 min, whereas the original single CPU-based version will impractically take more than 10 days. This model runs over 80% of the theoretical memory bandwidth with asynchronous data transfer. A novel CPU-GPU pipeline implementation of the IASI radiative transfer model is proposed. The GPU-based high-performance IASI radiative transfer model is suitable for the assimilation of the IASI radiance observations into the operational numerical weather forecast model.

97 MATHEMATICS AND COMPUTING↗

X-Ray Computed Tomography During Preliminary Examination of Apollo Drive Tube 73001

Introduction: Starting in 2019, the Apollo Next Generation Sample Analysis (ANGSA) Program has enabled consortium studies of specially curated Apollo samples that were previously unstudied (or under studied). This began with unsealed core tube 73002 [1,2] that is the upper part of a station 3 double drive tube. More recently the pro-gram extended to the study of a variety of frozen Apollo 17 samples [3], as well as the gas extraction [4] and dis-section [5] of 73001, the lower half of the station 3 double drive tube, that was sealed under vacuum on the Moon. In this abstract we will examine the role of X-ray Computed Tomography (XCT) during the preliminary examination process for sealed core 73001, including: (1) engineering scans to aid in understanding the gas extraction process, whole-core scanning prior to opening to inform extrusion and dissection work, and (3) individual particle scanning to characterize rock fragment lithologies for follow on studies. Methodology: Sample 73001 is a 33 cm long, 4 cm diameter regolith sample collected inside a drive tube (~1 mm aluminum walls). That drive tube was sealed inside a 0.5 mm thick stainless steel (SS) Core Sample Vacuum Container (CSVC). XCT scans for engineering purposes were done on the Nikon XTH 320 system at Johnson Space Center using the 225 kV multi-metal reflection source at 215 kV, 179 A, and a 38.49 m voxel size. Individual >4 mm particles separated from the core during processing (then triply sealed in Teflon bags) were also scanned at JSC using the 180 kV source at 90 kV, 33 A, and a 2.98 – 10.65 m voxel size. Whole-core scans were done at the University of Texas High-Resolution X-ray Computed Tomography Facility (UTCT) on the 225 kV reflection source on the North Star Imaging cabinet XCT system. These scans included: (1) a series of 9 overlapping super-resolution scans each covering a ~4 cm length of the tube at 190 kV, 180 µA, and a 12.9 µm voxel size and (2) a lower resolution continuous helical scan of the entire core at 190 kV, 180 µA, and a 51.8 µm voxel size. Progress and Results: Before piercing and extracting the gas from sample 73001, an XCT scan of the bottom portion of the CSVC was used to confirm the location of the Teflon cap on the inner drive tube, to ensure it was not accidentally pierced during gas extraction. Similarly, after piercing, the bottom and top portions of the CSVC were scanned in order to capture engineering knowledge about the results of the piercing process, as well as the metal knife edge vacuum seal (SS into In-Ag alloy). Both scans will provide constraints on future work of this type, particularly for samples collected during the Artemis mission. Another finding from these "engineering" scans was that the device in the drive tube that immobilizes the regolith (the keeper) was not seated in the tube properly. This meant that (1) the drive tube could not be removed from the CSVC for the trip to UTCT, and (2) the procedure for opening and extruding the drive tube had to be modified. Had either of these things not been known prior to opening the CSVC, it could have led to an inability to XCT scan the whole core at high resolution and/or potential disruption of the core stratigraphy during extrusion. At UTCT, the entire length of the core was scanned at high resolution (12.9 microns per voxel). This scan serves multiple purposes: (1) A lower resolution (and uncorrected) version of these scans stitched together was used to help inform the processors of potential pitfalls during extrusion and dissection; and (2) the full resolution corrected data will serve as the permanent in situ record of the stratigraphy of the sample and will enable future researchers to perform a variety of analyses. So far, 92 of the 121 >4 mm particles separated during dissection pass 1 of sample 73001 have been individually scanned. These scans clearly show the lithology of each particle while keeping the particles in pristine condition. Because of the dust adhering to particle exteriors it would otherwise be impossible to determine lithologies in a non-contaminating way. Thus far the types of lithologies seen in sample 73001 (e.g., regolith breccias, impact-melt breccias, agglutinates, and basalts) are similar to those previously identified in sample 73002 [2]. By the time of the meeting, all particles from all 3 dissection passes will have been scanned and statistics on the different lithologies in 73001 compiled. References: [1] Shearer et al. (2020) 51st LPSC, abstract 1181. [2] Zeigler et al. (2020) 51st LPSC, abstract 3023. [3] Kent et al. (2022) This Volume. [4] McDonald et al. (2022) European Lunar Symposium. [5] Gross et al (2022) This volume.

Moon↗

X-Ray Computed Tomography of Apollo Drive Tube 73001 as Part of the Apollo Next Generation Sample Analysis Program

Introduction: Starting in 2019, the Apollo Next Generation Sample Analysis (ANGSA) Program has enabled consortium studies of specially curated Apollo samples that were previously unstudied (or under studied). This program was intended as a participating scientist program for these Apollo samples, as well as a preparation for upcoming lunar sample return missions (e.g., Artemis). The work began with studies of unsealed core tube 73002 [1,2] that is the upper ~35 cm of an Apollo 17 double drive tube (~70 cm total depth) collected on the landslide deposit near Lara Crater at Station 3 in the Taurus Littrow Valley. More recently the program extended to the study of a variety of frozen Apollo 17 samples [3], as well as the gas extraction [4] and dissection [5] of 73001, the lower half of the station 3 double drive tube. Sample 73001 was sealed under vacuum on the Moon in a Core Sample Vacuum Container (CSVC). In this abstract we will examine the role of X-ray Computed Tomography (XCT) during the preliminary examination process for sealed core 73001, including: (1) engineering scans to aid in understanding the gas extraction process, (2) whole-core scanning prior to opening to inform extrusion and dissection work, and (3) individual particle scanning to characterize rock fragment lithologies for follow on studies. Methodology: Sample 73001 is a 33 cm long, 4 cm diameter regolith sample collected inside a lunar drive tube (~1 mm aluminum walls). That drive tube was sealed inside a 0.5 mm thick stainless steel (SS) CSVC. XCT scans for engineering purposes were done on the Nikon XTH 320 system at Johnson Space Center using the 225 kV multi-metal reflection source at 215 kV, 179 A, and a 38.49 m voxel size. Individual >4 mm particles separated from the core during processing (then triply sealed in Teflon bags) were also scanned at JSC using the 180 kV source at 90 kV, 33 A, and a 2.98 – 10.65 m voxel size. Whole-core scans were done at the University of Texas High-Resolution X-ray Computed Tomography Facility (UTCT) on the 225 kV reflection source on the North Star Imaging cabinet XCT system. These scans included: (1) a series of 9 overlapping super-resolution scans each covering a ~4 cm length of the tube at 190 kV, 180 µA, and a 12.9 µm voxel size and (2) a lower resolution continuous helical scan of the entire core at 190 kV, 180 µA, and a 51.8 µm voxel size. Progress and Results: Before piercing and extracting the gas from sample 73001, an XCT scan of the bottom portion of the CSVC was used to confirm the location of the Teflon cap on the inner drive tube and whether there was an “air” gap between the Teflon cap and the CSVC. This was to ensure the Teflon cap (which immobilized the soil inside the drive tube) was not accidentally pierced during gas extraction. Similarly, after piercing, the bottom and top portions of the CSVC were scanned in order to capture engineering knowledge about the results of the piercing process, as well as the metal knife edge vacuum seal (SS into an In-Ag alloy). Both scans will provide constraints on future work of this type, both for the design of tools used on the lunar surface during Artemis, as well as how we open future samples of this type. An unexpected finding from these engineering scans was that the device in the drive tube that immobilizes the regolith (the keeper) was not seated in the tube properly. This meant that (1) the drive tube could not be removed from the CSVC for the trip to UTCT, and (2) the procedure for opening and extruding the drive tube had to be modified. Had either of these things not been known prior to opening the CSVC, it could have led to an inability to XCT scan the whole core at high resolution and/or potential disruption of the core stratigraphy during extrusion. At UTCT, the entire length of the core was scanned at high resolution (12.9 microns per voxel). This scan serves multiple purposes: (1) A lower resolution (and uncorrected) version of these scans stitched together was used to help inform the processors of potential pitfalls during extrusion and dissection (voids, angular fragments at the edges of the sample, etc.); and (2) the full resolution corrected data will serve as the permanent in situ record of the stratigraphy of the sample and will enable future researchers to perform a variety of analyses. All 121 >4 mm particles separated during dissection pass 1 of sample 73001 have been individually scanned. These scans clearly show the lithology of each particle while keeping the particles in pristine condition (they are individually triply bagged in Teflon within our N2 purged processing cabinets). Because of the dust adhering to particle exteriors, it would otherwise be impossible to determine lithologies in a non-contaminating way. Thus far the types of lithologies seen in sample 73001 (e.g., regolith breccias, impact-melt breccias, agglutinates, and bas-alts) are similar to those previously identified in sample 73002 [2]. By the time of the meeting, all particles from all 3 dissection passes will have been scanned and statistics on the different lithologies in 73001 compiled. References: [1] Shearer et al. (2020) 51st LPSC, abstract 1181. [2] Zeigler et al. (2020) 51st LPSC, abstract 3023. [3] Kent et al. (2022) This Volume. [4] McDonald et al. (2022) European Lunar Symposium. [5] Gross et al (2022) This volume.

Moon↗

Solar Dynamics Observatory Guidance, Navigation, and Control System Overview

The Solar Dynamics Observatory (SDO) was designed and built at the Goddard Space Flight Center, launched from Cape Canaveral on February 11, 2010, and reached its final geosynchronous science orbit on March 16, 2010. The purpose of SDO is to observe the Sun and continuously relay data to a dedicated ground station. SDO remains Sun-pointing throughout most of its mission for the instruments to take measurements of the Sun. The SDO attitude control system (ACS) is a single-fault tolerant design. Its fully redundant attitude sensor complement includes sixteen coarse Sun sensors (CSSs), a digital Sun sensor (DSS), three two-axis inertial reference units (IRUs), and two star trackers (STs). The ACS also makes use of the four guide telescopes included as a part of one of the science instruments. Attitude actuation is performed using four reaction wheels assemblies (RWAs) and eight thrusters, with a single main engine used to provide velocity-change thrust for orbit raising. The attitude control software has five nominal control modes, three wheel-based modes and two thruster-based modes. A wheel-based Safehold running in the attitude control electronics box improves the robustness of the system as a whole. All six modes are designed on the same basic proportional-integral-derivative attitude error structure, with more robust modes setting their integral gains to zero. This paper details the final overall design of the SDO guidance, navigation, and control (GN&C) system and how it was used in practice during SDO launch, commissioning, and nominal operations. This overview will include the ACS control modes, attitude determination and sensor calibration, the high gain antenna (HGA) calibration, and jitter mitigation operation. The Solar Dynamics Observatory mission is part of the NASA Living With a Star program, which seeks to understand the changing Sun and its effects on the Solar System, life, and society. To this end, the SDO spacecraft carries three Sun-observing instruments: Helioseismic and Magnetic Imager (HMI), led by Stanford University; Atmospheric Imaging Assembly (AIA), led by Lockheed Martin Space and Astrophysics Laboratory; and Extreme Ultraviolet Variability Experiment (EVE), led by the University of Colorado. The basic mission is to observe the Sun for a very high percentage of the 5-year mission (10-year goal) with long stretches of uninterrupted observations and with constant, high-data-rate transmission to a dedicated ground station to be located in White Sands, New Mexico. These goals guided the design of the spacecraft bus that will carry and service the three-instrument payload. Overarching design goals for the bus are geosynchronous orbit, near-constant Sun observations with the ability to fly through eclipses, and constant HGA contact with the dedicated ground station. A three-axis stabilized ACS is needed both to point at the Sun accurately and to keep the roll about the Sun vector correctly positioned with respect to the solar north pole. This roll control is especially important for the magnetic field imaging of HM I. The mission requirements have several general impacts on the ACS design. Both the AIA and HMI instruments are very sensitive to the blurring caused by jitter. Each has an image stabilization system (ISS) with some ability to filter out high frequency motion, but below the bandwidth of the ISS the control system must compensate for disturbances within the ACS bandwidth or avoid exciting jitter at higher frequencies. Within the ACS bandwidth, the control requirement imposed by AIA is to place the center of the solar disk no more than 2 arc sec, 3 , from a body-defined target based on one of the GTs that accompany the instrument. This body-defined target, called the science reference boresight (SRB), was determined from the postlaunch orientation of the GTs by averaging the bounding telescope boresights for pitch to get a pitch SRB coordinate, and by averaging the bounding boresights for yaw toet the yaw SRB coordinate. The location of this SRB in the 0.5-deg field-of-view for each GT then becomes the central target for each telescope; one GT is selected for use as the ACS controlling guide telescope (CGT) at any given time. Fine Sun-pointing is effected based on this SRB for all three instruments when the Sun is within the linear range of the CGT. In addition to limiting jitter, HMI science requires averaging several observations, making the instrument sensitive to low frequency motion that induces differential motion between each observation. This requires the spacecraft attitude to be stable about the roll axis to approximately 10 arcsec over a ten-minute period. Instrument calibrations require that the spacecraft point the SRB up to 2.5 degrees in pitch and yaw away from the center of the Sun, placing the Sun outside the field-of-view of the guide telescopes. In such instances, when the GTs cannot provide the definitive target for the ACS, on-board attitude determination combined with ephemeris prediction of the Sun direction must provide the definitive target. EVE is capable of observing the Sun with less dependence on attitude control. However, the ground data processing needs for calibrations result in the most strict attitude knowledge requirements for the mission: [35,70,70] arcsec, 3 , of knowledge with respect to the center of the solar disk. In addition to driving the ACS sensor selection, the knowledge requirements, which have their effect primarily during Inertial mode calibrations, drive the accuracy requirements for the solar ephemeris. The need to achieve and maintain geosynchronous orbit (GEO) drove the need for high-efficiency propulsive systems and appropriate attitude control. The main engine provided high specific impulse for the maneuvers to attain GEO, while the smaller ACS thrusters managed the disturbance torques of the larger engine and provided the capability for much smaller adjustment burns on orbit. SDO s large solar profile means that solar radiation pressure is a large torque disturbance, and the momentum buildup from this disturbance and the GEO altitude drives the ACS to use thrusters to manage vehicle momentum. The demanding data capture budget for the mission, however, requires SDO to avoid frequent thruster maneuvers, while concerns about on-orbit jitter restrict the maximum desired wheel speeds desired from the RWAs. The plan for on-orbit wheel speed and momentum management will be discussed as well as what is now being done in operation after the jitter environment was characterized. The SDO ACS hardware complement is single-fault tolerant. Two main processors carry virtually identical copies of the command and data handling and ACS software, and two identical attitude control electronics (ACE) boxes carry Coldfire processors with contingency ACS software and other hardware interface cards; the ACE structure allows reaction wheels to be commanded by the Sun-pointing Safehold independent of the Mil Std 1553 data bus. The sixteen Adcole CSSs are grouped into primary and backup sets of eight sensors, each set providing the ability to calculate a sun vector. Each set of eight eyes provides full 4 -steradian coverage. The Adcole DSS comprises an optics head and a separate electronics box providing a 1553 data interface. The electronics box is mounted inside the Faraday cage created by the spacecraft bus module. The DSS head with its 32- deg square FOV is mounted on the instrument module with its boresight along the spacecraft X axis, nearly aligned with the Sun during observations. Adcole has designed the DSS calibration parameters so that the accuracy is 0.24 arcminutes within 10 deg of the boresight, and diminishes to 3 arcminutes as the Sun moves towards the edges of its FOV . This DSS calibration scheme provides higher accuracy attitude determination over the range of the instrument calibration maneuvers.

Morgenstern, Wendy M.↗