From: joshua.clayton@uniwest.com (Joshua Clayton)
To: linux-arm-kernel@lists.infradead.org
Subject: rtc test 2
Date: Wed, 18 Nov 2015 11:03:43 -0800 [thread overview]
Message-ID: <2089317.kdLWbOenKr@jclayton-pc> (raw)
In-Reply-To: <006901d12230$a8641180$f92c3480$@uniwest.com>
On Wednesday, November 18, 2015 10:40:53 AM Alan Miller wrote:
> With 2 points we can generate a time per setting slope (like shown).
> This graph point is 3 seconds out of 172800 or .000174 sec/sec. That?s
> get us to within 4 minutes in a year so a longer test may be needed and a
> better setting passed on with an upgrade. Not sure about the math you have
> Josh ? to get parts per billion, billion should be in the denominator.
Hah. You almost got me there. Made my head spin a little.
To convert from seconds per second to parts per billion, the numerator gets multiplied by a billion.
(technically the denominator gets multiplied too, but the billion is folded into the unit),
i.e. the billion in the denominator is implicit.
>
> Best accuracy to graph with would use the min & max settings for 2 points
> like below ? we now have 1. Maybe the slope is negative but would still
> work if our min/max adjustments can over/under compensate.
We actually do have a second and third data point:
the first test with Adams calculated guess
the test with the maximum adjustsment
I will dig out the emails with those results when I have time,
and when I have recovered some from the math fatigue :)
hopefully they are linear.
--
Joshua Clayton
Software Engineer
UniWest
122 S. 4th Avenue
Pasco, WA 99301
(509) 544-0720
prev parent reply other threads:[~2015-11-18 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2038851.J2zvFTXF8S@jclayton-pc>
[not found] ` <6767947.aE8xIVpPRR@jclayton-pc>
[not found] ` <564A1679.9070700@uniwest.com>
2015-11-18 17:38 ` rtc test 2 Joshua Clayton
[not found] ` <006901d12230$a8641180$f92c3480$@uniwest.com>
2015-11-18 19:03 ` Joshua Clayton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2089317.kdLWbOenKr@jclayton-pc \
--to=joshua.clayton@uniwest.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox