Skip to content

ComputeDVARSOutputSpec instance must be a float #1795

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
Closed
oesteban opened this issue Feb 2, 2017 · 1 comment
Closed

ComputeDVARSOutputSpec instance must be a float #1795

oesteban opened this issue Feb 2, 2017 · 1 comment
Assignees
@oesteban
Labels
bug

Comments

@oesteban
Copy link
Contributor

oesteban commented Feb 2, 2017 •
edited
Loading

Summary

Using uncompressed nifti, nibabel opens up the images as memmap objects

Actual behavior

A trait error is raised because the value is not purely float

Expected behavior

The trait successfully accepts a float

How to replicate the behavior

Calling ComputeDVARS with an uncompressed nifti

Platform details:

Only happens with nipype<1.12.0
Any platform

Please see nipreps/mriqc#356
@oesteban oesteban added the bug label Feb 2, 2017
@oesteban oesteban self-assigned this Feb 2, 2017
@oesteban oesteban mentioned this issue Feb 2, 2017
Closed
@oesteban
Copy link
Contributor Author

oesteban commented Feb 2, 2017

I've been playing around this, and the only safe solution I can come up with is requesting nipype>=1.12.0

WDYT @satra , @chrisfilo ?

oesteban added a commit to oesteban/nipype that referenced this issue Feb 2, 2017
@oesteban
Do not open nifti files with mmap if numpy < 1.12.0
7cbe9df 
Fixes nipy#1795
@oesteban oesteban mentioned this issue Feb 2, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@oesteban oesteban

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@oesteban