Exclaves, Enclaves, and Doughnuts

In which we explore the strange paths taken by national borders around the worldAlso, doughnuts. Mmmm, doughnuts…

Most national borders that exist today are the result of many decades (or even centuries) of redrawing, and these redrawings were often entangled with the wars, treaties, or imperial ambitions of the time. Sometimes, the border is the result of a very clear principle—for example, the US-Canada border runs neatly along the 49th parallel for much of its length (though this article shows how it’s not quite that simple). Other times, it’s the result of a long an torturous process—compare this map of the Holy Roman Empire in 1786 with the simpler subdivisions of the modern state of Germany. [Side note: all maps from this point onward are taken from Google Maps.]

In this post, I’ll share some examples of unusual national borders—just to get the lay of the land. In the next post, I’ll examine some of the most complicated examples, and begin to apply a mathematical concept (the fundamental group) that, hopefully, will clarify the messy business of national borders.

Before going any further, though, some terminology is in order.

Enclave: an enclave is any portion of a state/province/country that is completely surrounded by another state/province/country. One good example of an enclave is the entire nation of Lesotho, which is “enclaved” within South Africa.

Exclave: an exclave is a portion of a state/province/country that is separated from the main part by multiple states/provinces/countries. A good example of this is the Kentucky Bend, a portion of the US state of Kentucky that is surrounded by Missouri and Tennessee.

An interesting side note: the western borders of Kentucky and Tennessee are defined by the Mississippi River, following the course it ran when originally the border was originally defined. Over the years, most rivers will change their course in multiple places, which means that many states have small chunks that lie on the opposite side of the Mississippi River (go explore the above map to see what I mean). These are called pene-exclaves, since the border doesn’t separate them from their state, but rather a geographic feature (in this case, the river).

Warning! These definitions are not mutually exclusive. Some, but not all, exclaves are also enclaves. To avoid confusion, I’ll just say exclave to mean one portion of a country that’s separated from the main part, and enclave to mean a country that’s completely surrounded by a single other country.

Another Warning! These definitions depend on which country you’re referring to. One example of this is the Spanish town of Llívia (see map below); it is enclaved within France, but it is an exclave of Spain.

Let’s see what else is out there! We continue our tour through Europe:

Enclaved Countries. There are a number of microstates in Europe, but only two of them are true enclaves: San Marino and Vatican City, both surrounded by the Italian Republic. These two, along with Lesotho, give us all of the world’s enclaved countries.

Alpine Villages. The Alps are host to two interesting exclaves, both surrounded by Switzerland. One is the Campione d’Italia; it’s surrounded by the southern Swiss canton of Ticino. The other is Büsingen am Hochrhein, a German town surrounded by Schaffhausen canton.

The Politics of Railroads. The Belgium/Germany border is host to a strange series of exclaves.

As you can see from the map, there are five German exclaves surrounded by Belgium (one of which is just a house & its yard), which are just barely separated from their homeland. There are two roads and a rail line running to the east of these exclaves, which are owned by Belgium. Apparently, the entire thread of territory was once a rail line (the Vennbahn) that Germany ceded to Belgium as part of the Treaty of Versailles. The roads intersect with German roads and highways, but are still Belgian. It’s really strange—go poke around the map.

Doughnuts. Lest we spend all of this post in Europe, the Arabian peninsula is host to a fascinating little enclave/exclave situation. The village of Nahwa strides the border of Oman and the United Arab Emirates (UAE), which itself isn’t all that unusual in itself. However, the UAE portion is part of an enclave, surrounded by Omani territory which is itself surrounded by UAE territory, thus creating a doughnut-shaped chunk of Oman inside of the UAE.

The innermost UAE territory is an example of a second-order exclave: an exclave within an exclave. This might seem to be the height of absurdity when it comes to national borders, but it turns out we’re only getting started. In my next post, we will hit the accelerator and see how complicated things can really get—including a look at the world’s only third-order exclave.

See ya next time!

Physical Analogies: Making the Inconceivable Conceivable

In which we explore some of the more unusual attempts to make huge numbers more understandable.

In the modern world, there’s always a problem when explaining the realm of the very large or the very small to a general audience. When you’re faced with the fact that the sun is 333,000 times more massive than the Earth, which itself is billions of times more massive than the largest of objects that a person would come across in a typical day, you need to find creative ways to bridge the cognitive gap.

Often, this ends up producing some silly results. I’ve been collecting examples for several months now, and now it’s time to share! I will go in order from least silly to most silly.

1. The Astronomical Unit. In Mark Anderson’s book, The Day The World Discovered The Sun, the author recounts an analogy used by John Lathrop in his 1814 work “Lectures on Natural Philosophy” to put the Earth-Sun distance into context. According to Lathrop, the distance from the Earth to the Sun is “…so prodigious that a cannon ball going at the rate of 8 miles in a minute would be more than 22 years in traveling from our globe to the central and solar luminary of its orbit.” This analogy seems mildly silly, but only because a cannon ball is an archaic reference to most modern readers.

2. Precision of Atomic Clocks. This one is a case where the very large is used to explain something very small. Back in January, NPR aired a story “Tickety-Tock! An Even More Accurate Atomic Clock.” The reporter, Nell Greenfieldboyce, described a new atomic clock “…that would neither gain nor lose a second in 5 billion years.” This is just a way of contextualizing the fact that the clock is accurate to 0.2 nanoseconds over the course of a year. However, the report ends by musing that, one day, atomic clocks could be so accurate that they’d lose only 1 second every 50 billion years—a time interval more than 3 times the age of the universe. A true analogy, yes, but a little silly, too.

3. Randall Munroe’s What If? Blog. Munroe has become his own cottage industry of quirky physics speculation, and there’s no better example that his blog, What If?, in which he answers physics questions from readers. In one post, to explain exactly how fast the International Space Station moves as it orbits the Earth, he determines that while listening to the Proclaimers’ song I’m Gonna Be (500 miles), you’d travel about 1000 miles. In another post, he describes the precise flight path of the Rosetta spacecraft as being “…like throwing an object from New York and having it hit a particular key on a keyboard in San Francisco.”

4. The BP Oil Spill. Of course, I’ve saved the best ones for last. If you’re familiar with The Bugle podcast, you might know what you’re in for. In episode 116, John Oliver quotes a news article as saying that the 19 million gallons of oil spilled in the first 5 weeks of the BP oil spill is enough fill a line of 1 gallon milk jugs stretching from New York to Chicago, and back. In episode 117, an adventurous listener wrote in with another analogy—undoubtedly the most silly of the bunch. Specifically: If all the oil spilled in one day were frozen and molded into cricket bats, then laid end to end, it would stretch from London to Paris and back. Also, if you took all the oil spilled by May 1, the cricket bats would stretch from Caracas to Pyongyang and back. Silliness, we have a winner!

At some point, though, all of these examples—whatever their intention—are wrestling with the fundamental fact that daily human life occurs on a very specific scale in time and space, while the universe as a whole covers a much wider range. On some level, this means every physical analogy will seem at least somewhat absurd. I don’t see the silliness ending any time soon! In fact, if you take all the words from all physical analogies published since 1800, represent each one with a pack of gum, and line them up end to end, … okay, you get the idea.

Friday Fun: Calendar Outtakes

The best part of a comedy film is when the actors make small mistakes, and the cast and crew bust out laughing. It’s become common to run outtakes during the credits (by the way, this was first done by Peter Sellers in Being There, in 1979).

Here, I want to share some odd, silly, and independently interesting factoids about how our calendar systems have come up short—sometimes with dire consequences. These factoids all come from Nachum Dershowitz & Edward Reingold’s Calendrical Calculations, which I used last November for my dual posts on Thanksgiving and Hanukkah.

First up, a manufacturing disaster:

“…a computer software error at the Tiwai Point aluminum smelter at midnight on New Year’s Eve [in 1996] caused more than A$1 million of damage. The software error was the failure to consider 1996 a leap year; the same problem occurred 2 hours later at Comalco’s Bell Bay smelter in Tasmania.” [Reported in New Zealand Herald, 8 January 1997.]

This next one was an inconvenience for business travelers:

“…Microsoft Windows 95, 98, and NT get the start of daylight saving time wrong for years, like 2001, in which April 1 is a Sunday; in such cases, Windows has daylight saving time starting on April 8. An estimated 40 million to 50 million computers are affected, including some in hotels that are used for wake-up calls.” [Reported in New York Times, 12 January 1999.]

