I think you’re probably right that nobody’s running FIDE events at G/60 through G/65, I just wanted to clarify that so Leago knows to skip computing a fee for all dual-rated FIDE events. (The issue with 3rd party developers is that they tend to do what you tell them to do, not what you need them to do, so we need to make sure our instructions to them are correct.)
I’m not sure what the difference is, I’ll try to ask this at tomorrow’s Leago call, this isn’t a serious enough question to go into the issues tracking system IMHO.
The WEBGL code has been updated again, please see if it solves the problem or creates new one. (Murpy’s law)
The survey form for TDs has been changed to allow multiple submissions, and I think there will be a file upload feature added to it soon.
The two state messages have different purposes.
One of them says that there’s a difference between what is in the state field in the upload file and what is in the member record. The other one says there’s a difference between the state of the member and the state of the tournament. I’ve suggested that the validation message complaining about issues would be more helpful if they actually said what the data is that it’s complaining about so TDs don’t have to go look it up somewhere else. They would probably have to go to that other page to correct errors, but if they can see something on the validation issues list that says something like “Player in Iowa, Event in Nebraska” they might think ‘OK, that’s not a problem”. But if they see a ‘Player upload says member in New Jersey, Member record says Alabama”, that might be a problem.
Similarly, if it says “Upload Name is Bob Jones, file name is Rob Jones”, that might also produce a quick “That’s OK.”
I’m assuming the name and state data in the upload file probably came from a supplement file, so it could be 30-45 days out of date.
1 Like
This doesn’t track what I’m seeing.
Alert:
TDEXPORT.DBF:
MSA:
I checked a player file I had for Oren from 2023 and it had CA as the state then too…
EDIT: It’s possible Leago doesn’t understand that CA-N and CA-S are both CA in certain contexts?
Yeah, it does appear to be a CA vs CA-S issue. I’ve started a support ticket for this.
For address matching purposes, they need to use CA, for ranking purposes, CA-S and CA-N have separate ranking lists.
I always though USCF did this out of self preservation – especially at the small local level where half the people would not have become USCF members if they weren’t forced to to play. but I do not see the downside to partially submitting to FIDE.
I am still not 100% clear on FIDE sections.
if I am doing a G/90 and a 2400+ unexpectedly shows up that just mean his games can’t be fide rated - the rest are submitted (that seems the most reasonable)
PS.
One time I noticed a a tournament that had rated and not-rated sections with some of rated players participating in both sections (with quite a few byes in the rated sections). Technically legal?
All seems ok now.
I did try to go to a lot of different pages/functions so it seems like the WebGL2 was probably limited to the rotating pieces.
Yes, this is exactly how it works. As a concrete recent example, Hikaru Nakamura’s round 1 game in the Louisiana State Championship could not be rated as round 1 for that event was G/60;i30 (the remaining 6 games were G/90;i30 and were accordingly rated).
1 Like
Maybe, it’s hard to discern intent from crosstables, but it does sound a bit iffy.
Are a players rating floors (at least for the otb regular rating) going to be shown anywhere on their new rating page?
That’s on the task list.
2 Likes
I figured here was as good a place as any… Is this an issue with Leago, or an issue with it being in Beta (and data not being current)? I figured the latter, but since it’s saying I “expired in the future” and my expiration is even further past that (that it thinks)… it was kinda odd.
I need the event name or the ID to look at your event to check, but this may be a Leago issue.
ID is 20251018hzzku3.
I’m not seeing that error now, sometimes it takes a validation to clear errors.
Keep in mind the beta system is for practice only, until we go live this is not where real events are submitted yet.
The error didn’t preclude submission, but did show the yellow “alert” after validation and during submission. And I know - that’s why I’m using my old tournaments as tests. 
The only alert I’m seeing now is an expired member, which is a stale database issue, not the TD issue, so I’m not sure there’s anything to create a ticket on.
Are rating floors going to show for each of the six ratings or just the OTB regular rating like is currently done? Some people have gotten confused and thought there were no floors for the other five rating systems because they aren’t shown on a players MSA page.
I think they’re going to show all the ratings floors. I think there will another refresh of the beta ratings database later this week to test some fixes to the data transfer process. (We’ve got 20+ years of data to clean up.)
1 Like
For players who haven’t reached 1400 and thus don’t have a peak rating floor, it appears it’s always listing their floor as 100 but shouldn’t it be somewhere between 100-150 due to how the minimum floor works?