{"push_id":889502470,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"d9b25ebfec902c1b850789095097cfb14873a06c","before":"ad068153f83982bdae9cb6ea0156b464358a0a34","commits":[{"sha":"d9b25ebfec902c1b850789095097cfb14873a06c","author":{"email":"e8ccef0d579672eb34486e8afa814902e12059cf@gmail.com","name":"Scott Bronikowski"},"message":"3 Dec 15\n\n--Wrote gm-checking.sc with a couple functions to check output of OpenGM with\n  scores.  Have saved in the comments there a bunch of commands used in building\n  it.\n\n--Thinking about changing around the membership functions I use for the world\n  distance.  Had been using gaussmf before, but changed to sigmf.  Also look at\n  zmf.\n\n--Looking at viterbi code Jeff sent--trying to integrate it into inference.cpp\n  in order to get viterbi score to compare against OpenGM score.\n\n--Random thought-->should proposal score have more influence than it does?  Or\n  are my metrics just bad??  How could I use better binary metrics?\n\n--Or is my pixel distance sigmoid too steep?  With the center cross-over at\n  80px and a slope of -0.1, distances of up to 40px get a score above 0.98.\n\n--Trying a test with JUST pixel distance and the sigmoid parameters set to\n  [-0.075,40] using the standard set of k values.  Seeing if this affects\n  output.  This is 20151203a_top_k_{10,50,100,200}.\n\n--**FOUND** arithmetic error in calculation of box centers for pixel\n    distance-->computed (x2-x1)/2 (1/2 width) and (y2-y1)/2 (1/2 height), but\n    forgot to add x1 and y1 to those to find the center of the images.\n\n--Rerunning previous test as 20151203b*.\n\n--From Jeff: There is a much simpler solution. You are measuring image\n             distance. Since all proposals presumably have their edges bounded\n             by the image edges, their centers must lie within the image. The\n             minimum is 0 and the maximum is the image diagonal.Just scale\n             linearly in this range to [0,1].\n  Will try linear membership function once b test completes.\n\n--Proposal computation on aql errored on 5-0, 4-5, 4-4, 3-4, 3-3; also re-runs\n  of 1-2 and 1-5 from yesterday don't seem to have saved-->re-running all\n\n--20151203b* tests looked MUCH better--a few dummy boxes and a few boxes that\n  were the whole frame, but much more temporal coherence than before.  Never\n  tried linear membership function.\n\n--Thinking about changing pixel distance measure to IoU--looking for fast ways\n  to do it in matlab.","distinct":true,"url":"https://api.github.com/repos/scottbronikowski/codetection/commits/d9b25ebfec902c1b850789095097cfb14873a06c"}]}