Thread history

Fragment of a discussion from Talk:WhiteFang
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
No results
I will just be reverting back to it with the XOR filter which doesn't log real waves twice and I will use my better firepower formula to have a better score.
I don't think putting exactly the same bot will help because no bots has been change since WhiteFang but you may be right; my Bullet Shielding algorithm may cause extreme deviations in score.
Dsekercioglu (talk)16:32, 8 August 2018

The only purpose of putting the same bot twice with the same environment is to see how much noise there is with your testing method. Experience of improving ScalarBot told me that most of the time a small change in score is just noice; big drop is bug and big increase is new critical feature.

Xor (talk)15:42, 10 August 2018
I will put after 2.4.5; maybe it is just a great noise which I had been trying to pass for a long time =)
Dsekercioglu (talk)18:38, 10 August 2018
Oh, I am so dumb. It has nothing to do with my movement; contains this line of code:
                if (counter == 0) {
                    possibleFuturePositions[direction + 1] = (Point2D.Double) predictedPosition.clone();
Consequently it is impossible to have the future position predicted but my prediction system doesn't work so it made my scores lower =)
Anyways, thank you so much for your time and I have actually learnt a lot of things.
Dsekercioglu (talk)21:21, 10 August 2018

This is so annoying, the bug I have mentioned above is actually more sensible than "Sometimes predicting the future position correct and sometimes calculating the opposite direction" however, seems like this bug was also a Performance Enhancing bug.

Dsekercioglu (talk)10:01, 11 August 2018