Erm, yes, I seeeeeeeeeeee, but what does it all mean?

I still would like to come off the list, I am not comfortable sitting there!!   

I guess a bit more info would've been good...

I think it's just S/N where S is the number of saved games for that player and N is the average number of saved games for all players.

No...  See below.

I don't see that it's much more useful than the actual saved count.

The actual saved count has two drawbacks:

1) The count only gives the current number of saved games, not matches that are already expired.  If a notorious dropper doesn't log in for a while, his unfinished matches expire and he starts with a clean sheet;

2) the count is not corrected for activity. I would say that it is OK for an active player to have more saved matches than an inactive player.


During the time my bots were online, MonteCarlo had 313 of its matches expired; TURKIYE only had four.  Does this mean TURKIYE is more likely to finish a match?  No.  MonteCarlo started 73201 matches, so only 0.43% of them were unfinished.  TURKIYE started 35 matches and had four of them unfinished (11%). 

The total number number of unfinished games (of all the players in the table) was 1877 out of 185900 (1.01%).  TURKIYE's "rate" of unfinished matches is therefore 11.45 times the average and MonteCarlo's rate is only 0.42 times the average.  I guess it is safe to state that MonteCarlo is NOT a dropper!  TURKIYE on the other hand has the odds against him.

A score below 1 is BY DEFINITION a good score: it means they finish their matches more often than average.  Looking at the table, I guess that any score below 2.5-3 or so would be totally OK, but that is open to debate...

You say based on stats from 2006-2009...have you been spying on me this whole time?  How else do you know expired saved games over that time frame?

The data that are used for the scores are nothing else than the 'toggle report' results.  Public info that is monitored by Repbot and tobgol all the time.

Where did my first post go?

There is no evidence that was ever a first post...did you check it loaded up and didn't time out with the intermittent server issue?

 

In the long run, there is no distinction between 'expired games' and 'unfinished games': expired games are simply unfinished games.  Since this metric only looks at unfinished matches on an aggregate level, there's no need to tell which match was played to an end and which match wasn't.

For all players in the database you add two counters:

A) number of started matches, and

B) number of finished matches.

Whenever you see something like

   "AAAA and BBBB start an n point match"

you increase A for players AAAA and BBBB by 1. (Of course unlimited matches should be skipped.)  Whenever you see

   "CCCC wins an n point match against DDDD"

you increase B for players CCCC and DDDD by 1.  The numbers shown in the table above are [(A-B) / A] / [(sum(all A)-sum(all B)) / sum(all A)].

The idea is that Repbot issues a warning whenever the score of a player is above a certain level. I think with a little bit of mathematics, this level can even be player specific (based on his total number of started matches), so that NIHILIST's score of 33 would NOT be considered too high (only 3 started matches after all) but TURKIYE's score of 11 would.

I would say "RepBot, start logging!"


PS I presented the table NOT for naming and shaming reasons but to give an impression of whether or not this metric works. Maybe it is better if stog or socksey deletes it from FIBSboard.

Your proposed statistic keeps a historical record of saved matches, so even after the match expires form the server, it still counts in the user's reputation.

Repbot already detects match events, which is start and both regular and irregular end of matches. The events are stored in a mySQL table. This is needed to enforce Patti's rule that opinions can only be cast 24h after the last match event.
Code:
http://openfibs.svn.sourceforge.net/viewvc/openfibs/trunk/modules/repbot/src/main/java/net/sf/repbot/linelistener/MatchEventListener.java?revision=50&view=markup


Currently these events are garbage collected after 24h, because they no longer can possibly matter for the 24h rule.

The started-vs-finished matches metric boomslang proposes can be implemented as a rather simple extension to this table. First it needed to tell between different match events, start, end, user-logout-during-match. The latter is also already supported by RepBot and can be re-used. The event types are here:
http://openfibs.svn.sourceforge.net/viewvc/openfibs/trunk/modules/repbot/src/main/java/net/sf/repbot/linelistener/Monitor.java?revision=50&view=markup

The rationale for garbage collection was to keep the DB small because it is backed up daily and transfered to a backup location. I consider this too important to break it, or to bloat the DB with years of historic match start/end event data. So we need a refinement of the algorithm which aggregates the counts without the need to keep an arbitrarily long history. A possibility would be to keep the last say 6 month, and after that just keep an integer counter for match start and match end events.

That means that A and B must be calculated from 2 inputs, the elaborate event table for the last 6 months and the aggregated historical data older than 6 month. Given that events years back may be irrelevant, using a sliding window may actually even better. That means the quotient boomslang proposes is only calculated over match events for the last say 6 month. That should keep the table at a constant size and still is good enough in my view.

Another alternative, if you guys convince me that we really need an arbitrarily long history, is to exclude the match event table from the backup. Local disk space is a non-issue, of course. The rationale here is that if I am struck by lightening tomorrow, anybody must be able to pick up source and DB backup and continue RepBot. That wouldn't be the case if RepBot relied on private files only available on my server.

One obvious problem is that Repbot is not always online, so it would miss counting some matches - perhaps even resulting in some players having more completed matches than matches.  I don't think this is a showstopper, but something to consider.

Repbot has an uptime of 99%, it basically only goes offline for a minute if the server kernel or repbot itself is updated. Recovery after fibsquakes is good, repbot typically is one of the first bots back online after a server hickup. I am with Patti here: this is a game server and not a financial industry application. If we lose a few events, I couldn't care less

Implementation wise, each of you is welcome to add the functionality to RepBot. It is open source. My only condition was that it is done cleanly within the existing architecture. Avi Kivity is a genius coder and created excellent, easily maintainable code with a clean OO architecture. I intend to keep RepBot in that shape and will refuse incorporating dirty hacks. That said, 80% of the code needed is already there for the 24h rule, so carefully augmenting it shouldn't break the architecture.

The other issue is how to present the new metric. I can not simply change the output syntax of any command, because legacy bots and clients parse RepBot output and can break. So the new functionality must come as a new command. I would like to see an implementation of my weighted-sum approach here, otherwise for each new idea we need a new command, rendering the command interface hopelessly cluttered in a few years. Always keep in mind the commands are an API 3rd party software outside my control hardcodes. So I am very conservative here and insist on a clean command line interface design which can stand the test of time.

Any takers?

The rationale for garbage collection was to keep the DB small because it is backed up daily and transfered to a backup location. I consider this too important to break it, or to bloat the DB with years of historic match start/end event data. So we need a refinement of the algorithm which aggregates the counts without the need to keep an arbitrarily long history. A possibility would be to keep the last say 6 month, and after that just keep an integer counter for match start and match end events.

For my proposed metric there is no need to keep a log of individual events.  The only thing needed are two counters per player (started and finished matches). They should be backed up though, but that is not an issue.

It is also not needed to know if a player logs out during a match. (Although it might provide extra information). "Toggle report" information is the only input needed.

I think the implementation is therefore quite straightforward, don't you think, inim?

ah_clam has finished 78.3% of matches in the last six months and 84.3% overall.

I think expressing it as a percentage will be more easily understandable to most people than boomslangs normalized ratio.

My suggestion would be to issue just a simple warning when the ratio is too high (similar to RepBot now deciding that a reputation below 0 is BAD and above 0 is GOOD) and don't bother the user with numbers.
(If a user needs to see a number, then it should be normalized and it should be based on the player's  UNFINISHED percentage and not it's FINISHED percentage. 99.5% finished and 98.5% finished doesn't look like a big difference, but the latter is three times as high when it comes to unfinished percentage.)

I also don't think the metric should use a sliding window.  The more data about unfinished matches, the better the statistics get.  Long time users are not likely to suddenly start dropping matches.  Lots of effort was put into his/her account after all.


Maybe inim can tell what is needed (Eclipse, mySQL, ...) for adapting RepBot's code?