From 3592a7e928008b0e89286c91aa72b4db89a50d5f Mon Sep 17 00:00:00 2001
From: Steven Baltakatei Sandoval <baltakatei@gmail.com>
Date: Fri, 3 Jul 2020 20:58:01 +0000
Subject: [PATCH] doc(bkgpslog-plan):Closed TODO item

---
 exec/bkgpslog-plan.org | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/exec/bkgpslog-plan.org b/exec/bkgpslog-plan.org
index b7cc736..47154eb 100644
--- a/exec/bkgpslog-plan.org
+++ b/exec/bkgpslog-plan.org
@@ -33,7 +33,8 @@ done using a new function ~checkMakeTar~.
 magicWriteVersion() to be called whenever a new time-stamped ~VERSION~
 file needs to be generated and appended to the output tar file
 ~PATHOUT_TAR~.
-** TODO Rewrite buffer loop to reduce lag between gpspipe runs
+** DONE Rewrite buffer loop to reduce lag between gpspipe runs
+   CLOSED: [2020-07-03 Fri 20:57]
 2020-07-03T17:10Z; bktei> As is, there is still a 5-6 second lag
 between when ~gpspipe~ times out at the end of a buffer round and when
 ~gpspipe~ is called by the subsequent buffer round. I believe this can
@@ -47,7 +48,16 @@ while( $SECONDS < $SCRIPT_TTL); do
     writeBuffer &
 done
 #+END_EXAMPLE
-
+2020-07-03T20:56Z; bktei> I simplified it futher to something like
+this:
+#+BEGIN_EXAMPLE
+while( $SECONDS < $SCRIPT_TTL); do
+    writeBuffer &
+    sleep $SCRIPT_TTL
+done
+#+END_EXAMPLE
+Raspberry Pi Zero W shows approximately 71ms of drift per buffer round
+with 10s buffer.
 * bkgpslog narrative
 ** Initialize environment
 *** Init variables
-- 
2.30.2