Tomcat's future

Ok now i can say, that Tomcat reach 15th place. And it's means that easy level is completed and now starts really hard challenge. And there is future plans of Tomcat's development:

• Research kNN vs RS - i think it will first thing, which i will do. But my bycicle inventor's soul encourage me to implement my own vantage tree to NNS
• use in targeting same data source choose algorithm, like in movement. I think this will be second thing
• NN or GA approximator for simple (HOT, Linear and Circular) guns
• return to my new single-tick PIF gun research, which give me 66% hit rate against Crazy and 99% against Walls
• make real good movement (100% against HOT, >99% againt DevilFish and DoctorBob)
• try to implement RS/kNN-GF gun
• Bullet shielding. I leave it at the end, because this points i can get with gurantee. For Tomcat it's more significant improvement, because he successfully exploit information about places, where enemy is not fire
• Multiple wave surfing. I leave it lasty with same reason. Please, who done this, say how much APS you get with this improvement

And main: it's time to sleep a little:)

Good job, and don't worry, if you get too close i'll write a gun and just jump up into the top 10 (Nene uses Raiko's gun, who ranks #85).

Though I don't want to, as I have so much more work to do in the movement.

Chase, kNN rulez! So you may start write yours' gun:p

Wow, that's one hell of a gun update. Nice work, and congrats on top 10!

Thanks:) It was easier, than i expecting:)

Oh nice job.

Interesting, but change RS to kNN in movement give me -1 APS... So getting to club 2100 postponed a little:)

Congrats! I think you are the first one to ever push Shadow out of the top-10! And you are making it harder for me to reach top-5 (if I ever get the time).

Another idea to try: every time, when info about enemy fire angle collected, calculate intersection between profiles produced by hit & visit logs with same segmentations. Theoretically, intersection area must correlate with quality of segmentation. Or, if it can be executed in bounds of turn limit, generate every tick random segmentation, build visit and hit logs with this segmentation and see, how they intersects. In both cases use visit logs with segmentation with best intersection

As for the gains from multiple wave surfing. I don't know the APS figures, but I know this: When I about ideas for how to improve my bot (on Google Plus), Voidious mentioned this as his first item. I'm sure that must mean something. =) That said, CassiusClay does surf multiple waves, in a very simple manner (weighting each wave based on proximity).