Skip to content

[ENH] Use indexed_gzip with nibabel #788

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

Merged
merged 2 commits into from
Oct 25, 2017
Merged

Conversation

oesteban
Copy link
Member

This PR implements this suggestion #766 (comment)

If we find this useful, it is worth considering to add a new nipype config that leverages indexed_gzip with nibabel.

Hopefully, this is the last piece of several PRs to fix #766

This PR implements this suggestion nipreps#766 (comment)

If we find this useful, it is worth considering to add a new nipype config that leverages indexed_gzip with nibabel.

Hopefully, this is the last piece of several PRs to fix nipreps#766
import nibabel
nibabel.arrayproxy.KEEP_FILE_OPEN_DEFAULT = 'auto'
except ImportError:
pass
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can just do nibabel.arrayproxy.KEEP_FILE_OPEN_DEFAULT = 'auto', without checking imports. All that does is set the default to "use indexed_gzip if available, otherwise don't change behavior".

fmriprep/info.py Outdated
@@ -71,6 +71,7 @@
'statsmodels',
'nipype',
'seaborn',
'indexed_gzip',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

indexed_gzip>=0.6.1

You can get a slowdown on some operations with 0.6.0 or earlier.

@oesteban oesteban merged commit 1d4f501 into nipreps:master Oct 25, 2017
@oesteban oesteban deleted the fix/766 branch October 25, 2017 02:27
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 this pull request may close these issues.

Memory errors
2 participants