Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “objective”

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 541 records · Page 30
All sourcesNASA NTRSDOE OSTI
DOE OSTI2023

Multi-objective, robust constraints enforced global topology optimizer for optical devices

A method for optimization of photonic devices is disclosed. The method includes receiving a set of unconstrained latent variables; mapping the set of unconstrained latent variables to a constrained space to generate a constrained device; calculating the permittivity across each element of the constrained device; determining a permittivity-constrained width gradient based at least partially on the permittivity across each element; and optimizing the set of unconstrained latent variables by at least partially using the permittivity-constrained width gradient.

Fan, Jonathan↗
DOE OSTI2024

VPP Participation Models: What is the Objective?

Virtual power plants (VPPs) can provide grid services by aggregating and controlling many distributed energy resources. However, their design, operation, level of participation, and outcomes depend on the regulatory and market environments they operate in, DER owner preferences, grid service value, and technical capabilities (e.g., communications, forecasting, controls, user interfaces). Although VPPs are inherently complex, they could enable high shares of behind-the-meter solar plus storage and reduce the cost of electrifying, e.g., personal vehicles and space heating.

demand response↗
DOE OSTI2024

Molten Salt Reactor Safety Assessment - Three Approaches to A Common Objective

Safety adequacy assessment is central to nuclear power plant (NPP) licensing. Either NPP accident mitigation or prevention can result in adequate safety. Accident prevention, along with the the prevention of accident escalation, can be evaluated using either deterministic or probabilistic methods. Acceptable means to develop principal design criteria (PDCs) via probabilistic methods are provided in NRC Regulatory Guide 1.233 while advanced reactor design criteria are provided in NRC Regulatory Guide 1.232 (RG 1.232). Accident mitigation-based regulatory guidance for non-power reactors is provided in NUREG 1537. While RG 1.232 included class specific guidance for both sodium-cooled fast reactors and modular high-temperature gas-cooled reactors, it did not provide molten salt reactor (MSR) class specific guidance. Class specific design criteria more closely align with reactors in their class so will require less effort to employ to develop design specific PDCs. The American Nuclear Society has recently released a liquid-fueled MSR design safety standard (ANSI/ANS-20.2-2023) that provides class specific design criteria.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
DOE OSTI2020

HarDWR - Cumulative Water Rights Curves

