¥Why not use to3d directly to create AFNI datasets?
HEPI images collected
using GEÕs real time EPI sequence are saved in a peculiar fashion
åOnly
999 image files can be stored in a single directory
åIf a
run consists of 110 volumes of 27 slices each, we have 2970 image files
åWith a
limit of 999 I.* files per directory,
a run made up of 2970 images would have to be saved in 3 separate directories (numbered 001/,
021/, and 041/):
íE.g., 001/I.028ÉI.999 + 021/I.001ÉI.999 + 041/I.001ÉI.999 = 2970 I.* files total
åThe
second run would be stored in directories 061/I.001
Þ 101/I.973,
the third run in 101/I.974
Þ 161/I.946,
and the nightmare continuesÉ
åThis
setup already makes it difficult to delineate between runs. Now image what happens if the scanner hiccups, if you stop a scan in
the middle and start a new one, or start collecting scans with a different number
of slices!
¥Imon attempts to
identify complete scans from the images in those directories. It also monitors missing
or out-of-order images, and generates the commands necessary to turn them
into AFNI bricks using the script GERT_Reco2