Drive Cycle Data from the 3D Urban Traffic Simulator (ABM) in Unity (version 1.1.0)

This repository contains datasets from the 3D Urban Traffic Simulator ABM:<br>Each vehicle type, PHEV and ICEV were simulated across nine different speed limit adherence and density scenarios. The output data columns are:AgentID: the unique agent identifier.xAxisPos: the x-axis position of the agent.zAxisPos: the y-axis position of the agent.collisions: the total number of times a vehicle has collided with another.topSpeed(mph): the top speed the vehicle is set to achieve throughout its drive cycle.currentSpeed(mph): the current speed of the vehicle in mph.distanceOfTravel(meters): the distance the vehicle has travelled over its drive cycle.raycastLength: the length at which the vehicle can identify objects, 1 - very short to 10 high vision distance.tractionControl: traction control initiated; some vehicles will have traction control, others will not; this is entirely arbitrary.VelocityMagnitude(BETA): the magnitude of the velocity for the vehicle.VehicleMass: the vehicle weight in kg.Downforce: the force applied to the vehicle to create more grip, 0.1 - small force to 10.0 - more force.date-time: date and timestamps for each data point collected, currently its milliseconds and multiple actions by the raw physics engine can occur throughout the simulation. Therefore, large amounts of data points are collected for each run in a short space of time.File path:Data/PHEV or ICEV/- MC1: 10 Vehicles, all vehicles do not adhere to speed limits.- MC2: 10 Vehicles, half of which do not adhere to speed limits.- MC3: 10 Vehicles, all adhere to speed limits.- MC4: 50 Vehicles, all vehicles do not adhere to speed limits.- MC5: 50 Vehicles, half of which do not adhere to speed limits.- MC6: 50 Vehicles, all adhere to speed limits.- MC7: 100 Vehicles, all vehicles do not adhere to speed limits.- MC8: 100 Vehicles, half of which do not adhere to speed limits.- MC9: 100 Vehicles, all adhere to speed limits.