These two examples, while significant, had consequences that were relatively short-lived. But would you believe a calendar irregularity caused repeated political crises over the course of several centuries? It’s true, as the Ottoman Sultans would have told you. Some background information first…

The Ottoman Empire used the Islamic calendar, which is a lunar calendar with 12 months of 29 or 30 days. There are 11 leap days added every 30 years, so the average length of the year is 354 11/30 days. Obviously, this means that the Islamic calendar drifts throughout the solar year (about 11 days each year), and so the months don’t have any real connection to the changing seasons. April is always a spring month, but Ramadan can occur in any season.

Back to our story: when it came to finances, the Ottomans used the Islamic calendar for expenditures, but since many of the revenues came from seasonal activity (like farming), they used a solar calendar for tax collection. There are about 32 solar years for every 33 Islamic years, and in the 33rd year—the şiviş year—the government faced a fiscal crisis and ran the risk of failing to pay its employees (most notably the military). The financial crises easily became political crises, which have come to be known as “şiviş year crises”.

Now, in the US, we had a government shutdown where some federal employees went unpaid for 2 weeks, but could you imagine an entire year? Of course not. Any farsighted government would realize that the problem was coming, and action was often taken to adapt head off any revolt—devaluing the currency, deficit spending, spreading out payments for a few years to cover the gap, but these measures didn’t always avoid economic and political turmoil.

To give one example, the şiviş year 1677 (1088 A.H.) was weathered with significant deficit spending, but by 1687 the government was forced to postpone payments to its soldiers, whereupon the army marched to Edirne and deposed the Sultan Mehmed IV. Looking over some of the other şiviş years, it seems that one good way to avoid the crisis was to conquer a foreign country (Mehmed II greatly relieved his financial worries by taking Constantinople). It’s worth mentioning that Mehmed IV may have avoided his eventual downfall if his troops had been able to capture Vienna.

That’s all for now! You can read more about the şiviş year crises here.

On Euler’s Phi Function

In which we find that Euler’s phi function was neither phi nor a function.

First of all, a shout-out to all of my math(s) friends who are at (or traveling to) the Joint Mathematics Meetings in Baltimore! Now on to some math.

In my research for the “Evolution of…” series of posts, I came across the word totient in Steven Schwartzman’s The Words of Mathematics, which got me thinking about how Euler’s φ (phi) function—also called the “totient function”—came about. The word itself isn’t that mysterious: totient comes from the Latin word tot, meaning “so many.” In a way, it’s the answer to the question Quot? (“how many”?). Schwartzman notes that the Quo/To pairing is similar to the Wh/Th paring in English (Where? There. What? This. When? Then.). So much for the etymology.

It seems to me, though, that the more interesting questions are: who first defined it? how did the notation change over time? I did some digging, and here’s what I’ve discovered.

The first stop on my investigative tour was Leonard Dickson’s History of the Theory of Numbers (1952). At the beginning of Chapter V, titled “Euler’s Function, Generalizations; Farey Series”, Dickson has two things to say about Leonhard Euler:

“L. Euler… investigated the number φ(n) of positive integers which are relatively prime to n, without then using a functional notation for φ(n).”

“Euler later used πN to denote φ(N)…”

Each of these quotations contains a footnote, the first one to Euler’s paper “Demonstration of a new method in the theory of arithmetic” (written in 1758)  and the second to “Speculations about certain outstanding properties of numbers” (written in 1775). In the first paper, Euler is more interested in proving Fermat’s little theorem, which, true to form, he had already proven twice before. However, Euler does define the phi function (on p. 76, though as Dickson says, he doesn’t use function notation), and proves some basic facts about it, including the facts that φ(pm) = pm-1(p-1) [Theorem 3] and φ(AB) = φ(A)φ(B) when and B are relatively prime [Theorem 5]. This paper is in Latin, and while we do see the use of the words totidem and tot, they don’t seem to hold any special mathematical significance.

In the second paper, Euler returns to the phi function, having decided by this time to use π to represent it. Hard-core nerd that he is, Euler provides us with a table of values of πD for D up to 100, and replicates many of the facts he proved in the first paper. It’s interesting to note that, while Euler wrote this second paper in 1775, it wasn’t published until 1784, a year after his death.

It wasn’t until 1801, in Disquisiones Arithmeticae, that Carl Gauss introduced φN to indicate the value of the totient of N. So why did he pick φ rather than Euler’s π? Well, I checked the English translation by Arthur Clarke (no not, that Arthur Clarke), and I think it’s quite likely that he chose it for no discernible reason. In Clarke’s translation, Gauss introduces φ on page 20—and Gauss loved using Greek letters. In pages 5-19 (the beginning of Section II), he uses α, β, γ, κ, λ, μ, π, δ, ε, ξ, ν, ζ — and only after these does he use φ. As to the use of π, which was Euler’s notation, it’s possible that Gauss knew of Euler’s latter work and chose φ because he had already used π, but there’s no way to know for sure. (Also, π was already used for 3.14159… by this point, but if that was his reasoning, it’s odd that he used the symbol π at all.) Most likely, he just picked another Greek letter off the top of his head. It is important to remember that at no point did Gauss use function notation for the totient—it always appears as φN, never φ(N). (Also: Gauss goes on to use Γ and τ before getting tired of Greek and moving on to the fraktur letters 𝔄, 𝔅, and 𝖅.)

The next significant change came nearly a century later in J. J. Sylvester‘s article “On Certain Ternary Cubic-Form Equations,” published in the American Journal of Mathematics in 1879. On page 361, Sylvester examines the specific case npi, and says

pi-1(p-1) is what is commonly designated as the φ function of pi, the number of numbers less than pi and prime to it (the so-called φ function of any number I shall here and hereafter designate as its τ function and call its Totient).

While Sylvester’s usage of the word totient has become commonplace, mathematicians continue to use φ instead of τ. It just goes to show that a symbol can become entrenched in the mathematical community, even if a notational change would make more sense. Also of note is the fact that while Sylvester refers to the totient as a function, he doesn’t use the modern parenthesis notation, as in τ(n), but continues in Euler and Gauss’s footsteps by using τn.

And this is where our story ends. Sylvester’s use of the word totient, Gauss’s use of the letter φ, and Euler’s original definition all contributed to the modern construct that we call the phi/totient function. Even though Euler’s original definition came in a Latin paper, it wasn’t until Sylvester that the use of totient became commonplace.

However, Euler had proven many of the basic facts about it as early as 1758. So, while the original phi function was neither phi nor a function, it was undoubtedly Euler’s.

The Evolution of Weights and Measures

At long last, I’ve exhausted my curiosity in mathematical etymologies. Many word histories have been explored in the previous three installments:

This time around, I want to look at some of the words we use for measurements. There are a few interesting histories in the metric system (SI), but most of the fun comes from the English Imperial system.

The Roman Empire provided us with the primary pre-SI system of measurement in Europe, from which many of the medieval systems were derived. The Latin word mille gives us two important words today: million (related to “thousand”, as detailed in a previous post), and mile. As Roman legions marched across the Mediterranean world, they measured their distances according to paces, with a thousand paces being milia passuum. A pace is the distance traveled in two full steps, and is about 58-62 inches (depending, obviously, on an individual’s height). Using this reckoning, the Roman definition of a mile clocks in at 4,833-5,167 feet.

When the Roman Empire fractured in the West, their uniform measurement system fractured as well, occasionally with hilarious consequences. Later, by the 18th century, the Roman mile had evolved from one definition to many: there were Scots miles, English miles, German miles, and so on. The German mile was 24,000-some feet (at least according to Wikipedia), compared to the English mile’s comparably-paltry 5,280 feet. (Go check that Wikipedia reference, too—there are many more variants!)

