> I would advise against using python for something like this.
> time.sleep() of python is extremely inaccurate.
Where/when/what/how did you get that idea?
I've had no problems with Python timing. Am I not looking
in the right place? Were you using some really old
software or hardware?
Hi,
Magnus just reminded me, that, since USNO pulled the plug on
the old PTTI paper server, there has not been an official
replacement yet. And for whatever reason, my server doesn't
show up in google.
So if you are looking for old PTTI papers, direct your
browser to http://time.kinali.ch/ptti/
Hi Adam,
It would help to know, numerically, what you're goals or requirements
are. But it sounds like you're not interested in microseconds or
nanoseconds, maybe just milliseconds?
There are untold number of layers of latency in the system you describe,
especially since you're using a
On Sun, 5 Dec 2021 15:53:57 -0500
Adam Space wrote:
> For example,
> the only solutions in Python (which I would prefer to use if possible, but
> not necessary)
I would advise against using python for something like this.
time.sleep() of python is extremely inaccurate. For long
sleep times (a
This is something I have explored from time to time in order to find
a good local display option for Pis running as GIS-disciplined NTP
servers. I've done a lot of exploring and fiddling around with different
options but have yet to find a solution that I am fond of, for the
reasons that you
Most distributions of Linux already have a "clock" application that shows
the system time, but I am wondering how to program a more customizable
display on a Linux system / Raspberry pi. There are a few solutions that
pop up by googling the issue, but these are all insufficient. For example,
the
