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

xfm2tag unsafely assumes image and mask coordinates are the same #29

Open
bcdarwin opened this issue Aug 5, 2016 · 1 comment
Open
Labels

Comments

@bcdarwin
Copy link
Member

bcdarwin commented Aug 5, 2016

See here and here.

Arguably the real culprit here is C: get_volume_real_value exhibits undefined behaviour when fed garbage voxel indices. I found this bug in a pipeline where xfm2tag was segfaulting, but the same user has used the same combination of initial model (which determines the resolution of the output images) and different-resolution mask (which is used in the xfm2tag call) before and didn't get any errors, although it's possible tag points were not generated as a result ...

@bcdarwin bcdarwin added the bug label Aug 5, 2016
@gdevenyi
Copy link

gdevenyi commented Aug 6, 2016

I think I got bitten before by different resolutions of masks and atlases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants