Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “FILES”

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 1,801 records · Page 100

Navigation and Meteorological Data from Multiple Sensors on Airborne Platform (NAVMET-AIR) Value-Added Product Report

The Navigation and Meteorological Data from Multiple Sensors on Airborne Platform (NAVMET-AIR) value-added product encompasses the aafnaviwg data set in the ARM Data Center (ADC), known as the IWG file, named for the Inter-Agency Working Group for Airborne Data and Telemetry Systems (IWGADTS). Its purpose is to produce a suite of tools to promote standardization of instrument interface, data format, and data processing. This data set’s contents are navigational and meteorological state variables at 1 Hz. It also contains higher-order data flags created by ARM Aerial Facility (AAF) scientists to aid analysis such as periods when the aircraft is flying level, operating in maneuvers, or flying through cloud. Due to the nature of research flights, the payload of the aircraft consists of many duplicate and overlapping instruments to ensure, in case of instrument failure, there is a backup to record the data. Measurements from multiple instruments are consolidated into a single file. Each variable of this data set is carefully chosen from the onboard instrumentation and quality checked by AAF scientists to create this wholistic and most accurate data set for airborne research. This document is intended to be a hub towards the individual “read me” files produced for each campaign. For reference about what instrument was used for calculations on specific days, the read me files are located in the ARM IOP archive at the addresses listed, or access the IOP (intensive operational period) database at https://www.archive.arm.gov/.

54 ENVIRONMENTAL SCIENCES↗

Understanding Lustre Internals. Second Edition

The Lustre file system has become a preferred storage resource for systems on the Top500 list, and it is often the file system of choice for small- to medium-sized HPC systems that require parallel shared access to data. Several resources exist to help users deploy and configure Lustre, but the same cannot be said for resources that explain the inner workings of the Lustre source code. A previous ORNL technical report entitled "Understanding Lustre Filesystem Internals" (ORNL/TM-2009/117) provided an excellent summary of Lustre subsystem operations. However, that report is over a decade old and is based on Lustre version 1.6. Since that report was published, Lustre has evolved significantly. Several subsystems underwent significant code changes and many new features have been added to the file system, bringing the current Lustre version up to 2.15.This report aims to document and explain the internal workings of the latest version of the Lustre file system. It will provide more complete and up-to-date information than the previous technical report and should serve as a foundational document for anyone interested in Lustre software development. Key data structures will be described along with the APIs used for interaction among the various Lustre subsystems. Although the Lustre software is constantly being developed, the details in this document should remain relevant for the forseeable future.

97 MATHEMATICS AND COMPUTING↗

FY21 Progress Report: SRNL Analysis of ICCWR LCM and WAMS data for Corrosion and Cracking

