{"push_id":1417131462,"size":1,"distinct_size":1,"ref":"refs/heads/new_sensors","head":"4ce9c5058a46dbabb87d03e28a43b47666c13341","before":"66981ba696092fe06b4f45568f6fce260485cfe3","commits":[{"sha":"4ce9c5058a46dbabb87d03e28a43b47666c13341","author":{"name":"Travis Rhoden","email":"7cdbaf04b8eeaf9fd3ef3382968eb3df2950f2fd@gmail.com"},"message":"Introduce new SensorSuite and Aggregator\n\nTo encourage greater use of the Raspberry Pi, break the sensors into\nmultiple projects/binaries that can be deployed independently. Add a\npublisher that can collect data from the temperature and radiation\nsensors and push it up to the new aggregator.\n\nReplace the old gateway with a new Aggregator. The old gateway required\nknowing ahead of time how to reach the sensors, and also would not work\nacross NAT (it tried to connect to the sensors), which precluded hosting\nthe gateway on AWS, but hosting the Pi's at a conference.\n\nThe new aggregator dynamically accepts as many sensors as try to connect\nto it. It will automatically average the data and relay it to the game\ncontroller.\n\nOne other important change is that it is now expected that there is a\nsingle \"solar flare\" sensor -- a single source of truth for that data\npoint. The Solar Flare is really an input to the other sensors, so it\ndoes not make sense to have that be randomly generated for each team,\nand then to be \"averaged\" in any way. Either there is a solar flare that\nshould effect the trends, or there is not. Therefore, the aggregator\nqueries the solarflare endpoint directly, and it is expected that the\ntemperature and radiation sensors are querying the same solar flare\nendpoint as well.","distinct":true,"url":"https://api.github.com/repos/codedellemc/mars-challenge/commits/4ce9c5058a46dbabb87d03e28a43b47666c13341"}]}
{"actor":{"display_login":"codenrhoden"}}