finder:finder-en
                Differences
This shows you the differences between two versions of the page.
| Previous revision | |||
| — | finder:finder-en [2025/10/12 07:27] (current) – [Limitations] rjversluis | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== The Finder ====== | ||
| + | [[: | ||
| + | [[:english | Content ]] -> [[: | ||
| + |   * [[: | ||
| + | \\ | ||
| + | {{: | ||
| + | \\ | ||
| + | =====Introduction===== | ||
| + | The Finder can be used to find a path from one __**[[: | ||
| + | This function must be enabled with __**[[# | ||
| + | The Finder will be active after setting a __**[[: | ||
| + | \\ | ||
| + | |||
| + | =====How it works===== | ||
| + | After activating, by setting a destination, | ||
| + | More then one path can be found depending of the complexity of the layout.\\ | ||
| + | The path will be converted into a temporary schedule which will be activated for the selected Loco.\\ | ||
| + | The new schedule will have a " | ||
| + | Example of a schedule name created by the Finder: // | ||
| + | If already an " | ||
| + | |||
| + | ====Limitations==== | ||
| + | * To avoid looping and using too much CPU resources the max. recursive depth is set to the number of available Routes. | ||
| + | * The search will stop if the max. depth has been reach more then the available number routes. | ||
| + | * Routes which needs a direction change will be skipped. | ||
| + |   * A valid [[: | ||
| + | |||
| + | \\ | ||
| + | |||
| + | =====Requirements===== | ||
| + |   * The layout must be healthy: __**[[: | ||
| + | |||
| + | \\ | ||
| + | =====Settings===== | ||
| + | {{: | ||
| + | |||
| + | ====Use Finder for destination path==== | ||
| + | See: __**[[: | ||
| + | ====Path==== | ||
| + | If more than one path has been found the following options can be used for selecting one: \\ | ||
| + | ===Shortest=== | ||
| + | Select the shortest found path.\\ | ||
| + | **Note:** //The [[: | ||
| + | ===Longest=== | ||
| + | Select the longest found path.\\ | ||
| + | ===Direct=== | ||
| + | Only a direct route will be used to generate a schedule.(Rocrail version 2.1.2903+) \\ | ||
| + | ===Preferred=== | ||
| + | Select the most __**[[: | ||
| + | **Note:** //If there are only routes with preferred set to zero this option will not find any path.//\\ | ||
| + | \\ | ||
| + | ====Options==== | ||
| + | ===Find alternative paths=== | ||
| + | | [[: | ||
| + | If __not__ enabled, or no valid support key, the finder will stop after the first path that has been found. Depending on how the layout is designed this could be a (big) detour.\\ | ||
| + | The max. number of alternative paths can be set. The default is 10 which normally will do. Increasing this number can cause more CPU usage without any better paths found. __But in case of layouts with many routes, this number should be increased to be able to find the shortest way.__\\  | ||
| + | This number of alternative paths is also restricted by the number of routes.\\ | ||
| + | |||
| + | ===Max. recursive=== | ||
| + | Limits the number of repetitions when searching for paths. | ||
| + | * **Note:** If no suitable path is found, the value of the max. recursive may need to be increased.\\ | ||
| + | |||
| + | ===Find alternative direct paths=== | ||
| + | Search for more short direct paths.\\ This option is required incase the Finder usages is " | ||
| + | |||
| + | ===Regular stop=== | ||
| + | All schedule entries will get the __**[[: | ||
| + | |||
| + | ===Temporary schedules=== | ||
| + | The generated schedules will be removed at shutdown.\\ | ||
| + | __This is default and highly recommended!__ Changing routes can make Finder schedules invalid and can lead to deadlocks.\\ | ||
| + | |||
| + | ===Check permissions=== | ||
| + | Check if the loco has permission to use routes and blocks.\\ | ||
| + | |||
| + | ===Check destination permissions=== | ||
| + | Check if the loco has permission to use routes running to the destination block and of the destination block itself.\\ | ||
| + | |||
| + | ===Avoid occupied blocks=== | ||
| + | Avoid occupied blocks to find a path.\\ | ||
| + | Depending on the block occupancy and layout the find result could be zero.\\ | ||
| + | |||
| + | ===Avoid occupied routes=== | ||
| + | Avoid occupied routes to find a path.\\ | ||
| + | Depending on the route occupancy and layout the find result could be zero.\\ | ||
| + | |||
| + | ===Use locations=== | ||
| + | Use block locations in the generated schedule.\\ | ||
| + | If the option is __not__ activated, the finder creates a " | ||
| + | If this option is activated, it is checked whether the blocks are in a location. In these cases, the location is entered instead of the block.\\ | ||
| + | If not all blocks in a location leads to the same follow-up block/ | ||
| + | |||
| + | ===Destination=== | ||
| + | If this option is active (default), the "Use locations" | ||
| + | This option must be deactivated if an defined block is to be used in the destination instead of an existing location.\\ | ||
| + | |||
| + | ===Avoid terminal blocks for none commuter trains=== | ||
| + | If a train is allowed to enter a terminal block this could be a dead end.\\ | ||
| + | Use this option to avoid running into terminal stations.\\ | ||
| + | |||
| + | ===Update schedules=== | ||
| + | If a schedule already exist it will be updated to meet the actual permissions.\\ | ||
| + | This option is recommended to avoid running into occupied blocks.\\ | ||
| + | |||
| + | ===Reserve destination=== | ||
| + | The destination block will be reserved.\\ | ||
| + | Do not use incase the destination is a location.\\ | ||
| + | |||
| + | === Start only with a schedule after DnD === | ||
| + | If no path is found this option will prevent starting the loco after using Drag and Drop.\\ | ||
| + | |||
| + | === Depart side === | ||
| + | Set the __**[[: | ||
| + | \\ | ||
| + | =====Home===== | ||
| + | {{: | ||
| + | With the home action all locomotives with a __**[[: | ||
| + | The Finder will be used to find a path to the Home location.\\ | ||