From f0fdfa3271a7feeb2cf82596e6c911a917fd6beb Mon Sep 17 00:00:00 2001 From: David Venhoek Date: Fri, 24 Nov 2023 15:30:20 +0100 Subject: [PATCH] Minor adjustment to conclusion. --- validation/24-11-2023-boundary-clock/report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/validation/24-11-2023-boundary-clock/report.md b/validation/24-11-2023-boundary-clock/report.md index 8babd6d0d..19b1ad6f8 100644 --- a/validation/24-11-2023-boundary-clock/report.md +++ b/validation/24-11-2023-boundary-clock/report.md @@ -31,6 +31,6 @@ This shows the offset of the clock of the i210 when synchronized via a boundary ## Conclusions -The results are in line with those seen in the earlier [hardware timestamping validation results](../24-05-2022-hardware-timestamping/measurement_report.pdf), which was expected as no significant changes have occured to the way we adjust the clock. The observed sawtooth patterns indicate that there is signficant gain to be had from improvements in this area. +The results are in line with those seen in the earlier [hardware timestamping validation results](../24-05-2022-hardware-timestamping/measurement_report.pdf), which was expected as no significant changes have occured to how we use the measurements to adjust the clock. The observed sawtooth patterns indicate that we can make significant gains by improving how we use measurements to adjust the clock, and improvements in that are currently under development. With regards to the impact of the boundary clock, this seems to be limited with the current software, making the synchronization about 200ns worse. However, in light of the observed sawtooth patterns it is hard to determine to what degree this is from just the increased frequency of the sawtooth, and what part is actual stochastic worsening.