ActivityDispatching: yield in dispatching has different behavior then iterator when repeats are used
Consider this artificial example:
throughput {
iterations: 3
}
activities {
MoveRobot
MoveRobot
MoveRobot
MoveRobot
}
This could also be written as (read as: 4 repeats of this dispatching activity yield 3 products):
activities repeat: 4{
yield: 3
MoveRobot
}
However the actual behavior is that the unfolded version yields 4*3=12 products in 4 cycles which is wrong.
In simple words: yield should specify the number of products that are produced after the complete sequence has been performed.