602

edits

Jump to navigation
Jump to search

m
~~The interval package provides data types and operations for~~__TOC__~~verified computing~~[[File:Interval-sombrero. ~~ It can be used to handle uncertainties, estimate~~~~arithmetic errors and produce reliable results. Also it can help find~~~~guaranteed solutions to numerical problems. Thanks to GNU MPFR many~~~~arithmetic operations are provided with best possible accuracy. The~~~~implementation of intervals in inf-sup format is based on interval boundaries~~~~represented by binary64 numbers and is standard conforming to ~~png|280px|thumb|left|Example: Plotting the ~~(upcoming) standard for ~~interval ~~arithmetic ~~enclosure of a function]]~~[http~~<div style="clear:left"></~~/standards.ieee.org/develop/project/1788.html IEEE 1788].~~div>
~~{{quote|Give a digital computer a problem in arithmetic~~== Compatibility ==The interval package's main goal is to be compliant with IEEE Std 1788-2015, ~~and ~~so it ~~will grind away methodically, tirelessly, at gigahertz speed, until ultimately it produces ~~is compatible with other standard-conforming implementations (on the set of operations described by the ~~wrong answer~~standard document). ~~… An interval computation yields a pair of numbers, an upper and a lower bound~~Other implementations, which are ~~guaranteed ~~known 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|[http~~aim for standard conformance are:~~//dx.doi.org/10.1511/2003.6.484 DOI: 10.1511/2003.6.484]}}~~
~~{| class="wikitable" style="margin: auto"~~~~!Standard floating point arithmetic~~~~!Interval arithmetic~~~~|-~~~~| style = "vertical-align: top" |~~~~ <span style="opacity~~* [https://github.~~5">octave:1> <~~com/JuliaIntervals/~~span>19 * 0~~IntervalArithmetic.~~1 - 2 + 0~~jl IntervalArithmetic.~~1~~jl package] (Julia)~~ ans = 1.3878e-16~~~~| style = "vertical-align: top" |~~~~ <span style="opacity~~* [https://github.~~5">octave:1> <~~com/jinterval/~~span>x = infsup ~~jinterval JInterval library] (~~"0.1"~~Java)~~;~~~~ <span style="opacity~~* [https://github.~~5">octave:2> <~~com/nadezhin/~~span>19 * x - 2 ~~libieeep1788 ieeep1788 library] (C++ ~~x~~~~ ans ⊂ [-3.191891195797326e-16~~) created by Marco Nehmeier, ~~+1.3877787807814457e-16]~~~~|}~~later forked by Dmitry Nadezhin
~~Floating-point arithmetic, as specified by [http:~~=== Octave Forge simp package ===In 2008/~~/en.wikipedia.org/wiki/IEEE_floating_point 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~~2009 there was a Single Interval Mathematics Package (SIMP) for Octave, ~~the double-precision format is the default numeric data type in GNU ~~which has eventually become unmaintained at Octave~~. Benefits are obvious: The results of arithmetic operations are well-defined and comparable between different systems and computation is highly efficient~~Forge.
~~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. [http://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html] [http://www.cs.berkeley.edu/~wkahan/Mindless.pdf] [http://www.ima.umn.edu/~arnold/disasters/]~~~~* ~~The ~~binary data types categorically are not suitable for doing financial computations. Very often representational errors are introduced when using “real world” decimal numbers. [http://en.wikipedia.org/wiki/Decimal_computer]~~~~* Even if the developer would be proficient, most developing environments / technologies limit floating-point arithmetic capabilities to ~~simp package contains a ~~very limited subset of IEEE 754: Only one or two data types, no rounding modes, missing functions … [http://www.cs.berkeley.edu/~wkahan/JAVAhurt.pdf]~~~~* Results are hardly predictable. [https://hal.archives-ouvertes.fr/hal-00128124/en/] All operations produce the best possible accuracy ''at runtime'', this is how a floating point works. Contrariwise, financial computer systems typically use a [http://en.wikipedia.org/wiki/Fixed-point_arithmetic fixed-point ~~few basic interval arithmetic~~] (COBOL, PL/I, …), where overflow and rounding can be precisely predicted ''at compile-time''.~~~~* Results are system dependent. All but the most basic floating-point ~~operations ~~are not guaranteed to be accurate and produce different results depending ~~on ~~low level libraries and hardware~~scalar or vector intervals. ~~[http://www.gnu.org/software/libc/manual/html_node/Errors~~It does not consider inaccurate built-inarithmetic functions, round-~~Math-Functions.html#Errors-in-Math-Functions] [http://developer.amd.com/tools-and-sdks/cpu-development/libm/]~~~~* 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~~off, ~~when looking at numerical output ~~conversion and ~~the computer says “<code>ans = 0~~representational errors.~~1</code>,” this ~~As a result its syntax is ~~not absolutely correct. In fact~~very easy, but the ~~value is only ''close enough'' ~~arithmetic fails to ~~the value 0.1. Additionally, many functions ~~produce ~~limit values (∞ × −∞ = −∞, ∞ ÷ 0 = ∞, ∞ ÷ −0 = −∞, log (0) = −∞), which is sometimes (but not always!) useful when overflow and underflow occur~~guaranteed enclosures.
~~Interval arithmetic addresses above problems in its very special way and introduces new possibilities ~~It is recommended to use the interval package as a replacement for ~~algorithms~~simp. ~~For example~~However, function names and interval constructors are not compatible between the ~~[http://en.wikipedia.org/wiki/Interval_arithmetic#Interval_Newton_method interval newton method] is able to find ''all'' zeros of a particular function~~packages.
~~=== Online Introductions ===~~
~~[http~~<div style="display:~~//www.maths.manchester.ac.uk/~higham/narep/narep416.pdf Interval analysis in MATLAB] Note~~flex; align-items: ~~The INTLAB toolbox for Matlab is not entirely compatible ~~flex-start"><div style="margin-right: 2em">{{Code|Computation with this interval package ~~for GNU Octave~~|<syntaxhighlight lang="octave">pkg load intervalA1 = infsup (2, 3);B1 = hull (-4, ~~cf. [[#Compatibility]]. However~~A2);C1 = midrad (0, ~~basic operations can be compared and should be compatible for common intervals.~~2);
~~=== Moore's fundamental theroem of interval arithmetic ===~~A1 + B1 * C1~~Let '''''y''''' = ''f''('''''x''''') be the result of~~~~interval-evaluation of ''f'' over a box '''''x''''' = (''x''~~<~~sub~~/syntaxhighlight>~~1~~}}</~~sub~~div>~~, … , ''x''~~<~~sub~~div>~~''n''~~{{Code|Computation with INTLAB|<~~/sub~~syntaxhighlight lang="octave">~~)~~~~using any interval versions of its component library functions. Then~~startintlab~~# In all cases, '''''y''''' contains the range of ''f'' over '''''x''''', that is~~A2 = infsup (2, ~~the set of ''f''('''''x'''''~~3) ~~at points of '''''x''''' where it is defined: '''''y''''' ⊇ Rge(''f'' | '''''x''''') ~~;B2 =~~ {''f''~~hull (~~''x''~~-4, A2)~~ | ''x'' ∈ '''''x''''' ∩ Dom(''f'') }~~;~~# If also each library operation in ''f'' is everywhere defined on its inputs, while evaluating '''''y''''', then ''f'' is everywhere defined on '''''x''''', that is Dom~~C2 = midrad (~~''f'') ⊇ '''''x'''''.~~~~# If in addition, each library operation in ''f'' is everywhere continuous on its inputs, while evaluating '''''y''''', then ''f'' is everywhere continuous on '''''x'''''.~~~~# If some library operation in ''f'' is nowhere defined on its inputs~~0, ~~while evaluating '''''y''''', then ''f'' is nowhere defined on '''''x''''', that is Dom(''f''~~2)~~ ∩ '''''x''''' = Ø.~~;
~~== What to expect ==~~A2 + B2 * C2~~The interval arithmetic provided by this interval package is '''slow''', but '''accurate'''.~~</syntaxhighlight>}}</div></div>
~~''Why is the interval package slow?''~~~~All arithmetic interval operations are simulated in high-level octave language using C99 or multi-precision floating-point routines, which is a lot slower than a hardware implementation [https://books.google.de/books?id~~=~~JTc4XdXFnQIC&pg~~=~~PA61]. Building ~~== Known differences ====Simple programs written for INTLAB should run without modification with this interval ~~arithmetic operations from floating-point routines is easy for simple monotonic functions, e. g., addition and subtraction, but is complex for others, e. g., [http://exp~~package.~~ln0.de/heimlich-power-2011.htm interval power function], atan2, or [[#Reverse_arithmetic_operations|reverse ~~The following table lists common functions~~]]. For some interval operations it is not even possible to rely on floating-point routines, since not all required routines are available ~~that use a different name in ~~C99 or BLAS~~INTLAB.{|~~For example, multiplication of matrices with many elements becomes unfeasible as it takes a lot of time.~~! interval package! INTLAB|-~~{~~| ~~class="wikitable" style="margin: auto; align:right"~~infsup (x)|~~+ Approximate runtime ~~intval (~~wall clock time in seconds~~x) ~~<span style="font~~|-~~weight: normal">— Results have been produced with GNU Octave 3.8.2 and Interval package 0.1.4 on an Intel® Core™ i5-4340M CPU ~~| wid (~~2.9–3.6 GHz~~x)~~</span>~~~~!rowspan="2"~~|~~Interval matrix size~~diam (x)~~!valign="top" style="min~~|-~~width:6em"~~|~~<code>plus</code>~~subset (a, b)~~!valign="top" style="min-width:6em"~~|~~<code>times</code>~~in (a, b)~~!valign="top" style="min~~|-~~width:6em"~~|~~<code>log</code>~~interior (a, b)~~!valign="top" style="min-width:6em"~~|~~<code>pow</code>~~in0 (a, b)~~!valign="top" style="min~~|-~~width:6em"|<code>mtimes</code>~~~~!valign="top" style="min-width:6em"~~|~~<code>mtimes</code>~~isempty (x)~~!valign="top" style="min-width:6em"~~|~~<code>inv</code>~~isnan (x)
~~!style="font-weight:normal"~~|~~tightest<br/>accuracy~~disjoint (a, b)~~!style="font-weight:normal"~~|~~tightest<br/>accuracy~~~~!style="font-weight:normal"|tightest<br/>accuracy~~~~!style="font-weight:normal"|tightest<br/>accuracy~~~~!style="font-weight:normal"|valid<br/>accuracy~~~~!style="font-weight:normal"|tightest<br/>accuracy~~~~!style="font-weight:normal"|valid<br/>accuracy~~emptyintersect (a, b)
~~''Why is the interval package accurate?''~~== Developer Information ===== Source Code Repository ===~~The GNU Octave built-in floating-point routines are not useful for interval arithmetic~~https: ~~Their results depend on hardware, system libraries and compilation options~~//sourceforge. ~~The ~~net/p/octave/interval ~~package handles all arithmetic functions with the help of the [http:~~/ci/default/~~www.mpfr.org~~tree/ ~~GNU MPFR library]. With MPFR it is possible to compute system-independent, valid and tight enclosures of the correct results for most functions. However, it should be noted that some reverse operations and matrix operations do not exists in GNU MPFR and therefore cannot be computed with the same accuracy.~~
~~== Quick start introduction ==~~'''Build dependencies'''<code>apt-get install libmpfr-dev autoconf automake inkscape zopfli</code>
~~{{Code|Create ~~In a nutshell the package provides two new data types to users: bare intervals ~~for performing interval arithmetic|~~and decorated intervals. The data types are implemented as:* class <code>infsup<~~syntaxhighlight lang="octave"~~/code>~~infsupdec ~~(~~1~~bare interval) ~~# [1]_com~~~~infsupdec ~~with attributes <code>inf</code> (~~1, 2~~lower interval boundary) ~~# [1, 2]_com~~~~infsupdec ~~and <code>sup</code> (~~"3", "4"~~upper interval boundary) ~~# [3, 4]_com~~* class <code>infsupdec </code> (~~"1.1"~~decorated interval) ~~# [1.0999999999999998, 1.100000000000001]_com~~~~infsupdec ~~which extends the former and adds attribute <code>dec</code> (~~"5.8e-17")~~~~ # [5.799999999999999e-17, 5.800000000000001e-17]_com~~~~midrad (12, 3~~interval decoration) ~~# [9, 15]_com~~~~midrad ("4.2", "1e-7") # [4~~.~~199999899999999, 4.200000100000001]_com~~~~hull (3, 42, "19.3", "-2.3") # [-2.300000000000001, +42]_com~~~~hull ("pi", "e") # [2.718281828459045, 3.1415926535897936]_com~~~~</syntaxhighlight>~~~~}}~~
~~The default text representation ~~Almost all functions in the package are implemented as methods of ~~intervals is not guaranteed to be exact~~these classes, ~~because this would massively spam console output~~e. g. ~~For example, the exact text representation of ~~<code>~~realmin~~@infsup/sin</code> ~~would be over 700 decimal places long! However~~implements the sine function for bare intervals. Most code is kept in m-files. Arithmetic operations that require correctly-rounded results are implemented in oct-files (C++ code), these are used internally by the m-files of the ~~default text representation ~~package. The source code is ~~correct ~~organized as ~~it guarantees to contain the actual boundaries.~~follows:
~~{{Warning~~ +- doc/ – package manual +- inst/ |~~Decimal fractions as well as numbers of high magnitude ~~ +- @infsup/ | | +- infsup.m – class constructor for bare intervals | | +- sin.m – sine function for bare intervals (~~> 2<sup>53<~~uses mpfr_function_d internally) | | `- ... – further functions on bare intervals | +- @infsupdec/~~sup>~~ | | +- infsupdec.m – class constructor for decorated intervals | | +- sin.m – sine function for decorated intervals (uses @infsup/sin internally) ~~should always be passed as ~~ | | `- ... – further functions on decorated intervals | `- ... – a ~~string to the constructor~~few global functions that don't operate on intervals `- src/ +- mpfr_function_d. ~~Otherwise it is possible, that GNU Octave introduces conversion errors when the numeric literal is converted into floating~~cc – computes various arithmetic functions correctly rounded (using MPFR) `-~~point format '''before''' it is passed to the constructor~~.~~}}~~.. – other oct-file sources
~~{{Code|Beware of the conversion pitfall|~~=== Best practices ======= Parameter checking ====* All methods must check <code>nargin</code> and call <code>print_usage<~~syntaxhighlight lang="octave"~~/code>~~## The numeric constant “0.3” is an approximation of ~~if the~~## decimal ~~number ~~0~~of parameters is wrong.~~3~~This prevents simple errors by the user. ~~ An ~~* Methods with more than 1 parameter must convert non-interval ~~around this approximation~~~~## will not contain ~~parameters to intervals using the ~~decimal number 0.3.~~~~infsupdec (0.3) # [0.29999999999999998, 0~~class constructor.~~29999999999999999]_com~~~~## However, passing ~~This allows the ~~decimal number 0.3 as a string~~~~## ~~user to mix non-interval parameters with interval parameters and the ~~interval constructor ~~function treats any inputs as intervals. Invalid values will ~~create an interval which~~~~## actually encloses ~~be handled by the ~~decimal number~~class constructors.~~infsupdec ~~ if (not (isa (x, "~~0.3~~infsup") ~~# [0.29999999999999998~~)) x = infsup (x); endif if (not (isa (y, ~~0.3000000000000001]_com~~"infsup")))~~</syntaxhighlight>~~ y = infsup (y);~~}}~~ endif
~~Interval matrices behave like normal matrices in GNU ~~==== Use of Octave ~~and ~~functions ====Octave functions may be used as long as they don't introduce arithmetic errors. For example, the ceil function can be used ~~for broadcasting and vectorized ~~safely since it is exact on binary64 numbers. function ~~evaluation~~x = ceil (x) ... parameter checking ... x.inf = ceil (x.inf); x.sup = ceil (x.sup); endfunction
~~{{Code|Create interval matrices|~~If Octave functions would introduce arithmetic/rounding errors, there are interfaces to MPFR (<code>mpfr_function_d<~~syntaxhighlight lang="octave"~~/code>~~M = infsup (magic (3)~~)~~ # [8] [1] [6]~~~~ # [3] [5] [7]~~~~ # [4] [9] [2]~~~~infsup ~~and crlibm (~~magic (3), magic (3) + 1)~~~~ # [8, 9] [1, 2] [6, 7]~~~~ # [3, 4] [5, 6] [7, 8]~~~~ # [4, 5] [9, 10] [2, 3]~~~~infsupdec (["0.1"; "0.2"; "0.3"; "0.4"; "0.5"])~~~~ # [0.09999999999999999, 0.1000000000000001]_com~~~~ # [0.19999999999999998, 0.2000000000000001]_com~~~~ # [0.29999999999999998, 0.3000000000000001]_com~~~~ # [0.39999999999999996, 0.4000000000000001]_com~~~~ # [0.5]_com~~~~infsup ({1, eps; "4~~<code>crlibm_function</~~7", "pi"}, {2, 1; "e", "0xff"}~~code>)~~ # [1, 2] [2.220446049250313e-16~~, ~~1]~~~~ # [0~~which can produce guaranteed boundaries.~~5714285714285713, 2.7182818284590456] [3.141592653589793, 255]~~~~</syntaxhighlight>~~~~}}~~
~~Arithmetic functions in a set-based interval arithmetic follow these rules~~== VERSOFT ==The [http: ~~Intervals are sets~~//uivtx.cs. ~~They are subsets of the set of real numbers~~cas. ~~The interval version of an elementary function such as sin~~cz/~rohn/matlab/ VERSOFT] software package (by Jiří Rohn) has been released under a free software license (~~''x''~~Expat license) ~~is essentially the natural extension to sets of the corresponding point-wise function on real numbers. That is, the function is evaluated for each number in ~~and algorithms may be migrated into the interval ~~where the function is defined and the result must be an enclosure of all possible values that may occur~~package.
~~By default arithmetic functions are computed with best possible accuracy ~~{|! Function! Status! Information|-|colspan="3"|Real (~~which is more than what is guaranteed by GNU Octave core functions~~or complex)~~. The result will therefore be a tight and very accurate enclosure of the true mathematical value in most cases. Details on each function's accuracy can be found in its documentation, which is accessible with GNU Octave's help command.~~data only: Matrices|-|verbasis~~{{Code~~|~~Examples of using interval arithmetic functions~~style="color:red"| trapped|depends on <~~syntaxhighlight lang~~code style="~~octave~~color:red">verfullcolrank</code>~~sin (infsupdec (0.5)) # [.4794255386042029, .4794255386042031]_com~~|-~~pow (infsupdec (2), infsupdec (3, 4)) # [8, 16]_com~~|vercondnum~~atan2 (infsupdec (1), infsupdec (1))~~|style="color:red"| trapped~~ # [.7853981633974482, .7853981633974484]_com~~| depends on <code style="color:red">versingval</code>~~midrad (magic (3), 0.5) * pascal (3)~~|-~~ # [13.5, 16.5]_com [25, 31]_com [42, 52]_com~~|verdet~~ # [13.5, 16.5]_com [31, 37]_com [55, 65]_com~~~~ # [13.5, 16.5]_com [25, 31]_com [38, 48]_com~~|style="color:red"| trapped| depends on <code>vereig</~~syntaxhighlight~~code>~~}}~~|-|verdistsing|style=~~== Numerical operations ===~~"color:red"| trapped~~Some operations ~~| depends on ~~intervals do not return an interval enclosure, but a single number (in double-precision). Most important are ~~<codestyle="color:red">~~inf~~versingval</code> ~~and ~~|-|verfullcolrank|style="color:red"| trapped| depends on <code>~~sup~~verpinv</code>~~, which return the lower and upper interval boundaries.~~|-|vernorm2|style="color:red"| trapped~~More such operations are ~~| depends on <codestyle="color:red">~~mid~~versingval</code> |-|vernull (~~approximation of the interval's midpoint~~experimental)~~, ~~| unknown| depends on <codestyle="color:red">~~wid~~verlsq</code> ~~(approximation of the interval's width), ~~; todo: compare with local function inside <codestyle="color:green">~~rad~~verintlinineqs</code> ~~(approximation of the interval's radius), ~~|-|verorth|style="color:red"| trapped| depends on <codestyle="color:red">~~mag~~verbasis</code> ~~(interval's magnitude) ~~and <codestyle="color:red">~~mig~~verthinsvd</code> ~~(interval's mignitude).~~|-|verorthproj|style="color:red"| trapped| depends on <code style="color:red">verpinv</code> and <code style= ~~Boolean operations ==~~"color:red">verfullcolrank</code>|-|verpd|style="color:red"| trapped~~Interval comparison operations produce boolean results. While some comparisons are especially for intervals ~~| depends on <code>isspd</code> (~~subset~~by Rump, ~~interior, ismember, isempty, disjoint, …~~to be checked) ~~others are extensions of simple numerical comparison. For example, the less-or-equal comparison is mathematically defined as ∀~~and <~~sub~~code style="color:red">~~''a''~~vereig</~~sub~~code>~~ ∃~~|-|verpinv|style="color:red"| trapped| dependency <~~sub~~code>~~''b''~~verifylss</~~sub~~code>~~ ''a'' ≤ ''b'' ∧ ∀~~is implemented as <~~sub~~code>~~''b''~~mldivide</~~sub~~code>~~ ∃~~; depends on <~~sub~~code style="color:red">~~''a''~~verthinsvd</~~sub~~code>~~ ''a'' ≤ ''b''.~~|-|verpmat~~ ~~|style="color:red"| trapped| depends on <~~span ~~code style="~~opacity~~color:~~.5~~red">~~octave:1> ~~verregsing</~~span~~code>~~infsup (1, 3) <= infsup (2, 4)~~~~ ans = 1~~|-|verrank|style="color:red"| trapped| depends on <code style="color:red">versingval</code> and <code style= ~~Matrix operations ===~~~~Above mentioned operations can also be applied element-wise to interval vectors and matrices. Many operations use [http~~"color:red">verbasis</~~/www.gnu.org/software/octave/doc/interpreter/Vectorization~~code>|-~~and-Faster-Code-Execution.html#Vectorization-and-Faster-Code-Execution vectorization techniques].~~|verrref|style="color:red"| trapped~~In addition, there are matrix operations ~~| depends on ~~interval matrices. These operations comprise~~<code style="color: ~~dot product, matrix multiplication, vector sums (all with tightest accuracy), matrix inversion, matrix powers, and solving linear systems (the latter are less accurate). As a result of missing hardware ~~red">verfullcolrank</ ~~low-level library support ~~code> and ~~missing optimizations, these operations are relatively slow compared to familiar operations in floating-point arithmetic.~~ ~~{{Code|Examples of using interval matrix functions|~~<~~syntaxhighlight lang~~code style="~~octave~~color:red">verpinv</code>|-~~A ~~|colspan= ~~infsup ([1, 2, ~~"3~~; 4, 0, 0; 0, 0, 1]); A ~~"|Real (~~2, 3~~or complex) data only: Matrices: Eigenvalues and singular values|-|vereig|style= "~~[0, 6]~~color:red"| trapped~~ # [1] [2] [3]~~| depends on proprietary <code>verifyeig</code> function from INTLAB, depends on complex interval arithmetic~~ # [4] [0] [0, 6]~~|-~~ # [0] [0] [1]~~|<s>vereigback</s>~~B ~~|style= ~~inv ~~"color:green"| free, migrated (~~A~~for real eigenvalues)~~ # [0] [0.25] [-1.5, 0]~~| dependency <code>norm</code> is already implemented~~ # [0.5] [~~|-~~0.125] [-1.5, -0.75]~~~~ # [0] [0] [1]~~|verspectrad~~A * B~~|style="color:red"| trapped~~ # [1] [0] [-1.5, +1.5]~~| main part implemented in <code>vereig</code>~~ # [0] [1] [~~|-~~6, +6]~~~~ # [0] [0] [1]~~ ~~A ~~|colspan= ~~infsup ~~"3"|Real (~~magic (3)~~or complex)data only: Matrices: Decompositions~~ # [8] [1] [6]~~|-~~ # [3] [5] [7]~~|verpoldec~~ # [4] [9] [2]~~|style="color:red"| trapped~~c ~~| depends on <code style= ~~A \ [3; 4; 5]~~"color:red">verthinsvd</code>~~ # [0.18333333333333315, 0.18333333333333358]~~|-~~ # [0.43333333333333318, 0.43333333333333346]~~|verrankdec~~ # [0.18333333333333307, 0.18333333333333355]~~|style="color:red"| trapped~~A * c~~| depends on <code style="color:red">verfullcolrank</code> and <code style="color:red">verpinv</code>~~ # [2.9999999999999964, 3.0000000000000036]~~|-~~ # [3.9999999999999964, 4.000000000000004]~~|verspectdec~~ # [4.999999999999997, 5.000000000000003]~~|style="color:red"| trapped| main part implemented in <code>vereig</~~syntaxhighlight~~code>~~}}~~|-|verthinsvd|style=~~=== Notes on linear systems ====~~"color:red"| trapped~~A system of linear equations ~~| implemented in ~~the form A''x'' ~~<code>vereig</code>|-|colspan=~~ b with intervals can be seen as a range of ''classical'' linear systems, which can be solved simultaneously. Whereas classical algorithms compute an approximation for a single solution of a single linear system, interval algorithms compute an enclosure for all possible solutions of ~~"3"|Real (~~possibly several~~or complex) ~~linear systems. Some characteristics should definitely be known when linear interval systems are solved~~data only: Matrix functions|-|vermatfun|style="color:red"| trapped~~* If the linear system is underdetermined and has infinitely many solutions, the interval solution will be unbound ~~| main part implemented in ~~at least one of its coordinates. Contrariwise, from an unbound result it can not be concluded whether the linear system is underdetermined or has solutions.~~<code>vereig</code>~~* If the interval result is empty in at least one of its coordinates, the linear system is guaranteed to be underdetermined and has no solutions. Contrariwise, from a non~~|-~~empty result it can not be concluded whether all or some of the ~~|colspan="3"|Real data only: Linear systems ~~have solutions or not.~~(rectangular) ~~* Wide intervals within the matrix A can easily lead to a superposition of cases, where the rank of A is no longer unique. If the linear interval system contains cases of linear independent equations as well as linear dependent equations, the resulting enclosure of solutions will inevitably be very broad.~~|-|<s>verlinineqnn</s>~~However~~|style="color:green"| free, ~~solving linear systems with interval arithmetic can produce useful results in many cases and automatically carries ~~migrated| use <code>glpk</code> as a ~~guaranty ~~replacement for ~~error boundaries. Additionally, it can give better information than the floating~~<code>linprog</code>|-~~point variants for some cases.~~|verlinsys|style="color:red"| trapped~~{{Code~~|~~Standard floating point arithmetic versus interval arithmetic ~~dependency <code>verifylss</code> is implemented as <code>mldivide</code>; depends on ~~ill-conditioned linear systems|~~<~~syntaxhighlight lang~~code style="~~octave~~color:red">~~A ~~verpinv</code>, <code style= ~~[1, 0; 2, 0];~~~~## This linear system has no solutions~~~~A \ [3; 0]~~~~ # warning~~"color: ~~matrix singular to machine precision~~red">verfullcolrank</code>, ~~rcond ~~and <code style= ~~0~~"color:red">verbasis</code>~~ # 0.60000~~|-~~ # 0.00000~~|verlsq~~## This linear system has many solutions~~|style="color:red"| trapped~~A \ [4; 8]~~| depends on <code style="color:red">verpinv</code> and <code style="color:red">verfullcolrank</code>~~ # 4~~|-~~ # 0~~ ~~## The empty interval vector proves that there is no solution~~~~infsup (A) \ [~~|colspan="3~~; 0]~~"|Real data only: Optimization~~ # [Empty]~~|-~~ # [Empty]~~|verlcpall~~## The unbound interval vector indicates that there may be many solutions~~|style="color:green"| free~~infsup (A) \ [4; 8]~~| depends on <code>verabsvaleqnall</code>~~ # [4]~~~~ # [Entire]~~|-|<s>verlinprog</~~syntaxhighlight~~s>~~}}~~|style="color:green"| free, migrated| use <code>glpk</code> as a replacement for <code>linprog</code>; dependency <code>verifylss</code> is implemented as <code>mldivide</code>~~== Advanced topics ==~~|-|verlinprogg|style=~~== Error handling ===~~"color:red"| trapped| depends on <code>verfullcolrank</code>~~Due to the nature of set~~|-~~based interval arithmetic, one should not observe errors (in the sense of raised GNU Octave error messages) during computation unless operations are evaluated for incompatible data types. Arithmetic operations which are not defined for (parts of) their input, simply ignore anything that is outside of their domain.~~|verquadprog| unknown~~However, ~~| use <code>quadprog</code> from the ~~interval constructors can produce errors depending on the input. The ~~optim package; use <code>glpk</code> as a replacement for <code>~~infsup~~linprog</code> ~~constructor will fail if the interval boundaries are invalid. Contrariwise, the (preferred) ~~; dependency <code>~~infsupdec~~verifylss</code>~~, ~~is implemented as <code>~~midrad~~mldivide</code> ~~and ~~; depends on <code>~~hull~~isspd</code> ~~constructors will only issue a warning and return a ~~(by Rump, to be checked, algorithm in [~~NaI] object, which will propagate and survive through computations~~http://www.ti3.tuhh. ~~NaI stands for “not an interval”~~de/paper/rump/Ru06c.pdf]) ~~{{Code~~|~~Effects of set~~-~~based interval arithmetic on partial functions and the NaI object~~|~~<syntaxhighlight lang~~colspan="~~octave~~3"~~>~~|Real (or complex) data only: Polynomials~~## Evaluation of a function outside of its domain returns an empty interval~~|-~~infsupdec (2) / 0 # [Empty]_trv~~|verroots~~infsupdec (0) ^ infsupdec (0) # [Empty]_trv~~|style="color:red"| trapped| main part implemented in <code>vereig</code>~~## Illegal interval construction creates a NaI~~|-~~infsupdec ~~|colspan="3"|Interval (~~3, 2~~or real) ~~# [NaI]~~data: Matrices|-~~## NaI even survives through computations~~|verhurwstab~~ans + 1 # [NaI]~~|style="color:red"| trapped| depends on <code style="color:red">verposdef</~~syntaxhighlight~~code>~~}}~~|-|verinverse|style="color:green"| free~~There are some situations where the interval package cannot decide whether an error occurred or not and issues a warning. The user may choose to ignore these warnings or handle them as errors, see ~~| depends on <codestyle="color:green">~~help warning~~verintervalhull</code> ~~for instructions.~~, to be migrated|-|<s>verinvnonneg</s>~~{~~| ~~class~~style="~~wikitable~~color:green" | free, migrated|-|verposdef|style="~~margin~~color: ~~auto~~red"| trapped~~!Warning ID~~~~!Reason~~~~!Possible consequences~~| depends on <code>isspd</code> (by Rump, to be checked) and <code style="color:red">verregsing</code>
~~| mulRevToPair~~
~~| mulrev [http://octave.sourceforge.net/interval/function/@infsup/mulrev.html] with two output parameters~~
~~== Compatibility ==~~
~~ ~~
~~The interval package's main goal is to be compliant with IEEE 1788, so it is compatible with other standard-conforming implementations (on the set of operations described by the standard document).~~
~~ ~~
~~This interval package is ''not'' meant to be a replacement for INTLAB and any compatibility with it is pure coincidence. Since both are compatible with GNU Octave, they happen to agree on many function names and programs written for INTLAB may possibly run with this interval package as well. Some fundamental differences that I am currently aware of:~~
~~* INTLAB is non-free software, it grants none of the [http://www.gnu.org/philosophy/free-sw.html four essential freedoms] of free software~~
~~* INTLAB is not conforming to IEEE 1788 and the parsing of intervals from strings uses a different format—especially for the uncertain form~~
~~* INTLAB supports intervals with complex numbers and sparse interval matrices, but no empty intervals~~
~~* INTLAB uses inferior accuracy for most arithmetic operations, because it focuses on speed~~
~~* Basic operations can be found in both packages, but the availability of special functions depends~~
~~ ~~
~~{{Code|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~~
~~</syntaxhighlight>~~
~~}}~~
~~ ~~
~~== Related work ==~~
~~ ~~
~~For C++ there is an open source interval library [https://github.com/nehmeier/libieeep1788/ libieeep1788] by Marco Nehmeier (member of IEEE P1788). It aims to be standard compliant with IEEE 1788 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 C++, Pascal and Fortran there is a free interval library [http://www2.math.uni-wuppertal.de/~xsc/xsc-sprachen.html XSC]. It is not standard compliant with IEEE 1788. Some parts of the GNU Octave interval package have been derived from C-XSC.~~
~~ ~~
~~For Java there is a library [https://java.net/projects/jinterval/ jinterval] by Dmitry Nadezhin (member of IEEE P1788). It aims to be standard compliant with IEEE 1788, but is not complete yet.~~
~~ ~~
~~For MATLAB there is a popular, nonfree interval arithmetic toolbox [http://www.ti3.tu-harburg.de/rump/intlab/ INTLAB] by Siegfried Rump. It had been free of charge for academic use in the past, but no longer is. Its origin dates back to 1999, so it is well tested and comprises a lot of functionality, especially for vector / matrix operations. INTLAB is compatible with GNU Octave since Version 9 [http://www.ti3.tuhh.de/rump/intlab/Octave/octave.html].~~

Remove redundant Category:Packages.

The GNU Octave interval package for real-valued [~~http~~https://~~octave~~en.~~sourceforge~~wikipedia.~~net~~org/~~interval~~wiki/ Interval_arithmetic interval ~~package~~arithmetic] ~~for ~~.* Intervals are closed, connected subsets of the realnumbers. Intervals may be unbound (in either or both directions) or empty. In special cases <code>+inf</code> and <code>-~~valued ~~inf</code> are used to denote boundaries of unbound intervals, but any member of the interval is a finite real number.* Classical functions are extended to interval functions as follows: The result of function f evaluated on interval x is an interval '''enclosure of all possible values''' of f over x where the function is defined. Most interval arithmetic functions in this package manage to produce a very accurate such enclosure.* The result of an interval arithmeticfunction is an interval in general. It might happen, that the mathematical range of a function consist of several intervals, but their union will be returned, e. g., 1 / [-1, 1] = [Entire].

== ~~Features ~~Distribution ==* [https://octave.sourceforge.io/interval/ Latest version at Octave Forge]** <code>pkg install -forge interval</code>** [https://octave.sourceforge.io/interval/overview.html function reference]** [https://octave.sourceforge.io/interval/package_doc/index.html package documentation] (user manual)'''Third-party'''* [https://tracker.debian.org/pkg/octave-interval Debian GNU/Linux], [https://launchpad.net/ubuntu/+source/octave-interval Launchpad Ubuntu]* [https://aur.archlinux.org/packages/octave-interval/ archlinux user repository]* Included in [https://ftp.gnu.org/gnu/octave/windows/ official Windows installer] and installed automatically with Octave (since version 4.0.1)* [https://github.com/macports/macports-ports/tree/master/math/octave-interval/ MacPorts] for Mac OS X* [https://www.freshports.org/math/octave-forge-interval/ FreshPorts] for FreeBSD* [https://cygwin.com/cgi-bin2/package-grep.cgi?grep=octave-interval Cygwin] for Windows* [https://build.opensuse.org/package/show/science/octave-forge-interval openSUSE build service]

== Development ~~Status ~~status ==* Completeness** All required functions from [https://standards.ieee.org/findstds/standard/1788-2015.html IEEE Std 1788-2015], IEEE standard for interval arithmetic, are implemented. The standard was approved by IEEE-SA on June 11, 2015. It will remain active for ten years. The standard was approved by ANSI in 2016.** Also, the minimalistic standard [https://standards.ieee.org/findstds/standard/1788.1-2017.html IEEE Std 1788.1-2017], IEEE standard for interval arithmetic (simplified) is fully implemented. The standard was approved by IEEE-SA on December 6, 2017 (and published in January 2018).** In addition there are functions for interval matrix arithmetic, N-dimensional interval arrays, plotting, and solvers.* Quality** Most arithmetic operations produce tight, correctly-rounded results. That is, the smallest possible interval with double-precision (binary64) endpoints, which encloses the exact result.** Includes [https://github.com/oheim/ITF1788 large test suite] for arithmetic functions** For open bugs please refer to the [https://savannah.gnu.org/search/?words=forge+interval&type_of_search=bugs&only_group_id=1925&exact=1 bug tracker].* Performance** All elementary functions have been [https://octave.org/doc/interpreter/Vectorization-and-Faster-Code-Execution.html vectorized] and run fast on large input data.** Arithmetic is performed with the [http://www.mpfr.org/ GNU MPFR] library internally. Where possible, the optimized [http://web.archive.org/web/20170128033523/http://lipforge.ens-lyon.fr/www/crlibm/ CRlibm] library is used.* Portability** Runs in GNU Octave ≥ 3.8.2** Known to run under GNU/Linux, Microsoft Windows, macOS, and FreeBSD

== ~~Motivation ~~Project ideas (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>* Extend <code>subsasgn</code> to allow direct manipulation of inf and sup (and dec) properties. >> A = infsup ("[2, 4]"); >> A.inf = infsup ("[1, 3]") A = [1, 4] >> 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?* Tight Enclosure of Matrix Multiplication with Level 3 BLAS [http://kam.mff.cuni.cz/conferences/swim2015/abstracts/ozaki.pdf] [http://kam.mff.cuni.cz/conferences/swim2015/slides/ozaki.pdf]* Verified Convex Hull for Inexact Data [http://kam.mff.cuni.cz/conferences/swim2015/abstracts/ohta.pdf] [http://kam.mff.cuni.cz/conferences/swim2015/slides/ohta.pdf]* Implement user-controllable output from the interval standard (e. g. via printf functions): a) It should be possible to specify the preferred overall field width (the length of s). b) It should be possible to specify how Empty, Entire and NaI are output, e.g., whether lower or upper case, and whether Entire becomes [Entire] or [-Inf, Inf]. c) For l and u, it should be possible to specify the field width, and the number of digits after the point or the number of significant digits. (partly this is already implemented by output_precision (...) / `format long` / `format short`) d) It should be possible to output the bounds of an interval without punctuation, e.g., 1.234 2.345 instead of [1.234, 2.345]. For instance, this might be a convenient way to write intervals to a file for use by another application.

== ~~Theory ~~=INTLAB ===This interval package is ''not'' meant to be a replacement for INTLAB and any compatibility with it is pure coincidence. Since both are compatible with GNU Octave, they happen to agree on many function names and programs written for INTLAB may possibly run with this interval package as well. Some fundamental differences that I am currently aware of:* INTLAB is non-free software, it grants none of the [http://www.gnu.org/philosophy/free-sw.html four essential freedoms] of free software* INTLAB is not conforming to IEEE Std 1788-2015 and the parsing of intervals from strings uses a different format—especially for the uncertain form* INTLAB supports intervals with complex numbers and sparse interval matrices, but no empty intervals* INTLAB uses inferior accuracy for most arithmetic operations, because it focuses on speed* Basic operations can be found in both packages, but the availability of special functions depends

|-

|-

| ~~10 × 10~~hdist (a, b)|~~align="right"| < 0.001~~~~|align="right"| < 0.001~~~~|align="right"| 0.001~~~~|align="right"| 0.008~~~~|align="right"| 0.001~~~~|align="right"| 0.002~~~~|align="right"| 0.025~~qdist (a, b)

|-

| ~~100 × 100~~disp (x)|~~align="right"| 0.003~~~~|align="right"| 0.010~~~~|align="right"| 0.055~~~~|align="right"| 0.61~~~~|align="right"| 0.012~~~~|align="right"| 0.53~~~~|align="right"| 0.30~~disp2str (x)

|-

| ~~500 × 500~~infsup (s)|~~align="right"| 0.060~~~~|align="right"| 0.24~~~~|align="right"| 1.3~~~~|align="right"| 15~~~~|align="right"| 0.30~~~~|align="right"| 63~~~~|align="right"| 4.2~~str2intval (s)

|-

| isa (x, "infsup")

| isintval (x)

|}

== ~~Installation ~~= Dependencies ===~~The interval package is available at Octave Forge [http://octave.sourceforge.net/interval/] and can be installed from within GNU Octave (version ≥ 3.8.2). During installation parts of the package are compiled for the target system, which requires the GNU MPFR development libraries (version ≥ 3.1.0) to be installed.~~ ~~<span style="opacity:.5">octave:1> </span>pkg ~~apt-get install liboctave-~~forge interval~~~~ <span style="opacity:.5">octave:2> </span>pkg load interval~~dev mercurial make automake libmpfr-dev

=== Build ===The ~~''development version'' may be obtained from its mercurial ~~repository~~. For convenience ~~contains a Makefile ~~target allows running ~~which controls the ~~package from source~~build process.Some common targets are:~~ hg clone http:~~* <code>make release</~~/hg~~code> Create a release tarball and the HTML documentation for [[Octave Forge]] (takes a while).* <code~~.sf.net~~>make check</~~p/octave/interval octave~~code> Run the full test-~~interval~~suite to verify that code changes didn't break anything (takes a while).~~ cd octave-interval; ~~* <code>make run</code> Quickly start Octave with minimal recompilation and functions loaded from the workspace (for interactive testing of code changes).

=== ~~Input and output ~~Architecture ===~~Before exercising interval arithmetic, interval objects must be created from non-interval data. There are interval constants <code>empty</code> and <code>entire</code> and the interval constructors <code>infsupdec</code> (create an interval from boundaries), <code>midrad</code> (create an interval from midpoint and radius) and <code>hull</code> (create an interval enclosure for a list of mixed arguments: numbers, intervals or interval literals). The 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.~~

if (not (isa (x, "infsupdec"))) x =infsupdec (x); endif if (not (isa (y, "infsupdec"))) y =~~== Interval vectors and matrices ====~~infsupdec (y);~~Vectors and matrices of intervals can be created by passing numerical matrices, char vectors or cell arrays to the interval constructors. With cell arrays it is also possible to mix several types of boundaries.~~ endif

=== ~~Arithmetic operations ~~= Vectorization & Indexing ====~~The interval packages comprises many interval arithmetic operations~~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. ~~A complete list can ~~inf, y.inf, x.sup, y.sup may be ~~found in its [http://octave~~vectors or matrices) and then uses an indexing expression to adjust values where empty intervals would have produces problematic values. function x = plus (x, y) .~~sourceforge~~.~~net/interval/overview~~.~~html function reference]~~parameter checking ... l = mpfr_function_d ('plus', -inf, x.inf, y.inf); u = mpfr_function_d ('plus', +inf, x. ~~Function names match GNU Octave standard functions where applicable and follow recommendations by IEEE 1788 otherwise~~sup, ~~cf~~y. ~~[[#IEEE_1788_index~~sup); emptyresult = isempty (x) |~~IEEE 1788 index]].~~isempty (y); l(emptyresult) = inf; u(emptyresult) = -inf; … endfunction

|-

| ~~interval:PossiblyUndefined~~verregsing|style="~~vertical-align~~color:~~top~~red" | ~~Interval construction with boundaries in decimal format~~trapped| dependency <code>verifylss</code> is implemented as <code>mldivide</code>; depends on <code>isspd</code> (by Rump, to be checked) and ~~the constructor can't decide whether the lower boundary is smaller than the upper boundary~~<code>verintervalhull</code>; see also [http://uivtx. ~~Both boundaries are very close and lie between subsequent binary64 numbers~~cs.~~|style="vertical-align:top" | The constructed interval is a valid and tight enclosure of both numbers~~cas. ~~If the lower boundary was actually greater than the upper boundary, this illegal interval is not considered an error~~cz/~rohn/publist/singreg.pdf]

|-

| ~~interval:ImplicitPromote~~~~|style~~colspan="~~vertical-align:top~~3" | ~~An interval operation has been evaluated on both, a bare and a decorated interval. The bare interval has been converted into a decorated interval in order to produce a decorated result. Note: This warning does not occur if a bare interval literal string gets promoted into a decorated interval, e. g., <code>infsupdec (1, 2) + "[3, 4]"</code> does not produce this warning whereas <code>infsupdec ~~Interval (~~1, 2~~or real) ~~+ infsup (3, 4)</code> does. A bare interval can be explicitly promoted with the newdec [http~~data:~~//octave.sourceforge.net/interval/function/@infsup/newdec.html] function.~~~~|style="vertical-align~~Matrices:~~top" | The implicit conversion applies the best possible decoration for the bare interval. If the bare interval has been produced from an interval arithmetic computation, this branch of computation is not covered by the decoration information ~~Eigenvalues and ~~the final decoration could be considered wrong. For example, <code>infsupdec (1, 2) + infsup (0, 1) ^ 0</code> would ignore that 0<sup>0</sup> is undefined.~~singular values

|-

| ~~interval:NaI~~vereigsym|style="~~vertical-align~~color:~~top~~red" | ~~An error has occured during interval construction and the NaI object has been produced. The warning text contains further details. A NaI can be explicitly created with the nai [http://octave.sourceforge.net/interval/function/nai.html] function.~~trapped|~~style="vertical-align:top" | Nothing bad is going to happen, because the semantics of NaI are well defined by IEEE 1788. However, the user might choose to cancel the algorithm immediately when the NaI is encountered for the first time.~~~~|}~~ ~~=== Decorations ===~~~~The interval package provides a powerful decoration system for intervals, as specified by the IEEE standard for interval arithmetic. By default any interval carries a decoration, which collects additional information about the course of function evaluation on the interval data.~~ ~~Only the (unfavored) ~~main part implemented in <code>~~infsup~~vereig</code> ~~constructor creates bare~~, ~~undecorated intervals and the ~~depends on <codestyle="color:red">~~intervalpart~~verspectrad</code> ~~operation may be used to demote decorated intervals into bare, undecorated ones. It is highly recommended to always use the decorated interval arithmetic, which gives additional information about an interval result in exchange for a tiny overhead.~~ ~~The following decorations are available:~~ ~~{| class="wikitable" style="margin: auto"~~~~!Decoration~~~~!Bounded~~~~!Continuous~~~~!Defined~~~~!Definition~~

|-

| ~~com<br/>(common)~~vereigval| style="~~text-align~~color: ~~center~~red" | ~~✓~~trapped| depends on <code style="~~text-align~~color: ~~center~~red" ~~| ✓~~~~| style="text-align: center" | ✓~~~~| '''''x''''' is a bounded, nonempty subset of Dom(''f''); ''f'' is continuous at each point of '''''x'''''; and the computed interval ''f''('''''x''''') is bounded~~>verregsing</code>

|-

| ~~dac~~<~~br~~s>vereigvec</s>~~(defined & continuous)~~~~|~~~~| style="text-align: center" | ✓~~| style="~~text-align~~color: ~~center~~green" | ~~✓~~~~| '''''x''''' is a nonempty subset of Dom(''f''); and the restriction of ''f'' to '''''x''''' is continuous~~free, migrated

|-

| ~~def<br/>(defined)~~~~|~~~~|~~verperrvec| style="~~text-align~~color: ~~center~~green" | ~~✓~~free| ~~'''''x''''' ~~the function is just a ~~nonempty subset of Dom(''f'')~~wrapper around <code style="color:green">vereigvec</code>?!?

|-

| ~~trv<br/>(trivial)~~versingval|style="color:red"|trapped|~~| always true (so gives no information)~~depends on <code style="color:red">vereigsym</code>

|-

| ~~ill<br/>(ill-formed)~~~~|~~~~|~~~~|~~~~| Not an interval, at least one interval constructor failed during the course of computation~~~~|}~~ ~~The decoration information is especially useful after a very long and complicated function evaluation. For example, when the “def” decoration survives until the final result, it is proven that the overall function is actually defined for all values covered by the input intervals.~~ ~~{{Code|Examples of using the decoration system|<syntaxhighlight lang~~colspan="~~octave">~~~~x = infsupdec (~~3~~, 4) # [3, 4]_com~~~~y = x - 3.5 # [-0.5, +0.5]_com~~~~## The square root function ignores any negative part of the input,~~~~## but the decoration indicates whether this has or has not happened.~~~~sqrt (x) # [1.732050807568877, 2]_com~~~~sqrt (y) # [0, 0.7071067811865476]_trv~~~~</syntaxhighlight>~~~~}}~~ ~~=== Specialized interval constructors ===~~~~Above mentioned interval construction with decimal numbers or numeric data is straightforward. Beyond that, there are more ways to define intervals or interval boundaries.~~~~* Hexadecimal-floating-constant form: Each interval boundary may be defined by a hexadecimal number (optionally containing a point) and an exponent field with an integral power of two as defined by the C99 standard ([http://www.open-std.org/jtc1/sc22/WG14/www/docs/n1256.pdf ISO/IEC9899, N1256, §6.4.4.2]). This can be used as a convenient way to define interval boundaries in double-precision, because the hexadecimal form is much shorter than the decimal representation of many numbers.~~~~* Rational literals: Each interval boundary may be defined as a fraction of two decimal numbers. This is especially useful if interval boundaries shall be tightest enclosures of fractions, that would be hard to write down as a decimal number.~~~~* Uncertain form: The interval as a whole can be defined by a midpoint or upper/lower boundary and an integral number of [http://en.wikipedia.org/wiki/Unit_in_the_last_place “units in last place” (ULPs)] as an uncertainty. The format is <code>''m''?''ruE''</code>, where~~~~** <code>''m ''</code> is a mantissa in decimal,~~~~** <code>''r ''</code> is either empty (which means ½ ULP) or is a non-negative decimal integral ULP count or is the <code>?</code> character (for unbounded intervals),~~~~** <code>''u ''</code> is either empty (symmetrical uncertainty of ''r'' ULPs in both directions) or is either <code>u</code> (up) or <code>d</code> (down),~~~~** <code>''E ''</code> is either empty or an exponent field comprising the character <code>e</code> followed by a decimal integer exponent (base 10).~~ ~~{{Code|Examples of different formats during interval construction|<syntaxhighlight lang=~~"~~octave">~~~~infsup ("0x1.999999999999Ap-4") # hex-form~~~~ # [0.1, 0.1000000000000001]~~~~infsup ("1/3", "7/9") # rational form~~~~ # [0.3333333333333333, 0.7777777777777778]~~~~infsup ("121.2?") # uncertain form~~~~ # [121.14999999999999, 121.25]~~~~infsup ("5?32e2") # uncertain form with ulp count~~~~ # [-2700, +3700]~~~~infsup ("-42??u") # unbound uncertain form~~~~ # [-42, +Inf]~~~~</syntaxhighlight>~~~~}}~~ ~~=== Reverse arithmetic operations ===~~~~[[File:Reverse-power-functions.png~~|~~400px|thumb|right|Reverse power operations. A relevant subset of the function's domain is outlined and hatched. In this example we use ''x''<sup>''y''</sup> ∈ [2, 3].]]~~ ~~Some arithmetic functions also provide reverse mode operations. That is inverse functions with interval constraints. For example the <code>sqrrev</code> can compute the inverse of the <code>sqr</code> function on intervals. The syntax is <code>sqrrev ~~Interval (~~C, X)</code> and will compute the enclosure of all numbers ''x'' ∈ X that fulfill the constraint ''x''² ∈ C.~~ ~~In the following example, we compute the constraints for base and exponent of the power function <code>pow</code> as shown in the figure.~~~~ <span style="opacity:.5">octave:1> </span>x = powrev1 (infsup ("[1.1, 1.45]"), infsup (2, 3))~~~~ x ⊂ [1.6128979635153646, 2.714854726565793]~~~~ <span style="opacity:.5">octave:2> </span>y = powrev2 (infsup ("[2.14, 2.5]"), infsup (2, 3))~~~~ y ⊂ [0.7564707973660299, 1.4440113978403289]~~ ~~=== Tips & Tricks ===~~~~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.~~ ~~ <span style="opacity:.5">octave:1> </span>infsupdec ("17.7") + 1~~~~ ans ⊂ [18.699999999999999, 18.70000000000001]_com~~~~ <span style="opacity:.5">octave:2> </span>ans + "[0, 2]"~~~~ ans ⊂ [18.699999999999999, 20.70000000000001]_com~~ ~~Interval functions with only one argument can be called by using property syntax, e. g. <code>x.inf</code>, <code>x.sup</code> ~~or ~~even <code>x.sqr</code>.~~ ~~When matrices are resized using subscripted assignment, any implicit new matrix elements will carry an empty interval.~~~~ <span style="opacity:.5">octave:1> </span>M = infsup (magic (3~~real)~~); M (4, 4) = 42~~~~ M = 4×4 interval matrix~~~~ ~~~~ [8] [1] [6] [Empty]~~~~ [3] [5] [7] [Empty]~~~~ [4] [9] [2] [Empty]~~~~ [Empty] [Empty] [Empty] [42]~~ ~~Whilst most functions (<code>size</code>, <code>isvector</code>, <code>ismatrix</code>, …) work as expected on interval ~~data ~~types, the function <code>isempty</code> is evaluated element-wise and checks if an interval equals the empty set.~~~~ <span style="opacity~~:~~.5">octave~~Matrices:~~1> </span>builtin ("isempty", empty ()), isempty (empty ())~~~~ ans = 0~~~~ ans = 1~~ ~~== IEEE 1788 index ==~~ ~~{| class="wikitable" style="margin: auto; min-width: 50%"~~~~|+ In terms of a better integration into the GNU Octave language, several operations use a function name which is different from the name proposed in the standard document.~~~~!IEEE 1788~~~~!GNU Octave~~Decompositions

|-

| ~~numsToInterval~~verqr (experimental)| ~~bare version~~style="color: ~~infsup (''l'', ''u'') [http://octave.sourceforge.net/interval/function/@infsup/infsup.html]~~green"| free| <code>qr<~~br~~/code>~~decorated version: infsupdec (''l''~~has already been implemented using the Gram-Schmidt process, ~~''u'') [http://octave.sourceforge~~which seems to be more accurate and faster than the Cholsky decomposition or Householder reflections used in verqr.~~net/interval/function/@infsupdec/infsupdec~~No migration needed.~~html]~~

|-

| ~~textToInterval~~<s>verchol (experimental)</s>|style="color:green"| free, migrated| ~~bare ~~migrated version~~: infsup (''s'')~~has been named after the standard Octave function <code>chol<~~br~~/code>~~decorated version: infsupdec (''s'')~~

|-

| ~~setDec~~colspan="3"| ~~infsupdec ~~Interval (~~''x'', ''dx''~~or real) data: Linear systems (square)

|-

| ~~exp10~~verenclinthull| ~~pow10 [http~~style="color:~~//octave.sourceforge.net/interval/function/@infsup/pow10.html]~~green"| free| to be migrated

|-

| ~~exp2~~verhullparam| ~~pow2 [http~~style="color:green"| free| depends on <code>verintervalhull</~~/octave.sourceforge.net/interval/function/@infsup/pow2.html]~~code>, to be migrated

|-

| ~~recip~~verhullpatt| ~~inv [http~~style="color:green"| free| depends on <code>verhullparam</~~/octave.sourceforge.net/interval/function/@infsup/inv.html]~~code>, to be migrated

|-

| ~~sqrt~~verintervalhull| ~~realsqrt [http~~style="color:~~//octave.sourceforge.net/interval/function/@infsup/realsqrt.html]~~green"| free| to be migrated

|-

| ~~rootn~~colspan="3"| ~~nthroot [http~~Interval (or real) data:~~//octave.sourceforge.net/interval/function/@infsup/nthroot.html]~~Linear systems (rectangular)

|-

| ~~logp1~~verintlinineqs| ~~log1p [http~~style="color:green"| free| depends on <code style="color:green">verlinineqnn</~~/octave.sourceforge.net/interval/function/@infsup/log1p.html]~~code>

|-

| ~~roundTiesToAway~~veroettprag| ~~round [http~~style="color:~~//octave.sourceforge.net/interval/function/@infsup/round.html]~~green"| free

|-

| ~~roundTiesToEven~~vertolsol| ~~roundb [http~~style="color:green"| free| depends on <code style="color:green">verlinineqnn</~~/octave.sourceforge.net/interval/function/@infsup/roundb.html]~~code>

|-

| ~~trunc~~colspan="3"| ~~fix [http~~Interval (or real) data:~~//octave.sourceforge.net/interval/function/@infsup/fix.html]~~Matrix equations (rectangular)

|-

| ~~sum~~vermatreqn| ~~on intervals~~style="color: ~~sum [http://octave.sourceforge.net/interval/function/@infsup/sum.html]<br/>on numbers: mpfr_vector_sum_d [http://octave.sourceforge.net/interval/function/mpfr_vector_sum_d.html]~~green"| free

|-

| ~~dot~~colspan="3"| ~~on intervals~~Real data only: ~~dot [http://octave.sourceforge.net/interval/function/@infsup/dot.html]<br/>on numbers: mpfr_vector_dot_d [http://octave.sourceforge.net/interval/function/mpfr_vector_dot_d.html]~~Uncommon problems

|-

| ~~sumAbs~~plusminusoneset| ~~on intervals~~style="color: ~~sumabs [http://octave.sourceforge.net/interval/function/@infsup/sumabs.html]<br/>on numbers: mpfr_vector_sum_d (''rounding mode'', abs (''x''))~~green"| free

|-

| ~~sumSquare~~verabsvaleqn| ~~on intervals~~style="color: ~~sumsq [http://octave.sourceforge.net/interval/function/@infsup/sumsq.html]<br/>on numbers: mpfr_vector_dot_d (''rounding mode'', abs (''x''), abs (''x''))~~green"| free| to be migrated

|-

| ~~intersection~~verabsvaleqnall| ~~intersect ~~style="color:green"| free| depends on <code>verabsvaleqn</code>, see also [http://~~octave~~uivtx.~~sourceforge~~cs.~~net/interval~~cas.cz/~~function~~~rohn/~~@infsup~~publist/~~intersect~~absvaleqnall.~~html~~pdf], to be migrated

|-

| ~~convexHull~~verbasintnpprob| ~~union [http~~style="color:red"| trapped| depends on <code style="color:red">verregsing</~~/octave.sourceforge.net/interval/function/@infsup/union.html]~~code>

|-

|}

[[Category:Octave~~-~~Forge]]

Retrieved from "https://wiki.octave.org/Special:MobileDiff/6168...11977"

- Not logged in
- Talk
- Contributions
- Create account
- Log in