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

Testing of the model #41

Closed
build2create opened this issue Sep 28, 2017 · 2 comments · Fixed by #25
Closed

Testing of the model #41

build2create opened this issue Sep 28, 2017 · 2 comments · Fixed by #25

Comments

@build2create
Copy link

Hello @ellisdg Can you provide some inputs on how to view prediction.nii.gz that is generated after testing. Also please explain what is multi-class classification is doing exactly? I guess it is producing the label map but when I see the image in ITK Snap I can see only red aand green patches in the image. Any help in this regard is greatly appreciated.

@ellisdg
Copy link
Owner

ellisdg commented Oct 13, 2017

Did you train your model to predict multiple classes?

@build2create
Copy link
Author

build2create commented Oct 15, 2017

Yes we did the training with the exact same code you last committed. Also changed config file n_labels=4

ellisdg added a commit that referenced this issue Nov 18, 2017
1) Uses SimpleITK if N4BiasFieldCorrection cannot be found by nipype (closes #52 & closes #32).
2) Adds predict.py file that uses the trained model and writes the predicted labels to file (closes #51). The predictions are now multi-label (closes #41 & closes #36).
3) Fixes relative import (closes #49).
4) Removes "pickable" flag from training which fixes and closes #47.
5) Adds batch normalization option (closes #39).
6) Adds option to use patch training. This is will substantially reduce the memory requirement for training.
7) Updates README. Links to data that do not require registration (closes #37).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants