Will it take much if Chessnut changes from using numerical fields to using ‘char’ fields? What is the next step in formatting called? The old formatting is called 2C format. Do you know if Chessnut will be changing to a new format?
We’re not updating the format number just correcting an inconsistency in it. The format said to use numeric but the example given was clearly formatted like a char.
I don’t think I’ve checked any files from Chessnut to know if they’re using char fields or numeric ones. The files that led us to find the inconsistency came from a different source.
I do not know what Chessnut may do or when.
There is definitely a log on the current system of which program/format was used for uploaded events, but all it can do is report what was in the data format and program name fields. The original format did not have those fields.
I do not know if Leago is keeping track of that information or saving uploaded files. We currently keep the 3 uploaded files for a few weeks just in case we need to see what was actually uploaded. (This was how we were able to give Leago several hundred sets of upload files to test.)
Here’s a summary of upload file usage since 1/1/2023:
program version events affils
CAISSA 2C 2346 96
CHESS NUT 2C 291 31
CHESSMNGR 2C 200 23
CHESSPAIRINGS 2C 6 1
EASYPAIR 2C 10 2
SHRTCSTLE 2C 62 3
SSCH.1.0 2C 19 4
SWISSSYS 2C 1895 77
SWISSSYS10 2C 10044 279
SWISSSYS11 2C 13854 568
TOM2194 2C 205 1
TOM2197 2C 24 1
TOM2201 2C 112 1
WINTD4.10 2C 44 5
WINTD4.11 2C 110 5
WINTD4.20 2C 1506 105
WINTD5.00 2C 4298 258
-N- 2C 20 1
-N- CHESS.COM-1.0 1392 1
-N- Upl-V1 1840 88
(20 rows)
Didn’t Ken send you some Chess Nut files? You guys were talking about some issues that seemed to not be parser related. Was there any problem with those files? @KenFarrar besides that Unexpected Server Error have you run into issues uploading Chess Nut files to the new system?
This is Ken. I reissued them a 2nd time without the VPN being on, I guess. I was able to load them in the reissue and validate them. I didn’t need to send the files to MNolan.
I ran into no other errors.
Of course the affiliate I use expired at the end of August and I picked a few players that also had expired before September – so it tested a few things I was not planning on testing.
So I back off the date of tournament to 8/31 then all is well expect it becomes too old to rate without review (another bonus test)
I laughed as I spent over 30 years working on helping to maintain a test data version of HR data - and these date scenarios are all quite familiar - but being just a tester limits the work-arounds.
1 Like
I’m getting an error trying to access the beta system this morning:
**Error:**Error creating WebGL context.
I’ve alerted Leago.
It seems to be back up.
Jr.s seem to be confusing it though, along with anything more complicated than “Last, First”.
Same issue that the Chief TD can’t be the Organizer of a FIDE rated section.
Actually, the Organizer can’t overlap with any other role, it looks like.
Still failing here in firefox but works with Edge and Chrome.
that type of error is usually related to rendering 3d elements (especially in unsupported browsers) like those useless floating chess pieces
Seems like it was written using WebGL2 which older hardware doesn’t support. They probably are trying to fix it and then broke it for folks with newer hardware, too. Apparently, it is not as simple as falling back to WebGL1 since what they are doing may not be available w/o different code branches.
Yes - just get rid of the dancing pieces.
Or at least check for compatibility before trying to do them.
I don’t know if WebGL2 is being used for anything else in the Leago structure, I think I’ll ask about that in today’s tag-up call.
This would be great.
Leago is putting in code check for WebGL2 compatibility before displaying the dancing chess pieces.
1 Like
Why not just remove them? They genuinely make the site worse. It is the modern day equivalent of the 90s flame gifs. Am I alone on this ?
They could delete these, make the site better instantly, and spend the time they were going to spend making these compatible on functionality that matters
1 Like
Could the white King and black Queen be static? They could be still pics with the white King on the left side and the black Queen on the right side. The proper distances from the center would need to be determined. They could each be an equadistance apart from the center point.
1 Like
I got to a situation where I can no longer submit a tournament. Here is a quick review I sent to ratings-support about the new Leago tournament submission.
I did another test tournament submission on the new Leago system. These are some outstanding issues.
Directors page:
I'm unable to select anyone for the Default Organizer box. The search works, but no member is placed in the box once selected.
Suggestion: Show the TD certification level in the director search list and after the director is selected and placed on the form.
Section details:
Grand Prix is enabled by default. This should probably start off disabled as most events/sections are not Grand Prix.
Validation:
It initially reported that G/3;+2 is an invalid time control. In the section details, I changed it to G/90;+30. It then seemed to accept it. I then went back to G/3;+2, and the validation no longer reported it was an error.
I selected one member from the section as a house player. In the validation it shows "1 restricted values found", but no mention of what the issue is. I'm presuming it's because of the house player.
Speaking of house players, it looks like this now requires manual review by the staff. Is this a desired change, or should it still be automatic like in the past?
I then canceled the review request, and removed the house player, so that it was now a proper non-expired member. However, the validation still shows it having "1 restricted values found" even though the restriction has been removed. Clicking on "Re-validate" does not remove the restriction.
At this point it is no longer possible to submit the event.
I did a check and there were automatic approval of house players in 198 events in the first 9 months of 2025. That’s about 5 a week.
I don’t think that’s a show-stopper number, but we will probably want to have a more automated way of handling house players in the first round of enhancements to the new system. (I think that’s consistent with how we did that in 2005 as well.) It may not be a bad idea to have staff be a bit more aware of how many house player requests are being made.
The default organizer one may be a limitation on who can be an organizer but I’ve flagged it anyway. This field was only intended to be used in FIDE rated events to indicate the FIDE-certified organizer, but I think people have been using this field for non-FIDE events.
The G/3;+2 issue has already been reported, I don’t know where it is in the correction process.
I’ve entered dozens of events and none of them came up with Grand Prix set, I asked Kevin if the upload file had that flag set in it. (There is a field for that in the 2C upload file, but I don’t recall if the current system pays any attention to it.)
I”ve put in a request to display the TD’s certification level, I don’t know if that will be a high enough priority issue to be addressed prior to cutoff. Right now I”m more concerned with not showing the player’s pre-event published rating, sometimes that’s the only way to tell two players with similar names apart, since we cannot show things like an address or birthdate for privacy reasons.
When recording an extra rated games section of 3 or 4 games, do you call the TD who plays each of the extra rated games a House Player for the submitted Leago tournament?