Search NASASearch

SEARCH · Search NASA

Results for “robot operating system”

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 73 records · Page 4

Autonomous Robotic Manipulator Software

Autonomous robotic manipulation requires a deep and wide stack of supporting software. This paper presents Autonomous Robotic Manipulator Software (ARMS), a software suite designed at NASA Langley Research Center to support research and development of different algorithms for In-space Servicing, Assembly and Manufacturing (ISAM). ARMS solves common challenges along the autonomous manipulation software stack. Various challenges, such as integration with commercial hardware, simulation, and path planning, are solved through the use of Robot Operating System 2 and its community-developed packages. Other challenges, such as configuration management and task definition, and execution are solved in software built on those tools. The result is a modular approach to robotic system definition, agent actions, and assembly task definitions. ARMS has been used in two ISAM projects at NASA Langley Research Center, the Precision Assembled Space Structures project and the Built On-orbit Robotically assembled Gigatruss project.

Collin J Cresta

Autonomous Robotic Manipulator Software (ARMS)

Autonomous robotic manipulation requires a deep and wide stack of supporting software. This paper presents Autonomous Robotic Manipulator Software (ARMS), a software suite designed at NASA Langley Research Center to support research and development of different algorithms for In-space Servicing, Assembly and Manufacturing (ISAM). ARMS solves common challenges along the autonomous manipulation software stack. Various challenges, such as integration with commercial hardware, simulation, and path planning, are solved through the use of Robot Operating System 2 and its community-developed packages. Other challenges, such as configuration management and task definition, and execution are solved in software built on those tools. The result is a modular approach to robotic system definition, agent actions, and assembly task definitions. ARMS has been used in two ISAM projects at NASA Langley Research Center, the Precision Assembled Space Structures project and the Built On-orbit Robotically assembled Gigatruss project.

Collin J Cresta

ISRU Pilot Excavator Wheel Testing in Lunar Regolith Simulant

The ISRU Pilot Excavator, or IPEx, is a robotic excavator funded by NASA’s Space Technology Mission Directorate (STMD). The Concept of Operations for IPEx involves the robot driving on the lunar surface up to 70 km at a speed of up to 30 cm/s. As such, it is critical to the mission’s success to optimize the design of the wheels for performance in lunar conditions, specifically in lunar regolith. To achieve this, an array of tests was completed to observe the effects of various wheel design choices on the driving performance of the wheels in lunar regolith simulant. In order to facilitate testing, we designed a 12” dia. configurable wheel to allow for interchangeability between various wheel formations. Two types of wheel parts were designed to be swapped: cleats, which form the tread of the wheel; and grousers, which protrude from the treads. The test variables that we considered were as follows: square vs. round wheel shape, solid vs. perforated cleats, cleat spacing, grouser height, and grouser spacing. By combining different settings of each of these test variables, ten discrete wheel designs were created and tested. The configurable test wheels were mounted on the Regolith Advanced Surface Systems Operations Robot (RASSOR) developed at NASA’s Kennedy Space Center. In our experiments, the robot was driven at a controlled speed across a prepared surface of BP-1 lunar regolith simulant. Four types of tests were conducted: circle driving, straight driving, slope driving, and drawbar pull. The driving tests were chosen to mimic a variety of conditions in which IPEx may be expected to operate, and the drawbar pull test was chosen to provide a standard of comparison with existing wheel design literature. The circle and straight driving tests were each performed at different levels: for the circle driving test, the robot was driven at a constant linear speed and three different angular speeds, while for the straight driving test, the robot was driven at three different linear speeds. The data collected from these tests included the power usage from each of the wheels, measurements of the tread patterns left in the regolith surface, and the amount of slip the wheels experienced, which was calculated using data from an OptiTrack motion capture system. From the results of these experiments, we found that certain test variables were more significant than others in determining performance for each type of test, and no single wheel design clearly outperformed the others in all areas. The details of our findings will be discussed further in this paper. This data will be utilized to inform the design of the wheels for IPEx and can provide a basis for the design of wheels for future lunar terrain vehicles.

RASSOR

300_underground robot (final research report)

Recent advancements in mobile robotics have displayed impressive capabilities in traversing and accessing areas that are inaccessible to humans either due to the characteristics of the environment or potential hazards. Furthermore, these advancements within the field of mobile robotics, more specifically uncrewed ground vehicles (UGVs), give the ability to potentially survey, observe, and map these inaccessible areas for humans. However, one of the most challenging areas to implement this technology is underground environments. The main challenge with implementing this technology in underground environments is the dependence on either GPS or RF communication for UGVs to navigate properly. Therefore, in order to properly demonstrate the mapping capabilities of the UGV this challenge must be resolved. The overall goal of this study is to demonstrate the mapping capabilities of a UGV while addressing this challenge and documenting the implementation and testing phase of the robot. The proposed solution to this challenge is to implement a SLAM algorithm onto the main computational device of the UGV utilizing the Robot Operating System (ROS). The algorithm is the open-source software package Slam Toolbox developed by Steve Macenski. Furthermore, the sllidar_ros2 package from Slamtec will be used to gather the lidar data from an A3M1 2D lidar. A separate program will be created to gather odometry information for our UGV robot. All of these software packages will run together in a Docker environment. Through working on this project I have developed a better understanding of the world of robotics/autonomous systems, especially with applications such as navigation and mapping. Furthermore, through this project, I have been given exposure to how research is conducted within a DOE lab setting. As robotics/autonomous systems become more advanced it's important to pursue more avenues of research such as this project as it will ensure the development of our capabilities.

42 ENGINEERING

ICE-RASSOR: Intelligent Capabilities Enhanced

NASA’s Regolith Advanced Surface Systems Operations Robot (RASSOR) is principally designed to mine and deliver regolith for In-Situ Resource Utilization (ISRU) processing. RAS-SOR’s design enables it to efficiently collect and deposit regolith, return collected material for processing, and myriad related ISRU activities. To reliably perform these operations on the lunar sur-face, RASSOR software and sensory systems need to be robust and maximize the information extracted from on-board sensing. Herein, we present preliminary findings from the Intelligent Capabilities Enhanced RASSOR project. We apply supervised learning using real data to estimate the soil mass collected without the need for mass flow rate monitors or other explicate sensing techniques. We also create a reduced-order simulation environment to develop autonomous trenching controllers via reinforcement learning and proto-type state estimation architectures. Our initial results suggest that excavated regolith mass can be inferred within 2.9% RMS error of full scale, and reinforcement learning for autonomous operations has learned viable trenching strategies and helped identify desirable sensing capabilities, arrangements, and considerations. Future work includes regolith mass estimation during dynamic operation, expanding our simulation to more complex environments, and transfer learning from simulation to hardware.

machine learning

Astrobee: Five years of Completed, Current, and Future Research on the International Space Station using Free Flying Robots.

After five years on the International Space Station (ISS), the Astrobee Research Facility, has completed over 160 Test Sessions logging over 1200 hours of operations. Managed by the NASA ISS Program OZ office and supported by NASA Ames Research Center (ARC) in California, the Astrobee Team currently maintains two identical free-flying Astrobee robots and a Docking Station for research on the ISS. As a technology demonstration platform, the Astrobee Robots are available for Guest Scientists to use for a spectrum of research capabilities. Using ambient air on the ISS, propelled by battery-operated fans, Astrobee is designed to autonomously operate throughout most of the USOS (US Orbital Segment), with the objective of minimizing the need for astronaut support. Astrobee carries a suite of six cameras, a two degree-of-freedom (DOF) arm with a gripper that can grasp ISS handrails and other objects, and three payload bays that provide power and data for guest science hardware. Astrobee can autonomously execute hours-long flight plans or be tele-operated from the ground. While the Astrobee Team continues to improve mapping and autonomous flight capabilities, one of the main goals of Astrobee Robots is to provide research opportunities for Guest Scientists. The Astrobee Robot Software (ARS) makes extensive use of the open-source Robot Operating System (ROS). The ARS can be used interchangeably with an Astrobee Simulator or as Astrobee’s onboard software. ARS features include autonomous docking and perching, real-time teleoperations from the ground, plan based autonomous tasks, multi Astrobee communication, among other capabilities. Through simulation software and ground testing laboratories, the Astrobee Team is available to support Guest Scientists during development and testing and lead real-time ISS operations. The Astrobee Team and Guest Scientists have completed research including Astrobatics maneuvers, RFID and sound sensing capabilities, Gecko materials studies, student Robotics Programming Challenges, and Free Flyer formation flight investigations. Current science with the Astrobee Robots is investigating new docking capabilities through software only research as well as testing new docking hardware installed on the Astrobees. The Astrobee Team and other researchers at NASA Ames continue to explore robotics applications for future NASA missions such as Gateway and potential experiments involving human-robot interactions. Continued advanced mapping resolution capabilities, and high-resolution panoramic imagery also remains areas of research. Exciting in development research involves docking for rendezvous proximity operation (CLINGERS), multi resolution 3D scanning (MRS), space debris removal in microgravity (REACCH). This presentation will mainly focus on completed research over the past year and current science being performed on the Astrobees. This presentation will also focus on how a Guest Scientist/Researcher progresses from conception to running their science on the Astrobees on the ISS, as well as discuss the Astrobee Facility resources available for supporting ground testing and real-time ISS operations.

Astrobee

Space station automation and robotics study. Operator-systems interface

