# Automatic Labeled LiDAR Data Generation based on Precise Human Model

Wonjik Kim, Masayuki Tanaka, Masatoshi Okutomi, Yoko Sasaki

Abstract— Following improvements in deep neural networks, state-of-the-art networks have been proposed for human recognition using point clouds captured by LiDAR. However, the performance of these networks strongly depends on the training data. An issue with collecting training data is labeling. Labeling by humans is necessary to obtain the ground truth label; however, labeling requires huge costs. Therefore, we propose an automatic labeled data generation pipeline, for which we can change any parameters or data generation environments. Our approach uses a human model named Dhaiba and a background of Miraikan and consequently generated realistic artificial data. We present 500k+ data generated by the proposed pipeline. This paper also describes the specification of the pipeline and data details with evaluations of various approaches.

### I. INTRODUCTION

Deep neural networks have considerably impacted computer vision, robotics applications, among other fields. For example, various types of high-performance deep neural networks for pixel-wise segmentation of RGB images have been proposed [^1] [^2] [^3]. Following its success in RGB image segmentation, segmentation networks for depth map and point cloud data have also been vigorously researched [^4] [^5] [^6] [^7]. Human segmentation is a very important task in many types of robotics applications. Recently, Light Detection and Ranging (LiDAR) has become a powerful tool for human segmentation and detection. Therefore, in this study, we focus on human segmentation with three-dimensional point cloud data collected by the LiDAR.

Deep neural networks commonly require a considerable amount of manually labeled training data to achieve high performance. Collecting a sufficient amount of labeled data may incur massive costs in terms of both time and money. In this study, we develop a data generation pipeline that reduces the manual labeling cost. The proposed data generation pipeline comprises three steps: 1) background data collection, 2) human model building, and 3) LiDAR data generation with human labels. The data generation pipeline can provide depth maps, point cloud data with xyz coordinates, and ground truth human labels. The generated data already includes the ground truth human labels; therefore, we do not need a manual labeling process. Additionally, the proposed data generation pipeline can produce point cloud data with any size of human and any type of LiDAR by changing several parameters.

Our goal is to accelerate research of learning-based human segmentation with point cloud data. For that purpose, we have generated a large amount of labeled depth maps (more than 500K maps) with the proposed data generation pipeline. We have trained several segmentation networks with the generated training data. The trained networks have been evaluated with actual data collected by a real LiDAR sensor.

This paper is organized as follows. We quickly review related works in section II. In section III, the entire data generation procedure is explained in detail with a description of each step. Section IV-A contains a brief explanation of segmentation, and three different networks. The specific policy of the training and evaluation methods are described in section IV. A conclusion is provided in section V.

All generated data and labeled real data are presented in the following url. Trained network weight and test sample code also included.

### II. RELATED WORK

After the release of the Microsoft Kinect in 2010, several RGB-D datasets were published. RGB-D datasets for human recognition were also provided, such as for the reidentification of a person with RGB-D sensors [^8], BIWI RGBD-ID dataset [^9], and UPCV Gait dataset [^10]. As the Kinect cannot measure depths greater than 10 [m], LiDAR sensors were employed to handle depths over 10 [m]. In addition, LiDAR sensors are used in auto driving technology. In this field, the KITTI dataset [^11] is widely used by many researchers [^12], [^13]. However, KITTI only provided 93K+ depth data without labeling. Collecting labeled depth maps is still challenging. Pixel or point-wise labeling for 3D depth data is usually a challenging task that involves massive cost. Under the circumstances, the video game Grand Theft Auto was deployed to collect data [^4], [^14], [^15]. This approach may reduce the cost of data construction, but there are still limitations. Grand Theft Auto is not designed for research purposes; therefore, we cannot control specific properties of the circumstances of the simulation, such as human body type and model deployment location.

<http://www.ok.sc.e.titech.ac.jp/res/LHD/>

To deal with these problems, we constructed a data generation pipeline. This allows us to change any parameters and environments when generating depth maps. Furthermore, the proposed generator makes human labels in the process, thereby incorporating the human task into the computation cost. As a result, we can generate data continuously if there are enough computational resources.

---

![Image](images/9cb1a3455133e6d5ffd2b72735de1b5992b50bbe13b856d6b3deb95272cc6dcb.jpg)

<div style="text-align: center;">Fig. 1: Overview of the pipeline. Red words represent controllable parameters. (Green boxes: Human model building) Human models are built by weight and height, then they are combined with a human walking motion. (Blue boxes: LiDAR data generation) Random models are picked and deployed into the simulation field. Then, the depth map with human models is synthesized with a randomly picked background depth map. The depth map is labeled based on the information from the human model deployed location.</div>

### III. PROPOSED DATA GENERATION PIPELINE

### A. Overview

One of the main contributions of this paper is the automatic generation of labeled depth map without involving manual label. The labeled depth map generation comprises three steps: 1) background data collection, 2) human model building, and 3) depth map synthesis with automatic labeling. The background depth maps without human were collected in advance. We collected 2,363 background depth maps at the 3rd floor of Miraikan, a science museum in Tokyo [^16], using a velodyne HDL-32E LiDAR sensor [^17]. Precise and realistic 3D human models were synthesized based on a digital human model called Dhaiba. The depth maps were generated by composing the collected background depth map and the 3D human model. Label data can be obtained because we know where the 3D human models are. This means that we can generate labeled depth maps automatically without manual input. This is one of advantages of the proposed approach. The details are described in the following subsections, and an overview of the pipeline is illustrated in Fig. 1.

### B. Human model building

One of the key components of the proposed data generation pipeline is the precise 3D human model. We employed a digital human model, called "Dhaiba", of DhibaWorks [^18] to build precise 3D human models. The Dhaiba is a human body function model, and DhaibaWorks is a platform for producing digital human models based on Dhaiba. DhaibaWorks supports editing and visualizing basic models such as 3D meshes and skeletal structures, including human models with motion [^19]. Using DhaibaWorks, we can easily generate a specific human model by setting the human parameters such as height, weight, and action status [^20].

![Image](images/bebe19f3675f6024ab68941728b003a49c780e05a57501d1cf4462fc1e9c3fd6.jpg)

We assumed that the human model is walking during the depth map generation. Walking motion data is required to build an artificial walking human model. One period of

<div style="text-align: center;">(a) Human mesh</div>

![Image](images/1d9da25dade02e1fc72f310ee5bced1edde48e5bd5624fac368a308dcc3ed7c9.jpg)

<div style="text-align: center;">(b) Walking human mesh</div>

<div style="text-align: center;">Fig. 2: Example of built human models based on Dhaiba</div>

<div style="text-align: center;">TABLE I: Human model specification</div>

<table border=1 style='margin: auto; word-wrap: break-word;'><tr><td style='text-align: center; word-wrap: break-word;'>Height (mm)</td><td style='text-align: center; word-wrap: break-word;'>1200</td><td style='text-align: center; word-wrap: break-word;'>1400</td><td style='text-align: center; word-wrap: break-word;'>1600</td><td style='text-align: center; word-wrap: break-word;'>1700</td><td style='text-align: center; word-wrap: break-word;'>1800</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Weight (kg)</td><td style='text-align: center; word-wrap: break-word;'>15 20 30</td><td style='text-align: center; word-wrap: break-word;'>20 30 40</td><td style='text-align: center; word-wrap: break-word;'>40 50 70</td><td style='text-align: center; word-wrap: break-word;'>50 60 80</td><td style='text-align: center; word-wrap: break-word;'>50 70 90</td></tr></table>

walking data was collected using a motion capture system [^21]. The walking motion data has 230 frames for a single walking motion. Then, it is easy to build artificial walking human mesh models for depth map generation. Details including motion capture system are described in Kobayashi's work [^21].

In this study, we take fifteen typical combinations of height and weight as summarized in Table I. We believe that these combinations cover a variety of scenarios. Now, we have 230 frames of walking motion data and fifteen combinations of height and weight. As such, a total of 3,450 different types of walking models can be generated. Figure 2 shows an example of built human models.

---

![Image](images/6766d7c53ef46307754336012ff4b93bc1af5a0eac48491c18b9dd10573bb4d4.jpg)

<div style="text-align: center;">(a) Generated data</div>

![Image](images/18fe3707267783d888ebec682b099d41f36c84d613c38f1fe23d12ccbceb61d8.jpg)

<div style="text-align: center;">(b) Real data</div>

### C. LiDAR data generation with human labels

<div style="text-align: center;">Fig. 3: Example of data. Blue points denote background and red points denote human, and real data labeled manually.</div>

In the LiDAR data generation step, the depth map of the built human model is first synthesized. Thereafter, the synthesized depth map of the human model and the randomly picked background depth map are combined to generate the training depth map for human segmentation.

To synthesize the human model depth map, we virtually position the LiDAR sensor at $(0, 0, z_{s})$, where $z_{s}$ is the same height as the height of the sensor for background collection. We assumed that the LiDAR sensor was installed horizontally. Then, the human model depth map was synthesized for the given human model, virtually inserting the human model at $(x_{s}, y_{s}, 0)$, where $(x_{s}, y_{s})$ is a randomly sampled position. The human model direction was randomly sampled. Once the geometrical positions of the LiDAR sensor and the human model were provided, the associated depth map can easily be synthesized.

After synthesizing the human model depth map, it is simply combined with the background depth map by pixel-wise minimum depth selection. In this step, human model farther than background is deleted by minimum depth selection. The depth map taken by the LiDAR sensor usually includes holes or missing pixels whose depth could not be measured. We leave these holes as they are for the synthesis process because these types of holes are equally obtainable in the real sensing process. In addition, the human labeling task can be simultaneously performed because we know which pixels correspond to the human model depth map.

The parameters in the LiDAR data generation are summarized in Table II. Figure 3 shows an example of the generated and real point cloud data. The point cloud data is converted from the depth map.

<div style="text-align: center;">TABLE II: Data generation properties</div>

<table border=1 style='margin: auto; word-wrap: break-word;'><tr><td style='text-align: center; word-wrap: break-word;'>Description</td><td style='text-align: center; word-wrap: break-word;'>Specification</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Number of detector pairs</td><td style='text-align: center; word-wrap: break-word;'>32</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Limitation in horizontal scanning</td><td style='text-align: center; word-wrap: break-word;'>1024</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Vertical scanning range</td><td style='text-align: center; word-wrap: break-word;'>+10.67 to -30.67°</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Angular resolution in vertical</td><td style='text-align: center; word-wrap: break-word;'>1.33°</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Angular resolution in horizontal</td><td style='text-align: center; word-wrap: break-word;'>0.2°</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Human number in one image</td><td style='text-align: center; word-wrap: break-word;'>0 to 10</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Model located area</td><td style='text-align: center; word-wrap: break-word;'>0 to 25000[mm] from origin</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Rotation angle of Dhaiba</td><td style='text-align: center; word-wrap: break-word;'>0 to 360 degrees</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Output depth image size</td><td style='text-align: center; word-wrap: break-word;'>32 $\times$ 1024 $\times$ 1</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Output xyz map size</td><td style='text-align: center; word-wrap: break-word;'>32 $\times$ 1024 $\times$ 3</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Output label data size</td><td style='text-align: center; word-wrap: break-word;'>32 $\times$ 1024 $\times$ 1</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>LiDAR position</td><td style='text-align: center; word-wrap: break-word;'>(0, 0, 800) [mm]</td></tr></table>

