I would not guess that it is a RAM issue. More likely, there is a problem w/ the registrations for some subjects (assuming you provided probtrack with seed regions in a different space than diffusion space). Or, it could just be that some subjects have "less connectivity" than others, whatever that may mean. It depends on what you mean by "lots of zeros", as well.
________________________________________
From: FSL - FMRIB's Software Library [[log in to unmask]] on behalf of Ehsan [[log in to unmask]]
Sent: Monday, August 31, 2015 6:31 PM
To: [log in to unmask]
Subject: [FSL] Check Probtrackx outputs
Dear FSL experts,
I have run probtrackx on a few subjects using a cluster. It seems that for a few subjects, the output matrix contains lots of zeros in comparison to other subjects. However the log files do not report any problems. I think it's probably due to huge amount of RAM that probtrackx requires during the process. Since I have run multiple subjects simultaneously, there is a great chance that it might causes the problem. I was wondering what the best way is to check probtrackx outputs. Is there any way to tell whether one output is corrupted although no errors have been reported in the log files?
thanks in advance for your help
Best,
Ehsan.
|