Difference between revisions of "DeBroglie"
m (added link) |
(Updates for latest version) |
||
Line 6: | Line 6: | ||
| extends = [[AdvancedRobot]] | | extends = [[AdvancedRobot]] | ||
| targeting = [[GuessFactor Targeting (traditional)|GuessFactor]] | | targeting = [[GuessFactor Targeting (traditional)|GuessFactor]] | ||
− | | movement = [[Oscillator_Movement|Oscillator]] | + | | movement = Multiple: |
− | | current_version = 0. | + | *[[Wave_Surfing/GoTo_Surfing|GoTo wave surfing]] |
− | | released = | + | *[[Oscillator_Movement|Oscillator]] |
− | | best_rating = | + | | current_version = 0.66 |
+ | | released = 13 October 2010 | ||
+ | | best_rating = 274th | ||
| license = [[RWPCL]] | | license = [[RWPCL]] | ||
}} | }} | ||
Line 41: | Line 43: | ||
== Wheels (movement) == | == Wheels (movement) == | ||
− | + | When there are hostile waves in the air, deBroglie uses [[Wave_Surfing/GoTo_Surfing|GoTo wave surfing]] movement, randomly picking a point that is within a certain percentage range of the safest point on the wave. | |
− | + | When no waves are in the air, or when too close to effectively surf, deBroglie uses the old oscillator movement from my earliest ever Advanced bot. It uses a compound sine function to make the movement take longer for pattern matchers to get a lock on, and rams aggressively. | |
− | |||
− | |||
== Sword (targeting) == | == Sword (targeting) == | ||
Line 51: | Line 51: | ||
Currently the bot uses a [[GuessFactor Targeting (traditional)|Guess Factor]] type of targeting system. The best bin for the current firing situation is determined, then converted into an angle for firing. | Currently the bot uses a [[GuessFactor Targeting (traditional)|Guess Factor]] type of targeting system. The best bin for the current firing situation is determined, then converted into an angle for firing. | ||
− | The best bin for each firepower is determined via a simple percentage hit rate, with heavier weighting for real waves over virtual waves and a | + | The best bin for each firepower is determined via a simple percentage hit rate, with heavier weighting for real waves over virtual waves and a 5% penalty to bins with no real waves whatsoever. The best score for each firepower is then converted into an [[wikipedia:Expected value|expected value]] of points, yielding the net point gain the bot should expect from firing the bullet. The firing solution with the best expected point value is used. If there is no firing solution that is expected to generate positive points, the robot doesn't fire. |
− | |||
− | |||
== Eyes (radar) == | == Eyes (radar) == |
Revision as of 00:20, 27 November 2010
- Sub-pages:
- /Version History
deBroglie | |
Author(s) | Tkiesel |
Extends | AdvancedRobot |
Targeting | GuessFactor |
Movement | Multiple: |
Released | 13 October 2010 |
Best Rating | 274th |
Current Version | 0.66 |
Code License | RWPCL |
Contents
Name
This is my first wave surfing bot, and I'm a physicist by training, so it's named in honor of Louis de Broglie, who discovered that matter has wavelike properties. This was a foundational discovery in Quantum Mechanics.
In honor of the namesake, all data collection is done in the form of waves. Waves emanate from the bot for targeting data, and from the enemy for movement data.
This bot is very much a work in progress.
Design
Goals
I wanted to gather waves to use as targeting information, both incoming waves from the enemy for movement, but also outgoing waves from de Broglie for targeting. I wanted to reuse as little code as possible, so I've been working on implementing the wave system in as modular a way as possible.
Universe
The bot has a Universe object which contains all elements of its picture of the battlefield, including two simple Bot objects, one for itself, and one for the enemy. The Bots are updated on every scan.
The Universe feeds information to the Eyes, Wheels, and Sword which are radar, movement, and targeting respectively.
WavePredictor
The universe has two WavePredictor objects, one from the perspective of de Broglie being fired upon by the enemy, and one from the perspective of the enemy being fired upon by de Broglie. The data available to the targeting WavePredictor is (of course) more precise than the data available to the movement WavePredictor, but other than this caveat, there is total symmetry in how data is handled.
The WavePredictor handles all firing of Waves and data collection. The relevant WavePredictor can be queried by the Wheels and Sword.
Wheels (movement)
When there are hostile waves in the air, deBroglie uses GoTo wave surfing movement, randomly picking a point that is within a certain percentage range of the safest point on the wave.
When no waves are in the air, or when too close to effectively surf, deBroglie uses the old oscillator movement from my earliest ever Advanced bot. It uses a compound sine function to make the movement take longer for pattern matchers to get a lock on, and rams aggressively.
Sword (targeting)
Currently the bot uses a Guess Factor type of targeting system. The best bin for the current firing situation is determined, then converted into an angle for firing.
The best bin for each firepower is determined via a simple percentage hit rate, with heavier weighting for real waves over virtual waves and a 5% penalty to bins with no real waves whatsoever. The best score for each firepower is then converted into an expected value of points, yielding the net point gain the bot should expect from firing the bullet. The firing solution with the best expected point value is used. If there is no firing solution that is expected to generate positive points, the robot doesn't fire.
Eyes (radar)
Narrow Lock radar with a factor of 1.95.
Testing / Performance
Well, something's working right targeting-wise, because the current simple gun implementation can quickly learn sample bots like Walls and SpinBot. This tells me that I'm barking up the right tree so far.
Code
This bot's code (messy a state as it's in right now) is available under the RoboWiki Public Code License - Version 1.1 or any later version.