European Go Database / Wishlist Old

Sub-page of EuropeanGoDatabase

A page to hold old requests to the EGD

Table of contents

Winning probabilities

gaius: I looove this feature. But it's extremely slow when you request the winning probabilities from 1995 up to 2010 (basically, the whole period). I can also imagine that processing such a request puts a fairly big strain on the server... Maybe it's an idea to save the winning statistics of the *entire* database in a text file which is periodically updated, so that it can be retrieved quickly?

  • Flatline: Sure. My idea was to let people play around with the new toy for a while, then analyze the queries frequency from the logs and - according to the results - give a menu of possible choices (e.g.: "last year", "last month", "the whole database", "choose your own range", etc.). I'll do it, soon or later. For the time being, I'm happy that you looove the feature :-)

Ratings calculator (done)

  • IanDavis: I would like to request a ratings calculator for those of us who can't wait to find out what our rating will be next month.
    • DJ: Hi Ian, I've forwarded your wish to Paolo and Aldo... I'll keep you posted on the development.
    • Flatline: Hi Ian. As you know, EGD has changed its nature a couple of weeks ago (today is April 19th, 2009). Now tournaments results are uploaded directly by organizers, and all ratings are immediately updated. I hope this answers to your question.
      However, I'm also thinking about a GoR calculator to add to EGD for on-the-fly simulations. I'll release it soon.
      • IanDavis I am extremely impressed by what I have seen so far. Real Time updates, GoR changes per player, head to head information, EGD appears to have everything you could want.
        • Flatline: Thank you Ian, I'm touched :-)
    • Flatline: At last I did it: the GoR calculator is online. It is possible to simulate up to 10 games, declaring GoRs of opponents or leaving EGD to retrieve it via AJAX by typing PINs or last names.
  • geoff: The ratings calculator is excellent - thank you very much Aldo. Just one small improvement could be made. After getting the final GoR, if you change to some other page and then return, the results have been cleared. It would be better if you had a 'Clear results' button. Then clearing of results is under user control.

International tournaments (answered)

  • tapir: What is the point in adding data from e.g. the KPMC to the EGD?
    • Phelan: It was added to the [ext] European official ratings, and imported from there. Perhaps Ales Cieply can better answer that.
    • Herman: I assume that the point is that European players participate in the KPMC, thus adding those results improves the accuracy of their ratings.
    • tapir: Doesn't it add dozens of players from everywhere (that is without much games in the database = inaccurate rating) to the database? I thought the EGD is somehow an official outlet of the European official ratings... Am I wrong?
      • IanDavis It is useful to store such information, some federations may use this when choosing whether to promote a player based on their WAGC performance.
        • tapir: I won't argue against storing such information, but I don't see the point in keeping pro-ratings, worldwide amateur ratings according to WMSG, WAGC results only.

International tournaments, revisited (answered)

  • tapir: I want to restate my case about the inclusion of international tournaments and all players there with an example. Just look at this - Han Sang-hun is 13th in the korean pro rating:
15213374	Oh	Chimin	 DE	Ber	7d	2785	11	3
14237795	Han	Sang-hun KR	xxx	3p	2782	2
    • Herman: I think that the inclusion of such results can be useful. At events like the WMSG or WAGC, half the players there are European, so they will play many matches against each other. Korean players like Han Sang-hun are not actually ever put in the official EGF rating list (which only lists players from EGF member countries), and are thus more of an artefact. I do think that it would be good if the Find Player page filtered to something like "Players from EGF member countries only" by default to avoid listing only player like Han Sang-hun. (Also, I think the EGF assumption of 1p = 7d = 2700 is flawed, especially for Korean and Chinese professionals, but that is another matter).
      • tapir: Of course performance in worldwide events is important. But EGD becomes instantly a worldwide rank/rating database - despite lack in data for them. Aligning two rating systems (1p = 7d) can only work if there is some exchange between them.
        • Herman: GoGoD includes the ProGoR ratings that Ales Cieply once calculated, applying the EGF rating formula to the professional games in the GoGoD database. It would be interesting to see how they match up with the EGF ratinsgs, but as you said, that requires some exchange between them. The WMSG provides some exchange between amateurs and professional, as do a few other tournaments (eg: Ing Cup), but such games are rather limited.

Relation between EGD and EGF (answered)

  • tapir: Ales Cieply or Marco Silles according to him ([ext] http://gocafe.blogspot.com/2008/08/ales-cieply-gibt-egf-rating-ab.html), he'll maintain the GoR in future? I don't understand the relation between GoR and EGD at all...
    • Ian?: The EGD is an accessible frontend to the tournaments used to calculate GoR
    • Phelan: It seems that the European Go Ratings will be maintained at the EGD starting from April. Note on [ext] http://gemma.ujf.cas.cz/~cieply/GO/gor.html "The EGF ratings are moving to the European Go Database. We intend to complete the move by the next (April) update. A new system for results submission is already functional."
    • tapir: Deshis knowing German might be interested in this: [ext] http://gocafe.blogspot.com/2009/03/egf-rating-verschmilzt-mit-egd.html - merging of GoR and EGD - with an online access and semi.automatized result processing + the old issue FIGG/AGI, with the AGI maintaining the EGD while not officially EGF member.
    • Phelan: Deshis not knowing German might also be interested in it, and use babelfish to get the gist of the article. ;) Thanks for posting it here.
    • Flatline: I have to give an answer to this question:
      > I don't understand the relation between GoR and EGD at all....
      Starting from April 3rd, 2009, EGD has become the official repository of european tournaments, and every time a tournament is added, the GoR is automatically recalculated at once. No human intervention is needed any more.
      Of course there is a human supervisor, let's call him the "Ratings Manager".
      Today, this person is Aleš Cieply.
      • Flatline: I forgot to update this piece of information: as of August 2009, this person is me (Aldo Podavini)

Changing personal info (answered)

  • tapir: I moved. How can I change city and country entry in EGD?
    • Phelan: I used to ask the person in charge of updating our country's results to send an email to Ales. I don't know if there is a better way to do this in the current system, though.
    • tapir: I thought the whole point of the update was not to depend on Ales for everything... so this is a feature request :)
    • Flatline: Well, the whole point of the update concerns several aspects. One of them is definitely not to depend on the Ratings Manager for everything, another one (not less important) is to have a real-time update of results and ratings.
      Anyways: club and country are updated every time a player takes part in a tournament, with the new data declared by the tournament organizers. Of course, when a change occurs, it would be nice not to wait for the next tournament and submit the change at once. The new backend features allow this, but at the moment this function is restricted to the Ratings Manager. Maybe it will be opened to all people allowed to submit results, when we are sure that everything works fine. At the moment, we are still testing the new functionalities: they have been released a couple of weeks ago :-)
    • tapir: Oh, my tournament organizer just forgot about it, it seems. Now, what should I do? Email to secretary@agi.go.it (that is you, flatline?) with player id and current location?
      • Flatline: Yes, it's me behind that address :-)
        The right person for these issues is the Ratings Manager, who at the moment is still Aleš Cieply. Anyways, writing to me will work fine as well :-)
        • tapir: Adding Ales' email address to the page here or to the egd page may be helpful. The SL page doesn't reflect the current situation anyway.

Tournament classes rationale (answered)

  • tapir: Is someone who gets no sleep / drink too much on Go Congresses really a worse player? Or: What is the rationale behind weight differences in A, B, C class tournaments?
    • Classes differ by time controls. A are serious; long time limits, C quick, dirty :)
      • tapir: We should add this somewhere...

Rank resets (open)

  • tapir: The EGD policy to cope with fast-improving players is to reset the rating if a players declares a rank two stones above his old one. Incidentally some associations (e.g. Switzerland) try to prevent players declaring a rank two stones stronger than last time, thus effectively disabling the policy. Any thoughts about this? Doesn't this lead to overall rank deflation?
    • IanDavis: I strongly suspect that this may be the case. Especially in the cases where a large group of new or young players join the organisation. In fact I have produced graphs which I believe show this effect.
      • tapir: Will you share this graphs?
        • IanDavis: They are available on GoDiscussions forum actually. What I did was to make a histogram for active go players each year. I took bins 50 rating points wide, and mapped the change in the number of players in these bins per year per country. My impression is that the promotion system used in a particular country appears to influence the form or shape of the histogram. However there is less data than you would want to be able to make firm conclusions over this. The EGD actually has a similar statistics function, but its bins are far too wide (500 rating points) to show anything interesting.
          • tapir: I opened an account there to use the search function and finally found the graphs ([ext] http://www.godiscussions.com/forum/showthread.php?t=4075). Imho these graphs (normalized rating distribution etc.) show more about the population and the influx of new players than about deflation.
            • IanDavis: Possibly, but I believe that since influx of new players happened at the same time (Hikaru No Go) the differences between countries are interesting.
    • mgoetze: Yes. Another interesting statistic to consider is the GoR gains/losses of players from one country attending a tournament in another country. For instance, Finnish players at the LOGC 2003 gained 86 GoR points on average. I wrote about this problem in more Detail back in 2004 on the German Go Federation Forum ( [ext] http://www.dgob.de/yabbse/index.php?topic=1054.msg117798#msg117798 ).
      • tapir: Any further study of this effect? In recent years for different countries?
  • isd: I was looking at [ext] Svetlana Shikshina's playing card. I noticed she'd had a reset when she was promoted (purely for ceremonial purposes) to 3p. Is this normal practice in the pro ranks? Applying the policy used for amateur dan ranks it's an unquestionable decision, but I wondered if this was an eyebrow raiser. :)

Tournament waiting list (answered)

  • LovroF : Would it be possible to put something on the front page of EGD like tournament waiting list. List of tournaments which were sent to EGD but not yet approved by supervisors.
    • Flatline : That's not useful, IMHO, since usually tournaments stay in waiting list for not more than some hours. Furthermore, the RM can have his good reasons to leave them in stand-by, so I'd prefer not to put pressure on him.

Showing only EGF ranked players (done)

  • tapir: I'd like to have an option to not display a) the inactive players b) the players with "0" EGF rank. Instead of b) it would be possible to just change the sorting - starting with 1, with the 0 added at the end.
    • Herman: This is the option "EGF Ranked" in "Players filter" at the Find player page. The same list can also be found through [ext] http://www.europeangodatabase.eu/EGD/EGF_rating_system.php (the official rating lists).
      • tapir: Asking silly questions has the merit that step by step this becomes a genuine FAQ. I missed the option though :)

Rating calculation with old events (done)

  • Herman: I recently noticed that ratings are not always recalculated correctly when older events are added. For example, recently the [ext] Dutch Go Competition was added, which dates to march 9 of this year. I noticed that despite a very good result, the rating for [ext] Frederik Spanhoff did not actually seem to change. Now when I look at his GoR evolution, I can see that both this event, and the next one he played (Nijmegen, played march 21) are given as being calculated from a start rating of 2328.688. So apparently, the earlier event (which was entered later) is not taken into account when calculating the rating after the later event. Perhaps this is normal and there is a periodic recalculation, but I was curious about it.
    • Flatline: Good question. As a general rule, EGD recalculates the ratings at once when a tournament is submitted. But for old tournaments, in order to avoid massive waste of time when multiple submissions are made (a recalculation requires about ten seconds per month), EGD keeps track of the submitted tournament, but leaves to the Rating Manager to choose when launch a massive recalculation. Now you have spotted a case when this recalculation has not been launched; you got a point :-) Have a look at [ext] Frederik Spanhoff's card now: everything is ok.
      • Herman: Ok, thanks! Maybe massive recalculation could be automatically triggered late at night under certain conditions?
        • Flatline: Of course it can. But I don't want to spread the idea that EGD is adjourned once a day: EGD is adjourned as soon as the RM completes the confirmation process. The fault you have spotted must be regarded as a little lapse.
        • Flatline: Today (July 9th,2009) I've changed the confirmation workflow, so that now GoR is recalculated at once when a tournament is submitted, even when it is an old one.

Link to player (done)

  • Uberdude First of all well done on making a great site. However with all the recent changes it seems there has been a regression. There is no longer a link from the tournament page to the player page. Both the PIN and Name link go to that player's detail for that tournament rather than the player page. There used to be a link to do this and I found it really useful and I miss it now. In detail: I go to my player page and click link to my most recent tournament [ext] http://www.europeangodatabase.eu/EGD/Tournament_Card.php?&key=T090502B&pin=14337147 which lists my opponents. Both the "12801932" and "Kiyohiko Tanaka" links go to his results for the same tournament. I think the "12801932" link should go to his player page, i.e [ext] http://www.europeangodatabase.eu/EGD/Player_Card.php?&key=12801932. Currently I can find no way to do this other than copying the PIN and typing it into the URL directly.
    • Flatline Hi Uberdude, thanks for your appreciation. Fortunately there is a much faster way to reach "Kiyohiko Tanaka"'s card : you can click on the player's photo displayed at the left of the players list and - as happens in every social network when you click on a member's photo, as far as I know - you go to that player's card. So, the card of "Kiyohiko Tanaka" is only 2-clicks away from you :-)
      • Tapir: I admit that I missed the link as well.
      • Uberdude Ah, I missed that, and seems other people did too. Still, having both the player name and ID going to the same place is redundant, and 1 is better than 2 =)
      • tapir: I guess the reason people miss this option is that most people don't have a photo.
  • geoffkaniuk?

The last step in submitting results is a list of ratings resets in the tournament, and EGD asks you to check their grades before submitting. It would be really handy if you could include a link direct to the player's graph so that one can check on each one without having to go out of EGD.

Being able to put in the names, as they are (answered)

  • Zarlan: Apparently the EGD doesn't accept some letters, such as å,ä,ö,ü...

It also doesn't accept spaces. This does not reflect reality. There are many names with characters and/or spaces. Such flaws leads to an inability of accurate input of many names. I see no reasonable reason for this, nor do I see how this isn't something that shouldn't be fixed.

  • çÇ ğĞ ı İ ...
  • Flatline: Actually EGD does accept only letters belonging to the [ext] Latin alphabet. There are several good reasons to have such limitation, the first one being that Latin character set is the only one fully ASCII. So, unless we use this limitation, it would be quite difficult to make sure that a) incoming data are always correctly typed and b) data from the database are always correctly rendered by every user's browser. Fortunately, for every non-latin alphabets (including Asian languages, Hebrew, Cyrillic, etc...) there are transliteration systems widely accepted. The reason for not accepting spaces is different. The fact is that EGD is feeded by results tables exported by pairing programs, and in these tables fields are always spaces-delimited. So the space cannot be accepted within a name. When it occurs in real names, it is easily replaced by an underscore "_", and everything is fine :-)
  • Zarlan: Interesting reasons. Now lets see...
"So, unless we use this limitation, it would be quite difficult to make sure that a) incoming data are always correctly typed"
Using the ASCII-only restriction, means that names may be entered in different ways, depending on how they are transliterated or transcribed (this has happened, and is happening, in the EGD), so the ASCII-only limitation only makes the situation worse.
"b) data from the database are always correctly rendered by every user's browser."
While not every computer correctly renders Asian, Hebrew or Cyrillic characters, that isn't relevant. Those characters should be transliterated anyway (they should, after all, be readable by Europeans). Latin letters, however, don't cause any problems, as far as I know. As the wikipedia page you mention says, Latin letters are not restricted to ASCII. Å,ä,ö,ü,ç,ğ,ı,İ,æ,ñ, ø.... Those are all Latin letter.
"The fact is that EGD is feeded by results tables exported by pairing programs', and in these tables fields are always spaces-delimited."
While I understand how that would mean that the data received would generally have that restriction, why does the EGD have to have it as well? Also, as I mentioned above, when a name cannot be correctly written, the transliterations/transcriptions, generally won't be consistent. There are at least three different methods: The space might be skipped or replaced with a - or a _. Different names may be transliterated or transcribed in different ways (even in the same tournament) ...and at a different time, the same name may be written in a different manner.
"Using the ASCII-only restriction, means that names may be entered in different ways, depending on how they are transliterated or transcribed"
Yes, that may be true. But I don't think that this makes the situation worse. Also, consider that names corrections in EGD are quite easy.
"Latin letters, however, don't cause any problems, as far as I know. As the wikipedia page you mention says, Latin letters are not restricted to ASCII. Å,ä,ö,ü,ç,ğ,ı,İ,æ,ñ, ø.... Those are all Latin letter."
I do not agree: they are not Latin letters (we can discuss about "æ", but all the others definitely aren't). I cannot find where wikipedia says differently...
"While I understand how that would mean that the data received would generally have that restriction, why does the EGD have to have it as well?"
Yes, it would be easy to replace underscores by spaces when displaying data; still I think that this would be even worse, because people who prepare results tables, seeing spaces which they cannot use, would possibly adopt different alternatives (dashes, commas, etc...).
"Also, as I mentioned above, when a name cannot be correctly written, the transliterations/transcriptions, generally won't be consistent."
As you probably know, data which are sent to EGD have been written by many different people, with many different programs, keyboards and linguistic skills. For instance: I live in Italy, I have an Italian keyboard (with letters such as "à,è,ì,ò,ù..."). If I'm organising a tournament where is playing a player from Russia, let's say Богданов Виктор (Viktor Bogdanov), I would have great trouble if I had to type his name as it is, because: a) my keyboard hasn't those characters, b) the pairing program I'm using probably doesn't accept them, c) I cannot understand them.
"Yes, that may be true. But I don't think that this makes the situation worse."
It creates many more ways of writing the name, so the said problem (I.e making sure "incoming data are always correctly typed"), is further complicated. How doesn't that qualify as making the situation worse?
"they are not Latin letters (we can discuss about "æ", but all the others definetely aren't). I cannot find where wikipedia says differently..."
Aside from my utter surprise, that you would consider æ, more of a latin letter than the others... Here are some Wikipedia pages:

[ext] http://en.wikipedia.org/wiki/Latin_alphabet#Extensions The very one you linked to. If that's not enough...
[ext] http://en.wikipedia.org/wiki/List_of_Latin_letters [ext] http://en.wikipedia.org/wiki/English_alphabet#Old_English If that's still not enough...
[ext] http://en.wikipedia.org/wiki/Latin_characters_in_Unicode [ext] http://en.wikipedia.org/wiki/Latin-1_Supplement_unicode_block [ext] http://en.wikipedia.org/wiki/Latin_Extended-A_unicode_block [ext] http://en.wikipedia.org/wiki/Latin_Extended-B_unicode_block [ext] http://en.wikipedia.org/wiki/ISO-8859-15

