﻿ :: phodd.net :: Magic Microfortnights ::

# --- Microfortnight Clock -

Autoupdater:
Granularity:
Set standard weekday and time:
@::.
Real Microfortnight Time:
Approx Microfortnight Time:

# The Microfortnight Clock

Firstly, you may ask, "What on earth is a microfortnight?"

The answer is very simple. A microfortnight is the period of time that is precisely one millionth of a fortnight; i.e. two weeks.

Curiously, this period of time is exactly equivalent to 1.2096 seconds: There are 24x60x60 seconds in a day, multiplied by 14 days, gives 1209600 seconds. Dividing this by a million gives 1.2096.

This webpage extends the concept of a microfortnight to the level of a timepiece which measures time using that unit. On the way, this provided some unique challenges.

## Designing The Clock

Since time is all about measurement and number, the design required a lot of back-of-an-envelope mathematical scribblings. Some of these are presented here, with as much justification as possible, though perhaps still not enough.

Given that by definition, there are 1000000 microfortnights (henceforth µfs) in two weeks, there are therefore 500000 µfs in one week.

### A few slight hitches

Unfortunately, 500000 is not handily divisible by seven, meaning that there are 71428 4/7ths µfs in a day (Compare: there are 86400 seconds in a day). This means that 'Midnight' on most days does not fall on the tick of the clock!

Yet more issues come about because 71428 µfs per day does not divide well into 24 groups analagous to hours, nor into sensible fractions of those 'hours'.

To work around these inconveniences, the concept of introducing delaying 'leaps' has been borrowed from the greater calendar; i.e. in much the same way the calendar is brought back into line with the seasons by adding an extra day to February every 4 years, the µfClock adds an extra µf here and there to bring itself back into line with ordinary clock time.

### On with the design

Now, to keep things reasonably familiar, we divide the 71428 (or thereabouts) µfs into 24 µf-hours, all the while acknowledging this is not perfect. This makes for 2976 4/21sts µfs per µf-hour (Compare: There are 3600 seconds in an hour).

At this point we could divide that figure by 60 to make some µf-minutes, but that ignores the fact that 2976 (ignoring the fraction for a moment) divides evenly by a relatively large selection of other numbers. While there are other choices available, the decision was made that this clock would be designed around the fact that 62x48 = 2976. A decision was also made that there would be 62 µf-minutes per µf-hour, and 48 µfs per µf-minute, and not the other way about.

Those decisions were largely made to make the µf-clock look as much like ordinary clock time as possible as often as possible.

So far then, we have settled on a clock that ticks 24x62x48 times per day. Or 71424 µfs per day... which is short of the actual number of µfs in a day by 4 4/7ths.

To recover the missing 4 µfs (again ignoring the fraction for the time being), we decide to add a leap µf after each quarter of the day, i.e. after 6am, 12noon, 6pm and 12midnight. We could add them all at the end of the day, but we are trying to spread the corrections out evenly so that they are barely noticeable, and also so that the number of µfs in a µf-minute does not stray too far from the previously set 48.

We have now accounted for all but the remaining 4/7ths of a µf per day; Notice that this translates to 4 µfs over the course of a week.

These can be recovered by simply adding a leap µf at the end of any four days of the week. In this case, the leap µfs are added at the end of Tuesday, Thursday, Saturday and Sunday; Again this minimises the drift of µf-hours from actual hours, and assumes a western week of 5 days starting with Monday and a 2-day weekend to follow. This also has the added bonus of an ever-so-slightly longer weekend, which can only be a good thing!

### Wand'ring hands

Of course, because of the leap µfs, µf-midnight wanders a little relative to actual clock time midnight; This clock labels the days of the µf-week as µfNameofday because they do not exactly tally with the true days of the week. The discrepancy is slight, little more than a second in the worst case, but enough to warrant an alternate label. Secondly, towards the end of an hour, µf-time can look a little strange, with times like 14:61:34. Finally, it can seem very odd to watch a 'seconds' figure tick over from 47 to zero, or even 48 or 49 to zero when the leap seconds are in effect.

## The Approximate µf-Clock

Since the main µf-clock is designed to stick as close to familar 24-hour days as possible, the approximate µf-clock takes this one step further and literally uses the hour (and weekday) from standard time. It then divides the 3600 seconds of the hour into 2976 µf-like ticks and splits these into 62 µf-minutes of exactly 48 µfs, no more, no less.

As a middle ground between the two time systems it fares well, averaging little over one µf behind µf-time, though at worst just over two µfs.

## Why do this at all?

I'm a geek, plain and simple. As such, I have often leafed through - if such a verb is permissable for an online resource - the Hacker Jargon dictionary; More than once I've come across the entry for the microfortnight.

The fact that the number of µfs per second is a short terminating decimal fraction added to the wonderment of it. Had it been something like 1.142857... recurring or even a long terminator like 1.153564453125 I might have been less captured by it. Then again, if you're a bit OCD like me you'll have to find out why I chose the latter constant as an example, and perhaps I might have found myself doing just that, and being captured by it all the same.

Still, I paid a hefty price once I got into this project and realised that the number of µfs per day wasn't a round number!