### D. Provision of generated data

We generated 500K+ depth data generated by proposed pipeline. They contain depth, xyz coordinates, and human label in HDF5 format. We also provide specific information for each of 500K+ depth data in the shape of an xml file. Xml files contain a human number in the depth scene, location, weight, and height of each Dhaiba. The proposed pipeline allows us to control various properties easily. We also generated the 10K dataset described in section IV-C.2, 1K dataset for each property of the Dhiba described in section IV-C.3, 1K dataset for different backgrounds described in section IV-C.4, and 0.1K manually labeled real data.

### IV. EVALUATION

We used 47K generated data for training and 0.1K real data with manual labeling for validation and estimation. A total of 24101 human models were deployed in the 47K generated data. The model ratio with respect to distance was 74.45% between 0 to 5m, 14.78% between 5 to 10m, 4.726% between 10 to 15m, 3.301% between 15 to 20m, and 2.734% between 20 to 25m. Far models can easily be occluded if one human model is placed in close proximity to the LiDAR. This could be one reason the model ratio with respect to distance between 0 and 5 [m] is up to 74.45%.

In this section, four different networks are described in section IV-A, and the training method shown in IV-B. Section IV-C contains IV-C.1: the effect of train data number, IV-C.2: the effectiveness of precision of the human model, IV-C.3: a validation of different combinations of height and weight, IV-C.4. Then, the result of four networks for generated and real data is shown in IV-D.

### A. Segmentation neural networks

Semantic segmentation has been researched with various approaches for applications. The wide range of its application includes scene understanding, depth analysis, and autonomous driving. Semantic pixel-wise labeling has been gaining considerable interest due to improvements in deep learning [^2], [^22] [^23] [^24]. Four different networks were selected in this paper to evaluate the effectiveness of segmentation networks in the generated human depth maps.

---

![Image](images/a17beb7a163b30543a4a60d3af432727cc174b3c74dcb5817723616946f9b81d.jpg)

<div style="text-align: center;">Fig. 4: Effect of training data number</div>

1) Fully convolutional network: The Fully Convolutional Network (FCN) for segmentation was proposed by Long $^{[1]}$. Classification networks usually use fully connected layers in the end of the network to compute class scores. On the contrary, FCN changed the fully connected layer to a convolutional layer, and the output of the network also changed from a predicted score to a heatmap. Thus, the classification network can easily be changed to a segmentation network using the concept of FCN.

2) U-net: U-net was proposed by Ronneberger [^23]. The U-net architecture includes path contracting for capturing context and a symmetric expanding path. These paths allow the network to enable precise localization. This network won the ISBI cell tracking challenge in 2015 by a large margin, and the authors suggested that U-net could be trained end-to-end from limited data with high performance.

3) Fully convolutional DenseNets: Fully convolutional DenseNets were proposed by Jégou [^25]. They were inspired by Densely Connected Convolutional Networks (DenseNets) [^26]. DenseNets show good performance in image classification, and the concept of DenseNets is based on the observation that if each layer is directly connected to every other layer in a feedforward manner, then the network will be more accurate and easier to train. Jégou proposed an extension to the concept of DenseNets to handle the problem of semantic segmentation. In this paper, we refer to this network as FCDN.

4) Pointnet: Pointnet was proposed by Charles [^5]. Pointnet is designed for handling unordered point sets in 3D and is not affected by rotation or translation. In addition, by adapting a transform network into Pointnet, it accomplishes gaining interactions among points and capturing local structures from neighbor points. Pointnet has two versions; classification and segmentation. The architectures of both versions show differences in the latter half. In this paper, we employed Pointnet as a segmentation network.

### B. Training policy

We trained all networks with 500 epochs. In each epoch, we randomly picked 500 scenes from 47K datasets. We

![Image](images/519069ff69dd4d668ccf19db57afb0f4feb7534009f2c9d19367d16a3d0e0cea.jpg)

<div style="text-align: center;">(a) Example of real data</div>

![Image](images/7f6c65084b8eda3c1c4cf6c58cd94ca9e62329dad933a103d1ccc46f3f7eeaa6.jpg)

<div style="text-align: center;">(b) Ground truth</div>

![Image](images/3f494bd463de31b14f9c03fe4ef8ab8b40e30418fcd15a9d01ff850bf2eb4f08.jpg)

<div style="text-align: center;">(c) Prediction with 0.1K training</div>

![Image](images/b06eb7e28a763adc56c257ea368041c92a6581edf0b05d73fbf17154355d4297.jpg)

<div style="text-align: center;">(d) Prediction with 1K training</div>

![Image](images/8a179b3637324c7ebef9edb0dca45088eb0c4d5517d95fe32f2aee6f1de7751b.jpg)

<div style="text-align: center;">(e) Prediction with 10K training</div>

![Image](images/c6d5e655c5168dde691e9dd11a851508e7cafe3033b72edef332c736e3d4d1af.jpg)

<div style="text-align: center;">(f) Prediction with 47K training</div>

<div style="text-align: center;">Fig. 5: Example of prediction result. In (b), white area denotes human label. From (c) to (f), white area denotes true positive, red area denotes false negative, while blue area denotes false positive.</div>

set a different batch size, chosen experimentally, for each network; 25 for FCN, 10 for U-net, 16 for PointNet, and 5 for FCDN. We then coordinated the step for epoch as batchsize $\times$ stepforepoch = 500, except for PointNet. As PointNet takes a one-dimensional vector, we divided one scene into 16 vectors. Therefore, PointNet also trained with 500 scenes in one epoch, with a batch size of 16. We also employed Adam [^27] with learning rate = 0.001 and decay = 0.001 for the optimizer and categorical cross-entropy for the objective function.

From the Table II, the size of the input image is $32 \times 1024$. Therefore, we revised the Fully Convolutional Network, U-net, and FCDN algorithms in pooling layers. As the height of the input image is only 32, we only pooled input data in the width direction. For Pointnet, input images were divided vertically into 16 pieces of images and dealt with 2048 pixels as points for input data. For FCDN, we also revised the pooling layer to a width-pooling layer, the number of layers per dense block to 3, and the growth rate to 8.

### C. Generated LiDAR data evaluation

We analyzed the effectiveness of the produced data and verified them using various approaches. In this section, Avg. Acc denotes average of background accuracy and human accuracy. In addition, Avg. Acc, Precision, Recall, and Threat score [^28] were calculated as positive as human. In addition, we used that the real data described in table III to compare and evaluate performances.

1) Effect of training data number: In general, the performance of the learning-based approach can be improved by increasing the volume of the training data, especially in the field of deep neural networks. However, in practice, it is

---

<div style="text-align: center;">TABLE III: Real data for evaluation</div>

<table border=1 style='margin: auto; word-wrap: break-word;'><tr><td style='text-align: center; word-wrap: break-word;'>Description</td><td style='text-align: center; word-wrap: break-word;'>Specification</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Location</td><td style='text-align: center; word-wrap: break-word;'>Miraikan [^16]</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Date</td><td style='text-align: center; word-wrap: break-word;'>2017.Aug.04</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>LiDAR model</td><td style='text-align: center; word-wrap: break-word;'>Velodyne HDL32E</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>LiDAR height from ground</td><td style='text-align: center; word-wrap: break-word;'>800 [mm]</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Data number</td><td style='text-align: center; word-wrap: break-word;'>100</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Annotation method</td><td style='text-align: center; word-wrap: break-word;'>Manual</td></tr></table>

<div style="text-align: center;">TABLE IV: Comparison of results from different training data</div>

<table border=1 style='margin: auto; word-wrap: break-word;'><tr><td style='text-align: center; word-wrap: break-word;'></td><td style='text-align: center; word-wrap: break-word;'>Walking model</td><td style='text-align: center; word-wrap: break-word;'>Standing model</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Avg. Acc</td><td style='text-align: center; word-wrap: break-word;'>0.6922</td><td style='text-align: center; word-wrap: break-word;'>0.6058</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Precision</td><td style='text-align: center; word-wrap: break-word;'>0.5729</td><td style='text-align: center; word-wrap: break-word;'>0.7271</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Recall</td><td style='text-align: center; word-wrap: break-word;'>0.3504</td><td style='text-align: center; word-wrap: break-word;'>0.2047</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Threat score</td><td style='text-align: center; word-wrap: break-word;'>0.3448</td><td style='text-align: center; word-wrap: break-word;'>0.2061</td></tr></table>

difficult to collect a huge volume of training data due to the labeling cost. One of the advantages of the proposed depth map generation pipeline is automatic labeling. In this sense, the labeling cost of the proposed pipeline is much lower than that of manual labeling. Here, we clarify the effect of the number of training examples. We prepared four different sizes of training dataset, 0.1K, 1K, 10K, and 47K. Then, the FCN networks were trained with the four datasets. The trained networks were evaluated with the labeled real data.

Figure 4 shows the evaluation results. We can see that the average accuracy, recall, and threat score were improved by increasing the volume of the training data. However, precision shows a different tendency. In case of training with 0.1K data, the network could only be regarded as human when it has high confidence. Therefore, the average accuracy, recall, and threat score of the training 0.1K data were lower than those of any other cases but the precision was greater than 0.7. The network trained with 47K data shows higher performance than other cases in average accuracy, recall, and threat score, except for precision.

Figure 5 shows examples of the prediction for real data. From figure 5-(c) to figure 5-(f), it can be seen that increasing the number of the training data elevates the true positive number. Even the false positive rises as well, undetection of humans (false negative) is much more crucial than misdetection (false positive) in auto driving. Then, the increase in the recall with average accuracy and threat score can be considered entire improvements. In addition, the threat score denotes the intersection over union (IoU) in this experiment because there were only two labels. As a result, the increasing tendency of the threat score with respect to the number of training data represents improvement in the IoU. Following these reasons, we can conclude that a large volume of data helps to improve performance.

2) Effectiveness of precision of human model: We have proposed depth map generation based on a precise 3D human model. Here, we experimentally validate the effectiveness of

<div style="text-align: center;">TABLE V: Comparison of results from different body types</div>

