Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Categorical variables: queens on the board (and bishops of the color of f7) #6

Open
YodaEmbedding opened this issue Aug 30, 2020 · 1 comment

Comments

@YodaEmbedding
Copy link

YodaEmbedding commented Aug 30, 2020

I believe the greatest influencers towards playing f3/f6 are:

  • Presence of queens
  • Presence of queens
  • No really, the presence of queens
  • Bishops of the same color as the f7 pawn

So there are three binary categorical variables to check for:

  • presence of enemy queen
  • presence of enemy f7-colored bishop
  • presence of allied f7-colored bishop

I think the idea of "never play f6" only really applied to middle game positions with these factors present. Once these factors are removed, I'll bet that rating doesn't influence whether or not f6 should be played. Can this repository demonstrate that? And establish a good solid guideline towards the playing of f6? :)

My guess for the rating discrepancy that you're currently observing is that high-rated players that play f6 usually only do once these important attackers are gone.

@gjgd
Copy link
Owner

gjgd commented Aug 30, 2020

Yes that's a good point, I agree that in general the advice "never play f6" applies the most in the middlegame, so ideally we would want to:

  • remove the games where f3/f6 are played as part of an opening that is within theory
  • remove the games where f3/f6 are played in an endgame.

The second point is harder because, how do you define an endgame ? Queens are certainly a good indicator, but sometimes they are traded early and you have a queen-less middlegame and sometimes they are still there in the endgame.
My idea was to remove the games where f3/f6 are played after a certain move (for example move 20), but this method also has its fault. Let me know what you think!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants