afni.nimh.nih.gov

Hi-

The issue has now been resolved; it was an oversight on my part when the insets had brick scaling factors (which are often used for short/byte insets). Now, none of the byte or short inputs lead to crashes, and the byte, short and float insets all give identical output.

In the next build (on/after April 27, 2015), 3dROIMaker should be good to go on byte/short/float insets with/without brick scaling factors-- please let me know if it isn't!

--pt