<table border=1 style='margin: auto; word-wrap: break-word;'><tr><td style='text-align: center; word-wrap: break-word;'></td><td style='text-align: center; word-wrap: break-word;'>1000mm, 12kg</td><td style='text-align: center; word-wrap: break-word;'>1500mm, 50kg</td><td style='text-align: center; word-wrap: break-word;'>2000mm, 80kg</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Avg. Acc</td><td style='text-align: center; word-wrap: break-word;'>0.7747</td><td style='text-align: center; word-wrap: break-word;'>0.7433</td><td style='text-align: center; word-wrap: break-word;'>0.7423</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Precision</td><td style='text-align: center; word-wrap: break-word;'>0.4409</td><td style='text-align: center; word-wrap: break-word;'>0.5403</td><td style='text-align: center; word-wrap: break-word;'>0.5437</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Recall</td><td style='text-align: center; word-wrap: break-word;'>0.3886</td><td style='text-align: center; word-wrap: break-word;'>0.3896</td><td style='text-align: center; word-wrap: break-word;'>0.3814</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Threat score</td><td style='text-align: center; word-wrap: break-word;'>0.3635</td><td style='text-align: center; word-wrap: break-word;'>0.4152</td><td style='text-align: center; word-wrap: break-word;'>0.3879</td></tr><tr><td style='text-align: center; word-wrap: break-word;'></td><td style='text-align: center; word-wrap: break-word;'>1400mm, 20kg</td><td style='text-align: center; word-wrap: break-word;'>1600mm, 50kg</td><td style='text-align: center; word-wrap: break-word;'>1700mm, 80kg</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Avg. Acc</td><td style='text-align: center; word-wrap: break-word;'>0.7507</td><td style='text-align: center; word-wrap: break-word;'>0.7771</td><td style='text-align: center; word-wrap: break-word;'>0.7764</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Precision</td><td style='text-align: center; word-wrap: break-word;'>0.5110</td><td style='text-align: center; word-wrap: break-word;'>0.5119</td><td style='text-align: center; word-wrap: break-word;'>0.5716</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Recall</td><td style='text-align: center; word-wrap: break-word;'>0.3935</td><td style='text-align: center; word-wrap: break-word;'>0.4131</td><td style='text-align: center; word-wrap: break-word;'>0.4285</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Threat score</td><td style='text-align: center; word-wrap: break-word;'>0.4097</td><td style='text-align: center; word-wrap: break-word;'>0.4142</td><td style='text-align: center; word-wrap: break-word;'>0.4416</td></tr></table>

<div style="text-align: center;">TABLE VI: Comparison of results from different backgrounds</div>

<table border=1 style='margin: auto; word-wrap: break-word;'><tr><td style='text-align: center; word-wrap: break-word;'></td><td style='text-align: center; word-wrap: break-word;'>Different background</td><td style='text-align: center; word-wrap: break-word;'>Same background</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Avg. Acc</td><td style='text-align: center; word-wrap: break-word;'>0.6556</td><td style='text-align: center; word-wrap: break-word;'>0.7095</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Precision</td><td style='text-align: center; word-wrap: break-word;'>0.1297</td><td style='text-align: center; word-wrap: break-word;'>0.7047</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Recall</td><td style='text-align: center; word-wrap: break-word;'>0.3515</td><td style='text-align: center; word-wrap: break-word;'>0.4285</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Threat score</td><td style='text-align: center; word-wrap: break-word;'>0.1018</td><td style='text-align: center; word-wrap: break-word;'>0.3919</td></tr></table>

the precise 3D human model. In the proposed pipeline, we assume that humans' heights and weights are 15 different combinations and that the human is walking. Then, we build the precise 3D human model. For comparison, we built a human model assuming that the human height and weight were only 1600 mm-60 kg and that the human was standing toward the LiDAR, as shown in Fig. 2-(a). We call this human model the standing model. We generated 10K datasets with the human walking model of the proposed generation pipeline and with the standing model for comparison. Then, the FCN networks were trained with two training datasets. The two trained networks were evaluated using the manually labeled real data. Table IV shows the evaluation results. The comparison experimentally demonstrates that the precise human model improves the performance of the network.

3) Validation of different combinations of height and weight: We assumed 15 combinations of human heights and weights, as summarized in Table I. However, real human heights and weights were not a discrete 15 combinations. In this section, we test the FCN network with validation data with combinations of height and weight not used in the training. We picked combinations of 1000 mm-12 kg, 1500 mm-50 kg, and 2000 mm-80 kg for validation. The metrics used for the validation data are summarized in Table V, where we used the FCN network for validation. We also picked combinations of 1400 mm-20 kg, 1600 mm-50 kg, and 1700 mm-80 kg for comparison from Table I. Note that the training data does not include the validation data. From Table V, the performances for 1000 mm-12 kg, 1500 mm-50 kg, and 2000 mm-80 kg are comparable to those from Table V. Then, we can say that the trained networks sufficiently generalized in terms of the combinations of human heights and weights.

4) Background depth map: The performance of the human segmentation depends on the background scene. In this paper, we mainly focus on a specific site, namely Miraikan.

---

<div style="text-align: center;">TABLE VII: Result of the networks for human segmentation</div>

