forked from HastingsGreer/InverseConsistency
-
Notifications
You must be signed in to change notification settings - Fork 9
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
GradICON and ICON loss without using network wrapper #79
Comments
@HastingsGreer : Here is my attempt at it, you can see if the logic makes sense and matches the original implementation. I have used the same helper functions.
|
Hi @iyerkrithika21 , I have created standalone ICON and GradICON losses in PR #80 . I hope it will also help. :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am interested in calculating the GradICON and ICON loss for a network I am working on, and it does not follow the typical registration workflow with two input images and predicting the deformation fields, so I cannot use
InverseConsistentNet
orGradientICON
orGradientICONSparse.
Unfortunately, I cannot share my code.Is it possible to provide a standalone loss function that calculates the losses, given two deformation field matrices (equivalent to your
phi_AB.vectorfield
andphi_BA.vectorfield
variables?Also, could you briefly explain the format of the GradICON output? I am confused about the use of
phi_AB
as a function vs. the actual deformation field in the image coordinates.Thank you!
The text was updated successfully, but these errors were encountered: