Difference between revisions of "Thread:User talk:Kev/BeepBoop seems to be losing ~1.5 APS/reply (2)"

From Robowiki
Jump to navigation Jump to search
m
m
Line 1: Line 1:
−
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 agree. Enforcing 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'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.
 
I'll submit a PR for recomputing CPU constant, any suggestions are welcomed.

Revision as of 12:06, 16 January 2023

I agree. Enforcing 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.

Retrieved from "http://robowiki.net/w/index.php?title=Thread:User_talk:Kev/BeepBoop_seems_to_be_losing_~1.5_APS/reply_(2)&oldid=57256"