The development of algorithms for machine learning and data analysis for the 3013 Surveillance Program is a collaborative effort by the Savannah River National Laboratory (SRNL) and the University of South Carolina (USC). For corrosion detection, Laser Confocal Microscope (LCM) or Wide Area 3D Measurement System (WAMS) data is extracted from large binary files, with software written to convert the data to physical attributes (e.g., height, color and grayscale values; all as functions of a location in a plane projection). A user-friendly Matlab Graphical User Interface (GUI) that reads data from either LCM or WAMS files was developed to integrate input data with software developed for processing and evaluation. The GUI can selectively download binary data, interrogate data attributes, label data, flag significant features, execute Machine Learning (ML) algorithms, output parameters for trained ML algorithms, report ML model accuracy with respect to labeled data, and generate graphical representations for various analyses. Features can be called out by user-specified thresholds, manual labeling or machine learning algorithms when they have been completed. The ability to rapidly label data is important because of the volume of data required for training machine learning algorithms. The GUI has the flexibility to allow addition of improved ML algorithms, methods for data visualization, and statistical computations. Statistical analyses via the GUI include areas of pits within a defined range of pit depths, correlations between Red-Green-Blue (RGB) or grayscale intensity and relative surface height, covariances between values associated with features, and feature histograms. The development of supervised machine learning algorithms, however, has been hindered by a lack of training data. The machine learning algorithms for crack identification are being refined but require improvements to the true positive rate for crack detection. This shortcoming is an artifact of the limited training data currently available, perhaps more so than the structure of the neural networks. At present, the best results are had from a consensus over an ensemble of randomly generated Deep Neural Network (DNN) or Convolutional Neural Network (CNN) algorithms. Although the consensus accuracy method has yielded optimum true positive and true negative rates in excess of 80%, additional validation testing is necessary. In addition to the suite of LCM data that was initially used, and which represents the majority of the work presented in this report, WAMS image data was also reviewed at a preliminary level. The review included a comparison between image resolution and dynamic range for each method. WAMS (ZON file) image data was found to have a pixel pitch of 3.69μm compared to 1 μm for the LCM (vk4 file) data, which implies a lower resolution for the WAMS images. Conversely, the ratio of dynamic range of the WAMS data to the LCM data was approximately 41:20 for height data, suggesting that information from WAMS should more accurately determine the depth of pits. At present, the significance of the greater dynamic range of the WAMS data relative to the LCM data has not yet been evaluated.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Decay Curve Correction Analysis Report

The decay curve analysis that is done on the short-lived radionuclide gas samples is used to differentiate between gaseous radionuclides that have the same characteristic gamma decay energy, 511 kiloelectron-volts (keV). A sample of stack gas is isolated and the total counts in the 511 keV peak are counted repeatedly in 10-second intervals to evaluate the decay rate of the sample over time. Analysis of this decay data required a series of steps. First, a raw data report is generated by the gamma acquisition system, based on an analysis template within the acquisition software. The data report file was then loaded into Microsoft Word, and a macro was used to perform minor formatting (remove colons and insert tabs between data columns) to allow analysis within Excel. The file is then saved as a text file at this point. The text file is then uploaded into Excel and a series of macros are used to add labels, calculate radioactive decay constants, and analyze the gamma decay data using linear regression techniques. The analysis template has been used since 1998 for stack 53000303 (TA-53, building 0003, exhaust stack 03) and 2000 for stack 53000702. The overall process, including the gamma report format and the macros used in Word and Excel for processing the report, had remained unchanged until 2015. In October of 2015, staff made a change to the report template in the gamma acquisition software which resulted in an error in the calculations later performed by the Excel macro. This error was not caught until a more in-depth review of the analysis took place regarding 2020 data. This report covers a much more complete review of the issue that occurred regarding the decay curve analysis, a review of the calculations completed to correct the issue, a review of the updated decay curve analysis process, and recommendations for moving forward.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

PDQ Users Manual. Manual Version 2, for PDQ Code Version 1.20

PDQ is a tool for the management of the input and execution of batch jobs for simulation codes that use a text based input system. It accomplishes this goal by operating at two levels. First, it takes input file templates (commonly known at LANL as input deck templates) and creates multiple instantiations by performing substitutions of data from table files into symbols (variables) found in the template. Second, it provides commands to submit the created files to the SLURM batch system for execution. These two activities taken together produce a whole that is greater than the sum of its parts and provides an elegant way of executing studies across multiple similar simulations while minimizing the risk of typographical errors in the input files. PDQ was originally developed as a job management system called XVS by Jeff McAninch while he was at LANL. Besides the capabilities described here, XVS had many other features specific for interactions with particular simulation codes. After Jeff’s departure, maintenance of XVS was taken over by Rendell Carver; he added some new features as well as kept it functioning as the batch system at LANL was changed from LSF to MOAB to SLURM. In 2017, Rob Pelak decided to develop a different version that removed the additional features (many of which were rendered obsolete with the retirement of the simulation code or batch system that they supported) and produced a cleaner “bare bones” version of XVS. A few other behaviors of XVS that Rob found irksome were altered. Rob gave the resulting code a new name: PDQ. In 2022 Danielle McDermott developed a version that runs under Python 3.X. As suggested by Rob, she used the python2to3 utility to identify most changes. Given that PDQ continues to operate with Python version 2.7 we have advanced the version number to 1.20.

97 MATHEMATICS AND COMPUTING↗

MelMACCS User Guide - V.4.0.0

The MelMACCS User Guide is intended to assist analysts in how to use the MelMACCS application to create an interface file that can be used in a MACCS calculation. MelMACCS combines MELCOR results, in the form of a MELCOR plot file, with user input. This information is used to create a MelMACCS output file that is in a format compatible with MACCS. It can then be imported as an input file in WinMACCS and used for MACCS calculations.

97 MATHEMATICS AND COMPUTING↗

Easy_PERT: a Python tool for writing PERT cards and parsing PERT card results [Slides]

This presentation begins by providing an overview of the PERT card. The PERT card uses differential operator method to compute first- and second-order tally variations due to density, composition, and reaction cross-sections. It is possible to have multiple PERT cards in one MCNP input deck to study tally variations for several sets of nuclides, reactions, and energy ranges. Furthermore, the METHOD option tells MCNP to calculate either the perturbed tally (METHOD=-1, -2, -3) or the change in the unperturbed tally (METHOD=1, 2, 3). In summation, a powerful use-case for the MCNP code PERT card is that it facilitates calculating tally sensitivities to nuclear data. Writing PERT card entries and parsing output MCTAL files is tedious and error prone. however, Easy_PERT makes use of existing tools (Faust and MCNPTools) to handle writing PERT card entries and parsing the output MCTAL files. The PERT card is early in the development process and planned upcoming capabilities include calculating sensitivities and combining MCTAL files from separate runs into one JSON file.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

Grid Resilience Plans: State Requirements, Utility Practices, and Utility Plan Template

As of June 2024, 14 states and one city require jurisdictional electric utilities to file resilience plans. Drawing on these requirements and filed plans, this report offers a standard template that states and utilities can consider to improve utility filings for grid resilience plans, either as part of a distribution system plan or as a separate filing. Key elements include a vulnerability assessment, description of proposed resilience programs, and projected costs and rate impacts. While many of these requirements and plans focus on extreme weather hazards, the template also can be used to address additional threats, including cyber and physical attacks and seismic events.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Processing MCNP Elemental Edit Outputs

The Monte Carlo N-Particle (MCNP) transport code version 6 (also known as MCNP6) has the capability for tracking particles on unstructured mesh (UM) geometry models embedded into constructive solid geometry (CSG) cells. A UM geometry is a collection of elements representing a solid geometry. The first step of MCNP UM modeling is using other software packages to create a finite element mesh representation of a solid 3D geometry. Computer-aided design (CAD) or computer-aided manufacturing (CAM) software is typically used to create a solid geometry model, which is later imported into mesh generation software to create a UM model. The MCNP UM feature was originally designed for models generated by the Abaqus/CAE software. The MCNP code version 6.0 and later can process UM models formatted as Abaqus input files. MCNP can process a UM model consisting of several different element types including linear tetrahedral or hexahedral elements and calculate quantities of interest such as flux and energy deposition at elements. An MCNP UM simulation provides high-fidelity elemental edit (i.e., tally) outputs, which can be further used in multiphysics calculations. The MCNP UM feature was used for multiphysics simulations where quantities of interest calculated by MCNP are used as inputs for heat transfer calculations in Abaqus. MCNP6.3 can produce two types of elemental edit output (EEOUT) file formats: ASCII and HDF5. An EEOUT file type must be requested on an EMBED card while output type (flux or energy deposition) must be requested on an EMBEE card. We wrote Python3 scripts to extract energy deposition values in an ASCII or HDF5 EEOUT file and compute a heat flux profile for an Abaqus heat transfer calculation.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

Evaluation of Dose Coefficients Implemented in MACCS

A variety of dose conversion factor files (DCF files) have been supplied for use with the MACCS code since it was initially released. For MACCS 4.2, the MACCS DCF files have been updated to include coefficients used in the computation of acute skin doses from within the MACCS software to increase functionality and to add a pseudo-organ to represent the total effective dose equivalent (TEDE) (as defined in 10 CFR 20.1003) based on International Commission on Radiological Protection (ICRP) Publication 30. This report provides a description of how these changes have been implemented and a summary of the various DCF files supplied with MACCS 4.2. The report also provides supplemental discussions to assist the reader in understanding the technical basis for the MACCS DCFs. These supplemental discussions include a summary of basic dosimetry modeling concepts and a brief review of the Federal Guidance Reports (FGRs) upon which MACCS dose coefficients have historically been based.

97 MATHEMATICS AND COMPUTING↗

A Framework for Addressing Hydropower Modeling Gaps in Electric Grid Planning and Operational Studies [Slides]

Realistic representation of hydropower in power system planning and operation studies is extremely important as it helps in avoiding under/over-estimation of the services the hydro power units can provide. A framework and tools have been developed to account for hydrological conditions and modify power system models accordingly. For example, HyDat – data and AI driven platform, that provides that data required for editing the power system model files Collaborative effort with V&R Energy. Also, development of POM based tools have been performed, a) Tool1: editing .raw files with realistic current and maximum hydrogeneration and redispatch of other units, and b) Tool2: Editing .dyr files to represent water head, current and maximum generation. Finally the framework, HASP framework combines HyDat and V&R energy tools to produce modified power system model files. Key Take-away points from contingency analysis studies include a) the number of critical contingencies increases as the water levels are reduced (70%>75%>80%), and b) both the extent and the quality of dynamic response of the Hydropower unit is different with varying water head levels.

13 HYDRO ENERGY↗

Data Format and Descriptions for the Alabama Carbon Storage: Data Sharing and Engagement Project

The Alabama Carbon Storage: Data Sharing and Engagement (ACS-DSE) project seeks to develop publicly accessible geologic carbon storage models and data across the southern Gulf Coastal Plain of Alabama. The public online platform developed for this project will include geologic, geophysical, infrastructure, and other relevant datasets and geologic models of the study area. Datasets, model surfaces (e.g. structural contour maps, isolith maps, porosity maps), and infrastructure data (e.g. offshore pipelines, field boundaries) will be downloadable in commonly used file formats. The anticipated primary geologic datasets are well headers, formation tops, average reservoir properties, and core analyses; these will be available as commaseparated values (CSV) text files and MS Excel workbooks. Geophysical logs will be available in Log ASCII Standard (LAS) file format. Modeled surfaces, such as structure contour maps, will be available in ArcGIS formats and text files. Infrastructure data will be available as ArcGIS shapefiles. This document provides information on the data sources and attributes of the datasets.

01 COAL, LIGNITE, AND PEAT↗

Corrective Action Decision Document/Closure Report for Corrective Action Unit 560: Septic Systems, Nevada Test Site, Nevada, Revision 0 with ROTC 1

Corrective Action Unit 560 comprises seven corrective action sites (CASs): •03-51-01, Leach Pit •06-04-02, Septic Tank •06-05-03, Leach Pit •06-05-04, Leach Bed •06-59-03, Building CP-400 Septic System •06-59-04, Office Trailer Complex Sewage Pond •06-59-05, Control Point Septic System The purpose of this CADD/CR is to provide justification and documentation supporting the recommendation for closure of CAU 560 with no further corrective action. To achieve this, corrective action investigation (CAI) activities were performed from October 7, 2008, through February 24, 2010, as set forth in the Corrective Action Investigation Plan for Corrective Action Unit 560: Septic Systems, Nevada Test Site, Nevada, and Record of Technical Change No. 1. The purpose of the CAI was to fulfill the following data needs as defined during the data quality objective (DQO) process: •Determine whether contaminants of concern (COCs) are present. •If COCs are present, determine their nature and extent. •Provide sufficient information and data to complete appropriate corrective actions. The CAU 560 dataset from the investigation results was evaluated based on the data quality indicator parameters. This evaluation demonstrated the quality and acceptability of the dataset for use in fulfilling the DQO data needs. Analytes detected during the CAI were evaluated against final action levels (FALs) established in this document. The following contaminants were determined to be present at concentrations exceeding their corresponding FALs: •No contamination exceeding the FALs was identified at CASs 03-51-01, 06-04-02, and 06-59-04. •The soil at the base of the leach pit chamber at CAS 06-05-03 contains arsenic above the FAL of 23 milligrams per kilogram (mg/kg) and polychlorinated biphenyl (PCBs) above the FAL of 0.74 mg/kg, confined vertically from a depth of approximately 5 to 20 feet (ft) below ground surface. The contamination is confined laterally to the walls of the leach pit chamber and leach rock. The contamination present at CAS 06-05-03 within the leach pit was not feasible to remove. •The surface and subsurface soils within and surrounding the septic system at CAS 06-05-04 contained PCB concentrations above the FAL of 0.74 mg/kg. The lateral and vertical extent of COCs was determined for this CAS. Contaminated soils were removed up to within 18 ft of the building. The remaining contamination is confined to subsurface soils adjacent to and beneath Building CP-162 and was not feasible to remove. •The solid materials within the septic tank and soils immediately surrounding the inlet end of the tank at CAS 06-59-03 contained benzo(a)pyrene above the FAL of 0.21 mg/kg. The soils, tank contents, and tank were removed. Materials remaining at this CAS do not contain contamination exceeding FALs. •The solids contained within the septic tank and inlet pipe at CAS 06-59-05 contained the following contaminants above their respective FALs: PCBs, arsenic, lead, benzo(a)pyrene, and pesticides. The tank and inlet pipe contents were removed. Materials remaining at this CAS do not contain contamination exceeding FALs. Therefore, the U.S. Department of Energy, National Nuclear Security Administration Nevada Site Office (NNSA/NSO) provides the following corrective action recommendations: •No further action for CASs 03-51-01, 06-04-02, and 06-59-04, as no contaminants of potential concern were present that exceed FALs. •Closure in place for CAS 06-05-03 under a corrective action with a use restriction (UR) for remaining PCB- and arsenic-impacted potential source material (PSM). The UR form and map have been filed in the NNSA/NSO Facility Information Management System, the FFACO database, and NNSA/NSO CAU/CAS files. •Closure in place for CAS 06-05-04 under a corrective action with a UR for remaining PCBs in soil adjacent to and beneath Building CP-162. The UR form and map have been filed in the NNSA/NSO Facility Information Management System, the FFACO database, and NNSA/NSO CAU/CAS files. •No further action for CAS 06-59-03, as the COC of benzo(a)pyrene in soil and PSM have been removed. •No further action for CAS 06-59-05, as the COCs in PSM within the septic tank and inlet piping have been removed and the tank was filled with concrete.

54 ENVIRONMENTAL SCIENCES↗

Detailed Modeling, Design, and Evaluation of a Scalable Multi-level Checkpointing System