A dataset within the Harmonized Database of Western U.S. Water Rights (HarDWR). For a detailed description of the database, please see the meta-record v2.0. Changelog v2.0 - Recalculated based on Harmonized Water Rights Records v2.0 sourced from WestDAAT - Added "Unspecified" was a water source category, and files associated with this category v1.01 - Updated the names of each file with an ID number less than 3 digits to include leading 0s v1.0 - Initial public release Description This product an updated version of the database 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. (2024). This database contains 2,667 individual .csv files, three for each Water Management Area (WMA) in the 11-state region. File Naming WMA_[###]_[X]W.csv, where [###] is the unique identifier for each WMA, and [X] is either "S" for surface water rights, "G" for groundwater rights, or "U" for unspecified. 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) 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 the study region. 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 second index in this object, the data for California will also be in the second index for each accompanying list. wmasRightsPersGrd: A list of nested lists of data frames. Each state has one entry in the top level list and consist of a list with one data frame per WMA. The data frames in this object are the same as the above described .csv files, specifically for groundwater. wmasRightsPersSur: A list of nested lists of data frames. Each state has one entry in the top level list and consist of a list with one data frame per WMA. The data frames in this object are the same as the above described .csv files, specifically for surface water. wmasRightsPersUnsp: A list of nested lists of data frames. Each state has one entry in the top level list and consist of a list with one data frame per WMA. The data frames in this object are the same as the above described .csv files, specifically for water from an unspecified source. wmasRightsTotsGrd: A list of nested lists of data frames. Each state has one entry in the top level list and consist of a list with one data frame per WMA. The values in the data frames of this object would be the equivalent to multiplying the CUML column by the sector percentage columns to create the sector total ft3s-1, specifically for groundwater. This object is provided for convenience to check out original total values, if desired. wmasRightsTotsSur: A list of nested lists of data frames. Each state has one entry in the top level list and consist of a list with one data frame per WMA. The values in the data frames of this object would be the equivalent to multiplying the CUML column by the sector percentage columns to create the sector total ft3s-1, specifically for surface water. This object is provided for convenience to check out original total values, if desired. wmasRightsTotsUnsp: A list of nested lists of data frames. Each state has one entry in the top level list and consist of a list with one data frame per WMA. The values in the data frames of this object would be the equivalent to multiplying the CUML column by the sector percentage columns to create the sector total ft3s-1, specifically for water from an unspecified source. This object is provided for convenience to check out original total values, if desired. wmaIDByState: A list of data frames which contain the by state allocation by WMA matrix. There is a matrix for each state in a different data frame within the object.

Economics↗
DOE OSTI2022

3DBFSVBF (3D BatFinder Smart Video BioFilter and Multi-class BatFinder Smart Video BioFilter) [SWR-22-88]

Bats are notoriously difficult to study, therefore, identifying specific behavioral trends and the precise environmental conditions at the time of collision requires a monitoring solution that can reliably collect relevant data. To date, thermal infrared video surveillance has been extensively applied to study bats and has proven to be a powerful yet cumbersome tool. Current analytical approaches are time consuming because data processing data has not been fully automated. In the past, steps have been taken to record avian and bat activity in conjunction with complicated image processing techniques that separate species from other moving objects within the field of view (i.e. clouds and portions of the wind turbine). Once the videos are collected, the post-processing does not allow real time monitoring and identification, leading to a delay in both studying the behavior of these species and determining the effectiveness of any impact reduction strategy being studied. Moreover, object identification capability is lacking, thus limiting the usefulness of video data. To resolve these issues, we are using open source 3D computer vision and machine learning techniques allowing for automatic detection of objects in real-time with the ability to correlate these objects with environmental variables and recording the flight paths of each object. The machine learning has been trained on 3D data and allows for automated real-time data collection, identification and tracking, thereby eliminating the need for long and tedious post-analysis processing of the videos. This machine learning model is an added feature to the previous BatFinder Smart Video BioFilter and increases the accuracy of that systems classification by increasing the accuracy of identifying bats (90% accuracy) and insects (69% accuracy) to a 97% accuracy. There are two object classifier machine learning models, Binary and multi-classification. Binary object classifier labeled BatFinder_Smart_Video_BioFilter.h5 distinguishes between biological objects and non-biological objects. The main goal of this object classifier is to ignore the turbine blades while detecting biological object flying withing the rotor swept area of the turbine. Non-biological objects have a probability of 0 and biological objects have a probability of 1. Multi-classifier labeled Multiclass_BatFinder_Smart_Video_BioFilter.h5 distinguishes between bats, birds, insects and non-biological.

Yarbrough, John↗
DOE OSTI2020

Vision-Guided Automation and Assistance

Robotic automation and assistance is an excellent way to increase efficiency and safety when working in a potentially hazardous workspace. However, many traditional automation approaches rely on the precise placement of items to be manipulated. The scope of such automated tasks is also limited to the manipulation of one type of object since there is no way to distinguish between different objects. The addition of a vision pipeline, where robot vision is used to localize and recognize objects, can allow the robot to perform more complex tasks in a variable workspace. In my vision pipeline, a depth camera is used to generate a 3D point cloud of the workspace. Objects to be manipulated are isolated in the point cloud by filtering out shared surfaces and using Euclidean cluster extraction to group clusters of points. The locations of the objects are then estimated from the point cloud of the isolated objects. The localization of objects with robot vision allows for variable workspaces, reducing the overhead associated with requiring all objects to be precisely placed in the workspace. For object recognition, deep learning is used to train a neural network that classifies objects from the raw point clouds. More complex tasks that require multiple objects to be manipulated differently can be achieved through the vision pipeline. Through its ability to visualize the workspace, robot vision greatly improves efficiency and safety of automated and assistive tasks.

42 ENGINEERING↗
DOE OSTI2023

Asteroids seen by JWST-MIRI: Radiometric size, distance, and orbit constraints

Infrared measurements of asteroids are crucial for the determination of physical and thermal properties of individual objects, and for understanding the small-body populations in the solar system as a whole. However, standard radiometric methods can only be applied if the orbit of an object is known, hence its position at the time of the observation. With JWST-MIRI observations the situation will change and many unknown, often very small, solar system objects will be detected. Later orbit determinations are difficult due to the faintness of the objects and the lack of dedicated follow-up concepts. We present MIRI observations of the outer-belt asteroid (10920) 1998 BC1 and an unknown object, detected in all nine MIRI bands in close apparent proximity to (10920). We developed a new method called STM-ORBIT to interpret the multi-band measurements without knowing the object’s true location. The power of the new technique is that it determines the most-likely heliocentric and observer-centric distance and phase angle ranges, allowing us to make a radiometric size estimate. The application to the MIRI fluxes of (10920) was used to validate the method. It leads to a confirmation of the known radiometric size-albedo solution, and puts constraints on the asteroid’s location and orbit in agreement with its true orbit. To back up the validation of the method, we obtained additional ground-based light curve observations of (10920), combined with Gaia data, which indicate a very elongated object (a/b ≥ 1.5), with a spin-pole at (λ, β) ecl = (178°, +81°), with an estimated error of about 20°, and a rotation period of 4.861191 ± 0.000015 h. A thermophysical study of all available JWST-MIRI and WISE measurements leads to a size of 14.5–16.5 km (diameter of an equal-volume sphere), a geometric albedo pV between 0.05 and 0.10, and a thermal inertia in the range 9–35 (best value 15) J m -2 s -0.5 K -1 . For the newly discovered MIRI object, the STM-ORBIT method revealed a size of 100–230 m. The new asteroid must be on a low-inclination orbit (0.7° < i < 2.0°) and it was located in the inner main-belt region during JWST observations. A beaming parameter η larger than 1.0 would push the size even below 100 meters, a main-belt regime that has escaped IR detections so far. This kind of MIRI observations can therefore contribute to formation and evolution studies via classical size-frequency studies, which are currently limited to objects larger than about one kilometer in size. We estimate that MIRI frames with pointings close to the ecliptic and short integration times of only a few seconds will always include a few asteroids; most of them will be unknown objects.

79 ASTRONOMY AND ASTROPHYSICS↗
DOE OSTI2024

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↗
DOE OSTI2023

Serial Moire scanning phase contrast x-ray imaging

Method include emitting x-rays from an x-ray source, directing a first portion of the x-rays through an object grating situated adjacent to an object while the object is scanned relative to the object grating along a scan direction, directing a second portion of the x-rays through the object and subsequently through a detector grating without transmitting through the object grating, wherein the object grating and detector grating are adjacently arranged in a field of view of the x-rays sequentially with respect to each other in the scan direction, and receiving the first portion transmitted through the object and object grating with a first portion of a detector and receiving the second portion transmitted through the object and the detector grating with a second portion of the detector adjacent to the first portion of the detector. Systems are also disclosed, along with related techniques for beam hardening correction.

Miller, Erin A.↗