# Wolfram Alpha: no competition for Google

This afternoon there was a minor aftershock of Sunday's LA earthquake, and I noticed that the time on the USGS earthquake report was pretty much the same as when I felt it several tens of miles away. So I became curious: how fast do earthquakes travel, anyway?

This seemed like a good test case for Wolfram Alpha, a fancy new search engine from the makers of Mathematica, so I thought I'd try it. But "earthquake speed" as a query led it to think I was asking about two action movies with those titles, "how fast does an earthquake travel?" just confused it, and substituting "seismic wave" for earthquake at least avoided the movie misinterpretation but didn't get me any better results. "Seismic wave" alone as a query gave the results "Seismology: Additional functionality for this topic is under development... Leave your email address to be notified when it is ready." And I still didn't find out what I had set out to.

Finally, I gave up, went to the Google search box in my browser's toolbar, and typed the same query I'd started with, "earthquake speed". The first hit was exactly on-topic, and the snippet Google displayed with the hit showed that it was on-topic. The answer: it varies, but for the roughly 56 km between the epicenter and my location it should have taken between 4 seconds (for the fastest P waves) and 16 seconds (for the slowest S waves).

Combined with Wolfram Alpha's Babylonian arithmetic fiasco, this does not fill me with a lot of confidence in their service...

Short conclusion: I still feel lucky.

### Comments:

**None**: another error

**2009-05-20T03:01:53Z**

Search for "sum n^-1.5" (apparently this sum diverges, which came as a very large shock to me). Then search for "sum n^-1.500000" and you get the right answer. There's a reason it's still in alpha.

**11011110**: Re: another error

**2009-05-20T03:20:09Z**

At least with Google you have some idea how authoritative a result you're getting by considering where the result comes from. With WA, you get some answer, clearly stated and unsourced, with little indication how reliable it is supposed to be.

Their example "calculation" of $250 + 15% does not exactly inspire confidence, either. If it is trying to be intelligent about transforming that calculation into something that makes sense mathematically (should be $250 × 115% = $250 × 1.15), who knows what other transformations they're prepared to make and what fraction of the time it will transform nonsense into bigger nonsense and give you an authoritative nonsense answer rather than giving you some hint that you need to reformulate your question?

**None**: Re: another error

**2009-05-20T03:32:38Z**

There the interpretation is really fine: it interprets it as \( \sum_{n=1}\infty n^{-1.5} \). It just mysteriously gets the answer wrong. It's some sort of bizarre error with its handling of floating point numbers.

**helger**: Re: another error

**2009-05-20T09:34:53Z**

Not sure why though. I'd guess they'd use Mathematica as a backend, and Mathematica 7.0 gets Sum[n^(-1.5), {n, 1, \[Infinity]}] right.

**None**: Re: another error

**2009-05-20T05:58:41Z**

http://www68.wolframalpha.com/input/?i=sum+n^(-3%2F2)

**11011110**: Re: another error

**2009-05-20T06:10:03Z**

That one it gets right.

Here's another strangeness: this sum is interpreted as having 1 and infinity as its limits. But when one sums 2^-n it is interepreted as having 0 and infinity as its limits. In particular sum(n^-2)+sum(2^-n)≠sum(n^-2+2^-n). Is this sort of guesswork in a system that purports to give correct mathematical answers appropriate? Yes, it shows you what it has guessed, but if you didn't know to specify the limits in your input why would you know to check that they have been guessed correctly?

**helger**: Re: another error

**2009-05-20T09:37:42Z**

Probably because 0^const does not always make sense. For example, sum (n+1)^(-3/2) starts with n = 0. But not sure how it handles more difficult cases that are not so clearcut.

**None**: A positive comment

**2009-05-20T09:39:13Z**

I am trying not to be so critical: a bit more intelligent understanding of inputs for scientific calculations is what I was long looking for... Hopefully Wolfram|Alpha attracts a critical mass of users so it survives and becomes higher quality.

Yesterday I was trying to check my generating function for cycles and just entered "series -1/2 ln(1-x)" - my straightforward guess of the query - and it gave me the right answer.

At least it can save me buying Mathematica or other maths software and learning their syntax (as it is free so far) and maybe sometimes do a bit more.

**11011110**: Re: A positive comment

**2009-05-20T16:18:54Z**

You have a point. Some of the things it does are very different from Google and it's helpful to have them collected in one place this way. As long as you're using it as a check, rather than as a way of calculating the series, the verifiability problems should be much less of an issue.

**None**: 1.0001^10000 = 0

**2009-05-20T22:26:50Z**

1.001^1000 = 2.71692, 1.0001^10000 = 0.

From http://en.wikipedia.org/wiki/Talk:Wolfram_Alpha#Gross_Limitations

(Ok, 1.0001000000^10000 = 2.718146, but how was I supposed to know that I must use it like that?)

**11011110**: Re: 1.0001^10000 = 0

**2009-05-20T22:31:48Z**

Wow. I guess the moral is not to trust anything it does involving floating point?

**None**: Re: 1.0001^10000 = 0

**2009-05-28T17:16:35Z**

More fun:

Input: 1.0001^5754 Output: 2. Input: 1.0001^5755 Output: 2. Input: 1.0001^5756 Output: 0.

**None**: Re: 1.0001^10000 = 0

**2009-05-28T17:33:00Z**

Okay, I can't resist but this is my last one, I promise (and in my defense I'm not the first Anonymous who posted on this).

Input: 1.0003^800 Output: 1.3 Input: 1.0004^800 Output: 1. Input: 1.0005^800 Output: 1. Input: 1.0006^800 Output: 2.

**11011110**: Re: 1.0001^10000 = 0

**2009-05-28T17:37:42Z**

Any one of these answers, by itself, might make sense as rounding the exact answer to the number of significant digits remaining. What I don't understand is why the first one gets two digits and the rest only get one.

**None**: Graphs

**2009-05-20T22:39:27Z**

By the way, if it knows "(2,4)-complete bipartite graph", why doesn't it know "(4,2)-complete bipartite graph" or "(2,20)-complete bipartite graph"? I would have expected that knowing about things like "(a,b)-complete bipartite graph" for arbitrary inputs a and b would be exactly the kind of "computational search" that WA could handle.

**leonardo_m**:

**2009-05-21T21:35:14Z**

Wolfram Alpha isn't (so far) a search engine, and (so far) it has not tried to compete with Google.

**11011110**:

**2009-05-21T21:44:41Z**

Well, but see some of the comments above for ways in which it is not working well in the different-from-Google niche it is attempting to make for itself:

- It produces wrong answers
- It states these wrong answers authoritatively, with no way to check them
- It depends strongly on the detailed syntax of queries and does not make it obvious how to compose queries that will be interpreted correctly
- It has the appearance of being a computational engine for some queries that it really seems to handle only as a search engine (see the complete bipartite graph comment immediately above yours)

On top of which add:

**brentfolger**: Another Positive Comment

**2009-08-06T21:09:00Z**

While Google completely crushes Wolfram Alpha there are some very cool tricks and calculations you can perform with the new search engine. If you're involved a lot in mathematics like me (I run a ppc management company) then you might love Wolfram Alpha. Other than that Google stands above them all. Still though, Alpha is new and of course it will take time for them to work out all of these errors.

**None**: Re: Another Positive Comment

**2009-08-06T22:19:27Z**

I agree, Wolfram will take some time for users to jump on board. Currently you have Google, Yahoo and Bing: Yahoo and Bing are mergering (to a degree) so whats left? As long as Wolfram is cool with a long road ahead, then they should be fine.

Rob Greco

http://robgreco.com/blog

twitter.com/robertgreco