Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “IDS”

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 523 records · Page 29

RH-TRU Waste Content Codes (RH-TRUCON) (Rev. 14)

The Remote-Handled Transuranic (RH-TRU) Content Codes (RH-TRUCON) document describes the inventory of RH-TRU waste within the transportation parameters specified by the Remote-Handled Transuranic Waste Authorized Methods for Payload Control (RH-TRAMPAC). The RH-TRAMPAC defines the allowable payload for the RH-TRU 72-B. This document is a catalog of RH-TRU 72-B authorized contents by site. A content code is defined by the following components: (1) a two-letter site abbreviation that designates the physical location of the generated/stored waste (e.g., ID for Idaho National Laboratory [INL]); and (2) a three-digit code that designates the physical and chemical form of the waste (e.g., content code 317 denotes TRU Metal Waste). For RH-TRU waste to be transported in the RH-TRU 72-B, the first number of this three-digit code is "3." The second and third numbers of the three-digit code describe the physical and chemical form of the waste. Content codes are further defined as subcodes by an alpha trailer after the three-digit code to allow segregation of wastes that differ in one or more parameters. Examples are as follows: (1) the alpha trailers of ID 322A and ID 322D differentiate waste packaging configurations; (2) the alpha trailers of OR 321F and OR 321G differentiate shipping periods for the same waste (i.e., 60 days versus 10 days); and (3) the alpha trailers of OR 321D and OR 321H differentiate generating sources and time periods from the same waste stream, resulting in different isotopic content. As detailed in the RH-TRAMPAC, compliance with flammable gas limits may be demonstrated through the evaluation of compliance with either a decay heat limit or flammable gas generation rate (FGGR) limit per container specified in approved content codes. As applicable, if a container meets the watt*year criteria specified by the RH-TRAMPAC, the decay heat limits based on the dose-dependent G value may be used as specified in an approved content code.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

RH-TRU Waste Content Codes (RH-TRUCON) (Rev. 15)

The Remote-Handled Transuranic (RH-TRU) Content Codes (RH-TRUCON) document describes the inventory of RH-TRU waste within the transportation parameters specified by the Remote-Handled Transuranic Waste Authorized Methods for Payload Control (RH-TRAMPAC). The RH-TRAMPAC defines the allowable payload for the RH-TRU 72-B. This document is a catalog of RH-TRU 72-B authorized contents by site. A content code is defined by the following components: (1) a two-letter site abbreviation that designates the physical location of the generated/stored waste (e.g., ID for Idaho National Laboratory [INL]); and (2) a three-digit code that designates the physical and chemical form of the waste (e.g., content code 317 denotes TRU Metal Waste). For RH-TRU waste to be transported in the RH-TRU 72-B, the first number of this three-digit code is "3." The second and third numbers of the three-digit code describe the physical and chemical form of the waste. Content codes are further defined as subcodes by an alpha trailer after the three-digit code to allow segregation of wastes that differ in one or more parameters. Examples are as follows: (1) the alpha trailers of ID 322A and ID 322D differentiate waste packaging configurations; (2) the alpha trailers of OR 321F and OR 321G differentiate shipping periods for the same waste (i.e., 60 days versus 10 days); and (3) the alpha trailers of OR 321D and OR 321H differentiate generating sources and time periods from the same waste stream, resulting in different isotopic content. As detailed in the RH-TRAMPAC, compliance with flammable gas limits may be demonstrated through the evaluation of compliance with either a decay heat limit or flammable gas generation rate (FGGR) limit per container specified in approved content codes. As applicable, if a container meets the watt*year criteria specified by the RH-TRAMPAC, the decay heat limits based on the dose-dependent G value may be used as specified in an approved content code.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

RH-TRU Waste Content Codes (RH-TRUCON) (Rev. 16)

The Remote-Handled Transuranic (RH-TRU) Content Codes (RH-TRUCON) document describes the inventory of RH-TRU waste within the transportation parameters specified by the Remote-Handled Transuranic Waste Authorized Methods for Payload Control (RH-TRAMPAC). The RH-TRAMPAC defines the allowable payload for the RH-TRU 72-B. This document is a catalog of RH-TRU 72-B authorized contents by site. A content code is defined by the following components: (1) a two-letter site abbreviation that designates the physical location of the generated/stored waste (e.g., ID for Idaho National Laboratory [INL]); and (2) a three-digit code that designates the physical and chemical form of the waste (e.g., content code 317 denotes TRU Metal Waste). For RH-TRU waste to be transported in the RH-TRU 72-B, the first number of this three-digit code is "3." The second and third numbers of the three-digit code describe the physical and chemical form of the waste. Content codes are further defined as subcodes by an alpha trailer after the three-digit code to allow segregation of wastes that differ in one or more parameters. Examples are as follows: (1) the alpha trailers of ID 322A and ID 322D differentiate waste packaging configurations; (2) the alpha trailers of OR 321F and OR 321G differentiate shipping periods for the same waste (i.e., 60 days versus 10 days); and (3) the alpha trailers of OR 321D and OR 321H differentiate generating sources and time periods from the same waste stream, resulting in different isotopic content. As detailed in the RH-TRAMPAC, compliance with flammable gas limits may be demonstrated through the evaluation of compliance with either a decay heat limit or flammable gas generation rate (FGGR) limit per container specified in approved content codes. As applicable, if a container meets the watt*year criteria specified by the RH-TRAMPAC, the decay heat limits based on the dose-dependent G value may be used as specified in an approved content code.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Impacts of Biofuel Blending on MCCI Ignition Delay with Review of Methods for Defining Cycle-by-Cycle Ignition Points from Noisy Cylinder Pressure Data

Conventional diesel combustion, also known as Mixing-Controlled Compression Ignition (MCCI), is expected to be the primary power source for medium- and heavy-duty vehicles for decades to come. Displacing petroleum-based ultra-low-sulfur diesel (ULSD) as much as possible with low-net-carbon biofuels will become necessary to help mitigate effects on climate change. Neat biofuels may have difficulty meeting current diesel fuel standards but blends of 30% biofuel in ULSD show potential as ‘drop-in’ fuels. These blends must not make significant changes to the combustion phasing of the MCCI process if they are to be used interchangeably with neat ULSD. An important aspect of MCCI phasing is the ignition delay (ID), i.e. the time between the start of fuel injection and the initial premixed autoignition that initiates the MCCI process. Bench experiments can evaluate the expected ignition delay of a fuel via cetane number (CN) or alternative methods such as the indicated cetane number (ICN); however, neither CN nor ICN correlate perfectly with the ignition delay measured in actual engine experiments. Furthermore, there is no standardized methodology on how to quantify MCCI ignition delay from engine cylinder pressure measurements, creating difficulties in cross-study comparison. In this study, several engine ignition delay calculation methods are evaluated for robustness in deriving ignition delay on both a cycle-averaged and cycle-to-cycle basis. Eight biofuel blends with varying ICN, oxygen concentration and other fuel properties were used to study the different methods. This yields a thorough analysis of how certain biofuel blends affect ignition delay and the entire MCCI process, as well as a thorough evaluation of the differences between the ID calculation methods. Many of these methods are equally valid, but the choice of method has a significant impact on the resulting ID, which must be carefully considered when evaluating results across multiple studies.

47 OTHER INSTRUMENTATION↗

