@NoseKnowsAll Very interesting results!
If understand correctly the app that you are working on is this:
https://dojoratingbandconverter.netlify.app/
So it takes Lichess account info, chess.com account info, and UCSF ID as inputs.
Have you considered passing more explanatory variables to the model? For example:
Lichess blitz
Lichess rapid
Lichess classical
chess.com blitz
chess.com rapid
uscf rating
and fide rating is the target variable.
I think this might be help since many players especially stronger ones don't have classical rating (on lichess), and some people might have it but the rating might be outdated. And since for chess.com there is not classical anyway and you have to use rapid, maybe taking lichess rapid rating into account would make sense.
Adding more explanatory variables would make the model more complex, and it looks like there is not a ton of training data, so there could be overfitting concerns, but I still wanted to share the idea.
@NoseKnowsAll Very interesting results!
If understand correctly the app that you are working on is this:
https://dojoratingbandconverter.netlify.app/
So it takes Lichess account info, chess.com account info, and UCSF ID as inputs.
Have you considered passing more explanatory variables to the model? For example:
Lichess blitz
Lichess rapid
Lichess classical
chess.com blitz
chess.com rapid
uscf rating
and fide rating is the target variable.
I think this might be help since many players especially stronger ones don't have classical rating (on lichess), and some people might have it but the rating might be outdated. And since for chess.com there is not classical anyway and you have to use rapid, maybe taking lichess rapid rating into account would make sense.
Adding more explanatory variables would make the model more complex, and it looks like there is not a ton of training data, so there could be overfitting concerns, but I still wanted to share the idea.