Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “scope”

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 541 records · Page 30

T-1073: 2016 Precision Beam Timing Monitor

This is a technical scope of work (TSW) between the Fermi National Accelerator Laboratory (Fermilab) and the experimenters of Fermilab, Northern Illinois University (NIU), Lewis University, and Purdue University, who have committed to participate in beam tests to be carried out during the 2015-2016 Fermilab Test Beam Facility program. The TSW is intended primarily for the purpose of recording expectations for budget estimates and work allocations for Fermilab, the funding agencies and the participating institutions. It reflects an arrangement that currently is satisfactory to the parties; however, it is recognized and anticipated that changing circumstances of the evolving research program will necessitate revisions. The parties agree to modify this scope of work to reflect such required adjustments. Actual contractual obligations will be set forth in separate documents. This TSW fulfills Article 1 (facilities and scope of work) of the User Agreements signed (or still to be signed) by an authorized representative of each institution collaborating on this experiment.

43 PARTICLE ACCELERATORS↗

T-1068: The Beam Test for the SVX4 Telescope

This is a technical scope of work (TSW) between the Fermi National Accelerator Laboratory (Fermilab) and the experimenters of KEK and Osaka University who have committed to participate in beam tests to be carried out during the 2016 Fermilab Test Beam Facility program. The TSW is intended primarily for the purpose of recording expectations for budget estimates and work allocations for Fermilab, the funding agencies and the participating institutions. It reflects an arrangement that currently is satisfactory to the parties; however, it is recognized and anticipated that changing circumstances of the evolving research program will necessitate revisions. The parties agree to modify this scope of work to reflect such required adjustments. Actual contractual obligations will be set forth in separate documents. This TSW fulfills Article 1 (facilities and scope of work) of the User Agreements signed (or still to be signed) by an authorized representative of each institution collaborating on this experiment.

43 PARTICLE ACCELERATORS↗

Microchannel-based Membrane-less Extraction of Li from Unconventional Lithium Sources & the Separation of REE

