Mercurial Hosting > traffic-intelligence
diff tracking.cfg @ 948:584b9405e494
added safety analysis parameters for motion patterns
author | Nicolas Saunier <nicolas.saunier@polymtl.ca> |
---|---|
date | Fri, 21 Jul 2017 12:11:55 -0400 |
parents | b1e8453c207c |
children | a9b2beef0db4 |
line wrap: on
line diff
--- a/tracking.cfg Fri Jul 21 11:31:42 2017 -0400 +++ b/tracking.cfg Fri Jul 21 12:11:55 2017 -0400 @@ -75,7 +75,7 @@ # segmentation distance in feature grouping (world distance unit or px) mm-segmentation-distance = 1.81511847456 # maximum distance between features for grouping (world distance unit or px) -max-distance = 5 +mm-max-distance = 5 # minimum cosine of the angle between the velocity vectors for grouping min-velocity-cosine = 0.8 # minimum average number of features per frame to create a vehicle hypothesis @@ -86,7 +86,7 @@ # maximum speed when predicting future motion (km/h) max-predicted-speed = 50 # time horizon for collision prediction (s) -prediction-time-horizon = 5 +prediction-time-horizon = 150 # collision distance threshold (m) collision-distance = 1.8 # option to compute crossing zones and predicted PET @@ -108,4 +108,11 @@ # use feature positions and velocities for prediction use-features-prediction = true # use constant speed (motion pattern based prediction) -constant-speed = false \ No newline at end of file +constant-speed = false +# point distance threshold, for the chosen metric for trajectory matching using LCSS +max-lcss-distance = 2. +# distance metric for trajectory matching using LCSS +lcss-metric = cityblock +# similarity threshold for trajectory matching on normalized LCSS +min-lcss-similarity = 0.4 +# minimum past feature length for past trajectory matching for motion prediction -> using min-feature-time \ No newline at end of file