8.15.0.2
10 Stuff That Doesn’t Belong Anywhere Else🔗ℹ
10.1 Parallelization🔗ℹ
The maximum number of threads a parallelized
math function
will use. The default value is
(max 1 (processor-count)).
10.2 Discrete Fourier Transform Conventions🔗ℹ
A parameter controlling the convention used for scaling discrete Fourier transforms, such as those
performed by
array-fft. The default value is
'(1 -1), which represents the convention
used in signal processing.
In general, if
lst is
(list a b) and
n is the length of a transformed
array axis or vector, then
Conveniently, a Fourier transform with convention
(list (- a) (- b)) is the inverse
of a Fourier transform with convention
(list a b).
See Mathematica’s
documentation
on Fourier, from which this excellent idea was stolen.
Returns the convention used for inverse Fourier transforms, given the current convention.
10.3 Floating-Point Compliance Testing🔗ℹ
Runs a comprehensive test of the system’s IEEE 754 (floating-point) compliance, and reports
unexpected inaccuracies and errors.
In each test, a function is applied to some carefully chosen values, as well as n additional
random values.
Its corresponding bigfloat function is applied to the same values, and the answers are
compared.
Each test returns a list of failures, which are appended and returned.
Each failure in a failure list is formatted
where
name is the name of a function, such as
'fl+,
args ... are the
arguments it was applied to, and
reason is the reason for the failure.
If reason is a flonum, the failure was due to inaccuracy. For example,
means the result of
(fl+ 4.5 2.3) was off by
0.76 ulps.
The threshold for reporting unexpected inaccuracy depends on the function tested.
All the arithmetic and irrational functions exported by racket/flonum, for example,
must have no more than 0.5 ulps error in order to be compliant.
Two other possible failure reasons are
| (list 'different-zero 0.0 -0.0) |
| (list 'different-zero -0.0 0.0) |
The first zero is the answer returned by the function, and the second zero is the expected answer.
Other possible failure reasons have the form
meaning that the result
(values x y) is not a valid flonum expansion.
Such reasons are only given for failures of functions whose names begin with
fl2 or contain
/error.
These functions are currently undocumented, but are used to implement many
math/flonum,
math/special-functions, and
math/distributions functions.
Tests of functions that operate on and return flonum expansions are the strictest tests, requiring
hardware arithmetic to be perfectly IEEE 754 compliant.
They reliably fail on seemingly innocuous noncompliant behavior, such as computing intermediate
results with 80-bit precision.
When
(print-fp-test-progress?) is
#t, floating-point tests print and flush a
representation of their progress as they run. The default value is
#t.