LeelaChessZero / LeelaChessZero/lczero-client
Troubles installing Leela
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 74
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Hey,
have some troubles installing Leela, first of all CuDa is instaled, which I verify by:
nvcc -V
(I have GTX of course)
The engine ask about Password and Username and is then doing nothing:
I executed the client manually.
Thread is deadlocked after:
2018/08/09 23:11:23 lc0_main.go:537: serverParams: [--visits=800 --cpuct=1.2 --resign-percentage=0 --resign-playthrough=100]
lc0 is never quiet.
Args: [C:\Users\Agando\Desktop/lc0 selfplay --visits=800 --cpuct=1.2 --resign-percentage=0 --resign-playthrough=100 --training=true --weights=networks\0b742fce3f6ae15b64f7f0eaf417fe58c1688f97e5dbd6d9774bf97e10462140]
2018/08/09 23:11:23 lc0_main.go:455: BestMove channel closed unexpectedly, exiting train loop
2018/08/09 23:11:23 lc0_main.go:460: GameInfo channel closed, exiting train loop
2018/08/09 23:11:23 lc0_main.go:477: Waiting for lc0 to stop
lc0 exited with: exit status 32212257812018/08/09 23:11:23 lc0_main.go:482: lc0 stopped
2018/08/09 23:11:23 lc0_main.go:484: Waiting for uploads to complete
2018/08/09 23:11:23 lc0_main.go:661: Client self-exited without producing any games.
2018/08/09 23:11:23 lc0_main.go:662: Sleeping for 30 seconds...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Windows selfplay command from the report, including the supplied visits, training, and weights arguments. Start in lc0_main.go around the logged lines 455-484 and compare the client behavior with the lc0 exit status; done means the client produces games instead of exiting without any.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100