"Yes, it would be easy to replace underscores by spaces when displaying data; still I think that this would be even worse, because people who prepare results tables, seeing spaces which they cannot use, would possibly adopt different alternatives (dashes, commas, etc...)."
What? Why would they make results tables from the EGD? If I understand correctly, the tournament has pairing software, the software exports data that makes a results table, which is then input into the EGD. Why would people then create a results table, something that they already have, from the EGD? ...and why on earth would they have to limit themselves to not being able to use spaces, when they are obviously not creating the table from software that has such a limitation? (also, why should the EGD adapt to the software, and not the other way around?)
"As you probably know, data which are sent to EGD have been written by many different people, with many different programs, keyboards and linguistic skills."
My point exactly.
"For instance: I live in Italy, I have an Italian keyboard (with letters such as "à,è,ì,ò,ù..."). If I'm organising a tournament where is playing a player from Russia, let's say Богданов Виктор (Viktor Bogdanov), I would have great trouble if I had to type his name as it is"
WTF? As I already said:
"While not every computer correctly renders Asian, Hebrew or Cyrillic characters, that isn't relevant. Those characters should be transliterated anyway (they should, after all, be readable by Europeans)."
Now why are you arguing against a position [ext] I obviously don't hold (and have indeed clearly gone against)? That is rather rude. Did you not pay attention to what I said?
"because: a) my keyboard hasn't those characters, b) the pairing program I'm using probably doesn't accept them"
Point 'a' does have some merit, although there are easy ways of going around that. Point 'b' even more so, although I would say the same thing I do about the spaces, for that.

...oh, and BTW, about à,è,ì,ò,ù: Any, not too unusual, keyboard can produce those, with the `-key (the same goes for letter with ¨,~,^ or ´)

  • Flatline: Okay Zarlan, it's quite clear that we have different views on the matter. I just want to point out that:
    all your references from wikipedia speak about alphabets derived from Latin, not Latin itself. Anyways I don't want to stick to this definition, which is of course largely questionable. If you prefer, change my words replacing "Latin alphabet" with ASCII
    I didn't say that people are "making tables from the EGD". Nevertheless, they may (and do) have a look at EGD when putting players data into their tournaments data, especially when they have some doubts about spelling. And, as I said, they CANNOT use spaces.
    The problem with letters "à,è" and any other non-ASCII character should of course be solved using the Alt-n and other tricks, but nevertheless this can represent an obstacle for the general audience.

Having said this, it's clear that we do not agree. Not a problem, right ? Peace :-)

  • Zarlan: On the ASCII issue, I still say that Latin letters (alphabets derived from Latin? Letters derived from Latin, I can accept, but alphabets? Anyway...) are no problem for browsers to render ...and I do not have any idea what your talking about, with Alt-n. [ext] There are keys for ¨,~,^ and ` on any QWERTY keyboard (actually... that one seems a bit lacking, and I'm unsure how common [ext] this version is. Well, any non-English keyboard will have the proper keys ...with the curios exception of the Italian one), but again: why should limitations of input, limit the EGD? Either way, I accept that I won't be able to change your mind on the issue. As to the spaces...
"I didn't say that people are "making tables from the EGD". Nevertheless, they may (and do) have a look at EGD when putting players data into their tournaments data, especially when they have some doubts about spelling. And, as I said, they CANNOT use spaces."
Well they have two sources of spelling, as I see it: The actual person, from whom they presumable receive the name, either way ...so why would they be unsure about the spelling is beyond me (well, unless the player is highly dyslexic) and the EGD. If they decide to use an incorrect replacement for the space... well that's the case now, anyway, isn't it? (and if people know that underscores are automatically turned into spaces, surely they'd start using them, when they need something instead of a space?)

Zarlan: Oh wait! Alt-n!? do you mean like ALT + <number>? Alt codes? That's more something for letters like å and ß (I've memorised the Alt code for ß BTW. That and ¯).

Herman: I think you have an overly optimistic view of the simplicity of this issue. As the discussion already shows, there is no clear definition of what the "Latin alphabet" is. For computers, this might be Basic Latin (ascii) with the possible addition of [ext] Latin-1, [ext] Latin_Extended-A, [ext] Latin_Extended-B, [ext] Latin_Extended-C and [ext] Latin_Extended-D. My browser (FF3 on WinXP) can render Latin-1, Latin-A and part of latin-B, but none of Latin-C or Latin-D.

You reference [ext] ISO-8859-15, which discards the signs ¼, ½ and ¾. But these are extremely common in tournament tables. An alternative might be Windows-1251, which includes all printable characters from ISO-8859-15, as well as ¼, ½ and ¾, but that charset has its own problems, especially on non-Windows systems.

You dismiss Cyrillic with "should be transliterated anyway (they should, after all, be readable by Europeans).", but Russia is a part of Europe, and a member of the EGF, so why not [ext] cyrillize western European names for Russian easy of reading?

I think that instead, an approach that uses both an ascii representation and a "native alphabet" representation (so including Cyrillic, Hebrew, Chinese, etc) would be better. If things like integration between EGD and OpenGotha move ahead, players could simply be referred based on PIN, and tournament organizers could choose to either use the simple ascii representation when printing, or use native alphabet. Using PIN numbers for the results sent to the EGD would also preclude confusion on spelling and transliteration.

"If things like integration between EGD and OpenGotha move ahead, players could simply be referred based on PIN, ..."
I entirely agree with Herman. Of course it will require a lot of work on many sides (EGD, pairing programs, tournament organizers, etc.), but a lot has been done so far, it is important to keep on.

Tapir: Hi all, the cyrillic, hebrew, arabic letter argument in a discussion about latin alphabets pretty much looks like a straw-man. As well the ¼ argument in ISO-8859-15, since it is so very uncommon in names. However, contrary to Zarlan I believe adding all diacritical signs and language-specific special-letters to the package may allow to add the single correct spelling but will generally increase confusion as a lot of players may habitually write simplified-latin-alphabet e.g. in online forms, correctly in on-site forms etc. I would address this only after the PIN (integration) issue, however I don't like that Herman mixes things up conceptually - i.e. non-standard signs in latin alphabets with other alphabet types as native alphabet, because both are different issues. E.g. a name written in non-standard latin alphabet other latin alphabet users may at least read (and pronounce more or less wrong without need for transliteration) while cyrillic, hebrew, korean names will definitively need a transliteration at the European Go Congress.

Flatline: The discussion was not about Latin alphabets, until I had the bad idea of using this definition. I meant it strictly related to the Basic Latin, but unfortunately this messed things up because there are many "Latin alphabets". A couple of posts ago I suggested to drop any reference to Latin since it clearly drives us on a slippery floor, and stick to the ASCII definition. What I'm saying, is that for all the above mentioned reasons, I think that - for the time being - players names in EGD must be in ASCII characters, in order to avoid further complications.

tapir: Well, the request was about names with certain non-standard latin letters and diacritic marks. Regarding complications, I don't disagree :)

  • Zarlan: This might seem like I'm harping on about the issue, despite acknowledging that I wouldn't convince anyone, but Herman made new assertions, so:
I hardly see how not being able to render Latin_Extended-C, Latin_Extended-D and the last few letters in Latin_Extended-B, would cause any problem with names, so I think that's a straw man as well (not saying it's intentional, of course, but...). As I see it, Herman has, in arguing against me, done nothing more or less than confirm my point (about browsers being able to render the characters). The argument that Russia is a big part of Europe is also unconvincing. So is Greece. We don't use Greek letters, because only the Greek can read them. All of Europe can read Latin letter though.
I'd love to see an ASCII+Native solution though, with PINs to refer to players.

Herman: Actually, I was not arguing against you. I was arguing that although I like your idea in general, you seem to have an overly optimistic view of the simplicity of implementing it. I think it is a good idea for the EGD to support extended latin characters. But I also think it is a good idea to support other alphabets, like cyrillic. I think these are part of the same issue, and should not be solved separately, but together. I don't understand why you do not want Cyrillic. Over 10% of the EGD players have a Cyrillic name, are they second class go players?

Zarlan: Not arguing against me? You were arguing against my supposed overly optimistic view of how simple it is. How is that not arguing against me? (and what has your liking my idea, have to do with anything?)
Aaanyway...
Around 90% of EGD players can't read Cyrillic. 100% of EGD players can read Latin letters. Therefore, it is highly impractical to use Cyrillic, seeing as barely anyone would be able to read it. "Basic Latin vs Extended Latin" and "Basic Latin vs Complete Unicode" are completely different issues. To equate them, is an obvious [ext] category error. I don't think, say a Japanese person, would be offended at having his name written in latin letters, in the EGD. Everyone else would have reason to complain, if his name was written in kanji though, as gibberish (which it'd be, to anyone not able to read Japanese) has pretty much zero usefulness.

Herman: The current (basic latin) representation of the EGD is readable by 100% of players. What is the added value of using extended latin, when not all of extended latin is readable by 100% of the players? How many of the "extensions and ligatures" at the [ext] list of latin letters can you read? How many of the letters with diacritics? How many can you pronounce correctly?

In my opinion, the added value is that you can write a persons name correctly, even if that means that not everyone can read or pronounce it correctly. This especially has value in domestic tournaments or rating lists, where all the players will know how to correctly read and pronounce the names.

My suggestion was to use a basic latin representation, as well as a "native alphabet" representation. A solution that allows absolutely everyone to have their name represented in a readable format for Europeans in general, but also in a correct format for domestic use. So Russians at a Russian tournament can print names in Cyrillic, Hungarians tournaments can print them in the Hungarian alphabet, etc.

tapir: Can you read a wrong written (in simplified latin letters) e.g. turkish name correctly - without knowledge of the language? I guess no. You may not read correctly if it is written with extended latin letters, as well. But at least this is a strange argument against the extension - the diacritic mark or additional letter may at least makes you aware of that. Even in the player by PIN age there may well be three modes: simplified latin, extended latin for correct names in latin alphabets, native mode for non-latin alphabets. simplified latin for latin alphabets has little relation with transliteration from languages using non-latin script, and to point to this difference is no offence to speakers of those languages. Otherwise I totally agree to flatline and herman, that it is wise to wait for the PIN-age :)

Zarlan: Well Herman... "How many can you pronounce correctly?" you ask? Can you pronounce the name... "Louis" correctly? Or "Aron"? There are more than one way of doing it, you know. How do you pronounce the letter v? Basic ASCII, yet you still don't know how to pronounce it. The problem isn't the ability to pronounce, but to read. How many can I read? All (more or less correctly). Well, my browser might not render all of the letters, but as I've already said, I seriously doubt that any of those exist in names. As to the rest... I fully agree with tapir.

Herman: Er, yes, exactly. The point I was making above is that neither basic latin nor extended latin really allow non-native speakers to pronounce the name correctly. You claim you can read all of them. But what do you mean by that? Obviously, you don't mean you can pronounce them, so what do you mean when you say you can "read" them?

As I have said, multiple times now, I am not arguing against the inclusion of extended latin. I am arguing against the exclusion of Cyrillic (and other alphabets). Why should a large part of the European go players not be allowed to have their name spelled correctly? What is wrong with having both a correct (native alphabet) spelling and a general use (basic latin) spelling? Sure, as tapir suggests, we can have it in three formats (basic latin, extended latin and native) if we want. We could even have the software try to automatically convert between such representations (through iconv and things like that), based on what usage is intended.

Flatline: Forgive me if I may be repetitive, but I'd like to better explain my point of view.

1) people who send tournaments data to EGD are many, with many different systems and skills; I want to make things as easy as possible for them, and at the same time I want to reduce the possibility of serious mistakes. Please consider that such people often are handling players coming from different countries, so - for instance - an italian organizer can have in his tournament players coming from Lithuania (such as Janavièiûtë Þivilë and Damoðiûtë Rûta), from Norway (such as Vestgården, Øystein), France (such as Seailles Jean-François) etc... Well, this guy has neither an adequate keyboard nor the necessary skills to handle correctly these names. So, he will have troubles (first problem) and the data he will send to EGD will suffer of likely errors (second problem). And it's not a good answer saying "go and ask the player himself", because sometimes this can be difficult.

2) EGD wants to be as easy-accessible as possible. So I say that yes, I'm also concerned about the fact that not every browser renders correctly extended charsets. I agree that this can be played around by storing two different formats (maybe three, as tapir suggests), so I think that this will be the way. Not a trivial one, by the way...

tapir: I guess additional name formats will be possible/convenient to handle only after the PIN-age started, anyway. P.S. Just to make sure, EGD is wonderful even in basic latin letters.

Flatline:

"I guess additional name formats will be possible/convenient to handle only after the PIN-age started,"
Sure, I meant that.
"P.S. Just to make sure, EGD is wonderful even in basic latin letters."
Well, I feel better! Thank you :-)

Zarlan: I don't quite feel like explaining how people can read a name like say Vlad Ţepeş (aka Dracula), despite not quite knowing how to pronounce it and as it's not really that important in affecting the EGD anyway... Also, I should perhaps clearly state that I understand and acknowledge Flatline's concerns now. Not the rendering issue, on which I am still unconvinced, but the rest is enough by itself. I hope that the PIN-age will come soon :)

Tapir: Imho the "reading argument" wasn't an argument at all whether I write Özge Işık or Ozge Isik only people knowing the language will pronounce it correctly, both can be read, but the first is even written correctly and helps by indicating that your pronouncation may not be correct. Damoðiûtë Rûta is a fine example, I would instantly ask before the game how to pronounce the name. The "writing argument" is much more convincing. Waiting for the PIN-age...

deft: I can only say that the situation for scandinavian players is very bad, as there is a big difference between A and Å, O and Ø and in fact they may be completely different names. We normally substitute aa for å but in fact we have people who have this substitution in their family name for historic reasons. I think these letters are present in all Latin codepages and I know for a fact they are supported by the MacMahon software so I don't see any good reason why the EGD doesn't support them.

mohsart: Having reported the Swedish results for some years, I don't know how many DAYS I've spent changing spaces to _ or - and å, ä, ö to aa, ae, oe... And if we by any chance would like to use the data in other circumstances, it is not really possible to change back to the real, original, spelling since for example one player spells his name with a "oe" in his name. I have had thoughts about a workaround to spell these three characters with capitals, but it is such a ugly thing to do. Except for a small quarrel with Ales about this a couple of years ago, the last time I saw anybody defending 7 bit ascii was in the mid 90-ies, when email programs started to be able to handle extended ascii/ansi relatively consistent. Oh and if you didn't get it, the åäö, as well as the Polish L with a dash over it, are unique characters, they are not variations of a, o, and l, as e.g. ä is in german. So 1. The 7 bit ascii convention is not used by most programs today, and the less we support the use of it, the more programs will start accepting modern (well) standards like iso 8859-1. 2. Disallowing e.g. åäö and spaces makes it A LOT more work to report tournament results, my guess is that it tripled the time needed for me. 3. Not allowing e.g. åäö and spaces makes the database more or less useless for other uses, e.g. for a club to list their members. 4. For clubs, exchanging åäö with two character transcriptions brings more confusion about which club the player belongs to. Not is only e.g. Karlskoga and Karlshamn hard to separate, but also Örebro and Öregrund.

Laman: i know this was already answered, but nevertheless, i would like to repeat how much more convenient would be the inclusion of native forms of names. with the Czech diacritics being simply stripped when converting to ASCII, one has to only guess real forms of some unusual surnames. i also sometimes post tournament results to a news site egoban.cz and if i want to write foreign names i don't know with the original spelling (which i believe everyone deserves), it often requires a non-trivial effort to find it out on the national association ranking list, if such exists at all by the way, what separates us from the awaited PIN-identification age?

chtz: Would it be possible to give every player the opportunity to provide a real name, in cases where the transcription differs? Afterwards, it might be possible to optionally either search for real names or EGF names (or automatically transcribe names with non-ASCII characters when searching, but still additionally show the real names in result lists). You might even allow non-latin alphabets to be used for real names.

epsilon parameter (answered)

Not really that important for the EGD, but I noticed the eta parameter seemed to be at 0.0016 recently, it used to be lower. Did I miss when this was changed? Maybe a record could be left here?

  • Flatline (does this question come from tapir...?) Actually it isn't strictly an EGD question, nevertheless you are right, a record should have been left. The epsilon parameter changed recently from 0.014 to 0.016 (not 0.0016), exactly when all the ratings have been recalculated before the startup of EGD as official repository, i.e. at the beginning of April 2009.
    • IanDavis No I asked it, I think it looks like a good idea to increase the eta parameter.
    • Flatline: I know :-) I've explained WHEN this change occurred.
    • geoff How did you decide on the value of eta - did you carry out simulations?
      • Flatline: It has been decided by Aleš Cieply. Yes, he carried out simulations (BTW: epsilon, NOT eta)
  • IanDavis The BGA website uses a secret interpolation formula to track the rating of an average shodan across Europe. For many years this had been slowly sinking lower and lower in value - from 2100 down to 2035. This year it seems to be climbing upwards and has now reached 2039. This is an interesting development, if it continues there may be scope for reducing the epsilon parameter to 0.015?

GoR vs. Rank Progression Chart (done)

Edu: Currently the chart shows tournaments on the x-axis equally spaced. Could you think of changing it so, that the x-axis would really represent time. In other words, if there are tournaments in the beginning of 2004, 2005, and 2008, the spacing between the last two would be three times the spacing between the first two. This would help interpretation of any single chart as well as comparison of several charts.

  • Flatline: You are right. It's already in my to-do list.
  • Flatline: Ok, I did it (Sep 5th 2009)
    • tapir: Cool!
    • Phelan: I second the "Cool!". However, the graphs now are missing the legend that they had, indicating which is GoR and which is Rank progression.
      • tapir: Isn't that obvious?
      • Flatline: anyways I've added it
    • Edu: Great! Thank you also for such a quick response.

Herman: Is it an idea to have the graph size at a fixed width per year, instead of a fixed width for the whole graph? As it is, the graph will crunch further and further together as years get added. Instead, perhaps a format that uses 1 pixel per week (so 52 per year) would work? Those longest in the database (1996-2009, almost 14 years) will currently have a graph about 700 pixels wide, which is quite acceptable for any display resolution. I think it would also stay acceptable for quite a long time (eg: after 20 year, in 2016, the width will be just over 1000 pixels, easily acceptable even on today's screens).

  • Flatline: I'm not convinced... The advantage with fixed-width graphs is that you can get as much precision as you can with your - let's say - 700 pixels. The fact that they tend to crunch is anyway unavoidable, unless you plot graphs that exceed the normal screen width. The only real advantage I see in your proposal, is that it would make easier comparisons. But I'm already working on this, since I want to make a side-by-side graph comparison tool.

Pictures and .sgf policy (answered)

tapir: What is the policy regarding pictures and .sgf-files? Should not pictures be uploaded only with approval of the person showed? And what happens with kifus... if someone prefers not to have a game uploaded, but the opponent did?

  • Flatline: All pictures are uploaded only after a written request or permission by the person showed, or by his/her parent(s) if he/she is underage. Regarding sgf: once you participate in a tournament your games are public, and you can hardly claim they are not: they are under any perspective public sport events.
    • tapir: Admittedly, there are games I prefer to forget instead of having them downloadable for future generations.

tapir: Once more concerning .sgf's. What if a .sgf uploaded by one player contains mistakes? (Not only the mistakes made by the unhappy opponent who don't want to see it online, but recording mistakes.)

  • Flatline: Not a serious issue, anyway :-) It must be fixed, of course, or removed. What if the two players don't agree...? Well, never happened so far, in case I'll remove it.

eko410: What about to combine the .sgf files and game pictures? It would be great if we can upload a photo taken during a game like uploading the .sgf file of that game (the photo may show two opponents or the go board during the game).

Ranks 21-30k (answered)

sh: In some countries (e.g. Germany, Netherlands, Belgium) it is common practice to allow kyu ranks in the range from 1k to 30k. The EGD database however only allows kyu ranks from 1k to 20k. I think there are several arguments in favor of expanding the valid range to 30k:

1) It is more beginner-friendly. Especially for children who play casually on tournaments, because their daddy or mommy or elder brother/sister attends the tournament. When I started to play on tournaments (after having played on KGS and having studied the game intensely for four months) I was 20k, and I noticed that there was a huge difference to the 30k players. So some of these kids who are nominally 20k but actually 30k would get creamed by someone whose playing strength is really 20k. This would not be very motivating and possibly even scaring off newbies to attend tournaments.

2) Sometimes the pairings of tournaments are created based on these ratings (opposed to those based on self assessment which is actually the majority of tournaments in Germany). They claim to make the pairings so, that players of equal strength play each other, hence the (very useful) method according to McMahon is applied. However with the narrow range this claim would really go astray in the ddk ranks.

3) A 30k player can actually reach a rating of 400 if he beats other 30k's in a tournament (one of my daughters is an example for that). This means that all the ranking tables below a rating of 400 are completely meaningless and it would leave only 16 relevant kyu ranks (which has also an influence on pt. 2)

4) One thing that makes go unique is that it has such a huge broadness of difference in playing strength. It is said that there are 40 ranks from beginner to professional, if a difference of one rank is supposed to be a 2/3 vs. 1/3 win probability. In other games there much fewer ranks, even in chess and chess like games the number of ranks does not exceed 20. So if you subtract the maximally 10 dan ranks it would leave 30 ranks for kyu players. So here we are.

I wonder why the EGD opted to allow only 20 kyu ranks when it was created.

Herman: Agree. Actually, I think there should be no bottom at all. The AGA rating system seems to function just fine without a bottom. The effect that sh mentions in point 3 for ratings under 400 can be very easily seen in this graph: [ext] http://upload.wikimedia.org/wikipedia/commons/7/77/Distribution_of_EGF_ratings_over_Ranks.png

Dieter: Just another opinion (oh, how fun is it to flood the web with one's opinions): I cannot distinguish between 22k or 17k. When I have to assess a newcomer at the club, by the time I can, they have already progressed up to 15k. I think 15k is the real starting point of a meaningful rank. So, absolute beginners will always get a rank of 25k, which means "default beginner rank, soon to progress to a meaningful rank". The ranks between 25k and 15k are just there to give some consistency to the ranking system. From that point of view, a 30k must be someone who doesn't know the rules or doesn't see any atari: indeed, such condition gives little potential for progress.

tapir: In my opinion one should start fetishizing rank as late as possible, better never. Considering yourself as a "my strength is 27k, i have nearly no chance against this 22k" holds you back. Kalli Balduin lets people (children) start at 50k, adding one rank per win (never subtracting) til they reach meaningful ranks to give some feeling of progress. That is not relevant to EGD though.

sh: It seems reasonable that a 2d player cannot distinguish between a 17k and a 22k. To him both players are incredibly weak. However when I was 17k, I had a tough game with a 23k on a tournament, giving him three stones. So the rank difference at these stages do make sense in my point of view, even up to 30k. Being 30k is a little bit more than just knowing the rules. It includes knowing about some very basic concepts as shown (and trained) on [ext] playgo.to. Rank is not an end in itself, it just serves to roughly indicate one's playing strength and create interesting matches on tournaments.

tapir: The main argument wasn't handicap is of no use for beginners (sure it is and it should be used - and is used - in play but reported as 20k) but it changes too fast for a rating system based on tournaments (at most one a month often less) to cope with. Rank adjustment by 2 stones between the tournaments -> reset of rating may well be the rule there.

Flatline: Just for answering sh who asked: "I wonder why the EGD opted to allow only 20 kyu ranks when it was created.": EGD was created this way for the simple reason that this was (and is) the provision stated by the EGF rating system. Having said this, I think it works fine. Tournament directors are of course free to use ranks below 20k, and to compute handicap basing upon these ranks. But these results - for the reasons explained by tapir - are not relevant to the rating system.

Herman: I think that the largest problem with the current system is the fact that many ranks stronger than 20 kyu are also affected. If, for example, a 13 kyu defeats a 25 kyu with a 9 stone handicap, then under the current system this is considered equivalent to him winning an even game against an 11 kyu. This is because the system silently upgrades the 25 kyu to 20 kyu (rating 100, because it doesn't go any lower), but does not adjust the handicap. The player will receive some 60 rating points for this match, while realistically it should only be worth 10 or so.

Dieter: I can understand the existence of a 25k rank. A 30k would lose with nine stones to a 21, who's someone who barely understands the most basic concepts. One cannot forbid such people to play 19x19, neither in tournament conditions, but I wouldn't encourage it either by encapsulating it in a rating system.

Herman: I agree that there is probably little point in trying to calculate ratings for players under 20 kyu, because such players usually improve so rapidly that their rating is unlikely to ever be accurate. I do think that it is bothersome that such players do influence the ratings of other players though. How about a solution where any player weaker than 20 kyu is put in the database at their reported rank, with a rating of zero (so they will be sorted below all 20 kyu's for purpose of generating lists), and their game are ignored for other players ratings.

Question about Very Large Handicaps (answered)

Ian? I was looking at this event, [ext] http://www.europeangodatabase.eu/EGD/Tournament_ShowGoR.php?key=T090831B My understanding was that games using handicaps greater than 9 stones were not entered into the rating system. I see from this event that they are.

  • Flatline My fault. Actually games with handicaps greater than 9 stones have never been considered by the rating system. Now I've made the necessary corrections: EGD can accept them and can show them in the tournaments tables, but it doesn't consider them for the GoR recalculation. Sorry for the inconvenience.

AGA - GoR comparison (answered + obsolete)

tapir: agagd and egd using the same technics may be an opportunity to approach the RankWorldwideComparison statistically at least between aga - euro-ranks. is something like this planned?

tapir: With the AGA-EGD link in place right now... is there any possibility to see an output of AGA-EGD rating relations soon? Basically all is in place, one just needs to extract this data.

  • Flatline: Yes, basically... I haven't had a thorough look at the timeline of the double-hosted players yet, but I guess that very often they are people who have moved from Europe to US or vice-versa, so their data in the two databases come from different periods of their lives, making rating comparison unreliable. Nevertheless, maybe that some sort of comparison is possible.
  • Velobici: Yes, hoping that both Flatline and I get some free time at the same time that we might work on this together.
    • tapir: There is no AGAGD anymore.

Anonymity, data security, feasibility (answered)

Tapir: I read on a german go blog (Makko's Go Café) and the DGoB-Forum about some players wishing to be anonymous (in tournament play) and ongoing discussions between EGD and EGF and DGoB how to handle this. While I don't endorse this (tournaments are public, finally - though I dislike the excessive photographing at tournaments), I would be interested to read something about the current situation.

Herman: In my opinion, a go tournament is a public venue. If you do not want your name published, don't visit the tournament or register under a false name. You simply cannot run a tournament without publishing pairings and results. I do think we can expect tournament organizers to respect privacy insofar as to not publish personal details like email address, date of birth, or similar personal information, but I do not think that that privacy protection extends to the name of a player.

  • tapir: I share this opinion. However, there is an ongoing discussion already. (I asked before about game records, which are sent with all errors to the EGD by some players. And the shame attached to have all those silly defeats safed for eternity, but this is another issue.)

Flatline: I've tried to read the blogs, even if I had to rely upon Google for the translation, since I cannot read German. Anyway in the reported case EGD didn't accept the tournament results, so the player agreed to move back to his real name. This must be regarded as a standard policy: nicknames are not allowed, for all the reasons already pointed out in the blogs as well as here.

  • tapir: Thanks. If I am bored these days I can translate the blog entry. All what I know about it is from "Makko", I guess you stay in touch in EGD matters anyway.
    • Flatline: Yes, we are always in touch. Thank you for your promise to make a translation, but I have read easily enough Makko's Cafe, my problem is the DGob forum, where I've seen so many posts about the privacy issue, that I cannot ask you to translate all of them :-)
      • tapir: Indeed. That is way too much :)

Club graphing wrinkle (done)

PeterHB: Looking at this couple of examples:
[ext] http://www.europeangodatabase.eu/EGD/Stats_Country.php?ricerca=1&country_code=UK&club=Read
[ext] http://www.europeangodatabase.eu/EGD/Stats_Country.php?ricerca=1&country_code=UK&club=Purb
There is a 'JpGraph Error'. This appears to be caused by trying to create a graph from a single data point. I wonder if this special case might be intercepted, and a less obtrusive message displayed. Just a minor suggestion.

  • Flatline: You're right. I've removed the graph when there is a single point to be plotted.

Update the EGF logo

Since the European Go Federation has a new logo, I would like to request that the EGD updates their page to use that new logo.

  • It was so

Online Tournaments

Have you ever tought about giving rating for some online tournaments? The Fujitsu Preliminarys will be held on KGS this year... Maybe there would be more online tournaments for European players if they would be eligible for rating.

isd:The EGF doesn't accept ratings taken from online games. I don't see them changing their mind.

I know they didnt until now. But I think that would popularise playing of go. It would be good if they would maybe organise a tournament on some server once per month(or per two months, or every two weeks or whatever). Some players that are active but cannot attend tournaments would be quite satisfied.

isd: Wow, I just saw that the [ext] Fujitsu preliminarys were actually submitted. Maybe this is just a special case though?

I really hope they will start to accept online tournaments. As soon as they say they are accepting them, I will organise one.

Flatline: the Fujitsu preliminary has been a very special case. We are discussing within the ratings committee in order to settle rules for accepting on-line games in general. I guess that at the end they will be rather strict.

Well, we are waiting your decision than :)

Anything?

tapir: It seems kind of clear (to me) that in the end only special online events will count for this purpose. But how about e.g. the German Bundesliga. Played online regularly, but by people with identifiable EGF rating, appropriate time limits etc.

Lovro Furjanic - They will talk about it on AGM.

isd: From my understanding now, a very few limited events will be accepted.

Advanced tournament tables

It would be nice if the tournament table was presented as an HTML table, rather than as a simple text file in a box (the admin back end already has a function something like it). This table could then use some advanced styling and function. The German Association already has something like that on their own site. For example: [ext] http://www.dgob.de/tourn/tourn.cgi?f=07debbcp.txt&mode=cml

Some nice things that could be done:

  • Show a win as green, a loss as red, a jigo as yellow and an unplayed round as blue/grey.
  • Clicking on a result cell shows a popup with extra info (colors, handicap, result).
  • Clicking on a player shows a popup with list of opponents and results (already present, but not as a popup, now the page reloads when you select a different player).
  • Sorting by other columns (to show, eg, people with 4 points, or from the same club).

Flatline: Yes, it would be nice. When the tournament card was originally designed, it was intended in a very player-centric perspective. It occurs often to me to think that I should change it soon or later...


European Go Database / Wishlist Old last edited by 176.158.31.237 on October 20, 2020 - 10:08
RecentChanges · StartingPoints · About
Edit page ·Search · Related · Page info · Latest diff
[Welcome to Sensei's Library!]
RecentChanges
StartingPoints
About
RandomPage
Search position
Page history
Latest page diff
Partner sites:
Go Teaching Ladder
Goproblems.com
Login / Prefs
Tools
Sensei's Library