al.jayasek...@wustl.edu>>
Date: Friday, April 5, 2019 at 5:20 PM
To: Matt Glasser mailto:glass...@wustl.edu>>,
"hcp-users@humanconnectome.org<mailto:hcp-users@humanconnectome.org>"
mailto:hcp-users@humanconnectome.org>>
Subject: Re: [HCP-Users] nu_correct: crashed whi
hington University in St. Louis<https://wustl.edu/>
From: Glasser, Matthew
Sent: Friday, April 5, 2019 5:19:49 PM
To: Jayasekera, Dinal; hcp-users@humanconnectome.org
Subject: Re: [HCP-Users] nu_correct: crashed while running nu_evaluate
What OS are you
sers@humanconnectome.org>>
Subject: Re: [HCP-Users] nu_correct: crashed while running nu_evaluate
Interestingly I had set the path to Freesurfer v6, but the script was calling
on Freesurfer 5.3.0-HCP. After deleting the Freesurfer 5.3.0-HCP folder, the
attached log file showed t
@humanconnectome.org<mailto:hcp-users@humanconnectome.org>"
mailto:hcp-users@humanconnectome.org>>
Subject: Re: [HCP-Users] nu_correct: crashed while running nu_evaluate
Yes I am
Kind regards,
Dinal Jayasekera<https://dinaljay.weebly.com/>
PhD Candidate | InSITE Fellow<https://w
ectome.org>"
mailto:hcp-users@humanconnectome.org>>
Subject: Re: [HCP-Users] nu_correct: crashed while running nu_evaluate
Yes I am
Kind regards,
Dinal Jayasekera<https://dinaljay.weebly.com/>
PhD Candidate | InSITE Fellow<https://www.insitefellows.org/>
Amma
hington University in St. Louis<https://wustl.edu/>
From: Glasser, Matthew
Sent: Thursday, April 4, 2019 3:01:18 PM
To: Jayasekera, Dinal; hcp-users@humanconnectome.org
Subject: Re: [HCP-Users] nu_correct: crashed while running nu_evaluate
Are you usin
ectome.org>"
mailto:hcp-users@humanconnectome.org>>
Subject: [HCP-Users] nu_correct: crashed while running nu_evaluate
Dear all,
I have been running the FreeSurferPipelineBatch script (v4 of the HCP pipeline)
and I'm getting an error saying that nu_correct: crashed while runnin
Dear all,
I have been running the FreeSurferPipelineBatch script (v4 of the HCP pipeline)
and I'm getting an error saying that nu_correct: crashed while running
nu_evaluate. I didn't encounter this same issue with the previous version of
the pipeline script. I've attached the recon-all.log
