Sunday, December 13, 2009

How to use the Google calculator




Google’s calculator tries to understand the problem you are attempting to solve without requiring you to use special syntax. However, it may be helpful to know the most direct way to pose a question to get the best results. Listed below are a few suggestions for the most common type of expressions (and a few more esoteric ones).


Most operators come between the two numbers they combine, such as the plus sign in the expression 1+1.

Operator  Function  Example
+ addition  3+44
-  subtraction  13-5
*  multiplication  7*8
/  division  12/3
^ exponentiation (raise to a power of)  8^2
% modulo (finds the remainder after division) 8%7
choose  X choose Y determines the number of ways of choosing a set of Y elements from a set of X elements  18 choose 4
th root of  calculates the nth root of a number  5th root of 32
% of  X % of Y computes X percent of Y 20% of 150


Some operators work on only one number and should come before that number. In these cases, it often helps to put the number in parentheses.

Operator  Function  Example
sqrt  square root  sqrt(9)
sin, cos, etc. trigonometric functions (numbers are assumed to be radians)  sin(pi/3)
tan(45 degrees)
ln  logarithm base e  ln(17)
log logarithm base 10  log(1,000)


A few operators come after the number.

Operator  Function  Example
!  factorial  5!


Other good things to know

You can force the calculator to try and evaluate an expression by putting an equals sign (=) after it. This only works if the expression is mathematically resolvable. For example, 1-800-555-1234= will return a result, but 1/0= will not.

Parentheses can be used to enclose the parts of your expression that you want evaluated first. For example, (1+2)*3 causes the addition to happen before the multiplication.

The in operator is used to specify what units you want used to express the answer. Put the word in followed by the name of a unit at the end of your expression. This works well for unit conversions such as: 5 kilometers in miles.

0 comments: