Is it normal that stockfish send a greater number of readyok than I send it isready?
#being sent more readyoks than I send isready?
north moss
fathom ether
send the log
readyok is only ever sent as a response to isready pretty sure the issue lies within your code
north moss
Okay, thank you so much!
north moss
Does stockfish have an echo/trace mode for debugging? Essentially it echos back the commands you sent it in addition to its own responses?
I wish I could wrap boost::process::opstream
Rather, was skilled enough to do that faster than adding print statements
fathom ether
mh theres a log option but i dunno what it does tbh
i have my own implementation for commuting with stockfish in c++
which i have here https://github.com/Disservin/fastchess/tree/master/app/src/engine/process
north moss
Okay, so why after my first "go depth" is "readyok" printed before the depth information is?
THAT is apparently the case I'm not handling well
I would expect "go depth 20" to finish before readyok is sent to me
signal veldt
go isn't a blocking command. When you send isready the engine is expected to reply as soon as possible without waiting on existing searches
(this is what the uci spec states)
north moss
hmm.... how do I know when the depth search is finished then?
Also, hilariously, that invalidates a metric ton of numbers I crunched
Because I now don't know if the race condition meant I was recording the wrong eval for a position
signal veldt
hmm.... how do I know when the depth search is finished then?
it will send bestmove
unless it's an infinite search
north moss
oh, fantastic
signal veldt
then it won't ever end until you send stop