This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients mark.dickinson, nirinA, rhettinger, stutzbach, terry.reedy
Date 2008-07-22.01:12:36
SpamBayes Score 0.09440599
Marked as misclassified No
Message-id <>
It would be nice if we knew the error bounds for each of the 
approximation methods. Do we know how the coefficients were generated?

When switching from one method to another, it might be nice to have a 
range where the results slowly blend from one method to another:
  if x < a: return f1(x)
  if x > b: return f2(x)
  t = (x - a) / (b - a)
  return (1-t)*f1(x) + t*f2(x)
This minimizes discontinuities in the first and second derivatives.

The lowword/highword macros look to be tightly tied to the internal 
processor representation for floats.  It would be more portable and 
maintainable to replace that bit twiddling with something based on frexp
Date User Action Args
2008-07-22 01:12:43rhettingersetspambayes_score: 0.094406 -> 0.09440599
recipients: + rhettinger, terry.reedy, mark.dickinson, stutzbach, nirinA
2008-07-22 01:12:42rhettingersetspambayes_score: 0.094406 -> 0.094406
messageid: <>
2008-07-22 01:12:41rhettingerlinkissue3366 messages
2008-07-22 01:12:37rhettingercreate