But before I get too distracted by the history of the mile, let’s move on to some other length measurements.

  • Inch — this is a fun one. The word comes from the Latin uncia, which basically means “unit”. The strange thing is that an uncia was a unit of weight rather than length—it was 1/12th of a Roman pound. While the English inch is still 1/12th of its parent measure, the ounce somehow became 1/16th of a pound.
  • Furlong — rather simply, it’s a combination of furrow and long, with a furrow being the length of a ten-acre farm field. This makes it about 1/8th of a mile.
  • Yard and Rod — these two have an intertwined history. Today, a yard is 3 feet long, and a rod is 16.5 feet long. The word yard comes from Old English gierd, meaning “rod” or “stick.” Rod comes from the Old Norse rudda, meaning “club”. According to Schwartzman, the rod and the yard were used somewhat interchangeably during the Medieval period, and only later did they settle on 3 and 16.5 feet (or thereabouts)—the “short” and the “long” yard.   
  • Fathom — originating from the Old English fæðm (“faythm”), meaning “arms” or “grasp”. It was the length of a person’s outstretched arms, and is defined as 6 feet today. Perhaps, given its nautical use, a fathom was the distance you could fall off the boat while still being rescued by someone on board?

While there are lots of other words I could choose from, here are two in particular that have a surprising connection.

  • Pound — comes from the Latin pondus, meaning “a weight.” The abbreviation lb. comes from the Latin word libra, meaning “pound” or “balance.” In most markets, merchants would assess the value of precious metals offered for payment using a balance scale (still with us in the popular imagination today). Indeed, one of the signs of the Zodiac is a balance scale. Of course, you’d need to balance the payment against a set of known weights. Over time, then, the word for the weights themselves came to be the English pound, while the word for the scale itself (libra) evolved into its abbreviation.
  • Liter — comes from the Greek litra, which was a unit of weight. Yes, libra and litra have a common origin! Schwartzman notes that lytre and pound were used interchangeably in England as late as the 17th century. When France adopted a decimal system (the precursor to modern SI units), they borrowed the word litron, changing it from a unit of weight to a unit of volume.

There are many, many more words that I didn’t have the time or energy to write up! But hopefully it’s kept your interest throughout the whole series of posts. Get a copy of Schwartzman’s The Words of Mathematics if you want to learn more. 

What weighs more: a pound of gold or a pound of feathers?

Hi everyone! I had intended to write up a full etymology post this month, but time got away from me during the holidays. So for now, I offer an amusing fact taken from Jeff Suzuki’s book, Mathematics in Historical Context

You may know the old joke “What weighs more: a pound of gold, or a pound of feathers?” The answer, of course, is that a pound is the same regardless of what’s being weighed. However, this was not the case in the Medieval world! While the Romans imposed some uniformity of measurement on most of Europe, by Medieval times individual communities had developed their own variations. This bring us to Suzuki:

The complexity of the system of weights and measures is most obvious in what seems to be a nonsensical question: which weighs more, a pound of gold or a pound of feathers? Gold and other precious commodities were measured in Troy units, named after the semiannual trade fairs at Troyes in Champagne, France, where goods from throughout Europe could be exchanged. The Troy pound is divided into twelve troy ounces, and each ounce into twenty pennyweights, and each pennyweight into 24 grains: thus, a Troy pound is equal to 12 x 20 x 24 = 5760 grains. An avoirdupois pound (from the French “having weight”) was defined as having a weight of 7000 grains: thus a pound of gold (5760 grains) weighed less than a pound of feathers (7000 grains). Even more confusingly, the avoirdupois pound was divided into 16 inappropriately named ounces, so an ounce of gold (20 x 24 = 480 grains) was heavier than an ounce of feathers (7000 ÷ 16 = 437.5).

That’s it for now! I will return in the new year with one last post, on the origins of our words for weights and measures.

Calendars, Cycles, and Cool Coincidences (Part II)

This is my second post on the alignment of Thanksgiving and Hanukkah. Go back and read the first post, if you haven’t done so.

When compared to the Julian or Gregorian calendar, the Hebrew calendar is a different animal entirely. First of all, it is not a solar calendar, but is rather a lunisolar calendar. This means that while the years are kept in alignment with the solar year, the months are reckoned according to the motion of the moon. In ancient days, the start of the month was tied to the sighting of the new moon. Eventually, the Jewish people (and more specifically, the rabbis) realized that it would be better for the calendar to rely more on mathematical principles. Credit typically goes to Hillel II, who lived in the 300s CE. In the description that follows, I will be using Dershowitz and Reingold’s Calendrical Calculations as my primary source, with assistance from Tracy Rich’s Jew FAQ page.

The typical Jewish year contains 12 months of 29 or 30 days each, and is often 354 days long. (See how I worded that? It matters.) Clearly, this is significantly shorter than the solar year, so some adjustments are necessary. Specifically, there is a leap year for 7 of every 19 years. But instead of adding a leap day, the Hebrew calendar goes right ahead and adds an entire month (Adar II), which adds 30 days to the length of the year. Mathematically, you can figure out if year y is a leap year by calculating (7y+1) mod 19—if the answer is < 7, then y is a leap year. In the current year, 5774, the calculation is 7*5774+1 = 40419 = 6 (mod 19), so it’s a leap year. With just this fact, the average length of the year appears to be 365.053—about 4 1/2 hours fast. At a minimum, the leap months explain how Jewish holidays move through the Gregorian calendar: since the typical year is 354 days, a holiday will move earlier and earlier each year, until a leap month occurs, at which point it will snap back to a later date. (Next year, Hanukkah will be on 17 December.)

But it’s not as simple as all that. Owing to the lunar origins of the Hebrew calendar, the beginning of the new year is determined by the occurrence of the new moon (called the molad) in the month of Tishrei (the Jewish New Year, Rosh Hashanah, is on 1 Tishrei). Owing to the calendar reforms of Hillel II, this has become a purely mathematical process. Basically, you take a previously calculated molad and use the average length of the moon’s cycle to calculate the molad for any future month. Adding a wrinkle to this calculation is the fact that the ancient Jews used a timekeeping system in which the day had 24 hours and each hour was divided into 1080 “parts”. (So, one part = 3 1/3 seconds.) In this system, the average length of a lunar cycle is estimated as 29d 12h 793p. While this estimate is many centuries old, it is incredibly accurate—the average synodic period of the moon is 29d 12h 792.86688p, a difference of less than half a second.

Once the molad of Tishrei has been calculated, there are 4 postponement rules, called the dechiyot, which add another layer to the calculation:

  1. If the molad occurs late in the day (12pm or 6pm depending on your source) Rosh Hashanah is postponed by a day.
  2. Rosh Hashanah cannot occur on a Sunday, Wednesday, or Friday. If so, it gets postponed by a day.
  3. The year is only allowed to be 353-355 days long (or 383-385 days in a leap year). The calculations for year y can have the effect of making year y+1 too long, in which case Rosh Hashanah in year y will get postponed to avoid this problem.
  4. If year y-1 is a leap year, and Rosh Hashanah for year y is on a Monday, the year y-1 may be too short. Rosh Hashanah for year y needs to get postponed a day.

As someone who’s relatively new to the Hebrew calendar, all of this was very confusing to me. For one thing, it’s not clear that rules 3 and 4 will really keep the length of the year in the correct range. For another, it’s not clear what you’d do with the “extra” days that are inserted or removed. Here’s how I think of it: the years in the Hebrew calendar don’t live in arithmetical isolation, but are designed to be elastic. You can stretch or shrink adjacent years by a day or two so that the start of each year begins on an allowable day. When a year needs to be stretched, a leap day is included at the end of the month of Cheshvan. When a year needs to be shrunk, an “un-leap” day is removed from the end of Kislev.

Now here’s the question my mathematician’s soul wants to answer: How long is the period for the Hebrew calendar? This might seem an impossible question in light of all the postponement rules, but it turns out that each block of 19 years will have exactly the same length: 6939d 16h 595p, or 991 weeks with a remainder of 69,715 parts. As with the Julian calendar, the days of the week don’t match from block to block, so we need to use the length of a week (181,440 parts) and find the least common multiple. Using parts as the basic unit of measurement, we have:

lcm(69715, 181440) = 2,529,817,920 parts ≈ 689,472 years.

Wow! We can also calculate the “combined period” of the Hebrew and Gregorian calendars, to see how frequently they will align exactly. Writing the average year lengths as fractions, the calculation is:

lcm(689472*(365+24311/98496), 400*(365+97/400)) = 5,255,890,855,047 days = 14,390,140,400 Gregorian years = 14,389, 970,112 Hebrew years.

For comparison, the age of the universe is about 13,730,000,000 years. So while particular dates can align more frequently (for instance, Thanksgivukkah last occurred in 1888), the calendars as a whole won’t ever realign again. However, I suppose that claim depends on your view of the expansion of the universe!