The more I have thought about splitting the user layer into a composition and parameterisation layer (see #41), and then adding an additional "state" layer as Alex proposed (see #36) the more I think it is a good idea.
One reason I have just come to is that it makes designing (what I reckon will be) a pretty comprehensive experimental layer fairly trivial. What I have in mind consists of:
a duration
a model (consisting of composition & abstraction layers)
initial parameterisation and states (parameterisation & state layers)
"updates" at arbitrary time points using full or partial parameterisation & state layer descriptions.
"recording" (maybe using XPath-like syntax to select model elements)
"playing" to input pre-recorded (or experimental) data.
The more I have thought about splitting the user layer into a composition and parameterisation layer (see #41), and then adding an additional "state" layer as Alex proposed (see #36) the more I think it is a good idea.
One reason I have just come to is that it makes designing (what I reckon will be) a pretty comprehensive experimental layer fairly trivial. What I have in mind consists of:
Something like this
Events and step changes could be implemented by updating the regime from idle to active.
I haven't looked at SEDML so I don't know how close this is to what they have but what do you think?