-
Notifications
You must be signed in to change notification settings - Fork 18
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
Structure creation on GPU #175
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, after the adapter is done with the volume creation, the space on the GPU that was needed for all the tensors is not freed again. The memory is still allocated until the whole script is ended. Only then, is it freed up again.
…mory, moved to function instead
…served GPU memory
I'm not calling I've also fixed a bug in the vessel structure caused by random variable drawing. This only occurred in random occasions that's probably why it wasn't detected before. |
Signed-off-by: Kris Dreher <k.dreher@dkfz-heidelberg.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me
closes #166 |
Solves issue #166
The structures are now created using PyTorch instead of NumPy. Therefore, the input values were converted into torch tensors with float32 precision. NB: NumPys default precision was float64.
For compatibility reasons each structure generator still returns a Numpy array.
Depending on the user settings and hardware availability processing is done on GPU or CPU, as described in #169