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

driver location-pickups map, using regression analysis with K-means clustering to determine probability of collecting fares #22

Open
dmnisson opened this issue Nov 5, 2018 · 0 comments
Open

driver location-pickups map, using regression analysis with K-means clustering to determine probability of collecting fares #22

dmnisson opened this issue Nov 5, 2018 · 0 comments

Comments

@dmnisson
Copy link
Owner

dmnisson commented Nov 5, 2018

No description provided.

@dmnisson dmnisson changed the title driver location-ridership map driver location-pickups map Nov 5, 2018
@dmnisson dmnisson changed the title driver location-pickups map driver location-pickups map, regression analysis Nov 5, 2018
@dmnisson dmnisson changed the title driver location-pickups map, regression analysis driver location-pickups map, regression analysis to determine passenger probability Nov 5, 2018
@dmnisson dmnisson changed the title driver location-pickups map, regression analysis to determine passenger probability driver location-pickups map, regression analysis to determine probability of collecting fares Nov 9, 2018
dmnisson added a commit that referenced this issue Nov 9, 2018
@dmnisson
#22 added geocoding package and factory that is configurable through …
1b2bbe4 
…appsettings.json
dmnisson added a commit that referenced this issue Nov 12, 2018
@dmnisson
#2 and #22 removed registration page and added geolocation package an…
2ddd551 
…d web api for logistic regression analysis
dmnisson added a commit that referenced this issue Nov 17, 2018
@dmnisson
#22 added ridership prediction to front end, updated button styles
84ab5e2
dmnisson added a commit that referenced this issue Nov 19, 2018
@dmnisson
#22 compute probabilities of different amounts of ridership for a leg
953c099
@dmnisson dmnisson changed the title driver location-pickups map, regression analysis to determine probability of collecting fares driver location-pickups map, using regression analysis with correlation clustering to determine probability of collecting fares Nov 25, 2018
@dmnisson dmnisson changed the title driver location-pickups map, using regression analysis with correlation clustering to determine probability of collecting fares driver location-pickups map, using regression analysis with K-means clustering to determine probability of collecting fares Nov 25, 2018
dmnisson added a commit that referenced this issue Nov 26, 2018
@dmnisson
#22 added geocoding API
1aa3975
dmnisson added a commit that referenced this issue Jan 4, 2019
@dmnisson
#22 added location clustering functionality.
eb7963e 
Next step is to use location clustering decisions with logistic regression to determine ridership probability
dmnisson added a commit that referenced this issue Feb 16, 2019
@dmnisson
#22 Domain layer for predicting pickup/fare class probabilities.
121e7c1 
Unit tests are primarily for purposes of ensuring that Accord framework is leveraged properly and do not
necessarily guarantee accuracy of final result.
dmnisson added a commit that referenced this issue Feb 19, 2019
@dmnisson
Added #22 pickup predictor to frontend
382e407 
Also added the required API controller functions to access the backend.

In addition, handling correctly unresolvable addresses in the geocoding API,
as well as handling first-time setup correctly in LocationClustering by not
assuming k = 0 and using a default number of 1 if the renumbering algorithm has
not yet run.
dmnisson added a commit that referenced this issue Feb 20, 2019
@dmnisson
#22 Request fare class boundaries on init to avoid "undefined" issues.
fb6c46f 
Also made an explicit exception to handle insufficient data in the backend,
and setup the frontend component so that the page will scroll to reveal the results.
dmnisson added a commit that referenced this issue Mar 13, 2020
@dmnisson
#22 added geocoding package and factory that is configurable through …
955730b 
…appsettings.json
dmnisson added a commit that referenced this issue Mar 13, 2020
@dmnisson
#2 and #22 removed registration page and added geolocation package an…
731bcf5 
…d web api for logistic regression analysis
dmnisson added a commit that referenced this issue Mar 13, 2020
@dmnisson
#22 added ridership prediction to front end, updated button styles
7dc6c73
dmnisson added a commit that referenced this issue Mar 13, 2020
@dmnisson
#22 compute probabilities of different amounts of ridership for a leg
871f4dc
dmnisson added a commit that referenced this issue Mar 13, 2020
@dmnisson
#22 added geocoding API
35f9319
dmnisson added a commit that referenced this issue Mar 13, 2020
@dmnisson
#22 added location clustering functionality.
8eac637 
Next step is to use location clustering decisions with logistic regression to determine ridership probability
dmnisson added a commit that referenced this issue Mar 13, 2020
@dmnisson
#22 Domain layer for predicting pickup/fare class probabilities.
683f0a2 
Unit tests are primarily for purposes of ensuring that Accord framework is leveraged properly and do not
necessarily guarantee accuracy of final result.
dmnisson added a commit that referenced this issue Mar 13, 2020
@dmnisson
Added #22 pickup predictor to frontend
3650e35 
Also added the required API controller functions to access the backend.

In addition, handling correctly unresolvable addresses in the geocoding API,
as well as handling first-time setup correctly in LocationClustering by not
assuming k = 0 and using a default number of 1 if the renumbering algorithm has
not yet run.
dmnisson added a commit that referenced this issue Mar 13, 2020
@dmnisson
#22 Request fare class boundaries on init to avoid "undefined" issues.
3c67175 
Also made an explicit exception to handle insufficient data in the backend,
and setup the frontend component so that the page will scroll to reveal the results.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dmnisson