Reading the results
The results are stored in the results
folder. The subfolder with the results of an specific simulation will have the date and time of the moment when it was launched as a name in %Y-%m-%d_%H-%M-%S
format.
For each simulation there are four files that are saved: user_trips.csv
, bike_trips.csv
, config.json
and app.log
.
#
User tripsThe structure of the user_trips.csv
file can be found in the UserTrip.py
under the folder src
. The format is the same for the three types of system SB= Station-based, DL= Dockless, AUT= Autonomous. This output file contains the following colums:
Parameter | Description | Type of system |
---|---|---|
user_id | The id of the user who made the trip | SB, DL, AUT |
status | The user finished the tip (finished), there were no bikes in a walkable distance (no_bikes), there was no walkable station at the beginning of the trip (not_walkable_stations), there was no end station walkable or not walkable(no_end_station) | SB |
bike_id | The id of the bike used for that trip | SB, DL, AUT |
mode | 0=Station-based, 1=Dockless, 2= Autonomous | SB, DL, AUT |
time_departure | Elapsed time at the beginning of the trip [s] | SB, DL, AUT |
time_target | Elapsed time at arrival [s] | SB, DL, AUT |
time_walk_origin | Duration of the walk from the departure point to the bike/station [s] | SB, DL |
time_ride | Duration of the bike ride [s] | SB, DL, AUT |
time_wait | Duration of the wait time at the beginning of the trip [s] | AUT |
time_walk_destination | Duration of the walk at the end of the trip from the station to the destination [s] | SB |
origin_lon | Longitude of the departure point | SB, DL, AUT |
origin_lat | Latitude of the departure point | SB, DL, AUT |
destination_lon | Longitude of the destination point | SB, DL, AUT |
destination_lat | Latitude of the destination point | SB, DL, AUT |
origin_visited_stations | List of the ids of the stations visited until finding an available bike | SB |
destination_visited_stations | List of the ids of the stations visited until finding an available dock | SB |
origin_station | The id of the station where the user got the bike | SB |
destination_station | The id of the station where the user left the bike | SB |
instant_bike | Indicates if the used bike was an instantaneously rebalanced bike (1) or not (0) | SB, AUT |
instant_dock | Indicates if the used dock was liberated by an instantaneously rebalanced bike (1) or not (0) | SB |
bike_lon | Longitude of the location of the bike chosen for the trip | DL, AUT |
bike_lat | Latitude of the location of the bike chosen for the trip | DL, AUT |
#
Bike tripsThe structure of the bike_trips.csv
file can be found in the BikeTrip.py
under the folder src
. The format is the same for the three types of system SB= Station-based, DL= Dockless, AUT= Autonomous. This output file contains the following columns:
Parameter | Description | Type of system |
---|---|---|
bike_id | The id of the bike that made the trip | SB, DL, AUT |
user_id | The id of the user who made the trip | SB, DL, AUT |
mode | 0=Station-based, 1=Dockless, 2= Autonomous | SB, DL, AUT |
trip_type | 1=User drive, 2=Charge trip, 3=Rebalancing trip | AUT |
time_departure | Elapsed time at the beginning of the trip [s] | SB, DL, AUT |
time_ride | Duration of the bike ride [s] | SB, DL, AUT |
time_charge | Duration of the bike charging process [s] | AUT |
instant_bike | Indicates if the used bike was an instantaneously rebalanced bike (1) or not (0) | SB, AUT |
instant_dock | Indicates if the used dock was liberated by an instantaneously rebalanced bike (1) or not (0) | SB |
origin_station | The id of the station where the user got the bike | SB |
destination_station | The id of the station where the user left the bike | SB |
origin_lon | Longitude of the departure point | SB, DL, AUT |
origin_lat | Latitude of the departure point | SB, DL, AUT |
destination_lon | Longitude of the destination point | SB, DL, AUT |
destination_lat | Latitude of the destination point | SB, DL, AUT |
battery_in | Battery at the beginning of the trip/process | AUT |
battery_out | Battery at the end of the trip/process | AUT |
#
ConfigurationThe config.json
file saves the parameters that were used when running this simulation
#
LoggingThe app.log
file saves the log of the actions.
The logging can be activated and deactivated on the Results.py file, commenting out the self.setup_log() command.