art ; Discussion of precise time and frequency
> measurement
> Sent: Thursday, January 12, 2017 2:38 PM
> Subject: Re: [time-nuts] General questions about making measurements with
> time interval counter.
>
> Hi
>
> Keep in mind that when you do 1800 samples at 1
and frequency measurement
Sent: Thursday, January 12, 2017 5:22 PM
Subject: Re: [time-nuts] General questions about making measurements with time
interval counter.
Bob,
The minimal C code for (back-to-back or overlapping) ADEV is:
stride = overlap ? 1 : tau;
for (sum = n = i = 0
f precise time and frequency
measurement"
Sent: Thursday, January 12, 2017 2:36 PM
Subject: Re: [time-nuts] General questions about making measurements with time
interval counter.
The pesudo code for the Adev is quite easy to interpret.
For a frequency record of N samples
For each tau=M samples
rectly, too.
>
>
>
> Bob
>
>
>
>
>
> From: Bob Camp
>
> To: Bob Stewart ; Discussion of precise time and
> frequency measurement
>
> Sent: Thursday, January 12, 2017 2:38 PM
>
> Subject: Re: [time-nuts] General questions about making measu
bably stated that
incorrectly, too.
Bob
From: Bob Camp
To: Bob Stewart ; Discussion of precise time and frequency
measurement
Sent: Thursday, January 12, 2017 2:38 PM
Subject: Re: [time-nuts] General questions about making measurements with time
interval counter.
Hi
Keep in mi
>> Bob -
>> AE6RV.com
>>
>> GFS GPSDO list:
>> groups.yahoo.com/neo/groups/GFS-GPSDOs/info
>>
>> From: Bob Camp
>> To: Bob Stewart ; Discussion of precise time and frequency
>&
Subject: Re: [time-nuts] General questions about making measurements with time
interval counter.
Hi
It varies from 5370 to 5370. You see a lot of plots that run out to 10 samples
or less. Anything below 100 samples
is risky in some senses.
Bob
> On Jan 12, 2017, at 12:25 PM, Bob Stew
f precise time and frequency
> measurement
> Sent: Thursday, January 12, 2017 11:04 AM
> Subject: Re: [time-nuts] General questions about making measurements with
> time interval counter.
>
> Hi
>
> There is a big difference between RMS and single shot. Single shot, the 53
January 12, 2017 8:27 AM
> Subject: Re: [time-nuts] General questions about making measurements with
> time interval counter.
>
> Hi
>
> There are a number of ways to improve the resolution (and accuracy) of your
> data without spending
> big piles of cash. They hav
frequency measurement
Sent: Thursday, January 12, 2017 8:27 AM
Subject: Re: [time-nuts] General questions about making measurements with time
interval counter.
Hi
There are a number of ways to improve the resolution (and accuracy) of your
data without spending
big piles of cash. They have been
Hi
There are a number of ways to improve the resolution (and accuracy) of your
data without spending
big piles of cash. They have been discussed here on the list many times over
the last few years.
What I’m suggesting is that you dig into that ahead of taking data. You will
dive into it event
On 12 January 2017 at 02:31, Bob Camp wrote:
> Hi
>
Hi Bob
>
> The most basic issue you are going to run into is that your counter is not
> high enough
> resolution / accuracy to give you meaningful data for time intervals under
> a few hundred
> seconds.
Is that true if I'm not testing very
Hi
The most basic issue you are going to run into is that your counter is not high
enough
resolution / accuracy to give you meaningful data for time intervals under a
few hundred
seconds. I would focus on improving on that part of things before I went off on
a major
“test everything” adventure.
MY AIMS
1) Try to learn about the various statistical tests (ADEV, MDEV etc), and
how best to compare oscillators, by making some measurements on various
oscillators I have.
2) Investigate the short/medium term stability of the output of various
bits of test kit. All are locked to GPS by feeding
14 matches
Mail list logo
