An Arbitrary Precision Range Analysis Library

An Arbitrary Precision Range Analysis Library

Arpra: an arbitrary precision range analysis library Article (Published Version) Turner, James Paul and Nowotny, Thomas (2021) Arpra: an arbitrary precision range analysis library. Frontiers in Neuroinformatics, 15. a632729 1-21. ISSN 1662-5196 This version is available from Sussex Research Online: http://sro.sussex.ac.uk/id/eprint/99764/ This document is made available in accordance with publisher policies and may differ from the published version or from the version of record. If you wish to cite this item you are advised to consult the publisher’s version. Please see the URL above for details on accessing the published version. Copyright and reuse: Sussex Research Online is a digital repository of the research output of the University. Copyright and all moral rights to the version of the paper presented here belong to the individual author(s) and/or other copyright owners. To the extent reasonable and practicable, the material made available in SRO has been checked for eligibility before being made available. Copies of full text items generally can be reproduced, displayed or performed and given to third parties in any format or medium for personal research or study, educational, or not-for-profit purposes without prior permission or charge, provided that the authors, title and full bibliographic details are credited, a hyperlink and/or URL is given for the original metadata page and the content is not changed in any way. http://sro.sussex.ac.uk ORIGINAL RESEARCH published: 25 June 2021 doi: 10.3389/fninf.2021.632729 Arpra: An Arbitrary Precision Range Analysis Library James Paul Turner* and Thomas Nowotny School of Engineering and Informatics, University of Sussex, Brighton, United Kingdom Motivated by the challenge of investigating the reproducibility of spiking neural network simulations, we have developed the Arpra library: an open source C library for arbitrary precision range analysis based on the mixed Interval Arithmetic (IA)/Affine Arithmetic (AA) method. Arpra builds on this method by implementing a novel mixed trimmed IA/AA, in which the error terms of AA ranges are minimised using information from IA ranges. Overhead rounding error is minimised by computing intermediate values as extended precision variables using the MPFR library. This optimisation is most useful in cases where the ratio of overhead error to range width is high. Three novel affine term reduction strategies improve memory efficiency by merging affine terms of lesser significance. We also investigate the viability of using mixed trimmed IA/AA and other AA methods for studying reproducibility in unstable spiking neural network simulations. Keywords: interval arithmetic, affine arithmetic, range analysis, floating-point, reproducibility, numerical integration, spiking neural networks 1. INTRODUCTION Computer simulations are a valuable tool for understanding the behaviour of complex natural Edited by: systems, in particular in the context of Neuroscience and neural network simulations. They help Ludovico Minati, Tokyo Institute of Technology, Japan us form hypotheses and so reduce the need for expensive or at times impossible experiments. Executing simulations of computational models on computers, however, means accepting a Reviewed by: small amount of imprecision in the results stemming from rounding errors when performing Vincent Lefèvre, Inria Grenoble-Rhône-Alpes Research floating-point arithmetic, truncation errors when using approximate numerical methods, and even Centre, France errors due to limited precision representations of input data. Although small, when accumulated Malu Zhang, over time, these errors can influence the overall behaviour of a computation, sometimes with National University of Singapore, dramatic effect. In a famous example, gradual accumulation of unchecked rounding errors between Singapore January 1982 to November 1983 was causing stocks at the Vancouver stock exchange to loose *Correspondence: around 25 points per month (Huckle and Neckel, 2019). Such events have spurred a lot of interest James Paul Turner in analysing how numerical errors propagate through computer programs. This is particularly [email protected] relevant where numerical simulations rest on limited precision floating-point arithmetic (IEEE, 1985, 2008, 2019) and errors accumulate due to the iterative nature of the numerical integration Received: 23 November 2020 of models. To further complicate matters, there are sometimes subtle differences in the way Accepted: 31 May 2021 floating-point arithmetic is implemented across architectures, and additional differences in the Published: 25 June 2021 way compilers optimise floating-point arithmetic code (Monniaux, 2008; Whitehead and Fit-florea, Citation: 2011). The use of massively parallel General Purpose Graphics Processor Unit (GPGPU) code has Turner JP and Nowotny T (2021) Arpra: An Arbitrary Precision Range further compounded the problem as a large number of FPUs are used simultaneously, all operating Analysis Library. on the same data, with no guarantee on the order in which they will begin or finish an operation. Front. Neuroinform. 15:632729. In this work we present the Arpra library (Turner, 2019), which uses floating-point error doi: 10.3389/fninf.2021.632729 bounding techniques to analyse numerical error propagation in computations. We evaluate the Frontiers in Neuroinformatics | www.frontiersin.org 1 June 2021 | Volume 15 | Article 632729 Turner and Nowotny Arpra Library effectiveness of a novel mixed trimmed IA/AA method against different standards (Monniaux, 2008; Whitehead and Fit-florea, existing IA, AA and mixed IA/AA methods in example problems, 2011). For instance, in IEEE-754-1985, the only floating-point including a prototype spiking neural network. operations that are required to be correctly rounded are the basic ( , , /, , √) operations and floating-point conversion + − ∗ 1.1. Background functions. However, in later IEEE-754 revisions, the ‘fused Real numbers are in the vast majority of systems represented in multiply-add’ (FMA) function is included in this list. FMA floating-point number format f s m be, with s 1,1 instructions are now shipped as standard with AMD and Intel = · · ∈ {− } and m [1, b), where s, m and e are, respectively the sign, processors, respectively starting in 2011 with AMD’s ‘Bulldozer’ ∈ significand (also known as the mantissa) and exponent of f , (Hollingsworth, 2012) architecture, and in 2013 with Intel’s and b is the base of the floating-point system (usually two). The ‘Haswell’ (Intel, 2018) architecture, which provide fully IEEE- IEEE-754-1985 standard (IEEE, 1985), and later revisions (IEEE, 754-2008 compliant floating-point implementations. Even so, 2008, 2019), define the 32 bit single-precision and 64 bit double- there is still no guarantee that a given compiler will make use precision floating-point formats, corresponding to the float of FMA operations. As FMA incurs a single rounding error and double types in C-like programming languages. The but a separate multiply and add operation incurs two separate standard dictates that a subset of floating-point functions must errors, results can depend on the compiler vendor and version. be correctly rounded, meaning the result must be computed as if Transcendental functions are often implemented in software in infinite precision and then rounded to a nearby floating-point libraries, such as the glibc library used by GCC on Linux. Given number according to the selected rounding mode. that the error bounds for many of the glibc math functions have not been entered into the glibc manual (Loosemore, 2020) at 1.1.1. Numerical Errors the time of writing, it is difficult to determine whether results Because this representation of real numbers is discrete and computed by these functions exactly match those computed by approximate, small rounding errors can be introduced whenever alternate math libraries. It is well-known that results depend on an FPU and math library are utilised. There are three commonly the library, and can even change in different versions of the same used measures of numerical error (Goldberg, 1991), the first two library. Tests have been done on values that are difficult to round correctly (Lefèvre, 2021) and (Zimmermann, 2021). Accurate are absolute error, errorabs(f , r) f r , and relative error, f r = − libraries will compute matching results in general, but may return error (f , r) − , where f is the computed floating-point rel = r different results when the exact result is very close to the midpoint value, and r is the exact value. Thirdly there is the error in terms of consecutive floating-point numbers. of units in last place (ULP) of the significand, errorULP(f , r) Another layer of complexity is added with the growing r p 1 f r p 1 p = m b | − | b [0, b ), where p is the precision of f use of concurrency, for instance the massively parallel GPU − be − = be − ∈ (the number of digits in m) and e is the exponent of r. accelerators popular in machine learning. The basic arithmetic While rounding errors occur only in the least significant digit, functions of NVIDIA’s compute unified device architecture they can rapidly be amplified, for instance through a process (CUDA) (NVIDIA, 2018), including fused multiply-add, are called catastrophic cancellation. This occurs if two approximately fully IEEE-754-2008 compliant and even though the CUDA equal floating-point numbers are subtracted from each other implementations of the transcendental functions are not so the least significant bits of the two numbers determine the necessarily

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    22 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us