From 01a56d3cf75a7198ae6c28955bed14c20a8b0370 Mon Sep 17 00:00:00 2001 From: moi15moi Date: Tue, 17 Dec 2024 18:34:12 -0500 Subject: [PATCH] [doc] Remove example Since the version 0.1.0, we don't use integer anymore to represent the time of a frame. --- docs/Algorithm conversion explanation.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/docs/Algorithm conversion explanation.md b/docs/Algorithm conversion explanation.md index f5495e5..595de3d 100644 --- a/docs/Algorithm conversion explanation.md +++ b/docs/Algorithm conversion explanation.md @@ -57,19 +57,6 @@ The interval for each type of timing are defined like this: ``` -But, for our case, the interval are always integer, so it gives: - -```math -\begin{gather} -\text{EXACT : } [\lceil \text{CurrentFrameTimestamps} \rceil, \lceil \text{NextFrameTimestamps} \rceil - 1] \\ -\text{START : } [\lfloor \text{PreviousFrameTimestamps} \rfloor + 1, \lfloor \text{CurrentFrameTimestamps} \rfloor] \\ -\text{END : } [\lfloor \text{CurrentFrameTimestamps} \rfloor + 1, \lfloor \text{NextFrameTimestamps} \rfloor] -\end{gather} -``` - -The interval are integer because float/double don't have infinite precision, so there are some rounding issues that we don't want. But, there is a drawback. We cannot have a higher precision then the unit that the integer represent. So, I arbitrarily choosed to use nanoseconds because in all the chapter and subtitle format that I know, this is the smallest unit available. - -