The axes being different for the graphs for different openings caught me off guard. given the purpose of this research is to compare openings, I think it would be helpful to show this data all on the same graph. I'd suggest a dashed line for the expected elo gain/100 games, and a solid line for actual, which allows colour to be used for opening. and the axes being the same makes the comparison easier.
Alternatively, a practically more simple (and arguably more understandable) method is to make all of the axes have the same scale and values. The drawback with this method is it requires more manual excel tinkering (though less difficult I mean to say).
This is very interesting nonetheless, it would be good to see more openings shown as others mentioned. I think it would also be useful to include sample size for each of the graphs, to get an idea of scope and reliability.
@vikhyat0310 said in #17:
> It would be great if you could derive conclusions from this too. Various conclusions others than the most obvious ones.
I'm starting to see some patterns, but I's rather stabilize the tool first and hopefully get better chess players than me look at it too
@Fischer_and_Chips88 said in #21:
> The axes being different for the graphs for different openings caught me off guard. given the purpose of this research is to compare openings, I think it would be helpful to show this data all on the same graph. I'd suggest a dashed line for the expected elo gain/100 games, and a solid line for actual, which allows colour to be used for opening. and the axes being the same makes the comparison easier.
>
> Alternatively, a practically more simple (and arguably more understandable) method is to make all of the axes have the same scale and values. The drawback with this method is it requires more manual excel tinkering (though less difficult I mean to say).
>
> This is very interesting nonetheless, it would be good to see more openings shown as others mentioned. I think it would also be useful to include sample size for each of the graphs, to get an idea of scope and reliability.
Yesterday I improved the charts. Now I generate 1 chart per metric/idea. What do you think?
https://github.com/RemiFabre/WickedLines?tab=readme-ov-file#wickedlines--chess-opening-reachability--value-explorer
@LKama said in #11:
> You can follow the instructions in the README here: github.com/RemiFabre/WickedLines?tab=readme-ov-file#installation
>
> That should walk you through installation and usage.
>
> If you've never clone a repository or ran a command line program, this might sound a bit technical, but nowadays you can ask an LLM (like chatGPT) to guide you on how to achieve this. Once you install it, running it becomes very easy.
>
> If you do, please make a Pull Request with the reports that your "Hunts" will automatically generate
Your response is not helpful. Your guide asks the user to install python and know how to use it. It also assumes people know how to use Chat GBT to figure this out. I can say that I cannot do either. Please provide with an installer and UI.
lost at this point...
Install the required libraries (including the new scipy dependency):
pip install requests python-chess tabulate scipy
@MisterCereal said in #25:
> lost at this point...
>
> Install the required libraries (including the new scipy dependency):
> pip install requests python-chess tabulate scipy
Running the program with little computer science knowledge is difficult, I'll try to make something more user friendly.
In the meantime the only realistic path I see for you to get the this thing working is using chatGPT as a guide.
https://chatgpt.com/
Give it the link of my repo and ask for a step by step guide on how to get it to work. Give it info on your operating system (e.g. Windows) and your level of IT knowledge. You'll have to do some back and forth but it should be possible.
@MisterCereal said in #24:
> Your response is not helpful. Your guide asks the user to install python and know how to use it. It also assumes people know how to use Chat GBT to figure this out. I can say that I cannot do either. Please provide with an installer and UI.
Please remember that people releasing Open Source software (usually) do it for free and in their own spare time. Of course they usually want other people to use their creation, but their time and energy is limited. Making Open Source developers work as a free support for everyone is a quick way for burnout. I fear that if you want to use a niche software from Github you'll have to develop some IT skills yourself.
I'm not saying this to criticize you (politely requesting features or documentation is reasonable), I'm just saying that we should be grateful for @LKama for sharing this with the community and let him work on features for now.
I provided an example configuration with my pull request:
https://github.com/RemiFabre/WickedLines/pull/6
@Toadofsky said in #28:
> I provided an example configuration with my pull request:
> github.com/RemiFabre/WickedLines/pull/6
Very appreciated!
whats the middle finger doing on the graphic