Well the 2017 season ended yesterday afternoon for my Boston Red Sox as we lost 5–4 to the Houston Astros and they took Game 4 of the ALDS. So this morning we will surely see the critiques and hot takes on what to do to improve the team begin to make the internet rounds.
But before we get into all of that, I wanted to take a look at the 2017 season from a data perspective. At least, the regular season. After all, we can see how Sale in Game 1 and Kimbrel in Game 4 just had poorly timed bad days. But what about the other 162 games? After all, we will need to win a lot of them if we want to make it back to the playoffs in 2018.
I just pulled a couple quick stats from Baseball Reference. Now we can quibble about which stats are best another time, but from my experience the more sabremetric datapoints are lost on a general audience. So here we are using OPS, basically a hitter’s average combined with his power/slugging ability, and ERA, the amount of runs a pitcher can be expected to allow every nine innings. I also threw in defensive runs saved above average, i.e. is the player saving more runs than an average player.
You can read the graphic for the details, but the takeaway is that Boston, we need not panic. The 2017 Red Sox were a good team. Far from perfect—here is looking at you lack of middle-of-the-order power—but a solid lineup, good rotation, good defence, and a fantastic bullpen. How can we add without subtracting too much?
Well news definitely happened whilst your author was on holiday. So today we look at an informative piece from the New York Times that compares the weapons fire from the Las Vegas shooting to that of Orlando and a fully automatic weapon.
This piece makes good use of both audio and motion graphics to show how the bump stock makes a semi-automatic rifle more like what we might call a machine gun. It also includes some nice illustrations that demonstrate how the stock does what it does.
From an audio standpoint, I do want to point out that the designers made a wise decision in opting not to use authentic sounds. Instead they chose an abstracted sound, allowing the user to focus on the rapidity and steadiness of the sound.
Credit for the piece goes to Larry Buchanan, Evan Grothjan, Jon Huang, Yuliya Parshina-Kottas, Adam Pearce, Karen Yourish, C.J. Chivers, and Thomas Gibbons-Neff.
Last month, two massive earthquakes devastated Mexico. Now, if you were like me, you were captivated by the photos and videos of the quakes striking and tearing down buildings and infrastructure. But, think about it for a second, how did people know to take out their mobiles and record the tremors for posterity’s sake?
Well, the first thing you should know is that earthquakes consist of a number of different waves of energy. Some move quicker and are less damaging than the slower travelling ones. And it turns out that scientists have been able to use that speed differential to build early warning systems along and around fault lines.
The Washington Post did a really nice job of explaining how earthquake-prone California is developing just such a system to deal with its tremors. I won’t spoil all the details, you should go read the article if earthquakes are of any interest to you.
Today’s post is a sad post, hence why I did not run with it on Friday. But on Friday, we bid adieu to the little space probe that could, Cassini. This piece is not terribly heavy on the information design, but it does include one diagram—so it counts.
The BBC put together a piece reflecting on the Cassini mission, including its little lander Huygens. If you, like your author, are interested in space-y things, this article is worth the read.
Over the last several weeks we dealt with the impact of a few hurricanes from H to K, i.e. Harvey, Irma, Jose, and Katia. Now that the Atlantic basin has quieted a wee bit, it is time we get back to the lighter side of things.
So we turn to xkcd and its look at ensemble models, often used to try and predict the paths of hurricanes.
Like many Americans I followed the story of Hurricane Irma over the weekend. One of my favourite pieces of reporting was this article from the Washington Post. It did a really nice job of visually comparing Irma to some recent and more historic storms, such as 1992’s Hurricane Andrew.
It can be difficult to truly compare hurricanes, sometimes they are small and compact, other times more dispersed. Irma was just big with lots of potentially destructive power spread out across a wide area, almost the width of the Floridian peninsula. The article uses several graphics—I am also quite partial to the satellite image comparison so check out the article—but this one is perhaps my favourite.
It uses a colour palette that deepens in redness nearer the storm’s centre. This allows the user to compare the geographic area or footprint of the storms destructive winds.
I wonder, however, what would happen if the designers had superimposed each graphic atop the other. It might have allowed for an even better comparison of size instead of having to have the user mentally transpose each hurricane.
Still, a really nice graphic and visual article.
Credit for the piece goes to Bonnie Berkowitz, Laris Karklis, Reuben Fischer-Baum, and Chiqui Esteban.
About a year ago Pro Publica and the Texas Tribune published a piece that documented the calamity of a hurricane striking and flooding the city of Houston. It proved rather prescient a week or so ago.
So a little over a month ago the Washington Post published an article about the catastrophe that could await Tampa Bay if a major hurricane were to strike the area. I read it, enjoyed it, and found it informative, but opted not to share it with all of you.
Well now we have Hurricane Irma barrelling towards Florida after it struck the Leeward Islands this morning. So today felt like a decent day to share the story.
Credit for the piece goes to Darryl Fears, Zoeann Murphy, Kolin Pope, Denise Lu, and Danielle Rindler.
As my last two posts pointed out, yesterday was the Solar Eclipse. It certainly garnered media attention as a news helicopter hovered over my building during the height of the eclipse. Very peaceful indeed. But, knowing that my smartphone would not be able to take the best photos of the eclipse, even with a solar filter, I decided to do what any good designer might do. I sketched out the eclipse.
The task of sketching an eclipse is not easy. You cannot, or at least should not, look directly at the sun. (You’ll burn your eyes out, kid.) But the solar filters make seeing anything but the most intense light sources near impossible and so you have to remove them in order to doodle in a sketchbook. Eventually I found a solution and was able to quickly move from filtered glimpses of the Sun to the sketchbook. (At least when the clouds would permit.)
Last night I digitised those sketches into this simple graphic. The sketches are not entirely accurate as the position of the Moon jumps in a few spots. But it does give you the impression of peak eclipse about 14.45 with just a sliver, or 25% of the Sun remaining visible. And indeed the neighbourhood was visibly darker.