# Simulating Dice

Posted:In this post I will demonstrate two approaches for simulating rolls of a die of a given size, using only rolls of a die of a different size.

Throughout this post I will use `dn`

terminology to refer to a die of size `n`

. For example a `d6`

refers to the classic six-sided die.

## # Using base number conversion

Given an input die of size `n`

and a target die of size `m`

, this approach works by expanding the output space of the `dn`

by rolling it repeated times, and interpreting the rolls in base `n`

mod `m`

. Some rolls however must be discarded to prevent bias in the outcomes.

To present this approach, I will start with some small examples before building up to a fully generalized algorithm.

### # Simulating a d6 using repeated coin flips

Given a coin, we can flip it as many times as necessary for the number of outcomes to exceed the target number.

For a d6, we would need to flip the coin at least 3 times to produce more than 6 outcomes. If we only flipped 2 times, we could only output 4 outcomes. At 3 flips we can output 8 outcomes. Given that we have 8 outcomes, we need to discard 2.

Here is one scheme for doing that:

HHH | 1 |

HHT | 2 |

HTH | 3 |

HTT | 4 |

THH | 5 |

THT | 6 |

TTH | DISCARD |

TTT | DISCARD |

Note that the ordering here is arbitrary, but I have used binary ordering, treating `H`

as `0`

and `T`

as `1`

. Although arbitrary, this ordering will prove convenient for generalization to other die sizes.

Additionally notice that in this case both of the discarded results start with `TT`

, so we can restart after only the second flip if we have seen `TT`

so far.

We can combine the above two notes to produce a method of arriving at results without needing a lookup table:

- Flip a coin twice
- If the flips were
`TT`

, discard and restart - Otherwise flip a third time
- Treating
`H`

as`0`

and`T`

as`1`

, read the flip outcomes as a binary number and add 1.

### # Simulating a d6 with a d4

The above method of using a coin is equivalent to repeated use of a d2. *A coin is a d2*. We can extend this method to any other die size.

With a d4, we need two rolls to produce a large enough outcome space to simulate at least 6 results. The outcome space is much larger than we need though, having 16 outcomes.

But we can map a given target result to multiple rows in our table, like so:

First roll | Second Roll | Result |
---|---|---|

1 | 1 | 1 |

1 | 2 | 2 |

1 | 3 | 3 |

1 | 4 | 4 |

2 | 1 | 5 |

2 | 2 | 6 |

2 | 3 | 1 |

2 | 4 | 2 |

3 | 1 | 3 |

3 | 2 | 4 |

3 | 3 | 5 |

3 | 4 | 6 |

4 | 1 | DISCARD |

4 | 2 | DISCARD |

4 | 3 | DISCARD |

4 | 4 | DISCARD |

Note as before that we have an opportunity to terminate early. In this case when the first roll is a `4`

.

In order to produce a result without a lookup table we can use the same approach as before, but instead of interpreting `d2`

rolls in binary, we instead interpret `d4`

rolls in base 4, but also needing to take care to adjust for out by one errors caused by our base number system starting at 0, but the numbers on our dice conventionally starting at 1.

Precisely, one must follow these steps:

- Roll a d4.
- If the outcome was
`4`

, discard and restart. - Roll the d4 a second time.
- Subtract one from both outcomes.
- Concatenate the two results and read as a base-4 number.
- The computed value at this point will be between
`0`

and`11`

. - Add 1 to this value and then apply
`mod 6`

.

We can now extract from this a pattern to this process, in which any die can simulate any other die.

Given some pair of naturals `n`

and `m`

, We can simulate a `dm`

using a `dn`

as follows:

- Find the smallest natural
`k`

such that`n^k >= m`

. - Roll the
`dn`

repeatedly,`k`

times. - Read the rolls as digits of a base
`n`

number. - Discard values greater than the largest multiple of
`n`

that is less than or equal to`m`

. - Mod the result by
`m`

and add 1.

See below for an implementation of this process in TypeScript.

**[Click to expand]** Implementation

`/**`

* Given `n`, simulate rolling a `dn` once.

*

* The possible outcomes are the set of naturals from 1 to n inclusive.

*/

const d = (n: number) => Math.floor(n * Math.random()) + 1;

const produceOneResult = (n: number, repeatCount: number) => {

const rollResults = new Array(repeatCount).fill(0).map(() => d(n));

// This reads the results as a single number in base `n`

const result = rollResults

.map((roll, i) => (roll - 1) * n ** (repeatCount - i - 1))

.reduce((a, b) => a + b, 0);

return result;

};

/**

* Given a `dn`, simulate the outcomes of a `dm`

*/

const simulateMwithN = (m: number, n: number) => {

/**

* `repeatCount` is the number of times we will need to roll the smaller die.

*/

const repeatCount = Math.ceil(Math.log(m) / Math.log(n));

/**

* The maximum valid result is the largest multiple of n that is

* less than or equal to the size of our target space

*/

const maxValidResult = Math.floor(n ** repeatCount / m) * m - 1;

let result: number;

do {

result = produceOneResult(n, repeatCount);

} while (result > maxValidResult);

return (result % m) + 1;

};

