Group Abstract Group Abstract

Message Boards Message Boards

ComputationTImeout in geographical calculations

Posted 10 years ago

Hi, Inspired by the excellent graphic "all roads lead to Rome" posted elsewhere in this forum, I was experimenting with similar calculations for my own country. It's my first time out using geographical calculations. Somewhere along the line I typed:

TravelDirections[{Entity["City", {"Brisbane", "Queensland", "Australia"}],
Entity["City", {"Canberra", "AustralianCapitalTerritory", "Australia"}]},  "DataSet"]

and got the message $Failed[ComputationTimeout]. I tried using SetOptions[WolframAlpha, TimeConstraint -> 120] without success.

My only other thought is that TravelDirections uses Alpha calls, and I am running up against my limit (I have a personal license with 3000 calls per month I think). Is that the case, or is there some other fix?

POSTED BY: Simon
13 Replies
Posted 10 years ago

I'm having this problem too. TravelDirections worked for me two weeks ago. Now it doesn't. I tried updating to 10.3.1 but issue persists. I just sent a "feedback" message about the issue to Wolfram and will post any interesting response.

POSTED BY: Joseph D'Anna

Note my comments earlier. I have discussed the issue with the developers, they are aware of it, and the problem will be fixed in a next release (whatever it is officially named).

POSTED BY: David Reiss
Posted 10 years ago

Thank you David.

Not your problem but...unfortunately for me, Wolfram fixing it "in the next release" is not good enough. I rely on the function in code I just wrote for a charity fundraiser happening next week (my scout troop will collect Christmas trees from 500+ homes in one day).

I'm further frustrated and disappointed because I purchased the last upgrade because of the new geographic information functions. Now I have to write my own TravelDirections function, just as I had to write my own version of FindGeoLocation for street addresses. To be fair, the Mathematica Documentation states only that FindGeoLocation["address"] "attempts to find the geo location associated with the street address given"

POSTED BY: Joseph D'Anna

"AnatomicalStructure" is an Interpreter type and I imagine that that might have issues under a slow internet connection. However the issue with TravelDirections and so on above is a bug rather than an issue with connection speed. I have been informed by the developers that the issue is resolved and will be fixed in version 10.4 or perhaps via a paclet update. I am not sure that I understand the circumstances where certain issues can be pushed via a paclet update. So, for the time being assume that TravelDirections, TravelDistance, and TravelTime are broken.

POSTED BY: David Reiss

Hello David, that is interesting, thank you for clarifying! I was thinking about upgading to v10.3 just because of those new functions ...

Regards -- Henrik

POSTED BY: Henrik Schachner

the 10.3.1 update! It worked fine in 10.3.0 (the version I used for this post). OR it could be a problem on Wolfram's side of course. I already deleted 10.3.0 so I can't test that one. (Mac OSX btw).

Interesting that there will be a 10.4, not an 11 ;-) They always did .1 or .2 updates, so I was already surprised with the .3 update! Well, maybe this is a new kind of updating!

POSTED BY: Sander Huisman

In addition: it's strange because the 10.3.1 update specifically fixed some bugs with TravelDirections...

POSTED BY: Sander Huisman

Interesting that there will be a 10.4, not an 11 ;-)

That is just an internal label meaning "the next release" for the moment. It may very well have a different version number when released.

POSTED BY: Ilian Gachevski

Hi @Ilian Gachevski , just kidding!

In the end, I don't care! The major.minor.patch updates are bigger than the major update of Matlab ;) In the end, the numbers doesn't really matter of course, the only big difference is a new logo or not ;)

POSTED BY: Sander Huisman
Posted 10 years ago

Thanks to everyone for the replies. Three days later I just tried again, without any luck. If it's a Wolfram-side issue then it's a persistent one. I haven't done the 10.3.1 update yet, by the way.I'll do it today and see what happens.

UPDATE: 10.3.1 now installed and the problem persists.

POSTED BY: Simon

I am experiencing that problem quite regularly, e.g. in the context of AnatomicalStructure. My interpretation is that this timeout were due to my slow internet connection. I then have to try several times before I eventually get all the data. It would be interesting to know if this is the real reason.

POSTED BY: Henrik Schachner

Note that functions like TravelDistance and TravelTime are similarly not working.

POSTED BY: David Reiss
POSTED BY: David Reiss
Reply to this discussion
Community posts can be styled and formatted using the Markdown syntax.
Reply Preview
Attachments
Remove
or Discard