Difference between revisions of "Ali/Version History"
< Ali
Jump to navigation
Jump to search
(migrating from old wiki) |
m (Add link to TronsGun) |
||
Line 27: | Line 27: | ||
** Removed MultipleChoice. Now only uses the best matching log entry. | ** Removed MultipleChoice. Now only uses the best matching log entry. | ||
* Version 0.3.1 - '''1995''' - As of May 2005. Not comparable with the above scores, but with the below. | * Version 0.3.1 - '''1995''' - As of May 2005. Not comparable with the above scores, but with the below. | ||
− | ** Segmentation wall proximity, time since velocity change and distance traveled last 15, 60 and 120 ticks (TronsGun inspired) | + | ** Segmentation wall proximity, time since velocity change and distance traveled last 15, 60 and 120 ticks ([[TronsGun]] inspired) |
** Reinstalled MultipleChoice. Using the 15 best matching entries. | ** Reinstalled MultipleChoice. Using the 15 best matching entries. | ||
** Chebyshev Distance (|a - b|) used for comparing log entries | ** Chebyshev Distance (|a - b|) used for comparing log entries |
Latest revision as of 10:00, 14 September 2017
- Ali Sub-pages:
- Ali - Version History - BumbleBee
- Version 0.1 - 1973 (PM gun)
- Version 0.2 - 2042 (Fuzzy GF gun)
- Version 0.2.1 - 2043
- Bug fixes in the fuzzy matching.
- The log is now cleaned and truncated to 8000 waves when it reaches 12000 waves. (Based on how often each scan is fuzzily matched.)
- Version 0.2.2 - 2042
- Uses normalized real data instead of crude indexes
- Version 0.2.3 - 1999
- Only runs the matching once before firing
- Uses straight differences when matching (so called Manhattan distance)
- Tweaked dimensions weighting
- Version 0.2.4 - 1987
- Back to Euclidian distances in matching
- Reset the dimension weighting back to 0.2.2
- Version 0.2.5 - 2046
- Back to 0.2.3 config
- Gunalignment and "only-run-matching-once-per-bullet" re-visited.
- Version 0.3 - 1974
- Segmentation on velocity and wall proximity only
- Removed MultipleChoice. Now only uses the best matching log entry.
- Version 0.3.1 - 1995 - As of May 2005. Not comparable with the above scores, but with the below.
- Segmentation wall proximity, time since velocity change and distance traveled last 15, 60 and 120 ticks (TronsGun inspired)
- Reinstalled MultipleChoice. Using the 15 best matching entries.
- Chebyshev Distance (|a - b|) used for comparing log entries
- Version 0.4.1 - 2018
- ApproachVelocity dimension removed
- Dimensions somewhat normalized around 0-75
- Version 0.4.2 - 2032
- Reverse wall distance dimension added
- Tuned the threshold to select the log entries used for MultipleChoice
- Tuned the weights on each dimension
- Version 0.4.3 - 2032
- Using a fixed cluster size (100) of the best matching log entries.
- To speed things up the log is first filtered through a coarse selection of half-good matches.
- Weighting of dimensions: Firedistance = 1 and all others 2.
- Version 0.4.4 - 2031
- Minor tweak of cluster size and coarse filtereing threshold
- Refactored the selection process
- Version 0.4.5 - 2034 (Top 10!)
- Tweaking weights of segmentation dimensions
- Version 0.4.6 - 2037
- Using Euclidian distances for phase-2 cluster selection
- Version 0.4.7 - 2037
- DCBot inspired weighting of the dimensions (an experiment)
- Added segmentation on approach angle and time-since-fired. (Also DCBot inspired)
- Squared Euclidian distances used for both phase 1 & 2. (Squared since it should render the exact same results and I save quite a few calls to Math.sqrt() this way.)
- Some other stuff too that I can't really recall. All in all too many experiments in one batch to really be useful for feedback. But it seems in my little testing that the short-battle performance has imporoved.
(Everything is about the gun in this bot. The movement is always the same as the current dev version of CassiusClay.)