Hickup in rankings

Jump to navigation Jump to search
Revision as of 24 March 2022 at 04:27.
The highlighted comment was created in this revision.

Hickup in rankings

Hi all, seems that for some reason the participants list for roborumble, minirumble and nanorumble had a hickup (not for microrumble ??)

This means that the rankings start again from zero, but luckily all older results get in as soon as one battle has been fought. In order to get the rankings up-to-date again, every bot has to fight every other bot one time.

So, if you have the time and opportunity, please start your rumble client.

    GrubbmGait (talk)17:12, 22 March 2022

    It seems less worse than I thought at first sight. As soon as a bot has fought a battle, it appears in the ranking.

    When all bots are present, all bots have to fight one battle to get all pairings back. Hopefully LiteRumble is smart enough to get that done in one pass.

      GrubbmGait (talk)17:24, 22 March 2022
       

      That happens once every a few years ;( Maybe LiteRumble should have some check to prevent removing more than 100 bots at a time? Anyway LiteRumble *is* smart enough to recover with only 2000+ battles (1000+ to add back, 1000+ again to fix pairings), instead of 1000000 battles.

        Xor (talk)06:54, 23 March 2022

        However a bug in the rumble client actually prioritized already existing bots over bots without ranking, except in the clean run case. So it actually takes much more battles to add missing bots back ;(

        I submitted a PR for this bug. https://github.com/robo-code/robocode/pull/61.

        Bots without rank should always take highest priority, in all scenarios.

          Xor (talk)08:32, 23 March 2022
           

          Bad news. Once a bot is added, the pairings are only updated for newly added battles. e.g. one bot with 400 pairings, gets to 401 when one battle is submitted. The rest of the pairings seems not to add automatically. So this means 1000000 battles are needed. ;(

            Xor (talk)10:05, 23 March 2022

            I submitted a PR to literumble. https://github.com/jkflying/literumble/pull/3 Hopefully this PR will solve the issue, and with 1000+ battles, the ranking should restore stable.

              Xor (talk)11:15, 23 March 2022

              Merged and deployed, thanks. Should we also update Robocode versions?

                Skilgannon (talk)20:17, 23 March 2022

                Great! Anyway I think we could wait for the next release, where the fix for unranked bots are merged ;)

                  Xor (talk)04:47, 24 March 2022
                   

                  Looks like the ranking isn't recovering as fast as expected, bots with 400 pairings still goes to 401 instead of 1189 after 1 battle. Any idea of this behavior after the PR?

                    Xor (talk)05:05, 24 March 2022

                    Note that in the 507 still unstable bots, 449 are from minirumble, 421 are from microrumble and 228 are from nanorumble. So it seems that bots that also in mini/micro/nano rumble takes longer to get to stable state.

                    Also note that 391 / 507 unstable bots are last updated since the deploy of the fix.

                      Xor (talk)05:27, 24 March 2022
                       
                       
                       

                      It is restoring quite fast. At this moment half of the bots in roborumble have all their pairings back. And most of the others have at least 800 pairings.

                        GrubbmGait (talk)13:17, 23 March 2022

                        That may be caused by the batch processing. However, it should be fully recovered if it's caused by batch processing.

                          Xor (talk)05:07, 24 March 2022