README.md

ros_detection_legs

• ros_detection_legs
  • goal
  • use
    • deep-learning
      • preprocessing data
      • train model
    • ros
      • compilation packages
      • run nodes
  • architecture
    • data extraction
    • data preprocessing
      • segmentation
      • increase positive data
    • training
      • information about the current model
    • prediction

goal

Extract legs positions from lidar data, like this:

https://www.youtube.com/watch?v=KcfxU6_UrOo

use

deep-learning

⚠️ a model is already trained, saved in ./model/ folder :pencil: if you want to change some parameters, please update ./src/ros_detection_legs/deep_learning/config/parameters.json

preprocessing data

run preprocessing script:

$ python3 src/preprocessing.py

once run data are stored in ./data/train/

train model

run training script:

$ python3 src/training.py 

ros

compilation packages

# clone 'ros_pygame_radar_2D' to your workspace
$ git clone https://github.com/PouceHeure/ros_pygame_radar_2D

# compile package 
$ catkin build ros_pygame_radar_2D

# git 'ros_detection_legs' (this pkg) to your workspace
$ git clone https://github.com/PouceHeure/ros_detection_legs

# inside your ros workingspace
$ catkin build ros_detection_legs

run nodes

⚠️ source devel before

1. run detector_node

$ rosrun ros_detection_legs detector_node.py

2. use ros_pygame_radar2D

$ rosrun ros_pygame_radar_2D radar_node.py

3. update parameters, some parameters about model are dynamically reconfigurable. By default dynamic_reconfigure loads settings save in parameters.json, don't forget to recompile the project if you change parameters.json (because the dynamic_reconfigure generates a .h file from the cfg file) !

• compile cfg and generate new configuration file:

# update parameters.json 
$ catkin build 

• update parameters dynamically:

$ rosrun rqt_reconfigure rqt_reconfigure

architecture

data extraction

• package: ros_lidar_recorder https://github.com/PouceHeure/ros_lidar_recorder
• data labeling tool: lidar_tool_label https://github.com/PouceHeure/lidar_tool_label
• dataset: https://github.com/PouceHeure/dataset_lidar2D_legs

data preprocessing

This schema defines princpals steps:

We can create clusters with a segmentation method, by this way data will gathering if there are closed.

segmentation

Before segmentation, we have to found a way how to compute a distance between 2 polar points.

• First approach, convert all polar points to cartesien and apply a classic norm, but the complexity of this method is too high.

• Second approach, find a general expression from polar point to cartesian distance.

A second distance is computed:

Once expressions are defined, we have to define hyper-parameters:

• limit_distance
• limit_radius

After segmentation, we have to attach a label to each cluster. For this one, we define limit_cluster_valid.

increase positive data

We can increase positive data by applying a rotation on these data.

All positive clusters are selected, on each cluster the same tranformation is applied on each point.

The transformation is done by this expression:

So at after transformation, if we have N transformations

training

model used: RNN with LSTM cells.

more information about LSTM: https://www.tensorflow.org/api_docs/python/tf/keras/layers/LSTM

information about the current model

settings: model/train/parameters.json

learning curves:

prediction

A ros node, detector_node subscribes to /scan topic. Once data are pusblished to this topic, the node uses the training model to predict legs positions. Legs positions are published to /radar topic.

Like the training, data need to be tranformed. So before prediction, clusters are created directly in the subscriber callback function.

Define the center point of positive clusters:

Coordinate of the center of the cluster j are: