Is there anyway to constrain optimize.fmin to use single precision or even fewer digits in its internal calculations? I am trying to show that one approach to a problem is less prone to round off errors than another approach, but the results aren't all that dramatic with double precision numbers. Thanks, Ryan