bug-xboard
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-XBoard] Gpsshogi don't work


From: h . g . muller
Subject: Re: [Bug-XBoard] Gpsshogi don't work
Date: Fri, 12 Jul 2019 13:34:00 +0200
User-agent: SquirrelMail

Op Vr, 12 juli, 2019 12:38 pm schreef Sam Daille:
> I had the 4.8.0-2 version of Xboard, and I must have installed it with a
> sudo apt-get install command.

OK, thanks. This indeed did not have that preconfiguration yet. In fact I
see now that although I added it 2.5 years ago, we haven't done any
official release since then (4.9.1 was the last). So I should not have
expected it.

> Maybe I could try to change the line
> -uxiAdapter for the basic one (as the uc2wb don't work) ?

I am not sure what you mean here? What is the 'basic one'? Just an empty
string (-uxiAdapter ""), like it was? Note the name is 'uci2wb', not
'uc2wb'. And why do you say it does not work? So far the problem seems to
be that you did not have a working USI engine, which is not UCI2WB's
fault.

>
>
> My last trials : gtockfish run on the command line, and it works
> perfectly with Polyglot.on xboard (as sjaakii).

So this was with the original -adapterCommand in .xboardrc
('-adapterCommand 'polyglot -noini -ec "%fcp" -ed "%fd" -uci
NalimovCache=%defaultCacheSizeEGTB -pg showTbHits=true')? Sjaak II could
run again when you changed this -adapterCommand back to what it was? Could
it be that when you changed it to {uci2wb "%fcp" "%fd"} part of the old
command was inadvertantly left because it is so long that it extended over
two lines in the editor?

Anyhow, now you installed Polyglot there is no need to change the
-adapterCommand; for Chess, Polyglot (invoked by -fUCI or the UCI
checkbox) is as good as UCI2WB. Only for Shogi USI engines UCI2WB is
indispensible.

>
> gpshogi run on the command line, but then as I said when I enter usi it
> just reply usi and so on, without any indications. I had forgotten to
> ,tell
> you, but in the /usr/games/ there is, with gpsshogi, a gpsviewer and a
> gpsusi - can it disturb the uc2wb ?

Well, I am not very familiar with GPS Shogi. But that you have a separate
file gpsusi suggests that the USI and the xShogi version of GPS Shogi are
actually separate executables. (I had expected there to be a single
executable, that would decide what protocol to use for communication based
on whether the first command it received would be 'usi' or 'xshogi'. If
gpsshogi only 'speaks' xshogi, it is really gpsusi that you should use as
engine.

I have no idea what you mean by "and so on, without indications". For one
it should never reply 'usi' to a 'usi' command, but several "option name
..." lines and then 'usiok'. If not, then it is NOT a USI engine. Can you
show what exactly it prints in response to 'usi'? (And perhaps also what
gpsusi prints in that case?)

>
> (I didn't try yet to open shokidoki with ./shokidoki-x64 after
> re-installing it, I'll do this this weekend... And maybe I'll try to
> compile Bonanza too.)

OK. the problem I encountered was that after I unzipped it, the file did
not have execute permission; apparently this had gotten lost in the
process of zipping - uploading - downloading - unzipping. Zo Linux did not
want to run it at all. 'chmod 755' fixed that, and after that I could both
run it from the command line and in XBoard.

>
>
>
> Le ven. 12 juil. 2019 à 10:52, <address@hidden> a écrit :
>
>
>> I still have one question: which version of XBoard are you using (in
>> Help
>> -> About)? I have been looking at the installation script of UCI2WB,
>> because it puzzled me that your setting for -uxiAdapter originally was
>> an empty string, even though you had installed UCI2WB. (So that
>> hand-editing of .xboardrc was needed.)
>>
>> It turned out the install script of UCI2WB indeed is flawed (it sets
>> the -uxiAdapter in the user settings of 'root' instead of yours, because
>> the install will be done through the 'sudo' command). But that should
>> not have mattered, as any recent XBoard should already have been
>> pre-configured to use UCI2WB as -uxiAdapter, (through the accompanying
>> master settings file xboard.conf, which should be in /etc, /etc/xboard
>> or /usr/local/etc depending on how you installed XBoard), even if you
>> have not installed UCI2WB at all.
>>
>>
>> Op Do, 11 juli, 2019 2:25 pm schreef Sam Daille:
>>
>>> I'll try all this, but I wonder if I had the same problem with
>>> another interface like tagua ?
>>>
>>> Le jeu. 11 juil. 2019 à 13:57, <address@hidden> a écrit :
>>>
>>>
>>>
>>>> Oh, I was a bit wrong in my previous message. It appears I actually
>>>> did compile Bonanza on Ubuntu 10.04. And the required command is
>>>>
>>>> make gcc
>>>>
>>>> not just "make". And you should make sure you take the latest
>>>> snapshot of the 'test' branch of the repository, not the 'main'
>>>> branch, which is initially displayed. (The latter holds the original
>>>> Bonanza source I
>>>> used as a starting point.)
>>>>
>>>> I just pushed a new commit to that 'test' branch, as although
>>>> compiling worked on Ubuntu 10.04, it no longer did on Ubuntu 18.10.
>>>> This was due
>>>> to the required libraries being mentioned near the start of the
>>>> compile command, rather than at the end. After I changed that it
>>>> also compiles on Ubuntu 18.10. It does give a few bogus warnings in
>>>> the file csa.c (which
>>>> contains code that would not be executed if you use it as an XBoard
>>>> engine). Just ignore those.
>>>>
>>>> Op Do, 11 juli, 2019 11:34 am schreef Sam Daille:
>>>>
>>>>
>>>>> I have forgotten one thing : if you can explain me how to compil
>>>>> Bonanza
>>>>> using the files on your website, it will be nice of you. At first
>>>>> sight, it seems complicated to me...
>>>>>
>>>>> Le jeu. 11 juil. 2019 à 11:06, Sam Daille <address@hidden>
>>>>> a écrit
>>>>> :
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> I made few trials and I discovered :
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> * that shokidoki certainly had a compilation problem : when I
>>>>>> entered it in the prompt command, it's unknown, unlike gpshsogi
>>>>>> (my
>>>>>> ubuntu is xenial, 16, which is far from 10) ;
>>>>>>
>>>>>>
>>>>>> * that gpsshogi can't be opened step by step as you suggested
>>>>>> (when
>>>>>> I
>>>>>> put usi, it says usi, and so on) ;
>>>>>>
>>>>>> * that sjaakii don't work when I change the lines in .xboardrc
>>>>>> (so
>>>>>> maybe I did a wrong thing ; the other engines don't work, but I
>>>>>> expected it) ;
>>>>>>
>>>>>> * that (which may explain my problems) polyglot wasn't
>>>>>> installed on my computer...
>>>>>>
>>>>>> So I'm going to try again with polyglot installed, and I'll say
>>>>>> if it works (I hope).
>>>>>>
>>>>>> Le mer. 10 juil. 2019 à 10:02, <address@hidden> a écrit
>>>>>> :
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Op Wo, 10 juli, 2019 8:27 am schreef Sam Daille:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Thanks, I misunderstood the UCI/USI problem, now it's
>>>>>>>> clearer.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I installed uci2wb (and sjaakii and shokidoki), but the
>>>>>>>> problem remains
>>>>>>> :
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> when I changed the lines -adapterCommand -uxiAdapter on my
>>>>>>>> .xboardrc
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> (by
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> the prompt command or in hand), gpshsogi or shokidoki don't
>>>>>>>>  work (but sjakii work without this change, and it plays
>>>>>>>> better than gnushogi
>>>>>>> indeed
>>>>>>>> ^_^).
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> OK, one thing at the time...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> It is strange that Shokidoki doesn't work; this is not a USI
>>>>>>> engine, so the adapter commands should not matter for it, and
>>>>>>> you should be able to run it simply by "xboard -fcp shokidoki"
>>>>>>> from the command line (if the shokidoki binary is installed in
>>>>>>> a directory that is in your path, like /usr/local/bin/), or
>>>>>>> "xboard -fcp ./shokidoki" if it is in
>>>>>>> the current directory. Like sjaakii.
>>>>>>>
>>>>>>> Shokidoki is closed source, so I only distribute the binary,
>>>>>>> which I compiled on my own Linux VM. Problem might be that
>>>>>>> this was an Ubuntu 10.04 machine, and that this is now so
>>>>>>> outdated that binaries from there so not work anymore on
>>>>>>> recent Ubuntus. Perhaps you could try to run it from the
>>>>>>> command line directly (i.e. wiythout XBoard), through
>>>>>>> "./shokidoki", and then type
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> xboard protover 2
>>>>>>>
>>>>>>> to see if and how it responds?
>>>>>>>
>>>>>>>
>>>>>>> For GPS Shogi the same problem could apply. So the first step
>>>>>>>  here would also be to try to run it from the command line,
>>>>>>> thoughe the command "gpsshogi". (Or perhaps "./gpsshogi",
>>>>>>> depending on where it was installed. I will assume in the
>>>>>>> following that the required command is simply "gpsshogi".) If
>>>>>>> it starts you should type the line
>>>>>>>
>>>>>>>
>>>>>>> usi
>>>>>>>
>>>>>>> to it, and see if it responds by printing some "option name
>>>>>>> ..."
>>>>>>> lines followed by "usiok". And after that type "isready", to
>>>>>>> which it should respond with "readyok".
>>>>>>>
>>>>>>> If this works the next step would be to test it in
>>>>>>> combination with UCI2WB, through the command "uci2wb -s
>>>>>>> gpsshogi .", and type
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> xboard protover 2
>>>>>>>
>>>>>>> This should make it print a number of 'feature' lines ending
>>>>>>> with "feature
>>>>>>> done=1". Typing
>>>>>>>
>>>>>>> post memory 64 new variant shogi level 40 5 0 time 10000 go
>>>>>>>
>>>>>>> to it should set it thinking, and finally print a move.
>>>>>>>
>>>>>>> If this does work the problem must be in the interaction with
>>>>>>>  XBoard.
>>>>>>> To
>>>>>>> fiugure that out, first change the -uxiAdapter in the
>>>>>>> .xboardrc
>>>>>>> file to
>>>>>>>
>>>>>>> -uxiAdapter {uci2wb debug -%variant "%fcp" "%fd"}
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> and start XBoard with the command
>>>>>>>
>>>>>>> xboard -variant shogi -fcp gpsshogi -fUSI -debug
>>>>>>>
>>>>>>> The inclusion of the extra 'debug' options should make UCI2WB
>>>>>>>  report everything it does to XBoard, and make XBoard save
>>>>>>> all communication with UCI2WB on a file xboard.debug in the
>>>>>>> current directory. If things get stuck, just quit XBoard and
>>>>>>> attach that file to the e-mail so I can see what is going on.
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I noticed that in the .xboardrc there wasn't first an
>>>>>>>> -uxiAdapter
>>>>>>>> line, so maybe this line is useless ? Or maybe there is
>>>>>>>> another problem in the settings ?
>>>>>>>
>>>>>>> The -uxiAdapter setting specifies which command XBoard should
>>>>>>>  issue for an engine that was accompanied by the option -fUSI
>>>>>>> /
>>>>>>> -sUSI. Where
>>>>>>> words starting with '%' refer to the value of the XBoard
>>>>>>> option with the corresponding name. XBoard has no hard-coded
>>>>>>> default for this, so if it was not set to a value in the
>>>>>>> master settings file, it will be defined as empty string, and
>>>>>>> the -fUSI/-sUSI option (and USI/UCCI
>>>>>>> checkbox in the menu dialog, which add that option) would not
>>>>>>> work. This was originally the case, as the .xboardrc you
>>>>>>> mailed me contained
>>>>>>>
>>>>>>> -adapterCommand 'polyglot -noini -ec "%fcp" -ed "%fd" -uci
>>>>>>> NalimovCache=%defaultCacheSizeEGTB -pg ShowTbHits=true'
>>>>>>> -uxiAdapter ""
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> which has it as an empty string. From the point-of-view of
>>>>>>> Ubuntu
>>>>>>> package distribution that makes sense, as when you have not
>>>>>>> installed UCI2WB yet it could not work anyway. Ideally
>>>>>>> installing of UCI2WB would automatically set the -uxiAdapter
>>>>>>> in XBoard's settings to use it (as
>>>>>>> in theory there could be other USI adapters that you could
>>>>>>> have installed instead). The UCI2WB install procedure might
>>>>>>> not be smart enough to do that, though. This is why I wrote
>>>>>>> you should check it first.
>>>>>>>
>>>>>>> You can see that originally the -adapterCommand (used for
>>>>>>> engines that specify -fUCI) originally was set to use
>>>>>>> Polyglot, which is
>>>>>>> a Chess-only adapter for UCI (and should also be installed as a
>>>>>>> separate Ubuntu package before the -fUCI option can work).
>>>>>>> UCI2WB should be able
>>>>>>> to do the job as well, though, but there is no harm in having
>>>>>>> both UCI2WB
>>>>>>> and Polyglot on your system, so there isn't really any need to
>>>>>>>  change -adapterCommand as long as you have Polyglot
>>>>>>> installed. This pertains to the problem of running Stockfish.
>>>>>>>
>>>>>>>>
>>>>>>>> I joined you a copy of my .xboardrc, it may help.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Le mar. 9 juil. 2019 à 17:43, <address@hidden> a
>>>>>>>> écrit
>>>>>>>> :
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Neither Stockfish nor GPS Shogi support XBoard protocol;
>>>>>>>>> they can only be used on XBoard with the aid of an
>>>>>>>>> adapter. Stockfish
>>>>>>>>> communicates in UCI, and GPS Shogi in USI. The UCI2WB
>>>>>>>>> adapter can handle both these protocols. So to use these
>>>>>>>>> engines you have to
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 1) install uci2wb on your computer,
>>>>>>>>> 2) make sure xboard is configured to use UCI2WB as adapter
>>>>>>>>>  rather than Polyglot, 3) use the -fUCI or -fUSI options
>>>>>>>>> when starting XBoard from the command line, (e.g. "xboard
>>>>>>>>> -fcp
>>>>>>>>> stockfish -fUCI"), or tick the UCI or USI/UCCI checkbox
>>>>>>>>> when you embed the engine through the Load Engine dialog.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> To make sure step (2) is realized you could open the
>>>>>>>>> .xboardrc
>>>>>>>>> file (where the user settings for XBoard are saved) in
>>>>>>>>> your home directory with a text editor, and look at the
>>>>>>>>> value of the -adapterCommand and -uxiAdapter. The value
>>>>>>>>> for these should be
>>>>>>>>>
>>>>>>>>> -adapterCommand {uci2wb "%fcp" "%fd"}
>>>>>>>>> -uxiAdapter {uci2wb -%variant "%fcp" "%fd"}
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Only if this would not work there would be a genuine
>>>>>>>>> problem.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Note that GNUshogi is so buggy that it plays like total
>>>>>>>>> crap, and can randomly decide to overlook even mate in 1.
>>>>>>>>> There are
>>>>>>>>> a number of engines that are able to play decent Shogi on
>>>>>>>>> XBoard without
>>>>>>>>> adapter, though; in order of increasing strength these are
>>>>>>>>>  Sjaak
>>>>>>>>> II, CrazyWa,
>>>>>>>>> Shokidoki and
>>>>>>>>> Bonanza (the XBoard version in my on-line repository
>>>>>>>>> http://hgm.nubati.net/cgi-bin/gitweb.cgi ). I am not sure
>>>>>>>>> the latter would be weaker than GPS Shogi.
>>>>>>>>>
>>>>>>>>> Op Di, 9 juli, 2019 5:09 pm schreef Sam Daille:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hello.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I'm on Ubuntu Xenial and I installed Xboard to play
>>>>>>>>>> chess and shogi, but :
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> * Gpsshogi don't work (it never plays) when I open
>>>>>>>>>> Xboard
>>>>>>>>>> with it (-variant shogi -fcp gpsshogi)
>>>>>>>>>>
>>>>>>>>>> * Stockfish don't work when I open xboard with it (-fcp
>>>>>>>>>>  stockfish), it don't want to play and exit when I try
>>>>>>>>>> to force it to move now, but this bug is well-known :
>>>>>>>>>> http://savannah.gnu.org/bugs/?56024
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I tried to limit the reflexion time and to change the
>>>>>>>>>> size of the board, but no way.
>>>>>>>>>>
>>>>>>>>>> Do you have some ideas to suggest to me ? I'm ready to
>>>>>>>>>> try anything (because Gnushogi on Xshogi is really to
>>>>>>>>>> weak for me...)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks a lot.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Sam
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Bug-XBoard mailing list
>>>>>>>>>> address@hidden
>>>>>>>>>> https://lists.gnu.org/mailman/listinfo/bug-xboard
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>





reply via email to

[Prev in Thread] Current Thread [Next in Thread]