<table border=1 style='margin: auto; word-wrap: break-word;'><tr><td rowspan="2">Network Input</td><td rowspan="2"></td><td colspan="3">FCN [^1]</td><td colspan="3">U-net [^23]</td><td colspan="3">FCDN [^25]</td><td style='text-align: center; word-wrap: break-word;'>Pointnet [^5]</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>depth</td><td style='text-align: center; word-wrap: break-word;'>xyz</td><td style='text-align: center; word-wrap: break-word;'>depth+xyz</td><td style='text-align: center; word-wrap: break-word;'>depth</td><td style='text-align: center; word-wrap: break-word;'>xyz</td><td style='text-align: center; word-wrap: break-word;'>depth+xyz</td><td style='text-align: center; word-wrap: break-word;'>depth</td><td style='text-align: center; word-wrap: break-word;'>xyz</td><td style='text-align: center; word-wrap: break-word;'>depth+xyz</td><td style='text-align: center; word-wrap: break-word;'>xyz</td></tr><tr><td rowspan="4">Generated data</td><td style='text-align: center; word-wrap: break-word;'>Avg. Acc</td><td style='text-align: center; word-wrap: break-word;'>0.7529</td><td style='text-align: center; word-wrap: break-word;'>0.7199</td><td style='text-align: center; word-wrap: break-word;'>0.7160</td><td style='text-align: center; word-wrap: break-word;'>0.5898</td><td style='text-align: center; word-wrap: break-word;'>0.5696</td><td style='text-align: center; word-wrap: break-word;'>0.5847</td><td style='text-align: center; word-wrap: break-word;'>0.4990</td><td style='text-align: center; word-wrap: break-word;'>0.5090</td><td style='text-align: center; word-wrap: break-word;'>0.5870</td><td style='text-align: center; word-wrap: break-word;'>0.4978</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Precision</td><td style='text-align: center; word-wrap: break-word;'>0.5292</td><td style='text-align: center; word-wrap: break-word;'>0.4776</td><td style='text-align: center; word-wrap: break-word;'>0.5112</td><td style='text-align: center; word-wrap: break-word;'>0.5441</td><td style='text-align: center; word-wrap: break-word;'>0.3481</td><td style='text-align: center; word-wrap: break-word;'>0.4213</td><td style='text-align: center; word-wrap: break-word;'>0.0328</td><td style='text-align: center; word-wrap: break-word;'>0.0564</td><td style='text-align: center; word-wrap: break-word;'>0.0577</td><td style='text-align: center; word-wrap: break-word;'>0.0443</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Recall</td><td style='text-align: center; word-wrap: break-word;'>0.3973</td><td style='text-align: center; word-wrap: break-word;'>0.3388</td><td style='text-align: center; word-wrap: break-word;'>0.3107</td><td style='text-align: center; word-wrap: break-word;'>0.1660</td><td style='text-align: center; word-wrap: break-word;'>0.1477</td><td style='text-align: center; word-wrap: break-word;'>0.1840</td><td style='text-align: center; word-wrap: break-word;'>0.0064</td><td style='text-align: center; word-wrap: break-word;'>0.0086</td><td style='text-align: center; word-wrap: break-word;'>0.7707</td><td style='text-align: center; word-wrap: break-word;'>0.1392</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Threat score</td><td style='text-align: center; word-wrap: break-word;'>0.4062</td><td style='text-align: center; word-wrap: break-word;'>0.3401</td><td style='text-align: center; word-wrap: break-word;'>0.3565</td><td style='text-align: center; word-wrap: break-word;'>0.1584</td><td style='text-align: center; word-wrap: break-word;'>0.1268</td><td style='text-align: center; word-wrap: break-word;'>0.1558</td><td style='text-align: center; word-wrap: break-word;'>0.0035</td><td style='text-align: center; word-wrap: break-word;'>0.0282</td><td style='text-align: center; word-wrap: break-word;'>0.0568</td><td style='text-align: center; word-wrap: break-word;'>0.0295</td></tr><tr><td rowspan="4">Real data</td><td style='text-align: center; word-wrap: break-word;'>Avg. Acc</td><td style='text-align: center; word-wrap: break-word;'>0.7095</td><td style='text-align: center; word-wrap: break-word;'>0.5661</td><td style='text-align: center; word-wrap: break-word;'>0.6178</td><td style='text-align: center; word-wrap: break-word;'>0.5396</td><td style='text-align: center; word-wrap: break-word;'>0.6364</td><td style='text-align: center; word-wrap: break-word;'>0.6070</td><td style='text-align: center; word-wrap: break-word;'>0.4990</td><td style='text-align: center; word-wrap: break-word;'>0.5088</td><td style='text-align: center; word-wrap: break-word;'>0.6050</td><td style='text-align: center; word-wrap: break-word;'>0.5035</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Precision</td><td style='text-align: center; word-wrap: break-word;'>0.7047</td><td style='text-align: center; word-wrap: break-word;'>0.6623</td><td style='text-align: center; word-wrap: break-word;'>0.4835</td><td style='text-align: center; word-wrap: break-word;'>0.5831</td><td style='text-align: center; word-wrap: break-word;'>0.2620</td><td style='text-align: center; word-wrap: break-word;'>0.6126</td><td style='text-align: center; word-wrap: break-word;'>0.0723</td><td style='text-align: center; word-wrap: break-word;'>0.1369</td><td style='text-align: center; word-wrap: break-word;'>0.1239</td><td style='text-align: center; word-wrap: break-word;'>0.0719</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Recall</td><td style='text-align: center; word-wrap: break-word;'>0.3508</td><td style='text-align: center; word-wrap: break-word;'>0.1345</td><td style='text-align: center; word-wrap: break-word;'>0.2238</td><td style='text-align: center; word-wrap: break-word;'>0.0785</td><td style='text-align: center; word-wrap: break-word;'>0.2948</td><td style='text-align: center; word-wrap: break-word;'>0.1894</td><td style='text-align: center; word-wrap: break-word;'>0.0031</td><td style='text-align: center; word-wrap: break-word;'>0.0349</td><td style='text-align: center; word-wrap: break-word;'>0.7848</td><td style='text-align: center; word-wrap: break-word;'>0.0865</td></tr><tr><td style='text-align: center; word-wrap: break-word;'>Threat score</td><td style='text-align: center; word-wrap: break-word;'>0.3919</td><td style='text-align: center; word-wrap: break-word;'>0.1310</td><td style='text-align: center; word-wrap: break-word;'>0.2146</td><td style='text-align: center; word-wrap: break-word;'>0.0802</td><td style='text-align: center; word-wrap: break-word;'>0.2003</td><td style='text-align: center; word-wrap: break-word;'>0.2063</td><td style='text-align: center; word-wrap: break-word;'>0.0035</td><td style='text-align: center; word-wrap: break-word;'>0.0278</td><td style='text-align: center; word-wrap: break-word;'>0.1194</td><td style='text-align: center; word-wrap: break-word;'>0.0487</td></tr></table>

We collected the background data in advance. Here, we experimentally evaluated the effect of the background in the training. For that purpose, we collected outdoor background scenes, while the target scene is the inside of the building. Then, we generated the training data with the proposed pipeline for the outdoor background scene. After we trained the FCN networks with the training data for outdoor background scenes and Miraikan background scenes, the trained networks were evaluated with real depth maps taken at Miraikan. The evaluation results are summarized in Table VI. If the training background scenes were different from the target background, the performance of the network would be degraded, as expected. Therefore, our future works will include the collecting of various types of background data.

### D. Benchmarking existing networks

We evaluated four different types of networks learning with the training data generated by the proposed pipeline. For the FCN, U-net, and FCDN networks, we prepared three different types of input: the depth data only, the xyz data only, and the depth-and-xyz data. We used the xyz data for the input of the Pointnet due to the network structure of the Pointnet. The manually labeled 0.1K real data and the 1K test data generated by the proposed pipeline were used for the evaluation. Note that the training data does not include the test data.

Table VII shows the evaluation results. From these comparisons, the FCN network with the depth information generally resulted in high performance, except for recall in the real data, precision, and recall in the generated data. In terms of recall, the FCDN network with depth-and-xyz information was the best. It could be observed that if a network shows any metric over 0.5 except precision in the test data generated by the proposed pipeline, that network also shows a value over 0.5 for that metric with the real data. Similarly, if the metric except precision for the generated test data is less than 0.5, the metric for the real data is also less than 0.5. We can say that the evaluation with the generated test data helps predict the effectiveness for the real data. An example of prediction with FCN trained by depth and xyz coordinates is illustrated in Figure 6.

### V. CONCLUSION

In this paper, we proposed a fully automated data generation pipeline for human detection using LiDAR. With

![Image](images/4a418a8a259e5b65998b9a7d2e9b1e8a00bbb1444c4ad8ac749f2c1ddc3f4446.jpg)

<div style="text-align: center;">(a) Real data</div>

![Image](images/10c284944d9443108a2cc4cf7f113e9a5cdb7eade234146a0add7aff0c4b7bc1.jpg)

<div style="text-align: center;">(b) Prediction result of FCN trained by depth</div>

<div style="text-align: center;">Fig. 6: Example of result. Human label is colored red while background label is colored blue.</div>

this process, we can easily generate labeled data with any properties for LiDAR. Several approaches were taken to evaluate the generated data and compare the approaches. Following the result, we concluded that our generated data improve training for human detection. We presented 0.1K labeled real datasets and 500K+ generated datasets with human labels. We hope this dataset will support studies in many fields of robotics and computer vision.

We have considered three points for improving our work. The first point is in relation to the human model; although we used a confirmed method to produce the human model, it is not entirely representative of the real world. Then, we will try to consider clothes, backpacks, and other conditions for accurate simulations. The second point regards the background. Only data from Miraikan was used in the current investigation; in the future, we will employ other backgrounds for diversity of data generation. The third point is with regard to a balanced human ratio. Owing to occlusion, the current model ratio is unbalanced with respect to the distance. Filtering by distance or collecting data to balance the ratio may solve this problem.

---

## REFERENCES

[^1]: J. Long, E. Shelhamer, and T. Darrell., “Fully convolutional networks for semantic segmentation.” Proceedings of the IEEE conference on computer vision and pattern recognition (CVPR), pp. 3431–3440, 2015.

[^2]: C. Farabet, C. Couprie, L. Najman, and Y. LeCun., “Learning hierarchical features for scene labeling.” IEEE transactions on pattern analysis and machine intelligence, vol. 35, pp. 1915–1929, 2013.

[^3]: L. Chen, G. Papandreou, F. Schroff, and H. Adam, “Rethinking atrous convolution for semantic image segmentation,” CoRR, vol. abs/1706.05587, 2017. [Online]. Available: <http://arxiv.org/abs/1706.05587>

[^4]: B. Wu, A. Wan, X. Yue, and K. Keutzer, “Squeezeseg: Convolutional neural nets with recurrent CRF for real-time road-object segmentation from 3d lidar point cloud,” CoRR, vol. abs/1710.07368, 2017. [Online]. Available: <http://arxiv.org/abs/1710.07368>

[^5]: C. R. Qi, H. Su, K. Mo, and L. J. Guibas, “Pointnet: Deep learning on point sets for 3d classification and segmentation.” Proceedings of the IEEE conference on computer vision and pattern recognition (CVPR), pp. 77–85, 2017.

