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.

Sign up for GitHub

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

Jump to bottom

Make dti reconst less memory hungry #840

Closed
wants to merge 1 commit into from
Closed

Make dti reconst less memory hungry #840

wants to merge 1 commit into from

Commits on Jan 19, 2016

  1. Make dti reconst less memory hungry 

    Since the change to vectorized operation, it processes 1000 voxels by default instead of 1. While faster, it's also memory hungry (with the first version causing out of memory on simple datasets). Following the computing tracks as f32, here is a computing eigenvalues as f64, but returning them as f32 change. 

My plain normal dti script was using 12 go of ram on an hcp dataset (and something swapping), so this change should reduce the memory usage. It should also downgrade computed metrics to f32 precision, but as long as only the end result is returned as f32 everything should behave fine I recon.
    @samuelstjean
    samuelstjean committed Jan 19, 2016
    Configuration menu
    Copy the full SHA
    b852776 View commit details
    Browse the repository at this point in the history