Week 14 (17/5 – 23/5) – Data gathering and testing

This week’s work was mainly centered in the setup of the AtlasCar and in gathering data in the form of rosbags for testing.

Although launching the different lasers was relatively easy, the installation of cameras and the setup of the GPS and IMU combo required more work and troubleshooting, the last mainly with the transition from ROS Kinectic to ROS Melodic.

To record the rosbags, two places were chosen according their different features, one with straight road curbs and lines (Parque de Exposições) and one with inverted curbs and highway (Salinas).

In Figures 1, 2 and 3 there are examples of the performance of different edge detection filters in an inverted road curb situation. The algorithms positively identify the curbs and road limits.

In the highway situation, as predicted, the algorithm performs poorly due to lack of laser reading information on the account of high speeds.

Fig. 1: Example of data gathering in an inverted curbs situation – density grid (Daniela Rato, 2019)
Fig. 2: Example of data gathering in an inverted curbs situation – Prewitt grid (Daniela Rato, 2019)
Fig. 3: Example of data gathering in an inverted curbs situation – Laplacian grid (Daniela Rato, 2019)


Week 12 (10/5 – 16/5) – Writing and improvements

Although this week was mainly dedicated to writing, a few improves to the grids threshold were made and some corrections to gradient, Kirsh and Prewitt filters to obtain the best grids possible.

In addiction to this, some tests were performed regarding the performance of the quantitative evaluation using different cell types to try to create a defined ROC curve. The evaluation ground truth distance of each frame was also decrease from 40m to 20m, as the limits start becoming less defined further away from the car.

Week 11 (03/5 – 09/5) – Comparison of results with the obtained ground truth

Besides writing, this week was focused on improving the developed quantitative evaluation tool.

First, the ground truth grid was corrected with the right orientation. Then, the necessary was to clean the calculated limits to only contemplate the closest limits to the car. Once the main goal is to obtain the navigable limits of the road, everything besides that is unnecessary information and it was eliminated. This allows to overlay the ground truth grid with the new cleaned grid and perform a preliminary qualitative evaluation, as seen in vid. 1 (0:40min).

In general, the algorithm seems to obtain good results in the calculated limits and they mostly correspond to the real limits.

Vid. 1: Visualization of the ground truth overlaid with the closest limits to the car (Laplace filter). (Daniela Rato, 2019)

To perform a quantitative evaluation, the previously mentioned statistical measures were calculated. As discussed, this measures depends on the true and false positives and negatives. In this case, the unity was consider a grid square.

The results, for each frame that contemplates the ground truth extension, were exported to a CSV file that can be uploaded to a spreadsheet for further calculations.

Fig. 1 shows a ROC curve obtained from the Laplace filter grid.

Fig. 1: ROC curve of the statistical results given by the analysis of the Laplace Filter occupancy grid. (Daniela Rato, 2019)

Week 10 (26/4 – 02/5) – Development of an quantitative evaluation tool

This week’s work resulted a fully developed occupancy grid with the ground truth limits (vid. 1). This limits were imported from a .kml file created in google earth and allow to calculate the efficiency of the detected limits and compare detection methods between them.

Vid. 1.: Visualization of ground truth grid (Daniela Rato, 2019)

To evaluate this efficiency, statistical measures are to be calculated, as described in previous posts. This measures will be calculated frame-by-frame and uploaded in a .csv file. This file can be imported into excel to compute graphics and evaluate the influence of several factors to be studied.

As the cells are not very precise, taking into account that the cell resolution now used is 40cm, it will be given a tolerance of one cell to each side of the car.

Week 9 (19/4 – 25/4) – Development of an quantitative evaluation tool

This week’s work was still centered on the development of a tool to preform a quantitative evaluation of the method developed. This proved to be a bigger challenge than anticipated, yet, the more plausible solution seems to remain in the conversion of a line drawn in google earth to an occupancy grid. The data on this grid, corresponding to the road limits ground truth, will then be compared to the data on the detected limits grids and statistical measures can be evaluated.

At this point, the program is able to generate .kml files with the path traveled, read .kml files produced by google earth features, extract the coordinates and calculate its distance to the car coordinates.

However, this fails on the correct orientation of frames, considering that the world frame where the latitude and longitude are oriented is not aligned to the moving_axis frame, making the ground truth limits unaligned and in the wrong orientation.

To correct this problem, a possible solution is to insert the points in a new point cloud (with z=0) and use pcl_ros::transformPointCloud to transform the points within frames (wgs84 to moving_axis). This would return a new point cloud with the necessary corrections to align the frames, that would allow to correctly place the points in the occupancy grid.

Week 8 (12/4 – 18/4) – Development of an quantitative evaluation tool

This week, the presented challenge was to develop a tool/application to help identify the road limits’ ground truth and calculate the statistical measures.

The initial idea was to develop a GTK application with three windows, with a street map to select the road limits manually, an image of the limits detected by the chosen algorithm and camera image provided by the car camera. This idea is now on stand by due to difficulties migrating the street map to an OpenCv or GTK environment.

Then the option became to draw the limits in the Google Earth application and save them in a .kml file. This file would be upload and read in the code and drawn in an occupancy grid, which would be easily compared to the other grids with the calculated limits. The main challenges in this approach is the conversion between latitude and longitude coordinates in the generated .kml file to meters.

This week, a .kml file was also created with the data from the car GPS antena. This allows to visualize the traveled path in Google Earth to later draw the road limits. Mapviz was also used to visualize the created grids and images in the correct place according to GPS data.

Week 7 (05/4 – 11/4) – Occupancy grid conversion to image, edge detection and study of the influence of cell resolution. Quantitative evaluation of the method

This week started with the conversion of the density grid to an OpenCV image. This was a big addition because it opened a lot of new doors in edge detection filters like canny and LoG.

OpenCV images are very easily manipulated and can be converted back to occupancy grids with thresholds to eliminate low-density zones that do not correspond to road limits.

Video 1 shows the result of multiple edge detection filters as well as the study of the cell resolution influence in the density grid. After multiple tests, the grid resolution was then changed from 0.2m/cell to 0.4m/cell. Video 2 shows the obtained results from this revision.

Vid. 1. Cell resolution study and OpenCV edge detection filters.
Vid. 2. Resolution to 0.4m/cell.

With the need to evaluate the quality of the limits identified a literature review was conducted where that the most common way to evaluate the performance of a road limits detection algorithm found is by calculating the four statistical quantifiers presented in figure 1, where the obtained results are matched to a ground-truth of about 500-100 frames. For each algorithm, these indicators should be calculated in different situations, for example, in a straight and curved road, in the presence of positive and negative road curbs.

Since there are no databases for this kind of work, road segments are to be selected and road limits manually identified to create a database for each described situation to later calculate the indicators with the number of TP (true positives), FP (false positives), TN (true negatives) and FN (false negatives).

Fig. 1. Statistical measures. (2.1) Precision (Positive predictive value). (2.2) Specificity (True negative rate). (2.3) Negative predictive value. (2.4) Sensitivity (Total positive rate).