When are re-ratings run?
Thank you!
I was looking at the note on the section after a correction was submitted.
Note: corrections have been made to this section.
Any impact these corrections may have upon the ratings from this section will not show up until after the next rerate of this section.
Sometimes a rerate can take longer than a day. Last week’s rerate finished on Wednesday, for example.
Also on the week that includes the 3rd Wednesday of the month, we do a full rerate, starting on Monday and usually finishing on Wednesday, ahead of the creation of the next rating list. This week is such a week.
Whether that schedule will continue once we move to Leago is unclear. The main reason we scheduled rerates on Tuesday 20 years ago is that Tuesday is the low point in the week for submitting new events.
It’s interesting how much about Leago is still unclear at this late stage. Here’s hoping for the fog to lift
Eh. There’s no reason to present everything, but you can see some of the detail interestingly from the Rating Committee’s reports where they are working to make sure the rating algorithms (historical and current) are correct in Leago.
1 Like
Some things may be unclear TO ME, because I’m not the project leader, so there are issues on which I have no involvement, like how Leago is coordinating membership updates with the CIVI-CRM system that currently runs on a Linode server somewhere in PA, I think. The current methods for updating membership information on the ratings server (on the Postgres server) and the MSA system (on a MySQL server) could be improved upon, as the periodic posts about membership synchronization issues demonstrate.
Others may depend on policy issues, like scheduling rerates and supplements, and may also depend upon things like the speed of the Leago production system. Currently it takes about 35 hours to do a full rerate ahead of a supplement run, which takes another 6-8 hours. With time off for overnight tasks (backups and daily reports) that means we start the monthly rerate on Monday morning and it usually doesn’t finish until Wednesday evening while the new supplement files aren’t ready until some time on Thursday, hopefully by mid-morning. Leago thinks the new system will be faster, but they won’t know for sure until they get a full production system staged and can perform a full rerate.
And this is one of the more complex system conversions I’ve been involved in, and there are always loose ends that take a while to get figured out. I know when I converted a book publisher from a COBOL-based system to one based on Oracle, the changeover week was full of 20 hour days for me and we were rewriting reports for months afterwards. US Chess is moving from a Postgres RDBMS (with MySQL for the MSA system) to Azure and I don’t know what tool they’re developing programming in, but it isn’t PHP.
My main concerns are that the tournament entry/upload, validation and submission process not complicate life for TDs and that the ratings system basically produce the same ratings as the current system. MSA is probably going to look a LOT different, though it should have essentially the same information as before, and probably some new things.