Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nibbler doesnt work properly with leela chess 0 under windows 7 x64 #220

Open
Vukica14 opened this issue Jan 14, 2023 · 43 comments
Open

Nibbler doesnt work properly with leela chess 0 under windows 7 x64 #220

Vukica14 opened this issue Jan 14, 2023 · 43 comments
Labels
support Getting things up-and-running windows Windows-specific problems

Comments

@Vukica14
Copy link

Hello to everyone,
I am happy to have Nibbler and leela chess 0 but v29 of leela doesnt fit with Nibbler 2.4.0 and its working independently when I am running benchmark for example from cmd propmt.

Is there any workaround to help to fix this issue?

Many thanks in advance.
2023-01-14 16_29_11-Nibbler

@rooklift
Copy link
Owner

Is this different from #203 ?

@Vukica14
Copy link
Author

It is as I discovered what version of leela is incompatible with nibbler under win7 x64, so I decided to post again.

@rooklift
Copy link
Owner

I still don't know what to suggest.

@Vukica14
Copy link
Author

This is log file of nibbler:

Nibbler startup at Sat, 14 Jan 2023 15:48:56 GMT

Launching D:_LeelaZero\lc0-v0.29.0-windows-gpu-nvidia-cudnn\lc0.exe
(failed) --> uci

@Vukica14
Copy link
Author

and this is once when I load v26.1

--> uci

Launching D:_LeelaZero\lc0-v0.26.1-windows-gpu-nvidia-cuda\lc0.exe

(failed) --> quit
--> uci
. _
. | _ | |
. |_ |_ |_| v0.26.1 built Jul 15 2020
< id name Lc0 v0.26.1
< id author The LCZero Authors.
< option name WeightsFile type string default
< option name Backend type combo default cudnn-auto var cudnn-auto var cudnn var cudnn-fp16 var random var check var recordreplay var roundrobin var multiplexing var demux
< option name BackendOptions type string default
< option name Threads type spin default 2 min 1 max 128
< option name NNCacheSize type spin default 200000 min 0 max 999999999
< option name MinibatchSize type spin default 256 min 1 max 1024
< option name MaxPrefetch type spin default 32 min 0 max 1024
< option name CPuct type string default 2.147000
< option name CPuctAtRoot type string default 2.147000
< option name CPuctBase type string default 18368.000000
< option name CPuctBaseAtRoot type string default 18368.000000
< option name CPuctFactor type string default 2.815000
< option name CPuctFactorAtRoot type string default 2.815000
< option name RootHasOwnCpuctParams type check default true
< option name Temperature type string default 0.000000
< option name TempDecayMoves type spin default 0 min 0 max 100
< option name TempDecayDelayMoves type spin default 0 min 0 max 100
< option name TempCutoffMove type spin default 0 min 0 max 1000
< option name TempEndgame type string default 0.000000
< option name TempValueCutoff type string default 100.000000
< option name TempVisitOffset type string default 0.000000
< option name DirichletNoiseEpsilon type string default 0.000000
< option name DirichletNoiseAlpha type string default 0.300000
< option name VerboseMoveStats type check default false
< option name LogLiveStats type check default false
< option name FpuStrategy type combo default reduction var reduction var absolute
< option name FpuValue type string default 0.443000
< option name FpuStrategyAtRoot type combo default same var reduction var absolute var same
< option name FpuValueAtRoot type string default 1.000000
< option name CacheHistoryLength type spin default 0 min 0 max 7
< option name PolicyTemperature type string default 1.607000
< option name MaxCollisionEvents type spin default 32 min 1 max 65536
< option name MaxCollisionVisits type spin default 9999 min 1 max 1000000
< option name OutOfOrderEval type check default true
< option name MaxOutOfOrderEvalsFactor type string default 1.000000
< option name StickyEndgames type check default true
< option name SyzygyFastPlay type check default true
< option name MultiPV type spin default 1 min 1 max 500
< option name PerPVCounters type check default false
< option name ScoreType type combo default centipawn var centipawn var centipawn_with_drawscore var centipawn_2019 var centipawn_2018 var win_percentage var Q var W-L
< option name HistoryFill type combo default fen_only var no var fen_only var always
< option name MovesLeftMaxEffect type string default 0.100000
< option name MovesLeftThreshold type string default 1.000000
< option name MovesLeftSlope type string default 0.005000
< option name MovesLeftConstantFactor type string default 0.000000
< option name MovesLeftScaledFactor type string default 0.000000
< option name MovesLeftQuadraticFactor type string default 1.000000
< option name DisplayCacheUsage type check default false
< option name MaxConcurrentSearchers type spin default 1 min 0 max 128
< option name DrawScoreSideToMove type spin default 0 min -100 max 100
< option name DrawScoreOpponent type spin default 0 min -100 max 100
< option name DrawScoreWhite type spin default 0 min -100 max 100
< option name DrawScoreBlack type spin default 0 min -100 max 100
< option name NodesPerSecondLimit type string default 0.000000
< option name SolidTreeThreshold type spin default 100 min 1 max 2000000000
< option name SyzygyPath type string default
< option name Ponder type check default true
< option name UCI_Chess960 type check default false
--> setoption name UCI_Chess960 value true
< option name UCI_ShowWDL type check default false
< option name UCI_ShowMovesLeft type check default false
< option name ConfigFile type string default lc0.config
< option name KLDGainAverageInterval type spin default 100 min 1 max 10000000
< option name MinimumKLDGainPerNode type string default 0.000000
< option name SmartPruningFactor type string default 1.330000
< option name SmartPruningMinimumBatches type spin default 0 min 0 max 10000
< option name NodesAsPlayouts type check default false
< option name RamLimitMb type spin default 0 min 0 max 100000000
< option name MoveOverheadMs type spin default 200 min 0 max 100000000
< option name TimeManager type string default legacy
< option name StrictTiming type check default false
< option name LogFile type string default
< uciok
--> setoption name LogLiveStats value true
--> setoption name MoveOverheadMs value 0
--> setoption name MultiPV value 500
--> setoption name ScoreType value centipawn
--> setoption name SmartPruningFactor value 0
--> setoption name UCI_ShowWDL value true
--> setoption name VerboseMoveStats value true
--> isready
< readyok
--> ucinewgame
. Found pb network file: D:_LeelaZero\lc0-v0.26.1-windows-gpu-nvidia-cuda/703350.pb.gz
. Creating backend [cudnn-auto]...
. Switching to [cudnn]...
. CUDA Runtime version: 10.0.0
. Cudnn version: 7.4.2
. Latest version of CUDA supported by the driver: 11.4.0
. GPU: NVIDIA GeForce GTX 850M
. GPU memory: 2 Gb
. GPU clock frequency: 901.5 MHz
. GPU compute capability: 5.0

@Vukica14
Copy link
Author

Why you close this? maybe someone else has idea.

@rooklift
Copy link
Owner

I closed it because it's identical to #203 which is still open. Still I'll reopen this and close that one, if you prefer.

@rooklift rooklift reopened this Jan 14, 2023
@rooklift rooklift added windows Windows-specific problems support Getting things up-and-running labels Jan 14, 2023
@Vukica14
Copy link
Author

Thanks. I prefer to keep this one as it is more detailed.

@Vukica14
Copy link
Author

its interesting this initial part of log file when I am loading v26.1
Launching D:_LeelaZero\lc0-v0.26.1-windows-gpu-nvidia-cuda\lc0.exe

(failed) --> quit
--> uci
. _
. | _ | |

is that normal behavior?

@rooklift
Copy link
Owner

It seems for 0.29 you are using the cudnn version but for 0.26 you were using the cuda version - can you try the cuda version of 0.29?

@rooklift
Copy link
Owner

its interesting this initial part of log file when I am loading v26.1 Launching D:_LeelaZero\lc0-v0.26.1-windows-gpu-nvidia-cuda\lc0.exe

(failed) --> quit --> uci . _ . | _ | |

is that normal behavior?

I believe that was it trying to tell the previous engine (which didn't start) to quit, which it can't, because it didn't start.

@Vukica14
Copy link
Author

since version 26.2 cuda is transfered into cudNN. I try "go infinite" on cuda v29 but it didnt work so before v26.2 it must be CUDA and after that cudNN.
and, thanks for the clarification.

@rooklift
Copy link
Owner

OK, I see. But I don't know what to do.

@Vukica14
Copy link
Author

I posted also in leela chess but I am still wating for the answer. It seams leela working well but in combo with nibbler making a problems.

@rooklift
Copy link
Owner

btw, in the other issue you mentioned Stockfish not working either. Can you please turn off Dev --> Show engine state and then post a screenshot of what it looks like when loading Stockfish?

@Vukica14
Copy link
Author

Vukica14 commented Jan 14, 2023

sure here is version 15.1 and it is the same for v15
2023-01-14 17_06_43-Nibbler

@rooklift
Copy link
Owner

Please turn off Dev --> Show engine state first.

@Vukica14
Copy link
Author

Vukica14 commented Jan 14, 2023

2023-01-14 17_08_07-Nibbler
I did, I think
2023-01-14 17_08_07-Nibbler

@rooklift
Copy link
Owner

OFF

@rooklift
Copy link
Owner

(Or are you saying it doesn't turn off?)

@Vukica14
Copy link
Author

(Or are you saying it doesn't turn off?)

sorry I didnt get you. I enabled "enginee state" is there anything else I have to do? But both versions of the stockfish doeasnt work

@Vukica14
Copy link
Author

and stockfish both versions works well in fritz 16

@rooklift
Copy link
Owner

I enabled "enginee state"

Please turn it off.

@Vukica14
Copy link
Author

I enabled "enginee state"

Please turn it off.

here it is
2023-01-14 17_22_36-Nibbler

@Vukica14
Copy link
Author

ooo after GO it works :D

@rooklift
Copy link
Owner

So how else were you trying to start the analysis, and was that other way not working?

@Vukica14
Copy link
Author

and for leela 29
2023-01-14 17_23_55-Nibbler

@Vukica14
Copy link
Author

So how else were you trying to start the analysis, and was that other way not working?

for versions lower than 26.2 I see that initialization of the enginee (leela) and for higher versions it cant start

@rooklift
Copy link
Owner

Right, yeah, Leela is definitely failing to start. Could it be a memory issue?

I doubt it will help, but try:

Dev --> Disable hardware acceleration for GUI (turn it on, ticked, enabled)

@rooklift
Copy link
Owner

And then restart Nibbler.

@Vukica14
Copy link
Author

And then restart Nibbler.

I try but it is the same

@rooklift
Copy link
Owner

Can you post your system hardware info?

@Vukica14
Copy link
Author

Can you post your system hardware info?

sure just where to find it?

@rooklift
Copy link
Owner

rooklift commented Jan 14, 2023

Uh. Well I guess I wanted to know how much RAM your computer has, your graphics card, and how much RAM it has as well.

If you don't know them I guess I don't know exactly how one finds them in Windows 7. I would guess your PC is fairly old?

@Vukica14
Copy link
Author

here is GPU
GPU: NVIDIA GeForce GTX 850M
. GPU memory: 2 Gb
. GPU clock frequency: 901.5 MHz
. GPU compute capability: 5.0

and I have
2023-01-14 17_29_51-System

@Vukica14
Copy link
Author

its bit old but I think still powerful 16GB of RAM and quad core

@rooklift
Copy link
Owner

Yeah I think it should be good enough. Uh, can you try the Windows OpenCL version of Leela 0.29, just to see if it works?

@Vukica14
Copy link
Author

Vukica14 commented Jan 14, 2023

I try and its the same.

Awaiting UCIOK

whats that?

@rooklift
Copy link
Owner

When a UCI engine starts up, it sends some info and finally the line uciok. The message from Nibbler indicates we never even got this far.

@rooklift
Copy link
Owner

Actually, now that I think about it, the OpenCL client has a substantial "tuning" period on first run, do you see any output at all on the right side of the window?

@Vukica14
Copy link
Author

Vukica14 commented Jan 14, 2023

2023-01-14 17_43_24-Nibbler

Actually, now that I think about it, the OpenCL client has a substantial "tuning" period on first run, do you see any output at all on the right side of the window?

this is the window
2023-01-14 17_43_24-Nibbler
with HW acc enabled and disabled

======================================================================================================================================
Nibbler startup at Sat, 14 Jan 2023 16:44:05 GMT

Launching D:_LeelaZero\lc0-v0.29.0-windows-gpu-opencl\lc0.exe

(failed) --> uci

@rooklift
Copy link
Owner

OK. Sorry, I wish I knew the cause but I can't figure it out.

@Vukica14
Copy link
Author

OK. Sorry, I wish I knew the cause but I can't figure it out.

No prob and many thanks for the wish to help out here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Getting things up-and-running windows Windows-specific problems
Projects
None yet
Development

No branches or pull requests

2 participants