Minibot?

Jump to navigation Jump to search
Revision as of 7 September 2014 at 23:29.
The highlighted comment was created in this revision.

Does anyone know why Gilgalad, and many other megabots are now listed under minibots in the rankings page?

    AW (talk)23:43, 27 August 2014

    We discussed it about a month ago and agreement was that this it the bug in 1.9 robocode. I think we still have not reported it to developers.

    I also noticed that the new robocode seems to run multi threaded (at least in 1.9.2). In my opinion this is not a welcome change, since it eats all available cores of my CPU. I used to run rumble, melerumble, and top 30 melee on my machine, but now they fight between each other and consume more than I want to spare for robocode.

      Beaming (talk)02:06, 28 August 2014

      There are a couple different uploaders presently. When some of them upload, it appears the codesize isn't respected. As soon as a couple others do, the big bots get pruned.

        Gralth (talk)16:13, 29 August 2014
         

        There are a couple different uploaders presently. When some of them upload, it appears the codesize isn't respected. As soon as a couple others do, the big bots get pruned.

          Gralth (talk)16:16, 29 August 2014

          Well, I think my uploaders use to be (and probably still are) culprits. But I did not do any tweaking or modification of stock client. I was also under suspicion that even with mine, some of my machines were doing the correct size report and other were not. But they all have identical configs and java distributions.

          The only thing which might be of importance: I run everything on OpenJDK, may be it has a different way to evaluate the code size.

          Nevertheless, I stopped uploading for a week, so new wrong entries are due to new uploaders. May be we should look for correlation, and see what is the possible reason for the size misreporting.

            Beaming (talk)16:29, 31 August 2014

            Hi all. Apparently all we need to do is to report bugs to developers :) I did so and Fnl fixed it within a day.

            I suggest everyone to upgrade to 1.9.2.2 and kindly ask Rednaxela to tune rumble server to accept client with this version and above.

              Beaming (talk)00:24, 4 September 2014

              It would be Skilgannon that runs the rumble server, not I. ;)

                Rednaxela (talk)14:16, 4 September 2014

                Shame on me, I keep doing this mistake over and over :(

                  Beaming (talk)16:24, 4 September 2014

                  No worries =) The rumble is updated, and only accepting contributions from 1.9.2.2

                    Skilgannon (talk)18:18, 4 September 2014

                    Beaming, it seems your new client is still uploading megabots to the minirumble :-/

                    Edit: never mind, it now seems to be removing them. Maybe they were left over from the old install?

                    Edit2: it seems you have two clients running, one is removing and one adding.

                      Skilgannon (talk)08:19, 5 September 2014

                      Yes, I run 2 clients. More specifically 2 machines, both of which run roborumble and meleerumble, one of this additionally runs meleeTop30. As far as I can see, they have identical relevant software configuration.

                      I do not get it: microrumble and nanorumble seems to be fine with either of the clients, but minirumble is populated with megabots. Any idea what is going on?

                      As fat as I see after some tests, it is not a particular client issue. At start up, either of the clients cleans the mess, i.e. removes bogus entries. But then as it runs, it reintroduces them.

                      Also, both clients complain:

                      Could not load properties file: ./roborumble/files/codesize1v1.txt
                      

                      I will report it to Fnl again.

                        Beaming (talk)13:41, 5 September 2014

                        I think I managed to fix the last part of the bug. I made a version 1.9.2.3 here, which is not official (yet). If it works, I will release it pretty much as it is. If not, I will need to work much harder to figure out what causes the problem?!

                          Fnl (talk)23:22, 7 September 2014

                          Thanks Fnl.

                          Now we wait till Skilgannon switches accepted clients in rumble.

                            Beaming (talk)00:29, 8 September 2014