This final report provides an overview of the Project's entire duration, covering July 1, 2021 to December 31, 2023. It primarily focuses on the achievements, technological developments, and unique challenges the team faced while working on separating and extracting Lithium from produced waters. The project's primary aim was to create an integrated, high-throughput, membrane-less, and modular microfluidic platform that could extract Lithium from unconventional sources. We have successfully met all goals and milestones envisioned in the SOPO document. The most critical primary milestones, including the Go-No-Go milestone (refer to the Gantt chart in the Appendices), were successfully accomplished. We demonstrated phase separation (>90%) and extraction (>85%) performance in the MPSE using synthetic, and representative produced water composition feed at 50 ml/min total flow through MPSE 36. We have also performed a parametric study of the MPSE operations, beyond the scope of SOPO, exploring operating conditions of current and broader interest. The extended investigation of operational parameters is concurrent with our efforts to seek further development of the MPSE technology beyond the scope of the Project. Along these lines of development, we have made efforts to be responsive to DOE calls for technological developments of other types of resources (beyond PW) for the recovery of Critical Materials and higher TRL development (beyond TRL 4). During the work on this Project, we developed and implemented three innovative technical approaches that emerged from our efforts to successfully meet the Project milestones. The innovative & original technical approaches developed and implemented in this Project are now the contributions to process engineering that could be clearly credited to the Project. First, Convergent Design Approach is a comprehensive feedforward & feedback loop of four design phases: i) design for functionality, ii) design for manufacturing, iii) design for sustainability, and iv) design for market. Next was Process Intensification. A major aim of this Project was to create an innovative phase separation & extraction microscale-based technology for Li separation – thus the words microchannel-based in the Project title. A microscale-based technology is intrinsically in the center of the Process Intensification domain as defined by its unique principles. Therefore, Process Intensification was implicitly envisioned in the Project’s SOPO. Lastly, Time Scale Analysis is a novel tool for discovering the needs and directions of Process Intensification implementations in any process technology. This Project is fully credited for developing and implementing the three novel technical approaches mentioned above. These are general contributions to process engineering that emerged from this Project. Beyond the original SOPO scope, the OSU-U.Pitt research group utilized a Convergent Design methodology, integrating first-principles mathematical modeling with experimental validation on the Minimum Development Vehicle. By creating these Digital Twins, the team rapidly assessed manufacturing iterations to support TEA analysis. This framework further enabled the development of advanced Surface Modification Techniques, where hydrophobic and oleophobic coating strategies were optimized via Digital Twin tools and validated through rigorous 100-hour longevity testing. TEA Analysis: The closing efforts of this Project were focused on the TEA analysis. TEA analysis had two primary functions: i) enabling critical assessments of design variations withing 10 the Concurrent Design Approach, thus enabling evolution of the MPSE design to reach faster- better-cheaper alternatives; and ii) to create a bridge between the accomplishments of this Project and future projects of higher TRL, beyond TRL 6 level. It is important to note that the TEA model created in the Project stirred the technological solutions for the recovery of critical materials toward a vision of a very profitable modular plant that has unique zero-waste water discharge signature. More importantly, thanks to our experimental performance data and conservative assumptions, the TEA model predicts minimal technological and investment risks. Low cost of a modular unit of a nominal capacity of [1000 tons of Li 2 CO 3 /year] positions the MPSE based technology within the reach of community investors, thus offering a paradigm shift in the development of critical technologies. The project successfully navigated two primary challenges: solvent selection and manufacturing adaptation. Restricted by the SOPO to existing literature for lithium recovery, the team identified a critical need for a "material excellence program" to develop next-generation solvents, eventually concluding with a preliminary investigation into promising Ionic Liquids (ILs). Simultaneously, COVID-19 supply chain disruptions forced a pivot from traditional manufacturing to advanced additive methods at ATAMI-OSU. By transitioning from stainless steel to 3D-printed polymer substrates, the team achieved a transformative three-order-of- magnitude reduction in manufacturing costs and compressed prototyping timelines from several months to just two days. The MPSE technology offers significant energy, environmental, and economic advantages by overcoming the traditional bottlenecks of phase-separation hardware and contactor size. Unlike conventional mixer-settlers or membrane-based systems, MPSE operates without moving parts or fouling-prone membranes, achieving robust performance even with challenging, viscous, or particulate-heavy feeds. Key performance metrics include an energy intensity reduction of 5–50x (3–40 kJ/m 3 ) compared to incumbent technologies and a dramatic reduction of processing time to under 60 seconds, which drastically reduces the physical plant footprint. These technical efficiencies translate into superior economic outcomes; for a 100 t/year Li 2 CO 3 facility, implementing MPSE is projected to nearly halve contactor CAPEX (from $\$$6.08M to $\$$3.01M) and significantly increase the project's Net Present Value (NPV), derisking new investment and enabling distributed critical-mineral processing configurations. The commercialization of MPSE technology is being spearheaded by Vigsur Dynamics Inc., which has adopted a structured, parallel approach to technical and business development since its formation in January 2026. Following extensive customer discovery and engagement with the Oregon State University accelerator, Vigsur Dynamics is working to establish a business model that transitions from pilot demonstrations to modular hardware sales, ultimately aiming for a "build-own-operate" service strategy. Current technical milestones—including 100 hours of continuous operation, superior energy efficiency, and successful 6-unit modular scale-up— provide a foundation for this transition. Backed by ongoing IP licensing and a growing network of industrial and venture advisors, the company is actively de-risking the platform to replace conventional mixer-settler systems in the critical minerals market.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

Preliminary Neutronics Design Studies for a Molten Salt Blanket LIFE Engine

