From 2c644214711489617f2099a8435c161f17433712 Mon Sep 17 00:00:00 2001 From: MediaPipe Team Date: Thu, 9 Mar 2023 09:47:04 -0800 Subject: [PATCH] Fix minor typos in MediaPipe synchronization description. PiperOrigin-RevId: 515362264 --- docs/framework_concepts/synchronization.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/framework_concepts/synchronization.md b/docs/framework_concepts/synchronization.md index e35e1032d..e12d077a7 100644 --- a/docs/framework_concepts/synchronization.md +++ b/docs/framework_concepts/synchronization.md @@ -113,14 +113,14 @@ Warning: On the other hand, it is not guaranteed that an input packet will always be available for all streams. To explain how it works, we need to introduce the definition of a settled -timestamp. We say that a timestamp in a stream is *settled* if it lower than the -timestamp bound. In other words, a timestamp is settled for a stream once the -state of the input at that timestamp is irrevocably known: either there is a +timestamp. We say that a timestamp in a stream is *settled* if it is lower than +the timestamp bound. In other words, a timestamp is settled for a stream once +the state of the input at that timestamp is irrevocably known: either there is a packet, or there is the certainty that a packet with that timestamp will not arrive. Note: For this reason, MediaPipe also allows a stream producer to explicitly -advance the timestamp bound farther that what the last packet implies, i.e. to +advance the timestamp bound farther than what the last packet implies, i.e. to provide a tighter bound. This can allow the downstream nodes to settle their inputs sooner.