Dear Tanja,
I have had a quick look and I can't find any obvious limitations. It's all pretty much dynamic.
I have never seen what you describe in the data we process, which is typically 576 volumes. The screen prints you attached don't really help.
Potentially more useful would be if we knew the mapping, i.e. a list of where at least the b=0 files were expected to be and where they ended up.
Jesper
On 2 Apr 2013, at 16:22, Tanja Kassuba wrote:
> Hi Jesper,
>
> I would like to catch up on my last thread (see below). To summarize again, I have a data set with 4 sets of 256 directions, 2 of each opposing phase encoding direction. If I run eddy with the --topup option on the whole data set (see http://dl.dropbox.com/u/18433894/eddy_whole_data ), eddy screws up the image order in the second half of the data (i.e. the B0s are not at the positions where they should be within the output data set). If I run eddy on just half that data (i.e., first opposing pair, see http://dl.dropbox.com/u/18433894/eddy_1st_half , or second opposing pair, see http://dl.dropbox.com/u/18433894/eddy_2nd_half) it works fine. Any idea what is happening? I wonder if there is a limitation on how much data eddy can process at once?
>
> Cheers and thanks,
> Tanja
>
|