simulateMwithN(6, 4);

Try in the TypeScript Playground

## # Using recursive unit interval segmentation

Given an input die of size `n`

and a target die of size `m`

, this approach works by mapping to and from the unit interval. First segment the unit interval by `m`

. Then treat rolls of the `dn`

as "narrowing in" on a range of the unit line segment. We start from a range inclusive of the whole unit line segment: `0`

to `1`

. Then for example we can treat a roll of a `1`

on a `d4`

as narrowing from the range `0-1`

to `0-1/4`

. If we rolled at again and it came up `2`

we would then narrow to the second quarter of the current range, i.e. `0-1/4`

to `1/16-2/16`

. At each stage we can check whether the current range fits entirely within a single 'segment' of the output die. If so we output the value on the target die associated with the segment. Otherwise we continue narrowing.

Let's show a complete example to demonstrate.

Given an input `d4`

and target `d20`

.

The target segments are 20 equal sized segments on the unit interval.

The current input range is the full `0-1`

.

The first roll of the `d4`

yields a `3`

. The current input range is narrowed to `2/4-3/4`

. The current viable output values are `11-15`

. We need to narrow further.

The second roll of the `d4`

yields a `1`

. The current input range is narrowed to `8/16-9/16`

. The current viable output values are `11-12`

. We need to narrow further.

The third roll of the `d4`

yields a `4`

. The current input range is narrowed to `35/64-36/64`

. The current viable output values are `12`

. We halt with the output `12`

.

See below for an implementation of this process in TypeScript:

**[Click to expand]** Implementation

`/**`

* Represents a range on the unit interval

*/

type Interval = [number, number];

/**

* Given `n`, simulate rolling a `dn` once.

*

* The possible outcomes are the set of naturals from 1 to n inclusive.

*/

const d = (n: number) => Math.floor(n * Math.random()) + 1;

/**

* Let the unit interval be segmented into `m` segments of equal size,

* label the segments from 1 to `m`.

*

* Then given some `n` on the unit interval, output which segment of `m` it belongs to.

*/

const fromUnitNtoSegmentsM = (m: number) => (n: number) => {

if (n === 0) return 1;

return Math.ceil(n * m);

};

/**

* Given a die, map a single result to the unit interval

*/

const fromDNtoInterval = (n: number) => {

const dieResult = d(n);

const lowerBound = (dieResult - 1) * (1 / n);

const upperBound = lowerBound + 1 / n;

return [lowerBound, upperBound];

};

/**

* Given an interval and a die size,

* narrow the interval using a single role of the die

*/

const narrowIntervalWithDN =

(n: number) =>

(interval: Interval): Interval => {

// This generates a new unit interval

const [innerLower, innerUpper] = fromDNtoInterval(n);

// But we need to map it into our existing interval

const currentIntervalSize = interval[1] - interval[0];

const newLowerBound = interval[0] + innerLower * currentIntervalSize;

const newUpperBound = interval[0] + innerUpper * currentIntervalSize;

return [newLowerBound, newUpperBound];

};

/**

* Given a `dn`, simulate the outcomes of a `dm`

*/

const simulateMwithN = (m: number, n: number) => {

// We'll use a tuple to track a range on the unit interval

let interval: Interval = [0, 1];

const mapToDM = fromUnitNtoSegmentsM(m);

const mapFromDN = narrowIntervalWithDN(n);

// In this loop we repeatedly narrow our output interval

// Until its lower and upper bounds fit within the same segment of `dm`

while (mapToDM(interval[0]) !== mapToDM(interval[1])) {

interval = mapFromDN(interval);

}

return mapToDM(interval[0]);

};

/**

* A test of the distribution of a simulated dice

*

* Outputs a record where each key is a die result,

* and each value is how often that result occured

*/

const test = new Array(10000)

.fill(0)

.map(() => simulateMwithN(6, 4))

.reduce<Record<number, number>>(

(acc, curr) => ({ ...acc, [curr]: (acc[curr] ?? 0) + 1 }),

{}

);

/**

* If the test is successful, each value should be roughly equal

*/

console.log(test);

Try in the TypeScript Playground

## # Comparisons

Both approaches could theoretically *never halt*. In the first approach, we might always hit a DISCARD result. In the second approach we might always narrow in on a segment that straddles the boundary between two possible output values. However in practice the probability of this happening for either approach tends to zero for sufficiently many rolls of the input die.

One might also consider the practicality of either approach. In the presence of a computer there are much more convenient methods for simulating a die. However in the absence, the first approach can be somewhat pre-computed by drawing up lookup tables for a given input die (such as the ubiquitous d6) and a selection of output die.

I can't find a comparative advantage to the second approach compared to the first... and yet I can't help but shake some gut feeling of preference for it. Something about "zooming in" on the unit segment appeals to me.

That's all for this post.

Take care,

Rupert