changeset 976:7f5cbdc107c5

corrected bug in converting time horizon to frames for internal computations (results for TTC, pPET and PET will be in frames)
author Nicolas Saunier <nicolas.saunier@polymtl.ca>
date Mon, 05 Feb 2018 16:41:36 -0500
parents 4a262dc896c2
children 9c27a0315c4d
files python/storage.py tracking.cfg
diffstat 2 files changed, 2 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/python/storage.py	Fri Feb 02 17:07:13 2018 -0500
+++ b/python/storage.py	Mon Feb 05 16:41:36 2018 -0500
@@ -1372,7 +1372,7 @@
         
         # Safety parameters
         self.maxPredictedSpeed = config.getfloat(self.sectionHeader, 'max-predicted-speed')/3.6/self.videoFrameRate
-        self.predictionTimeHorizon = config.getfloat(self.sectionHeader, 'prediction-time-horizon')
+        self.predictionTimeHorizon = config.getfloat(self.sectionHeader, 'prediction-time-horizon')*self.videoFrameRate
         self.collisionDistance = config.getfloat(self.sectionHeader, 'collision-distance')
         self.crossingZones = config.getboolean(self.sectionHeader, 'crossing-zones')
         self.predictionMethod = config.get(self.sectionHeader, 'prediction-method')
--- a/tracking.cfg	Fri Feb 02 17:07:13 2018 -0500
+++ b/tracking.cfg	Mon Feb 05 16:41:36 2018 -0500
@@ -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 = 150
+prediction-time-horizon = 5.0
 # collision distance threshold (m)
 collision-distance = 1.8
 # option to compute crossing zones and predicted PET