CLOSE
Original image

World War I Centennial: Bulgaria, Serbia, Greece Declare War

Original image

The First World War was an unprecedented catastrophe that killed millions and set the continent of Europe on the path to further calamity two decades later. But it didn’t come out of nowhere.

With the centennial of the outbreak of hostilities coming up in 2014, Erik Sass will be looking back at the lead-up to the war, when seemingly minor moments of friction accumulated until the situation was ready to explode. He'll be covering those events 100 years after they occurred. This is the 40th installment in the series. (See all entries here.)

World War I Centennial: Bulgaria, Serbia, Greece Declare War


Turkish cavalry detailed to defend Constantinople.

Ten days after Montenegro declared war on the Ottoman Empire, the rest of the Balkan League piled on, with simultaneous declarations of war by Bulgaria, Serbia, and Greece, which ultimately sent some 750,000 troops across the borders to seize Turkish territory in Europe.

The war on land was divided into three main theatres. To the northwest, the Serbs and Montenegrins both invaded the Sanjak of Novi Bazar, the narrow strip of Turkish territory separating their two kingdoms, while a separate Montenegrin force marched south towards the important city of Scutari near the Adriatic Sea, in what is now Albania. In the central theatre, Serbian, Greek, and Bulgarian troops converged on Macedonia, the main object of the war. Further east, Bulgarian troops headed south into the Ottoman territory of Thrace, hoping to capture the ancient city of Adrianople (Edirne) and maybe even Constantinople itself. Meanwhile at sea, the Greek navy closed in on Turkish-controlled islands in the Aegean Sea and attempted to blockade the Ottoman Empire’s European and Asiatic coastlines.

While the Turkish armies only numbered around 335,000, or less than half the forces of the Balkan League arrayed against them, contemporary observers thought the Turks’ chances were pretty good, as they enjoyed several advantages: Geographically, they held a central position and could choose their battlefields, and the Ottoman administration had also instituted military reforms intended to bring the Turkish armies up to European standards.

But in the end these advantages were either squandered or canceled out by other factors. The Turks had only embarked on their far-sighted reforms in 1911, meaning they were nowhere near complete—in fact, the Turkish armies may have been more disorganized as a result. They also failed to take advantage of their central position by concentrating their forces; instead, they spread their armies out, allowing the forces of the Balkan League to defeat them one at a time. Worst of all, by deciding to boldly take the offensive in Macedonia, the Turkish commander-in-chief, Nazim Pasha, gave up the defensive advantage including choice of battlefields.

To be fair, the Turks faced additional challenges. The Slavic inhabitants of the contested regions tended to be sympathetic to the invaders and hostile to their Turkish rulers, meaning the Turks had to contend with guerrilla warfare by their own subject populations in addition to the forces of the Balkan League. (Of course, the Turks’ earlier atrocities against Slavic Christians were at least partly to blame for the animosity.)

But the first and biggest mistake, as noted, was Nazim Pasha’s decision to immediately bring the fight to the invading armies, which resulted in disaster when ill-prepared and only partially mobilized Turkish forces confronted the Serbs at Kumanovo on October 23 and 24, and the Bulgarians in the simultaneous battle of Kirk Kilisse, October 22-24.

See previous installment, next installment, or all entries.

Original image
iStock // Ekaterina Minaeva
technology
arrow
Man Buys Two Metric Tons of LEGO Bricks; Sorts Them Via Machine Learning
May 21, 2017
Original image
iStock // Ekaterina Minaeva

Jacques Mattheij made a small, but awesome, mistake. He went on eBay one evening and bid on a bunch of bulk LEGO brick auctions, then went to sleep. Upon waking, he discovered that he was the high bidder on many, and was now the proud owner of two tons of LEGO bricks. (This is about 4400 pounds.) He wrote, "[L]esson 1: if you win almost all bids you are bidding too high."

Mattheij had noticed that bulk, unsorted bricks sell for something like €10/kilogram, whereas sets are roughly €40/kg and rare parts go for up to €100/kg. Much of the value of the bricks is in their sorting. If he could reduce the entropy of these bins of unsorted bricks, he could make a tidy profit. While many people do this work by hand, the problem is enormous—just the kind of challenge for a computer. Mattheij writes:

There are 38000+ shapes and there are 100+ possible shades of color (you can roughly tell how old someone is by asking them what lego colors they remember from their youth).

In the following months, Mattheij built a proof-of-concept sorting system using, of course, LEGO. He broke the problem down into a series of sub-problems (including "feeding LEGO reliably from a hopper is surprisingly hard," one of those facts of nature that will stymie even the best system design). After tinkering with the prototype at length, he expanded the system to a surprisingly complex system of conveyer belts (powered by a home treadmill), various pieces of cabinetry, and "copious quantities of crazy glue."

Here's a video showing the current system running at low speed:

The key part of the system was running the bricks past a camera paired with a computer running a neural net-based image classifier. That allows the computer (when sufficiently trained on brick images) to recognize bricks and thus categorize them by color, shape, or other parameters. Remember that as bricks pass by, they can be in any orientation, can be dirty, can even be stuck to other pieces. So having a flexible software system is key to recognizing—in a fraction of a second—what a given brick is, in order to sort it out. When a match is found, a jet of compressed air pops the piece off the conveyer belt and into a waiting bin.

After much experimentation, Mattheij rewrote the software (several times in fact) to accomplish a variety of basic tasks. At its core, the system takes images from a webcam and feeds them to a neural network to do the classification. Of course, the neural net needs to be "trained" by showing it lots of images, and telling it what those images represent. Mattheij's breakthrough was allowing the machine to effectively train itself, with guidance: Running pieces through allows the system to take its own photos, make a guess, and build on that guess. As long as Mattheij corrects the incorrect guesses, he ends up with a decent (and self-reinforcing) corpus of training data. As the machine continues running, it can rack up more training, allowing it to recognize a broad variety of pieces on the fly.

Here's another video, focusing on how the pieces move on conveyer belts (running at slow speed so puny humans can follow). You can also see the air jets in action:

In an email interview, Mattheij told Mental Floss that the system currently sorts LEGO bricks into more than 50 categories. It can also be run in a color-sorting mode to bin the parts across 12 color groups. (Thus at present you'd likely do a two-pass sort on the bricks: once for shape, then a separate pass for color.) He continues to refine the system, with a focus on making its recognition abilities faster. At some point down the line, he plans to make the software portion open source. You're on your own as far as building conveyer belts, bins, and so forth.

Check out Mattheij's writeup in two parts for more information. It starts with an overview of the story, followed up with a deep dive on the software. He's also tweeting about the project (among other things). And if you look around a bit, you'll find bulk LEGO brick auctions online—it's definitely a thing!

Original image
Nick Briggs/Comic Relief
entertainment
arrow
What Happened to Jamie and Aurelia From Love Actually?
May 26, 2017
Original image
Nick Briggs/Comic Relief

Fans of the romantic-comedy Love Actually recently got a bonus reunion in the form of Red Nose Day Actually, a short charity special that gave audiences a peek at where their favorite characters ended up almost 15 years later.

One of the most improbable pairings from the original film was between Jamie (Colin Firth) and Aurelia (Lúcia Moniz), who fell in love despite almost no shared vocabulary. Jamie is English, and Aurelia is Portuguese, and they know just enough of each other’s native tongues for Jamie to propose and Aurelia to accept.

A decade and a half on, they have both improved their knowledge of each other’s languages—if not perfectly, in Jamie’s case. But apparently, their love is much stronger than his grasp on Portuguese grammar, because they’ve got three bilingual kids and another on the way. (And still enjoy having important romantic moments in the car.)

In 2015, Love Actually script editor Emma Freud revealed via Twitter what happened between Karen and Harry (Emma Thompson and Alan Rickman, who passed away last year). Most of the other couples get happy endings in the short—even if Hugh Grant's character hasn't gotten any better at dancing.

[h/t TV Guide]

SECTIONS
BIG QUESTIONS
BIG QUESTIONS
WEATHER WATCH
BE THE CHANGE
JOB SECRETS
QUIZZES
WORLD WAR 1
SMART SHOPPING
STONES, BONES, & WRECKS
#TBT
THE PRESIDENTS
WORDS
RETROBITUARIES