timeSinceDirChange bug

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.

---

You can view and copy the source of this page:

Hey, I was trying to plug Druss' gun into Knight (to do some experiments using my MEA/preciseIntersection/features calculations to see if they break your gun) and I noticed something interesting in the code. I looked throughout the wiki and found nothing about it being a known bug (and probably performance enchancing?), so I'll put it here anyway. In the onScannedRobot() method, you override the "lastDirection" variable with the new direction value before updating "timeSinceDirChange". This causes this variable to be incremented at every scan, as you increment it if(lastDirection == direction). So, the normalized version 1/(1+2x) goes quickly towards zero during the round, which is probably almost the same as having a very low weight for this feature. Not sure when you introduced this, but maybe it is worth fixing it in the future for a possible programmatic tuning round.

Return to Thread:Talk:DrussGT/timeSinceDirChange bug.

That certainly isn't intended behaviour, and might also explain why I was never able to get much benefit from this attribute. Thanks!

• Parent
• More

• History
• View source
• Link to

Skilgannon (talk)‎09:55, 31 October 2017

And then that attribute serves as another time attributes ;) you may want to reintroduce it to simulate legacy behavior at some point ;)

• Parent
• More

• History
• View source
• Link to

Xor (talk)‎10:10, 31 October 2017