HarDWR - Cumulative Water Rights Curves

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. This product is the dataset used as input to the WBM model (Grogan et al., in review; Grogan et al. 2022), and is the result of the step creating cumulative water rights curves described in Lisk et al. (submission pending). This database contains 1,744 individual .csv files, two for each Water Management Area (WMA; see here) in the 11-state region. File naming convention: WMA_[###]_[X]W.csv, where [###] is the unique identifier for each WMA, and [X] is either S for surface water rights, or G for groundwater rights. Column headers in each file: Year: the priority date year CUML: the total cumulative water rights allocated up to this priority date year (ft3s-1) Irrigation: The percent of cumulative water rights allocated to the Irrigation category up to this priority date year (%) Domestic: The percent of cumulative water rights allocated to the Domestic category up to this priority date year (%) Livestock: The percent of cumulative water rights allocated to the Livestock category up to this priority date year (%) Fish: The percent of cumulative water rights allocated to the Fish category up to this priority date year (%) Industrial: The percent of cumulative water rights allocated to the Industrial category up to this priority date year (%) Environmental: The percent of cumulative water rights allocated to the Environmental category up to this priority date year (%) Other: The percent of cumulative water rights allocated to the Other category up to this priority date year (%) In addition to the database files, there is a companion .csv file, called stateWMAs_ID.csv. The main purpose of this file is to provide the means of translating between the ### unique identifier and the various other id of the WMA the file is attached to. This translation file has five columns, which are: basinNum: The official state given alpha-numeric identifier of the WMA basinName: the state provided English name of the area, where applicable state: the state name uniID: a unique identifier we created by concatenating the state name, and underscore, and the state numerical ID ID: a unique numeric identifier we created as a requirement for the files to be used within WBM (Grogan et al., in review)

Economics↗

Model run output for WM-ABM 2024 HESS Publication

Model output for computational experiments introducing WM-ABM. See associated HESS publication here: https://egusphere.copernicus.org/preprints/2023/egusphere-2023-1604/ all_nldas_cdl_data_v3.txt - Cropland Data Layer data aggregated to 1/8 degree resolution for input into the PMP calibration process. Variables include NLDAS ID, crop type, year, the count of pixels in the grid cell of the crop type, CDL crop ID, and GCAM crop ID. 20230115 ABM runs - WM-ABM model outputs for various scenarios described in HESS publication. If multiple versions exist (e.g., v2, v3, etc.) latest version indicates dataset generated for manuscript. The "baseline" run is the primary run, where as the "memXX" runs indicate sensitivity runs testing different parameters of agent memory. Output files starting with "abm_results_" include groundwater irrigated acres and surface water irrigated acres for each farm/agent combination. Other CSV outputs provide summary statistics of various agent and water shortage outcomes, used for generation of figures in the HESS manuscript.

ABM↗

HarDWR - Cumulative Water Rights Curves

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. This product is the dataset used as input to the WBM model (Grogan et al., in review; Grogan et al. 2022), and is the result of the step creating cumulative water rights curves described in Lisk et al. (submission pending). This database contains 1,744 individual .csv files, two for each Water Management Area (WMA; see here) in the 11-state region. File naming convention: WMA_[###]_[X]W.csv, where [###] is the unique identifier for each WMA, and [X] is either S for surface water rights, or G for groundwater rights. Column headers in each file: Year: the priority date year CUML: the total cumulative water rights allocated up to this priority date year (ft3s-1) Irrigation: The percent of cumulative water rights allocated to the Irrigation category up to this priority date year (%) Domestic: The percent of cumulative water rights allocated to the Domestic category up to this priority date year (%) Livestock: The percent of cumulative water rights allocated to the Livestock category up to this priority date year (%) Fish: The percent of cumulative water rights allocated to the Fish category up to this priority date year (%) Industrial: The percent of cumulative water rights allocated to the Industrial category up to this priority date year (%) Environmental: The percent of cumulative water rights allocated to the Environmental category up to this priority date year (%) Other: The percent of cumulative water rights allocated to the Other category up to this priority date year (%) In addition to the database files, there is a companion .csv file, called stateWMAs_ID.csv. The main purpose of this file is to provide the means of translating between the ### unique identifier and the various other id of the WMA the file is attached to. This translation file has five columns, which are: basinNum: The official state given alpha-numeric identifier of the WMA basinName: the state provided English name of the area, where applicable state: the state name uniID: a unique identifier we created by concatenating the state name, and underscore, and the state numerical ID ID: a unique numeric identifier we created as a requirement for the files to be used within WBM (Grogan et al., in review) The code related to the creation of this dataset can be viewed within HarDWR GitHub Repository/dataCumulationCurves.

Economics↗

HarDWR - Harmonized Water Rights Records

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. Here we present a new dataset of western U.S. water rights records. This dataset provides consistent unique identifiers for each spatial unit of water management across the domain, unique identifiers for each water right record, and a consistent categorization scheme that puts each water right record into one of 7 broad use categories. These data were instrumental in conducting a study of the multi-sector dynamics of intersectoral water allocation changes through water markets (Grogan et al., in review). Specifically, the data were formatted for use as input to a process-based hydrologic model, WBM, with a water rights module (Grogan et al., in review). While this specific study motivated the development of the database presented here, U.S. west water management is a rich area of study (e.g., Anderson and Woosly, 2005; Tidwell, 2014; Null and Prudencio, 2016; Carney et al, 2021) so releasing this database publicly with documentation and usage notes will enable other researchers to do further work on water management in the U.S. west. The raw downloaded data for each state is described in Lisk et al. (in review), as well as here. The dataset is a series of various files organized by state sub-directories. The first two characters of each file name is the abbreviation for the state the in which the file contains data for. After the abbreviation is the text which describes the contents of the file. Here is each file type described in detail: XXFullHarmonizedRights.csv: A file of the combined groundwater and surface water records for each state. Essentially, this file is the merging of XXGroundwaterHarmonizedRights.csv and XXSurfaceWaterHarmonizedRights.csv by state. The column headers for each of this type of file are: state - The name of the state the data comes from. FIPS - The two-digit numeric state ID code. waterRightID - The unique identifying ID of the water right, the same identifier as its state uses. priorityDate - The priority date associated with the right. origWaterUse - The original stated water use(s) from the state. waterUse - The water use category under the unified use categories established here. source - Whether the right is for surface water or groundwater. basinNum - The alpha-numeric identifier of the WMA the record belongs to. CFS - The maximum flow of the allocation in cubic feet per second (ft3s-1). Arizona is unique among the states, as its surface and groundwater resources are managed with two different sets of boundaries. So, for Arizona, the basinNum column is missing and instead there are two columns: surBasinNum - The alpha-numeric identifier of the surface water WMA the record belongs to. grdBasinNum - The alpha-numeric identifier of the groundwater WMA the record belongs to. XXStatePOD.shp: A shapefile which identifies the location of the Points of Diversion for the state's water rights. It should be noted that not all water right records in XXFullHarmonizedRights.csv have coordinates, and therefore may be missing from this file. XXStatePOU.shp: A shapefile which contains the area(s) in which each water right is claimed to be used. Currently, only Idaho and Washington provided valid data to include within this file. XXGroundwaterHarmonizedRights.csv: A file which contains only harmonized groundwater rights collected from each state. See XXFullHarmonizedRights.csv for more details on how the data is formatted. XXSurfaceWaterHarmonizedRights.csv: A file which contains only harmonized surface water rights collected from each state. See XXFullHarmonizedRights.csv for more details on how the data is formatted. Additionally, one file, stateWMALabels.csv, is not stored within a sub-directory. While we have referred to the spatial boundaries that each state uses to manage its water resources as WMAs, this term is not shared across all states. This file lists the proper name for each boundary set, by state. For those whom may be interested in exploring our code more in depth, we are also making available an internal data file for convenience. The file is in .RData format and contains everything described above as well as some minor additional objects used within the code calculating the cumulative curves. For completeness, here is a detailed description of the various objects which can be found within the .RData file: states: A character vector containing the state names for those states in which data was collected for. More importantly, the index of the state name is also the index in which that state's data can be found in the various following list objects. For example, if California is the third index in this object, the data for California will also be in the third index for each accompanying list. rightsByState_ground: A list of data frames with the cleaned ground water rights collected from each state. This object holds the the data that is exported to created the xxGroundwaterHarmonizedRights.csv files. rightsByState_surface: A list of data frames with the cleaned surface water rights collected from each state. This object holds the the data that is exported to created the xxSurfaceWaterHarmonizedRights.csv files. fullRightsRecs: A list of the combined groundwater and surface water records for each state. This object holds the the data that is exported to created the xxFullHarmonizedRights.csv files. projProj: The spatial projection used for map creation in the beginning of the project. Specifically, the World Geodetic System (WGS84) as a coordinate reference system (CRS) string in PROJ.4 format. wmaStateLabel: The name and/or abbreviation for what each state legally calls their WMAs. h2oUseByState: A list of spatial polygon data frames which contain the area(s) in which each water right is claimed to be used. It should be noted that not all water right records have a listed area(s) of use in this object. Currently, only Idaho and Washington provided valid data to be included in this object. h2oDivByState: A list of spatial points data frames which identifies the location of the Point of Diversion for the state's water rights. It should be noted that not all water right records have a listed Point of Diversion in this object. spatialWMAByState: A list of spatial polygon data frames which contain the spatial WMA boundaries for each state. The only data contained within the table are identifiers for each polygon. It is worth reiterating that Arizona is the only state in which the surface and groundwater WMA boundaries are not the same. wmaIDByState: A list which contains the unique ID values of the WMAs for each state. plottingDim: A character vector used to inform mapping functions for internal map making. Each state is classified as either "tall" or "wide", to maximize space on a typical 8x11 page. The code related to the creation of this dataset can be viewed within HarDWR GitHub Repository/dataHarmonization.

Economics↗

Key elements in building a successful photocomposition applications program

TEXTCOMP, a photocomposition applications program developed by the Technical Information and Documentation Division of the Jet Propulsion Laboratory using the Comp-2 language of Alphanumeric Publication Systems, is described. In Comp-2, each unique block of information such as a paragraph, centered heading, or side heading is termed a 'record'. All commands required for typesetting a record are grouped and identified by a record ID. Once the basic ground rules for typesetting are put into effect by a record ID, changes can be made in texts by means of in-text codes designed to access special characters or perform special operations. The approach used in the design of record ID's and in-text codes for TEXTCOMP to produce a code set structured for maximum usability by non-computer oriented personnel is discussed.

Korbuly, D. K.↗

NSSDC data listing

The National Space Science Data Center (NSSDC) Data Listing is in an abbreviated form compared to the data catalogs normally published by NSSDC/WDC-A-R&S. It is organized by NSSDC spacecraft common name. The launch date and NSSDC ID are printed for each spacecraft. The experiments are listed alphabetically by the principal investigator's name and NSSDC ID are printed for each experiment. The data sets are listed by NSSDC ID following the experiment name. The data set name, data form code, quantity of data, and the time span of the data as verified by NSSDC are printed for each data set. Information on NSSDC facilities and ordering procedures are included.

Source record↗

NSSDC Data listing

A convenient reference to space science and supportive data available from the National Space Science Data Center (NSSDC) is provided. Satellite data are organized by NSSDC spacecraft common name. The launch date and NSSDC ID are given. Experiments are listed alphabetically by the principal investigator or team leader. The experiment name and NSSDC ID, data set ID, data set name, data form code, quantity of data, and the time span of the data as verified by NSSDC are shown. Ground-based data, models, computer routines, and composite spacecraft data that are available from NSSDC are listed alphabetically by discipline, source, data type, data content, and data set. The data set name, data form code, quantity of data, and the time span covered where appropriate are included.

Source record↗

Field experience with various slicing methods

Wafer slicing using internal diameter (ID) saw, multiblade slurry (MBS) saw and multiwire slurry (MWS) saw techniques were evaluated. Wafer parameters such as bow, taper, and roughness which may not be important factors for solar cell fabrication, were considerably better for ID saw than those of the MBS and MWS saw. Analysis of add-on slicing cost indicated that machine productivity seems to be a major limiting factor for ID saw, while expendible material costs are a major factor for both MBS and MWS saw. Slicing experience indicated that the most important factors controling final wafer cost are: (1) silicon cost (wafer thickness + kerf loss); (2) add-on slicing cost, and (3) mechanical yield. There is a very strong interaction between these parameters, suggesting a necessity of optimization of these parameters.

Yoo, H. I.↗

NSSDC data listing

The first part of this listing, Satellite Data, is in an abbreviated form compared to the data catalogs published by NSSDC. It is organized by NSSDC spacecraft common name. The launch date and NSSDC ID are printed for each spacecraft. The experiments are listed alphabetically by the principal investigator's or team leader's last name following the spacecraft name. The experiment name and NSSDC ID are printed for each experiment. The data sets are listed by NSSDC ID following the experiment name. The data set name, data form code, quantity of data, and the time span of the data as verified by NSSDC are printed for each data set.

Source record↗

Silicon slicing by fixed abrasive slicing technique

One of the major cost factors in silicon ingot technology adaptation for terrestrial photovoltaic application is in slicing boules into wafers. The most developed industrial practice is the Internal Diameter (ID) slicing. This method utilizes diamond cutting. The diamond stands up for long periods, hence, the cost of expendable materials is low. However, the ID technology as practiced today has poor material utilization. The Multiblade Slurry (MBS) method has low equipment and labor costs but its expendable material costs are high. Recently Multiwire Slurry (MWS) technology has shown very good material utilization, but its expendable material costs are even higher than MBS. The multiwire Fixed Abrasive Slicing Technique (FAST) still in advanced development stage, combines the low expendable material costs of ID method, the low labor and equipment costs of MBS and high material utilization of MWS.

Schmid, F.↗

Intensity dependent spread theory

The Intensity Dependent Spread (IDS) procedure is an image-processing technique based on a model of the processing which occurs in the human visual system. IDS processing is relevant to many aspects of machine vision and image processing. For quantum limited images, it produces an ideal trade-off between spatial resolution and noise averaging, performs edge enhancement thus requiring only mean-crossing detection for the subsequent extraction of scene edges, and yields edge responses whose amplitudes are independent of scene illumination, depending only upon the ratio of the reflectance on the two sides of the edge. These properties suggest that the IDS process may provide significant bandwidth reduction while losing only minimal scene information when used as a preprocessor at or near the image plane.

Holben, Richard↗

Formulation and verification of frequency response system identification techniques for large space structures

For the past several years much effort has been given to the development of techniques for designing control systems for large space structures (LSS's). The main objective of these efforts has been to develop a LSS control methodology that produces designs that meet strenuous performance requirements and are robust to model inaccuracies. Unfortunately, performance and robustness are conflicting requirements. Because LSS's can not be fully tested on ground, it has become an accepted fact that the design of LSS control systems to meet performance requirements can not be completed until the LSS is placed on-orbit and tested and an accurate model is extracted from on-orbit test results. Modern MIMO sampled-data frequency response design techniques are viable candidates for designing LSS control systems. First, this paper presents techniques for performing MIMO system identification (ID) from test data. Then, techniques for improving the performance of the system ID process in the presence of noise are presented. Finally, practical utility of the system ID approaches are validated by the presentation of results obtained from application on the LSS Ground Test Facility at Marshall Space Flight Center.

Mitchell, Jerrel R.↗

STS-102 Mission Highlight Resource Tape, Tape 2 of 4

A continuation of 'STS-102 Mission Highlight Resource Tape, Part 1 of 2, Tape 1 of 2' (internal ID 2001096942), this video shows highlights from flight day five of STS-102, including the deployment of the Space Shuttle's Robotic Arm and the opening of the hatch between the Unity Module and Leonard Multipurpose Logistics Module by Expedition 1 Commander Bill Shepherd. The activities of flight days 6-14 can be seen on 'STS-102 Mission Highlight Resource Tape, Part 2 of 2, Tape 1 of 2' (internal ID 2001096943) and 'STS-102 Mission Highlight Resource Tape, Part 2 of 2, Tape 2 of 2' (internal ID 2001096940).

Source record↗

STS-102 Mission Highlight Resource Tape, Tape 4 of 4

A continuation of 'STS-102 Mission Highlight Resource Tape, Part 1 of 2, Tape 1 of 2' (internal ID 2001096942), 'STS-102 Mission Highlight Resource Tape, Part 1 of 2, Tape 2 of 2' (internal ID 2001096941), and 'STS-102 Mission Highlight Resource Tape, Part 2 of 2, Tape 1 of 2' (internal ID 2001096943), this video shows the activities of flight days 13 and 14 of the STS-102 mission. The landing of the Discovery orbiter is seen from several viewpoints, and the crew of STS-102 (Commander James Wetherbee, Pilot James Kelly, and Mission Specialists Andrew Thomas and Paul Richards) and the Expedition 1 crew (William Shepherd, Yuri Gidzenko, and Sergei Krikalev) are seen as they disembark from Discovery.

Source record↗