User talk:Tkiesel/MovementPredictor
- [View source↑]
- [History↑]
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| License | 4 | 04:31, 11 June 2012 |
| My Improved Code | 1 | 14:34, 27 May 2012 |
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |
Anyone have a favorite license they'd like this work to be under? Nat's original is Public Domain.
Nothing wrong with public domain. =) I've been using zlib, and I also like MIT. A common one on the wiki (which I also once used) is RWPCL. I actually posted some thoughts on licenses a while back here: Archived_talk:User:Voidious_20110909#Choice_of_license. It's definitely up to personal preference.
zlib, MIT and Creative Commons Attribution all look nice to me as "credit where credit is due" permissive licenses.
The smoother method I'm hoping to use is from a talk page here on RoboWiki. RoboWiki:Copyrights is blank, so I'm not sure how to proceed with that code.
Should have this code in a testable state, hopefully with a test painter bot to squash bugs this weekend or on Monday, depending on how life goes.
Anything without a license listed is probably free to use as if it's public domain. I think we stumbled on deciding on a license for wiki content because so much of it was added before any license was specified, so it seems wrong to try and retroactively add a license. Very good point that we should update RoboWiki:Copyrights, though, given how prominently it's displayed.
I've just capped off all of deBroglie's files, including the MovementPredictor with a zlib notice.
I added a clause to two files regarding not using the code in programming competitions without my consent. Those two files are a bit more uniquely "me" (or at least represent a lot more of me bashing my head against the wall) than the rest.
As of the next release, deBroglie will be a majority zlib bot. :)
Thanks for the food for thought!
I never thought someone would actually use my code, so I never got around posting the improved version. I'll try to do that for you soon (as soon as I can find the code)
Though the core movement function hasn't changed, and my improvements probably wouldn't affect your expansion, it does include (what I believe to be) some cool features. GoTo-wrapping is one, another is method to find possible sequence of 'PredictionStatus' from one status to another over given time. It is extremely useful in melee battle, though I haven't test if it give better result than simple linear-prediction.
That's wonderful! I'd love to incorporate your improved version, and hopefully the work I've done will be useful to you and others here on RoboWiki!
I've got precise MEA up and working, including an example bot. I've put it into DeBroglie so I can see how it looks with real firing waves, and enemy bots sometimes do get outside of the marked angular bounds on the wave. Something to debug here...
The wall smoothing freaks out a bit when a bot intentionally goes for the wall.. and its especially touchy with a bot like sample.Walls.
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |



