edickie / ciftify

The tools of the Human Connectome Project (HCP) adapted for working with non-HCP datasets
https://edickie.github.io/ciftify/
MIT License
112 stars 158 forks source link

Error in ciftify_subject_fmri with --func-ref option #65

Closed NeuroImagingWorld closed 6 years ago

NeuroImagingWorld commented 6 years ago

File "${CODEPATH}/ciftify/bin/ciftify_subject_fmri.py", line 522, in define_func_3D cifify.meants.verify_nifti_dimensions_match(settings.ref_vol.path, NameError: name 'cifify' is not defined

After correcting the typo, running into below issue

ciftify.meants.verify_nifti_dimensions_match(settings.ref_vol.path, AttributeError: 'Settings' object has no attribute 'ref_vol'

Here is the command that is used

ciftify_subject_fmri --surf-reg FS --ciftify-work-dir ${PROCESSDIR} --FLIRT-to-T1w --func-ref ${DATAPATH}/fmri_map1.nii.gz fmri_mapAll.nii.gz SUBJECT mapname

Please assist if you see any issue in the usage

Thanks

edickie commented 6 years ago

Looks like a bug on my end.. will debug ASAP

On Sun, Jun 17, 2018 at 1:42 PM, NeuroImagingWorld <notifications@github.com

wrote:

File "${CODEPATH}/ciftify/bin/ciftify_subject_fmri.py", line 522, in define_func_3D cifify.meants.verify_nifti_dimensions_match(settings.ref_vol.path, NameError: name 'cifify' is not defined

After correcting the typo, running into below issue

ciftify.meants.verify_nifti_dimensions_match(settings.ref_vol.path, AttributeError: 'Settings' object has no attribute 'ref_vol'

Here is the command that is used

ciftify_subject_fmri --surf-reg FS --ciftify-work-dir ${PROCESSDIR} --FLIRT-to-T1w --func-ref ${DATAPATH}/fmri_map1.nii.gz fmri_mapAll.nii.gz SUBJECT mapname

Please assist if you see any issue in the usage

Thanks

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/edickie/ciftify/issues/65, or mute the thread https://github.com/notifications/unsubscribe-auth/AMl59lX2X8gKXn5vo7Q1QBxHcxKGvcl-ks5t9pT4gaJpZM4Uq6Yv .

edickie commented 6 years ago

Bug fixed. It should be fine with version 2.0.3