Unit tests for the stats code as promised
Check in the history of the score components as well

So that we can see how people's scores increased, and how it affected their engagement
Merge pull request #37 from shankari/gamification

Unit tests + store the history of the score components in stats
Change the gamified calculation to use the data from the day before yesterday

Because there is currently a significant lag in the time for e-mission to
prompt for entries, so people may not confirm yesterday's trips until sometime
today, which means that it won't be counted in their score.
Merge pull request #39 from shankari/gamification

Change the gamified calculation to use the data from the day before yest...
Check in a script to regenerate the scores and carbon footprints based on the trip data

As part of this, change the client scripts to be more general and to accept the
date as input for running background jobs
Merge pull request #40 from shankari/gamification

Check in a script to regenerate the scores and carbon footprints based o...