Long shot: I'm trying to gauge the quality of some "random" numbers…
by Administrator. Average Reading Time: about a minute.
Long shot: I'm trying to gauge the quality of some "random" numbers that I have generated. I'm using the "dieharder" http://www.phy.duke.edu/~rgb/General/dieharder.php library to analyse the data I have (in a file)
I use a file for my data (even though that's not recommended) and give that data to dieharder:
dieharder -g 202 -f my_data.input -s 1
(where -g 202 tells dieharder to use the input file) and -s 1 is the test to run.
This fails spectacularly with all tests. If I create a file of random numbers from one of the built in generators, I get the same (failing) result. Running dieharder with the -v 1 option (for debug purposes), I can see the file of data being read and parsed seemingly correctly.
Any ideas out there in G+ land?
Embedded Link
Robert G. Brown's General Tools Pagergb's Books
Robert G. Brown's General Tools Page. Things on the site itself that may be of interest to students or philosophers of any age or generation include complete online books of poetry, various suppor…
Google+: View post on Google+
Post imported by Google+Blog. Created By Daniel Treadwell.
Should you not use mode 201, e.g. raw_input?
I can try, but I read the docs to the effect that raw input is indeed "raw" bytes, not formatted ascii numbers. OTOH – I had the idea under the shower to just rewrite my generator to write to STDOUT and let dieharder read from STDIN – that should do the trick
You don't need to rewrite it, make it write into a named pipe…
it's trivial to rewrite (puts instead of file.puts) :)
and neither 201 nor 202 work – just tried for good measures