Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Boston Hubway Fleet Size Trials #9

Open
kqnguyen0000 opened this issue Jun 24, 2019 · 0 comments
Open

Boston Hubway Fleet Size Trials #9

kqnguyen0000 opened this issue Jun 24, 2019 · 0 comments
Labels
Discussion Used to discuss questions about features and implementation Documentation Used to track the documentation of a feature or bug

Comments

@kqnguyen0000
Copy link
Collaborator

firefox_5niOoULQGU

This test was run with three equally weighted PEV spawn points: MIT Media Lab, Fenway Park, and Boston Commons.

Insights:

  • Our current Hubway data only exists from 0:00-12:00. We have no data for 12:00-24:00.
  • From a fleet size of 110 to 200 cars, we only save a minute from each metric. (avg, 50%, 75% wait)
  • However a fleet size of 105 cars has much worse performance. This is also the threshold where we start seeing assignment times. (When there are no free cars available for the request)
  • For our current dataset, we need a minimum of 110 cars to replace Hubway.
@kqnguyen0000 kqnguyen0000 added Discussion Used to discuss questions about features and implementation Documentation Used to track the documentation of a feature or bug labels Jun 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Discussion Used to discuss questions about features and implementation Documentation Used to track the documentation of a feature or bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kqnguyen0000