Timelines documentation - #415
Conversation
…dition of matching timelines
|
Include the example Lourens suggested in multiscale/ymmsl-python#66: "I think it would be good to have an example of an init component dispatching to a micro with one or two filters, because that's the first use case for BRIDGE." |
…ivalence' into timeline-docs
LourensVeen
left a comment
LourensVeen
left a comment
There was a problem hiding this comment.
This is super nice! Clear, concise, and hopefully not too computer sciency and abstract, which is a common complaint about anything related to MUSCLE3 and MMSF. We'll see what the users think, but I don't see a way of doing it better.
I added a few comments that you may want to look at, I'll leave it to you to decide since your background is closer to that of the users than mine.
| In that case you can declare the two timelines as matching timelines. Each | ||
| component still has its own timeline, but conduits between ports on matching | ||
| timelines are then allowed. See the yMMSL documentation on | ||
| :external+ymmsl:ref:`matching_timelines <Matching timelines>` for how to |
There was a problem hiding this comment.
These external references don't seem to work, but maybe that's just because they're not pointing at the right version?
There was a problem hiding this comment.
Ah, yes, stable, so that should start working after the release. Although maybe we can change it to develop temporarily to test?
There was a problem hiding this comment.
I’ll change it to develop. Would you like me to just check it, or should I leave it as is and change it back after we’ve merged the Timeline Bridge documentation?
2 participants
No description provided.