I think we wanted to show you this error when you came to Princeton, but couldn't' find any of the problematic ROI files at the time. Plus, I just noticed the difference in the roi list yesterday, so I finally felt I had a grasp on what the issue was related to.

Speaking of roi files and ROI2dataset. When you came to Princeton this past winter, we asked you how to convert .roi to a .dset (using ROI2dataset) in which the output would maintain a column ordering structure based on how an roi was draw (vs. ascending order of nodes).

For example, we want a .dset file to look like this:
5 1
6 1
0 1
3 1
4 1
2 2
1 2
7 0


as opposed to this

0 1
1 2
2 2
3 1
4 1
5 1
6 1
7 0

IF my memory is serving me correctly, you were able to create a dset file (via ROI2dataset) in which the ordering was based upon how you drew the roi (not node order). However, I've been unable to reproduce this on my own.

I've tried saving rois drawn in SUMA under .niml AND .1D, as well as trying out each of the -of options. All yield an output in ascending node order.

Here is the command line I use for ROI2dataset:

ROI2dataset -prefix roi -of 1D -input roi.1D.roi (or roi.niml.roi)


Thanks,
Mike