Hi Saad,
>Did you manage to run tbss_3_postreg on the same data? It should have
>taken more or less he same amount of RAM as tbss_non_FA...
When I try with 20 patients study, I don't see this problem in
tbss_3_postgress..but the machine worked to night!!!
>I suppose you could split your group into 3 parts for tbss_non_FA.
Yes!!! In few minutes the memory is full!!!
>For each subgroup, tbss_non_FA will produce a file called
all_<something>_skeleton.These >files should be less memory demanding than
the all_<something> files, so you should be >able to merge them afterwards
when you get to doing the stats.
Ok, I can try it!
cheers,
Eddy
|