Change Request #4052
[DSML] Allow real values and functions
In cases where one has to deal with divisions, real values can not be avoided either.
Real values shall never be enforced, just supported when necessary.
We need the transmission time of a signal over a bus. As we don't know where the signal will be deployed, we cannot divide the signal size by the bandwidth beforehand and are forced to let the solver take care of that.
Theoretically, the values can be precalculated as a matrix, with signals being rows and buses being columns. With both indices, one could look up the precalculated ratio. However, this would require the implementation of a whole new data structure in DSML and its translation to SMT - all for a very specific use case. Given the little effort necessary to allow (but not enforce!) real values, this seems like a more future proof and reusable alternative.
#1 Updated by Tiziano Munaro about 2 months ago
#2 Updated by Tiziano Munaro about 2 months ago
- Run all SMT unit tests.
- Import the projects from https://git.fortiss.org/idea/af3-dse-extension/-/tree/1 and test the schedulability constraints by importing the attached project and modifying
- the bandwidth of the buses,
- the coupling / decoupling of tasks, and
- the message size