| Re: [app4mc-dev] SOA - Amalthea Modelling Language |
|
Hello, comments below… Best regards From: app4mc-dev <app4mc-dev-bounces@xxxxxxxxxxx>
On Behalf Of Ibrahim Özcan Hello Dear Harald, I am not sure whether my understanding of local and global mode and the labels related to modes is correct. For example, is Ignition ON a global mode, and global mode label is used to represent that mode? In effect, this is simply particular
state of the system, right? Local mode labels are even less clear to me. Do they simply reflect the different execution paths of the runnable? Again, this could be simply related to some state, the runnable is in, right? But then the conditions used for instance
in Switch, can be only built comparing integer values – isn’t this a relevant limitation? [Harald] ModeLabels are system-wide states. They have initial values and can be manipulated. Their main purpose is to specify different execution paths that are relevant in different modes. An additional possibility is the "user-defined" scheduling behaviour. For that reason we introduced numeric mode labels that can be used as counters. LocalModeLabels describe an execution context local to an Executable (Task, ISR, Runnable).
In addition, I realized that there is no local variable. For example, runnables write and read labels but there is no specification (behavior) to manipulate these labels. There is no way to assign those labels to a local variable after
a runnable reads the label. And, when a runnable writes a label, you cannot specify what you are writing into it. [Harald] We wanted to make very clear that the AMALTHEA model only describes timing (for computation, access to memory, etc.). Therefore labels have no specified values! On the attached example, it shows that the runnable does something when the condition holds. I assume Amalthea is not capable to define such behavior. Are you aware of any work which tries to extend Amalthea to enable the modeling of such
behavior? Or maybe a valid assumption could be to use there for instance Matlab Simulink? [Harald] This was never in the scope of the AMALTHEA model. If you want to combine "Timing simulation" (like TA Tool or ChronSim) and "Functional simulation" (like Matlab Simulink) this can be done by co-simulation via FMI (https://fmi-standard.org/). Finally, Amalthea is supposed to enable a system synthesis (i.e. partitioning), and optimization. Are there any tools which can do that, both free and commercial? I know TA Tool can simulate timing models of Amalthea, but it does not suggest
proper partitioning, which could preserve the semantics of the runnables’ execution. [Harald] I do not know what commercial tools are offering… Best regards, Ibrahim Özcan |