0.6.X ... some broken. RECALLED
0.41 Score: 1874
You ment in the range of 0 -> 320 didnt you?? Anyway i am not sure how it will affect my rankings, but with my current segmentation i had to take 320 if i wanted it to increase from 160. (my fast learing array segments the distance like this : distance/160 :/ )--deathcon
I meant from 150 -> 320. Just guessing. Not too far from 160. =) I'm pretty sure you'll lose rating points by that change. But we'll see, won't we? -- PEZ
Once again you were right. Want to compete with rozu - the robocode-oracle ??? :D --deathcon
Nah! But you lost about as many points as I gained when going the other direction. Among everything fuzzy in Robocoding this is now non-fuzzy I'd say. Power 2 is better than 3 for all ranges but the very closest. Good to know. -- PEZ
Hey! Does that mean that you gained 23 points just by using firepower 1.9 instead of 2.1? No other changes? -- PEZ
That's it. --deathcon
Amazing. I know I have experimented a lot and at the moment CC uses firepower 1.91. =) But I wouldn't have guessed that it could make such a difference going from 2.1 to 1.9. You know my theory says power 1.7x should be best. But I haven't managed to prove that in real points. This is another nice little PerfomanceMystery?. -- PEZ
I think, that you cant say what firepower is BEST in general. You always have to find a good firepower that fits to your prefered fighting distance AND that of your enemy. Of cause it depends on the strenght of your enemy and your hit rate as well. So once more TESTING,TESTING,TESTING ... :D --deathcon
Well, everybody who really test it seems to end up on 1.9. -- PEZ
You may be right that 1.9 fits to many current top-bots in the current rumble (current opponents) - many bots we have there dont mind about their fighting distance, so top bots can keep their 500-600. They also have good hit rates so 1.9 seems ok. But if your bots fights closer to your enemy 2.3 would take you higher one the ranking table.
Uploaded an updates ShivaRRGC to see how the change of guess factor segments from version 1.10.3 to 2.0beta2 affected the result.