Alkyl chain engineering of chlorinated acceptors for elevated solar conversion
Abstract not provided
SEARCH · Search NASA
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.
Abstract not provided
Conference paper for the ASME 2022 Turbomachinery Technical Conference & ExpositionJune 13-17, 2022, Rotterdam, The Netherlands<br>
Abstract not provided.
Abstract not provided.
Abstract not provided.
Alnico is a rare-earth free; permanent magnet (PM) which maintains its saturation magnetization while at temperatures up to 550°C but lacks the coercivity and energy product needed for a wide range of demanding applications. With an optimal set of processing and manufacturing techniques, Alnico could replace Dy-free Nd-Fe-B magnets in certain applications if the microstructure is textured in a $\langle$001$\rangle$ direction. Additive manufacturing (AM) of near-net-shape magnets may provide such texture. To investigate the possibility, directed-energy deposition (DED) in conjunction with an actively cooled substrate was used to build samples with a compositionally modified, gas-atomized, Alnico 8 alloy. The resulting samples were solutionized and quenched, followed by magnetic annealing and a heat treatment. Magnetic properties and microstructures are compared to previous work.
Explore the source record for details and available documents.
Paper submitted to 2023 AIAA SciTech Forum. This paper discusses the occurrence of stable, but unsteady (periodic) variations in detonation wave spacing in a Rotating Detonation Combustor.
Explore the source record for details and available documents.
Fractures in subsurface shale formations serve multiple purposes, for example, in the recovery of resources in hydraulic fracturing or as potential harmful leakage passages through caprocks that may contribute undesired fluids to the atmosphere or functional groundwater aquifers. A proposed method to seal or influence fracture properties is Ureolysis-Induced Calcium Carbonate Precipitation (UICP), a bio-mineralization technology driven by the enzymatic hydrolysis of urea, resulting in the formation of calcium carbonate. The resulting calcium carbonate can bridge the gaps in fractured shale and reduce fluid flow through fractures. This study represents the first step toward determining the influence of UICP treatment on shale material and its subsequent mechanical strength properties. The goal of this preliminary work is twofold: first, we aim to identify a method to test tensile strength along a core axis and second, we seek to assess the effect of temperature on the tensile strength of intact, unfractured shale cores (2.54 cm (1 in) diameter, 5.08 cm (2 in) long for comparison with future fractured and UICP-treated cores. A modified Brazilian indirect tensile strength test successfully measured splitting tensile strength of shale cores from Eagle Ford and Wolfcamp formations at room temperature and 60°C.
Explore the source record for details and available documents.
Abstract not provided.
This Implementation Guide describes the principles of Cyber-Informed Engineering (CIE) and outlines questions that engineering teams should consider during each phase of a system’s lifecycle to effectively employ these principles. It describes what it means to engineer systems in a cyber-informed way, rather than offering a comprehensive, step-by-step process or procedure for CIE implementation. This guide complements—but does not replace—the application of cybersecurity standards or practices currently in place within an organization. Engineers and technicians that design critical energy infrastructure installations can use this Implementation Guide to integrate the 12 principles of CIE into each phase of the engineering lifecycle, from concept to retirement. The guide is aimed at system or design engineers, rather than software engineers or operational cybersecurity practitioners. The engineers who design, build, operate, and maintain the physical infrastructure are best positioned to leverage a system’s engineering design to diminish the severity of cyber attacks or digital technology failures. CIE expands cybersecurity decisions into the engineering space, not by asking engineers to become cyber experts, but by calling on engineers to apply engineering tools and make engineering decisions that improve cybersecurity outcomes. CIE examines the engineering consequences that a sophisticated cyber attacker could achieve and drives engineering changes that may provide deterministic mitigations to limit or eliminate those consequences.
This Implementation Guide describes the principles of Cyber-Informed Engineering (CIE) and outlines questions that engineering teams should consider during each phase of a system's lifecycle to effectively employ these principles. It describes what it means to engineer systems in a cyber-informed way, rather than offering a comprehensive, step-by-step process or procedure for CIE implementation. This guide complements - but does not replace - the application of cybersecurity standards or practices currently in place within an organization. Engineers and technicians that design critical energy infrastructure installations can use this Implementation Guide to integrate the 12 principles of CIE into each phase of the engineering lifecycle, from concept to retirement. The guide is aimed at system or design engineers, rather than software engineers or operational cybersecurity practitioners. The engineers who design, build, operate, and maintain the physical infrastructure are best positioned to leverage a system's engineering design to diminish the severity of cyber attacks or digital technology failures. CIE expands cybersecurity decisions into the engineering space, not by asking engineers to become cyber experts, but by calling on engineers to apply engineering tools and make engineering decisions that improve cybersecurity outcomes. CIE examines the engineering consequences that a sophisticated cyber attacker could achieve and drives engineering changes that may provide deterministic mitigations to limit or eliminate those consequences.
CIE is an emerging method to integrate cybersecurity considerations into the conception, design, development, and operation of any physical system that has digital connectivity, monitoring, or control. CIE complements—but does not replace—the application of cybersecurity standards or practices currently in place within an organization. Rather, it expands cybersecurity decisions into the engineering space, not by asking engineers to become cyber experts, but by calling on engineers to apply engineering tools and make engineering decisions that improve cybersecurity outcomes. CIE examines the engineering consequences that a sophisticated cyber attacker could achieve, and drives engineering changes that may provide deterministic mitigations to limit or eliminate those consequences. Engineers and technicians that design critical energy infrastructure installations can integrate the 12 principles of CIE into each phase of the engineering lifecycle, from concept to retirement. These principles are aimed at system or design engineers, operators, and technicians, rather than software engineers or operational cybersecurity practitioners, because the engineers who design, build, operate, and maintain the physical infrastructure are best positioned to leverage a system’s engineering design to diminish the severity of cyber attacks or digital technology failures. This approach creates new opportunities for engineering teams—and not just cybersecurity teams—to secure the system using the physics and mechanics of engineering controls—not just digital monitoring and controls.
This manual will attempt to motivate the use of an automated build system for the purposes of computational science and engineering. As part of this motivation, the surrounding computational practices of version control, documen tation, compute environment management, and regression testing will also be addressed as applied to the practice of computational engineering. Specifically, this manual intends to motivate the adoption of these traditional software engineering practices for use in research and production engineering simulation projects. This manual is not the first such effort in the greater scientific computing community. In fact, the authors relied heavily on the lesson plans of the Software Carpentry, established to teach computing skills to researchers in 1998. As the intention for this manual is to lay out fundamental practices of engineering computing, it will not attempt to fully teach the underlying concepts and will instead reference the well designed lesson plans of the Software Carpentry. Where possible, this manual will explain to general computing practices and concepts and limit discussion of specific software implementations to examples or vehicles for practice in concrete application. The specific software taught by the Software Carpentry curriculum is an excellent starting point to learn the core concepts of computational engi neering. However, the authors have found that applications to engineering simulation and analysis require translation of these software development concepts into the language and workflows of computational engineers. Adopting these computational tools may require engineers to re-imagine their workflows in some combination of traditional engineer ing and software concepts. It has also been necessary to extend existing software build systems for engineering practices beyond the simple wrap ping of engineering software execution. Where necessary, examples of specific software and their method of extension to engineering simulations will be given, with reference to the User Manual for recommended practical use. Where this manual relies on specific implementation examples, it should be understood that the practicing engineer may find that different software is more amenable to their specific work. It is always the overall collection of computational practices is more important than any specific software implementation. The ability to recognize which concepts are implemented by a software package will make a practicing engineer agile to changing project needs, computing resources, numeric solvers, programming languages, and even available funding.