Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “light-duty”

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 181 records · Page 10

DOE EV Data Collection - Charging Data

Charging data are collected from one of three sources, each with varying levels of additional information. These sources, in approximate order from most to least additional information, are: • The electric vehicle supply equipment (charger) • Onboard the vehicle itself • From a utility submeter. Many chargers provide software that allows for the collection and reporting of charging session data. If unavailable, data may be recorded by the charging vehicle’s onboard systems. If neither of these options is available, data can be acquired from utility submeters that simply track the energy flowing to one or more chargers. Data collected directly from the electric vehicle supply equipment (EVSE) are typically the most accurate and highest frequency. However, it is not always possible to discern which exact vehicle is being charged during any one session. EVSE-side data can be identified where a single charger ID but a range of vehicle IDs are present (e.g., CH001, EV001-EV005). Data collected from the vehicle’s onboard systems usually does not provide information on which exact charger is being used. Vehicle-side data can be identified where a single Vehicle ID but a range of Charger IDs are present (e.g., EV001, CH001-CH005). Data collected from utility submeters provide no information on which specific vehicle is charging or which specific charger is in use. Submeter data can be identified where multiple Vehicle IDs and multiple Charger IDs are present, but only a single Fleet ID is present (e.g., EV001-EV005, CH001-CH005, Fleet01). The **Charge Data Daily/Session Dictionaries** contains definitions for each available parameter collected as part of an individual charging session, aggregated at either a daily or session level. The parameters available will vary between vehicles and chargers. The **Charger Attributes** table contains specific charger characteristics, coded to at least one anonymous Charger ID and linked to either a single or a range of Vehicle IDs. Vehicle ID can be used as a key between charging data and vehicle attribute tables. The **Charger Attributes Data Dictionary** contains definitions for each available parameter collected on the physical and operational characteristics of the charging hardware itself. The **Vehicle Attributes Data Dictionary** contains definitions for each available parameter associated with a vehicle’s physical and functional attributes and fleet context. The **Vehicle Attributes** table contains specific vehicle characteristics, coded to an anonymous Vehicle ID. This Vehicle ID can be used as a key between vehicle data and vehicle attribute tables, and in cases where charging data are supplied, links a vehicle with the charger(s) that supplied it power. The **Charging Data** tables contain the data from each charger’s operations, coded to at least one anonymous Charger ID and linked to either a single or a range of Vehicle IDs. Vehicle ID can be used as a key between charging data and vehicle attribute tables. Data is being uploaded quarterly through 2023 and subject to change until the conclusion of the project.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

DOE EV Data Collection - Facility Data

Facility data includes information on electricity consumption by larger-scale infrastructure, including buildings, solar arrays, and energy storage systems. Parameter definitions can be found in the data dictionary. If a connection between specific vehicle information and facility data exists, it will be available in the vehicle attributes table. Vehicle ID can be used as a key between vehicle data and vehicle attribute tables. Data is being uploaded quarterly through 2023 and subject to change until the conclusion of the project.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Raw Lidar and Camera Data Synchronized with Precipitation and Present Weather Data

