Vote Ranking

Jump to navigation Jump to search
Revision as of 22 March 2013 at 14:59.
The highlighted comment was created in this revision.

Vote Ranking

I gotta say, I love the Vote ranking. Gives you a completely different perspective on the rumble.

    Chase11:48, 22 March 2013

    Yeah, I really like it as well. I'm thinking of doing away with (A)NPP though, it seems a bit redundant, and it uses tons of memory to calculate.

      Skilgannon12:09, 22 March 2013
       

      I have no problem with that. But I think we should get some other opinions on it.

        Chase12:20, 22 March 2013
         

        ANPP is actually the one I love =), but I'm fine with dropping it if you want. I find it pretty meaningful in the GigaRumble.

          Voidious14:20, 22 March 2013
           

          Hmm. My main concern with it is that it requires me to do a full nxn grid of scores, which is taking up a full GB of RAM on the backend, and causing soft-kills. If I could somehow implement it as an incremental score, which is updated along with APS, I wouldn't mind it so much.

          At least with the KNN-PBI I only need sqrt(rumblesize) in memory at once.

            Skilgannon14:26, 22 March 2013
             

            Pretty sure you could do it without nxn grid. You could do min/max for each bot just loading one row (n) at a time. Then ANPP vs each bot the same way. Then each bot's avg with another pass one row at a time. Unless even that process requires nxn with the code/data model. I certainly don't see anyway to do it drastically quicker, like on par with APS.

            It's still probably the most CPU intensive and least useful of the rankings, so I totally agree it's a good candidate for the axe.

              Voidious15:59, 22 March 2013