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)

I'll let you borrow my tables when I get around to adding micros to my list ;) --Miked0801 09:02, 20 June 2009 (UTC)

I'm not talking about the VCS table, I'm talking about movement table i.e. the table that allow you to know what is your position next tick if you are at (x,y) with a velocity of v and the enemy is at θ with a distance of d or something. It is the replacement of Precise Prediction used in minibot and megabot. » Nat | Talk » 09:25, 20 June 2009 (UTC)

I haven't dealed with wavesurfing yet, but do you need precise prediction? Is there anything less complex that could replace it? Anyway, take a look at kb.WaveShark, it's supposed to be a wavesurfer. --HUNRobar 14:38, 20 June 2009 (UTC)

LOL, it is kc.WaveShark. Actually it is that robot which inspire me about this. » Nat | Talk » 14:40, 20 June 2009 (UTC)

Pugilist is an example of a wave surfing without precise prediction I think, that might be able to give some inspiration --Rednaxela 15:53, 20 June 2009 (UTC)

Thanks. I have looked at it now, the prediction thing is still too large I think. But I'll give it a try... » Nat | Talk » 16:09, 20 June 2009 (UTC)

Bi-hourly release

Wonder is this is right thing to do or not. Because the number of clients running among this day, I can release my robot bi-hourly. But since I'm not running those clients, I not sure if this is right thing to do or not. » Nat | Talk » 11:42, 21 June 2009 (UTC)

if there are no other bots waiting, not a problem. But, my bot has been waiting for a bit to get to 2k battles in nanos. If you need this much info and are feeling guilty, use roboresearch for your tests. You'll get your answers just as quick without the guilt. --Miked0801 15:26, 21 June 2009 (UTC)

Sorry. When I checked and see the "PAIRINGS COMPLETE" text, I decided that the ranking is completed. Actually I'm not needing it fast, just roughly seen where it place is enough for me to decided what to do with next version, and I usually take only 10 minutes to do it. I'll try to run it on RoboResarch next time. Thanks. » Nat | Talk » 15:39, 21 June 2009 (UTC)

I think the rule of thumb used to be maximum one release per day? There are quite a few bots in the nano & micro categories still below 2000 battles. If you're feeling guilty, run a client and help out... --Darkcanuck 17:28, 21 June 2009 (UTC)

Hey Nat. I've seen that you are trying to use melee surfing. For dodging the bullets you can get the distance to closest bullet and create some points in that distance. It works well in melee but it dowsn't work very well in one on one because it uust goes to a safe point. Not the safest one. It is also very easy to use.

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.

I just couldn't give up on that robot. Even though I wanted to. I might have to go back and look over other old robots of mine and fix errors in those, and re enter them into the rumble. Like Tyrra.

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.

Thank you. It seems that I does miss a lot :)

This ought to cover a lot.

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. :)

Would this be a good extension to install on this wiki?

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.

I am not even sure why he made this post on Nat's talk page. That said, I never found OpenID to be that easy to use (or to setup to use).

It would be easier for the end user and probably to setup to use one of the many "Login in X" systems. Where X is Twitter, Google, Facebook, or what have you.