Might you be interested in trying to compile and hosting a cygwin1.dll independent version of Jaap Weidemann's modified polyglot, in addition to the 1.4w version you are now offering for download?
Below is a list of improvements/changes Jaap made to polyglot. The last one he released was, I believe, "PolyGlot 1.4 X 070325". The below list is from the read me text included in the PolyGlot 1.4 X 070325 zip file.
Maybe since "Polyglot 1.4w is based on polyglot 1.3w" it isn't possible to do?
2007/03/13: PolyGlot 1.4 X 070313
- added elo to the UCI_Opponent string
- added kibitzing of bookpv and tbhits
- added "DrawOffer" and "DrawOfferMoves" commands
- fixed issues with parsing certain tag strings in book-making
- fixed draws by repitition while still in book
- fixed engine time losses
2007/03/25: PolyGlot 1.4 X 070325
- added -min-elo option to book making
Jaap's website has been down awhile, but his last released Windows version of polyglot can be gotten here (source code included in the zip).
(at the time of uploading the above file, connecting to the rapidshare site was near impossible for me.)
Hi Charles
I've looked at Jaap's polyglot version,but saw not much 'added value' in the extra features.
Are there any extensions in particular that you would like to see in my version?
The dust moved forward & the dust moved back.
New Broom.
The dust ends up in a brown paper sack.
New Broom.
Progress is made but progress is slow.
more polyglot 1.4w fixes
Olivier and Leo reported problems with Timea and Learning Lemming.
I don't have those (they are private) but "fortunatly" i noticed Madeleine had the same problems too
and could use that to test,find and fix the old broom.
The bugs show up for engines that need the "SyncStop" fix for pondering.
Also added "Affinity" option,to tie the engine to 1 or more cpu's of your choice.(ok,so its freaky )
more polyglot 1.4w fixes
Olivier and Leo reported problems with Timea and Learning Lemming.
I don't have those (they are private) but "fortunatly" i noticed Madeleine had the same problems too
and could use that to test,find and fix the old broom.
The bugs show up for engines that need the "SyncStop" fix for pondering.
Also added "Affinity" option,to tie the engine to 1 or more cpu's of your choice.(ok,so its freaky )
I kind of like the draw option supported in the last version of polyglot by the way...better of course would be if UCI LET YOU OFFER AND ACCEPT DRAWS !!!GRRRR!!!! and polyglot passed that info on.
more polyglot 1.4w fixes
Olivier and Leo reported problems with Timea and Learning Lemming.
I don't have those (they are private) but "fortunatly" i noticed Madeleine had the same problems too
and could use that to test,find and fix the old broom.
The bugs show up for engines that need the "SyncStop" fix for pondering.
Also added "Affinity" option,to tie the engine to 1 or more cpu's of your choice.(ok,so its freaky )
I kind of like the draw option supported in the last version of polyglot by the way...better of course would be if UCI LET YOU OFFER AND ACCEPT DRAWS !!!GRRRR!!!! and polyglot passed that info on.
-Sam
well , why not,polyglot is not a uci gui but a uci<->winboard adapter
so we can relax a bit from the uci philosophy.
from the uci protocol definition:
option
This command tells the GUI which parameters can be changed in the engine.
This should be sent once at engine startup after the "uci" and the "id" commands
if any parameter can be changed in the engine.
The GUI should parse this and build a dialog for the user to change the settings.
Note that not every option needs to appear in this dialog as some options like
"Ponder", "UCI_AnalyseMode", etc. are better handled elsewhere or are set automatically.
so one could define a parameter UCI_Drawoffer,that would cause no problems with any standard uci gui.
eg "option name UCI_DrawOffer type string\n"
Now we only need to define suitable strings for incoming/outgoing drawoffers and declines.
Ofcouse we need to take care of engines not handling this option at all.
Anyone has a more detailed proposal?
can you describe briefly in which cases (of "wrongdoing" by an engine) the SyncStop option must be set, and why the Polyglot behaviour for SyncStop is not the default behaviour?
This is a part of the "confusion" being discussed in the thread Sam pointed you to.
can you describe briefly in which cases (of "wrongdoing" by an engine) the SyncStop option must be set, and why the Polyglot behaviour for SyncStop is not the default behaviour?
This is a part of the "confusion" being discussed in the thread Sam pointed you to.
Sven
Madeleine was playing illegal moves,eg it played the ponder move which was just played by the opponent.But that was before i removed some bugs
so one could define a parameter UCI_Drawoffer,that would cause no problems with any standard uci gui.
eg "option name UCI_DrawOffer type string\n"
Now we only need to define suitable strings for incoming/outgoing drawoffers and declines.
Ofcouse we need to take care of engines not handling this option at all.
Anyone has a more detailed proposal?
Best
Fonzy
I don't have a more detailed suggestion, but I would LOVE if someone implemented something like that. The main reason I am considering the bother of adding Winboard support is I really want to be able to do intelligent draw decisions...without it UCI engines are banned from making some important chess decisions (and bug the heck out of human players in drawn positions I am sure). Any support you put in polyglot for sending / receiving draw offers I would happily add in my engine.
One other thing I remember Jaap said he added you might consider, he automatically set polyglot at a high priority level I think, so it would always process and send along input (otherwise sometimes the engine would hog all the cpu and not know polyglot was trying to tell it something for some time...enough to cause time losses in some cases.
so one could define a parameter UCI_Drawoffer,that would cause no problems with any standard uci gui.
eg "option name UCI_DrawOffer type string\n"
Now we only need to define suitable strings for incoming/outgoing drawoffers and declines.
Ofcouse we need to take care of engines not handling this option at all.
Anyone has a more detailed proposal?
Best
Fonzy
I don't have a more detailed suggestion, but I would LOVE if someone implemented something like that. The main reason I am considering the bother of adding Winboard support is I really want to be able to do intelligent draw decisions...without it UCI engines are banned from making some important chess decisions (and bug the heck out of human players in drawn positions I am sure). Any support you put in polyglot for sending / receiving draw offers I would happily add in my engine.
One other thing I remember Jaap said he added you might consider, he automatically set polyglot at a high priority level I think, so it would always process and send along input (otherwise sometimes the engine would hog all the cpu and not know polyglot was trying to tell it something for some time...enough to cause time losses in some cases.
-Sam
I'll look at the draw stuff.
I don't like the idea yet for setting pg at a high(er) prio per default.
But it might be an idea to implement "nice" in the windows version of pg.
Best
Fonzy
)