# Interval package

The interval package provides data types and fundamental operations for real valued interval arithmetic based on the common floating-point format “binary64” a. k. a. double-precision. **Interval arithmetic** produces mathematically proven numerical results. It aims to be standard compliant with the (upcoming) IEEE 1788 and therefore implements the *set-based* interval arithmetic flavor.

Warning: The package has not yet been released.

## Motivation

Give a digital computer a problem in arithmetic, and it will grind away methodically, tirelessly, at gigahertz speed, until ultimately it produces the wrong answer. … An interval computation yields a pair of numbers, an upper and a lower bound, which are guaranteed to enclose the exact answer. Maybe you still don’t know the truth, but at least you know how much you don’t know.—Brian Hayes, DOI: 10.1511/2003.6.484

Standard floating point arithmetic | Interval arithmetic |
---|---|

octave:1> 19 * 0.1 - 2 + 0.1 ans = 1.3878e-16 |
octave:1> x = infsup ("0.1"); octave:2> 19 * x - 2 + x ans = [-3.1918911957973251e-16, +1.3877787807814457e-16] |

Floating point arithmetic, as specified by IEEE 754, is available in almost every computer system today. It is wide-spread, implemented in common hardware and integral part in programming languages. For example, the extended precision format is the default numeric data type in GNU Octave. Benefits are obvious: The performance of arithmetic operations is well-defined, highly efficient and results are comparable between different systems.

However, there are some downsides of floating point arithmetic in practice, which will eventually produce errors in computations.

- Floating point arithmetic is often used mindlessly by developers. [1]
- The binary data types categorically are not suitable for doing financial computations. Very often representational errors are introduced when using “real world” decimal numbers.
- Even if the developer would be proficient, most developing environments / technologies limit floating point arithmetic capabilities to a very limited subset of IEEE 754: Only one or two data types, no rounding modes, …
- Results are hardly predictable. All operations produce the best possible accuracy
*at runtime*, this is how floating point works. Contrariwise, financial computer systems typically use a fixed-point arithmetic (COBOL, PL/I, …), where overflow and rounding can be precisely predicted*at compile-time*. - If you do not know the technical details, cf. first bullet, you ignore the fact that the computer lies to you in many situations. For example, when looking at numerical output and the computer says “
`ans = 0.1`

,” this is not absolutely correct. In fact, the value is only*close enough*to the value 0.1.

Interval arithmetic addresses above problems in its very special way and introduces new possibilities for algorithms. For example, the interval newton method is able to find *all* zeros of a particular function.

## Theory

### Moore's fundamental theroem of interval arithmetic

Let * y* =

*f*(

*) be the result of interval-evaluation of*

**x***f*over a box

*= (*

**x***x*

_{1}, … ,

*x*

_{n}) using any interval versions of its component library functions. Then

- In all cases,
contains the range of**y***f*over, that is, the set of**x***f*() at points of**x**where it is defined:**x**⊇ Rge(**y***f*|) = {**x***f*(*x*) |*x*∈∩ Dom(**x***f*) } - If also each library operation in
*f*is everywhere defined on its inputs, while evaluating, then**y***f*is everywhere defined on, that is Dom(**x***f*) ⊇.**x** - If in addition, each library operation in
*f*is everywhere continuous on its inputs, while evaluating, then**y***f*is everywhere continuous on.**x** - If some library operation in
*f*is nowhere defined on its inputs, while evaluating, then**y***f*is nowhere defined on, that is Dom(**x***f*) ∩= Ø.**x**

## Quick start introduction

### Input and output

Before exercising interval arithmetic, interval objects must be created, typically from non-interval data. There are interval constants `empty`

and `entire`

and the class constructors `infsup`

for bare intervals and `infsupdec`

for decorated intervals. The class constructors are very sophisticated and can be used with several kinds of parameters: Interval boundaries can be given by numeric values or string values with decimal numbers. Also it is possible to use so called interval literals with square brackets.

octave:1> infsup (1) ans = [1] octave:2> infsup (1, 2) ans = [1, 2] octave:3> infsup ("3", "4") ans = [3, 4] octave:4> infsup ("1.1") ans = [1.0999999999999998, 1.1000000000000001] octave:5> infsup ("[5, 6.5]") ans = [5, 6.5] octave:6> infsup ("[5.8e-17]") ans = [5.799999999999999e-17, 5.800000000000001e-17]

It is possible to access the exact numeric interval boundaries with the functions `inf`

and `sup`

. The default text representation of intervals can be created with `intervaltotext`

. The default text representation is not guaranteed to be exact (see function `intervaltoexact`

), because this would massively spam console output. For example, the exact text representation of `realmin`

would be over 700 decimal places long! However, the default text representation is correct as it guarantees to contain the actual boundaries and is accurate enough to separate different boundaries.

octave:7> infsup (1, 1 + eps) ans = [1, 1.0000000000000003] octave:8> infsup (1, 1 + 2 * eps) ans = [1, 1.0000000000000005]

Warning: Decimal fractions should always be passed as a string to the constructor. Otherwise it is possible, that GNU Octave introduces conversion errors when the numeric literal is converted into floating-point format **before** it is passed to the constructor.

octave:9> infsup (0.2) ans = [.20000000000000001, .20000000000000002] octave:10> infsup ("0.2") ans = [.19999999999999998, .20000000000000002]

For convenience it is possible to implicitly call the interval constructor during all interval operations if at least one input already is an interval object.

octave:11> infsup ("17.7") + 1 ans = [18.699999999999999, 18.700000000000003] octave:12> ans + "[0, 2]" ans = [18.699999999999999, 20.700000000000003]