Summary
The current parking coordinator uses a simple "grab and go" approach that may be inefficient for large scenarios. There's no way to configure batching behavior or prevent retrofitted track overflow. "Grab and go" is opportunistic. If a loco is idle it will grab the loco and get as much wagons from the track if there is space on the chosen parking track. In many cases this leedds to small rakes and in the end to a lot of coupling and decvoupling time.
Acceptance criteria
Implement two configurable strategies:
Summary
The current parking coordinator uses a simple "grab and go" approach that may be inefficient for large scenarios. There's no way to configure batching behavior or prevent retrofitted track overflow. "Grab and go" is opportunistic. If a loco is idle it will grab the loco and get as much wagons from the track if there is space on the chosen parking track. In many cases this leedds to small rakes and in the end to a lot of coupling and decvoupling time.
Acceptance criteria
Implement two configurable strategies: