Search results for all lists

7280 messages found
Sort by
List: time-nuts@lists.febo.com
From: Bruce Griffiths
 
Re: [time-nuts] Common sky pps errors for any GPSDOs?
Mon, Jan 5, 2009 11:03 PM
One can use the datasheet ADEV to estimate worst case ADEV for pairs of such oscillators. To gauge the relative ADEV between oscillator pairs in your environment you will need to make some measurements as the various unspecified thermal time constants of the OCXO will be significant. >> Something else to consider is doing post processing..
List: time-nuts@lists.febo.com
From: Björn Gabrielsson
 
Re: [time-nuts] Common sky pps errors for any GPSDOs?
Tue, Jan 6, 2009 1:11 PM
Then look at the receivers estimate of local oscillator drift for your frequency measurement. This is a fairly simple integration of COTS modules. Since the rovers are not taking advantage of beeing at a surveyed stationary position this is not the optimal solution. Someone on the list with the equipment and time to set this system up?
List: time-nuts@lists.febo.com
From: J.D. Bakker
 
Re: [time-nuts] femtosecond jitter anyone?
Thu, Apr 9, 2009 11:46 AM
Look at the recent TI Asynchronous Sample Rate Converters (ASRCs); their rate estimators have a bandwidth much tighter than needed to track a worst-case AES11 signal.
List: time-nuts@lists.febo.com
From: bg@lysator.liu.se
 
Re: [time-nuts] Better GPS
Sun, Aug 29, 2010 6:51 PM
Yes, but you would only need one dual freq receiver to estimate the Iono. Or have real time access to one in the vincinity. Another way, would be to use the models for Iono and Tropo errors that are available in real time. One example is the SBAS (Waas, Egnos, Msas, etc) signals. They should get you down below 2 meters.
List: time-nuts@lists.febo.com
From: Steve Rooke
 
Re: [time-nuts] Freestanding mast
Tue, Sep 7, 2010 10:29 PM
. > > A preliminary estimate of the McQueen's Valley (MQZG) co-seismic > displacement is 135 mm at about 300 degrees azimuth. This permanent receiver > is located on Banks Peninsula.
List: time-nuts@lists.febo.com
From: Bob Camp
 
Re: [time-nuts] Clock Calibration
Thu, Jan 27, 2011 9:56 PM
Deviations between clocks in an ensemble were used to estimate shorter time periods. I don't find it to unbelievable that you could time an astronomical event to ~ 0.1 seconds or better without anything very fancy being involved. If you wanted to automate it, light sensors date back into the 1850's.
List: time-nuts@lists.febo.com
From: John Miles
 
Re: [time-nuts] Interpreting the ADEV plot in TimeLab
Sat, Oct 22, 2011 1:58 AM
You wouldn't feel confident in your t=86400s accuracy estimate until you had checked it every day for a week, for instance. Even then, you might observe that your watch gains an average of 2 seconds per day the first week, 3 the next week, and 8 the week after that.
List: time-nuts@lists.febo.com
From: Tom Van Baak
 
Re: [time-nuts] Neutrino timing
Mon, Oct 24, 2011 11:45 PM
[time-nuts] Neutrino timing > Tom > Thanks > I see how your comments apply to the later reported test but not so much to > the US experiment IF one accepts as accurate the statements that Marvin > Marshak posted which said in part; > "This U.S. beam has been used to make a similar measurement, > but the GPS timing equipment that was used resulted in an estimated
List: time-nuts@lists.febo.com
From: David J Taylor
 
Re: [time-nuts] Thunderbolt GPS TimeKeeper
Tue, Jan 24, 2012 10:20 AM
The scale on the graphs for PCs Alta and Bacchus does not allow the deviations to be estimated accurately (as they were not originally intended as stratum-1 servers), but the deviation may well be under 0.3 ms. A couple of these PCs have speaking clocks (software) running, and multiple speakers speaking at differing times is rather distracting.
List: time-nuts@lists.febo.com
From: Bob Camp
 
Re: [time-nuts] Heathkit GC-1000 WWVDO
Thu, Mar 1, 2012 6:05 PM
NTP normally just does an estimate of where things should be and moves on. With either WWVB or WWV, the phase change in the carrier is pretty massive. To use carrier phase you would need a multi day average to feed the loop.