Search NASA⌕ Search

SEARCH · Search NASA

Results for “Code Validation Plan”

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.

311 records · Page 18
All sourcesNASA NTRSDOE OSTI
DOE OSTI2025

IM3 Open Source Data Center Atlas

IM3 Open Source Data Center Atlas Description This dataset contains locations of existing data center facilities in the United States. Data center locations were derived from OpenStreetMap (OSM), a crowd-sourced database. Data points from OSM are processed in various ways to determine additional variables provided in the data including: facility area (square feet), associated US county, and US state. This dataset can be used to identify areas of concentrated data center development and inform government and private sector planning strategies for future buildout of data centers and the infrastructure necessary to support it. Usage Notes Validation of OSM-derived data center locations is an ongoing development under the IM3 project, and the database will be updated as new information becomes available. In some instances, both the data center area (e.g., campus) and individual data center buildings are included as overlapping areas in the database. Both values are retained. Data center points, buildings, and campus areas are provided as separate layers in the downloadable data package. Note that data items are not necessarily complete across layers. That is, a specific data center may only be present as a single point geometry in the "point" layer while other data centers are represented in both the campus and building layers. In some cases, data center campuses and/or buildings straddle a county boundary line. Mappings to both counties are retained in the database as separate rows. These data rows will have the same data center id information, but each will have different county information. Crowd-sourced data, by nature, relies on individuals and communities to provide information. As a result, some data may be missing where it has not yet been reported. As we collect information on additional data center locations and as OSM receives additional contributions, the database will be updated to capture additional data points not yet shown. Technical Information Data is available for download under the following formats: GeoPackage (GPKG) CSV Geospatial data is provided in the WGS84 (EPSG:4326) coordinate reference system. The GeoPackage download contains the following layers. See usage notes for more information. "point" "building" "campus" The "point" layer includes all data from OSM that had POINT geometry type (i.e., individual coordinates). The "building" layer includes all OSM data that did not have POINT geometry and where the building tag in the OSM export was neither equal to "no" or null. Data that did not meet the "point" or "building" qualification was assumed to be a facility campus and included in the "campus" layer. The dataset contains the following parameters. Variables provided by OSM are labeled with (OSM-provided). id - unique identification number (OSM-provided with prefix of "node/", "relation/" and similar attributes removed) state - name of US state state_abb - two letter US state abbreviation state_id - state ID number county - name of US county county_id - county ID number ref - reference numbers or codes (OSM-provided) operator - the name of the company, corporation, or person in charge facility (OSM-provided) name - name of facility (OSM-provided) sqft - surface area of facility polygon, measured in square feet. Only available for "building" and "campus" layers lat - latitude of data centroid point lon - longitude of data centroid point type – represented spatial information. One of "point", "building", or "campus". geometry – POLYGON geometry of area footprint (in "campus" and "building" layers) or POINT geometry of locations (in "point" layer). This parameter is not included in the csv download. Attribution Data center locations were derived from OpenStreetMap, which is made available at openstreetmap.org under the Open Database License (ODbL). US state and county boundary information was collected from the US Census Bureau for the year 2024, which is made publicly available at https://www.census.gov/geographies/mapping-files.html Acknowledgment IM3 is a multi-institutional effort led by Pacific Northwest National Laboratory and supported by the U.S. Department of Energy's Office of Science as part of research in MultiSector Dynamics, Earth and Environmental Systems Modeling Program. License The IM3 Open Source Data Center Atlas is made available under the Open Database License: http://opendatacommons.org/licenses/odbl/1.0/. Disclaimer This material was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the United States Department of Energy, nor the Contractor, nor any or their employees, nor any jurisdiction or organization that has cooperated in the development of these materials, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness or any information, apparatus, product, software, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof, or Battelle Memorial Institute. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or any agency thereof. PACIFIC NORTHWEST NATIONAL LABORATORYoperated byBATTELLEfor theUNITED STATES DEPARTMENT OF ENERGYunder Contract DE-AC05-76RL01830

Mongird, Kendall [Pacific Northwest National Labor↗
DOE OSTI2025

Cross-Code Verification of Neutronics Analysis Tools at INL Applied for 238 Pu Production in the Advanced Test Reactor

Here, analyses are completed for experiments prior to experiment irradiation in the Advanced Test Reactor (ATR) at Idaho National Laboratory (INL). Various codes are used to qualify all experiments planned for insertion in the reactor, thereby ensuring that all safety and programmatic requirements are satisfied preirradiation. Among the common experiment analysis tools at INL are MCNP5 coupled to ORIGEN2 (MOPY) and MC21. MOPY uses MCNP5 for transport calculations along with calculations for fluxes and select reaction rates, and then ORIGEN2 handles the step-by-step and postirradiation depletion. MC21 handles all in-reactor transport and step-by-step, during-irradiation, depletion calculations, and then ORIGEN (SCALE 6.2.3) is used for decay and dose calculations postirradiation. The MOPY results, along with those obtained via two variations of the MC21 model, were compared in terms of 238 Pu production in the ATR’s H10 position. For the MOPY model, the MC21 model utilizing the HELIOS-based fission product (FP) library, and the MC21 model utilizing the expanded 1300 FP library, the during-cycle irradiation in-core heating results were sufficiently equivalent; however, the MOPY model and the MC21 model with the HELIOS library showed some differences relating to the respective FP libraries. Ultimately, the MC21 model with a 1300 FP library produced the most consistent results throughout the cycle, whereas the MC21 model that utilized the (smaller) HELIOS library was able to handle during-irradiation analysis but lacked certain short-lived FPs that significantly contributed to the total decay heat at shutdown. MOPY, on the other hand, was found to overpredict fission gas production, as a result of limitations in the ORIGEN2 code.

ATR↗
DOE OSTI2026

IM3 Open Source Data Center Atlas

IM3 Open Source Data Center Atlas Description This dataset contains locations of existing data center facilities in the United States. Data center locations were derived from OpenStreetMap (OSM), a crowd-sourced database. Data points from OSM are processed in various ways to determine additional variables provided in the data including: facility area (square feet), associated US county, and US state. This dataset can be used to identify areas of concentrated data center development and inform government and private sector planning strategies for future buildout of data centers and the infrastructure necessary to support it. Usage Notes Validation of OSM-derived data center locations is an ongoing development under the IM3 project, and the database will be updated as new information becomes available. In some instances, both the data center area (e.g., campus) and individual data center buildings are included as overlapping areas in the database. Both values are retained. Data center points, buildings, and campus areas are provided as separate layers in the downloadable data package. Note that data items are not necessarily complete across layers. That is, a specific data center may only be present as a single point geometry in the "point" layer while other data centers are represented in both the campus and building layers. In some cases, data center campuses and/or buildings straddle a county boundary line. Mappings to both counties are retained in the database as separate rows. These data rows will have the same data center id information, but each will have different county information. Crowd-sourced data, by nature, relies on individuals and communities to provide information. As a result, some data may be missing where it has not yet been reported. As we collect information on additional data center locations and as OSM receives additional contributions, the database will be updated to capture additional data points not yet shown. Data items will occasionally be removed from OSM if they are misidentified, if they no longer exist, if they are duplicates of another item, or similar. For that reason, updated versions of this database may not contain all data center locations included in previous versions. Technical Information Data is available for download under the following formats: GeoPackage (GPKG) CSV Geospatial data is provided in the WGS84 (EPSG:4326) coordinate reference system. The GeoPackage download contains the following layers. See usage notes for more information. "point" "building" "campus" The "point" layer includes all data from OSM that had POINT geometry type (i.e., individual coordinates). The "building" layer includes all OSM data that did not have POINT geometry and where the building tag in the OSM export was neither equal to "no" or null. Data that did not meet the "point" or "building" qualification was assumed to be a facility campus and included in the "campus" layer. The dataset contains the following parameters. Variables provided by OSM are labeled with (OSM-provided). id - unique identification number (OSM-provided with prefix of "node/", "relation/" and similar attributes removed) state - name of US state state_abb - two letter US state abbreviation state_id - state ID number county - name of US county county_id - county ID number ref - reference numbers or codes (OSM-provided) operator - the name of the company, corporation, or person in charge facility (OSM-provided) name - name of facility (OSM-provided) sqft - surface area of facility polygon, measured in square feet. Only available for "building" and "campus" layers lat - latitude of data centroid point lon - longitude of data centroid point type – represented spatial information. One of "point", "building", or "campus". geometry – POLYGON geometry of area footprint (in "campus" and "building" layers) or POINT geometry of locations (in "point" layer). This parameter is not included in the csv download. Attribution Data center locations were derived from OpenStreetMap, which is made available at openstreetmap.org under the Open Database License (ODbL). US state and county boundary information was collected from the US Census Bureau for the year 2024, which is made publicly available at https://www.census.gov/geographies/mapping-files.html Acknowledgment IM3 is a multi-institutional effort led by Pacific Northwest National Laboratory and supported by the U.S. Department of Energy's Office of Science as part of research in MultiSector Dynamics, Earth and Environmental Systems Modeling Program. License The IM3 Open Source Data Center Atlas is made available under the Open Database License: http://opendatacommons.org/licenses/odbl/1.0/. Disclaimer This material was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the United States Department of Energy, nor the Contractor, nor any or their employees, nor any jurisdiction or organization that has cooperated in the development of these materials, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness or any information, apparatus, product, software, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof, or Battelle Memorial Institute. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or any agency thereof. PACIFIC NORTHWEST NATIONAL LABORATORYoperated byBATTELLEfor theUNITED STATES DEPARTMENT OF ENERGYunder Contract DE-AC05-76RL01830

Mongird, Kendall [Pacific Northwest National Labor↗
DOE OSTI2022

Bay Area Regional Energy: Network Integrated Commercial Retrofits (BRICR) Project. Final Report

The BRICR project applied large-scale building energy modeling concepts with the aim of reducing the cost of energy efficiency targeting, design, and project development, and measurement of energy savings for energy efficiency programs implemented by local governments that serve small and medium commercial buildings (SMB). The project leveraged the services and resources of existing local government energy programs serving disadvantaged and hard-to-reach SMB customers. In contrast to programs run by utilities, local government programs generally do not have direct access to energy billing records for an entire class of customers in a geographic area, which prior research demonstrated useful for large-scale building energy model baseline development and calibration. , However, local governments are rich in public records that offer important clues about physical attributes and uses that, along with behavior, determine energy use. Relying only on public records, BRICR demonstrated development of credible baseline energy models for 3,792 office, retail, and hotel buildings. Publicly disclosed annual energy use data from a local energy benchmarking program and anonymized data from the Building Performance Database, the nation’s largest dataset about energy-related characteristics of buildings, were utilized to validate and calibrate energy models via an innovative method comparing distributions of energy intensity by fuel type for portfolios of buildings of similar size, vintage, and use. Portfolio calibration does not provide certainty that an energy model fits an individual building; the method is useful when billing data is not accessible – a common situation for researchers, energy service providers and ESCOs, local governments, and any party other than a utility. A software component was developed, the BRICR gem, which automates simulation when relevant data is added or edited by the user to a file saved in the standardized BuildingSync XML schema for energy audit data. The component was demonstrated as a simplified means to generate a mass of energy models corresponding to public records containing basic attributes such as building scale, location, use, year built, and aspect ratio in combination with building energy code prototype data corresponding to use and vintage. The component was also demonstrated as a simplified means to automate energy simulation when attributes are revised; the intention was to enable iterative improvement of the baseline model and energy savings estimates for common energy conservation measures as users revise relevant attributes based on their observations. In the context of institutional change and uncertainty for the participating local government energy programs, 13 whole building retrofits were completed. Impacts were measured by applying the CalTRACK2.0 methods to standardize measurement of normalized metered energy consumption. The GRIDMeter methods of stratified sampling and individual load shape analysis were applied to adjust for impacts of the effect of COVID-19 on retrofitted buildings in the context of all local buildings of similar size and use. Excluding impacts of the pandemic, retrofitted buildings demonstrated between 1.6% and 25.1% reduction in energy use. The project contributed use cases and feedback that helped inform evolution of the software tools and data formats that were combined for the first time in the BRICR project.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗
DOE OSTI2020

Sensitive Resources Assessment and Forest Analysis for the Proposed Versatile Test Reactor, Oak Ridge, Tennessee

The US Department of Energy’s (DOE’s) Oak Ridge National Laboratory (ORNL) is a leading institution in advanced materials, supercomputing, neutrons, and nuclear science. As a research laboratory managed by UT-Battelle, LLC for DOE, ORNL has national priorities in energy, security, and scientific discovery that necessitate facility improvements and expansions. DOE is also committed to environmental stewardship. The laboratory is located on the ~32,000-acre (~13,000-ha) Oak Ridge Reservation (ORR), much of which is categorized as a National Environmental Research Park (NERP) and a state Wildlife Management Area. DOE works with the Tennessee Wildlife Resources Agency (TWRA), Tennessee Department of Environment and Conservation (TDEC), US Fish and Wildlife Service (USFWS), US Department of Agriculture, and other agencies to serve as an effective steward of the ORR. Accordingly, project managers must conform to environmental regulations, agreements, and policies at the federal, state, and institutional levels. Per 40 CFR (Code of Federal Regulations) 1508.14, potential effects on research and science education also represent potential effects of federal actions on the NERP, and impacts on, e.g., deer harvest, must be considered on the Oak Ridge Wildlife Management Area when other aspects of the human environment are affected. The United States currently has no fast neutron testing capability to support advanced nuclear research and development. The proposed Versatile Test Reactor (VTR) will take advantage of current investments by the US government and private industry in nuclear reactors to expedite the design and construction process, using proven technology to create a world-class scientific infrastructure. The VTR will take advantage of fast neutrons provided by this proven technology, along with a capability to rapidly insert, conduct, and remove state-of-the-art experiments. An advantage of the VTR is that it can support future innovations in experimental capabilities without modifying the facility. The VTR will support progress in a variety of science and technology areas, including testing and qualification of advanced reactor fuels; testing and qualification of innovative structural materials; testing of innovative components and instruments; validation of advanced modeling and simulation tools; and versatility for future technical missions. Through proven technology, the VTR can take advantage of existing reactor designs and operating experience to reduce the risk, cost, and time for design and construction. The top available resources of DOE laboratories, industry, and universities will be used to expedite reactor design and construction toward developing the scientific infrastructure that affords a strong testing capability that can be sustained over many years. This report summarizes current knowledge of natural and cultural resources primarily within the VTR construction area. At the time of this report, the proposed VTR site design includes a construction area of ~150.4 acres (~69.9 ha), which contains an ~51.3-acre (~20.8-ha) operations area, located within forested natural areas of the ORR. The primary goal of the work presented here was to evaluate potential effects on sensitive resources that might result from development and construction activities associated with VTR. In addition to on-the-ground surveys during spring and summer 2020 by the ORNL Natural Resources Management Program and Aquatic Ecology Group staff, this report makes use of historical (pre-1995) and contemporary (1995 to present) data from additional confirmed sources (e.g., TDEC). Likewise, forest conditions were compiled from a 2011 forest inventory and supplemented with limited ground observations in 2020. The individuals who obtained and compiled the data presented here are familiar with and routinely assess sensitive resources on the ORR. Anyone who references this report must consider that the timing of surveys did not permit a complete delineation of the resources that will be affected. If the VTR project proceeds, additional surveys will be required to account for the seasonal patterns of various threatened and endangered species. Data deficiencies and potential resources that likely went undetected are indicated where possible. Accordingly, this report should facilitate more environmentally sound decisions during planning and 2 development of the VTR site, provide a foundation for further assessment of sensitive and cultural resources, and help project managers better address regulatory guidance and DOE policies on sustainable development in compliance with, for example, the US Endangered Species Act (ESA), Migratory Bird Treaty Act (MBTA), Tennessee Rare Plant Protection and Conservation Act of 1985, Tennessee Nongame and Endangered or Threatened Wildlife Species Conservation Act of 1974, several federal and state regulations regarding aquatic resource protection, and site-specific policies as outlined in various ORR management plans developed by ORNL and TWRA for DOE.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