The Quantitative Peace

The Military and Competitive Sports

I missed my last post, but thankfully I'm on top of this week's edition. 

Kyleanne Hunter and Oliver Kaplan have a piece at Political Violence @ a Glance discussing some of the military roots of the biathlon. I've never known much about the sport's history, but it certainly makes sense that its origins are so closely tied to the kinds of security needs that Hunter and Kaplan cite. This was particularly interesting to me as both my wife and I grew up close to Lake Placid, New York. Lake Placid hosted the winter Olympics twice—once in 1932 and again in 1980—and continues to be a destination for tourists and athletes alike. Additionally, the 10th Mountain Division is headquartered about three hours from there at Fort Drum, and they have an armory located in Saranac Lake, New York where I grew up. Two members of the US biathlon team are also from Saranac Lake: Annelies Cook and Tim Burke. 

I went to high school with both Annelies and Tim, and it's great to see them doing so well. Hunter and Kaplan's discussion of the biathlon's history also makes me appreciate the sport and where I grew up a little bit more, and it's neat to think about the sport in terms of how it intersects with my own personal historical/research interests. The idea that specific military assignments can evolve into cooperative/competitive sporting events is really interesting, and I'm sure there's been much more written about it than I'm aware of (which is little). Naturally this makes me wonder what other sports have evolved out of military activities. Archery comes to mind, but I suspect that has competitive origins that are less exclusively military. There are a number of other shooting-related events during the summer games (see here), but again, many of these events are not necessarily exclusively military in origin either. Some of the historical information the link provides, and the descriptions of some of the events, suggest more of a hunting-related background. And many of these events appear to have been phased out, or have only been held once or twice.

It also makes me wonder as to what kind of selection effects might be at work in terms of how these activities evolve into competitive sports. Presumably you need activities that are a mixture of some highly specialized skill, but also something that's not overly secretive. After all, you don't want other states knowing that you have individuals highly trained in a particular task if that will compromise their work in some way. You also need an activity where multiple countries have need of the same type of training or force. As Hunter and Kaplan discuss, multiple countries were deploying similar sorts of forces to patrol remote, mountainous border regions, thereby facilitating the development of some sort of competitive event based on these shared activities. So not every state needs to have a given force, but at least a few do in order for it to be competitive. 

So what are some contemporary examples of the sorts of military activities that could evolve into internationally competitive sports? And how has technological innovation changed the landscape, so to speak, in terms of the pool of potential activities that could evolve in this way? My mind immediately went to some underwater sports, thinking of some combination of navigating an underwater obstacle course, and then performing some task requiring a demonstration of dexterity. This list of underwater sports suggests there are some sports that at least partly resemble these activities. Underwater navigation and underwater target shooting, specifically. This article also indicates that no underwater sports have been a part of the Olympic games. This appears to be due to the International Olympic Committee selecting which games it will grant approval to. Still, these seem like activities that require a high degree of specialization, but are also pursued by enough countries to facilitate competition. 

Another future possibility would be sort sort of aerial drone competition. Competitors might be judged on their ability to take off, perform certain maneuvers, perhaps "paint" a moving target for a given period of time, and then land. Though there are more advanced military variants, less sophisticated and less expensive drone variants are already being experimented with for a variety of purposes (see Amazon's recent talk of drone-based delivery). Though this would certainly emphasize physical performance less than other athletic activities, I'm not sure it's all that different from other activities like shooting, much of which emphasizes hand-eye coordination. This is also technology that more countries are likely to pursue for security/military purposes as time goes on.

If anyone can think of other military activities that might translate into internationally competitive sports, please share in the comments. 

The Dark Knight Rises and the Economic Impact of Bane's Occupation of Gotham

I started working on this post a long time ago and, for whatever reason, never got around to finishing it. So please keep in mind that this was largely written shortly after the film first came out. I should also disclose at the outset that this post will contain spoilers, so if there is some sort of unbelievably powerful force that has kept you from seeing this fantastic movie, please be warned. For those still interested, there's more after the jump.

How Do You Review?

I’ve been sending articles out for review for a few years now, and I’ve also had the opportunity to review several papers for journals. Having been through each side of the ordeal, I’ve begun to form some opinions on the peer review process as a whole. This is something other political scientists have written extensively about. For example, Michael Allen recently addressed the issue on this blog, and Nathan Jensen recently wrote an interesting piece about one of his paper’s journeys through the political science peer review process.  However, some of my recent experiences have prompted me to think about the process from the vantage point of the reviewer. Most of what I can recall reading on the subject tends to focus on the process as a whole, or discusses the process from the point of view of the submitter, rather than the reviewer. So I thought I’d reflect on my experiences and what practices I’ve tried to incorporate into my reviews.

1. Take reviews seriously: This might seem like an obvious point, and it's one Jensen makes in his post, but for anyone who has been through the process you know you can’t always take this for granted. We’ve all gotten terrible reviews in some way shape or form—some of them are condescending in their tone, some of them seem to address topics or ideas that are completely irrelevant to the paper in question (even after much reflection), some of them are incredibly short, and some of them are just wrong. And these points just concern content. Some reviewers just don’t respond to review requests from journals, and others don’t seem to get around to the review until several months after the paper was submitted.

For the most part, all of these things are well within the power of the reviewer to control. I say “for the most part” because sometimes comments or suggestions made in a review may be wrong, but I’d like to believe reviewers are not dishing out incorrect information on purpose. And maybe sometimes people just aren’t communicating their thoughts well, thereby leaving the reader with no idea as to how those thoughts apply to their paper. Also, sometimes life does get in the way, causing unexpected delays. But, quite often, you as a reviewer can control these sorts of factors.

The review process can and does put a burden on journal editors and reviewers—there’s no question about that. As Jensen notes in his post, senior scholars in particular can be swamped with review requests. But reviewing is probably one area in which scholars can have the greatest impact on the professional fortunes of other scholars. And I don’t mean to imply that reviewers should fail to reject a paper just to provide a boost to someone else’s career. Not every paper deserves to be accepted or given a revise and resubmit, but editors rely to varying degrees on the advice given to them by reviewers. We also know that there are plenty of hard working people out there who face rejection after rejection, many of which are for really silly reasons. If you’re going to reject a paper, the author deserves to know why. A flippant one-line response is not helpful to anyone.

I typically try to get my reviews back within a month or two, if possible. I'm still pretty early on in my career, at a point where not many people know much of my work, so it's probably pretty easy for me to meet this goal as compared to more senior scholars. On the one occasion that I've known in advance that I wasn't able to get reviews back in a timely manner, I’ve communicated this to the editor. It’s easy to blow this responsibility off—I mean, this isn’t your work, right? You are taking time away from your own busy schedule to review someone else’s work. Still, more likely than not you are asking others to do the same for you. 

2. Be clear and detailed: Along the lines of the previous point, a lack of detail in a review doesn’t help anyone. I once received reviews on a paper that ran the gamut from a single sentence saying to publish the article as is, to a rather lengthy, and in no uncertain terms, reject. As nice as it was to see that someone enjoyed your paper so much that they suggested accepting it, I’m not sure that such a brief reply helps. Truthfully, some of the more lengthy and critical reviews provided me with ideas for changes that I really do believe made the paper a better one.  

More often than not, papers are going to be rejected, and reviewers should know this. Even if you like a paper so much that you want to see it accepted as is, or with minor revisions, there will usually be at least one other reviewer on a given paper, and it is quite possible that this other reviewer will have a very different take. No paper is perfect, so it can be helpful to know why a reviewer believes that the strengths of a paper outweigh any weaknesses. Especially when other reviewers are less supportive. It’s also helpful to be able to compare reviews to see if there are any common themes/complaints that are popping up across readers. Given the high rate of rejection, I think it’s important to remember that it’s not really just about the one or two reviews that the author receives on a given round of submission. Setting aside for a moment the fact that one person can get the same paper to review over the course of that paper’s journey through the review process, if reviewers are clearly raising the same concerns through multiple rounds of reviews that might be a pretty good signal that something needs to be changed. Sometimes these sorts of things are easy to spot from one set of reviews, and at other times they’re not, but the authors can’t tell if the reviewer doesn’t provide the detail. Given the high probability of rejection, if you, as a reviewer, think that a paper's strengths outweigh its weaknesses, a failure to highlight those very features could result in them being erased in future rounds of reviews.

I’ve gotten to the point where I offer a brief statement at the beginning of the review in which I explicitly state whether or not I’m recommending acceptance, rejection, etc. I also try to offer a brief summation of what factors I’m considering in making this recommendation. I also try as hard as possible to not waver in my judgment—if you have “mixed feelings” or you “could be convinced” that a paper could be worthy of publication, don’t try to pass the buck to the editor and the other reviewers. Just recommend an R&R and move on. Nothing says you have to accept the second or third round of revisions, but given how competitive the review process is, this kind of waffling is effectively the same thing as rejecting the paper outright, and it's probably not all that helpful to the author.

Beyond the introduction, I also try to clearly identify each individual point that I want to address. And yes, this often involves an enumerated list and/or bullet points. To some extent I think this is just a matter of style. However, it can be difficult in a meandering review to discern the exact points that the reviewer wants you to address, and as much as it is the author’s responsibility to take their revisions seriously, it is also the reviewer’s responsibility to make clear those points that need addressing. Furthermore, we hold ourselves to a pretty high standard when it comes to organizing our thoughts and arguments in the context of an academic paper, so why shouldn’t it bethe same in reviews? It is, after all, all part of the same, broader, knowledge-generating process.

3. Offer constructive criticism: Again, this seems like an obvious one, but you can’t take it for granted. We spend an awful lot of time in college and graduate school learning/practicing how to pick apart other people’s arguments. So while pointing out the flaws in someone’s article is certainly an important part of the review process, I also think it’s equally important to be able to point out its strengths.

For the most part, my experience on this point leads me to believe that most reviewers are pretty good about this. However, I have received reviews that are highly critical, with little in the way of constructive commentary. "Complainy" might be the most appropriate made-up adjective to describe these reviews. If you as a reviewer think that there are some deficiencies with an argument or method, you need to spell that out for the author. If such deficiencies were clear to all, then they probably wouldn’t be in the paper to begin with. Further, I think the degree to which any flaw is damning to the overall article is contingent upon the availability of feasible alternatives. If you don’t like a measure that the author uses, don’t just complain and then move on. At the very least, ask the author to clarify whether or not superior measures are actually available. If you are aware of one that you believe is superior, then please share it and explain why you believe it to be better suited to the analysis at hand. Again, this is a collaborative venture, and part of the review process is being able to access the knowledge of other scholars.

I would also say that personally, as a junior scholar, I really do appreciate a good review when I get one. Some people have clearly taken the time to think about my work, and I appreciate it. As I said before, I’ve been fortunate enough to get some great feedback that I have subsequently incorporated into my work, and I do think the work is better for it. Criticism accompanied by constructive feedback and advice generally seems to be more helpful than merely pointing out the faults of a particular project.

4. Be transparent when it comes to your own limitations: As I stated above, sometimes reviewer comments are just wrong. Sometimes this is an honest mistake, and the reviewer is trying to offer sincere advice or criticism, but just gets it wrong. But, as an author this can be incredibly annoying—particularly if some factually incorrect statement could have been a major contributing factor to your paper’s rejection. If I’m reviewing a paper and I’m unclear about a measure, statistic, or method, I typically try to be entirely transparent when it comes to my own ignorance on the matter. Now I'm pretty confident in the substantive and methodological training that I received in graduate school, but this doesn’t mean I’ve mastered every analytical approach or estimation technique. Nor does it mean that I can’t learn even more about those topics and methods that I have been exposed to. Indeed, I’ve learned a lot over the past seven years, but as this SMBC comic so nicely conveys, sometimes expanding your knowledge base can raise new questions. So, when you think you don’t know, or you know you don’t know, just say, “I don’t know.” Feel free to even pose a question on the issue to the author in your review. After all, there is a certain irony in the idea that certain people, having devoted themselves to an industry that (ostensibly) is based on the discovery and accumulation of knowledge, would be so reluctant to utter those three words.

I'm sure senior scholars may have a different take on some of these issues. As I said, I'm still very early on in my career, so I'm not facing the same kinds of pressures from as many sources as they are. I don't have to deal with dissertation committees or a never ending stream of review requests. Still, I don't mind reviews all that much. They can provide me with some insights into what people in my general area of expertise are working on, and they often lead me to read works that I've not previously noticed or thought much about. But perhaps my views will change given time. 

 

 

 

 

 

Update

Just a quick update. Three months ago I said we would resume posting later in the spring. Naturally, deadlines are made to be pushed back. It's been a pretty big and glorious summer, though, so I hope our reader(s) will excuse us for the prolonged absence. I'm happy to say that I got married in June (at a zoo, no less) and have just turned in the final copy of my dissertation to the Graduate School, and most of us are in, or have recently completed, the process of moving to new jobs. I could do without the packing, but the road trip will be fun. Anyway, we're hoping that by the fall we'll be back in the swing of things. 

Links from the Weekend

• Peer Review of the Internet - "It will enable sentence-level critique of written words combined with a sophisticated yet easy-to-use model of community peer-review. It will work as an overlay on top of any stable content, including news, blogs, scientific articles, books, terms of service, ballot initiatives, legislation and regulations, software code and more-without requiring participation of the underlying site." h/t - orgtheory
  
  
• South Korea launches an online "Unification Channel" to educate younger generations about the dangers of reunification. 


• What 7 billion people look like
  
  
• Graphic Dispatches from a Recent College Grad Still Living in a College Town - Gift prices for the holidays v. education v. the real world.
  
  
• 3QD prize voting is now open - Several of the nominated posts are by political scientists and the winner will receive a $1,000 prize.

Maps Maps Maps, Part Deux

I posted a few days ago about openheatmap.com, a website that will convert your csv files into fancy thermal maps.  One problem with our initial attempts to map out the presence of American military forces abroad was that the data are highly skewed.  Some countries host upwards of 50,000--60,000 American military personnel in the year we're looking at (2005).  In the past this figure was even higher---Germany at one point plays host to roughly 250,000 members of the American military during the Cold War.  

As you can imagine, we don't have that many soldiers in most countries.  The original map I posted was somewhat misleading, as countries such as China and Russia appeared to have more soldiers within their boarders than they actually have, and this was mostly the result of the combination of skewed data and the way that software color-coded countries.  Phil Arena suggested logging the troop values to see if this would help to take care of the issue:

 

I've changed the colors from blues to reds, as I think this helps a bit, but the figures used to generate the map above are the logged values of troops within the country.  The paler countries obviously have fewer soldiers than the darker countries.  Overall I think this map looks better, but there is still a fairly substantial amount of variation that is being masked by the limited range of tones.  For example, Iran is actually coded as having one American soldier present during 2005, which explains why it's a pale tan/organge.  Nevertheless, I think the important information that the map is intended to convey (namely the extent to which the US military has at least some presence virtually everywhere) is still there. 

On a final note, I also found that the map doesn't distinguish between 0 values and positive values---rather, a 0 and a 1 will share the same color.  Any observations that have a 0 value need to be dropped out of the data before the map is created.  This is kind of a funny feature, but something that users should be aware of.   

Sounds About Right

courtesy: www.smbc-comics.com

Maps Maps Maps

Back in December I had a brief post about CRACK, a mapmaking software package for Macs.  The downside was that CRACK only worked for making maps of the United States.  As the need has arisen, Michael Allen and I began looking for something similar that could handle world maps.  This brings me to OpenHeatMap, an online platform for making those fancy looking thermal heat maps using data from a spreadsheet.  We were looking for something to visually display some data that we have on US Military Personnel abroad, and this seems to work pretty well.  Here's an example:

The program lets you mess with some of the details, such as borders, colors, etc.  The only downside is that it does not appear to allow you to save an image.  Mac users have the option of taking screen shots by selecting particular areas on the screen, but I don't think PCs have this feature yet.  Anywho, if you have a Mac, this lack of a downloadable file probably won't matter too much to you.  Also, there are some small troop deployments to some microstates that this map does not display--getting it to recognize some of the country names in the data may also be a bit of a struggle.   

Also, the data used for making this map was obtained from Tim Kane at the Heritage Foundation. 

 

While no one was looking?

http://www.bbc.co.uk/news/world-middle-east-12612133

The Domestic Side of Things

Clearly I'm trying to make up for a post drought from the past couple of months.  I'll leave the more in-depth commentary to someone who has been following this situation more closely, but it looks like the Wisconsin State Government is experiencing a wheeeeee-bit of a principal-agent problem (via Boing Boing).

Wisconsin Police Have Joined Protest Inside State Capitol

I will say that it's not immediately clear to me whether we're talking about off-duty cops only, or if we're talking about both on and off-duty police officers.  If the latter are protesting that would seem to be less of a problem, but the article seems to indicate that on-duty officers are the ones refusing to remove protestors from the capitol.  On the other hand, the man in the video looks more to be an off-duty officer expressing support (if his jacket is any indication).