Closed oricon closed 6 years ago
Thanks for lettinge know. Will debug today.
We think we fixed everything with the 2.0.4-alpha version.
Hi the install works without a problem, but now I run into an error with niio in ciftify_subject_fmri when it gets to the Subcortical Processing:
Traceback (most recent call last):
File "/apps/psyc/ciftify/2.0.4/ciftify/bin/ciftify_subject_fmri", line 1062, in
VolumefMRI: /fdata/scratch/joseph.orr/adaptcog/fmri/hcp/sub-M80301092/MNINonLinear/Results/task-ritl_acq-MB_run-01/task-ritl_acq-MB_run-01.nii.gz
oops sorry. It looks like the final bug fixes were not included in the 2.0.4 release. 2.0.5 has been pushed.
On Sat, Jun 23, 2018 at 5:09 PM, Joseph M. Orr notifications@github.com wrote:
Hi the install works without a problem, but now I run into an error with niio in ciftify_subject_fmri when it gets to the Subcortical Processing:
Traceback (most recent call last): File "/apps/psyc/ciftify/2.0.4/ciftify/bin/ciftify_subject_fmri", line 1062, in main() File "/apps/psyc/ciftify/2.0.4/ciftify/bin/ciftify_subject_fmri", line 1057, in main ret = run_ciftify_subject_fmri(settings, tmpdir) File "/apps/psyc/ciftify/2.0.4/ciftify/bin/ciftify_subject_fmri", line 190, in run_ciftify_subject_fmri tmpdir) File "/apps/psyc/ciftify/2.0.4/ciftify/bin/ciftify_subject_fmri", line 893, in subcortical_atlas func_vx_size = ciftify.niio.voxel_spacing(input_fMRI) AttributeError: module 'ciftify' has no attribute 'niio' Here's the last line of the ciftify_subject_fmri.log: 2018-06-23 15:53:57.789319 : Subcortical Processing
VolumefMRI: /fdata/scratch/joseph.orr/adaptcog/fmri/hcp/sub- M80301092/MNINonLinear/Results/task-ritl_acq-MB_run- 01/task-ritl_acq-MB_run-01.nii.gz
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/edickie/ciftify/issues/66#issuecomment-399710810, or mute the thread https://github.com/notifications/unsubscribe-auth/AMl59pDIeWdfRRyoQyRFdism52dPSJGZks5t_q5_gaJpZM4Usx09 .
Looks like this bug is fixed, thanks!
I think there might be a bug in the latest update. I tried installed the update with pip but there was an error. (I replicated the problem on another computer with Python 3.6.5)
So I did a manual install and still have an issue running commands: