This repository has been archived by the owner on Jan 20, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
format.txt
160 lines (126 loc) · 8.09 KB
/
format.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
The following data files should be included in the data folder:
arc_data.txt
assignment_data.txt
node_data.txt
objective_data.txt
od_data.txt
operator_cost_data.txt
problem_data.txt
transit_data.txt
user_cost_data.txt
vehicle_data.txt
The contents of these files will be explained below. Most include IDs for each of their elements. For the purposes of our solution algorithm, these are assumed to consecutive integers beginning at 0, and this is how they will be treated for the purposes of array placement.
Unless otherwise specified, the following units are used:
cost = dollars
distance = miles
time = minutes
================================================================================
arc_data.txt
================================================================================
Information related to all arcs.
Contains the following columns:
-ID: Unique identifying number.
-Type: Arc type ID. The types in use are:
0: line arc
1: boarding arc
2: alighting arc
3: core network walking arc (stop nodes only)
4: accessibility network walking arc (stop nodes, population centers, and facilities)
-Line: Line ID of a line arc, and -1 otherwise.
-Tail: Node ID of the arc's tail.
-Head: Node ID of the arc's head.
-Time: Constant part of travel time of arc. Boarding arcs, whose travel time is based on the line frequency, have a listed time of 0.
================================================================================
assignment_data.txt
================================================================================
Information related to the Spiess and Florian assignment model.
Contains the following rows:
-Epsilon: Optimality gap threshold to use for ending the Frank-Wolfe algorithm.
-Cutoff: Iteration cutoff for the Frank-Wolfe algorithm.
-Elements: Number of parameters listed on the following rows. Currently set to 2.
-alpha: Alpha parameter of the conical congestion function.
-beta: Beta parameter of the conical congestion function. By definition it should equal (2*alpha-1)/(2*alpha-2), and is included here only for convenience.
================================================================================
node_data.txt
================================================================================
Information related to all nodes.
Contains the following columns:
-ID: Unique identifying number. Used to reference specific nodes in the other data files.
-Name: Name of the node. Most stops are simply called "Stop" followed by their ID number. Boarding nodes also append the name of their line. Population centers and primary care facilities use their real names.
-Type: Node type ID. The types in use are:
0: stop node
1: boarding node
2: population center
3: primary care facility
-Line: Line ID of a boarding node, and -1 otherwise.
-Value: Population of a population center, facility weight of a primary care facility, and -1 otherwise.
================================================================================
objective_data.txt
================================================================================
Information related to defining the objective function and related accessibility metrics.
Contains the following rows:
-Elements: Number of parameters listed on the following rows. Currently set to 3.
-Lowest: Number of lowest-metric population centers to take for the objective function.
-FCA_Cutoff: Time cutoff to define catchment areas for the 2SFCA metric.
-Gravity_Falloff: Exponent used to define distance falloff in gravity metric. This should be a positive value, and will be treated as negative in the program. A larger value means faster falloff.
================================================================================
od_data.txt
================================================================================
Origin/destination travel demands. Only nonzero demands are meant to be included.
Contains the following columns:
-ID: Unique identifying number.
-Origin: Node ID of origin.
-Destination: Node ID of destination.
-Volume: Number of people wishing to travel from the origin to the destination.
================================================================================
operator_cost_data.txt
================================================================================
Information related to defining the operator cost function.
Contains the following rows:
-Initial: Operator cost of the initial solution. Used for defining the allowable relative increase bounds. Note that this is not calculated automatically during preprocessing, and must be filled in by hand by using the single-run model.
-Elements: Number of parameters listed on the following rows. Currently set to 2.
-Operating_Cost: Weight of the vehicle operating costs.
-Fares: Fare collected from each boarding.
================================================================================
problem_data.txt
================================================================================
Miscellaneous data required to define the problem.
Contains the following rows:
-Elements: Number of parameters listed on the following rows. Currently set to 1.
-Horizon: Total daily time horizon.
================================================================================
transit_data.txt
================================================================================
Information related to each transit line. This includes a variety of fields directly related to the solution vector, such as the initial number of vehicles on each line (which constitutes the initial solution vector).
Contains the following columns:
-ID: Unique identifying number. This should indicate its position in the solution vector. Also used for line-specific references in the other data files.
-Name: Name of the line listed in the GTFS files.
-Type: Vehicle type ID. Matches one of the IDs listed in the vehicle data file.
-Fleet: Initial fleet size.
-Circuit: Total time for a vehicle to complete one circuit.
-Scaling: Fraction of the day during which the line is active. 1.0 indicates the entire 24-hour period.
-LB: Lower bound of allowable fleet size.
-UB: Upper bound of allowable fleet size.
-Fare: Boarding fare.
-Frequency: Initial line frequency, measured only during its active portion of the day. Relatively unimportant since it is recalculated each iteration for the current solution. The equation is: frequency = (fleet size) / (circuit time).
-Capacity: Initial line capacity, measured as a total number of passengers that can be transported per day. Relatively unimportant since it is recalculated each iteration for the current solution. The equation is: capacity = frequency * (daily time horizon) * (active fraction of day) * (vehicle type seating capacity).
================================================================================
user_cost_data.txt
================================================================================
Information related to defining the user cost function.
Contains the following rows:
-Initial: User cost of the initial solution. Used for defining the allowable relative increase bounds. Note that this is not calculated automatically during preprocessing, and must be filled in by hand by using the single-run model.
-Elements: Number of parameters listed on the following rows. Currently set to 3.
-Riding: Weight of in-vehicle riding time.
-Walking: Weight of walking time.
-Waiting: Weight of waiting time.
================================================================================
vehicle_data.txt
================================================================================
Information related to each vehicle. Each route has a specified vehicle type, and only routes with the same vehicle type may exchange vehicles during the search algorithm.
Contains the following columns:
-Type: Vehicle type ID. Referenced in the transit data file to specify the vehicle type of each route.
-Name: Name of the vehicle.
-UB: Maximum number of this type of vehicle allowed in the network.
-Capacity: Seating capacity of this vehicle type. It is assumed that loading factor has already been taken into account. For trains, it is assumed that this includes all cars on a given train.
-Cost: Operating cost per unit time.