**When would I ever want to pick a random point in a circle?**

Imagine you are working on a First Person Shooter as a Gameplay Engineer. Your job is to implement the shotgun firing mode. That means you need to fire multiple projectiles at once from a single round. Obviously a shotgun would not fire all the projectiles on the same straight line of sight. Shotguns fire rounds that break up into multiple projectiles that are spread out over a certain area. The shape of the area made up by the projectiles is circular because the barrel of a shotgun is circular.

One way we could simulate the shotgun spread mechanic is by allowing a Designer to specify a max radius. We could then pick a random point from the center of our reticle to the max radius.

### How do we get a random point in a circle?

#### The Box Method

There are several ways we could pick a random point in our circle. One way would be to pick a random point in a square. If the distance from the center of the circle to our random point is greater than our Designer’s radius, then we reject it and try again.

*Code Sample:*

*Code Sample:*

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
// Pick random points but only // put them in our point list if the distance // to the random point is less than or equal to our // circle's radius. void generatePoints() { PVector centerPos = new PVector( cx, cy ); points.clear(); for( int i=0; i <= maxPoints; ++i ) { float x = cx + random(-radius, radius); float y = cy + random(-radius, radius); PVector randomPos = new PVector( x, y ); if( centerPos.dist( randomPos ) <= radius ) { points.add( randomPos ); } } } |

Using the box method, we will get results that look uniformly distributed however there is a price to be paid.

There is no way to guarantee how many random points you will end up with unless you sit in a while loop until you have all the points you want. You can use a while loop if you prefer but there is no way to know how long this operation will take. This might be acceptable if you are using the box method during an initialization process but if you need to pick random points in a circle per frame or in an update loop, there are much better ways of doing it.

#### Polar Coordinates

A more efficient way to pick a random point in a circle is to use polar coordinates. Typically, we use what are called Cartesian coordinates to pick a point on a graph. Cartesian coordinates have an * x* and

*component. We move horizontally by however many units are specified by the*

**y***value and likewise do the same vertically based on how many units are specified by the*

**x***component.*

**y**Polar Coordinates are just another way to pick points on a graph.

Instead of moving linearly both horizontally and vertically, Polar Coordinates allow us to move more easily around a circle. A Polar Coordinate has 2 components similarly to the Cartesian Coordinate system. Polar Coordinate look like , where is the radius or distance from the center point of the circle and is the angle about which we rotate around the center point.

**Figure 3.**

To pick a random point using polar coordinates, we just need to pick a random radius and random angle.

We can do so in code like so,

*Code Sample:*

*Code Sample:*

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
void randomPolarCoordinatePoints(float diameter) { points.clear(); for( int i=0; i <= maxPoints; ++i ) { float radius = diameter / 2.0; float theta = random(0, 2 * 3.14159); float distance = random(0.0, 1.0) * radius; float px = distance * cos( theta ) + centerX; float py = distance * sin( theta ) + centerY; PVector pos = new PVector( px, py ); points.add( pos ); } } |

but this will give us an output like this

Notice how we chose more points towards the center of the circle than towards that outer edges of the circle. For some games, this spread may be appropriate. However what if you wanted your points to be uniformly spread out and not so dense in the center?

So why does randomly choosing an angle and radius make our random point selection more dense towards the center? Imagine you only have 50 points and you want to randomly distribute them about a very small circle. You will probably be able to do that just fine. However as you scale the circle out, you will start to have more and more area that you need to cover but not enough points to cover all the area because you are limited to only 50 points. Take a look at Figure 6 to visualize this.

### Exploiting the Area of a Circle

We were on the right track when using polar coordinates to pick a randomly distributed set of points in our circle. The only problem that stood in our way was the fact that our random points were more dense toward the center of the circle. The fundamental problem is that we are not uniformly covering all of the circle’s area. The random angle we chose should be fine because an angle has nothing to do with the area of the circle. However the radius cuts through the area of the circle. Therefore we want to focus in on how we can randomly pick a better radius. We need to somehow ensure that the probability of the radius distance is proportional to the area of the circle. In other words, we need to ensure that our random function takes into account the area of our circle. If only we could multiply our desired radius by some random weight that took our circle’s area into consideration…

Lets start by thinking about what the area of a circle is.

The formula for the area of a circle is .

The area of a circle is agnostic to any kind of probability. So if we could derive the formula for the radius based on the area of a circle, we should be able to randomly distribute our points in a uniform fashion.

Now pay close attention to the relationship between the the fraction and the area of a circle which is .

In both math and philosophy, it is often wise to test the limits or extreme cases of a statement to find out whether that statement is logically consistent and what ultimate conclusions that statement may lead to.

What would be the area of our circle if our radius was 1?

.

So forget about what the *actual* radius is of our circle. Lets keep things simple and pretend that our circle’s radius is between 0 and 1. Our fraction means that when the Area is 0, and when the area is , then . However since we are taking the square root of our fraction, it gives less weight to lower values than does the earlier linear version we tried. That is exactly what we want because the problem we were running into earlier was that we gave too much weight to points closer to the center of the circle and not enough weight towards the edge of the circle. Take a look at Figure 7 to visualize the difference between square root vs linear weighting.

**Figure 7.
**

So really we can substitute our fraction, , under the square root with any number between the values of 0 to 1.

As seen in the graph in Figure 7, the value of will still be within the range of 0 to 1 which we can use as a percentage scalar to multiply by the actual radius!

Therefore to pick a random uniformly distributed point in a circle using polar coordinates, we can do the following,

Radius

Angle

**Figure 8.**

Figure 8 was generated via the following Processing sketch.

*Code Sample:*

*Code Sample:*

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 |
// Processing Example // Random Uniformly Vs Non-Uniformly // Distributed Points In a Circle float diameter = 300.0; int maxPoints = 50000; ArrayList nonUniformPoints; ArrayList uniformPoints; PVector nonUniformCirclePosition = new PVector(0, 0); PVector uniformCirclePosition = new PVector(0, 0); //---------------------------------------------------------------- void setup() { size(800, 600); float cy = height / 2.0 |