You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: further parametrization and parallelization (#317)
* refactor parameter set for pt mapping
Extracted the parameter set class => cleaner code
some quality of life name changes
* feat: parametrized pt modes
now for each schedule mode, we can add a specific number of links and maximum search distance parameters
we can also use strict rule: when number of links is reached no additional links are added
backwards compatibility is ensured
* parallelize creating facilities and links sequences
Parallelize the generation of facilities and links from pseudo routes, speeding up the process considerably
* make threads and chunk size configurable
* fix typo
* extract reused variable
* remove duplicate exception
* rename fields to match original names
* update default pt mapper config
* fix copy-paste
* remove static
* use local variables
We now use local variables and do not adjust global ones if, for this mode, we need to use mode-specific rules
* add a modeSpecificRules test
* test to check the strict num of links rule
Copy file name to clipboardExpand all lines: doc/defaultPTMapperConfig.xml
+10-3Lines changed: 10 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,8 @@
18
18
between stops from the schedule. If travelCostType is
19
19
linkLength minTravel cost is the beeline distance. -->
20
20
<paramname="maxTravelCostFactor"value="5.0" />
21
+
<!-- Instead of using general number of links and maximum search distance rule, use the schedule mode specific rules to be defined within the parameter sets. For those that no information is provided the general values will be used. Options: [false, true]. Default: false. -->
22
+
<paramname="modeSpecificRules"value="false" />
21
23
<!-- All links that do not have a transit route on them are removed, except the ones
22
24
listed in this set (typically only car). Separated by comma. -->
23
25
<paramname="modesToKeepOnCleanUp"value="car" />
@@ -47,19 +49,24 @@
47
49
transit routes passing using it. This is recommended for "artificial", additional
48
50
modes (especially "rail", if used) can be added, separated by commas. -->
@@ -181,14 +190,18 @@ public final Map<String, String> getComments() {
181
190
"\t\tNo link candidates beyond this distance are added.");
182
191
map.put(NETWORK_ROUTER,
183
192
"The router that should be used. Possible options are: [SpeedyALT, AStarLandmarks]");
193
+
map.put(USE_MODE_SPECIFIC_RULES, "Instead of using general number of links and maximum search distance rule, use the schedule mode specific rules "
194
+
+ "to be defined within the parameter sets. For those that no information is provided the general values will be used. Options: [false, true]. Default: false.");
195
+
map.put(THREAD_CHUNK_SIZE, "The size of the chunk that is sent to the pt mapper thread at the time to build"
0 commit comments