High-performance computing (HPC) systems are growing more powerful by utilizing more hardware components. As the system mean-time-before-failure correspondingly drops, applications must checkpoint more frequently to make progress. However, as the system memory sizes grow faster than the bandwidth to the parallel file system, the cost of checkpointing begins to dominate application run times. A potential solution to this problem is to use multi-level checkpointing, which employs multiple types of checkpoints with different costs and different levels of resiliency in a single run. The goal is to design light-weight checkpoints to handle the most common failure modes and rely on more expensive checkpoints for less common, but more severe failures. While this approach is theoretically promising, it has not been fully evaluated in a large-scale, production system context. To this end we have designed a system, called the Scalable Checkpoint/Restart (SCR) library, that writes checkpoints to storage on the compute nodes utilizing RAM, Flash, or disk, in addition to the parallel file system. We present the performance and reliability properties of SCR as well as a probabilistic Markov model that predicts its performance on current and future systems. We show that multi-level checkpointing improves efficiency on existing large-scale systems and that this benefit increases as the system size grows. In particular, we developed low-cost checkpoint schemes that are 100x-1000x faster than the parallel file system and effective against 85% of our system failures. This leads to a gain in machine efficiency of up to 35%, and it reduces the the load on the parallel file system by a factor of two on current and future systems.

99 GENERAL AND MISCELLANEOUS↗

NW-MILO Acoustic Data Collection

There is an enduring requirement to improve our ability to detect potential threats and discriminate these from the legitimate commercial and recreational activity ongoing in the nearshore/littoral portion of the maritime domain. The Northwest Maritime Information and Littoral Operations (NW-MILO) Program at PNNL’s Coastal Security Institute in Sequim, Washington is establishing a methodology to detect and classify these threats - in part through developing a better understanding of acoustic signatures in a near-shore environment. The purpose of the acoustic data collection described here is to investigate the acoustic signatures of small vessels. The data is being recorded continuously, 24 hours a day, along with radar track data and imagery. The recording began in August 2008, and to date the data contains tens of thousands of signals from small vessels recorded in a variety of environmental conditions. The quantity and variety of this data collection, with the supporting imagery and radar track data, makes it particularly useful for the development of robust acoustic signature models and advanced algorithms for signal classification and information extraction. The underwater acoustic sensing system is part of a multi-modal sensing system that is operating near the mouth of Sequim Bay. Sequim Bay opens onto the Straight of Juan de Fuca, which contains part of the border between the U.S. and Canada. Table 1 lists the specific components used for the NW-MILO system. The acoustic sensor is a hydrophone permanently deployed at a mean depth of about 3 meters. In addition to a hydrophone, the other sensors in the system are a marine radar, an electro-optical (EO) camera and an infra-red (IR) camera. The radar is integrated with a vessel tracking system (VTS) that provides position, speed and heading information. The data from all the sensors is recorded and saved to a central server. The data has been validated in terms of its usability for characterizing the signatures of small vessels. The sampling rate of 8 kHz and low pass filtering to 2 kHz results in an alias-free signal in the frequency band that is appropriate for small vessels. Calibration was performed using a Lubell underwater speaker so that the raw data signal levels can be converted to sound pressure. Background noise is present due to a nearby pump and as a result of tidal currents. More study is needed to fully characterize the noise, but it does not pose an obstacle to using the acoustic data for the purposes of vessel detection and signature analysis. The detection range for a small vessel was estimated using the calibrated voltage response of the system and a cylindrical spreading model for transmission loss. The sound pressure of a typical vessel with an outboard motor was found to be around 140 dB mPa, and could theoretically be detected from 10 km away. In practical terms, a small vessel could reliably be detected from 3 - 5 km away. The data is archived in netCDF files, a standard scientific file format that is "self describing". This means that each data file contains the metadata - timestamps, units, origin, etc. - needed to make the data meaningful and portable. Other file formats, such as XML, are also supported. A visualization tool has been developed to view the acoustic data in the form of spectrograms, along with the coincident radar track data and camera images.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence P - Raw Data

