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

BVLC/caffe "windows environment python 3.5 plot_training_log.py" #6169

Open
briansune opened this issue Jan 13, 2018 · 2 comments
Open

BVLC/caffe "windows environment python 3.5 plot_training_log.py" #6169

briansune opened this issue Jan 13, 2018 · 2 comments

Comments

@briansune
Copy link

Issue summary
BVLC/caffe python is developed under python 2.7 environment and the python script have lots of issues:
By running "python plot_training_log.py" or other python scripts errors or python syntax problems are shown.

Steps to reproduce*
Just simply run the the plot_training_log script there are at least different forms of errors:
@ line 141 & atfer
"print xxxx %xxxx"
syntax must modify into
"print(xxxx %xxx)"

@line 45 & after
for i in xrange(num_fields):
syntax must modify into
for i in range(num_fields):

There are more syntax incompatibilities issues in other script.
Please add two version of python script folders / file and labeled as _35 & _27.

System configuration
Operating system: Windows 7 x64
Python 3.5 @ Anaconda3

@Noiredd
Copy link
Member

Noiredd commented Jan 15, 2018

Good idea for a PR! resize_and_crop_images.py and summarize.py have problems with print expressions as well. There are some inconsistencies in parse_log.py, which has both print xxx and print(xxx) syntax. I did not check for other issues as I'm not very familiar with Python 3.5 myself.

Would you be able to fix bugs and provide 3.5-compatible versions of the scripts? I would gladly accept such PR.
I would recommend leaving existing (2.7-compatible) scripts intact - people might load them in their own programs, so renaming or significantly modifying them might break their setups.

@briansune
Copy link
Author

@Noiredd May i ask what are the steps for the PR <- Should i directly modify the code or other methods?

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

No branches or pull requests

2 participants