-
Notifications
You must be signed in to change notification settings - Fork 243
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
I can´t find the rendered file #1292
Comments
Hi @alecail I'm not sure what is happening. Is that the full eror log you've provided? I would have expected to see an error message, or at least the error code in it too. Is there a filesystem permission issue maybe? Can you create new files in the folder where you're running The other option that comes to mind is some illegal instruction being executed on your CPU. We've seen weird behavior in the past with Xeon CPUs, and the part of the code that develops the final image can potentially use some very specific instructions. |
There is no filesystem issue. It's just your standard folder, in which I copied scene.xml. Local install, nothing fancy.
python3 test.py
Then a rendering of a Cornell box is written in the file cbox.exr I can ´t find anything about: jit_llvm_init(): your CPU does not support the |
In the python script, could you try replacing These are slighlty different code paths, and the latter one is used by |
@njroussel This doesn't break test.py on my end |
I'm stumped, my only suggestion would be to build the project yourself (be careful to checkout |
Maybe an issue with the struct converter for that particular CPU generation? What if you build from source, but explicitly set |
Summary
I can´t find the rendered file
System configuration
I am using python3.
System information:
Description
I downloaded the Cornell box from here: https://mitsuba.readthedocs.io/en/stable/src/gallery.html
After this command line finished executing:
$ mitsuba scene.xml -o out.exr
I don't have a file named out.exr at the end of the process.
The error code is 252 according to my terminal
Steps to reproduce
The text was updated successfully, but these errors were encountered: