The actual code calculating the number of saved games is here:
http://openfibs.svn.sourceforge.net/viewvc/openfibs/trunk/modules/repbot/src/main/java/net/sf/repbot/savedgames/FilteringSavedGamesReader.java?revision=50&view=markupWhat it does is this:
1) On day n, it receives the saved games list from fibs.com and stores it
2) On day n+1, it calculates the number of saved games as intersection of day n and day n+1. Only saved games reported as saveds on BOTH days are considered.
3) On day n+2, it deletes the old data from day n and the old n+1 becomes the new n, and n+2 becomes n+1
4) Goto 1
The algorithm described above, a sliding window of 2 days over the saved game data, was designed and validated by Avik. He claims it yields more reliable figures than using data only from the current day. I haven't verified that claim, but tend to trust Avik.
This means Repbot almost never will give the same number as the saved games list from fibs.com, which itself almost never will be identical to "show saved". Always keep in mind that the saved games list fibs.com makes available has systemic errors. You should look at the RepBot figure as some sort of averaged and smoothed ballpark estimate of saved games for that player, not an exact number. The latter is impossible to calculate for Repbot, given the error in the input data.
