Mercurial Hosting > traffic-intelligence
comparison python/storage.py @ 755:f3aeb0b47eff dev
comment improvement: vissim time is multiplied to get integers similar to frame numbers
author | Nicolas Saunier <nicolas.saunier@polymtl.ca> |
---|---|
date | Fri, 30 Oct 2015 14:15:03 -0400 |
parents | 782e8fd3672c |
children | a73f43aac00e |
comparison
equal
deleted
inserted
replaced
754:782e8fd3672c | 755:f3aeb0b47eff |
---|---|
761 printDBError(error) | 761 printDBError(error) |
762 | 762 |
763 | 763 |
764 def loadTrajectoriesFromVissimFile(filename, simulationStepsPerTimeUnit, objectNumbers = None, warmUpLastInstant = None, usePandas = False, nDecimals = 2, lowMemory = True): | 764 def loadTrajectoriesFromVissimFile(filename, simulationStepsPerTimeUnit, objectNumbers = None, warmUpLastInstant = None, usePandas = False, nDecimals = 2, lowMemory = True): |
765 '''Reads data from VISSIM .fzp trajectory file | 765 '''Reads data from VISSIM .fzp trajectory file |
766 simulationStepsPerTimeUnit is the number of simulation steps per unit of time used by VISSIM | 766 simulationStepsPerTimeUnit is the number of simulation steps per unit of time used by VISSIM (second) |
767 for example, there seems to be 5 simulation steps per simulated second in VISSIM, | 767 for example, there seems to be 10 simulation steps per simulated second in VISSIM, |
768 so simulationStepsPerTimeUnit should be 5, | 768 so simulationStepsPerTimeUnit should be 10, |
769 so that all times correspond to the number of the simulation step (and can be stored as integers) | 769 so that all times correspond to the number of the simulation step (and can be stored as integers) |
770 | 770 |
771 Objects positions will be considered only after warmUpLastInstant | 771 Objects positions will be considered only after warmUpLastInstant |
772 (if the object has no such position, it won't be loaded) | 772 (if the object has no such position, it won't be loaded) |
773 | 773 |