<div style="float: right; margin: 0 3em">[[ File: Octave-interval. png|center]]</ div>The GNU Octave interval package for real-valued interval arithmetic.
right|Plotting the interval enclosure of a function]]
== Distribution ==
http://octave.sourceforge. net/interval/ index.html Latest version at Octave Forge]
** <code>pkg install -forge interval</code>
http://octave.sourceforge. net/interval/overview.html function reference]** [ http://octave.sourceforge. net/interval/package_doc/index.html package documentation] (user manual)* [https:// trac. macports.org/ browser/ trunk/ dports/math/octave-interval MacPorts] for Mac OS X* [ http://www.freshports.org/math/octave-forge-interval/ FreshPorts] for FreeBSD
== Development status ==
** All required functions from IEEE Std 1788-2015, IEEE standard for interval arithmetic, are implemented. The standard was approved on June 11, 2015. It will remain active for ten years.** In addition there are functions for interval matrix arithmetic, plotting and solvers.
tests for all functions, many tests for basic functions** No known bugs. The package is quite new and still has a small user base, so there might be hidden bugs. Also some advanced functions will always need more testing.
** Runs in GNU Octave 3.8.2
and 4.0.0** Known to run under GNU/Linux, Microsoft Windows, Mac OS X and FreeBSD * Possible TODOs ** To be considered in the future: Algorithms can be migrated from the C-XSC Toolbox (C++ code) from [http://www2.math.uni-wuppertal.de/wrswt/xsc/cxsc_new.html] (nlinsys.cpp and cpzero.cpp), however these would need gradient arithmetic and complex arithmetic. ** Interval version of <code>interp1</code> ** The [http://capd.ii.uj.edu.pl/ CAPD package] contains an algorithm for QR factorization. Analyze. Migrate. ** Extend <code>subsasgn</code> to allow direct manipulation of inf and sup properties.
>> A = infsup ("[2, 4]");
>> A.inf = infsup ("[1, 3]")
>> A.inf = 5
A = [Empty]
** While at it, also allow multiple subscripts in <code>subsasgn</code>
>> A(:)(2:4)(2) = 42; # equivalent to A(3) = 42
>> A.inf(3) = 42; # also A(3).inf = 42
>> A.inf.inf = 42 # should produce error?
>> A.inf.sup = 42 # should produce error?
== Compatibility ==
The interval package's main goal is to be compliant with IEEE Std 1788-2015, so it is compatible with other standard-conforming implementations (on the set of operations described by the standard document).
=== Octave Forge simp package ===
* Basic operations can be found in both packages, but the availability of special functions depends
In GNU Octave the interval package can also be run alongside INTLAB.|<syntaxhighlight lang="octave"> # INTLAB intervals A1 = infsup (2, 3); B1 = hull (-4, A1); C1 = midrad (0, 2); # Interval package intervals pkg load interval A2 = infsup (2, 3); B2 = hull (-4, A2); C2 = midrad (0, 2); pkg unload interval # Computation with INTLAB A1 + B1 * C1 # Computation without INTLAB A2 + B2 * C2
==== Known differences ====
| isintval (x)
== Similar software ==
For C++ there is an interval library [https://github.com/nehmeier/libieeep1788/ libieeep1788] by Marco Nehmeier (member of IEEE P1788). It aims to be standard compliant with IEEE Std 1788-2015 and is designed in a modular way, supporting several interval data types and different flavors of interval arithmetic [http://www.youtube.com/watch?v=GOa9aWAZO_Q]. The GNU Octave interval package shares several unit tests with libieeep1788.
For Julia there is an evolving interval library [https://github.com/dpsanders/ValidatedNumerics.jl ValidatedNumerics.jl] by Luis Benet and David P. Sanders. It is planned to become conforming to IEEE Std 1788-2015 (or to the basic standard 1788.1) in the future.
== Developer Information ==
=== Source Code Repository ===
=== Build ===
* Octave ** Version 3.8.0 or greater ** No need to compile from source, but you need development files e.g. package <code> liboctave- dev</code> in Debian. * Mercurial * Texinfo * MPFR ** Version 3.1.0 or greater ** No need to compile from source, but you need development files e.g. package <code>libmpfr-dev </code> in Debian. * Octave package: doctest ** Purpose: Verification of the examples in the manual and in the function documentation ** Installation: Use <code>pkg install -forge doctest</code> inside Octave * Octave package: generate_html ** Purpose: Generate HTML documenation for publication on Octave Forge (only needed for release) ** Installation: Use <code>pkg install -forge generate_html</code> inside Octave * ITF1788 ** Purpose: Compilation of unit-test ** Installation: **# Clone the git repository from https://github.com/oheim/ITF1788 **# Install python 3 and the dependencies described by ITF1788's <code>setup.py</code> file **# Set up an environment variable ITF1788_HOME to point to your local git workspace, for example put the line <code>export IFT1788_HOME=/home/user/ITF1788</code> into your <code>.bashrc</code>. * LilyPond, Inkscape, Poppler ** Purpose: Generate / convert images for the manual ** Installation: Use your distribution's package manager (look for packages called <code>lilypond</code> <code>inkscape</code> <code>poppler-utils</code>)
=== Architecture ===
| | `- ... – further functions on decorated intervals
| `- ... – a few global functions that don't operate on intervals
+- src/ | | +- mpfr_function_d.cc – computes various arithmetic functions correctly rounded (using MPFR) | | `- ... – other oct-file sources `- test/ – interval arithmetic unit tests
=== Best practices ===
* Methods with more than 1 parameter must convert non-interval parameters to intervals using the class constructor. This allows the user to mix non-interval parameters with interval parameters and the function treats any inputs as intervals. Invalid values will be handled by the class constructors.
if (not (isa (x, "infsup")))
x = infsup (x);
if (not (isa (y, "infsup")))
y = infsup (y);
if (not (isa (x, "infsupdec")))
x = infsupdec (x);
if (not (isa (y, "infsupdec")))
y = infsupdec (y); endif * Methods of class <code>infsupdec</code> as well as methods of class <code>infsup</code> that are not overridden by <code>infsupdec</code> must check parameters using the <code>isnai</code> function and return the NAI value if it is present. This will propagate NAI values through any function evaluations. if (isnai (x)) result = x; return
==== Use of Octave functions ====
Octave functions may be used as long as they don't introduce arithmetic errors. For example, the ceil function can be used safely since it is exact on binary64 numbers.
result = ceil (x) ... parameter checking ... result = infsup (ceil (x.inf) , ceil (x.sup ));
==== Vectorization & Indexing ====
All functions should be implemented using vectorization and indexing. This is very important for performance on large data. For example, consider the plus function. It computes lower and upper boundaries of the result (x.inf, y.inf, x.sup, y.sup may be vectors or matrices) and then uses an indexing expression to adjust values where empty intervals would have produces problematic values.
result = plus (x, y) ... parameter checking ... l = mpfr_function_d ('plus', -inf, x.inf, y.inf); u = mpfr_function_d ('plus', +inf, x.sup, y.sup);
emptyresult = isempty (x) | isempty (y); l(emptyresult) = inf; u(emptyresult) = -inf; result = infsup (l, u);