Glacier/Version History

From Robowiki
< Glacier
Revision as of 12:50, 19 June 2021 by Rednaxela (talk | contribs) (Document Glacier 0.2.11)
Jump to navigation Jump to search
Glacier Sub-pages:
Glacier - Version History - Hypothermia - GlacialHawk
  • 0.2.11 - 18/06/2021
    • MeleeRumble ‒ APS: 69.63% (7th), PL: 390-8 (8th), Survival: 47.41%
    • Apply BulletHitEvent & HitByBulletEvent to cancel out expected energy change for purposes of wave detection.
  • 0.2.10 - 18/06/2021
    • MeleeRumble ‒ APS: 69.71% (6th), PL: 390-8 (8th), Survival: 48.35%
    • Revert to 0.2.8
    • Replace virtual bullets with more accurate precise intersection waves
      • This was based upon importing code I wrote around May 2012 or so, yet never actually became part of a released bot.
      • Still only tries to dodge HOT and linear targeting like before, but now done with much more accurate waves.
        • "much more accurate" means that in a test where Glacier never fires, 1v1 versus sample.TrackFire, it now dodges flawlessly, often with very precise dodges. Glacier 0.2.8 in contrast would make some mistakes. Getting the basics like this to be accurate really counts
      • Note that when enemy robot scans are interpolated, the wave detection code will generate multiple waves, one for each tick where firing could have occurred. The wave then has an associated probability of existing, which danger score caused by the wave is weighted based upon.
      • Associated with this, the "go-to" path simulation in the |minimum risk movement engine is replaced with a more accurate version.
    • Movement intent is now accounted for when aiming.
    • Keep dodging anything that needs to be dodged in the moments after all other bots are gone.
    • Commentary:
      • This version does measurably worse in overall 1v1 rumble than 0.2.8, despite doing better in melee rumble. I presume this is due how, while it dodges HOT+linear more reliably, it also is more predictable versus certain other targeting. This is fine, since 1v1 is only a diagnostic measure of where things can be improved for now.
      • Interestingly, this version is now a real huge ProblemBot for Tron, with -60.82 KNNPBI as of this writing. <- This is because Tron is currently broken in Robocode 1.9.4.2 & OpenJDK 11 for some reason.
      • It's also by a hefty margin the lowest overall ranking bot in 1v1 rumble to have >0.7% in the "Vote" column, which counts for something in my eyes.
  • 0.2.9 - 17/06/2021
    • MeleeRumble ‒ APS: 69.06% (8th), PL: 389-9 (10th), Survival: 46.68%
    • A quick hack of a movement tweak. Seems it made things slightly worse in melee (though 1v1 improved slightly?). Will be reverting.
  • 0.2.8 - 16/06/2021
    • MeleeRumble ‒ APS: 69.67% (6th), PL: 390-8 (8th), Survival: 47.09%
    • Fix a bug in targeting. The 'acceleration' feature for KNN search was badly miscalculated.
  • 0.2.7 - 29/10/2009
    • 16/06/2021 results: MeleeRumble ‒ APS: 68.93% (8th), PL: 389-9 (10th), Survival: 42.3%
    • 30/10/2009 results: MeleeRumble ‒ APS: 69.32% (4th), PL: 278-4 (5th), Survival: 90.51%
    • Rewrite the radar, to create a truly optimal melee radar. First of it's kind that I know of.
  • 0.2.6 - 29/10/2009
    • MeleeRumble ‒ APS: 69.14% (4th), PL: 279-4 (5th), Survival: 90.23%
    • Don't use gun turn to assist radar sweeps except 1) at start of battle, and 2) when changing radar directions
      • Using gun to assist radar sweep was previously being bad in the circumstances where the radar just spun in one direction, because it caused the gun to aim in poor directions where it would take longer to aim again from.
  • 0.2.5 - 28/10/2009
    • MeleeRumble ‒ APS: 69.04% (4th), PL: 277-5 (5th), Survival: 90.55%
    • Add the optimal-radar-starting-direction back again, with a stupid bug fixed
    • Don't start moving or recording data until all enemies are known
    • Use the gun/body to to increase the size of radar sweeps ;)
  • 0.2.4 - 27/10/2009
    • MeleeRumble ‒ APS: 69.21% (4th), PL: 279-3 (3rd), Survival: 90.04%
    • Revert to 0.2.2, and then make PIF wall boundary checking more lenient like 0.2.3
  • 0.2.3 - 25/10/2009
    • MeleeRumble ‒ APS: 69.17% (4th), PL: 278-3 (4th), Survival: 90.07%
    • Re-release of 0.2 to check melee score drift
  • 0.2.2 - 24/10/2009
    • MeleeRumble ‒ APS: 68.88% (4th), PL: 277-3 (4th), Survival: 89.64%
    • Revert radar changes of 0.2.1
  • 0.2.1 - 16/10/2009
    • MeleeRumble ‒ APS: 68.28% (4th), PL: 278-3 (4th), Survival: 89.06%
    • Use 'turn towards center' for initial radar direction
    • Use 'shadow' style Play-If-forward for now
      • Pure BFT approach appears to be notably faster in my tests, but my implementation is locking up from time to time. Not sure it's worth the effort.
  • 0.2 - 26/9/2009
    • MeleeRumble ‒ APS: 69.21% (4th), PL: 277-3 (4th), Survival: 90.31%
    • Quick hack to dodge linear targeting in addition too.
  • 0.1 - 25/9/2009
    • Melee APS diffs:
    • MeleeRumble ‒ APS: 68.95% (4th), PL: 279-4 (4th), Survival: 89.64%
    • Uses GlacialHawk 1.10 targeting.
    • Uses old movement HOT-dodging movement developed just prior to begining the GlacialHawk experiments.
Retrieved from "http://robowiki.net/w/index.php?title=Glacier/Version_History&oldid=56660"