The other day, @philikir000 and I were displeased with the way that time is measured. Every unit of measurement has an Imperial (US) and Metric (everywhere else) variant. Length, volume, mass, temperature, etc. The only one that doesn’t have a metric equivalent is time. Just like any other Imperial unit, it’s quite odd. 60 seconds in a minute? 60 minutes in an hour? 24 hours in a day?? Today, we solve that. Behold: The Chron! (Pronounced kron) “Metric Time,” as we’ve dubbed it (not to be confused with actual Metric Time), is inspired by the scale of the meter and is coincidentally similar to Decimal Time. (Look it up!) The Conversion ratios can be seen below: Imperial to Chrons: 1 day = 1 kilochron = 1000 chrons 1 hour ≈ 41.667 chrons 1 minute ≈ 0.6944 chrons = 69.444 centichrons 1 second ≈ 1.1574 centichrons Chrons to Imperial: 1 kilochron = 24 hours 1 chron = 1.44 minutes = 86.4 seconds 1 centichron = 0.864 seconds Because there are only 10 Hectochrons (100 Chrons) in a day, the clock measures from 0-9, with 0 being Midnight, 250 being 6 AM, 500 being Noon, and 750 being 6 PM. Now, for the clock on your screen. This is our first prototype of the Metriclock, which (supposedly) adapts to your time zone to show what Chron it is. The time is determined using the (days since 2000) block, which always gives a number from the UTC timezone. Using this information and the (current [hour]) block (which does adapt to your timezone) and some other stupid math, we’re done! A fully functional clock. If you have any questions, please ask in the comments.
