Sensitivities for Guiding Refinement in Arbitrary-Precision Arithmetic

Total Page:16

File Type:pdf, Size:1020Kb

Sensitivities for Guiding Refinement in Arbitrary-Precision Arithmetic Sensitivities for Guiding Refinement in Arbitrary-Precision Arithmetic by Jesse Michel B.S., Massachusetts Institute of Technology (2019) Submitted to the Department of Electrical Engineering and Computer Science in partial fulfillment of the requirements for the degree of Master of Engineering in Electrical Engineering and Computer Science at the MASSACHUSETTS INSTITUTE OF TECHNOLOGY May 2020 © Massachusetts Institute of Technology 2020. All rights reserved. Author.................................................................... Department of Electrical Engineering and Computer Science May 18, 2020 Certified by . Michael Carbin Jamieson Career Development Assistant Professor of Electrical Engineering and Computer Science Thesis Supervisor Accepted by............................................................... Katrina LaCurts Chair, Master of Engineering Thesis Committee 2 Sensitivities for Guiding Refinement in Arbitrary-Precision Arithmetic by Jesse Michel Submitted to the Department of Electrical Engineering and Computer Science on May 18, 2020, in partial fulfillment of the requirements for the degree of Master of Engineering in Electrical Engineering and Computer Science Abstract Programmers often develop and analyze numerical algorithms assuming that they operate on real numbers, but implementations generally use floating-point approximations. Arbitrary- precision arithmetic enables developers to write programs that operate over reals: given an output error bound, the program will produce a result within that bound. A key drawback of arbitrary-precision arithmetic is its speed. Fast implementations of arbitrary-precision arithmetic use interval arithmetic (which provides a lower and upper bound for all vari- ables and expressions in a computation) computed at successively higher precisions until the result is within the error bound. Current approaches refine computations at precisions that increase uniformly across the computation rather than changing precisions per-variable or per-operator. This thesis proposes a novel definition and implementation of derivatives through interval code that I use to create a sensitivity analysis. I present and analyze the critical path algorithm, which uses sensitivities to guide precision refinements in the compu- tation. Finally, I evaluate this approach empirically on sample programs and demonstrate its effectiveness. Thesis Supervisor: Michael Carbin Title: Jamieson Career Development Assistant Professor of Electrical Engineering and Computer Science 3 4 Acknowledgments I thank my advisor Michael Carbin. He helped guide the intuition and motivation that shaped this thesis and provided useful feedback and guidance on the experimental results. I would also like to thank Ben Sherman for helping to develop technical aspects of this thesis, for making the time to review my writing, and for his guidance throughout the research process. Alex Renda, Rogers Epstein, Stefan Grosser, and Nina Thacker provided useful feedback. I am grateful for the financial support that I have received from NSF grant CCF- 1751011. I thank my parents, sisters, and extended family for their love and support and my nephew Joseph for being a shining light in my life. 5 6 Contents 1 Introduction 13 1.1 Motivating example . 15 1.2 Thesis . 17 1.3 Outline . 17 2 Background on Interval Arithmetic 19 2.1 Interval addition . 20 2.2 Interval multiplication . 20 2.3 Interval sine . 21 2.4 Analysis . 23 3 Sensitivities for Precision Refinement 25 3.1 A baseline schedule . 26 3.2 Sensitivities from derivatives . 27 3.2.1 Constructing sensitivities . 27 3.2.2 Sensitivity as a derivative . 28 3.2.3 Introducing a cost model . 29 3.3 A schedule using sensitivities . 30 3.4 Analysis . 31 3.4.1 Uniform schedule . 32 3.4.2 Critical path schedule . 32 3.4.3 Cost-modeled schedule . 33 3.4.4 A comparison of schedules . 34 7 4 Automatic Differentiation of Interval Arithmetic 37 4.1 Introduction to automatic differentiation . 37 4.2 Automatic differentiation on intervals . 38 4.2.1 Derivative of interval addition . 39 4.2.2 Derivative of interval multiplication . 40 4.2.3 Derivative of interval sine . 41 4.3 Analysis . 42 5 Results 45 5.1 Schedules . 45 5.1.1 Baseline schedule . 45 5.1.2 Critical path schedule . 46 5.2 Empirical comparison . 46 5.2.1 Improving a configuration . 46 5.2.2 Improving a schedule . 47 5.3 Implementation . 48 6 Related Work 49 6.1 Mixed-precision tuning and sensitivity analysis . 50 6.2 Arbitrary-precision arithmetic . 50 6.2.1 Pull-based approaches . 51 6.2.2 Push-based approaches . 51 7 Discussion and Future Work 53 7.1 Benchmarks . 53 7.2 Further improving precision refinement . 54 7.2.1 Per-primitive cost modeling . 54 7.2.2 Unexplored trade-offs in precision refinement . 55 7.2.3 Generalizing the critical path algorithm . 56 7.3 New applications to experimental research . 56 8 Conclusions 57 8 List of Figures 1-1 Example of a uniform configuration . 15 1-2 Derivatives of the computation in Figure 1-1. 16 1-3 Sensitivities of the computation in Figure 1-1 . 16 1-4 Example of a non-uniform configuration . 16 2-1 The four key monotonic regions for the definition of interval sine. 22 2-2 A simple Python implementation of interval sin. 23 3-1 Computation graph for theoretical analysis . 31 4-1 Reverse-mode automatic differentiation on intervals. 39 4-2 Interval addition with derivatives. 40 9 10 List of Tables 3.1 Theoretical comparison of schedules . 35 5.1 Comparison of precisions for configurations . 47 5.2 Comparison of error and time for configurations . 47 7.1 FPBench benchmark results. 55 11 12 Chapter 1 Introduction Floating-point computations can produce arbitrarily large errors. For example, Python implements the IEEE-754 standard, which produces the following behavior for 64-bit floating- point numbers: >>> 1 + 1e17 - 1e17 0.0 The result of this computation is 0 instead of 1! This leads to an arbitrarily large error in results; for example, (1 + 1e17 − 1e17)푥 will be always be 0 instead of 푥. Resilience to numerical-computing error is especially desirable for safety-critical software such as control systems for vehicles, medical equipment, and industrial plants, which are known to produce incorrect results because of numerical errors [12]. In contrast to floating-point arithmetic, arbitrary-precision arithmetic computes a result within a given error bound. Concretely, given the function 푦 = 푓(푥) and an error bound 휖, arbitrary-precision arithmetic produces a result 푦˜ such that |푦˜ − 푦| < 휖. Arbitrary-precision primitives It is necessary to use a data-type that supports arbi- trary rational numbers in order to refine to arbitrarily small error. I chose to use a multiple- precision floating-point implemented in MPFR [14]. To understand the representation, con- 13 sider the example of representing 휋 to 5 mantissa bits: exponent ⏞ ⏟ −3 11.0012 = 110012 ×2 . ⏟ ⏞ mantissa The exponent automatically adjusts as appropriate, so requesting 10 mantissa bits of preci- sion results in −8 11.001001002 = 11001001002 × 2 . Since the exponent adjusts automatically, I focus on setting the number of mantissa bits for the variables and operators in the computation. For the rest of the thesis, bits of precision will denote mantissa bits. Implementing arbitrary-precision arithmetic The push-based approach to implement- ing arbitrary-precision sets the precisions at which to compute each variable and operator and computes the error in the output. It then refines results at increasingly high precisions until the result is within the given error bound. Each pass through the computation uses interval arithmetic, which computes error bounds by “pushing” bounds from the leaves of the computation graph up to the root. For example, assuming no error in addition, ; works such that [1, 2] ; [3, 4] = [4, 6]. 2 More realistically, suppose that the function +푝 : R × R → R for bounded addition at pre- cision 푝. Then, +푝 and +푝 compute the lower and upper bound for adding inputs truncated to precision 푝. They satisfy the property that for all 푎, 푏 ∈ R, (푎 +푝 푏) ≤ (푎 + 푏) ≤ (푎 +푝 푏) where + is exact and where as 푝 → ∞ the inequality becomes an equality. Assuming error in addition, [1, 2] ;푝 [3, 4] = [1 +푝 3, 2 +푝 4], which will always have a lower bound ≤ 4 and an upper bound ≥ 6. Computing constants such as 휋 or 푒 makes the need for this type of approximation clearer since it requires infinite space to represent them exactly (since 휋 and 푒 are transcendental). However, they are soundly computed using arbitrary-precision arithmetic. 14 1.1 Motivating example Current push-based implementations refine precisions uniformly across the computation graph [30, 25]. Concretely, this means setting all variables and operators to the same preci- sion (e.g. 1 mantissa bit) and if the error bound is not satisfied, repeating the computation at a higher precision (e.g. 2 mantissa bits). This means that certain variables and operators are computed to a high precision even when they contribute little to the error – an inefficient allocation of compute resources. For example, consider computing 푒 + 1000휋 to a generous error bound of 500. Existing approaches refine precision uniformly across vari- ables and operators [30, 25]. In the best case scenario, these approaches require 5 mantissa bits for ;, 푒, 5, and 휋 (since 푘 is a constant, it remains at a fixed precision). Note that ; and 5 are the addition and multiplication operators over intervals respectively, described in detail in Chapter 2. An example of this computation is shown in Figure 1-1. Suppose the ; [3070, 3460] 푒 [2.62, 2.75] 5 [3070, 3330] 푘 [1000, 1000] 휋 [3.12, 3.25] Figure 1-1: The figure presents a computation graph evaluated at a uniform precision of5 mantissa bits of precision (except for the constant 푘) with an error of 3460 − 2070 = 390. approach to precision-refinement is to start at a uniform precision of 1 mantissa bit,and then increment precisions (mantissa bits) until the error bound is satisfied.
Recommended publications
  • Variable Precision in Modern Floating-Point Computing
    Variable precision in modern floating-point computing David H. Bailey Lawrence Berkeley Natlional Laboratory (retired) University of California, Davis, Department of Computer Science 1 / 33 August 13, 2018 Questions to examine in this talk I How can we ensure accuracy and reproducibility in floating-point computing? I What types of applications require more than 64-bit precision? I What types of applications require less than 32-bit precision? I What software support is required for variable precision? I How can one move efficiently between precision levels at the user level? 2 / 33 Commonly used formats for floating-point computing Formal Number of bits name Nickname Sign Exponent Mantissa Hidden Digits IEEE 16-bit “IEEE half” 1 5 10 1 3 (none) “ARM half” 1 5 10 1 3 (none) “bfloat16” 1 8 7 1 2 IEEE 32-bit “IEEE single” 1 7 24 1 7 IEEE 64-bit “IEEE double” 1 11 52 1 15 IEEE 80-bit “IEEE extended” 1 15 64 0 19 IEEE 128-bit “IEEE quad” 1 15 112 1 34 (none) “double double” 1 11 104 2 31 (none) “quad double” 1 11 208 4 62 (none) “multiple” 1 varies varies varies varies 3 / 33 Numerical reproducibility in scientific computing A December 2012 workshop on reproducibility in scientific computing, held at Brown University, USA, noted that Science is built upon the foundations of theory and experiment validated and improved through open, transparent communication. ... Numerical round-off error and numerical differences are greatly magnified as computational simulations are scaled up to run on highly parallel systems.
    [Show full text]
  • A Library for Interval Arithmetic Was Developed
    1 Verified Real Number Calculations: A Library for Interval Arithmetic Marc Daumas, David Lester, and César Muñoz Abstract— Real number calculations on elementary functions about a page long and requires the use of several trigonometric are remarkably difficult to handle in mechanical proofs. In this properties. paper, we show how these calculations can be performed within In many cases the formal checking of numerical calculations a theorem prover or proof assistant in a convenient and highly automated as well as interactive way. First, we formally establish is so cumbersome that the effort seems futile; it is then upper and lower bounds for elementary functions. Then, based tempting to perform the calculations out of the system, and on these bounds, we develop a rational interval arithmetic where introduce the results as axioms.1 However, chances are that real number calculations take place in an algebraic setting. In the external calculations will be performed using floating-point order to reduce the dependency effect of interval arithmetic, arithmetic. Without formal checking of the results, we will we integrate two techniques: interval splitting and taylor series expansions. This pragmatic approach has been developed, and never be sure of the correctness of the calculations. formally verified, in a theorem prover. The formal development In this paper we present a set of interactive tools to automat- also includes a set of customizable strategies to automate proofs ically prove numerical properties, such as Formula (1), within involving explicit calculations over real numbers. Our ultimate a proof assistant. The point of departure is a collection of lower goal is to provide guaranteed proofs of numerical properties with minimal human theorem-prover interaction.
    [Show full text]
  • Signedness-Agnostic Program Analysis: Precise Integer Bounds for Low-Level Code
    Signedness-Agnostic Program Analysis: Precise Integer Bounds for Low-Level Code Jorge A. Navas, Peter Schachte, Harald Søndergaard, and Peter J. Stuckey Department of Computing and Information Systems, The University of Melbourne, Victoria 3010, Australia Abstract. Many compilers target common back-ends, thereby avoid- ing the need to implement the same analyses for many different source languages. This has led to interest in static analysis of LLVM code. In LLVM (and similar languages) most signedness information associated with variables has been compiled away. Current analyses of LLVM code tend to assume that either all values are signed or all are unsigned (except where the code specifies the signedness). We show how program analysis can simultaneously consider each bit-string to be both signed and un- signed, thus improving precision, and we implement the idea for the spe- cific case of integer bounds analysis. Experimental evaluation shows that this provides higher precision at little extra cost. Our approach turns out to be beneficial even when all signedness information is available, such as when analysing C or Java code. 1 Introduction The “Low Level Virtual Machine” LLVM is rapidly gaining popularity as a target for compilers for a range of programming languages. As a result, the literature on static analysis of LLVM code is growing (for example, see [2, 7, 9, 11, 12]). LLVM IR (Intermediate Representation) carefully specifies the bit- width of all integer values, but in most cases does not specify whether values are signed or unsigned. This is because, for most operations, two’s complement arithmetic (treating the inputs as signed numbers) produces the same bit-vectors as unsigned arithmetic.
    [Show full text]
  • Complete Interval Arithmetic and Its Implementation on the Computer
    Complete Interval Arithmetic and its Implementation on the Computer Ulrich W. Kulisch Institut f¨ur Angewandte und Numerische Mathematik Universit¨at Karlsruhe Abstract: Let IIR be the set of closed and bounded intervals of real numbers. Arithmetic in IIR can be defined via the power set IPIR (the set of all subsets) of real numbers. If divisors containing zero are excluded, arithmetic in IIR is an algebraically closed subset of the arithmetic in IPIR, i.e., an operation in IIR performed in IPIR gives a result that is in IIR. Arithmetic in IPIR also allows division by an interval that contains zero. Such division results in closed intervals of real numbers which, however, are no longer bounded. The union of the set IIR with these new intervals is denoted by (IIR). The paper shows that arithmetic operations can be extended to all elements of the set (IIR). On the computer, arithmetic in (IIR) is approximated by arithmetic in the subset (IF ) of closed intervals over the floating-point numbers F ⊂ IR. The usual exceptions of floating-point arithmetic like underflow, overflow, division by zero, or invalid operation do not occur in (IF ). Keywords: computer arithmetic, floating-point arithmetic, interval arithmetic, arith- metic standards. 1 Introduction or a Vision of Future Computing Computers are getting ever faster. The time can already be foreseen when the P C will be a teraflops computer. With this tremendous computing power scientific computing will experience a significant shift from floating-point arithmetic toward increased use of interval arithmetic. With very little extra hardware, interval arith- metic can be made as fast as simple floating-point arithmetic [3].
    [Show full text]
  • MPFI: a Library for Arbitrary Precision Interval Arithmetic
    MPFI: a library for arbitrary precision interval arithmetic Nathalie Revol Ar´enaire (CNRS/ENSL/INRIA), LIP, ENS-Lyon and Lab. ANO, Univ. Lille [email protected] Fabrice Rouillier Spaces, CNRS, LIP6, Univ. Paris 6, LORIA-INRIA [email protected] SCAN 2002, Paris, France, 24-27 September Reliable computing: Interval Arithmetic (Moore 1966, Kulisch 1983, Neumaier 1990, Rump 1994, Alefeld and Mayer 2000. ) Numbers are replaced by intervals. Ex: π replaced by [3.14159, 3.14160] Computations: can be done with interval operands. Advantages: • Every result is guaranteed (including rounding errors). • Data known up to measurement errors are representable. • Global information can be reached (“computing in the large”). Drawbacks: overestimation of the results. SCAN 2002, Paris, France - 1 N. Revol & F. Rouillier Hansen’s algorithm for global optimization Hansen 1992 L = list of boxes to process := {X0} F : function to minimize while L= 6 ∅ loop suppress X from L reject X ? yes if F (X) > f¯ yes if GradF (X) 63 0 yes if HF (X) has its diag. non > 0 reduce X Newton applied with the gradient solve Y ⊂ X such that F (Y ) ≤ f¯ bisect Y into Y1 and Y2 if Y is not a result insert Y1 and Y2 in L SCAN 2002, Paris, France - 2 N. Revol & F. Rouillier Solving linear systems preconditioned Gauss-Seidel algorithm Hansen & Sengupta 1981 Linear system: Ax = b with A and b given. Problem: compute an enclosure of Hull (Σ∃∃(A, b)) = Hull ({x : ∃A ∈ A, ∃b ∈ b, Ax = b}). Hansen & Sengupta’s algorithm compute C an approximation of mid(A)−1 apply Gauss-Seidel to CAx = Cb until convergence.
    [Show full text]
  • Floating Point Computation (Slides 1–123)
    UNIVERSITY OF CAMBRIDGE Floating Point Computation (slides 1–123) A six-lecture course D J Greaves (thanks to Alan Mycroft) Computer Laboratory, University of Cambridge http://www.cl.cam.ac.uk/teaching/current/FPComp Lent 2010–11 Floating Point Computation 1 Lent 2010–11 A Few Cautionary Tales UNIVERSITY OF CAMBRIDGE The main enemy of this course is the simple phrase “the computer calculated it, so it must be right”. We’re happy to be wary for integer programs, e.g. having unit tests to check that sorting [5,1,3,2] gives [1,2,3,5], but then we suspend our belief for programs producing real-number values, especially if they implement a “mathematical formula”. Floating Point Computation 2 Lent 2010–11 Global Warming UNIVERSITY OF CAMBRIDGE Apocryphal story – Dr X has just produced a new climate modelling program. Interviewer: what does it predict? Dr X: Oh, the expected 2–4◦C rise in average temperatures by 2100. Interviewer: is your figure robust? ... Floating Point Computation 3 Lent 2010–11 Global Warming (2) UNIVERSITY OF CAMBRIDGE Apocryphal story – Dr X has just produced a new climate modelling program. Interviewer: what does it predict? Dr X: Oh, the expected 2–4◦C rise in average temperatures by 2100. Interviewer: is your figure robust? Dr X: Oh yes, indeed it gives results in the same range even if the input data is randomly permuted . We laugh, but let’s learn from this. Floating Point Computation 4 Lent 2010–11 Global Warming (3) UNIVERSITY OF What could cause this sort or error? CAMBRIDGE the wrong mathematical model of reality (most subject areas lack • models as precise and well-understood as Newtonian gravity) a parameterised model with parameters chosen to fit expected • results (‘over-fitting’) the model being very sensitive to input or parameter values • the discretisation of the continuous model for computation • the build-up or propagation of inaccuracies caused by the finite • precision of floating-point numbers plain old programming errors • We’ll only look at the last four, but don’t forget the first two.
    [Show full text]
  • Draft Standard for Interval Arithmetic (Simplified)
    IEEE P1788.1/D9.8, March 2017 IEEE Draft Standard for Interval Arithmetic (Simplified) 1 2 P1788.1/D9.8 3 Draft Standard for Interval Arithmetic (Simplified) 4 5 Sponsor 6 Microprocessor Standards Committee 7 of the 8 IEEE Computer Society IEEE P1788.1/D9.8, March 2017 IEEE Draft Standard for Interval Arithmetic (Simplified) 1 Abstract: TM 2 This standard is a simplified version and a subset of the IEEE Std 1788 -2015 for Interval Arithmetic and 3 includes those operations and features of the latter that in the the editors' view are most commonly used in 4 practice. IEEE P1788.1 specifies interval arithmetic operations based on intervals whose endpoints are IEEE 754 5 binary64 floating-point numbers and a decoration system for exception-free computations and propagation of 6 properties of the computed results. 7 A program built on top of an implementation of IEEE P1788.1 should compile and run, and give identical output TM 8 within round off, using an implementation of IEEE Std 1788 -2015, or any superset of the former. TM 9 Compared to IEEE Std 1788 -2015, this standard aims to be minimalistic, yet to cover much of the functionality 10 needed for interval computations. As such, it is more accessible and will be much easier to implement, and thus 11 will speed up production of implementations. TM 12 Keywords: arithmetic, computing, decoration, enclosure, interval, operation, verified, IEEE Std 1788 -2015 13 14 The Institute of Electrical and Electronics Engineers, Inc. 15 3 Park Avenue, New York, NY 10016-5997, USA 16 Copyright c 2014 by The Institute of Electrical and Electronics Engineers, Inc.
    [Show full text]
  • Interval Arithmetic to the C++ Standard Library (Revision 2)
    Doc No: N2137=06-0207 A Proposal to add Interval Arithmetic to the C++ Standard Library (revision 2) Hervé Brönnimann∗ Guillaume Melquiond† Sylvain Pion‡ 2006-11-01 Contents Contents 1 I History of changes to this document 2 II Motivation and Scope 3 III Impact on the Standard 4 IV Design Decisions 4 V Proposed Text for the Standard 9 26.6 Interval numbers . 10 26.6.1 Header <interval> synopsis . 10 26.6.2 interval numeric specializations . 14 26.6.3 interval member functions . 16 26.6.4 interval member operators . 17 26.6.5 interval non-member operations . 18 26.6.6 bool_set comparisons . 18 26.6.7 Possibly comparisons . 19 26.6.8 Certainly comparisons . 20 26.6.9 Set inclusion comparisons . 21 26.6.10 interval IO operations . 22 26.6.11 interval value operations . 22 26.6.12 interval set operations . 23 26.6.13 interval mathematical functions . 24 26.6.14 interval mathematical partial functions . 28 26.6.15 interval mathematical relations . 29 26.6.16 interval static value operations . 30 VI Examples of usage of the interval class. 30 VI.1 Unidimensional solver . 31 VI.2 Multi-dimensional solver . 32 VII Acknowledgements 33 References 34 ∗CIS, Polytechnic University, Six Metrotech, Brooklyn, NY 11201, USA. [email protected] †École Normale Supérieure de Lyon, 46 allée d’Italie, 69364 Lyon cedex 07, France. [email protected] ‡INRIA, BP 93, 06902 Sophia Antipolis cedex, France. [email protected] 1 I History of changes to this document Since revision 1 (N2067=06-0137) : — Added nth_root and nth_root_rel functions.
    [Show full text]
  • Interval Arithmetic with Fixed Rounding Mode
    NOLTA, IEICE Paper Interval arithmetic with fixed rounding mode Siegfried M. Rump 1 ,3 a), Takeshi Ogita 2 b), Yusuke Morikura 3 , and Shin’ichi Oishi 3 1 Institute for Reliable Computing, Hamburg University of Technology, Schwarzenbergstraße 95, Hamburg 21071, Germany 2 Division of Mathematical Sciences, Tokyo Woman’s Christian University, 2-6-1 Zempukuji, Suginami-ku, Tokyo 167-8585, Japan 3 Faculty of Science and Engineering, Waseda University, 3-4-1 Okubo, Shinjuku-ku, Tokyo 169–8555, Japan a) [email protected] b) [email protected] Received December 10, 2015; Revised March 25, 2016; Published July 1, 2016 Abstract: We discuss several methods to simulate interval arithmetic operations using floating- point operations with fixed rounding mode. In particular we present formulas using only rounding to nearest and using only chop rounding (towards zero). The latter was the default and only rounding on GPU (Graphics Processing Unit) and cell processors, which in turn are very fast and therefore attractive in scientific computations. Key Words: rounding mode, chop rounding, interval arithmetic, predecessor, successor, IEEE 754 1. Notation There is a growing interest in so-called verification methods, i.e. algorithms with rigorous verification of the correctness of the result. Such algorithms require error estimations of the basic floating-point operations. A specifically convenient way to do this is using rounding modes as defined in the IEEE 754 floating- point standard [1]. In particular performing an operation in rounding downwards and rounding upwards computes the narrowest interval with floating-point bounds including the correct value of the operation. However, such an approach requires frequent changing of the rounding mode.
    [Show full text]
  • An Interval Component for Continuous Constraints Laurent Granvilliers
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Elsevier - Publisher Connector Journal of Computational and Applied Mathematics 162 (2004) 79–92 www.elsevier.com/locate/cam An interval component for continuous constraints Laurent Granvilliers IRIN, Universiteà de Nantes, B.P. 92208, 44322 Nantes Cedex 3, France Received 29 November 2001; received in revised form 13 November 2002 Abstract Local consistency techniques for numerical constraints over interval domains combine interval arithmetic, constraint inversion and bisection to reduce variable domains.In this paper, we study the problem of integrating any speciÿc interval arithmetic library in constraint solvers.For this purpose, we design an interface between consistency algorithms and arithmetic.The interface has a two-level architecture: functional interval arithmetic at low-level, which is only a speciÿcation to be implemented by speciÿc libraries, and a set of operations required by solvers, such as relational interval arithmetic or bisection primitives.This work leads to the implementation of an interval component by means of C++ generic programming methods.The overhead resulting from generic programming is discussed. c 2003 Elsevier B.V. All rights reserved. Keywords: Interval arithmetic; Consistency techniques; Constraint solving; Generic programming; C++ 1. Introduction Interval arithmetic has been introduced by Ramon E.Moore [ 9] in the late 1960s to deal with inÿniteness, to model uncertainty, and to tackle rounding errors of numerical
    [Show full text]
  • Proceedings of the 7 Python in Science Conference
    Proceedings of the 7th Python in Science Conference SciPy Conference – Pasadena, CA, August 19-24, 2008. Editors: Gaël Varoquaux, Travis Vaught, Jarrod Millman Proceedings of the 7th Python in Science Conference (SciPy 2008) Contents Editorial 3 G. Varoquaux, T. Vaught, J. Millman The State of SciPy 5 J. Millman, T. Vaught Exploring Network Structure, Dynamics, and Function using NetworkX 11 A. Hagberg, D. Schult, P. Swart Interval Arithmetic: Python Implementation and Applications 16 S. Taschini Experiences Using SciPy for Computer Vision Research 22 D. Eads, E. Rosten The SciPy Documentation Project (Technical Overview) 27 S. Van der Walt Matplotlib Solves the Riddle of the Sphinx 29 M. Droettboom The SciPy Documentation Project 33 J. Harrington Pysynphot: A Python Re-Implementation of a Legacy App in Astronomy 36 V. Laidler, P. Greenfield, I. Busko, R. Jedrzejewski How the Large Synoptic Survey Telescope (LSST) is using Python 39 R. Lupton Realtime Astronomical Time-series Classification and Broadcast Pipeline 42 D. Starr, J. Bloom, J. Brewer Analysis and Visualization of Multi-Scale Astrophysical Simulations Using Python and NumPy 46 M. Turk Mayavi: Making 3D Data Visualization Reusable 51 P. Ramachandran, G. Varoquaux Finite Element Modeling of Contact and Impact Problems Using Python 57 R. Krauss Circuitscape: A Tool for Landscape Ecology 62 V. Shah, B. McRae Summarizing Complexity in High Dimensional Spaces 66 K. Young Converting Python Functions to Dynamically Compiled C 70 I. Schnell 1 unPython: Converting Python Numerical Programs into C 73 R. Garg, J. Amaral The content of the articles of the Proceedings of the Python in Science Conference is copyrighted and owned by their original authors.
    [Show full text]
  • Complete Interval Arithmetic and Its Implementation on the Computer
    Complete Interval Arithmetic and its Implementation on the Computer Ulrich W. Kulisch Institut f¨ur Angewandte und Numerische Mathematik Universit¨at Karlsruhe Abstract: Let IIR be the set of closed and bounded intervals of real numbers. Arithmetic in IIR can be defined via the power set IPIR of real numbers. If divisors containing zero are excluded, arithmetic in IIR is an algebraically closed subset of the arithmetic in IPIR, i.e., an operation in IIR performed in IPIR gives a result that is in IIR. Arithmetic in IPIR also allows division by an interval that contains zero. Such division results in closed intervals of real numbers which, however, are no longer bounded. The union of the set IIR with these new intervals is denoted by (IIR). This paper shows that arithmetic operations can be extended to all elements of the set (IIR). Let F ⊂ IR denote the set of floating-point numbers. On the computer, arithmetic in (IIR) is approximated by arithmetic in the subset (IF ) of closed intervals with floating- point bounds. The usual exceptions of floating-point arithmetic like underflow, overflow, division by zero, or invalid operation do not occur in (IF ). Keywords: computer arithmetic, floating-point arithmetic, interval arithmetic, arith- metic standards. 1 Introduction or a Vision of Future Computing Computers are getting ever faster. On all relevant processors floating-point arith- metic is provided by fast hardware. The time can already be foreseen when the P C will be a teraflops computer. With this tremendous computing power scientific computing will experience a significant shift from floating-point arithmetic toward increased use of interval arithmetic.
    [Show full text]