-
Notifications
You must be signed in to change notification settings - Fork 3
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
ray_trace fails when built using O2 or O3 optimization #3
Comments
Hi @antoimau to clarify, are you getting the proper outputs from ray_trace, but its returning a bad return code? |
Also, can you please specify the version of minc-toolkit you're using, and how you installed it (binary packages or build from source) |
Hello @gdevenyi, No Thank you for your answer. |
The example files you uploaded (obj{1..3}.obj and vol_noise.mnc) are completely empty. In fact, obj2 and obj3 are zero-size. Perhaps this is the origin if your issues. |
Hello, Yeah, it is something we noticed but it does not seem to be the issue. Indeed, I haven't realized I provided an empty volume. I attach here a new Concerning the empty files: files_for_community.zip Thank you for your help |
Can you reproduce these with valid volumes and obj files? |
Hello,
We noticed that in some cases, ray_trace exits with non-zero status when it's compiled with
-O3
or-O2
, and exits with zero status with the same data when compiled with-O1
Here is the problematic call:
We attached a zip folder in which we put the input data we used for the previous call.
Files: data_for_community.zip
Let me know if you have any questions,
Best,
Antoine
The text was updated successfully, but these errors were encountered: