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.

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

DC app not showing right number of bikes at stations #61

Closed
jpvelez opened this issue Aug 29, 2013 · 4 comments
Closed

DC app not showing right number of bikes at stations #61

jpvelez opened this issue Aug 29, 2013 · 4 comments
Assignees
Labels

Comments

@jpvelez
Copy link
Contributor

jpvelez commented Aug 29, 2013

The number of bikes and docks (and max docks) currently being displayed on the DC app are not in line with what's on the API.

It looks like the data in the database is in sync with the api, so the problem probably lies in the webapp.

@ghost ghost assigned hunterowens and darkzeroman Aug 29, 2013
@hunterowens
Copy link
Member

So, http://bikeshare.dssg.io/predict/17/60 returns

{
"current_bikes": 0,
"expected_num_bikes": 1.75,
"lat": 38.922925,
"lon": -77.042581,
"max_slots": 15,
"name": "Adams Mill & Columbia Rd NW",
"prob_empty": 0.9,
"prob_full": 0,
"station_id": 18
}

which matches the output of http://www.capitalbikeshare.com/data/stations/bikeStations.xml -

@hunterowens
Copy link
Member

the http://bikeshare.dssg.io/predict_all/ method returns a 500 internal service error, so that will have to be debugged.

@hunterowens
Copy link
Member

Debuged: There is an error when the server tries to unpickle the cache.p, this is because predictions.py is appending to it-

Does that makes sense, @darkzeroman?

@hunterowens
Copy link
Member

Actually, cron was not running python but the logs were not getting emailed. Testing again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants