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

Creates Empty SGF and then analyzes :-) #12

Open
laefsky opened this issue Mar 6, 2018 · 11 comments
Open

Creates Empty SGF and then analyzes :-) #12

laefsky opened this issue Mar 6, 2018 · 11 comments

Comments

@laefsky
Copy link

laefsky commented Mar 6, 2018

Thank you for what I know was a lot of work and which I hope will improve my go playing and analysis
I know some python, the python installed as a system default is Anaconda 3.6 so I am using a winpython 2.7
to run the program mybat.bat is my running script. When I run the program seems to write a zero length
sgf file and then proceed to do its analysis. Can you offer any advice. Is there an email address or phone number where I can contact you directly. My email is laefsky AT comcast DOT net

Windows Bat File Follows

.\python.exe E:\leela-analysis-master\sgfanalyze.py -v3 E:\downloads\testa.sgf --leela E:\Leela0110GTP\Leela0110GTP_OpenCL.exe > test2.sgf
my email is : laefsky AT comcast DOT net

@lightvector
Copy link
Owner

Does the ">" operation work differently in windows? The idea is supposed to be that you redirect the output of the program to a file, because the output to stdout is the SGF contents. So that's not working if it creates the file and then still outputs the SGF to console.

Or maybe you didn't wait long enough for the analysis to finish? If what you're seeing on the console is information about the progress of the analysis, then of course the SGF file will be empty for a while, it hasn't finished analyzing it yet to output anything. You need to just wait until it's done and when it's done the SGF will be nonempty.

@laefsky
Copy link
Author

laefsky commented Mar 6, 2018

Thank You for the rapid reply. As far as I know > redirects STDOUT to a file and >> redirects STDOUT and appends. Some differences are that I need to run python on the file from an executable as the system Python is Anaconda 3.6. Is it supposed to create a null foo.sgf immediately and then append the results of the analysis? Are there flags to place
The intermediate analysis files in a given directory? Is the fact that I’m running python from a command shell and only then redirecting output mean that I am not capturing the results of the python program output.
How long should the analysis run with a multicore i7 and GTX 1080 GPU? I am creating the analysis intermediate files and watching program output with -v3 in a python shell window but I don’t know whether I am effectively redirecting output from the python subprocess?

Many thanks for your excellent program and for your anticipated help.

--Ira Laefsky

@lightvector
Copy link
Owner

lightvector commented Mar 6, 2018

Yes, it's supposed to create an empty file immediately, this has nothing to do with any of my code, that's what ">" does, it creates a file and then over time as the program outputs, it puts that output in the file.

Sounds like you should just wait for the analysis to finish? It will output all the sgf analysis when the whole program is done running, which then should get redirected to your file.

Edit: It will show a (very approximate) time estimate, if you watch it. Normally it should take at least some hours, more if you told it to use more time per move.

@laefsky
Copy link
Author

laefsky commented Mar 6, 2018 via email

@lightvector
Copy link
Owner

lightvector commented Mar 6, 2018 via email

@laefsky
Copy link
Author

laefsky commented Mar 6, 2018 via email

@laefsky
Copy link
Author

laefsky commented Mar 6, 2018 via email

@lightvector
Copy link
Owner

lightvector commented Mar 6, 2018 via email

@laefsky
Copy link
Author

laefsky commented Mar 7, 2018 via email

@laefsky
Copy link
Author

laefsky commented Mar 7, 2018 via email

@laefsky
Copy link
Author

laefsky commented Mar 7, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants