Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/r5py/r5py/issues/292 below:

Default value for departure_time_window · Issue #292 · r5py/r5py · GitHub

Hi all. I wanted to raise a discussion about the default value for departure_time_window, which is currently set for 1 hour in r5py.

The default value we use in r5r is 1 minute, which in practical terms equals to using the exact departure time with no time window. Here is is reason why we opted for this in r5r.

1. When we do transport routing, most users think of setting a precise departure time. This is intuitive, and it's how all trasport route engines work. We wanted r5r to be as intuitive and as friendly as possible for both newcomers with little experience with routing analysis and for experienced users coming from other routing engines.
2. The capability of sampling multiple departure times in R5 in fantastic and being able to use it on the fly with a simple parameter like time_window is major contribution. However, we feel this is an 'advanced' feature. Hence, we belive users should make a conscious decision on how they should used it (a window size of 1 hour? 20 minutes? 3 hours?) and whether they really want to use it at all.

This is why we set a default time window value that mimics precise departure time behavior, and leave it to advanced users who read the documentation to make a conscious decision on whether and how they would like to do sampling with the time window parameter.

Whad to you think?

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4