detailed_itineraries - function missing a timeout limit

[SRN1973]

When I feed a lot ot origin-destination pairs to the detailed_itineraries function I always happen to have some connections to calculate that seem to slow down the overall calculation process quite dramatically (cause the function to run for a few minutes for a few connections out of the data-set). Do you think it would be possible to implement some kind of additional timeout parameter so that if one of the triggered parallel processes takes too long it is terminated automatically, and returns NULL?

[mvpsaraiva]

That's a very interesting feature, thanks for the suggestion. I'm not sure we can do this without some upstream changes in R5, but I'll take a look.

[mvpsaraiva]

Hi @SRN1973.

I've checked and we cannot add a timeout limit to detailed_itineraries(), or any of the other of the package's functions, without a lot of work done upstream in R5.
Do you think the new version of travel_time_matrix() that we're preparing (issue #194) provides enough output information that you may be able to use it instead of detailed_itineraries()? It's much faster, and probably will fix some of the issues you had.

[rafapereirabr]

Unfortunately, this could only be done upstream in R5. If you like the feature, we'd recommend opening a request on R5 github repo.