|
| 1 | +sim: |
| 2 | + # (required) any name you want to give your simulation (go ahead, be creative); |
| 3 | + sim_name: denver_demo |
| 4 | + |
| 5 | + # (required) the start time of the simulation; |
| 6 | + start_time: "1970-01-01T00:00:00" |
| 7 | + |
| 8 | + # (required) the end time of the simulation; |
| 9 | + end_time: "1970-01-02T00:00:00" |
| 10 | + |
| 11 | + # (optional) how many seconds does a single hive time step represent; |
| 12 | + # must be an integer; generally, 60 seconds is the recommended value based on internal testing and validation; |
| 13 | + timestep_duration_seconds: 60 |
| 14 | + |
| 15 | + # (optional) represents how long a request will be active in the simulation; |
| 16 | + # after this timeout the request is destroyed; |
| 17 | + request_cancel_time_seconds: 600 |
| 18 | + |
| 19 | + # (optional) what is the atomic unit of the simulation; |
| 20 | + # 15 is equivalent to approximately 1 meter; |
| 21 | + sim_h3_resolution: 15 |
| 22 | + |
| 23 | + # (optional) which h3 resolution should we search for entities? |
| 24 | + sim_h3_search_resolution: 7 |
| 25 | + |
| 26 | + # (optional) if using human drivers, what type of schedule should we use? |
| 27 | + schedule_type: "time_range" |
| 28 | + |
| 29 | +network: |
| 30 | + # (required) what type of network to use; options: osm_network | euclidean |
| 31 | + network_type: osm_network |
| 32 | + |
| 33 | + # (optional) if no speed exists in the road network data input, we fill it in with this value; |
| 34 | + default_speed_kmph: 40.0 |
| 35 | + |
| 36 | +input: |
| 37 | + # (required) |
| 38 | + vehicles_file: denver_demo_vehicles_no_stations.csv |
| 39 | + |
| 40 | + # (required) |
| 41 | + requests_file: denver_demo_requests.csv |
| 42 | + |
| 43 | + # (required) |
| 44 | + bases_file: denver_demo_no_stations.csv |
| 45 | + |
| 46 | + # (required) |
| 47 | + stations_file: denver_demo_no_stations.csv |
| 48 | + |
| 49 | + # (optional) only used with `network_type: osm_network` |
| 50 | + road_network_file: downtown_denver_network.json |
| 51 | + |
| 52 | + # (optional) outline a geofence for control purposes |
| 53 | + geofence_file: downtown_denver.geojson |
| 54 | + |
| 55 | + # (optional) defaults to zero cost if not specified |
| 56 | + rate_structure_file: rate_structure.csv |
| 57 | + |
| 58 | + # (optional) defaults to zero cost if not specified |
| 59 | + charging_price_file: denver_charging_prices_by_geoid.csv |
| 60 | + |
| 61 | + # (optional) default is no demand forecasting |
| 62 | + demand_forecast_file: denver_demand.csv |
| 63 | + |
| 64 | +dispatcher: |
| 65 | + # (optional) how often should we issue dispatching instructions? |
| 66 | + default_update_interval_seconds: 600 |
| 67 | + |
| 68 | + # (optional) ingnore searching for any entity beyond this threshold |
| 69 | + max_search_radius_km: 100.0 |
| 70 | + |
| 71 | + ## Parameters for the default matching dispatcher |
| 72 | + |
| 73 | + # (optional) don't match requests to vehicles beyond this range |
| 74 | + matching_range_km_threshold: 20 |
| 75 | + |
| 76 | + # (optional) which states will the default matching dispatcher consider valid? |
| 77 | + valid_dispatch_states: |
| 78 | + - Idle |
| 79 | + - Repositioning |
| 80 | + |
| 81 | + ## Parameters for the default charging dispatcher |
| 82 | + |
| 83 | + # (optional) how to search for stations? nearest_shortest_queue | shortest_time_to_charge |
| 84 | + charging_search_type: nearest_shortest_queue |
| 85 | + |
| 86 | + # (optional) ignore charging at stations when remaining range is greater than this plus the nearest station distance |
| 87 | + charging_range_km_threshold: 20 |
| 88 | + |
| 89 | + # (optional) ignore charging at stations when remaining range is greater than this |
| 90 | + charging_range_km_soft_threshold: 50 |
| 91 | + |
| 92 | + # (optional) ignore base charging at bases more than this threshold |
| 93 | + base_charging_range_km_threshold: 100 |
| 94 | + |
| 95 | + ## Parameters for the driver control |
| 96 | + |
| 97 | + # (optional) SOC target for fast charging at a station |
| 98 | + ideal_fastcharge_soc_limit: 0.8 |
| 99 | + |
| 100 | + # (optional) how long do drivers idle before returning to a base? |
| 101 | + idle_time_out_seconds: 1800 |
0 commit comments