Sequence P: Wake Flow Visualization, Upwind (P) This test sequence used an upwind, rigid turbine with a 0° cone angle. The wind speed ranged from 5 m/s to 15 m/s. Yaw angles of 0° to –60° were achieved. The blade tip pitch was 3°. The rotor rotated at 72 RPM. Blade and probe pressure measurements were collected. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to –99999.99 Nm. The teeter link load cell was pre-tensioned to 40,000 N. The aluminum blade tip designed to contain a smoke generator was installed, and counterweights were installed in the non-instrumented blade tip to compensate. The turbine was positioned at the appropriate yaw angle, and the smoke generator was ignited remotely. The campaign duration was 3 minutes for all tests except P1000000, which was 2 minutes. The file name convention was the standard format except for P10000A0, which indicated a 3° pitch angle. File P1000000 used a 12° pitch angle. After these two campaigns were collected, it was determined that all subsequent data should be collected with a 3° pitch angle. Pressure data were not acquired during this sequence, so all associated data values were flagged as not applicable by setting the measured values in the data file to 0.000 Pa. Corresponding pressure data are available from Sequence H for the 3° pitch angle test points. Flow visualization data obtained from wall- and ceiling-mounted video cameras were recorded to videotape. The camera locations and calibration procedures are described in Appendix J.

17 WIND ENERGY↗

Front-of-Meter Model Results

These files contains aggregations of key variables from the NREL Distributed Wind Futures Study using full parcel level data. These variables describe total technical and economic potential for distributed wind turbine deployment. Aggregations are available at the (1) county, (2) zipcode (zip code tabulation area or zcta), and (3) US Census block group level. Each scenario is coded with the scenario name (e.g., baseline) and year (e.g., 2022). Those files postfixed with 'econpot' contain results for only those parcels that are economically viable while the files postfixed with 'techpot' include results for all parcels that are technically feasible. Hence these correspond to technoeconomic and technical potential respectively. The data are available as CSV or Geopackage. Columns in the files are as follows: * geoid: geographic identifier (FIPS code or similar) * min_techpot_sum_kw: technical potential for all parcels in kW using turbines downsized to demand when appropriate * max_techpot_sum_kw: technical potential for all parcels in kW without downsizing turbines * aep_sum_kwh: annual energy production estimate in kWh * cf_mean_ratio: mean capacity factor * lcoe_mean_cents_per_kwh: mean levelized cost of energy for parcels in geography in cents per kWh * lcoe_std_cents_per_kwh: standard deviation of the above * parcel_area_sum_acres: total area of viable parcels in acres * n_turbines: number of cited turbines (one per viable parcel currently) Note: These are preliminary results from the full-parcel 2024 update of the Distributed Wind Energy Futures study. Please take care when making use of the data, and feel free to contact the team with any questions. Full documentation in support of these data is in progress and will follow.

17 WIND ENERGY↗

Behind-the-Meter Model Results

These files contains aggregations of key variables from the NREL Distributed Wind Futures Study using full parcel level data. These variables describe total technical and economic potential for distributed wind turbine deployment. Aggregations are available at the (1) county, (2) zipcode (zip code tabulation area or zcta), and (3) US Census block group level. Each scenario is coded with the scenario name (e.g., baseline) and year (e.g., 2022). Those files postfixed with 'econpot' contain results for only those parcels that are economically viable while the files postfixed with 'techpot' include results for all parcels that are technically feasible. Hence these correspond to technoeconomic and technical potential respectively. The data are available as CSV or Geopackage. Columns in the files are as follows: * geoid: geographic identifier (FIPS code or similar) * min_techpot_sum_kw: technical potential for all parcels in kW using turbines downsized to demand when appropriate * max_techpot_sum_kw: technical potential for all parcels in kW without downsizing turbines * aep_sum_kwh: annual energy production estimate in kWh * cf_mean_ratio: mean capacity factor * lcoe_mean_cents_per_kwh: mean levelized cost of energy for parcels in geography in cents per kWh * lcoe_std_cents_per_kwh: standard deviation of the above * parcel_area_sum_acres: total area of viable parcels in acres * n_turbines: number of cited turbines (one per viable parcel currently)

17 WIND ENERGY↗

Refine your search to explore more results.