[time-nuts] seeking a time/clock software architecture

Chris Howard chris at elfpen.com
Fri Sep 23 21:00:21 UTC 2011

Seems like a lot of unknowns.  You would have to
have sensors monitoring the sensors.

Do you lose too much by just maintaining a lifetime worst-case number, or
maybe some kind of probability function?

On 9/23/2011 3:45 PM, Poul-Henning Kamp wrote:
> And then it gets nasty:
> 	Vehicle Thermal balance model
> 		a function of:
> 		Vehicle configuation
> 		Vehicle orientation
> 		Nearby objects (sun, planets, moon)
> 		Wavelength
> 	Clock model:
> 		a function of:
> 		vehicle temperature,
> 		bus voltage
> 		gravity
> 		magnetic fields from craft
> 		vibration (micrometeorites, think: Hipparcos)
> 		clock age
> 		random clock internal events

More information about the time-nuts mailing list