Changes

Jump to navigation Jump to search
68 bytes removed ,  11:52, 18 January 2015
m
→‎What to expect: Typo & formatting
{| class="wikitable" style="margin: auto; align:right"
|+align="bottom" | Approximate runtime (wall clock time in seconds) on an <br/>Intel® Core™ i5-4340M CPU(2.9 GHz)
!Matrix dimension
!Interval <code>plus</code>
!Interval <code>inv</code>
|-
|align="right"| 10
|align="right"| < 0.1
|align="right"| < 0.1
|align="right"| 3.3
|-
|align="right"| 20
|align="right"| < 0.1
|align="right"| < 0.1
|style="text-align:right; font-weight: bold; color:orange"| 32.3
|-
|align="right"| 30
|align="right"| < 0.1
|align="right"| < 0.1
|style="text-align:right; font-weight: bold; color:red"| 142.1
|-
|align="right"| 40
|align="right"| < 0.1
|align="right"| 0.1
|align="right"| 15.6
|
|-
|align="right"| 50
|align="right"| 0.1
|align="right"| 0.2
|style="text-align:right; font-weight: bold; color:orange"| 29.1
|
|}
''Why is the interval package accurate?''
The GNU Octave builtin built-in floating-point routines are not useful for interval arithmetic: Their results depend on hardware, system libraries and compilation options.  
The interval package handles all arithmetic functions with the help of the [http://www.mpfr.org/ GNU MPFR library]. With MPFR it is possible to compute system-independent, valid and tight enclosures of the correct results.
240

edits

Navigation menu