Setting real range after data type conversion

This change is designed to fix a bug in minctracc which occurs when
using mutual information (-mi), in which the thresholds are interpreted
in the byte range rather than the real range. Setting the real range
after converstion in this function should solve that problem.
Merge pull request #2 from dallascard/master

Small fix to deal with a bug in minctracc