You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Matches in SRComp are represented as having two timing boundaries:
the slot, which is the time that that match can be thought of as having priority in the arena (i.e: it is being set up, run or torn down), and
the game, which is the time when the match is actually playing
The game portion is at most the same duration as the slot, though for practical reasons is likely to be non-trivially smaller. However there is nothing which requires that a game be in the middle of a slot. While that is the most common configuration, it could be at one end or the other.
Mixtape on the other hand assumes that it can listen to the event stream for the match events, which are fired when the stream detects that the "current" match has changed. (The bounds of the "current" match are those of its slot).
As Mixtape has no other source of timing information: if a compstate were configured which had the game starting at the start of the slot then mixtape would always be "late" to the start of the match -- the match even from the stream would happen a few seconds after the actual start time (the stream polls for changes about every 2 seconds) and mixtape is downstream from that.
The text was updated successfully, but these errors were encountered:
Matches in SRComp are represented as having two timing boundaries:
The game portion is at most the same duration as the slot, though for practical reasons is likely to be non-trivially smaller. However there is nothing which requires that a game be in the middle of a slot. While that is the most common configuration, it could be at one end or the other.
Mixtape on the other hand assumes that it can listen to the event stream for the
match
events, which are fired when the stream detects that the "current" match has changed. (The bounds of the "current" match are those of its slot).As Mixtape has no other source of timing information: if a compstate were configured which had the game starting at the start of the slot then mixtape would always be "late" to the start of the match -- the
match
even from the stream would happen a few seconds after the actual start time (the stream polls for changes about every 2 seconds) and mixtape is downstream from that.The text was updated successfully, but these errors were encountered: