Optimizing a game we're developing, we're running into the phase where every CPU cycle won counts. We using radians for position calculations of objects circling around other objects and I want to cut the needless accuracy in my lookup tables. For that, we make heavy use of a predefined Pi. How accurate should this Pi be?
So, my question is:
You might as well just make it as accurate as whatever floating-point representation you can store is. It won't take longer to perform calculations using a more accurate floating-point number of the same type.
Accuracy is generally measured as number of significant digits; you'll need to decide for yourself how many digits of accuracy you're interested in. If you use a less accurate value for pi, that value's inaccuracy will propagate to the other calculations it's in.
As a comparision: I think NASA use pi with 7 decimals accuracy to be able to dock into space.
First of all we need to determine how accurate your position calculations need to be, i.e. how accurate the formulas in your program which depends on pi have to be. We need to start there in order to know how accurate pi you need to achive this.
Once that has been determined, you can probably use more or less straight forward numerical analysis to determine how good accuracy you need for pi. I can help you with that, but I need the position formulas to do that :)
Edit: I suspect that your formulas are linearly dependent on pi, i.e. you aren't using some obscure function f(x,y,z,pi) where pi is squared or similar. In that case the accuracy of your formula is a factor times the pi accuracy, e.g. k*eps(pi). Otherwise it's basically a factor times the derivative of f with respect to pi. Not counting the accuracy of all other parameters f depends on !
Cheers !
It depends on how many significant digits you have in your calculation. Given the formula
C = pi * d
if you want to know how many inches in the circumference of a circle one mile in diameter, you'd need six digits of pi to keep the accuracy you want, since there are 63,360 inches in a mile, and there would be 199,051 inches in the circumference. Since there are six significant digits in the answer, I need six digits of pi to calculate it to the needed accuracy.
3.14 * 63,360 = 198950.4
3.142 * 63,360 = 199077.12
3.1416 * 63,360 = 199051.776
3.14159 * 63,360 = 199051.1424
As you can see, I got the right answer in this case with only 5 digits of pi, but that's not always going to be the case. You need at least as many digits of pi as you have significant digits to ensure you have enough precision.
If you're precalculating it and storing it, you can just use the math library on your system to compute it one time as accurately as possible. A good option is:
double PI = (16.0 * atan(1/5)) - (4.0 * atan(1/239));
That will give you a fairly accurate value for PI which you can compute at startup and reuse as needed. It's difficult to get a more accurate version than that which is easily reusable.
It's not fully clear what you are doing. Are you looking up coordinates based on an angle? In this case the accuracy of Pi doesn't matter at all. Important is the size of the lookup table and you will of course precalculate it with the highest possible accuracy. Further accuracy doesn't cost additional execution time besides you are thinking about changing the data type from single to double.
If you are pre-calculating the value make it as accurate as feasible to store but to get the true feel of what accuracy in actually needed you have to look at your formulas and the accuracy of other components and than make sure the accuracy you have for pi matches that for other components. Numerical analysis will give you plaenty of clues.
new formula for pi
Pi=2.m.sin(90/m)
Pi=3.m.sin(60/m)
Pi=4.m.sin(45/m)
Pi=5.m.sin(36/m)
For millions across the value of PI free calculator XP,XM,….. recommend m=1.0E+10000000 to the success of the calculator you need to install netframework2.0
