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

"There should be a folder "supervisely" at /home/myName/supervisely_yolo\" #4

Open
kitsiosvas opened this issue Oct 1, 2021 · 4 comments

Comments

@kitsiosvas
Copy link

kitsiosvas commented Oct 1, 2021

I am trying to run the examples (both supervisely_to_yolo and reverse) and I get this error. I have copied of course the files from the example/ directory into the root, but this error still persists. One thing that is weird the the "" character at the end of the path name in the error message. My path is /home/myName/supervisely_yolo/...
The contents of this directory are :
~/supervisely_yolo$ dir
output: examples LICENSE README.md supervisely supervisely_yolo.py yolo
So as you can see, the two files (supervisely and yolo) are in the root directory.
That said, when running python3 supervisely_yolo.py It returns:
Error [meta.json not found] => There should be a folder "supervisely" at /home/myName/supervisely_yolo\

Any thoughts on this issue?

@Delilovic
Copy link
Owner

Hello!

What OS are you using? I only tested the script on Windows.

@kitsiosvas
Copy link
Author

kitsiosvas commented Oct 1, 2021 via email

@Delilovic
Copy link
Owner

Delilovic commented Oct 1, 2021

As expected, it has something to do with how paths are managed in Windows (where I tested the script) and Linux. Just replace any \\ with / in supervisely_yolo.py and it should work (you can use any text editor for that). If you want, you can also commit this change and I will accept it since it works on Windows, even after replacing it.

Let me know if it works.

Kind Regards

@kitsiosvas
Copy link
Author

kitsiosvas commented Oct 3, 2021

Greeting, apologies for my late reply. I did as you said, and it seems to work correctly now. Thanks for your help. Will commit the new file as suggested when I get the chance.

@kitsiosvas kitsiosvas reopened this Oct 3, 2021
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