As part of the sensor characterization task of the SMART 2.0 project, this dataset includes raw data from three spinning lidars ([Ouster OS2-128](https://ouster.com/products/scanning-lidar/os2-sensor/), [Velodyne Puck (VLP-16)](https://velodynelidar.com/products/puck/), and [Velodyne Ultra Puck (VLP-32)](https://velodynelidar.com/products/ultra-puck/)), one camera ([Mako G-319](https://www.alliedvision.com/en/camera-selector/detail/mako/g-319/)), and one present weather sensor ([Vaisala FD-70](https://www.vaisala.com/en/products/weather-environmental-sensors/forward-scatter-fd70)). All data were synchronized, with the log start time indicated in the file name (HHMMSS). The data can be filtered by date, log time (HHMMSS), sensor, frame ID, and weather classification. These data were gathered statically at the Argonne Testbed for Multiscale Observational Science (ATMOS). Two target stop signs were placed in view of the sensors to contribute a target for comparing sensor data under different conditions. The weather data for each day are stored in netCDF “.nc” files. The lidar data contain the X, Y, Z, intensity, reflectivity, and ring from Ouster OS2-128 rev6, Velodyne VLP-16, and Velodyne VLP-32 lidars. ![raw lidar image](LiDAR_pointcloud_ATMOS.png)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Individual Motorist Data - Ohio EV Ownership Trends

The individual motorist dataset contains data and analysis of consumer electric vehicle (EV) ownership trends in rural Appalachian Ohio in comparison with statewide trends. The data span four years, from Q1 2020 to Q2 2023 (partial). They are sourced from the Ohio Bureau of Motor Vehicles registration records and contain detail on drivetrain type (battery-electric vehicle [BEV] or plug-in hybrid electric vehicle [PHEV]); specific vehicle make and model; and registration location at county, city, and ZIP code levels of spatial resolution. Registration data are analyzed at the county level against such indicators as median income, poverty status, urban-rural status, and density of public charging infrastructure. In addition to tabular data, a GIS shapefile with many analysis fields joined is included.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Raw_data_Batch_I: Argonne to Shorewood via I-55

Date of collection: May 12, 2023 Location: Interstate 55, DuPage County, IL This data set contains lidar and vision data collected along a round trip between I-55 Exit 273A and Exit 253. The data contains the following Robot Operating System (ROS) topics: - /Central_Camera_blurred – Image flow from coaxial camera heading, vehicle front. - /Left_Camera_blurred – Image flow from left camera, 60° from central camera on the left side. - /Right_Camera_blurred – Image flow from right camera, 60° from central camera on the right side. - /camera0/camera_info – Intrinsic and distortion information of left camera. - /camera0/projection_matrix – Extrinsic matrix of left camera from lidar. - /camera2/camera_info – Intrinsic and distortion information of central camera. - /camera2/projection_matrix – Extrinsic matrix of central camera from lidar. - /camera5/camera_info – Intrinsic and distortion information of right camera. - /camera5/projection_matrix – Extrinsic matrix of right camera from lidar. - /novatel/oem7/bestpos – Latitude, longitude, and elevation information from NovAtel GNSS-INS system. - /points_raw – VLP-32 lidar point cloud. - /tf – Vehicle base frame. The data are organized into a data description file and one or more ROS .bag files, dependent on original file size. The data description file provides information about the data collection date, location, and detailed mapping, while the .bag file(s) contain the actual data. Please note that for the purpose of securing personally identifiable information, all license plates and faces included in this publication have been intentionally blurred during real-time processing. ![argonne shorewood image](argone-shorewood.png)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Raw_data_Batch_I: Ashland Avenue

Date of collection: May 26, 2023 Location: Ashland Avenue, Chicago, IL This data set contains lidar and vision data collected along Ashland Avenue. A south-to-north run starts from the intersection of Irving Park and Ashland and ends at Andersonville Garden. A north-to-south run starts from Andersonville Garden and ends around the intersection of Irving Park and Ashland. The data contains the following Robot Operating System (ROS) topics: - /Central_Camera_blurred – Image flow from coaxial camera heading, vehicle front. - /Left_Camera_blurred – Image flow from left camera, 60° from central camera on the left side. - /Right_Camera_blurred – Image flow from right camera, 60° from central camera on the right side. - /camera0/camera_info – Intrinsic and distortion information of left camera. - /camera0/projection_matrix – Extrinsic matrix of left camera from lidar. - /camera2/camera_info – Intrinsic and distortion information of central camera. - /camera2/projection_matrix – Extrinsic matrix of central camera from lidar. - /camera5/camera_info – Intrinsic and distortion information of right camera. - /camera5/projection_matrix – Extrinsic matrix of right camera from lidar. - /novatel/oem7/bestpos – Latitude, longitude, and elevation information from NovAtel GNSS-INS system. - /points_raw – VLP-32 lidar point cloud. - /tf – Vehicle base frame. The data are organized into a data description file and one or more ROS .bag files, dependent on original file size. The data description file provides information about the data collection date, location, and detailed mapping, while the .bag file(s) contain the actual data. Please note that for the purpose of securing personally identifiable information, all license plates and faces included in this publication have been intentionally blurred during real-time processing. ![ashland avenue image](ashland-avenue.png)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Raw_data_Batch_I: Downers Grove to Darien

Date of collection: May 11, 2023 Location: Downers Grove to Darien, IL This dataset contains lidar and vision data collected in Downers Grove and Darien, IL. The vehicle started in Downers Grove at the intersection of Main and Ogden, headed east. At the intersection of Odgen and IL 83, it then headed south until IL 33 and then west along IL 33 until the intersection of IL 33 and Lemont Road. It then headed north along Lemont Road/Main Street until the intersection of Main and Ogden. The data contains the following Robot Operating System (ROS) topics: - /Central_Camera_blurred – Image flow from coaxial camera heading, vehicle front. - /Left_Camera_blurred – Image flow from left camera, 60° from central camera on the left side. - /Right_Camera_blurred – Image flow from right camera, 60° from central camera on the right side. - /camera0/camera_info – Intrinsic and distortion information of left camera. - /camera0/projection_matrix – Extrinsic matrix of left camera from lidar. - /camera2/camera_info – Intrinsic and distortion information of central camera. - /camera2/projection_matrix – Extrinsic matrix of central camera from lidar. - /camera5/camera_info – Intrinsic and distortion information of right camera. - /camera5/projection_matrix – Extrinsic matrix of right camera from lidar. - /novatel/oem7/bestpos – Latitude, longitude, and elevation information from NovAtel GNSS-INS system. - /points_raw – VLP-32 lidar point cloud. - /tf – Vehicle base frame. The data are organized into a data description file and one or more ROS .bag files, dependent on original file size. The data description file provides information about the data collection date, location, and detailed mapping, while the .bag file(s) contain the actual data. Please note that for the purpose of securing personally identifiable information, all license plates and faces included in this publication have been intentionally blurred during real-time processing. ![downers grove image](downers-grove-darien.png)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Raw_data_Batch_I: Garfield Ridge

Date of collection: May 4, 2023 Location: Garfield Ridge, Chicago, IL This data set contains lidar and vision data collected in Garfield Ridge, Chicago. The vehicle started from the intersection of Garfield Ridge and S. Harlem, headed east until S. Central Ave. The vehicle headed south along S. Central Ave. until West 60th Street, headed west, and turned north along S. Austin Ave. until it turned west onto W. 59th Street. The vehicle then headed north along S. Harlem Ave. and returned to the intersection of Garfield Ridge and S. Harlem. The data contains the following Robot Operating System (ROS) topics: - /Central_Camera_blurred – Image flow from coaxial camera heading, vehicle front. - /Left_Camera_blurred – Image flow from left camera, 60° from central camera on the left side. - /Right_Camera_blurred – Image flow from right camera, 60° from central camera on the right side. - /camera0/camera_info – Intrinsic and distortion information of left camera. - /camera0/projection_matrix – Extrinsic matrix of left camera from lidar. - /camera2/camera_info – Intrinsic and distortion information of central camera. - /camera2/projection_matrix – Extrinsic matrix of central camera from lidar. - /camera5/camera_info – Intrinsic and distortion information of right camera. - /camera5/projection_matrix – Extrinsic matrix of right camera from lidar. - /novatel/oem7/bestpos – Latitude, longitude, and elevation information from NovAtel GNSS-INS system. - /points_raw – VLP-32 lidar point cloud. - /tf – Vehicle base frame. The data are organized into a data description file and one or more ROS .bag files, dependent on original file size. The data description file provides information about the data collection date, location, and detailed mapping, while the .bag file(s) contain the actual data. Please note that for the purpose of securing personally identifiable information, all license plates and faces included in this publication have been intentionally blurred during real-time processing. ![garfield ridge image](garfield-ridge.png)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Raw_data_Batch_I: Lakeshore Drive

Date of collection: May 18, 2023 Location: Lakeshore Drive, Chicago, IL Content: “North to South” “South to North” This data set contains lidar and vision data collected along Lakeshore Drive. The “South to North” folder starts from the intersection of Lakeshore Drive and 31st Street and ends at Hollywood Towers Chicago. The “North to South” folder starts from the intersection of Lakeshore Drive and Sheridan Avenue and ends at the 31st Street intersection. The data contains the following Robot Operating System (ROS) topics: - /Central_Camera_blurred – Image flow from coaxial camera heading, vehicle front. - /Left_Camera_blurred – Image flow from left camera, 60° from central camera on the left side. - /Right_Camera_blurred – Image flow from right camera, 60° from central camera on the right side. - /camera0/camera_info – Intrinsic and distortion information of left camera. - /camera0/projection_matrix – Extrinsic matrix of left camera from lidar. - /camera2/camera_info – Intrinsic and distortion information of central camera. - /camera2/projection_matrix – Extrinsic matrix of central camera from lidar. - /camera5/camera_info – Intrinsic and distortion information of right camera. - /camera5/projection_matrix – Extrinsic matrix of right camera from lidar. - /novatel/oem7/bestpos – Latitude, longitude, and elevation information from NovAtel GNSS-INS system. - /points_raw – VLP-32 lidar point cloud. - /tf – Vehicle base frame. The data are organized into a data description file and one or more ROS .bag files, dependent on original file size. The data description file provides information about the data collection date, location, and detailed mapping, while the .bag file(s) contain the actual data. Please note that for the purpose of securing personally identifiable information, all license plates and faces included in this publication have been intentionally blurred during real-time processing. ![lakeshore drive image](lakeshore-drive.png)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Raw_data_Batch_I: Lisle to Waterfall Glen

Date of collection: May 11, 2023 Location: DuPage County, IL This dataset contains lidar and vision data collected between Lisle, IL, and the Waterfall Glen parking lot. The vehicle started near Cass School District 63, headed east along IL 34. The vehicle then turned south along IL 83 until Interstate 55. Finally, the vehicle turned southwest along I 55 until Exit 273A and headed toward the Waterfall Glen parking lot. The data contains the following Robot Operating System (ROS) topics: - /Central_Camera_blurred – Image flow from coaxial camera heading, vehicle front. - /Left_Camera_blurred – Image flow from left camera, 60° from central camera on the left side. - /Right_Camera_blurred – Image flow from right camera, 60° from central camera on the right side. - /camera0/camera_info – Intrinsic and distortion information of left camera. - /camera0/projection_matrix – Extrinsic matrix of left camera from lidar. - /camera2/camera_info – Intrinsic and distortion information of central camera. - /camera2/projection_matrix – Extrinsic matrix of central camera from lidar. - /camera5/camera_info – Intrinsic and distortion information of right camera. - /camera5/projection_matrix – Extrinsic matrix of right camera from lidar. - /novatel/oem7/bestpos – Latitude, longitude, and elevation information from NovAtel GNSS-INS system. - /points_raw – VLP-32 lidar point cloud. - /tf – Vehicle base frame. The data are organized into a data description file and one or more ROS .bag files, dependent on original file size. The data description file provides information about the data collection date, location, and detailed mapping, while the .bag file(s) contain the actual data. Please note that for the purpose of securing personally identifiable information, all license plates and faces included in this publication have been intentionally blurred during real-time processing. ![lisle waterfall image](lisle-waterfall.png)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Raw_data_Batch_I: Randall Road

Date of collection: June 3, 2022 Location: Randall Road, DuPage County, IL Content: “North to South” “South to North” This data set contains lidar and vision data collected along Randall Road in DuPage County, Illinois. The “South to North” folder starts at 1480 N. Orchard Road, Aurora, IL 60506, headed north along Randall Road until 238 N. Randall Road, St. Charles, IL 60174. The “North to South” folder starts from 238 N. Randall Road, St. Charles, IL 60174, headed south along Randall Road until 1480 N. Orchard Road, Aurora, IL. The data contains the following Robot Operating System (ROS) topics: - /Central_Camera_blurred – Image flow from coaxial camera heading, vehicle front. - /Left_Camera_blurred – Image flow from left camera, 60° from central camera on the left side. - /Right_Camera_blurred – Image flow from right camera, 60° from central camera on the right side. - /camera0/camera_info – Intrinsic and distortion information of left camera. - /camera0/projection_matrix – Extrinsic matrix of left camera from lidar. - /camera2/camera_info – Intrinsic and distortion information of central camera. - /camera2/projection_matrix – Extrinsic matrix of central camera from lidar. - /camera5/camera_info – Intrinsic and distortion information of right camera. - /camera5/projection_matrix – Extrinsic matrix of right camera from lidar. - /novatel/oem7/bestpos – Latitude, longitude, and elevation information from NovAtel GNSS-INS system. - /points_raw – VLP-32 lidar point cloud. - /tf – Vehicle base frame. The data are organized into a data description file and one or more ROS .bag files, dependent on original file size. The data description file provides information about the data collection date, location, and detailed mapping, while the .bag file(s) contain the actual data. Please note that for the purpose of securing personally identifiable information, all license plates and faces included in this publication have been intentionally blurred during real-time processing. ![randall road image](randall-road.png)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Raw_data_Batch_I: State Street

Date of collection: May 18, 2023 Location: State Street, Chicago, IL This data set contains lidar and vision data collected along State Street. The vehicle started from outside of the McCormick Tribune Campus Center at the Illinois Institute of Technology’s Mies Campus and headed north along State Street, until the north end of State Street in the Gold Coast. The data contains the following Robot Operating System (ROS) topics: - /Central_Camera_blurred – Image flow from coaxial camera heading, vehicle front. - /Left_Camera_blurred – Image flow from left camera, 60° from central camera on the left side. - /Right_Camera_blurred – Image flow from right camera, 60° from central camera on the right side. - /camera0/camera_info – Intrinsic and distortion information of left camera. - /camera0/projection_matrix – Extrinsic matrix of left camera from lidar. - /camera2/camera_info – Intrinsic and distortion information of central camera. - /camera2/projection_matrix – Extrinsic matrix of central camera from lidar. - /camera5/camera_info – Intrinsic and distortion information of right camera. - /camera5/projection_matrix – Extrinsic matrix of right camera from lidar. - /novatel/oem7/bestpos – Latitude, longitude, and elevation information from NovAtel GNSS-INS system. - /points_raw – VLP-32 lidar point cloud. - /tf – Vehicle base frame. The data are organized into a data description file and one or more ROS .bag files, dependent on original file size. The data description file provides information about the data collection date, location, and detailed mapping, while the .bag file(s) contain the actual data. Please note that for the purpose of securing personally identifiable information, all license plates and faces included in this publication have been intentionally blurred during real-time processing. ![state street image](state-street.png)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Underlying Data for the EVI-RoadTrip Web Tool

The dataset contains simulation-based charging infrastructure outputs that are visualized on the EVI-RoadTrip webtool. The outputs are aggregated to lower spatial resolution (e.g., state-level, corridor-level).

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Load Profiles Data for the EVI-RoadTrip Web Tool

The dataset contains EVI-RoadTrip outputs, minute-by-minute load profiles in kW for each station in the simulation based on assumed utilization and network density. The load profiles are aggregated to lower spatial resolution (e.g., state-level, corridor-level) by summation of all station loads associated with the respective geography. This results in a load profile for each scenario that summarizes the corridor's, state's, or county's load profile in minute-level resolution.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Detailed Simulation Datasets Quantifying U.S. DOE VTO/HFTO R&D Benefits Across Light- to Heavy-Duty Vehicles

For more than 20 years, Argonne National Laboratory’s Vehicle & Mobility Systems Department has assessed how R&D investments by the U.S. Department of Energy’s Transportation Technologies Office and Alternative Fuels and Feedstocks Office affect vehicle energy use and cost. The analyses are performed using Autonomie, Argonne’s full-vehicle simulation tool for energy consumption, performance, and cost. The study covers five time frames ranging from present day through 2050, with more than 30 vehicle classes and applications (10 light duty and >20 medium and heavy duty), as well as six powertrain configurations (conventional, start-stop, hybrid electric vehicle, plug-in hybrid electric vehicle, battery-electric vehicle, and fuel cell electric vehicle) and five fuels (gasoline, diesel, natural gas, hydrogen, and electricity). Low and high technology uncertainty scenarios have been considered to capture a realistic range of outcomes. The resulting datasets include the assumptions used (i.e., efficiency, $/kWh), vehicle-level data (power, energy, weight, and cost), and outputs such as energy consumption, manufacturer’s suggested retail price, and total cost of ownership. These data are critical to stakeholders working in transportation, technology assessment, and long-term R&D planning.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Downloadable Dynamometer Database (D3): Public Test Data on Advanced-Technology Vehicles

Access to high-quality, independent vehicle test data is critical to advancing energy-efficient transportation research. The Downloadable Dynamometer Database (D3) is a public repository of dynamometer test data on advanced-technology vehicles, generated at the Advanced Mobility Technology Laboratory (AMTL) at Argonne National Laboratory and hosted by the Transportation and Power Systems Division. The database has been made available to support researchers, students, and professionals engaged in energy-efficient vehicle research, development, and education. A wide range of vehicle categories has been tested (i.e., alternative fuel vehicles, conventional gasoline and diesel vehicles, all-electric vehicles, hybrid electric vehicles, and plug-in hybrid electric vehicles), as well as various drive cycles and test conditions documented in the accompanying D3 user presentation. Stakeholders can select a vehicle type, identify a vehicle of interest, and download the associated test data for use in their own analyses. Data downloaded from D3 must be accompanied by the required attribution: "This data is from the Downloadable Dynamometer Database and was generated at the Advanced Mobility Technology Laboratory (AMTL) at Argonne National Laboratory." These data are critical to vehicle modeling, validation, technology assessment, and educational use.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