The Laser Inertial Confinement Fusion Fission Energy (LIFE) Program being developed at Lawrence Livermore National Laboratory (LLNL) aims to design a hybrid fission-fusion subcritical nuclear engine that uses a laser-driven Inertial Confinement Fusion (ICF) system to drive a subcritical fission blanket. This combined fusion-fission hybrid system could be used for generating electricity, material transmutation or incineration, or other applications. LIFE does not require enriched fuel since it is a sub-critical system and LIFE can sustain power operation beyond the burnup levels at which typical fission reactors need to be refueled. In light of these factors, numerous options have been suggested and are being investigated. Options being investigated include fueling LIFE engines with spent nuclear fuel to aid in disposal/incineration of commercial spent nuclear fuel or using depleted uranium or thorium fueled options to enhance proliferation resistance and utilize non-fissile materials [1]. LIFE engine blanket designs using a molten salt fuel system represent one area of investigation. Possible applications of a LIFE engine with a molten salt blanket include uses as a spent nuclear fuel burner, fissile fuel breeding platform, and providing a backup alternative to other LIFE engine blanket designs using TRISO fuel particles in case the TRISO particles are found to be unable to withstand the irradiation they will be subjected to. These molten salts consist of a mixture of LiF with UF{sub 4} or ThF{sub 4} or some combination thereof. Future systems could look at using PuF{sub 3} or PuF{sub 4} as well, though no work on such system with initial plutonium loadings has been performed for studies documented in this report. The purpose of this report is to document preliminary neutronics design studies performed to support the development of a molten salt blanket LIFE engine option, as part of the LIFE Program being performed at Lawrence Livermore National laboratory. Preliminary design studies looking at fast ignition and hot spot ignition fusion options are documented, along with limited scoping studies performed to investigate other options of interest that surfaced during the main design effort. Lastly, side studies that were not part of the main design effort but may alter future work performed on LIFE engine designs are shown. The majority of all work reported in this document was performed during the Molten Salt Fast Ignition Moderator Study (MSFIMS) which sought to optimize the amount of moderator mixed into the molten salt region in order to produce the most compelling design. The studies in this report are of a limited scope and are intended to provide a preliminary neutronics analysis of the design concepts described herein to help guide decision processes and explore various options that a LIFE engine with a molten salt blanket might enable. None of the designs shown in this report, even reference cases selected for detailed description and analysis, have been fully optimized. The analyses were performed primarily as a neutronics study, though some consultation was made regarding thermal-hydraulic and structural concerns during both scoping out an initial model and subsequent to identifying a neutronics-based reference case to ensure that the design work contained no glaring mechanical or thermal issues that would preclude its feasibility. Any analyses and recommendations made in this report are either primarily or solely from the point of view of LIFE neutronics and ignore other fundamental issues related to molten salt fuel blankets such as chemical processing feasibility and political feasibility of a molten salt system.

42 ENGINEERING↗

Fiscal Year 2007 Phased Construction Completion Report for the Zone 2 Soils, Slabs, and Subsurface Structures at East Tennessee Technology Park, Oak Ridge, Tennessee

The purpose of this Phased Construction Completion Report (PCCR) is to present the fiscal year (FY) 2007 results of characterization activities and recommended remedial actions (RAs) for 11 exposure units (EUs) in Zone 2 (Z2-01, Z2-03, Z2-08, Z2-23, Z2-24, Z2-28, Z2-34, Z2-37, Z2-41, Z2-43, and Z2-44) at the East Tennessee Technology Park (ETTP), which is located in the northwest corner of the U.S. Department of Energy (DOE) Oak Ridge Reservation in Oak Ridge, Tennessee (Fig. 1). ETTP encompasses a total land area of approximately 5000 acres that has been subdivided into three zones--Zone 1 ({approx}1400 acres), Zone 2 ({approx}800 acres), and the Boundary Area ({approx}2800 acres). Zone 2, which encompasses the highly industrialized portion of ETTP shown in Fig. 1, consists of all formerly secured areas of the facility, including the large processing buildings and direct support facilities; experimental laboratories and chemical and materials handling facilities; materials storage and waste disposal facilities; secure document records libraries; and shipping and receiving warehouses. The Zone 2 Record of Decision for Soil, Buried Waste, and Subsurface Structure Actions in Zone 2, East Tennessee Technology Park, Oak Ridge, Tennessee (DOE 2005) (Zone 2 ROD) specifies the future end use for Zone 2 acreage as uncontrolled industrial for the upper 10 ft of soils. Characterization activities in these areas were conducted in compliance with the Zone 2 ROD and the Dynamic Verification Strategy (DVS) and data quality objectives (DQOs) presented in the Remedial Design Report/Remedial Action Work Plan for Zone 2 Soils, Slabs, and Subsurface Structures, East Tennessee Technology Park, Oak Ridge, Tennessee (DOE 2007) (Zone 2 RDR/RAWP). The purpose of this PCCR is to address the following: (1) Document DVS characterization results for the accessible EUs in FY 2007; (2) Describe and document the risk evaluation for each EU, and determine if the EU met the Zone 2 ROD requirements for unrestricted industrial use to 10 ft bgs; (3) Identify additional areas not defined in the Zone 2 ROD that require remediation based on the DVS evaluation results; and (4) Describe the RAs performed in Zone 2. The Zone 2 ROD divided the Zone 2 area into 7 geographic areas and 44 EUs. To facilitate the DQOs of the DVS process, the Zone 2 RDR/RAWP regrouped the 44 EUs into 12 DQO scoping EU groups. These groups facilitated the DQO process by placing similar facilities and their support facilities together and allowed identification of data gaps. The EU groups were no longer pertinent after DQO planning was completed, and characterization was conducted as areas became accessible. As the opportunity to complete characterization became available, the planned DVS program was executed and completed in FY 2007 for the 11 EUs addressed in this document. The main body of this report describes both the DVS process and scope of work performed and the RAs completed. The scope and approach for performing DVS activities performed in FY 2007 that lead to action/no further action decisions are presented in Sects. 2 through 4. RAs performed in FY 2007 are presented in Sects. 5 through 10. Future land use is described in Sect. 11, and the status of all Zone 2 EUs as of this PCCR is presented in Sect. 12.

