Difference between revisions of "Chronicle of 2017"

From Robowiki
Jump to navigation Jump to search
(Add news)
(Add news)
Line 8: Line 8:
 
* '''August 29, 2017''' – '''[[Roborio]]''' by [[User:Rsalesc|rsalesc]] entered the top 30.
 
* '''August 29, 2017''' – '''[[Roborio]]''' by [[User:Rsalesc|rsalesc]] entered the top 30.
 
* '''August 30, 2017''' – Roborio ranked at #11 in APS and #5 in Survival (!!)
 
* '''August 30, 2017''' – Roborio ranked at #11 in APS and #5 in Survival (!!)
 +
* '''September 3-8, 2017''' – There were discussions on the wiki ([[Thread:Talk:RoboRumble/Client java version|thread 1]], [[Thread:Talk:RoboRumble/ThreadDeath problem|thread 2]], [[Thread:Talk:RoboRumble/ThreadDeath problem and large amount of skipped turns|thread 3]]) about Java versions, skipped turns, [[MoxieBot]] bugs, forced robot stops, RoboRumble clients, CPU usage, time per turn, Robocode internals, Robocode versions, ThreadDeath exceptions, race conditions, dropped log messages, TPS sliders, CPU constants, thread sleeping, and timing mechanisms. At least [https://sourceforge.net/p/robocode/bugs/387/ one bug in Robocode] was identified (and [https://github.com/robo-code/robocode/commit/a69d8e85bd65b33d432110de4a7befe39009dee5 promptly patched]).
 
* '''September 5, 2017''' – '''[[GrubbmThree]]''' was [[Thread:Talk:GrubbmThree/Planned investigations|updated]]. '''[[MaxRisk]]''' was reintroduced into the rumble.
 
* '''September 5, 2017''' – '''[[GrubbmThree]]''' was [[Thread:Talk:GrubbmThree/Planned investigations|updated]]. '''[[MaxRisk]]''' was reintroduced into the rumble.
 
* '''September 6-7, 2017''' – [[Thread:Talk:RoboRumble/Participants/Keeping worse bots|An attempt]] to stabilize rankings and reduce load on [[RoboRumble]] clients by removing bots ranked lower than [[SittingDuck]] ironically led to a competition to create the worst-ranking robot possible. Current competitors include '''[[awful]]''' by [[Beaming]], '''[[WorstBot]]''' by [[Xor]], '''Retreat''' by [[Sheldor]], and '''SuperSittingDuck''' by [[MN]].
 
* '''September 6-7, 2017''' – [[Thread:Talk:RoboRumble/Participants/Keeping worse bots|An attempt]] to stabilize rankings and reduce load on [[RoboRumble]] clients by removing bots ranked lower than [[SittingDuck]] ironically led to a competition to create the worst-ranking robot possible. Current competitors include '''[[awful]]''' by [[Beaming]], '''[[WorstBot]]''' by [[Xor]], '''Retreat''' by [[Sheldor]], and '''SuperSittingDuck''' by [[MN]].
* '''September 3-8, 2017''' – There were discussions on the wiki ([[Thread:Talk:RoboRumble/Client java version|thread 1]], [[Thread:Talk:RoboRumble/ThreadDeath problem|thread 2]], [[Thread:Talk:RoboRumble/ThreadDeath problem and large amount of skipped turns|thread 3]]) about Java versions, skipped turns, [[MoxieBot]] bugs, forced robot stops, RoboRumble clients, CPU usage, time per turn, Robocode internals, Robocode versions, ThreadDeath exceptions, race conditions, dropped log messages, TPS sliders, CPU constants, thread sleeping, and timing mechanisms. At least [https://sourceforge.net/p/robocode/bugs/387/ one bug in Robocode] was identified (and [https://github.com/robo-code/robocode/commit/a69d8e85bd65b33d432110de4a7befe39009dee5 promptly patched]).
 
 
* '''September 10, 2017''' – '''DeepThought''' by [[User:Cb|Cb]] entered the top 30 in general 1v1 [[RoboRumble]].
 
* '''September 10, 2017''' – '''DeepThought''' by [[User:Cb|Cb]] entered the top 30 in general 1v1 [[RoboRumble]].
 
* '''September 12, 2017''' – '''[[Monk]]''' by [[User:Rsalesc|rsalesc]] entered the top 15 in [[MeleeRumble]].
 
* '''September 12, 2017''' – '''[[Monk]]''' by [[User:Rsalesc|rsalesc]] entered the top 15 in [[MeleeRumble]].
 
* '''September 13, 2017''' – '''[[ScalarBot]]''' by [[User:Xor|Xor]] ranked at #9 in APS and #11 in survival.
 
* '''September 13, 2017''' – '''[[ScalarBot]]''' by [[User:Xor|Xor]] ranked at #9 in APS and #11 in survival.
 
* '''September 14-17, 2017''' – [[Thread:Talk:RoboRumble/Participants/GigaRumble/Nominations 2017-09|A discussion]] about updating the [[RoboRumble/Participants/GigaRumble|GigaRumble]] led to the creation of its rumble config files, allowing the GigaRumble to be run for the first time in three years.
 
* '''September 14-17, 2017''' – [[Thread:Talk:RoboRumble/Participants/GigaRumble/Nominations 2017-09|A discussion]] about updating the [[RoboRumble/Participants/GigaRumble|GigaRumble]] led to the creation of its rumble config files, allowing the GigaRumble to be run for the first time in three years.
 +
* '''September 16-26, 2017''' – There were discussions on the wiki ([[Thread:Talk:Maximum Escape Angle/Is wiki wrong about MEA?|Beaming's thread]], [[User:Xor/Better MEA formula|Xor's page]], [[User talk:Xor/Better MEA formula|discussion of Xor's page]], [[User:Dsekercioglu/MEA|Dsekercioglu's page]], [[User talk:Dsekercioglu/MEA|discussion of Dsekercioglu's page]]) about [[Maximum Escape Angle]] and the formulas used to calculate them.
 
* '''September 24, 2017''' – After one month of continuous development and testing, '''[[GrubbmThree]]''' 0.9x outranked '''[[MaxRisk]]''' (#440 vs. #450 in APS, #407 vs. #429 in [[PWIN]], #488 vs. #497 in Survival). It is now the best 1v1 [[rambot]] in the [[RoboRumble]].
 
* '''September 24, 2017''' – After one month of continuous development and testing, '''[[GrubbmThree]]''' 0.9x outranked '''[[MaxRisk]]''' (#440 vs. #450 in APS, #407 vs. #429 in [[PWIN]], #488 vs. #497 in Survival). It is now the best 1v1 [[rambot]] in the [[RoboRumble]].
  
 
[[Category: Chronicle]]
 
[[Category: Chronicle]]

Revision as of 21:36, 26 September 2017

RoboWiki isn't dead! Here's what happened this year: