<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Algorithm for Predicting the Trajectory of Road Users to Automate Control of an Autonomous Vehicle*</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Andrey Azarchenkov</string-name>
          <email>azarchenkovaa@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Bryansk State Technical University</institution>
          ,
          <addr-line>Bryansk</addr-line>
          ,
          <country country="RU">Russia</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>One of the problems faced by developers of artificial intelligence algorithms when creating car control systems is that the actions of other road users are difficult to predict and have a large variability. Even if we assume that all actions comply with traffic rules and participants do not make mistakes, that is, to bring the actual environment closer to the ideal, the task of automating vehicle control still contains many difficulties. This paper describes what difficulties exist in the field of predicting the trajectory of objects, shows concepts that will help in solving this problem, and also describes a particular method of forecasting, which allows you to make a forecast for cars moving along traffic lanes. The main forecasting stages and the results of testing the method collected by using a ready-made data set are given. The results presented in the form of a set of metrics, are compared with another algorithm for predicting trajectories. As a result, the advantages and disadvantages of the created solution were identified.</p>
      </abstract>
      <kwd-group>
        <kwd>Trajectory Prediction</kwd>
        <kwd>Autonomous Driving Car</kwd>
        <kwd>Regression Model</kwd>
        <kwd>NuScenes Dataset</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        [0000-0003-0702-3662]
Driving a car is a complex process that requires drivers to understand the situation and
control many dynamic processes in real time, as well as making decisions to react to
these processes in seconds. Unfortunately, we can say that not all people cope with this
task, which is confirmed by negative statistics. In 2019, 164,318 accidents were
committed on the territory of Russia, in which 16,981 people were killed [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Despite all
the measures taken to minimize the number of accidents, there is no decreasing trend
in these indicators.
      </p>
      <p>
        In addition, human errors are the cause of up to 94% of accidents [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Based on this
fact, it can be assumed that eliminating the unreliable human factor could potentially
save thousands of lives. Recent advances in artificial intelligence and high-performance
computing allow to develop in this direction.
      </p>
      <p>
        Creating a fully autonomous car requires solving many of the problems faced by a
person driving a car. One of these tasks is to assess the trajectory of other road users. If
we consider the solution of this problem as a separate subsystem, different types of
information can be fed to its input. In the simplest case, this is different information
about the physical properties of the object, such as speed, acceleration, orientation, and
others [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The methods that use this information are the simplest to implementing, but
they can't be said to have high accuracy.
      </p>
      <p>
        The most popular group of methods for predicting the trajectory of movement, in
terms of the number of scientific papers, is based on the use of the trajectory of
movement from the past. In most cases, this problem is solved using neural networks. This
is because they are good at identifying patterns, in this case patterns from the trajectory
of movement. In addition, a popular solution for this method is to use recurrent layers
[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], especially such recurrent layers as LSTM [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. There is also a large
number of publicly available data sets containing motion paths that can be used for
neural network training [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
      <p>
        The disadvantage of these methods is that they consider the trajectory of a single
object, without taking into account others. The solution to this problem is to use the
input representation [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] (Fig 1). The principles of generating such an image may differ,
but the general points are the presence of layers with objects, as well as the presence of
roads in the image [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ].
A number of methods based on using images from the camera should be singled out
separately. The idea is that the object is detected in the image, then the neural network
predicts its position on the same frame. Most often, recurrent layers are also used for
this purpose. [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. Then, having the calibration parameters of the camera,
we can understand the position of the object in space [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ].
      </p>
      <p>Algorithm for Predicting the Trajectory of Road Users to Automate Control 3
In addition, it is important to separate the task of trajectory planning for an
autonomous driving car and predicting traffic paths for other objects. Although the input and
output data for this problem are similar, the methods for solving it are different. The
subsystem based on input data returns the expected position of an object or objects. The
position can be specified exactly, or it can be a sequence of points or a motion vector.
As part of the task, it is planned to determine the sequence of points. The selected time
for making the forecast is 6 seconds.</p>
      <p>
        nuScenes set was chosen as the data set for testing the developed method [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]. A
special feature of this set is the amount of information marked up. In addition to the
classic object detection and segmentation tasks, the data set provides physical
characteristics of each object, its exact position in space, and tracking. Special attention is
paid to information storage. To work with a data set, a library provided by developers
is used that not only provides access to objects, but also allows to filter them by various
criteria. The data set is divided into 1000 scenes, each lasting 20 seconds. The vehicle
collecting data was equipped with an omnidirectional lidar, cameras, radars, GPS and
IMU sensors. In total, the set contains 1,400,000 images, and 390,000 lidar images. It
is important to have marked maps for all the sections where data were collected. This
allows to define the traffic lane for each object that it moves along.
2
2.1
      </p>
      <p>Approach to predict the trajectory</p>
    </sec>
    <sec id="sec-2">
      <title>Description of prediction method</title>
      <p>After analyzing existing scientific papers, as well as industrial solutions in the field
of trajectory forecasting, several concepts were identified that can improve the results
of the work:
• Application of algorithms depending on the class of the object. Since the
trajectory is predicted for objects that have different behavior and the class is
known in advance, it is possible to predict the trajectory of their movement in
different ways.
• Division of algorithms depending on the position of the object. Objects of the
same class may have different behaviors depending on their location.
• Use of maps prepared in advance. The main task for which using the module
under development is needed is related to predicting the trajectory of the car
along the traffic lanes. Information about the position of roads can be
considered static, since changes to existing roads are rare. At the same time, while
driving on the road, the absolute majority of cars move along the lane. This
applies to both straight sections and turns of the road. In this regard,
information about the position of lanes can be used to predict the trajectory of
traffic in cases where the orientation of the car differs slightly from the direction
of the road. To do this, the current position of the car is projected to the middle
of the lane, and from this position an angular coordinate is defined, equal to
the distance that the car will travel according to the forecast. The resulting
road section is shifted to the current position of the car, and an adjustment is
made for its orientation.
•
•
•</p>
      <p>Building a regression model for speed prediction. To implement the previous
idea, we need to know the position of the road lane in space and the predicted
distance of car movement. Since it is planned to use a static time interval when
predicting the trajectory, the distance traveled can be determined by knowing
the speed and acceleration of the object. However, for a long period of time,
the acceleration that we know before making the forecast cannot be considered
constant for the entire forecast section. In addition, drivers often adjust the
speed of the vehicle using similar models. In this regard, to increase the
accuracy, it was decided to use the predicted final speed, which can be obtained
using a regression model. To train the model, it was decided to use the initial
speed and acceleration of the object, as well as changing the orientation of the
object, in comparison with the state from the past.</p>
      <p>Calculating the probabilities of predicted trajectories. Firstly, we can use
probabilities to make a decision about using trajectories. Secondly, using a single
algorithm, we can get a number of trajectories that also need to be compared.
Finally, the obtained probabilities can be used with subsequent modules or the
prediction module itself for further calculation.</p>
      <p>Using recurrent layers to predict the trajectory if there is no map. Based on the
analysis of existing approaches, we can conclude that recurrent layers are used
in most neural networks that perform trajectory prediction.
2.2.</p>
    </sec>
    <sec id="sec-3">
      <title>Trajectory prediction using maps prepared</title>
      <p>Initially, the prediction task was implemented for cars that move along traffic lanes.
Within the task, a trajectory forecast is made for 6 seconds, with a frequency of 2 Hertz.
Accordingly, the resulting trajectory includes 12 points.</p>
      <p>The algorithm consists of the following steps:
• receiving data;
• search for lanes;
• calculation of the final speed;
• calculation of angular coordinates for each suitable lane;
• calculation of trajectory points.</p>
      <p>Figure 1 shows examples of the obtained trajectories. Here and further the following
rules will be applied when making up drawings: the blue trajectory represents the real
trajectory of the object, while the red one is predicted using the algorithm being
developed. The green one is predicted using a third-party algorithm where the latter is
present. When implementing the algorithm, the following complications were identified:
• Within the selected data set the current lane ends at the moment when there is
an alternative path. This raises the problem of choosing a new lane. This
problem was solved by constructing a function between the angle of orientation
change and the speed. This angle was calculated as the difference between the
current orientation and the direction of the alternate lane. This method is
effective when the choice is limited to two options, for example, moving straight
and turning. However, there is a high probability of error in lanes where
multiple turns are possible. In real life, this task is also difficult and is solved by
determining the speed of the car by the driver, as well as using turn signals,</p>
      <p>Algorithm for Predicting the Trajectory of Road Users to Automate Control 5
•
which is a more effective way. In this regard, in situations where multiple
choices are possible, it was decided to consider both trajectories. First, these
trajectories have a partial intersection as a part of the current lane, and second,
in the case when the turn signal is not visible, the driver in reality also allows
both versions of trajectories. However, it should be noted that we are talking
about situations when the car is moving along the lane, and is not making a
lane change.</p>
      <p>In areas where there is a large number of lanes, the starting lane selection may
not be correct, due to the car being too far off-center. It was decided to
calculate paths using several lanes within a given radius, with the probability of
each of them inversely proportional to the distance from the object to the lane
center.</p>
      <p>The training part of the dataset was used to train the regression model, but since
nuScenes test dataset contains many objects, including inanimate objects which
location and physical parameters are also different, a number of filters were applied to the
entire training sample:
• filtering by class, only transport was used;
• speed filtering, many objects have zero speed;
• filtering by tracking time. For training, the object speed was used after 6
seconds, relative to the prediction;
• filtering by acceleration and direction of the object.</p>
      <p>As a result, 65,000 training objects were obtained. 90% percent for training, 10% for
accuracy testing. Several regression models with the selected parameters were tested
(Table 1). The speed of the models was also taken into account, but all the models under
consideration showed acceptable results at the specified parameter values, so the speed
comparison was not performed. The standard error between the predicted speed value
and the correct one (1) was used to estimate accuracy. This metric allows to evaluate
errors with different signs, in addition, its feature is that large errors are taken into
account to a greater extent, due to using the square of difference in values.</p>
      <p>= 1 ∑ =1(  −  ̌ )2</p>
      <p>not have very accurate results, since they strongly depend on the correct definition of
the trajectory length.</p>
      <p>To compare the results, we used one of the standard algorithms for this problem, which
means generation of trajectory points depending on the current speed and orientation</p>
      <p>Algorithm for Predicting the Trajectory of Road Users to Automate Control 7
of the object. The algorithm returns an exceptionally straight trajectory. This method
was considered as a basic one.</p>
      <p>In addition, to demonstrate the advantages of the regression model and show the
relationship between metrics and the trajectory length, the results for the algorithm under
development were considered, by replacing the regression model with the constant
speed, as well as changing the speed based on the initial acceleration. In accordance
with the Euler method, integration was performed, that is, half of the object's
acceleration was added to the initial speed, since the time between two steps is 0.5 seconds.
This operation was carried out for two and for 12 steps. As a result, the following
indicators were obtained for 7,600 objects (Table 2).
Analyzing the examples, we can conclude that the main reason that negatively affects
the accuracy is errors in predicting the length of the trajectory. However, it should be
noted that despite its impact on metrics, this problem is less significant in real
conditions. In addition, it is important to note the following fact: most of the considered
trajectories are straight. Often, the prediction of such trajectories is not problematic and
the base method copes with this well. However, the main difficulty is represented by
curved paths. Figure 3 shows examples of such paths. Most of the methods of trajectory
prediction aim at curved trajectories. At the same time, due to different number of cases
of linear motion, the effect of the developed algorithm, in terms of predicting a curved
trajectory, is lost in comparison with the basic one. Therefore, it was decided to
calculate the metrics considered earlier not on all available objects, but on objects which
orientation change is greater than 0.1 radian, that is, the angle of rotation of the object
changed by 0.1 radian between the current position and the previous one in the training
sample. According to the results of this filtering, 1,772 objects were obtained. Table 3
shows the results. It can be seen that the difference between the two methods has
increased significantly.
At this stage, the feasibility of the concept was tested by predicting the trajectory of
cars based on the use of maps prepared in advance. Analyzing the results of the
algorithm on the selected data set, we can conclude that this method allows to predict the
direction of the car movement with high accuracy. First of all, the predicted trajectory
length has a negative impact on metrics. However, in real-world problems, the accuracy
of the trajectory length is less important.</p>
      <p>The resulting algorithm can be used to predict car trajectories in unmanned control
systems. In such systems, it is necessary to implement this task, since it is not enough
for an unmanned vehicle to simply detect an object in order to perform maneuvers.
Without information about further movement of the object, it is impossible to move,
because the danger of a particular maneuver is not clear.</p>
      <p>In the future, it is planned to implement a trajectory prediction method for cars that
make changes or move off the road, as well as for other objects, such as pedestrians and
two-wheeled transport. The implemented set of algorithms will be tested on nuScenes
dataset.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. Road safety indicators, http://stat.gibdd.ru/, last accesses 19/07/
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Singh</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <article-title>Critical reasons for crashes investigated in the national motor vehicle crash causation survey</article-title>
          .
          <source>Technical Report DOT HS 812 115</source>
          ,
          <string-name>
            <given-names>National</given-names>
            <surname>Highway Traffic Safety Administration</surname>
          </string-name>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Scholler</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aravantinos</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lay</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Knoll</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <article-title>What the Constant Velocity Model Can Teach Us About Pedestrian Motion Prediction</article-title>
          . arXiv:
          <year>1903</year>
          .07933v3 (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Wenjing</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yuan</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tingting</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chenyang</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <article-title>Trajectory Prediction with Recurrent Neural Networks for Predictive Resource Allocation</article-title>
          .
          <source>14th IEEE International Conference on Signal Processing (ICSP)</source>
          pp.
          <fpage>1</fpage>
          -
          <lpage>8</lpage>
          . (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Alahi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Goel</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ramanathan</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Robicquet</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fei-Fei</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savares</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Social</surname>
            <given-names>LSTM</given-names>
          </string-name>
          :
          <article-title>Human Trajectory Prediction in Crowded Spaces IEEE Conference on Computer Vision and Pattern Recognition (CVPR</article-title>
          ), pp.
          <fpage>2</fpage>
          -
          <lpage>6</lpage>
          . (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6. The Autoware Foundatiion, https://www.autoware.org/, last accessed 19/06/
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Vemula</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Muelling</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oh</surname>
            ,
            <given-names>J. Social</given-names>
          </string-name>
          <string-name>
            <surname>Attention</surname>
          </string-name>
          : Modeling Attention in Human Crowds arXiv:
          <fpage>1710</fpage>
          .
          <string-name>
            <surname>04689v2</surname>
          </string-name>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Deo</surname>
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Trivedi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>Convolutional Social Pooling for Vehicle Trajectory Prediction arXiv:</article-title>
          <year>1805</year>
          .06771v1,
          <year>2018</year>
          . - 9 p.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. US Highway 101 Dataset, https://www.fhwa.dot.gov/publications/research/operations/07030/index.cfm, last accesses 19/07/
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <article-title>Interstate 80 Freeway Dataset</article-title>
          . https://www.fhwa.dot.gov/publications/research/operations/06137/, last accesses 19/07/
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Djuric</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Radosavljevic</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cui</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nguyen</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chou</surname>
            ,
            <given-names>F. C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lin</surname>
            ,
            <given-names>T. H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nitin</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schneider</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          :
          <article-title>Uncertainty-aware Short-term Motion Prediction of Traffic Actors for Autonomous Driving</article-title>
          . CoRR abs/
          <year>1808</year>
          .05819, https://arxiv.org/abs/
          <year>1808</year>
          .05819 (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Cui</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Radosavljevic</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chou</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lin</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nguyen</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Huang</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schneider</surname>
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Djuric</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          <article-title>Multimodal Trajectory Predictions for Autonomous Driving using Deep Convolutional Networks 2019</article-title>
          <source>International Conference on Robotics and Automation (ICRA)</source>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>5</lpage>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Grigore</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Boulton</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Beijbom</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wolff</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <article-title>CoverNet: Multimodal Behavior Prediction using Trajectory arXiv:</article-title>
          <year>1911</year>
          .10298v1 (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14. GTC 2020:
          <article-title>PredictionNet: Predicting the Future in Multi-Agent Environments for Autonomous Vehicle Applications</article-title>
          , https://developer.nvidia.com/gtc/2020/video/s21899-vid,
          <source>last accessed 06/20.</source>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Ma</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhu</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yang</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Manocha</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <article-title>TrafficPredict: Trajectory Prediction for Heterogeneous Traffic</article-title>
          . arXiv:
          <year>1811</year>
          .02146v5 (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Rasouli</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kotseruba</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kunic</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tsotso</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <article-title>PIE: A Large-Scale Dataset and Models for Pedestrian Intention Estimation andTrajectory Prediction</article-title>
          . IEEE/CVF International Conference on Computer Vision (ICCV), p.
          <volume>10</volume>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Yau</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Xuo</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Choi</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Crandall</surname>
            ,
            <given-names>D. J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Atkins</surname>
            ,
            <given-names>E. M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dariush</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <article-title>Egocentric Vision-based Future Vehicle Localization for Intelligent Driving Assistance Systems</article-title>
          . arXiv:
          <year>1809</year>
          .07408v2 (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Siswantoro</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Prabuwono</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Abdullah</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <article-title>Real World Coordinate from Image Coordinate Using Single Calibrated Camera Based on Analytic Geometry</article-title>
          .
          <source>International Multi-Conference on Artificial Intelligence Technology</source>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>11</lpage>
          (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>19. Nuscenes dataset, https://www.nuscenes.org, last accesed 19/06/20.</mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>