a bus is created and assigned to the block. its energy reserves and its starting depot_id are noted.
Before any trip starts, a bus evaluates if it has enough energy to serve the
full trip to its final destination.
If it does have enough energy it completes the trip,substracting the energy
required to serve the trip from its energy reserves.
If a charger is present at the termini where it completes its trip, the
bus will opportunistically charge until it has to depart for its next
assigned trip.
It repeats this process until one of the following:
If it does not have enough energy, the bus returns to the starting depot,
and another fully charged bus replaces it. This bus has no starting depot, as it starts in the middle of the block. It follows steps 1-4.
If it completes its block, it returns to the nearest depot and charges.
Current outcome:
Buses are reassigned before finishing blocks
buses return to the depot before finishing the block and then return to serve the block.
Further details:
Details about Block_id: 93217702 in AC Transit, scenario 220kwh battery, 500kw nondepot chargers.
See this trips file. Strip the .log filetype after downloading, since GH doesnt permit .csv
Intro:
This block has 3 buses that are used to complete the block: 672, 673, and 674.
First, lets see a summary of all trips in the block. We can see here that we start with bus 672, which leaves from depot 3 and performs a single trip. It then gets reassigned to another block (see details about the bus below) and is replaced by 673. 673 Continues the block until it is out of energy. Once it is out of energy, it returns to depot 3, charges fully (! this is surprising) and then completes one trip. Then Bus 674 takes over, and completing 3 trips and then returning to depot 3. The block is complete.
Next lets look at what each of the buses themselves do. First up, Bus 672:
This bus starts on the block detailed above for one trip. It then gets reassigned to another block, 93217602. (why?) It then serves three trips for that block, completing the block and returning to the depot 3, nearly fully charged.
Next Bus 673: Since 672 is reassigned, 673 picks up. Since it starts in the middle of the block, it does not have a starting depot listed. It travels to the start of the next trip in the block and continues to serve those trips until it no longer has enough energy to serve the next trip. It returns to depot 3 and charges fully (this is unexpected) then returns to finish the block. I need to dig more to see if it actually meets the required starting time of the next trip in the block, given that it has time to return and fully charge. It then serves one additional trip in the block, then returns to the depot before block has been completed, almost fully charged. It is not deployed again.
Since bus 673 returns to the depot, bus 674 is assigned. It, however, does have a starting depot unlike 673 did. (why?) It continues to serve the remaining trips in the block, and then once the block is complete, it returns to the depot.
Expected outcome:
Current outcome:
Further details: Details about Block_id: 93217702 in AC Transit, scenario 220kwh battery, 500kw nondepot chargers.
See this trips file. Strip the .log filetype after downloading, since GH doesnt permit .csv
Intro: This block has 3 buses that are used to complete the block: 672, 673, and 674.
First, lets see a summary of all trips in the block. We can see here that we start with bus 672, which leaves from depot 3 and performs a single trip. It then gets reassigned to another block (see details about the bus below) and is replaced by 673. 673 Continues the block until it is out of energy. Once it is out of energy, it returns to depot 3, charges fully (! this is surprising) and then completes one trip. Then Bus 674 takes over, and completing 3 trips and then returning to depot 3. The block is complete.
Next lets look at what each of the buses themselves do. First up, Bus 672:
This bus starts on the block detailed above for one trip. It then gets reassigned to another block, 93217602. (why?) It then serves three trips for that block, completing the block and returning to the depot 3, nearly fully charged.
Next Bus 673: Since 672 is reassigned, 673 picks up. Since it starts in the middle of the block, it does not have a starting depot listed. It travels to the start of the next trip in the block and continues to serve those trips until it no longer has enough energy to serve the next trip. It returns to depot 3 and charges fully (this is unexpected) then returns to finish the block. I need to dig more to see if it actually meets the required starting time of the next trip in the block, given that it has time to return and fully charge. It then serves one additional trip in the block, then returns to the depot before block has been completed, almost fully charged. It is not deployed again.
And finally Bus 674:
Since bus 673 returns to the depot, bus 674 is assigned. It, however, does have a starting depot unlike 673 did. (why?) It continues to serve the remaining trips in the block, and then once the block is complete, it returns to the depot.