View source for User talk:Nat
- Archived Talk:
- 2009/04/06 - 2009/06/20
MicroBot Wave Surfing
Anyone have 10TB of memory and hard disk to spare? I need that to perform my own microbot wave surfing. The large part of Wave Surfing is precise prediction, which nonetheless can't fit in micro. I wonder if I cached all the prediction and just access it at runtime. Now I roughly calculated. Let see, I restricted the location, absBearing, velocity and distance to all integer. Total possible location on the map is 764*564 = 430896 locations, multiply by 360 absBearing, ~950 distance, 17 velocity. Saves in short (2 bytes), contain x and y will result in around 764*564*360*950*17*2*2 = 10020917376000 B 9786052125 KiB = ~9,556,692 MiB = ~9,333 GiB = ~9.114 TiB.
Anyone have ideas how can I reduced those number? If I use 80*60 possible locations, 36 possible absBearing, 17 velocity and 19 possible distance, it still cost 43MB Note that this need to be preloaded into the robot, not calculating on-the-fly. span style="font-size:0.9em;color:darkgreen;">Nat | Talk » 05:17, 20 June 2009 (UTC)
I've done a fair amount of work with precalculated movement table things. I once got a precalculated movement table down to about 2MB, but that's still too big for ethical pre-loading, AND the optimizations it used took rather large codesize to turn into something usable in battle. I don't think you're going to be able make this realistically work Nat honestly. --Rednaxela 05:27, 20 June 2009 (UTC)
=( Well, thanks for the info. » Nat | Talk » 05:50, 20 June 2009 (UTC)
- [View source↑]
- [History↑]
Contents
Thread title | Replies | Last modified |
---|---|---|
TheRiver Melee Surfing | 0 | 16:15, 11 February 2017 |
What am I missing? | 6 | 18:26, 29 September 2013 |
[https://www.mediawiki.org/wiki/Extension:OpenID Extension:Openid OpenID extension] | 2 | 21:59, 12 September 2013 |
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page.
Return to Thread:User talk:Nat/TheRiver Melee Surfing.
So I have been gone for about a year and a half, and want to go back to this game again (guess you can never left robocode completely).
Basically, what innovations/technological breakthrough did I miss?
Not sure if you noticed, but we transitioned to LiteRumble when DarkCanuck's server went down. Sheldor and I took the nano crown with a collaboration bot, Yatagan. Nz.jdc updated LittleBlackBook's table, and wrote his own table-driven bot. They are both above Yatagan in the nanorumble, but they are sort of cheesy because they react to enemy name, not enemy behaviour. DrussGT now has a bullet-shielding mode which is tried at the beginning of each match. Chase finally found a bug in Seraphim and its APS now matches its strong PL score. I improved Neuromancer's 1v1 score a lot, and got it to 1st in melee.
I'm sure I've missed a lot of other stuff.
Welcome back!
- RoboRumble 1v1 crossed 1,000 participants.
- I wrote RoboRunner, a new multi-threaded battle runner, and Skotty wrote RoboJogger, a GUI version of it.
- We upgraded to MediaWiki 1.19. So the Twitter feed and bigger font got reverted and we still haven't fixed it. Need to upgrade PHP before moving past that.
- Personally, I've written/released a game called BerryBots in that time, which spawned from the Raspberry Pi discussion here at the RoboWiki. Right now working on replay support, which is almost ready (sample).
I restarted working on Roboflight again for a bit, made it easier to write stuff in, currently on the back burner though. Not sure if you were around for it, but I also finally added a proper gun that I wrote to Nene. Aside from that a lot of robots have been updated in general.
Skilgannon's and my bot Yatagan did quite well in the NanoRumble. My bot EpeeistMicro has a perfect PWIN (PL percentage) score in the MicroRumble. I still haven't started writing a minibot yet, but I do plan to sometime in the current century. :)
[https://www.mediawiki.org/wiki/Extension:OpenID Extension:Openid OpenID extension]
I'm open to it if people want it. Would you have preferred to login with OpenID?
Only problem I see is it requires MediaWiki 1.21 and we're on 1.19. I think I stopped there because it required upgrading PHP, but we should do that and upgrade MediaWiki sometime anyway.