54 ENVIRONMENTAL SCIENCES↗

Executive summary of major NuMI lessons learned: a review of relevant meetings of Fermilab's DUSEL Beamline Working Group

We have gained tremendous experience with the NuMI Project on what was a new level of neutrino beams from a high power proton source. We expect to build on that experience for any new long baseline neutrino beam. In particular, we have learned about some things which have worked well and/or where the experience is fairly directly applicable to the next project (e.g., similar civil construction issues including: tunneling, service buildings, outfitting, and potential claims/legal issues). Some things might be done very differently (e.g., decay pipe, windows, target, beam dump, and precision of power supply control/monitoring). The NuMI experience does lead to identification of critical items for any future such project, and what issues it will be important to address. The DUSEL Beamline Working Group established at Fermilab has been meeting weekly to collect and discuss information from that NuMI experience. This document attempts to assemble much of that information in one place. In this Executive Summary, we group relevant discussion of some of the major issues and lessons learned under seven categories: (1) Differences Between the NuMI Project and Any Next Project; (2) The Process of Starting Up the Project; (3) Decision and Review Processes; (4) ES&H: Environment, Safety, and Health; (5) Local Community Buy-In; (6) Transition from Project Status to Operation; and (7) Some Lessons on Technical Elements. We concentrate here on internal project management issues, including technical areas that require special attention. We cannot ignore, however, two major external management problems that plagued the NuMI project. The first problem was the top-down imposition of an unrealistic combination of scope, cost, and schedule. This situation was partially corrected by a rebaselining. However, the full, desirable scope was never achievable. The second problem was a crippling shortage of resources. Critical early design work could not be done in a timely fashion, leading to schedule delays, inefficiencies, and corrective actions. The Working Group discussions emphasized that early planning and up-front appreciation of the problems ahead are very important for minimizing the cost and for the greatest success of any such project. Perhaps part of the project approval process should re-enforce this need. The cost of all this up-front work is now reflected in the DOE cost of any project we do. If we are being held to an upper limit on the project cost, the only thing available for compromise is the eventual project scope.

43 PARTICLE ACCELERATORS↗

FY-09 Summary Report to the Office of Petroleum Reserves on the Western Energy Corridor Initiative Activities and Accomplishments

To meet its programmatic obligations under the Energy Policy Act of 2005, the Office of Naval Petroleum and Shale Oil Reserves (NPSOR) has initiated the Western Energy Corridor Initiative (WECI). The WECI will implement the Unconventional Strategic Fuels Task Force recommendations for accelerating and promoting the development of domestic unconventional fuels to help meet the nations’ energy needs. The mission of the WECI is to bolster America’s future fuel security by facilitating socially and environmentally responsible development of unconventional fuels resources in the Western Energy Corridor, using sound engineering principles and science-based methods to define and assess benefits, impacts, uncertainties, and mitigation options and to resolve impediments. The Task Force proposed a three-year program in its commercialization plan. The work described herein represents work performed by Idaho National Laboratory (INL) in support of the DOE’s WECI. This effort represents an interim phase of work, designed to initiate only select portions of the initiative, limited by available funding resources within NPOSR. Specifically, the work presented here addresses what was accomplished in FY-09 with the remaining carryover (~$420K) from NPOSR FY-08 funds. It was the intent of the NPOSR program to seek additional funding for full implementation of the full scope of work; however, the original tasks were reduced in scope, terminated, or eliminated (as noted below). An effort is ongoing to obtain funding to continue the tasks initiated under this project. This study will focus on the integrated development of multiple energy resources in a carbon-neutral and environmentally acceptable manner. Emphasis will be placed on analyses of the interrelationships of various energy-resource development plans and the infrastructure, employment, training, fiscal, and economic demands placed on the region as a result of various development scenarios. The interactions at build-out during the design, permitting, and construction of individual and multiple energy developments are not fully considered at the local, state, regional, or national levels. The net impacts to the Western Energy Corridor cannot be understood and the design optimized under the current approach. A regional development plan is needed to model cumulative impacts, determine the carrying capacity of the basin, and provide valuable technically based information to both skeptics and advocates. The INL scope of work for FY-09 involved six tasks: 1. Evaluation of the ASPEN Code as a dynamic systems model for application and use under the WECI and communications with Alberta Oil Sands Research Institutions as an “analog” resource development in the Western Energy Corridor 2. Application of the Aspen Plus computer model to several oil shale processes to consider energy balances and inputs and outputs (e.g. water consumption, CO2 production, etc.) 3. Development of a regulatory roadmap for oil shale developments 4. Defining of the physiographic extent of the natural resource reserves that comprise the Western Energy Corridor 5. A review of the Unconventional Fuels Task Force Report to Congress for ideas, concepts and recommendations that crosscutting plans 6. Program development with stakeholders, including industry, academics, state and federal agencies, and non government organizations. This task also includes project management, strategic development and reporting.

04 OIL SHALES AND TAR SANDS↗

Adagio 4.14 user s guide.

This document is a user's guide for the code Adagio. Adagio is a three-dimensional, implicit solid mechanics code with a versatile element library, nonlinear material models, and capabilities for modeling large deformation and contact. Adagio is a parallel code, and its nonlinear solver and contact capabilities enable scalable solutions of large problems. It is built on the SIERRA Framework [1, 2]. SIERRA provides a data management framework in a parallel computing environment that allows the addition of capabilities in a modular fashion. The Adagio 4.14 User's Guide provides information about the functionality in Adagio and the command structure required to access this functionality in a user input file. This document is divided into chapters based primarily on functionality. For example, the command structure related to the use of various element types is grouped in one chapter; descriptions of material models are grouped in another chapter. The input and usage of Adagio is similar to that of the code Presto [3]. Presto, like Adagio, is a solid mechanics code built on the SIERRA Framework. The primary difference between the two codes is that Presto uses explicit time integration for transient dynamics analysis, whereas Adagio is an implicit code. Because of the similarities in input and usage between Adagio and Presto, the user's guides for the two codes are structured in the same manner and share common material. (Once you have mastered the input structure for one code, it will be easy to master the syntax structure for the other code.) To maintain the commonality between the two user's guides, we have used a variety of techniques. For example, references to Presto may be found in the Adagio user's guide and vice versa, and the chapter order across the two guides is the same. On the other hand, each of the two user's guides is expressly tailored to the features of the specific code and documents the particular functionality for that code. For example, though both Presto and Adagio have contact functionality, the content of the chapter on contact in the two guides differs. Important references for both Adagio and Presto are given in the references section at the end of this chapter. Adagio was preceded by the codes JAC and JAS3D; JAC is described in Reference 4; JAS3D is described in Reference 5. Presto was preceded by the code Pronto3D. Pronto3D is described in References 6 and 7. Some of the fundamental nonlinear technology used by both Presto and Adagio are described in References 8, 9, and 10. Currently, both Presto and Adagio use the Exodus II database and the XDMF database; Exodus II is more commonly used than XDMF. (Other options may be added in the future.) The Exodus II database format is described in Reference 11, and the XDMF database format is described in Reference 12. Important information about contact is provided in the reference document for ACME [13]. ACME is a third-party library for contact. One of the key concepts for the command structure in the input file is a concept referred to as scope. A detailed explanation of scope is provided in Section 1.2. Most of the command lines in Chapter 2 are related to a certain scope rather than to some particular functionality.

97 MATHEMATICS AND COMPUTING↗

Presto 4.14 user s guide.

