The work on xboard.cpp is still ongoing, but I've updated my already converted files to the LIME 66 version (was LIME 62).
https://github.com/shinkarom/delimiterc ... a261e7271d
Delimiter development diary
Moderators: hgm, Rebel, chrisw
-
- Posts: 92
- Joined: Tue Nov 19, 2019 1:26 pm
- Full name: Roman Shynkarenko
-
- Posts: 92
- Joined: Tue Nov 19, 2019 1:26 pm
- Full name: Roman Shynkarenko
Re: Delimiter development diary
Converted xboard.cpp.
I selected xboard to convert because I use UCI, and therefore, should start with what I don't like first, to leave the easier parts for later.
https://github.com/shinkarom/delimiterc ... 892693cdc9
I selected xboard to convert because I use UCI, and therefore, should start with what I don't like first, to leave the easier parts for later.
https://github.com/shinkarom/delimiterc ... 892693cdc9
-
- Posts: 771
- Joined: Sat Sep 08, 2018 5:37 pm
- Location: Ukraine
- Full name: Maksim Korzh
Re: Delimiter development diary
Why to use both?shinkarom wrote: ↑Sun Jan 03, 2021 6:28 pm Converted xboard.cpp.
I selected xboard to convert because I use UCI, and therefore, should start with what I don't like first, to leave the easier parts for later.
https://github.com/shinkarom/delimiterc ... 892693cdc9
Why not just one of them?
Didactic chess engines:
https://www.chessprogramming.org/Maksim_Korzh
Chess programming YouTube channel:
https://www.youtube.com/channel/UCB9-pr ... KKqDgXhsMQ
https://www.chessprogramming.org/Maksim_Korzh
Chess programming YouTube channel:
https://www.youtube.com/channel/UCB9-pr ... KKqDgXhsMQ
-
- Posts: 92
- Joined: Tue Nov 19, 2019 1:26 pm
- Full name: Roman Shynkarenko
Re: Delimiter development diary
Having both protocols provides flexibility. For example, Chessmaster Grandmaster Edition supports only XBoard, while LucasChess supports only UCI.
-
- Posts: 92
- Joined: Tue Nov 19, 2019 1:26 pm
- Full name: Roman Shynkarenko
-
- Posts: 92
- Joined: Tue Nov 19, 2019 1:26 pm
- Full name: Roman Shynkarenko
Re: Delimiter development diary
Converted root.cpp.
Not much of a dev diary, eh? No talking, just dry journaling.
https://github.com/shinkarom/delimiterc ... f5adad49a7
Not much of a dev diary, eh? No talking, just dry journaling.
https://github.com/shinkarom/delimiterc ... f5adad49a7
-
- Posts: 771
- Joined: Sat Sep 08, 2018 5:37 pm
- Location: Ukraine
- Full name: Maksim Korzh
Re: Delimiter development diary
It reminds me commits on githubshinkarom wrote: ↑Wed Jan 06, 2021 4:21 pm Converted root.cpp.
Not much of a dev diary, eh? No talking, just dry journaling.
https://github.com/shinkarom/delimiterc ... f5adad49a7
Diary like thread example: http://talkchess.com/forum3/viewtopic.p ... 9&p=875598
Didactic chess engines:
https://www.chessprogramming.org/Maksim_Korzh
Chess programming YouTube channel:
https://www.youtube.com/channel/UCB9-pr ... KKqDgXhsMQ
https://www.chessprogramming.org/Maksim_Korzh
Chess programming YouTube channel:
https://www.youtube.com/channel/UCB9-pr ... KKqDgXhsMQ
-
- Posts: 92
- Joined: Tue Nov 19, 2019 1:26 pm
- Full name: Roman Shynkarenko
Re: Delimiter development diary
I'm starting work on uci.cpp.
This brings me to a question: how should Delimiter be credited? Since my modifications won't amount to much change in the search results, it would be unfair to leave Richard Allbert out of "id author".
On the other hand, including him would imply that he personally assisted me in the project, that he worked with this specific repository, which is not the case.
On the third hand, "based on Lime by Richard Allbert" (a la Rodent) is too much text.
On the fourth hand, should I be impatient and not stop with just porting Lime but continue developing Delimiter in my personal direciton, what would be the advice then?
-
- Posts: 771
- Joined: Sat Sep 08, 2018 5:37 pm
- Location: Ukraine
- Full name: Maksim Korzh
Re: Delimiter development diary
id name delimetershinkarom wrote: ↑Thu Jan 07, 2021 1:57 pmI'm starting work on uci.cpp.
This brings me to a question: how should Delimiter be credited? Since my modifications won't amount to much change in the search results, it would be unfair to leave Richard Allbert out of "id author".
On the other hand, including him would imply that he personally assisted me in the project, that he worked with this specific repository, which is not the case.
On the third hand, "based on Lime by Richard Allbert" (a la Rodent) is too much text.
On the fourth hand, should I be impatient and not stop with just porting Lime but continue developing Delimiter in my personal direciton, what would be the advice then?
id author your_name
in readme: lime derivative/port/based on/inspired by/whatever
id name and author in UCI is just a way for engine to identify itself and get distinguished from other engines.
Didactic chess engines:
https://www.chessprogramming.org/Maksim_Korzh
Chess programming YouTube channel:
https://www.youtube.com/channel/UCB9-pr ... KKqDgXhsMQ
https://www.chessprogramming.org/Maksim_Korzh
Chess programming YouTube channel:
https://www.youtube.com/channel/UCB9-pr ... KKqDgXhsMQ
-
- Posts: 92
- Joined: Tue Nov 19, 2019 1:26 pm
- Full name: Roman Shynkarenko
Re: Delimiter development diary
Converted uci.cpp.
The author included the UCI option "Ponder" but forgot to do anything with it in parse_option. It seems like this option will for some time do nothing.
https://github.com/shinkarom/delimiterc ... 0f71fc9546
PS. Apologies to Richard Delorme. I'm not trying to steal his status as a resident D expert. Had I thought about using Dumb earlier, it would be a different project in this thread.
The author included the UCI option "Ponder" but forgot to do anything with it in parse_option. It seems like this option will for some time do nothing.
https://github.com/shinkarom/delimiterc ... 0f71fc9546
PS. Apologies to Richard Delorme. I'm not trying to steal his status as a resident D expert. Had I thought about using Dumb earlier, it would be a different project in this thread.