The electrical length of the adapter could be estimated with a high degree of accuracy with a ruler amd knowing the diectric constant (its usually PTFE).

When cost estimates start running into the billions of dollars, looking for an easy way out is not optional any more, then it becomes a duty. And saving even a few tens of millions of dollars can never be a shamefull thing for anybody. >Time is complex. Embrace the complexity. No, geology and orbital mechanics is complex.

The prior antenna estimate was: 39:11:24.692 123:09:50.548 819.224 feet A second of lat is about 100 feet anywhere so the delta Lat is about 10 feet A second of lon at 39N is about 77.5 feet so the delta Lon is about 5 feet The 100 feet elevation difference escapes me.

In the 5052B you have a PLL with non-zero bandwidth, so below some offset you probably get an optimistic estimate because the PLL is actually following the noise.

With a few > external network servers you can also estimate approximate delay or > offset.

The flying clock allowed a very nice complement as it allowed the removal of time-bias which could only be estimated. > I know in North Carolina, USA a law was still on the books a few years ago > that it was illegal to look at your wife naked. Law is often slow to catch > up with society and technology.

Thus, only for short-term stability may straight averaging work for estimation. Cheers, Magnus

Use overlapping or similar estimator to get good > It seems to be common lore that the Allan variance minimum is the best > obtainable frequency accuracy for an oscillator, but the least squares > fits seem to be much better. I have problems understanding this. Allan Variance/Deviation performs a particular filtering prior to squaring and averaging.

I got a chance to verify some of the points that I feel is important, such as separation of noise and systematic effects, and that the definition of the scale shall not be confused with the form of the estimators (non-overlapping, overlapping, Hadamard, TOTALDEV, Theo etc.) once bias-corrections have been done.

It's easy to get a pulse at 1 ms intervals when the code epoch comes by, but you really want to get a range estimate, and that means figuring out where you are in the bigger scheme of things. and, then getting that ingested into whatever computation scheme you're using. > > > > _______________________________________________ > > time-nuts mailing list -- time-nuts