Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “api”

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 163 records · Page 9

CMinx: A CMake Documentation Generator

This manuscript introduces CMinx, a program for generating application programming interface (API) documentation written in the CMake language, and CMake modules in particular. Since most of CMinx’s intended audience is comprised of C/C++ developers, CMinx is designed to operate similar to Doxygen, the de facto C/C++ API documentation tool. Specifically, developers annotate their CMake source with “documentation” comments, which are traditional CMake block comments starting with an extra “[” character. The documentation comments, written in reST, describe to the reader how the functions, parameters, and variables should be used. Running CMinx on the annotated source code generates reST files containing the API documentation. The reST files can then be converted into static websites with tools such as Sphinx or easily converted to another format via Pandoc.

97 MATHEMATICS AND COMPUTING↗

High Temperature Erosion Modeling in Particle Based CSP Systems

1. Introduction. Wear and erosion damage of materials from solid particle and surface interactions is a major issue in various industries. Although more common in mining and oil and gas production, erosion is becoming a critical issue in renewable technologies as well such as particle based concentrated solar thermal power (CSP) systems. In particle based CSP systems, solid particles are used to absorb solar energy and as thermal storage. However, these particles may cause significant amount of wear to system components while through the system at high temperatures. This damage can be costly, and therefore, requires a greater understanding of solid particle erosion in CSP systems. Throughout the years, models and tools have been developed to predict and control erosion in industries such as oil and gas production. However, these erosion models and erosion prediction tools have been mainly developed based on erosion data for much higher velocities and lower temperatures, i.e. the operating conditions for which the existing models have been built are not pertinent to those expected in CSP system. It is known that erosion depends on many factors such as material properties, erodent particle properties, and particle impact speed and angle. However, the effect of temperature on erosion is not vastly investigated. In this work, a temperature-based correlation is introduced that will be used to modify the existing erosion models to predict erosion rates at velocities and temperatures relevant to Gen3 CSP systems. The existing models are first validated against erosion experiments run at low temperatures and low velocities. Subsequently, a temperature correction term is developed that can extend the existing models to high temperatures, based on the available experimental data showing the effect of temperature on impact erosion. 2. Erosion Models. Continuing sequence of impacts from solid particles on surfaces would result in loss of material due to mechanical interaction between solid surface and particles. Erosion equations have been developed to predict erosion under different conditions and erosion mechanism, including cutting and deformation erosion. These models are mainly either mechanistic, empirical, and semi-mechanistic models, when the latter combine the theory of the erosion mechanism and particle motion with the available experimental data. One of the first empirical correlation was introduced by American Petroleum Institute (API) Recommended Practice (RP) 14E [1]. This correlation was very conservative, and several improved empirical and semi-mechanistic equations were developed in the years following. More recently, the models introduced by Erosion/Corrosion Research Center (E/CRC) at the University of Tulsa and Arabnejad. et al. [2] are frequently used in the literature and industry, as they account for many parameters affecting erosion including particle impact speed and angle, material density and hardness, and particle size and shape. However, both these models were developed based on data at relatively high velocities and also do not take into account any mechanical changes in material associated with thermal cycling at high temperatures. 3. Erosion Prediction at High Temperatures. In this work, the accuracy of Arabnejad et al. model and E/CRC model is investigated to predict impact erosion at conditions relevant to Gen3 CSP systems. Two significant deviations expected in Gen3 systems compared to operating conditions used to build these models are particle impact velocities and system temperature. As a first step, the performance of these models was validated at low velocities and temperatures. Impact erosion experiments were conducted on SS316 coupons using HSP 40/70 ceramic particles. Assuming particle rate of 1 kg/s/m, 0.0254 m of particle curtain thickness, and particle velocity of 1.5 m/s in the system, an overall erosion of 0.59 mm/year was calculated. The experimental results were subsequently compared to those from computational simulations and erosion of 0.47 mm/year was obtained using the Arabnejad et al. model. The results indicated that the models work well at low velocities and low temperature conditions. To account for temperature effect, a mathematical correlation was developed using data published by DUCOM [3] for Inconel 600 eroded by alumina particles at high velocities. The correlation was applied to both Arabnejad et. al model and the E/CRC model. The prediction results from these modified models were within 20% of this experimental data. Predictions of of erosion by the modified E/CRC model at three different temperatures are made. Similar to the calculation at low temperature, a typical CSP system with 1 kg/s/m of particle flow rate per unit length of the particle curtain and a curtain thickness of 0.0254 m is assumed. The annual thickness loss calculations were run for different particle impact velocities, assuming a uniform particle impact area equal to the cross-sectional area of the curtain (particle-particle interactions and dispersion of particles are not considered in obtaining the results). It is observed that erosion increases exponentially as temperature increases. Furthermore, it is also noted that, erosion changes non-linearly with impact velocity. Currently, experiments are also being conducted to measure erosion of SS316 at 800 ºC with HSP 40/70 particles at low impact velocities. We expect to use the results from high temperature testing to further improve the temperature correlation function. Similar models are also being developed for abrasion erosion resulting from particle sliding along the surfaces as well as attrition from particle to particle and particle to surface interactions. References. [1] Institute, A. P. (1991). API Recommended Practice for Design and Installation of Offshore Production Platform Piping System, API RP 14E. [2] Arabnejad, H., Mansouri, A., Shirazi, S. A., and McLaury, B. S. (2015a). Development of mechanistic erosion equation for solid particles. Wear, 332–333, 1044–1050. http://doi.org/10.1016/j.wear.2015.01.031. [3] https://ducom.com/high-temperature-erosion-evaluating-sample-wear/

14 SOLAR ENERGY↗

Model-Based Diagnostics and Mitigation of Cyber Threats

The report summarizes key tasks performed to develop a toolkit for detecting cyber-attack events in instrumentation and control (I&C) systems of nuclear power plants. The toolkit connects the state-of-the-art GPWR Simulator with the RELAP5 code providing best-estimate nuclear steam supply system (NSSS) analyses, via the application programming interface (API), and allows users to introduce potential cyber-attack scenarios into power plant operational simulation. This summary for the project reflects topical reports submitted during the project as well as a journal paper published in 2022. The focus areas of the summary include: (1) modeling I&C systems for the AP1000 Generation III+ nuclear plant and GPWR simulator, (2) simulation and monitoring of plant response to cyber-attack events, (3) API structure for the toolkit interfacing the GPWR simulator and RELAP5 code, and (4) restructuring of the three-loop NSSS software of GPWR to model the two-loop AP1000 structure. Discussed in some details are (a) the attack tree analysis assessing the susceptibility of the AP1000 I&C system, resulting in reactor trips, in terms of the attack possibility and component sensitivity and (b) realistic estimation of the time to steam generator trip due to cyber-intrusions in the GPWR Simulator. Finally, sample demonstrations of the cyber-security tool kit, in the form of the GPWR-RELAP5 API, are summarized.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

Gantryless Associated-Particle Neutron Radiography

The present work reports on the development of techniques for in-field fast-neutron radiography measurements using the associated-particle imaging (API) method. The API method employs alpha-neutron coincidences from the d+t→α+n reaction to enable fast neutron transmission imaging with excellent contrast using a wide cone beam. However, for field radiography applications, the API method is burdened by the need for the relative positions of the source and detector to be known. Fortunately, these relative positions can be inferred from transmission data. The inferred positions also enable accurate stitching of multiple images into a composite image even when using a low-resolution detector panel and acquiring images having few overlapping pixels. The developed techniques address analysis of measurements where (1) the source and detector panel are separately hand positioned rather than held in registration by a gantry, (2) multiple detector panel positions within the “coincident cone” of tagged neutrons are required to piece together an image of an item of interest, and (3) normalization measurements that have identical source-detector positioning but without the inspected object are not possible. The present work will describe the system calibrations (including timing calibrations and neutron direction calibrations) necessary for subsequent analyses, the method of locating the detector in the coincident cone of neutrons with millimeter precision using the timing and directions of coincident neutrons, the method of calculating a normalization image for a given detector panel position, and the method used to project multiple images into a common image.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

SIMD Programming for the SMASH Shock Physics Code

Many modern CPUs that are available to the NNSA as mission computing resources support vector instruction sets. Making good use of vector instructions, referred to as “vectorization”, is often critical to getting the best performance from these CPUs. While other codes choose to rely on compiler auto-vectorization, the SMASH shock physics code chooses to leverage APIs for explicit vectorization. These APIs are similar to directly calling the CPU vendor’s vector intrinsics, with the additional benefit of being vendor-agnostic. This document explains what the SIMD APIs are and how to use them in developing SMASH.

97 MATHEMATICS AND COMPUTING↗

Integrating DOE ASCR Computing into HEPCloud through GlideinWMS

Fermilab's HEPCloud facility expands the laboratory's computing capacity by provisioning resources beyond the local grid, using GlideinWMS to deliver pilots to where experiments such as CMS and DUNE run. The High-Performance Computing (HPC) facilities of the DOE Office of Advanced Scientific Computing Research (ASCR) are a growing part of that pool. HEPCloud currently provisions NERSC over SSH, but NERSC is moving away from that path as it adopts multi-factor authentication and directs automated access to its Superfacility API and the DOE Integrated Research Infrastructure (IRI) APIs. Maintaining and extending access across the ASCR ecosystem now requires provisioning through these interfaces. This work adds new pilot submission paths to GlideinWMS for the NERSC Superfacility API, IRI, and Globus Compute. Each uses the provisioning model GlideinWMS already applies to batch resources, so experiments can run on ASCR computing resources without changes to their existing workflows. This work finally presents a comparison of the paths to guide which interfaces are best suited for different workflows.

Majumder, Meghanto [U. Houston (main)]↗

Determination of nitrogen monoxide in high purity nitrogen gas with an atmospheric pressure ionization mass spectrometer

An atmospheric pressure ionization mass spectrometric (API-MS) method was studied for the determination of residual NO in high purity N2 gas. The API-MS is very sensitive to NO, but the presence of O2 interferes with the NO measurement. Nitrogen gas in cylinders as sample gas was mixed with NO standard gas and/or O2 standard gas, and then introduced into the API-MS. The calibration curves of NO and O2 has linearity in the region of 0 - 2 ppm, but the slopes changed with every cylinder. The effect of O2 on NO+ peak was additive and proportional to O2 concentration in the range of 0 - 0.5 ppm. The increase in NO+ intensity due to O2 was (0.07 - 0.13)%/O2, 1 ppm. Determination of NO and O2 was carried out by the standard addition method to eliminate the influence of variation of slopes. The interference due to O2 was estimated from the product of the O2 concentration and the ratio of slope A to Slope B. Slope A is the change in the NO+ intensity with the O2 concentration. Slope B is the intensity with O2 concentration.

Kato, K.↗

Soil moisture estimation using GOES-VISSR infrared data - A case study with a simple statistical method

Five days of clear sky observations of Kansas and Nebraska are used to examine the statistical relationship between soil moisture and infrared surface temperature observations taken from a geosynchronous satellite. Linear regression is used to relate soil moisture to surface temperature and other variables that represent wind speed, vegetation cover, and low-level temperature advection. Results show good agreement between estimated and observed soil moisture features on each of the 5 days. The average coefficient of determination for five pseudoindependent tests in which the test day is held out of the regression is 0.71. It is shown that a depletion coefficient of 0.92, when used to compute antecedent precipitation index (API), produces the best correlation between API and soil moisture as inferred from GOES thermal infrared data. By averaging daily predicted values over the 5-day rain-free case study period, 92 percent of the variance of the morning surface temperature change is explained by a simple multiple linear regression with all independent variables, or, alternatively, 85 percent of the observed variance in API is explained. It is concluded that this approach can distinguish at least four classes of soil wetness, but the necessity for measurement of surface advection may limit its usefulness in remote areas.

Wetzel, Peter J.↗

Estimating soil wetness using satellite data

Improved estimates of soil wetness were obtained using observations from both the NIMBUS-7 Scanning Multichannel Microwave Radiometer (SMMR) and the NOAA-7 Advanced Very High Resolution Radiometer (AVHRR). SMMR 66 GHz frequency, horizontal polarization, brightness temperature T(BH) was first correlated with soil wetness, as computed using an Antecedent Precipitation Index (API) model, for a number of SMMR ground resolution areas involving a fairly wide range of vegetation densities. The API generally accounted for more than 70 percent of the observed temporal variability in T(BH), with linear correlations being significant at the 1 percent level. The regression slope of T(BH) versus API correlated well, at the 1 percent level, with a vegetation index derived from AVHRR visible and near-infrared observations. The regression intercept was found to correlate less satisfactorily, but was significant at the 5 percent level. These linear regression results were used to develop a diagnostic model for soil wetness using SMMR and AVHRR data only.

Choudhury, Bhaskar J.↗

Subsetting and Formatting Landsat-7 LOR ETM+ and Data Products

The Landsat-7 Processing System (LPS) processes Landsat-7 Enhanced Thematic Mapper (ETM+) instrument data into large, contiguous segments called "subintervals" and stores them in Level OR (LOR) data files. The LPS processed subinterval products must be subsetted and reformatted before the Level I processing systems can ingest them. The initial full subintervals produced by the LPS are stored mainly in HDF Earth Observing System (HDF-EOS) format which is an extension to the Hierarchical Data Format (HDF). The final LOR products are stored in native HDF format. Primarily the EOS Core System (ECS) and alternately the DAAC Emergency System (DES) subset the subinterval data for the operational Landsat-7 data processing systems. The HDF and HDF-EOS application programming interfaces (APIs) can be used for extensive data subsetting and data reorganization. A stand-alone subsetter tool has been developed which is based on some of the DES code. This tool makes use of the HDF and HDFEOS APIs to perform Landsat-7 LOR product subsetting and demonstrates how HDF and HDFEOS can be used for creating various configurations of full LOR products. How these APIs can be used to efficiently subset, format, and organize Landsat-7 LOR data as demonstrated by the subsetter tool and the DES is discussed.

Reid, Michael R.↗

Shuttle-Data-Tape XML Translator

JSDTImport is a computer program for translating native Shuttle Data Tape (SDT) files from American Standard Code for Information Interchange (ASCII) format into databases in other formats. JSDTImport solves the problem of organizing the SDT content, affording flexibility to enable users to choose how to store the information in a database to better support client and server applications. JSDTImport can be dynamically configured by use of a simple Extensible Markup Language (XML) file. JSDTImport uses this XML file to define how each record and field will be parsed, its layout and definition, and how the resulting database will be structured. JSDTImport also includes a client application programming interface (API) layer that provides abstraction for the data-querying process. The API enables a user to specify the search criteria to apply in gathering all the data relevant to a query. The API can be used to organize the SDT content and translate into a native XML database. The XML format is structured into efficient sections, enabling excellent query performance by use of the XPath query language. Optionally, the content can be translated into a Structured Query Language (SQL) database for fast, reliable SQL queries on standard database server computers.

Barry, Matthew R.↗

Activity-Centric Approach to Distributed Programming

The first phase of an effort to develop a NASA version of the Cybele software system has been completed. To give meaning to even a highly abbreviated summary of the modifications to be embodied in the NASA version, it is necessary to present the following background information on Cybele: Cybele is a proprietary software infrastructure for use by programmers in developing agent-based application programs [complex application programs that contain autonomous, interacting components (agents)]. Cybele provides support for event handling from multiple sources, multithreading, concurrency control, migration, and load balancing. A Cybele agent follows a programming paradigm, called activity-centric programming, that enables an abstraction over system-level thread mechanisms. Activity centric programming relieves application programmers of the complex tasks of thread management, concurrency control, and event management. In order to provide such functionality, activity-centric programming demands support of other layers of software. This concludes the background information. In the first phase of the present development, a new architecture for Cybele was defined. In this architecture, Cybele follows a modular service-based approach to coupling of the programming and service layers of software architecture. In a service-based approach, the functionalities supported by activity-centric programming are apportioned, according to their characteristics, among several groups called services. A well-defined interface among all such services serves as a path that facilitates the maintenance and enhancement of such services without adverse effect on the whole software framework. The activity-centric application-program interface (API) is part of a kernel. The kernel API calls the services by use of their published interface. This approach makes it possible for any application code written exclusively under the API to be portable for any configuration of Cybele.

Levy, Renato↗

TraceContract: A Scala DSL for Trace Analysis

In this paper we describe TRACECONTRACT, an API for trace analysis, implemented in the SCALA programming language. We argue that for certain forms of trace analysis the best weapon is a high level programming language augmented with constructs for temporal reasoning. A trace is a sequence of events, which may for example be generated by a running program, instrumented appropriately to generate events. The API supports writing properties in a notation that combines an advanced form of data parameterized state machines with temporal logic. The implementation utilizes SCALA's support for defining internal Domain Specific Languages (DSLs). Furthermore SCALA's combination of object oriented and functional programming features, including partial functions and pattern matching, makes it an ideal host language for such an API.

log file analysis↗

The NASA Tournament Laboratory (NTL): Improving Data Access at PDS while Spreading Joy and Engaging Students through 16 Micro-Contests

NASA PDS hosts terabytes of valuable data from hundreds of data sources and spans decades of research. Data is stored on flat-file systems regulated through careful meta dictionaries. PDS's data is available to the public through its website which supports data searches through drill-down navigation. While the system returns data quickly, result sets in response to identical input differ depending on the drill-down path a user follows. To correct this Issue, to allow custom searching, and to improve general accessibility, PDS sought to create a new data structure and API, and to use them to build applications that are a joy to use and showcase the value of the data to students, teachers and citizens. PDS engaged TopCoder and Harvard Business School through the NTL to pursue these objectives in a pilot effort. Scope was limited to Small Bodies Node data. NTL analyzed data, proposed a solution, and implemented it through a series of micro-contests. Contest focused on different segments of the problem; conceptualization, architectural design, implementation, testing, etc. To demonstrate the utility of the completed solution, NTL developed web-based and mobile applications that can compare targets, regardless of mission. To further explore the potential of the solution NTL hosted "Mash-up" challenges that integrated the API with other publically available assets, to produce consumer and teaching applications, including an Augmented Reality iPad tool. Two contests were also posted to middle and high school students via the NoNameSite.com platform, and as a result of these contests, PDS/SBN has initiated a Facebook program. These contests defined and implemented a data warehouse with the necessary migration tools to transform legacy data, produced a public web interface for the new search, developed a public API, and produced four mobile applications that we expect to appeal to users both within and, without the academic community.

LaMora, Andy↗

Stability Analysis of ISS Medications

It is known that medications degrade over time, and that extreme storage conditions will hasten their degradation. The temperature and humidity conditions of the ISS have been shown to be within the ideal ranges for medication storage, but the effects of other environmental factors, like elevated exposure to radiation, have not yet been evaluated. Current operational procedures ensure that ISS medications are re-stocked before expiration, but this may not be possible on long duration exploration missions. For this reason, medications that have experienced long duration storage on the ISS were returned to JSC for analysis to determine any unusual effects of aging in the low- Earth orbit environment. METHODS Medications were obtained by the JSC Pharmacy from commercial distributors and were re-packaged by JSC pharmacists to conserve up mass and volume. All medication doses were part of the ISS crew medical kit and were transported to the International Space Station (ISS) via NASA's Shuttle Transportation System (Space Shuttle). After 568 days of storage, the medications were removed from the supply chain and returned to Earth on a Dragon (SpaceX) capsule. Upon return to Earth, medications were transferred to temperature and humidity controlled environmental chambers until analysis. Nine medications were chosen on the basis of their availability for study. The medications included several of the most heavily used by US crewmembers: 2 sleep aids, 2 antihistamines/decongestants, 3 pain relievers, an antidiarrheal and an alertness medication. Each medication was available at a single time point; analysis of the same medication at multiple time points was not possible. Because the samples examined in this study were obtained opportunistically from medical supplies, there were no control samples available (i.e. samples aged for a similar period of time on the ground); a significant limitation of this study. Medications were analyzed using the HPLC/MS methods described in the United States Pharmacopeia (USP) to measure the amount of intact active ingredient, identify degradation products and measure their amounts. Some analyses were conducted by an independent analytical laboratory, but certain (Schedule) medications could not be shipped to their facility and were analyzed at JSC. RESULTS Nine medications were analyzed with respect to active pharmaceutical ingredient (API) and degradant amounts. Results were compared to the USP requirements for API and degradants/impurities content for every FDA-approved medication. One medication met USP requirements at 5 months after its expiration date. Four of the nine (44% of those tested) medications tested met USP requirements up to 8 months post-expiration. Another 3 medications (33% of those tested) met USP guidelines 2-3 months before expiration. One medication, a compound classed by the FDA as a dietary supplement and sometimes used as a sleep aid, failed to meet USP requirements at 11 months post-expiration. CONCLUSION Analysis of each medication at a single time point provides limited information on the stability of a medication stored in particular conditions; it is not possible to predict how long a medication may be safe and effective from these data. Notwithstanding, five of the nine medications tested (56%) met USP requirements for API and degradants/impurities at least 5 months past expiration dates. The single compound that failed to meet USP requirements is not regulated as strictly as prescription medications are during manufacture; it is unknown if this medication would have met the requirements prior to flight. Notably, it was the furthest beyond its expiration date. Only more comprehensive analysis of flight-aged samples compared to appropriate ground controls will permit determination of spaceflight effects on medication stability.

Wotring, V. E.↗

Prototyping Operational Autonomy for Space Traffic Management

Current state of the art in Space Traffic Management (STM) relies on a handful of providers for surveillance and collision prediction, and manual coordination between operators. Neither is scalable to support the expected 10x increase in spacecraft population in less than 10 years, nor does it support automated manuever planning. We present a software prototype of an STM architecture based on open Application Programming Interfaces (APIs), drawing on previous work by NASA to develop an architecture for low-altitude Unmanned Aerial System Traffic Management. The STM architecture is designed to provide structure to the interactions between spacecraft operators, various regulatory bodies, and service suppliers, while maintaining flexibility of these interactions and the ability for new market participants to enter easily. Autonomy is an indispensable part of the proposed architecture in enabling efficient data sharing, coordination between STM participants and safe flight operations. Examples of autonomy within STM include syncing multiple non-authoritative catalogs of resident space objects, or determining which spacecraft maneuvers when preventing impending conjunctions between multiple spacecraft. The STM prototype is based on modern micro-service architecture adhering to OpenAPI standards and deployed in industry standard Docker containers, facilitating easy communication between different participants or services. The system architecture is designed to facilitate adding and replacing services with minimal disruption. We have implemented some example participant services (e.g. a space situational awareness provider/SSA, a conjunction assessment supplier/CAS, an automated maneuver advisor/AMA) within the prototype. Different services, with creative algorithms folded into then, can fulfil similar functional roles within the STM architecture by flexibly connecting to it using pre-defined APIs and data models, thereby lowering the barrier to entry of new players in the STM marketplace. We demonstrate the STM prototype on a multiple conjunction scenario with multiple maneuverable spacecraft, where an example CAS and AMA can recommend optimal maneuvers to the spacecraft operators, based on a predefined reward function. Such tools can intelligently search the space of potential collision avoidance maneuvers with varying parameters like lead time and propellant usage, optimize a customized reward function, and be implemented as a scheduling service within the STM architecture. The case study shows an example of autonomous maneuver planning is possible using the API-based framework. As satellite populations and predicted conjunctions increase, an STM architecture can facilitate seamless information exchange related to collision prediction and mitigation among various service applications on different platforms and servers. The availability of such an STM network also opens up new research topics on satellite maneuver planning, scheduling and negotiation across disjoint entities.

space traffic management↗

Probabilistic Modeling of Commercial Building Occupancy Patterns Using Location-Based Map Data: Preprint

Considering occupancy patterns is crucial to simulate buildings' energy use. Current energy models use inputs that simplify the actual diversity in occupancy into static occupancy patterns and are not able to represent the numerous variations in occupancy patterns between buildings and across different locations. Recently, inferring occupancy schedules from metered electricity consumption data was used to model occupancy in commercial buildings. However, the translation from metered data to occupancy schedules requires many assumptions that might not capture the reality, and the process is hindered by the availability of data from advanced metering infrastructure. With the development of information technologies, occupancy modeling should not be limited to traditional approaches. The prevalence of social networks and location services with real-time user feedback provides publicly accessible data via Maps Application Programming Interfaces (APIs) such as Google Maps, SafeGraph, Mapbox, Foursquare, etc. This paper presents an automated framework for modeling parametric occupancy patterns using such APIs to calibrate commercial district buildings' energy models. This process includes three main steps: data extraction and processing, parametric schedules generation, and schedules integration. We demonstrated this framework in districts where we used maps API to generate more accurate behavioral patterns for operations and electric vehicle charging events. We used these patterns to determine differences in energy use across key sociodemographic and spatial parameters. The presented method has the potential for worldwide applications. Users can utilize this framework to extract data for selected locations of interest to create more realistic behavioral patterns for commercial facilities across different districts.

building energy modeling↗

Flaw Tolerance Assessment for DOE Standard SNF Dry Storage Canisters - 26550

The U.S. DOE has designed four spent nuclear fuel (SNF) dry storage canisters for storing DOE standardized SNFs. The DOE standard canisters are cylindrical shells with a diameter of 24 inches (610 m) or 18 inches (457 m), a wall thickness of 0.5 inches (12.7 m) or 0.375 inches (9.53 m), and a length of 15 feet (4.57 m) or 10 feet (3.05 m). These DOE canister geometries are completely different from commercial canisters. The latter may experience chloride-induced stress cracking corrosion (CI-SCC) because they are stored near coastal regions. The former may not experience CI-SCC but face different challenges because they are stored in the SNF storage facilities. Because of large residual stresses, mechanical flaws may occur in the DOE canisters during long-distance transportation or lifting handling. To date, only limited structural integrity analyses were carried out through drop tests on the DOE canisters, but a more general flaw tolerance assessment has not been performed. Therefore, the failure assessment diagram (FAD)-based fracture mechanics method, as codified by the latest API 579-1/ASME FFS-1-2021 Edition, is adopted in this work to assess surface flaw tolerance for DOE canisters under operation loading and welding residual stresses (WRS), where the new code-recommended WRS distributions are used. To more adequately consider the transverse distribution of WRS, an equivalent WRS distribution is proposed to account for the WRS reduction with distance from the weld centerline. Moreover, the closed-form solutions of stress intensity factor K, which serves as the crack driving force during subcritical crack growth, are developed from the tabular data of the K factors provided in API 579-1/ASME FFS-1 and used to determine more accurate flaw sizes at flaw instability. Subsequently, the Level 2 assessment procedures with 12 assessment steps, as codified and detailed in API 579-1 and ASME FFS-1, are followed to assess the flaw tolerance for the surface flaws in the DOE standard canisters with consideration of normal or accident operation loads combined with WRS. The assessment results show that the four designs of DOE standard canisters can tolerate all surface flaws that meet the code permitted maximum sizes of a flaw length of 8 inches (i.e., 200 mm) and a flaw depth of 80% wall thickness. This demonstrates that all designs of DOE standard canisters are robust and reliable.

DOE standard canister↗