BeepBoop seems to be losing ~1.5 APS

Jump to navigation Jump to search

I see your point, but we should not forget that there are probabilities involved. Maybe WallGuy3 get lucky once. For example, BeeBoop was spawn in the corner very close to the opponent.

Also, looking in the rumble logs is a bit useless without ability to correlate them with load of the system.

Ideally, we should solve it in the robocode client and not by running in pristine/controlled environment. None of us can dedicate computers to a single task. A potential solution is to have a thread which estimates CPU load (but even then there could be transient load spikes which might be undetected).

Beaming (talk)‎03:54, 8 February 2023

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

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

Return to Thread:User talk:Kev/BeepBoop seems to be losing ~1.5 APS/reply (10).

Totally agreed about logging. Will do it right away.

Beaming (talk)‎05:02, 8 February 2023
 
 
Retrieved from "http://robowiki.net/wiki/Thread:User_talk:Kev/BeepBoop_seems_to_be_losing_~1.5_APS/reply_(9)#BeepBoop_seems_to_be_losing_.7E1.5_APS_6940"