It's a little overkill to use that many decimals, you just really need 3 significant figures in this case since (a) you're not interested in knowing exactly to the picometre what your top speed will be and (b) you can't really read the speed nor the RPM to higher precision than about three significant figures anyways.

So for practical purposes I would set x_mph = 336 and x_kph = 209

Also I think the formula would benefit from being written as a multiplication instead of a string of divisions:

Code:

` a/(b/c/d/e) = a/(b*(1/c)*(1/d)*(1/e)) = a/(b/(c*d*e)) = a*c*d*e/b`

In my opinion it's easier to read it that way.

Code:

`wheel size = x*[Gear ratio]*[Final ratio]*[Speed] / [RPM]`

You should also write what the dimension (radius or diameter?) and unit (meters or inches?) of the wheel size is.

Another approach could be to get rid of the x entirely (it's basically a "magic number", hard to work out where it comes from) and instead write the formula as a set of equations. This way it's easier to figure out where everything comes from and check that the formula is correct. Here's an example with four equations for calculating the wheel radius:

where

*r* is the wheel radius in meters,

*ω* is the angular speed of the wheel (how fast it rotates) in radians per second,

*v* is the speed of the car in meters per second and

*R* is the ratio of the gearing.

The first equation gives the basic relationship between the radius of the wheel, the angular velocity of the wheel and the speed of the wheel.

The second equation provides a way to calculate the angular velocity of the wheel based on the engine rpm and the total gear ratio.

The third equation states that the total gear ratio is equal to the gear ratio multiplied by the final drive ratio.

The fourth equation converts the wheel speed from km/h or mph to m/s.