Hi friends,
Exists a utility that it allows me to divide a database in two parts?
From a part a database with the players who have played as an example more than 100 games, and from the other part a database with the players who have played less than 100 games.
It would be much profit in order to then try the database with ELOstat, which it does not allow to try database with more than 1000 players.
Thanks in advance,
Salvo Spitaleri
Hello Salvo,Hi friends,
Exists a utility that it allows me to divide a database in two parts?
From a part a database with the players who have played as an example more than 100 games, and from the other part a database with the players who have played less than 100 games.
It would be much profit in order to then try the database with ELOstat, which it does not allow to try database with more than 1000 players.
Thanks in advance,
Salvo Spitaleri
There may very well be such a utility BUT may I suggest that you check Leo's WBEC pages. Tab the downloads and select Elostat 1.2b. That version can handle 2000 players.
I hope that this helps.
Later.
Was that the version from my site?Hello Salvo,Hi friends,
Exists a utility that it allows me to divide a database in two parts?
From a part a database with the players who have played as an example more than 100 games, and from the other part a database with the players who have played less than 100 games.
It would be much profit in order to then try the database with ELOstat, which it does not allow to try database with more than 1000 players.
Thanks in advance,
Salvo Spitaleri
There may very well be such a utility BUT may I suggest that you check Leo's WBEC pages. Tab the downloads and select Elostat 1.2b. That version can handle 2000 players.
I hope that this helps.
Later.
Hello Roger,
Thanks for the answer but I have tried ELOstat 1.2b in console mode and unfortunately it can only handle 1000 players.
Best
Salvo Spitaleri
Was that the version from my site?Hello Salvo,Hi friends,
Exists a utility that it allows me to divide a database in two parts?
From a part a database with the players who have played as an example more than 100 games, and from the other part a database with the players who have played less than 100 games.
It would be much profit in order to then try the database with ELOstat, which it does not allow to try database with more than 1000 players.
Thanks in advance,
Salvo Spitaleri
There may very well be such a utility BUT may I suggest that you check Leo's WBEC pages. Tab the downloads and select Elostat 1.2b. That version can handle 2000 players.
I hope that this helps.
Later.
Hello Roger,
Thanks for the answer but I have tried ELOstat 1.2b in console mode and unfortunately it can only handle 1000 players.
Best
Salvo Spitaleri
Frank Schubert told me it could handle until 2000 players.
Best wishes,
Leo.
Hi SalvoHi friends,
Exists a utility that it allows me to divide a database in two parts?
From a part a database with the players who have played as an example more than 100 games, and from the other part a database with the players who have played less than 100 games.
It would be much profit in order to then try the database with ELOstat, which it does not allow to try database with more than 1000 players.
Thanks in advance,
Salvo Spitaleri
Does this mean, that you want some games in both databases? For example player A might have played 200 games. So he should be in the first database. Player B has played 10 games, so he should be in the second database. Yes? When there was a game (or more than one) between A and B - should they be in both databases?Hi friends,
Exists a utility that it allows me to divide a database in two parts?
From a part a database with the players who have played as an example more than 100 games, and from the other part a database with the players who have played less than 100 games.
Hi SalvoHi friends,
Exists a utility that it allows me to divide a database in two parts?
From a part a database with the players who have played as an example more than 100 games, and from the other part a database with the players who have played less than 100 games.
It would be much profit in order to then try the database with ELOstat, which it does not allow to try database with more than 1000 players.
Thanks in advance,
Salvo Spitaleri
Elostat has a setting for "minimum number of games".
Regards
Dave
Yes, exact.Does this mean, that you want some games in both databases? For example player A might have played 200 games. So he should be in the first database. Player B has played 10 games, so he should be in the second database. Yes?Hi friends,
Exists a utility that it allows me to divide a database in two parts?
From a part a database with the players who have played as an example more than 100 games, and from the other part a database with the players who have played less than 100 games.
When there was a game (or more than one) between A and B - should they be in both databases?
Such a tool would not be too difficult to write - at least when the exact spellings of the players are reliable (So for example always "Hübner, R." and never "Huebner, R.", "Hubner, R.". "Dr. Hübner", ...).
Without a specifically written program, it seems unlikely, that it can be done.
Regards,
Dieter
It could do it, if I wrote the code ...Yace could do this? to divide a database in two parts?
From a part a database with the players who have played as an example more than 100 games, and from the other part a database with the players who have played less than 100 games.
This mean, that I want some games in both databases.
For example player A might have played 200 games. So he should be in the first database. Player B has played 10 games, so he should be in the second database.
When there is a game (or more than one) between A and B, only games of player A should be in first database (if Player A have played 200 games and there are 5 games between A and B, then in the first database there will be only 195 games, if I have set "minimum number of game" to 100. If I have set "minimum number of game" to 200, then in first database not there will be neither A neither B).
It could do it, if I wrote the code ...Yace could do this? to divide a database in two parts?
From a part a database with the players who have played as an example more than 100 games, and from the other part a database with the players who have played less than 100 games.
This mean, that I want some games in both databases.
For example player A might have played 200 games. So he should be in the first database. Player B has played 10 games, so he should be in the second database.
When there is a game (or more than one) between A and B, only games of player A should be in first database (if Player A have played 200 games and there are 5 games between A and B, then in the first database there will be only 195 games, if I have set "minimum number of game" to 100. If I have set "minimum number of game" to 200, then in first database not there will be neither A neither B).
I might write the code, if I see, that it would take only an hour or so. Might be possible.
I am not sure I understand. Your example below ...
... has no games in both databases. Under which condition would there be games in both databases?
Also, your example is not that easy. Consider the 3 players, A,B,C (out of many). A played 110 games, B 105 games and C 90 games. So, at first sight, games of A and B should be in DB 1.
Now say, B played 8 games vs. C. Only 97 games left - yes? This puts all games of B into DB 2? Then say A played 15 games vs. B. Now A has only 90 games left. So all the games of A go to DB 2, too?
Other rules would probably easy to implement. For example, count all the games of all players, and put every game where both players had over 100 games in DB 1 and all other games in DB2. Or put every game, where at least one player had 100 games in DB 1 and other games in DB 2. Or put games were one player has over 100 games and the other less, in both databases (or into a 3rd database). As I understand the example above, it seems not easy to implement. But perhaps with using the same procedure more than once, the goal could be reached easily.
Can you program yourself? It might be not too difficult to implement something like this even for a beginner (at least, when one can assume clean PGNs).
Other rules would probably easy to implement. For example, count all the games of all players, and put every game where both players had over 100 games in DB 1 and all other games in DB2.
It could do it, if I wrote the code ...Yace could do this? to divide a database in two parts?
From a part a database with the players who have played as an example more than 100 games, and from the other part a database with the players who have played less than 100 games.
This mean, that I want some games in both databases.
For example player A might have played 200 games. So he should be in the first database. Player B has played 10 games, so he should be in the second database.
When there is a game (or more than one) between A and B, only games of player A should be in first database (if Player A have played 200 games and there are 5 games between A and B, then in the first database there will be only 195 games, if I have set "minimum number of game" to 100. If I have set "minimum number of game" to 200, then in first database not there will be neither A neither B).
I might write the code, if I see, that it would take only an hour or so. Might be possible.
I am not sure I understand. Your example below ...
... has no games in both databases. Under which condition would there be games in both databases?
Also, your example is not that easy. Consider the 3 players, A,B,C (out of many). A played 110 games, B 105 games and C 90 games. So, at first sight, games of A and B should be in DB 1.
Now say, B played 8 games vs. C. Only 97 games left - yes? This puts all games of B into DB 2? Then say A played 15 games vs. B. Now A has only 90 games left. So all the games of A go to DB 2, too?
Other rules would probably easy to implement. For example, count all the games of all players, and put every game where both players had over 100 games in DB 1 and all other games in DB2. Or put every game, where at least one player had 100 games in DB 1 and other games in DB 2. Or put games were one player has over 100 games and the other less, in both databases (or into a 3rd database). As I understand the example above, it seems not easy to implement. But perhaps with using the same procedure more than once, the goal could be reached easily.
Can you program yourself? It might be not too difficult to implement something like this even for a beginner (at least, when one can assume clean PGNs).
Other rules would probably easy to implement. For example, count all the games of all players, and put every game where both players had over 100 games in DB 1 and all other games in DB2.
Return to Archive (Old Parsimony Forum)
Users browsing this forum: No registered users and 25 guests