From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: how to analyze clock drift Date: Wed, 19 Nov 2014 02:44:18 +0000 (UTC) Organization: Aioe.org NNTP Server Message-ID: References: <6uun6alsp3jh1pob6g9qgcg85etqgenmd0@4ax.com> NNTP-Posting-Host: ru/enNNyVkms/PPjid3aKA.user.speranza.aioe.org X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Tom's custom newsreader Xref: news.eternal-september.org comp.lang.ada:23536 Date: 2014-11-19T02:44:18+00:00 List-Id: >>Anyone knows how I can apply some math/stat method to >>find out the average drift, and/or if the drift will >>average out, or just about any conclusions you can get >>out of the material? >> > > Feed the data to "R" and play around with various commands? To quote Richard Hamming "The purpose of computing is insight, not numbers". What is it that you want to know here? How do you hope to make use of what you learn?