BeepBoop seems to be losing ~1.5 APS
Fragment of a discussion from User talk:Kev
Jump to navigation
Jump to search
I agree. Enforce recomputing of CPU constant at the start and per e.g. 100 battles is necessary, as it highly affects results and is easy to get wrong. By recomputing periodically, it can also solve the problem that other heavy tasks are affecting RoboRumble, without adding too much overhead.
I'm also thinking about adding some test set before allowing score submission, but that would be a long term plan.
I'll submit a PR for recomputing CPU constant, any suggestions are welcomed.