Hi Bruce,
Is that the reason why >10GB of disk space is consumed? I hope that it is possible to limit the amount of this type of output by some means to prevent the problem I ran into.
Cheers and good luck with improving v6.
Ed
On 10 Mar 2016, at 19:22, freesurfer-request@nmr.mgh.harvard.edumailto:freesurfer-request@nmr.mgh.harvard.edu wrote:
Hi Ed,
the problem is that you have a defect that has >40K vertices - about 1/3 the total size of a typical hemi. 6.0 when it is out will complete for this kind of thing but even it is unlikely to generate an accurate surface with that big a defect. You should try down the source of it and fix it then rerun.
cheers Bruce
On Thu, 10 Mar 2016, Gronenschild Ed (NP) wrote:
Hi Bruce, Here it is
Cheers, Ed
not sure, but maybe. Try tracking it down and seeing why you have such a huge defect. There's no easy way for us to stop this from happening other than detecting a memory allocation failure
On Thu, 10 Mar 2016, Gronenschild Ed (NP) wrote:
Hi Bruce, Is that the reason why >10GB of disk space is consumed? I hope that it is possible to limit the amount of this type of output by some means to prevent the problem I ran into.
Cheers and good luck with improving v6.
Ed
On 10 Mar 2016, at 19:22, freesurfer-request@nmr.mgh.harvard.edu wrote:
Hi Ed, the problem is that you have a defect that has >40K vertices - about 1/3 the total size of a typical hemi. 6.0 when it is out will complete for this kind of thing but even it is unlikely to generate an accurate surface with that big a defect. You should try down the source of it and fix it then rerun. cheers Bruce On Thu, 10 Mar 2016, Gronenschild Ed (NP) wrote: Hi Bruce, Here it is Cheers, Ed
What is it that is actually consuming the disk space? Is it the log file? Or is there a temp file?
On 03/10/2016 02:25 PM, Bruce Fischl wrote:
not sure, but maybe. Try tracking it down and seeing why you have such a huge defect. There's no easy way for us to stop this from happening other than detecting a memory allocation failure
On Thu, 10 Mar 2016, Gronenschild Ed (NP) wrote:
Hi Bruce, Is that the reason why >10GB of disk space is consumed? I hope that it is possible to limit the amount of this type of output by some means to prevent the problem I ran into.
Cheers and good luck with improving v6.
Ed
On 10 Mar 2016, at 19:22, freesurfer-request@nmr.mgh.harvard.edu wrote:
Hi Ed, the problem is that you have a defect that has >40K vertices - about 1/3 the total size of a typical hemi. 6.0 when it is out will complete for this kind of thing but even it is unlikely to generate an accurate surface with that big a defect. You should try down the source of it and fix it then rerun. cheers Bruce On Thu, 10 Mar 2016, Gronenschild Ed (NP) wrote: Hi Bruce, Here it is Cheers, Ed
Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
freesurfer@nmr.mgh.harvard.edu
-
Bruce Fischl -
Douglas N Greve -
Gronenschild Ed (NP)