-
Notifications
You must be signed in to change notification settings - Fork 89
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
[HELP!] Loading image error #110
Comments
This error message is not comprehensive; the most likely issue is that you forget to modify the paths in the data JSON file. I sincerely hope you can resolve your problem and if you have time, it would be great to verify the test results as well as #109. |
Thanks for your reply. I have modified the path in 3 yaml files named "test_config","train_config" and "xception", but the error is still there. According to the traceback, I checked the file "trainer.py" to see if the path used in this file was wrong, but the outcome shows the path was correct. I can't figure out why there's still a image loading error. I wonder if there's a specific yaml file I haven't change? What I have done is as follows:
The full error message is given below. I will try to run the code in another server later. |
I guess the issue lies with the |
So weird, I use a print function in the function you've mentioned to see if the path file was wrong. The outcome shows the path is right 🤔. I'll try to run the code in another server later, hope I can't get the same error. |
This problem is obvious, because you set |
Thanks a lot for your help!!! It's running nomally. I'll continue to get the result and verify the test results as well as #109 |
I was wondering if you've been able to replicate the results from the paper. I‘am looking forward to your reply. |
I'm trying tu run the code in the Readme segment 5 traning "python training/train.py \ --detector_path ./training/config/detector/xception.yaml". But here comes the loading image error. I think maybe I set the wrong direction to the data set but I don't know which.
The text was updated successfully, but these errors were encountered: