Broken Routes from the bus minimization / the bus minimization objective does not reduce the number of routes over busses if the objective is defined for one bus
Observed bugs
Assume the following structure:
—Bus—
| |
E E
| |
—Bus—
- When defining a single objective to minimize the number of busses, routes are generated traversing all busses. This implies that selected bus is not minimized.
- Only when defining two bus minimization targets and including them in the minimization, the number of routes over different busses is minimized.
Discussion
It seems that the bus minimization objective is not operating as
intended. According to the observations, it seems that the objective
should be defined on a set of Busses to be minimized, which would also
improve UX.
However, one of the root of the problem could be that the created
expressions refer only to the selected transmission unit, instead of the
set of present transmission units (from which only one or more busses
selected bus are optimized away).
Another problem to be investigated is the route calculation performed by
the solving the optimization problem: In the second example (see below),
the route “Route_HeadUnitECU_PowertrainECU” is broken, which can be
easily seen in the attached xml.
Example
See attachment. For each of the following setups, allocation constraints were defined that force two communicating Tasks onto different ECUs.
- Allocation-MinFlex —>4 different routes present (2 Busses * 2 Directions). NOTE: 4 out of 6 Routes are broken.
- Allocation-MinFlex+MinGeneric —>2 different routes present. NOTE: 1 out of 2 Routes are broken.
(from redmine: issue id 4021, created on 2020-05-14, closed on 2020-08-12)
- Uploads: