Engineering Papers⌕ Search

Engineering topics

Ulrich, Rachel Alicia

Publications and source records attributed to Ulrich, Rachel Alicia.

Tools for Water Ingress Testing

The Safety Storage and Engineering Team, as part of the Production Support Services division (PSS-2), is tasked with ensuring the safety of containers used for handling and storage of nuclear materials. As part of this work, water ingress tests are conducted to evaluate the water-tightness of containers intended for in-glovebox use. In collaboration, the statistics group of the Computer and Computational Sciences Division (CCS-6) provided support in developing a statistically defensible approach for determining appropriate sample sizes for water ingress testing. Water ingress testing involves multiple measurements on multiple containers. Our approach uses a simple random effects model to analyze a pilot data set, implementing prediction limits to evaluate the efficacy of collecting additional data. Although this study capitalizes on available data, our approach can be used with estimates of the ratio of between and within variability and average values, often available from past testing or expert knowledge. An interactive Shiny tool was developed as a final user-friendly product for future testing. The Shiny interface is an open-source package providing a framework for building web applications. Raw data exploration and prediction interval-based sample size assessments can quickly be conducted by the engineering team without needing to interact with the underlying code.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Historic Source Inspection Metadata

Although this data dictionary describes the raw data format, it is relevant only for data entered in 2017 and later. Entries in this date range represent formatted, standardized data that have been verified against original, raw data files by the database manager. She took ownership of the database in September 2022 and was able to standardize entries by comparing against raw data files back to 2017. Furthermore, for comparison of historic pre-source inspection data to new pre-source data supplied by the vendor and intended for action limit analysis purposes, this time period is of sufficient length.

97 MATHEMATICS AND COMPUTING↗

Historic Source Inspection Records

To create true counts of number of containers, each container can be identified by a combination of the purchase order, unique part number and type of inspection. The column TestEventName and any columns derived from TestEventName should not be used in the instance of presource inspection because the vendor may mete out testing over multiple months, meaning that a container would be counted twice if a single test was completed in one month and another test in a different month. By counting on this combination of values, we are able to drop row entries that signify multiple tests completed on a single container. Inspection type must be used because each container will be tested by the vendor and re-tested by the LANL container engineering team. Recall that the vendor will complete action limit tests for the full set of containers during pre-source inspection but during source inspection, action limit tests are completed for only a random subset. However, LANL SMEs will complete a manual inspection for the full set of containers.

42 ENGINEERING↗