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

Relight CLI not working #76

Open
DanchGit opened this issue Jul 28, 2024 · 4 comments
Open

Relight CLI not working #76

DanchGit opened this issue Jul 28, 2024 · 4 comments

Comments

@DanchGit
Copy link

Hello,

I am trying to use the function relight-cli, but it does not detect the lp file, even when there is one. I have double checked the folder address. Am I doing something wrong?

I am attaching images of the error I am getting, as well as my folder.

Thank you!

relight cli not working 1
relight cli not working 2

@ponchio
Copy link
Contributor

ponchio commented Jul 28, 2024

Hi,
I do not have a windows machine, it is possible the problem is related to way the path is written.

Could you cd to the "output test" folder and call (with the full path) the executable like this:

/relight-cli ./

And see what if it is working?

@DanchGit
Copy link
Author

Hello, I tried this but it doesn't help.

I tried doing a cd to the output folder and a cd to the input folder with the lp file and images, but neither worked.

I have also tried this on two separate Windows devices.

@ponchio
Copy link
Contributor

ponchio commented Jul 30, 2024

I have added a couple of error checks in the last commit, since I cannot replicate the issue on Linux.
You can download the executable from the actions page, here, at the bottom: https://github.com/cnr-isti-vclab/relight/actions/runs/10163918613

Would you test again?

I have problems getting someone to test this on windows, as everybody is on vacation here.

@DanchGit
Copy link
Author

Hello,

Thanks for your quick responses even during vacation time! I switched to Linux because I am working on a strict deadline, and everything works fine there.

However, one potential issue could be that instead of mentioning the input path first, it should have been the output path mentioned first in the command.

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