https://www.chess.com/events/2023-c...

Airthings Masters (2023)

Hey <MissScarlett>, chess24 and other sites have the <Airthings Masters> rounds 1-9, matches and Armageddon games all together. Then they have divisions 1-3 wins and losses seperate.

I was thinking of keeping it as is and putting the divisions 1-3 wins in one TID and division 1-3 losses in another. Sort of how the other sites have it.

In the link (below) you will see that chess24 has rounds 1-9, matches and Armageddon games all together and divisions 1-3 seperate. Any suggestions before uploading the divisions 1 - 3 wins and losses.

https://chess24.com/en/watch/live-t...

***

Looking at past tournaments here on <CG> it was all put together and we just wrote out the standings in the tournament bio section. Below is an example on how FIDE Grand Prix Belgrade was done.

By the qualifying Swiss, I meant to include the matches and Armageddon.

<I was thinking of keeping it as is and putting the divisions 1-3 wins in one TID and division 1-3 losses in another.>

You will see that 365chess, Chessbase, TWIC, and others follow this convention.

How this maps into <CG> structures, e.g. tid's, never has been properly worked out, afaic.

So Div 1 winners in one TID AND Div 1 Losers in another TID. Same with Div 2 and Div 3, Winners and losers in different TID.

I saw thats how TWIC and chess24 are doing it.

But then <Miss> suggested one way and <steve> said to look how we've done it in the past and showed me:

FIDE Grand Prix Belgrade (2022)
Where Pool A, B, C and D are all together.

55th Biel GM (2022)
Classical, Rapid and Blitz games are all together.

Fall Chess Classic (2022)
Pool A and B together

****

* * * * *

<MIssy> doesn't really understand PGN, at least the way the rest of the world is using it. And the "<CG> way" was really established without the full appreciation of all the subtleties mentioned below, or what the incompatibility with the rest of the world really means.

Especially in regards to the the importance of using xtabs to cross-check for errors, correctness, consistency, and completeness(*).

I don't mind if you "de-normalize" the <CG> PGN headers for a given tid (though it would make me a little sad).... which is to say put all the tournament games on the same page, but with different (Event / Site / Eventdate) tag headers for the difference segments of play (e.g. knockout groups (A->Z), round robin elimination, final, main tiebreak, secondary tiebreaks, etc.).

I don't expect <CG> to follow this sage advice presently - given that they haven't in the past. But since you're just starting out in this business, I thought I'd offer you some explanation and rational as to why the rest of the world is doing what they do.

Which is to say, doing it "right".

My old adage is as follows:

"<CG> can be better than the rest, but first it has to be at least as good".

In this case, one number for a tournament isn't enough. There needs to be another id for the different phrases of the tournament (which can include nullified games, a category not mentioned above).

Really, the two id system would be analogous to one id acting as the tournament book, and the other for the different phases of play within the tournament.

Of course, things like the Grand Prix introduce the need for a meta-id, but let's save that discussion for another day.

Anyways, congrats if you've made it this far.

* * * * *

(*) In the old days when I was a very active contributor, I was pretty much alone in checking the status of many historical games. I found lots and lots of errors, like dropped games, denormalized headers, etc, from TI tournaments by using xtabs.

I agree, eventually we would like to display why the 403 occurred.
If it's when trying to post a comment or make an edit, the culprit is most likely a false positive for SQL injections(e.g <So--Abdusattorov>). I believe we would need to create and manage a "regex pattern set"(https://docs.aws.amazon.com/waf/lat...) for our firewall to permit these false positives. I'll be looking into it, it's a learning curve.

<<ERROR: Our dedicated chess analysis server is currently overworked. Please try your request again in a few minutes.> These messages are coming constantly. :( Please buy this: https://www.theserverstore.com/Dell... with 4x Xeon Platinum 8180 and 3T memory. OK it starts at $28,536.00, but that's not that bad.>
We can only use servers/instances provided by AWS (https://aws.amazon.com/ec2/instance...). Our server is plenty for the majority of the day but it does hit it's max in the peak hours. This will no longer be an issue when we implement the analysis queue.

Why? The winner of the losers gets to play the winner of the winners in the Division 1 grand final, so it's all the same event.

The site probably needs to be hardened against XSS and SQL injection attacks. Oftentimes these attacks are conducted on forms (where you must submit information) whose software is in need of an update.> chessgames.com chessforum