Print

Print
Hi,

Thanks for this offer. This might be helpfull since I did not manage to run the whole analysis yet und try to track down the Problem. I run FSL on machines with CentOS 5.3 64bit.

wolf


Matthew Webster wrote:
[log in to unmask]" type="cite">Hello,
          This error message may be due to a different flameo bug that we have recently fixed in our internal builds. If you let me know which architecture you are using I can send you a test-version of the current internal flameo?

Many Regards

Matthew

Hi,

I had a problem with  a higher level analysis:
An exception has been thrown
Runtime error:- detected by Newmat: matrix is singular
Searching the mailing list gave me a possible solution, that this could happen, if the mask includes voxels in the filtered_func_data 4D file with all zeros. In a post about a year ago it was stated that this problem is solved with a new FSL version. However, recently there was a comparable discussion with the result that the mask should not include voxels with all zero. So, is it still a problem when the mask includes zero-voxels? If so, what is the best trick to avoid the creation of a mask as preparatory step in the higher level analysis and instead use an alternative a mask similar as one can do in the first level analysis at the end of the .fsf-file? So far I copied a custom made mask into the gfeat-directory at the beginning of the analysis and made sure that it is write protected. Did work fine until today...

Thanks for the help,
wolf