Polyglot 1.4w Released

[F. Bluemers]

Thanks both.
Source fixed and updated.
Kenny,the pipe.h and pipe.cpp files are not part of the source anymore.
Might be better to unzip to an empty directory

Best
Fonzy

[krazyken]

I'm fairly certain pipe.h and pipe.cpp are still in the zip file I download from the website. But deleting them, it compiles and runs for me now. (under Mac OS X)
Thanks!

[F. Bluemers]

Zip file cleaned up:pipe.h and pipe.cpp removed
Resigning added.
The engine can now resign.
(note: this will not bring many elo points )

1.To activate draw offers or resigning,the engine has
to define the "UCI_DrawOffers" parameter with the 'option" command at startup.

2.To offer a draw or accept a draw offer:just send "info string DrawOffer" to polyglot.
3.If winboard sends "draw", polyglot sends "setoption DrawOffer draw" to the engine.
4.To resign: send "info string Resign" to polyglot.
Please check the winboard documentation for the draw/drawoffer and resign commands.

[BubbaTough]

Resigning added.
The engine can now resign.

Sweet! I will go work on my ultra-cool resign logic.

[F. Bluemers]

multipv analysis output has been fixed.
note that the worst move is in the top of the engine output window.
added timestamp to logfile

edit:playing games with multipv will not make sense
Best
Fonzy

[Dirt]

multipv analysis output has been fixed.
note that the worst move is in the top of the engine output window.
added timestamp to logfile

edit:playing games with multipv will not make sense :lol:
Best
Fonzy

Thanks for the effort. It is improved, but I wonder if you're seeing the same thing I am with Rybak 2.2n2 32-bit:

1) Only the current depth is displayed.

2) At deeper depths, the engine output can be completely blank for long periods of time.

3) Once all the PVs for a depth are displayed, the main line (in the board window, not the engine output) shows the worst of the lines.

I can guess that with the current Winboard, fixing #1 would probably require sending the entire analysis for all depths with each update, and #3 might not be possible to fix at all. Is it possible to fix #2?

[F. Bluemers]

multipv analysis output has been fixed.
note that the worst move is in the top of the engine output window.
added timestamp to logfile

edit:playing games with multipv will not make sense
Best
Fonzy

Thanks for the effort. It is improved, but I wonder if you're seeing the same thing I am with Rybak 2.2n2 32-bit:

1) Only the current depth is displayed.

2) At deeper depths, the engine output can be completely blank for long periods of time.

3) Once all the PVs for a depth are displayed, the main line (in the board window, not the engine output) shows the worst of the lines.

I can guess that with the current Winboard, fixing #1 would probably require sending the entire analysis for all depths with each update, and #3 might not be possible to fix at all. Is it possible to fix #2?

I cannot reproduce #2 at the moment,I always have at least 1 pv.
Are there any special rybka settings you are using?
how big did you set multipv?
Best
Fonzy

[Dirt]

I cannot reproduce #2 at the moment,I always have at least 1 pv.
Are there any special rybka settings you are using?
how big did you set multipv?
Best
Fonzy

Nothing special that I'm aware of. I've been using MultiPV=4. It's most likely OS related, since I'm still using Window98. Unless someone else has this problem while using a newer OS you should probably just ignore it.

[F. Bluemers]

I cannot reproduce #2 at the moment,I always have at least 1 pv.
Are there any special rybka settings you are using?
how big did you set multipv?
Best
Fonzy

Nothing special that I'm aware of. I've been using MultiPV=4. It's most likely OS related, since I'm still using Window98. Unless someone else has this problem while using a newer OS you should probably just ignore it.

Ok,probably.Just curious ,do other engines behave the same?

btw fixing #1 and #3 will be more complicated.
I'll look into it.hope this fix will be usable till then
Best
Fonzy

[Dirt]

I cannot reproduce #2 at the moment,I always have at least 1 pv.
Are there any special rybka settings you are using?
how big did you set multipv?
Best
Fonzy

Nothing special that I'm aware of. I've been using MultiPV=4. It's most likely OS related, since I'm still using Window98. Unless someone else has this problem while using a newer OS you should probably just ignore it.

Ok,probably.Just curious ,do other engines behave the same?

btw fixing #1 and #3 will be more complicated.
I'll look into it.hope this fix will be usable till then
Best
Fonzy

I just tried Glaurung 2.1 and it's about the same. At shallow depths it often will just add each new variation as it finds it, but when it gets deeper (say, over a minute for a ply) it usually displays one line and quickly erases it, then displays two lines and quickly erases it, etc. until it show them all, which stay up until it has finished the first variation at the next depth.