This is the final report of a Space Station Automation and Robotics Planning Study, which was a joint project of the Boeing Aerospace Company, Boeing Commercial Airplane Company, and Boeing Computer Services Company. The study is in support of the Advanced Technology Advisory Committee established by NASA in accordance with a mandate by the U.S. Congress. Boeing support complements that provided to the NASA Contractor study team by four aerospace contractors, the Stanford Research Institute (SRI), and the California Space Institute. This study identifies automation and robotics (A&R) technologies that can be advanced by requirements levied by the Space Station Program. The methodology used in the study is to establish functional requirements for the operator system interface (OSI), establish the technologies needed to meet these requirements, and to forecast the availability of these technologies. The OSI would perform path planning, tracking and control, object recognition, fault detection and correction, and plan modifications in connection with extravehicular (EV) robot operations.

Source record

Astrobee: Completed, Current, and Future Research using Free Flying Robots on the International Space Station

After four years on the International Space Station (ISS), the Astrobee Research Facility, has completed over 130 Test Sessions logging over 1000 hours of operations. Managed by the NASA ISS Program OZ office and supported by NASA Ames Research Center (ARC) in California, the Astrobee Team maintains three identical free-flying Astrobee robots for research on the ISS. As a technology demonstration platform, the Astrobee Robots are available for Guest Scientists to use for a spectrum of research capabilities. Astrobee, propelled by battery-operated fans, is designed to autonomously operate throughout most of the USOS (US Orbital Segment), with the objective of minimizing astronaut support. Astrobee carries a suite of six cameras, a two degree-of-freedom (DOF) arm with a gripper that can grasp ISS handrails and other objects, and three payload bays that provide power and data for guest science hardware. Astrobee can autonomously execute hours-long flight plans or be teleoperated from the ground or by astronauts. While the Astrobee Team continues to improve mapping and autonomous flight capabilities, one of the main goals of Astrobee Robots is to provide research opportunities for Guest Scientists. The Astrobee Robot Software (ARS) makes extensive use of the open-source Robot Operating System (ROS). The ARS can be used interchangeably with an Astrobee Simulator or as Astrobee’s onboard software. ARS features include autonomous docking and perching, real-time teleoperations from the ground, plan based autonomous tasks, multi Astrobee communication, among other capabilities. Through simulation software and ground testing laboratories, the Astrobee Team is available to support Guest Scientists during development and testing and lead real-time ISS operations. Guest Scientists can participate in this research opportunity following the Guest Science Lifecycle (GSL) shown in Figure 1: Guest Science Lifecycle below. The Astrobee Team and Guest Scientists have complete research including Gecko materials studies, RFID and sound sensing capabilities, student Robotics Programming Challenges, and Free Flyer formation flight investigations. Current science with the Astrobee Robots includes Free Flyer self-toss studies, new docking capabilities, advanced mapping resolution capabilities, and high resolution panoramic imagery. Future Guest scientists and Astrobee Team research will focus on robotics applications for future NASA missions such as Gateway and Artemis and potential experiments involving human-robot interactions. This presentation will focus on four main subjects, 1) completed, current, and future planned research using the Astrobee robots, 2) how Guest Scientist get from conception to the ISS, 3) Astrobee Facility resources available for Guest Science ground testing and real-time ISS operations support, and 4) lessons learned from four years of ISS operations.

Astrobee

Real-time Object Bounding in LiDAR Data With Computer Vision

The Multimodal Measurement System is a roadside radiation measurement testbed used to detect radiation sources in passing vehicles. It works by combining sensor signals from various modalities to produce a thorough scan of the source. A LiDAR sensor is used to measure the dimensions of the vehicle and provide a velocity estimate. However, the current LiDAR setup uses propriety software for which the source code is unavailable and cannot be updated to improve performance. Therefore, it is imperative to the accuracy of the analysis to create a custom vehicle detection that can return the dimensions and velocity of passing vehicles in real time. This new custom detection is written in C++ using the PointCloud Library, which keeps it lightweight. It also utilizes Docker and the Robot Operating System, which allows the versatility of running both on a small computer or the Lawrence Livermore National Laboratory cluster while utilizing different models of LiDAR sensors. The custom detection outperforms the current detection model, which increases the accuracy of radiation source detection.

97 MATHEMATICS AND COMPUTING

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

Perceptual telerobotics

A sensory world modeling system, congruent with a human expert's perception, is proposed. The Experiential Knowledge Base (EKB) system can provide a highly intelligible communication interface for telemonitoring and telecontrol of a real time robotic system operating in space. Paradigmatic acquisition of empirical perceptual knowledge, and real time experiential pattern recognition and knowledge integration are reviewed. The cellular architecture and operation of the EKB system are also examined.

Ligomenides, Panos A.