{"push_id":721070729,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"98267925d5f0e28df82062084ae6c548aabe537d","before":"32c77f0b258f6321c32a9838d1951f7f178f9bf3","commits":[{"sha":"0cb33c0c8b19c37ed307b2d0811ba232f1994302","author":{"email":"4b0f9ce64d44d895572667c91224bee16c43c56d@gmail.com","name":"Ben"},"message":"Debugging.\nThe simulation is hooked in, but somewhere along the way the homography becomes incredibly ill-conditioned and unfit for navigation. I've verified that the feature points seem to match up correctly and that they are passed from the findAndMatch node to the homography calculation. I think the homography may be calculated incorrectly or something. At any rate, by the time it feeds back to the simulation, the navigation command is on the order of 10^37... which is ridiculous.","distinct":true,"url":"https://api.github.com/repos/speedyswimmer1000/homography_calc/commits/0cb33c0c8b19c37ed307b2d0811ba232f1994302"},{"sha":"98267925d5f0e28df82062084ae6c548aabe537d","author":{"email":"4b0f9ce64d44d895572667c91224bee16c43c56d@gmail.com","name":"Ben"},"message":"tilde","distinct":true,"url":"https://api.github.com/repos/speedyswimmer1000/homography_calc/commits/98267925d5f0e28df82062084ae6c548aabe537d"}]}