[^6]: I. Laina, C. Rupprecht, V. Belagiannis, F. Tombari, and N. Navab, “Deeper depth prediction with fully convolutional residual networks,” in 3D Vision (3DV), 2016 Fourth International Conference on. IEEE, 2016, pp. 239–248.

[^7]: F. Liu, C. Shen, and G. Lin, “Deep convolutional neural fields for depth estimation from a single image,” in Proceedings of the IEEE Conference on Computer Vision and Pattern Recognition, 2015, pp. 5162–5170.

[^8]: I. B. Barbosa, M. Cristani, A. Del Bue, L. Bazzani, and V. Murino, "Re-identification with rgb-d sensors," in European Conference on Computer Vision. Springer, 2012, pp. 433–442.

[^9]: M. Munaro, A. Basso, A. Fossati, L. Van Gool, and E. Menegatti, "3d reconstruction of freely moving persons for re-identification with a depth sensor," in Robotics and Automation (ICRA), 2014 IEEE International Conference on. IEEE, 2014, pp. 4512–4519.

[^10]: D. Kastaniotis, I. Theodorakopoulos, C. Theoharatos, G. Economou, and S. Fotopoulos, “A framework for gait-based recognition using kinect,” Pattern Recognition Letters, vol. 68, pp. 327–335, 2015.

[^11]: A. Geiger, P. Lenz, and R. Urtasun, "Are we ready for autonomous driving? the kitti vision benchmark suite," in Conference on Computer Vision and Pattern Recognition (CVPR), 2012.

[^12]: C. Premebida, J. Carreira, J. Batista, and U. Nunes, “Pedestrian detection combining rgb and dense lidar data,” in Intelligent Robots and Systems (IROS 2014), 2014 IEEE/RSJ International Conference on. IEEE, 2014, pp. 4112–4117.

[^13]: D. Levi, N. Garnett, E. Fetaya, and I. Herzlyia, “Stixelnet: A deep convolutional network for obstacle detection and road segmentation.” in BMVC, 2015, pp. 109–1.

[^14]: M. Johnson-Roberson, C. Barto, R. Mehta, S. N. Sridhar, K. Rosaen, and R. Vasudevan, “Driving in the matrix: Can virtual worlds replace human-generated annotations for real world tasks?” in Robotics and Automation (ICRA), 2017 IEEE International Conference on. IEEE, 2017, pp. 746–753.

[^15]: S. R. Richter, V. Vineet, S. Roth, and V. Koltun, “Playing for data: Ground truth from computer games,” in European Conference on Computer Vision. Springer, 2016, pp. 102–118.

[^16]: Miraikan, <https://www.miraikan.jst.go.jp>, accessed in 2018 May 27.

[^17]: V. LiDAR, <https://velodynelidar.com//hdl-32e.html>, accessed in 2018 May 25.

[^18]: M. Mochimaru, M. Kouchi, N. Miyata, M. Tada, Y. Yoshida, K. Aoki, K. Kawachi, and Y. Motomura, “Dhaiba: Functional human models to represent variation of shape, motion and subjective assessment,” SAE Technical Paper, Tech. Rep., 2006.

[^19]: Y. Endo, M. Tada, and M. Mochimaru, “Hand modeling and motion reconstruction for individuals,” Int. J. of Automation Technology Vol. vol. 8, no. 3, 2014.

[^20]: —, “Estimation of arbitrary human models from anthropometric dimensions,” in International Conference on Digital Human Modeling and Applications in Health, Safety, Ergonomics and Risk Management. Springer, 2015, pp. 3–14.

[^21]: Y. Kobayashi, H. Hobara, T. A. Heldoorn, M. Kouchi, and M. Mochimaru, “Age-independent and age-dependent sex differences in gait pattern determined by principal component analysis,” Gait & posture, vol. 46, pp. 11–17, 2016.

[^22]: S. Hong, H. Noh, and B. Han, “Decoupled deep neural network for semi-supervised semantic segmentation.” Advances in neural information processing systems (NIPS), pp. 1495–1503, 2015.

[^23]: O. Ronneberger, P. Fischer, and T. Brox, "U-net: Convolutional networks for biomedical image segmentation," pp. 234–241, 2015.

[^24]: D. Eigen and R. Fergus, “Predicting depth, surface normals and semantic labels with a common multi-scale convolutional architecture.” Proceedings of the IEEE International Conference on Computer Vision (ICCV), pp. 2650–2658, 2015.

[^25]: S. Jégou, M. Drozdzal, D. Vazquez, A. Romero, and Y. Bengio, “The one hundred layers tiramisu: Fully convolutional densenets for semantic segmentation,” in Computer Vision and Pattern Recognition Workshops (CVPRW), 2017 IEEE Conference on. IEEE, 2017, pp. 1175–1183.

[^26]: F. Iandola, M. Moskewicz, S. Karayev, R. Girshick, T. Darrell, and K. Keutzer, “Densenet: Implementing efficient convnet descriptor pyramids,” arXiv preprint arXiv:1404.1869, 2014.

[^27]: D. P. Kingma and J. Ba, “Adam: A method for stochastic optimization,” CoRR, vol. abs/1412.6980, 2014. [Online]. Available: <http://arxiv.org/abs/1412.6980>

[^28]: I. T. Jolliffe and D. B. Stephenson, Forecast verification: a practitioner's guide in atmospheric science. John Wiley & Sons, 2003.
