Last updated on 2025-02-18 02:50:47 CET.
Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
---|---|---|---|---|---|---|
r-devel-linux-x86_64-debian-clang | 0.2.6 | 33.11 | 28.83 | 61.94 | NOTE | |
r-devel-linux-x86_64-debian-gcc | 0.2.6 | 29.13 | 23.14 | 52.27 | NOTE | |
r-devel-linux-x86_64-fedora-clang | 0.2.6 | 107.73 | NOTE | |||
r-devel-linux-x86_64-fedora-gcc | 0.2.6 | 125.82 | NOTE | |||
r-devel-macos-arm64 | 0.2.6 | 42.00 | NOTE | |||
r-devel-macos-x86_64 | 0.2.6 | 58.00 | NOTE | |||
r-devel-windows-x86_64 | 0.2.6 | 77.00 | 78.00 | 155.00 | OK | |
r-patched-linux-x86_64 | 0.2.6 | 35.72 | 27.12 | 62.84 | OK | |
r-release-linux-x86_64 | 0.2.6 | 35.82 | 27.21 | 63.03 | OK | |
r-release-macos-arm64 | 0.2.6 | 42.00 | OK | |||
r-release-macos-x86_64 | 0.2.6 | 48.00 | OK | |||
r-release-windows-x86_64 | 0.2.6 | 79.00 | 77.00 | 156.00 | OK | |
r-oldrel-macos-arm64 | 0.2.6 | 47.00 | OK | |||
r-oldrel-macos-x86_64 | 0.2.6 | 90.00 | OK | |||
r-oldrel-windows-x86_64 | 0.2.6 | 81.00 | 72.00 | 153.00 | OK |
Version: 0.2.6
Check: top-level files
Result: NOTE
possible bashism in configure.ac line 17 (should be 'b = a'):
if test "${ENDIAN}" == "little"; then
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Version: 0.2.6
Check: tests
Result: NOTE
Running ‘RDieHarder.R’ [0s/0s]
Comparing ‘RDieHarder.Rout’ to ‘RDieHarder.Rout.save’ ...7,72d6
<
< dieharder version 3.31.1 Copyright 2003 Robert G. Brown
<
< Usage:
< dieharder [-a] [-b bits] [-d diehard test number] [-f filename]
< [-g generator number] [-h] [-i iterations] [-l]
< [-n ntuple] [-p number of p samples] [-q] [-o filename]
< [-N] [-r rgb test number] [-s sts test number]
< [-t number of test samples] [-u user test number]
< [-v verbose flag] [-x xvalue] [-y yvalue] [-z zvalue]
<
< -a Runs all the tests with standard/default options to create a report
< -b bits - sets the number of bits to be used in tests that act on a bit
< string of variable length, e.g. the rgb bitdist test.
< -d test number - selects specific diehard test.
< -f filename - two generators permit either formatted ASCII numbers
< or raw binary numbers to be read in from a file for testing.
< Note well that some (default) tests require 10,000,000 or more rands!
< To see a sample of the (required) header for ASCII formatted input, run
<
< dieharder -o -f example.input -t 10
<
< and then examine the contents of example.input.
< Raw binary input reads 32 bit increments of the specified data stream.
< -g generator number - selects a specific generator for testing. Using
< -1 causes all known generators to be printed out to the display.
< -h prints context-sensitive help -- usually Usage (this message) or a
< test synopsis if entered as e.g. dieharder -d 3 -h.
< -i iterations - sets iteration count for timing runs (should not be
< needed).
< -l list all known tests.
< -n ntuple - set ntuple length for tests on short bit strings that permit
< the length to be varied (e.g. rgb bitdist).
< -o filename - output -t count random numbers to file.
< -N force the usage of non-overlapping samples in certain diehard tests.
< -p count - sets the number of p-value samples per test (default 100).
< -q selects "quiet" operation: results only are printed on a single line
< (where applicable). This is a way of getting a very compact report.
< -r test number - selects specific rgb test.
< -S seed. Any (uint) seed but (default) 0 surpresses per-test,
< fully automated reseeding from /dev/random if available or the
< clock if not (where the latter is NOT really desireable).
< -s test number - selects specific sts test.
< -t count - sets the number of random entities used in each test, where
< possible. Be warned -- some tests will take a long time with the
< default value of 10000. Read the test synopses for suggested settings
< for -t or use -a first.
< -u test number - selects specific user-developed test, if you've added
< one or more to this tool. dieharder provides this interface to make
< it easy to add your own tests.
< -v verbose flag -- controls the verbosity of the output for debugging
< only. Probably of little use to non-developers, and developers can
< read the enum(s) in dieharder.h and the test sources to see which
< flag values turn on output on which routines. 1 is "all" and will
< result in a fairly detailed trace of program activity.
< -x,-y,-z number - Some tests have parameters that can safely be varied
< from their default value. For example, in the diehard birthdays test,
< one can vary the number of "dates" drawn from the "year" of some
< length, which can also be varied. -x 2048 -y 30 alters these two
< values but should still run fine.
<
< NOTE WELL: The "bogomegarates" returned by this tool are BOGUS
< and may not be even approximately correct in your context. Also, the
< quality assessment(s) for the rngs may, in fact, be completely incorrect
< or misleading. Use them at your Own Risk! Be Warned!
<
Flavors: r-devel-macos-arm64, r-devel-macos-x86_64