this is only a minor rearrangement in the Algorithm, but allows to re-boot computation should node connectivity go to zero. With current capabilities, this could not happen, but I'm considering to add a »pruning« parameter to create the possibility to generate multiple shorter chains instead of one complete chain -- which more closely emulates reality for Scheduler load patterns. |
||
|---|---|---|
| .. | ||
| gear | ||
| mem | ||
| DIR_INFO | ||