Thread history
Viewing a history listing
Time | User | Activity | Comment |
---|---|---|---|
02:42, 16 November 2012 | Tkiesel (talk | contribs) | New reply created | (Reply to unit testing movement predictor) |
20:29, 15 November 2012 | Voidious (talk | contribs) | New thread created |
I posted what I used to test my prediction here: User:Voidious/LocationBot. Basically it's a bot that records its movement along a bunch of random paths and prints the input (start location / heading / velocity, movement commands) and output (final location / heading) that you'd need to pass to a precise prediction unit test. (Actually it prints the actual method call so you can just copy/paste it into a unit test, if you sync it up with your method name and parameter list.)
Thanks! I'll use that to suss out any MovementPredictor bugs.
The whole thing is probably far far less than ideal in performance terms.. but the pluggable prediction ender and pluggable distance controller are features I liked adding for the purpose of letting people plug this into their own bots. :)