Version: 4.1.1 (using KDE 4.1.1) Compiler: gcc 4.2 OS: Linux Installed from: Gentoo Packages When running the digital clock plasmoid with seconds turned on and visually comparing this to the Qt example code clock from the Qt web site that has been modified to add a second hand I noticed that the plasmoid digital clock was about 3/4s of a second behind the system time as displayed by the modified Qt example code clock. I had a look at the digital clock plasmoid code and it appears that the time is updated in response to a signal that calls the dataUpdated(..) slot and that this signal is aligned to Plasma::AlignToMinute. It appears that there is a significant latency between the actual minute alignment of the system clock and when the dataUpdated(..) slot is called. Since I use a high accuracy reference clock (Motorola OnCore UT+) to drive ntp on my system and this keeps my system clock correct to with in about 20 microseconds of UTC (worst case but most of the time to with in 5 microseconds) I was disappointed to see that the time displayed in the digital clock plasmoid is off by about 750,000 microseconds. According to authoritative sources a difference of more than 1/4 second between two clocks is something that is apparent to most observers. So you should try to reduce this latency to below 1/4 second.
we will work on accuracy and what not, but microsecond accuracy of timing devices isn't a design goal for plasma.
I guess I didn't communicate the issue very well. I merely pointed out that my system clock has near microsecond accuracy*. I stated that your goal should be to get the plasma clocks to change the displayed time within 250 milliseconds (1/4 second) of the actual seconds epoch of the system clock. This is a far cry from microsecond accuracy (by more than 4 orders of magnitude) and it is a fairly loose requirement as time keeping things go. I didn't ask for the plasma clocks to have microsecond accurate displays. The Qt timer functions only have a millisecond resolution and I think this puts a lower bound on how accurate these plasma clocks can be. In other words I only want the plasma clocks to have a low enough latency that it is not apparent that there is a significant lag between the plasma clock and the system clock. Of course if you can get the plasma clock synced more tightly to the system clock (for example if you where to get the latency below for example 50 milliseconds) then that would be a good thing. The US NIST, which is considered the worlds experts on time related issues, says the following in "WWVB Radio Controlled Clocks: Recommended Practices for Manufacturers and Consumers" (see http://tf.nist.gov/general/pdf/1976.df page 5) "3. RECOMMENDED PRACTICES FOR CLOCK ACCURACY, CLOCK DISPLAY AND CONTROLS ALL RCC products should display time accurate to at least within +-0.5 s, so that when the time is rounded to the nearest second, the seconds value is always correct. Tighter synchronization (to within +-0.2s) is desirable. This prevents the human eye from detecting any errors when checking a RCC display against another independent time reference, whereas a 0.5 s error could be noticeable." As you can see NIST states that latencies much greater than 0.2 seconds can result in the human eye detecting the offset. I am only asking that the latency of the plasma clocks be low enough that it "prevents the human eye from detecting any errors". The current plasma clocks have a latency that appears to be close to 750 milliseconds which is well above the maximum error that is recommended by NIST. It is also very apparent to human observers. My main goal was to give you some concrete information about this so that you would put in place a requirement to reduce the latency to the point it "prevents the human eye from detecting any errors" and to give you some guidance on what latencies will give a result that meets that requirement (IE. under 200 milliseconds). * This is admittedly an unusual setup since it requires a patched kernel and special hardware. There are probably only a few hundred Linux machines in existence that are configured this way. But a commonly used and fairly simple setup using ntp and Internet based time servers can easily keep the local computer clock synced to within 10 milliseconds of the actual time and with careful selection of time servers this type of setup can get the clock offset into the 1 to 2 millisecond range. Even for this simple time keeping setup the plasma latency errors are over 2 orders of magnitude greater than the local clock errors.