LUMIERA.clone/src/lib/rational.hpp
Ichthyostega 3b3600379a Library: introduce formating variants for decimal10
showDecimal -> decimal10 (maximal precision to survive round-trip through decimal representation=

showComplete -> max_decimal10 (enough decimal places to capture each possible distinct floating-point value)


Use these new functions to rewrite the format4csv() helper
2024-03-14 17:32:22 +01:00

180 lines
7 KiB
C++

/*
RATIONAL.hpp - support for precise rational arithmetics
Copyright (C) Lumiera.org
2022, Hermann Vosseler <Ichthyostega@web.de>
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of
the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*/
/** @file rational.hpp
** Rational number support, based on `boost::rational`.
** As an extension to integral arithmetics, rational numbers can be defined
** as a pair (numerator, denominator); since most calculations imply multiplication
** by common factors, each calculation will be followed by normalisation to greatest
** common denominator, to keep numbers within value range. Obviously, this incurs
** a significant performance penalty — while on the other hand allowing for lossless
** computations on fractional scales, which can be notoriously difficult to handle
** with floating point numbers. The primary motivation for using this number format
** is for handling fractional time values properly, e.g 1/30 sec or 1/44100 sec.
**
** The underlying implementation from boost::rational can be parametrised with various
** integral data types; since our time handling is based on 64bit integers, we mainly
** use the specialisation `boost::rational<int64_t>`.
**
** @note all compatible integral types can be automatically converted to rational
** numbers, which is a lossless conversion. The opposite is not true: to get
** a "ordinary" number — be it integral or floating point — an explicit
** conversion using `rational_cast<NUM> (fraction)` is necessary, which
** performs the division of `numerator/denominator` in the target value domain.
**
** # Perils of fractional arithmetics
**
** While the always precise results of integral numbers might seem compelling, the
** danger of _numeric overflow_ is significantly increased by fractional computations.
** Most notably, this danger is *not limited to large numbers*. Adding two fractional
** number requires multiplications with both denominators, which can overflow easily.
** Thus, for every given fractional number, there is a class of »dangerous counterparts«
** which can not be added without derailing the computation, leading to arbitrary wrong
** results without detectable failure. And these problematic counterparts are distributed
** _over the whole valid numeric range._ To give an extreme example, any numbers of the
** form `n / INT_MAX` can not be added or subtracted with any other rational number > 1,
** while being themselves perfectly valid and representable.
** \par rule of thumb
** Use fractional arithmetics only where it is possible to control the denominators involved.
** Never use them for computations drawing from arbitrary (external) input.
**
** @see Rational_test
** @see zoom-window.hpp
** @see timevalue.hpp
*/
#ifndef LIB_RATIONAL_H
#define LIB_RATIONAL_H
#include "lib/integral.hpp"
#include "lib/util-quant.hpp"
#include <cmath>
#include <limits>
#include <stdint.h>
#include <boost/rational.hpp>
namespace util {
using Rat = boost::rational<int64_t>;
using boost::rational_cast;
using std::abs;
inline bool
can_represent_Product (int64_t a, int64_t b)
{
return ilog2(abs(a))+1
+ ilog2(abs(b))+1
< 63;
}
inline bool
can_represent_Product (Rat a, Rat b)
{
return can_represent_Product(a.numerator(), b.numerator())
and can_represent_Product(a.denominator(), b.denominator());
}
inline bool
can_represent_Sum (Rat a, Rat b)
{
return can_represent_Product(a.numerator(), b.denominator())
and can_represent_Product(b.numerator(), a.denominator());
}
/**
* Re-Quantise a number into a new grid, truncating to the next lower grid point.
* @remark Grid-aligned values can be interpreted as rational numbers (integer fractions),
* where the quantiser corresponds to the denominator and the numerator counts
* the number of grid steps. To work both around precision problems and the
* danger of integer wrap-around, the integer division is performed on the
* old value and then the re-quantisation done on the remainder, using
* 128bit floating point for maximum precision. This operation can
* also be used to re-form a fraction to be cast in terms of the
* new quantiser; this introduces a tiny error, but typically
* allows for safe or simplified calculations.
* @param num the count in old grid-steps (#den) or the numerator
* @param den the old quantiser or the denominator of a fraction
* @param u the new quantiser or the new denominator to use
* @return the adjusted numerator, so that the fraction with u
* will be almost the same than dividing #num by #den
*/
inline int64_t
reQuant (int64_t num, int64_t den, int64_t u)
{
u = 0!=u? u:1;
auto [d,r] = util::iDiv (num, den);
// round to smallest integer fraction, to shake off "number dust"
f128 const ROUND_ULP = 1 + 1/(f128(std::numeric_limits<int64_t>::max()) * 2);
// construct approximation quantised to 1/u
f128 frac = f128(r) / den;
int64_t res = d*u + int64_t(frac*u * ROUND_ULP);
ENSURE (abs (f128(res)/u - rational_cast<f128>(Rat{num,den})) <= 1.0/abs(u)
,"Requantisation error exceeded num=%li / den=%li -> res=%li / quant=%li"
, num, den, res, u);
return res;
}
/**
* re-Quantise a rational number to a (typically smaller) denominator.
* @param u the new denominator to use
* @warning this is a lossy operation and possibly introduces an error
* of up to 1/u
* @remark Rational numbers with large numerators can be »poisonous«,
* causing numeric overflow when used, even just additively.
* This function can thus be used to _"sanitise"_ a number,
* and thus accept a small error while preventing overflow.
* @note using extended-precision floating point to get close to the
* quantiser even for large denominator. Some platforms
* fall back to double, leading to extended error bounds
*/
inline Rat
reQuant (Rat src, int64_t u)
{
return Rat{reQuant (src.numerator(), src.denominator(), u), u};
}
} // namespace util
/**
* user defined literal for constant rational numbers.
* \code
* Rat twoThirds = 2_r/3;
* \endcode
*/
inline util::Rat
operator""_r (unsigned long long num)
{
return util::Rat{num};
}
#endif /*LIB_RATIONAL_H*/