[time-nuts] lunatic fringe time standards
lists at rtty.us
Thu Apr 15 11:30:27 UTC 2010
I'm not 100% sure I understand exactly what you are thinking about setting up. My guess is that the counter needs to run at the same THz speed as the oscillator. That's pretty fast. I suspect that what ever you use, speed / propagation delay in the counter it's self will be an issue. That will get you back to either a ripple counter or a Johnson counter.
On Apr 15, 2010, at 7:07 AM, Eugen Leitl wrote:
> On Thu, Apr 15, 2010 at 02:48:58AM -0700, Hal Murray wrote:
>> I'm not aware of anything like I think you are describing.
>> What problem are you trying to solve?
>> The main reason that I think of using gray codes is for crossing clock
>> But as Magnus pointed out, another possible problem is just counting at high
> I was idly musing about how to reliably count an integrated solid-state
> THz oscillator adjacent to a (very wide) counter. The problem is due
> of relativistic signal delays which are in the ballpark of counter
> feature size. A way to circumvent that is to keep relevant state changes
> to the oscillator lightcone. Hence Gray codes with local bit flips,
> or something similar.
> The compensation for drift and e.g. relativistic (spacetime curvature
> and motion) effects would happen by directly applying small numerical
> deltas to the ALU downstream of the counter. The result would be a
> clock directly compensated against movement and position in a gravitation
> Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org
> ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org
> 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
More information about the time-nuts