This test case contains various ways of setting up timing relationships. Objects can be started at the same time using the <par> element. Objects can be started after one another using the <seq> element. Finally object can be ended when other objects end using the syncbase end timing attribute (end="xxx.end").
A <par> time container contains a sequence and an aqua rectangle. The sequence that contains a red rectangle followed a nested <par> time container. The nested <par> contains two additional sequences. The the nested sequences run in parallel and each contains two rectangles. The second rectangle (fuchsia) in one of the nested sequences ends when the aqua rectangle ends.
A red rectangles starts the container sequence at t=0s and lasts for 5s. An aqua rectangle starts at t=3s and lasts for 9 seconds (t=12s) After the red rectangle ends (at t=5s) the two sequences commence in a par container. One sequence has a green rectangle for 5s followed by a blue rectangle for 5s. The other sequence has a yellow rectangle for 3s followed by a fuchsia rectangle. The fuchsia rectangle ends when the aqua rectangle ends at t=12s.
The diagram at the top of the windows displays the timing relationships and highlights when the various rectangles exist.
Snapshot taken of IBMTimeContainersParSeqEndSync.mp4
![]() |
t=0s
|
![]() |
t=3s
|
![]() |
t=5s
|
![]() |
t=8s
|
![]() |
t=10s
|
![]() |
t=12s
|
![]() |
t=15s
|