Based on my previous experience watching a roost in Woodbury last fall, where a fellow observer Russ counted 938 swifts, I estimate that there are around 300 swifts here, but possibly even more. The chimney is located on 149 York St and I watch the spectacle from the 7th-floor garage right across the street.

After 1PM, I walked the sandbars during low tide: Frank Mantlik's Laughing gull flock was visiting and was loud and active along the shoreline (estimating 200), 2 Great Black backed gulls, (herring & ring billed gulls) Piping plovers- some on sand bar, 3 in nest exclosure with 3 chicks running around, 7 American Oystercatchers (1 with yellow leg bands)

Regarding the OP's remark that it's not so easy to make Beziers match curves on an imported bitmap, there is indeed some initial learning to be done, but have gotten quite adept at estimating where I need to put control points to approximate any curve to an appropriate amount of detail, as well as gotten acquainted with the Inkscape Bezier tools, which help a

You might have to resort to invoking it 10^6 times (or more) and using the overall execution time to get an estimate. On Sun, Feb 9, 2025 at 2:34 PM John David via Discuss < discuss@lists.openscad.org> wrote: > I was thinking along the lines of: > > start = time(); > mymodule(); > echo(time() - start); > > If time is given in ms, then this makes sense.

You typically use GNSS to measure / estimate asymmetry and compensate. Turns out that WAN networks offer larger challenges than PON, since IP networks does not really have any guarantee for two directions between two nodes take the same path. In fact, for traffic engineering reasons it can vary quite a bit in some cases.

algorithm > actually originating in the world of direction detection, applied to > frequency estimation.

>simple arithmetic with a timescale with a variable second would give an order of magnitude better estimate of the amount of time between 2005 Dec 31 23:59:59.9 and 2006 Jan 01 00:00:00.1 than UTC does! UTC will tell you that there is EXACTLY 1.2 seconds between those two points.

They certainly are related, however the relation (especially around the speed of sound) is difficult to estimate.

The mathematicians on duty could estimate the best achievable plot for a sample HP oven osc trained by NTP (with some periodic query, filtering, etc.) Same problem as "Can I set my watch by the Rooster's call every morning?" (no DST needed here!)

In the specific case of the Trace Duration field, TimeLab will estimate the rate at which readings arrive from the counter if you press the "Monitor" button and wait a bit for the estimate to settle down. If it doesn't seem to be converging on the right rate, try toggling the Monitor button off and on.