News for hackers. Stuff that matters.
Re:Why bad scientific code beats code following "best practi... by barrkel on Monday May 12, 2014 @08:43AM (#7732361)
random()%NUM is usually wrong even if NUM < MAX_RAND.

random() is often a linear congruential generator (LCG: http://en.wikipedia.org/wiki/Linear_congruential_generator) for speed and simplicity purposes. LCGs are a multiply, an add and a modulus (the modulus is usually implicit from the machine word size). That means their low bits are highly predictable and not random at all.

    X(n+1) = (a * X(n) + c) mod m
Assume m is a power of 2 since it's usually implemented via machine word wrap-around. If c is relatively prime with m (in order to fill the whole range of m), then it will be odd. a-1 is normally a multiple of 4 since m is a power of two, so a is odd too.

So if X(n) is odd, X(n+1) will be even (o * o+o => o+o => e), and X(n+2) will be odd (o * e+o => e+o => o), and so on, with zero randomness.

So if you're trying to simulate coin flips and use %2, you will get a 1,0,1,0... sequence.

Re:Why bad scientific code beats code following "best practi... by Someone on Monday May 12, 2014 @12:40PM (#7733787)
It is often wrong even if random() were to produce perfectly random numbers; random()%NUM, for most values of NUM, will be biased.

For example, if RAND_MAX is 255, random()%10 equals 0, 1, 2, 3, 4, or 5 26/256 of the time, but 6, 7, 8, or 9 only 25/256 of the time.

That's why good libraries have a 'next(maxValue)' function that is more complex than random()%NUM. For example, see lines 251-268 of http://developer.classpath.org/doc/java/util/Random-source.h....

Re:Why bad scientific code beats code following "best practi... by raverbashing on Monday May 12, 2014 @11:01AM (#7733061)
I just tested this quickly (on MacOS 10.9.2), it is not a 1,0,1,0 sequence. (It is repeatable since I'm not seeding)

On Linux, same thing. It even gives the same sequence as the Mac OS version

(it's 100 numbers, "1,0,1,1...0,1," no \n at the end)

./rt | md5sum 7a5a5a0758ca83c95b21906be6052666

Re:Why bad scientific code beats code following "best practi... by mturmon on Monday May 12, 2014 @11:59AM (#7733493)
@barrkel made a small mistake, confusing rand() and random().

rand() is the earliest C random number generator. Its low-order bits (back in the day) went through a predictable sequence, so rand() & 0x1 was a bad source of random bits.

I don't think that rand() was specified so fully as to make this behavior required, but typical implementations exhibited it, so you could not use rand() for any serious work.

random() came after, does not use a LCG, and thus fixed this problem, so you would not see it if your code calls random(), whose man page says:

  The difference [between random() and rand()] is that rand() produces a much less
  random sequence -- in fact, the low dozen bits generated by rand go through a
  cyclic pattern.  All of the bits generated by random() are usable.  For
  example, `random()&01' will produce a random binary value.
Typically, because of this screwup, people use a third-party generator, like the "Mersenne twister".
Re:Why bad scientific code beats code following "best practi... by barrkel on Monday May 12, 2014 @12:28PM (#7733701)
LCG can be used for serious work, depending on your definition of serious. You need to use multiplication instead of modulus.
Re:Why bad scientific code beats code following "best practi... by barrkel on Monday May 12, 2014 @12:31PM (#7733721)
My comments were not specific to C. They were a general statement about runtime library provided random number functions across all languages - a risk to be aware of.

There are other mitigations. For example, Java's RNG uses an LCG, but returns the high 32 bits and uses a 48-bit modulus to counter this weakness.