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
pytorch bindings #508
base: master
Are you sure you want to change the base?
pytorch bindings #508
Conversation
Thanks @Emvlt , I'll have a look. AFAIK: 2D works, 3D crashes. |
So, the crash only happens when forward is called a second time. I can compute a first forward pass exactly the way it should be, but the second call always crashes in 3D. The problematic line is |
I am a bit confused on the different way you tread the 3D version and the 2D version, can you explain further? In TIGRE, there is no 2D operators, there are only 3D operators that can take 3 rd dimension == 1, so a priori, there is no need to change anything in the way you call Ax(). Would it not make it easier to treat these the same way? i.e. always assume you get a 3D tensor (+batch) as input. This makes it 4D for the THREE_D image case right? why do you have 5D sometimes in the THREE_D case? |
Maybe its because of #509 |
…iscrepancy minimisation and 2D lpd training on MNIST; known bug on 3D=breaks at second call of A
…nd backward in OperatorS.py
This pull request accounts for:
|
Bug appears only in 3D