Difference between revisions of "Talk:Wintermute"

From Robowiki
Jump to navigation Jump to search
(nice!)
(low score and common code)
Line 13: Line 13:
  
 
Nice, but score lower than I expected :-) Anyway, it also has many code very similar with [[DrussGT]] (and it look really like old [[Stormrider]] code, btw) &raquo; <span style="font-size:0.9em;color:darkgreen;">[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]</span> &raquo; 06:49, 14 April 2009 (UTC)
 
Nice, but score lower than I expected :-) Anyway, it also has many code very similar with [[DrussGT]] (and it look really like old [[Stormrider]] code, btw) &raquo; <span style="font-size:0.9em;color:darkgreen;">[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]</span> &raquo; 06:49, 14 April 2009 (UTC)
 +
 +
I just released this as an early version to see how it's doing, it is still a long way from being complete. Look at the list of things left to implement in the "What's next". I'm actually surprised at it's high rank, considering that it's coming close to bots like Lukious, XSeries, SilverSurfer, Chalk etc without even looking at the second wave, my danger function barely being tuned, etc.
 +
 +
I'm not sure how the code is like [[Stormrider]], the movement code is a complete rewrite. Maybe you're confusing my coding style/structure with actual functionality? Stormrider was 1) a goto surfer, 2) didn't use a tree, 3) only had one weighting system, 4) surfed both waves, 5) didn't use precise angles, 6) had a flattener, and 7) smoothed all the scans into bins before surfing them, 8) getting the danger at a point as the value in the corresponding bin. Wintermute is a 1) True surfer, 2) uses [[Simonton]]'s tree, 3) has 3 (and soon more) weighting systems, 4) only surfs the until the first wave has passed over it, 5) uses precise angles in the movement, 6) doesn't have a flattener, 7) keeps a list of scans similar to the firing one and 8) figures out the danger over a GF range by testing the GF's nearness to them. That doesn't leave much room for shared code. The only code they might share (I'm not sure if [[Stormrider]] used the current one or if it was only introduced in a later DrussGT) is the orbital (ie. non-wave) movement, which doesn't affect the surfing. One other thing they might share is finding which wave to log a hit to, but that is pretty much as-is from BasicSurfer. --[[User:Skilgannon|Skilgannon]] 08:04, 14 April 2009 (UTC)

Revision as of 09:04, 14 April 2009

Do we expected to see a True Surfing Stormrider here? » Nat | Talk » 12:33, 4 April 2009 (UTC)

No, Stormrider didn't use any sub-pixel precise targeting or movement. This bot is, in concept, similar to RougeDC I think. --Skilgannon 12:40, 4 April 2009 (UTC)

I mean Stormrider re-create with current DrussGT. Isn't sub-pixel SuperBotWidth? I think DrussGT use SuperBotWidth in both Movement and Targeting. » Nat | Talk » 12:55, 4 April 2009 (UTC)

  • DrussGT uses SuperBotWidth in the gun but not in the movement. I tried it in the movement but it actually hurt my score. This isn't going to be pure True Surfing however, because I want to be able to evaluate all points on the next wave, which will require some goto stuff =) --Skilgannon 17:12, 4 April 2009 (UTC)

Awesome name. :-) I presume this will be the heir to the throne? Good luck! --Voidious 16:41, 4 April 2009 (UTC)

Thanks! I was wondering what to call my new bot, and I had just read a book from 1984 called Neuromancer. Wintermute is the very smart AI that is striving to gain a personality by merging with the AI called Neuromancer, which in turn lacks resources and the drive to collect and process information. So my bot Wintermute will be exactly the same: no witty insulters, no victory dances, just straight plain functionality. If it ever attains number 1 then I'll give it a couple of these 'extras' =) --Skilgannon 17:12, 4 April 2009 (UTC)

Yeah, Neuromancer is a great book! That's neat to hear about the significance of the name to the bot's design, too. --Voidious 18:25, 4 April 2009 (UTC)

Nice, but score lower than I expected :-) Anyway, it also has many code very similar with DrussGT (and it look really like old Stormrider code, btw) » Nat | Talk » 06:49, 14 April 2009 (UTC)

I just released this as an early version to see how it's doing, it is still a long way from being complete. Look at the list of things left to implement in the "What's next". I'm actually surprised at it's high rank, considering that it's coming close to bots like Lukious, XSeries, SilverSurfer, Chalk etc without even looking at the second wave, my danger function barely being tuned, etc.

I'm not sure how the code is like Stormrider, the movement code is a complete rewrite. Maybe you're confusing my coding style/structure with actual functionality? Stormrider was 1) a goto surfer, 2) didn't use a tree, 3) only had one weighting system, 4) surfed both waves, 5) didn't use precise angles, 6) had a flattener, and 7) smoothed all the scans into bins before surfing them, 8) getting the danger at a point as the value in the corresponding bin. Wintermute is a 1) True surfer, 2) uses Simonton's tree, 3) has 3 (and soon more) weighting systems, 4) only surfs the until the first wave has passed over it, 5) uses precise angles in the movement, 6) doesn't have a flattener, 7) keeps a list of scans similar to the firing one and 8) figures out the danger over a GF range by testing the GF's nearness to them. That doesn't leave much room for shared code. The only code they might share (I'm not sure if Stormrider used the current one or if it was only introduced in a later DrussGT) is the orbital (ie. non-wave) movement, which doesn't affect the surfing. One other thing they might share is finding which wave to log a hit to, but that is pretty much as-is from BasicSurfer. --Skilgannon 08:04, 14 April 2009 (UTC)