Presto is a three-dimensional transient dynamics code with a versatile element library, nonlinear material models, large deformation capabilities, and contact. It is built on the SIERRA Framework [1, 2]. SIERRA provides a data management framework in a parallel computing environment that allows the addition of capabilities in a modular fashion. Contact capabilities are parallel and scalable. The Presto 4.14 User's Guide provides information about the functionality in Presto and the command structure required to access this functionality in a user input file. This document is divided into chapters based primarily on functionality. For example, the command structure related to the use of various element types is grouped in one chapter; descriptions of material models are grouped in another chapter. The input and usage of Presto is similar to that of the code Adagio [3]. Adagio is a three-dimensional quasi-static code with a versatile element library, nonlinear material models, large deformation capabilities, and contact. Adagio, like Presto, is built on the SIERRA Framework [1]. Contact capabilities for Adagio are also parallel and scalable. A significant feature of Adagio is that it offers a multilevel, nonlinear iterative solver. Because of the similarities in input and usage between Presto and Adagio, the user's guides for the two codes are structured in the same manner and share common material. (Once you have mastered the input structure for one code, it will be easy to master the syntax structure for the other code.) To maintain the commonality between the two user's guides, we have used a variety of techniques. For example, references to Adagio may be found in the Presto user's guide and vice versa, and the chapter order across the two guides is the same. On the other hand, each of the two user's guides is expressly tailored to the features of the specific code and documents the particular functionality for that code. For example, though both Presto and Adagio have contact functionality, the content of the chapter on contact in the two guides differs. Important references for both Adagio and Presto are given in the references section at the end of this chapter. Adagio was preceded by the codes JAC and JAS3D; JAC is described in Reference 4; JAS3D is described in Reference 5. Presto was preceded by the code Pronto3D. Pronto3D is described in References 6 and 7. Some of the fundamental nonlinear technology used by both Presto and Adagio are described in References 8, 9, and 10. Currently, both Presto and Adagio use the Exodus II database and the XDMF database; Exodus II is more commonly used than XDMF. (Other options may be added in the future.) The Exodus II database format is described in Reference 11, and the XDMF database format is described in Reference 12. Important information about contact is provided in the reference document for ACME [13]. ACME is a third-party library for contact. One of the key concepts for the command structure in the input file is a concept referred to as scope. A detailed explanation of scope is provided in Section 1.2. Most of the command lines in Chapter 2 are related to a certain scope rather than to some particular functionality.

97 MATHEMATICS AND COMPUTING↗

Presto 4.16 user s guide.

Presto is a three-dimensional transient dynamics code with a versatile element library, nonlinear material models, large deformation capabilities, and contact. It is built on the SIERRA Framework [1, 2]. SIERRA provides a data management framework in a parallel computing environment that allows the addition of capabilities in a modular fashion. Contact capabilities are parallel and scalable. The Presto 4.16 User's Guide provides information about the functionality in Presto and the command structure required to access this functionality in a user input file. This document is divided into chapters based primarily on functionality. For example, the command structure related to the use of various element types is grouped in one chapter; descriptions of material models are grouped in another chapter. The input and usage of Presto is similar to that of the code Adagio [3]. Adagio is a three-dimensional quasi-static code with a versatile element library, nonlinear material models, large deformation capabilities, and contact. Adagio, like Presto, is built on the SIERRA Framework [1]. Contact capabilities for Adagio are also parallel and scalable. A significant feature of Adagio is that it offers a multilevel, nonlinear iterative solver. Because of the similarities in input and usage between Presto and Adagio, the user's guides for the two codes are structured in the same manner and share common material. (Once you have mastered the input structure for one code, it will be easy to master the syntax structure for the other code.) To maintain the commonality between the two user's guides, we have used a variety of techniques. For example, references to Adagio may be found in the Presto user's guide and vice versa, and the chapter order across the two guides is the same. On the other hand, each of the two user's guides is expressly tailored to the features of the specific code and documents the particular functionality for that code. For example, though both Presto and Adagio have contact functionality, the content of the chapter on contact in the two guides differs. Important references for both Adagio and Presto are given in the references section at the end of this chapter. Adagio was preceded by the codes JAC and JAS3D; JAC is described in Reference 4; JAS3D is described in Reference 5. Presto was preceded by the code Pronto3D. Pronto3D is described in References 6 and 7. Some of the fundamental nonlinear technology used by both Presto and Adagio are described in References 8, 9, and 10. Currently, both Presto and Adagio use the Exodus II database and the XDMF database; Exodus II is more commonly used than XDMF. (Other options may be added in the future.) The Exodus II database format is described in Reference 11, and the XDMF database format is described in Reference 12. Important information about contact is provided in the reference document for ACME [13]. ACME is a third-party library for contact. One of the key concepts for the command structure in the input file is a concept referred to as scope. A detailed explanation of scope is provided in Section 1.2. Most of the command lines in Chapter 2 are related to a certain scope rather than to some particular functionality.

97 MATHEMATICS AND COMPUTING↗

Adagio 4.16 user s guide.

Adagio is a three-dimensional, implicit solid mechanics code with a versatile element library, nonlinear material models, and capabilities for modeling large deformation and contact. Adagio is a parallel code, and its nonlinear solver and contact capabilities enable scalable solutions of large problems. It is built on the SIERRA Framework [1, 2]. SIERRA provides a data management framework in a parallel computing environment that allows the addition of capabilities in a modular fashion. The Adagio 4.16 User's Guide provides information about the functionality in Adagio and the command structure required to access this functionality in a user input file. This document is divided into chapters based primarily on functionality. For example, the command structure related to the use of various element types is grouped in one chapter; descriptions of material models are grouped in another chapter. The input and usage of Adagio is similar to that of the code Presto [3]. Presto, like Adagio, is a solid mechanics code built on the SIERRA Framework. The primary difference between the two codes is that Presto uses explicit time integration for transient dynamics analysis, whereas Adagio is an implicit code. Because of the similarities in input and usage between Adagio and Presto, the user's guides for the two codes are structured in the same manner and share common material. (Once you have mastered the input structure for one code, it will be easy to master the syntax structure for the other code.) To maintain the commonality between the two user's guides, we have used a variety of techniques. For example, references to Presto may be found in the Adagio user's guide and vice versa, and the chapter order across the two guides is the same. On the other hand, each of the two user's guides is expressly tailored to the features of the specific code and documents the particular functionality for that code. For example, though both Presto and Adagio have contact functionality, the content of the chapter on contact in the two guides differs. Important references for both Adagio and Presto are given in the references section at the end of this chapter. Adagio was preceded by the codes JAC and JAS3D; JAC is described in Reference 4; JAS3D is described in Reference 5. Presto was preceded by the code Pronto3D. Pronto3D is described in References 6 and 7. Some of the fundamental nonlinear technology used by both Presto and Adagio are described in References 8, 9, and 10. Currently, both Presto and Adagio use the Exodus II database and the XDMF database; Exodus II is more commonly used than XDMF. (Other options may be added in the future.) The Exodus II database format is described in Reference 11, and the XDMF database format is described in Reference 12. Important information about contact is provided in the reference document for ACME [13]. ACME is a third-party library for contact. One of the key concepts for the command structure in the input file is a concept referred to as scope. A detailed explanation of scope is provided in Section 1.2. Most of the command lines in Chapter 2 are related to a certain scope rather than to some particular functionality.

97 MATHEMATICS AND COMPUTING↗

DMTN-107: Options for Alert Production in LSST Operations Year 1

This document reviews five options for alert production in LSST Operations Year 1 (LOY1), taking into account any implications on LSST formal requirements including up-scopes, down-scopes or explicit violations. The Data Management System Science Team's preferred option for maximizing LSST science is to generate template images from as much of the data from the commissioning and/or science verification phases as possible and use them to run Difference Image Analysis and alert production during LOY1. A proposal to increase the sky area covered during commissioning via a "filler" scheduler program is also presented. As a potential moderate up-scope, this study presents an option to build interim templates on a $\sim$monthly basis during LOY1, which could increase the accessible sky area by ~1000-2000 deg**2 per month, and should be reconsidered closer to the start of Operations.

79 ASTRONOMY AND ASTROPHYSICS↗

An emulator for minimizing finite element analysis implementation resources

A finite element analysis emulator providing a basis for efficiently establishing an optimum computer implementation strategy when many calculations are involved is described. The SCOPE emulator determines computer resources required as a function of the structural model, structural load-deflection equation characteristics, the storage allocation plan, and computer hardware capabilities. Thereby, it provides data for trading analysis implementation options to arrive at a best strategy. The models contained in SCOPE lead to micro-operation computer counts of each finite element operation as well as overall computer resource cost estimates. Application of SCOPE to the Memphis-Arkansas bridge analysis provides measures of the accuracy of resource assessments. Data indicate that predictions are within 17.3 percent for calculation times and within 3.2 percent for peripheral storage resources for the ELAS code.

Melosh, R. J.↗

Lunar landing and launch facilities and operations

A preliminary definition of a lunar landing and launch facility (LLLF or Complex 391) has been formulated. A Phase 3 lunar base is considered. Without specifying specific lunar base scenarios, three traffic levels are envisioned: 6, 12, and 24 landings/launches per year. A single, multipurpose vehicle for the lunar module is assumed. The design and specification of the vehicle and of the lunar base are outside the scope of this study. However, these two items will impact those items considered within the scope of this study because of interactions at the system boundaries. The scope of this study is graphically portrayed with the systems diagram. Based upon this diagram, nine major design items or areas are considered. These items are: (1) landing/launch site considerations; (2) structure, shelter, safety, and environmental needs; (3) landing/launch guidance, communications, and computing needs; (4) lunar module surface transport system; (5) heavy cargo unloading/loading systems; (6) personnel unloading/loading systems; (7) propellant unloading/loading systems; (8) vehicle storage; and (9) maintenance, repair, test and check-out requirements. Initially, a general, conceptual description of each of these items is given. Then, preliminary sizes, capacities, and other relevant design data for some of these items are identified. The Earth-Moon transportation infrastructure and the baseline lunar module design are summarized.

Source record↗

Dynamic Constraint Satisfaction with Reasonable Global Constraints

Previously studied theoretical frameworks for dynamic constraint satisfaction problems (DCSPs) employ a small set of primitive operators to modify a problem instance. They do not address the desire to model problems using sophisticated global constraints, and do not address efficiency questions related to incremental constraint enforcement. In this paper, we extend a DCSP framework to incorporate global constraints with flexible scope. A simple approach to incremental propagation after scope modification can be inefficient under some circumstances. We characterize the cases when this inefficiency can occur, and discuss two ways to alleviate this problem: adding rejection variables to the scope of flexible constraints, and adding new features to constraints that permit increased control over incremental propagation.

Frank, Jeremy↗

New Direction of NASA Exploration Life Support

NASA's activities in life support Research and Technology Development (R&TD) have changed in both focus and scope following implementation of recommendations from the Exploration System Architecture Study (ESAS). The limited resources available and the compressed schedule to conduct life support R&TD have required that future efforts address the needs of the Crew Exploration Vehicle (CEV), the Lunar Surface Access Module (LSAM) and Lunar Outpost (LO). Advanced Life Support (ALS) efforts related to long duration planetary bases have been deferred or canceled. This paper describes the scope of the new Exploration Life Support (ELS) project; how it differs from ALS, and how it supports critical needs for the CEV, LSAM and LO. In addition, this paper provides rationale for changes in the scope and focus of technical content within ongoing life support R&TD activities.

Chambliss, Joe↗

Modelling the Future Hydroclimatology of the Lower Fraser River and its Impacts on the Spawning Migration Survival of Sockeye Salmon

Short episodic high temperature events can be lethal for migrating adult Pacific salmon (Oncorhynchus spp.). We downscaled temperatures for the Fraser River, British Columbia to evaluate the impact of climate warming on the frequency of exceeding thermal thresholds associated with salmon migratory success. Alarmingly, a modest 1.0 C increase in average summer water temperature over 100 years (1981-2000 to 2081-2100) tripled the number of days per year exceeding critical salmonid thermal thresholds (i.e. 19.0 C). Refined thresholds for two populations (Gates Creek and Weaver Creek) of sockeye salmon (Oncorhynchus nerka) were defined using physiological constraint models based on aerobic scope. While extreme temperatures leading to complete aerobic collapse remained unlikely under our warming scenario, both populations were increasingly forced to migrate upriver at reduced levels of aerobic performance (e.g. in 80% of future simulations, => 90% of salmon encountered temperatures exceeding population specific thermal optima for maximum aerobic scope; T(sub opt)) = 16.3 C for Gates Creek and T(sub sopt)=14.5 C for Weaver Creek). Assuming recent changes to river entry timing persist, we also predicted dramatic increases in the probability of freshwater mortality for Weaver Creek salmon due to reductions in aerobic, and general physiological, performance (e.g. in 42% of future simulations =>50% of Weaver Creek fish exceeded temperature thresholds associated with 0 - 60% of maximum aerobic scope). Potential for adaptation via directional selection on run-timing was more evident for the Weaver Creek population. Early entry Weaver Creek fish experienced 25% (range: 15 - 31%) more suboptimal temperatures than late entrants, compared with an 8% difference (range: 0 - 17%) between early and late Gates Creek fish. Our results emphasize the need to consider daily temperature variability in association with population-specific differences in behaviour and physiological constraints when forecasting impacts of climate change on migratory survival of aquatic species.

Hague, M. J.↗

Multi Modality Brain Mapping System (MBMS) Using Artificial Intelligence and Pattern Recognition

A Multimodality Brain Mapping System (MBMS), comprising one or more scopes (e.g., microscopes or endoscopes) coupled to one or more processors, wherein the one or more processors obtain training data from one or more first images and/or first data, wherein one or more abnormal regions and one or more normal regions are identified; receive a second image captured by one or more of the scopes at a later time than the one or more first images and/or first data and/or captured using a different imaging technique; and generate, using machine learning trained using the training data, one or more viewable indicators identifying one or abnormalities in the second image, wherein the one or more viewable indicators are generated in real time as the second image is formed. One or more of the scopes display the one or more viewable indicators on the second image.

Kateb, Babak↗