Hi Mike the ones I would be careful of are the PRETESS_FILL ones. The others are more heuristics to avoid topological problems.
cheers Bruce On Tue, 13 Mar 2012, Michael Harms wrote: > > Is there any practical relevance/concern to deleting DIAGONAL_FILL > values (or any of the other classes) if needed to open up a path to an > area of gray matter that was otherwise closed off? > > thanks, > -MH > > On Tue, 2012-03-13 at 13:56 -0400, Bruce Fischl wrote: >> Hi Mike >> >> they are in mri.h if you have a source distribution: >> >> #define THICKEN_FILL 200 >> #define NBHD_FILL 210 >> #define VENTRICLE_FILL 220 >> #define DIAGONAL_FILL 230 >> #define DEGENERATE_FILL 240 >> #define OFFSET_FILTER_FILL 245 >> #define AUTO_FILL 250 >> #define PRETESS_FILL 215 >> #define WM_EDITED_ON_VAL 255 >> #define WM_EDITED_OFF_VAL 1 >> >> On Tue, 13 Mar 2012, >> Michael Harms wrote: >> >>> >>> Hello, >>> Is there a "key" for what all the various altered voxel values in wm.mgz >>> represent? For example, I know that if you manually add a voxel, it >>> gets set to 255, and if you delete a voxel it gets set to 1. >>> >>> What is the analogous "key" for values of 200, 215, 230, and 250? >>> >>> thanks, >>> -MH >>> >>> >>> >> >> >> The information in this e-mail is intended only for the person to whom it is >> addressed. If you believe this e-mail was sent to you in error and the e-mail >> contains patient information, please contact the Partners Compliance >> HelpLine at >> http://www.partners.org/complianceline . If the e-mail was sent to you in >> error >> but does not contain patient information, please contact the sender and >> properly >> dispose of the e-mail. > > > _______________________________________________ Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
