Posts Tagged ‘runner’

How I fixed it.

Altra Viho shoes. Something stabbed my foot, drew blood. But I couldn’t see or find anything inside, even after taking out the insole. I had to actually run in the shoe, putting a lot of weight on it, to even get to the point where it would poke me.

Much searching on the sole found a little dot that looked like it might be the culprit. Scraping it with a straight pin suggested it was the only hard thing in the vicinity. It offered resistance, gave a little click when I forced the pinpoint across it.

Decided to try it. I used a 1/16″ drill bit, smallest I had, with an electric power drill. Tried to drill right on target, but couldn’t be sure. I thought about using a hot needle instead, but I was afraid the spike would get stuck in the melted rubber and might remain there, undetectable. Also that a hot needle might make an even bigger hole than the drill bit. Which I think was probably true: when I pulled the drill bit out, the rubber around the hole swelled to pretty much fill it. The remaining hole is tiny. I’ll still dab a bit of Shoe Goo on it.

In the fragments the drill bit brought out, I thought I might have seen something, but I couldn’t be sure. Turned the shoe over and looked inside. The drill had poked the thorn up into the inside of the shoe. There it was, about a quarter-inch of it. I reached in with needlenose pliers and pulled it out.

So there you are. Layman’s hardware to the rescue. I would have used hammer and screwdriver too, if I had seen a way. And saved maybe $15-20 in shoe repair.

I am a runner. I am not your coach, doctor, or therapist. You need to see any and all professionals whose advice may be relevant to your situation, and you should believe them rather than me if we disagree.

There are many good sites on how to be a runner. This blog post is not the first or only page you should consult.

My purpose here is simple. I am offering suggestions and opinions arising from my own observations and experience. I hope my remarks aid in understanding and applying the advice of others. Please feel free to disagree with my words, or to add your own, in the Comments section (below).

Contents

Clothing and Luggage
Injuries and Shoes
Hydration and Food
Lights
Weapons and Other Gear
How to Get Started

.

Clothing and Luggage

Do not wear heavy clothes on a hot day, in hopes of losing water weight. That poses a real risk of dehydration plus overheating (e.g., heat stroke). If you want to take the risks associated with losing a lot of water weight, learn to run distances. You can lose several pounds in a single long run. And then it will come right back, as it should, when you end the run and start sucking down the Gatorade, or some other mix of salts and liquid.

Excessive heat triggers cardiological issues for me, so I err on the cool side. From that perspective, my advice is: don’t overdress. Realize that you will warm up within the first half-mile or mile of running – or if you don’t, you really may be underdressed. I wear a mesh sleeveless shirt down to 65°F, a short-sleeved T-shirt down to around 55°F, and a long-sleeved T-shirt down into the thirties, with another optional short-sleeved T-shirt as an underlayer, depending on wind and other factors. At still lower temperatures, a windbreaker and a possible additional layer may help. I’d favor multiple layers that I can add or shed. I don’t know if I’ve ever worn a coat on a run.

Windbreakers: I prefer a zipper rather than a pullover for venting. If I wanted to drag one along just in case, I could consider the packable kind; the self-contained pack on my old Turfer has belt loops. You can get a snug-fitting backpack that works for running, but ideally your windbreaker could squeeze into a no-bounce fanny pack. There are slim fanny packs that hold little more than a phone; an alternative for the phone is a bicep strap. A loaded backpack may change the weight and motion dynamic, provoking joint and leg muscle issues. It may be best to ease into that sort of thing, gradually building up familiarity with rising weight and distance. An option for some is to park one’s stuff in a locker at the gym, and start the run from there.

When temperatures drop into the low thirties, I add tights under my running shorts. (Rather than shorts, I wear swim trunks, because they typically offer a rear pocket.) In the twenties, I replace those with wind pants. A layer of silk or polyester thermal underwear may become advisable below 20°F, depending on wind. A second thermal layer and face mask may be advisable below zero. You can run in a wind at -20°F; you just had probably better keep moving. The adage here is: There is no bad weather. There are just bad clothing choices.

Nylon or silk glove liners can give your hands a bit of protection from cold air, without requiring much space in your pockets. So can a greasy layer of Vaseline – but don’t use it with nylon. A headband is usually enough to ward off earaches, from 50°F down into the thirties at least. Below that, a good fleece hat will keep you warm on anything short of Mars.

If you’re like me, what you lose in skin comfort at colder temperatures, you gain in improved breathing comfort. Goodbye humidity, mold, and random heat-baked pollutants; hello crisp, fresh air. I wouldn’t want to deny the pleasure of a run in a summer thunderstorm. But there is never a sure thing: one time in Wisconsin, the thunderstorm turned into hail. I was lucky it was small hail. It would have been a good time to have a hat.

Injuries and Shoes

To many people, “injury” means the same as “accident.” Not so in running. For a runner, an injury is just something that is injured. So if you’re running down the street and suddenly you pull a calf muscle, that’s an injury.

Probably the best way to get an injury is to overdo it. If you want to be a runner, don’t overdo it. That is the classic beginner’s mistake.

It’s not a question of whether you’re strong or eager. The simple problem is that the start is when your body is least ready. If you injure yourself, you may be out of commission for months. If you feel impatient now, just imagine how impatient you’ll be then.

In the worst case, you can injure yourself permanently. I did that with my right calf. That problem is still with me, 15 years later. It took 10 years to figure out a workaround, a way to prevent it from interrupting runs, often and seemingly at random, to the point where I feared I might never again be able to run regularly.

The general advice, subject to revision for individual cases, is to increase your running distance by 10% per week. Many interpret that in terms of the total: raise a five-mile week to 5.5 miles next week. I interpret it in terms of each individual run: raise your ability to run a mile, this week, to 1.1 miles next week. At five or six miles, maybe just start adding in terms of round miles: your longest run next week can be up to six or seven miles. That seems consistent with many gradual marathon training plans.

Running in a weakened state may increase your risk of injury. It also makes runs less fun. Your body needs rest, not only to build and repair muscles and other tissues, but also to restore your glycogen level.

There are injuries available for everyone. WebMD emphasizes the basic point: stress fractures are “often due to working too hard before your body gets used to a new activity”; shin splints “are common after changing your workout, such as running longer distances or increasing the number of days you run, too quickly”; Achilles tendinitis “is usually caused by repetitive stress … [due to] too much distance.” People who are overweight when they start may want to observe some special precautions.

In short, take it easy and build up gradually. Note, however, that not all injuries require or benefit from time off. You have to get to know your own history. For instance, I sprained my right ankle when I was 15, stepping off a pickup truck’s tailgate while carrying a 75-lb. pack of asphalt roofing shingles. That injury almost never bothers me except when I’m first starting to run, after a period of weeks or months off. The solution in that case is not to stop running and wait for it to feel better. It never will: the pain will return, every time I try to resume running. The solution is to run through it. Within a short time – sometimes within just a minute or two – it goes away.

I have a similar problem with my left knee. Sometimes it aches. The solution there seems to be better (especially faster and lighter) running – not, say, backpacking up hills with a heavy load. Taking a year off, as I did one time, didn’t help it at all. That injury originated in New York City in 1987, when a driver T-boned me at the entrance to the Lincoln Tunnel. At first, I couldn’t walk. It recovered in a few days – but the potential for issues has been there ever since.

It’s been a while, but I know sometimes new runners can get painful sideaches. Among the suggestions offered by various sources, I found that I could often avoid these by running faster – over a shorter distance, if necessary – until I stopped getting them.

They say motion is lotion. If you can find a way to get the joints and muscles moving, and keep them moving without pain, your body will produce natural painkillers that will tend to make it easier to keep moving. Unfortunately, that will only work for some injuries. You may have to figure out, the hard way, whether taking it easy helps, or whether trying to run through it aggravates the problem. Going to a specialist may help, but they can’t always identify the issue, or prescribe anything that may help.

I became somewhat less fond of specialists when an orthopedic intern treated my running like something that couldn’t continue because I was so terribly old. I suppose people in less-than-perfect would be at risk of similar treatment in some places. Discouragement is one thing you don’t need when you’re just starting out. Not to deny that I can be guilty of it too. I saw an obese guy on the trail one time, trying to run. I felt guilty that I didn’t turn around, run beside him, and offer him some advice on starting slowly. Maybe that would have been helpful. But a year or so later, I saw what was, I think, the same guy, and now he was just beefy and strong-looking, still charging ahead with that same determined look on his face.

Cross-training is another way to reduce the risk of injury; indeed, Runner’s World says that injury prevention is the number one benefit of cross-training. The general idea is that you are working the same or related muscles in a different way. According to Marathon Handbook, great cross-training activities for runners include weightlifting, swimming and aqua jogging, biking, yoga and pilates, elliptical, walking, hiking, golf, and team sports. My own favorite form of cross-training is riding my Razor push scooter up and down the hills at 3 AM, when I have the streets to myself. If you have a cross-training activity that you really enjoy, you may find it relatively easy to make it your primary form of activity (rather than skipping exercise altogether) when injuries prevent you from running. An example: people who have knee replacement surgery often transition to biking as their primary form of exercise. Biking evidently places less stress on the knee.

Shoes are important. There is no one-size-fits-all. I always thought I was a size 13. It took a long time to realize that size 14 caused fewer issues – such as toes jammed up against the ends of the shoes, making my toenails turn black and fall off.

Cushioning is another shoe issue. After assorted foot and knee problems, I wound up becoming an Altra customer, using relatively flat-soled models without a ton of cushioning or heel lift or arch support – most recently the Escalante Racer ’19, before that the Altra One 2.5. I think the Escalantes were warranted for only 300 miles, and WebMD advises that shoes “are recommended to last for [only] a certain mileage.” But I put 1,600 miles of running and another thousand miles of walking on those Escalantes. You know, if it works, don’t fix it.

I think it may have stopped working, though. A few months ago, I came down with plantar fasciitis. While my post concluded that the plantar fasciitis boot was an integral part of my solution back in 2013, this time I seem to be holding it at bay with heel drops for 45 seconds, four or five times a day (see RunningPhysio). I realized the jig was up for the Escalantes when water began coming in through the sole. Now they’re my house slippers, with laces tied permanently to make them slip-ons. I hope my new Altra Vihos are not too much of a transition.

(I don’t get any payments from anyone – other than readers who make a very welcome donation – for anything in my blogs. I say that I’m using Altras simply because that’s the truth. I got the Vihos (no longer generally available) for $50. Comparable Escalantes are at least $100.)

I’ll just add a suggestion that, for best results with long laces, don’t tape them or tie them in a granny knot to keep them from unraveling. Just make the loops long, when you tie them, and tuck those long loops under the crosshatched laces ahead of the knot. Then they won’t get tangled in your bike pedals or chain; they will never come untied; and if you do it right, you can untie them in the dark without creating a worse knot, just by pulling on one of the loose ends.

Hydration and Food

Don’t overhydrate. Some runners actually gain weight, during a run, because they drink more liquid than they lose in sweat and pee. Hyponatremia is the word for excessive loss of blood sodium. This can happen when you consume too much water, thereby diluting the nutrients in your blood. According to Human Kinetics, exercise-induced hyponatremia resulting in as little as a 1% weight gain can impair performance, and a gain of 6% is likely to be fatal.

I never carry liquids. I don’t want the weight sloshing around and putting weird stresses on my knees or other joints. I want that skin on my back to be exposed to cooling air, not kept warm by a Camelbak bladder. Possibly the liquid would help on a long, hot run. For me, that might be above 15 miles, above 65°F. I try to avoid long, hot runs.

No doubt there’s a point when you need food. I have to balance that against the risk of stomach upset – which, in the worst cases, can incapacitate you. My solution is to virtually never run with food in my stomach. If I really needed fuel at runtime, I would consider a sugary beverage. But that doesn’t happen. I just don’t run within at least three (preferably, five or more) hours after a meal. Unless I’ve eaten a lot, or have eaten something hard to digest, that is apparently long enough for the stomach to empty out. I don’t eat until the run is over.

I also tend to be careful about not drinking too much, too quickly. One time, after a 20-mile run in Colorado, I went into a convenience store, bought a quart of Gatorade, and slurped it down on the bus ride home – and then promptly barfed it right back into the bag it came in. Fortunately, the bag had no holes. So I just carried a bag full of barfed Gatorade for a 20-mile bus ride. The bus driver was keeping an eye on me in his rearview mirror. I suppose I could have tried to redrink it.

When food leaves your stomach, it goes into your small intestine. It can stay there for some hours. If you already have some internal or external fat, even a smallish amount of food in the small intestine can make you feel really full and/or fat. The solution here seems to be, lose the fat if you can, so as to enable yourself to run, five or ten hours after a meal, without feeling full or fat.

Feeling full or fat seems to be more of a problem at the start. After a mile or two, it’s less of a burden, at least for me: I’m skinny. I don’t know what heavier people experience.

When food leaves your small intestine, it goes into your large intestine (a/k/a colon). Now we’re approaching pooptime. Going for a run is a great way to discover that you really need to use a toilet. When you run in the middle of the night, you learn the locations of all the Porta-potties and the 24-hour gas stations and hotels with public restrooms. Nobody wants a runs run.

For that, I have three precautions. First, realize that switching from a run to a walk can quickly diminish the desperate desire to defecate. Second, if there’s a chance you’ll be using a Porta-potty or taking a dump in the weeds, carry a Handi-Wipe. I use the individually packaged ones, but a bulk-packaged Wet Wipe in a Ziploc bag would work too.

Third, use a glycerin suppository before your run. This is an inexpensive, soft, crayon- or cone-shaped stick composed of a carbohydrate that dissolves in your colon. The trick is getting it there. The advice seems to be, bend over, make like you’re going to poop, push the thing up your butt at least a half-finger length, and then hold off pooping as long as you can. Five minutes may be more than enough. It won’t start a bowel movement, nor will it clear out everything, every time; but it can reduce the odds of needing a toilet during your run. Note that people have also suggested other solutions.

Lights

It may seem obvious that, if you run at night, you should wear a ton of lights to make sure that everyone within a three-block radius can see you. I don’t do that. I have a few reasons. One is that, when you run in the wee hours, there isn’t a lot of traffic. It’s not hard to avoid vehicles.

There will be the occasional self-righteous drunk driver who flashes his/her brights at you, to let you know that s/he was able to see you but might not have noticed you in some alternate universe. The greater concern is the occasional psychopath who may want to kidnap or take a random shot at you. Better not to advertise your existence. If I have to run from someone, I don’t want to be trying to turn off all my lights at the same time.

Where I live, the bars close at 2 AM, and the last survivors slowly abandon their parking lots. By 2:30 the streets are dead. Then you’ve got a quiet hour and a half, or more, before the uptight early morning restaurant-opening hyper-caffeinated workers hit the road. They will be ready to hit you, if you are four millimeters away from the part of the roadway where they think you belong; but they aren’t impaired and they aren’t pathological per se. Better still, there usually aren’t many of them. Then things quiet down again, until sometime after 5. The schedule runs a bit later on Saturday morning, and much later on Sunday morning.

Another reason for disliking lights is that they screw up your night vision. You find you can only see what’s lit – which is not great, if you’re moving fast enough to deny a long advance look at obstacles. There is the occasional spot that lacks illumination from street lights, headlights, and light pollution. For that, a headlamp could be useful. But you would still ideally not have to wear it constantly, thereby drawing bugs into your eyes and giving you a headache, especially if you’ve got its strap pulled tight to keep it from bouncing around.

You may also have to wear a headlamp, so as to use the dark and unsafe sidewalk, if the police in your city threaten you with anything like my experience of a bored cop who gave me a warning ticket for running along the edge of a deserted street in the middle of the night. Generally, though, night vision is the better solution.

You don’t need lights for running in the daytime, but in some situations a strobe or other attention-getting light could save your life. The problem with daytime running is that drivers are constantly pulling out of driveways and side streets onto the main roadway. They commonly launch their vehicles right across the sidewalk before they come to a stop. So if you are running down the sidewalk at the wrong moment, they will knock you out into oncoming traffic, in front of a speeding vehicle that will kill you.

For this, one solution is to run on the same side of the street as oncoming traffic, so that the driver who has lurched out from a side street will be looking in your direction for oncoming vehicles, and thus could at least theoretically see you coming. No guarantees on that one: they are looking for vehicles, not runners, and can therefore look right past you. Another solution is to veer out as far into the street as you can – again risking a ticket from a bored cop – so as to get more fully into the driver’s line of sight, and to give yourself a bit of space to work with, in case they do happen to hit the gas just as you’re crossing in front of them. Really bright flashing lights could be an aid in that case. So could a whistle, worn on a cord around your neck.

Despite my precautions and experience, I did face a risk of death one night, a few months back. I was running along a street with no sidewalk. A driver came toward me – and then he veered off the road, heading directly at me. There was a wall to my left: no exit. Possibly a boatload of flashing lights would have caught his attention – but not if he was too intoxicated to get it together, or if he had simply fallen asleep or passed out at the wheel. I was running past a few trees, but they did not seem thick enough, individually or collectively, to stop a vehicle at his speed. My only real solution was to dash across to the other side of the street as soon as I saw the problem. But I wasn’t on-the-ball enough to do that. What saved me was luck: he got his vehicle back on the street and went roaring past.

Weapons and Other Gear

It may make sense to carry a suitable gun if you run through areas where bears, mountain lions, or wild pigs are a risk. This depends on circumstances: mountain lions and wild pigs can be found, and may be bold, even within urban areas. For the most part, a knife or animal mace may be more than enough. Even a pack of coyotes is very unlikely to attack you.

Smaller animals (e.g., opossums, raccoons) are almost always afraid of you. I did become acquainted, over a period of months, with a territorial skunk who would come marching right at me – unlike most of them, who can’t hear very well but who will run a half-mile back to safety once they do notice your presence. Deer vary: some, especially bucks, will warily stand their ground, or slowly retreat a bit; others run like hell as soon as they see you. Little grey foxes in my vicinity are about as wary as stray cats. I have twice encountered a very self-assured red fox who does not seem to care whether I am there or not, as he chases those same cats. I did have an owl or buzzard flap his wings right above my head one time – I think he may have been close to clawing me – but I put my hands up; he tried again and I responded again; and then he left, no weapon needed.

In theory, a knife could also be useful for scaring or perhaps actually injuring an aggressive human. But there is a risk that the attacker has a gun, and that pulling your knife gives him/her a self-defense excuse for using it. Carrying a gun could be even more of an accident waiting to happen, if there is any chance that you would use it without thinking, in a moment of anger – because your friendly local motorists are going to give you some of those, as they indulge their usually distracted but sometimes deliberate efforts to kill you.

It’s probably a good idea to carry a phone, turned on, if you run at night. In my ten years of night running, I haven’t needed to make a single emergency call on my own behalf. I could have used a good video camera, when I was biking at these hours, because there were a few truly close calls, when I was nearly sideswiped by apparently intoxicated and/or psychopathic drivers. It seems, unfortunately, that the camera tech is still not good enough to capture sharp nighttime video. I have however seen the occasional car wreck. With one exception, the cops or other first responders beat me there. In that exception, the people were already dead, run over by a dump truck driver who fell asleep at the wheel. There could be a late-night emergency in which a phone could save a life.

Carrying a radio is an entertainment option, though phones can typically serve the same purposes. When using a radio or other device to play audio in the company of others (e.g., on a busy sidewalk or in a well-used park, or in the quiet hours of the night), earphones are the essential alternative to rudely imposing your tastes on everyone else and turning nature into an extension of a street downtown.

Other than that, you might want to carry plastic bags to protect electrical devices in case of rain; cough drops or candy for your throat, or for a bit of emergency energy; cash or a card, sufficient to buy Gatorade or a bus ride home; an ID card if stopped by police (though I’ve gotten by with just a photocopy of my driver’s license, which you can laminate with clear Contact paper); and the entry cards or keys for your gym or any other place where you’d want to stop off, for shower or restroom use or otherwise, before or after your run.

How to Get Started

The first rule: start when you’re young. There have been amazing exceptions (e.g., Kathy Martin). But for the most part, the younger you are when you begin, the more likely you are to view running, not as a chore, but rather as an intrinsic part of who you are. You’ll be more inclined to fight your way back to it, in midlife and even in old age, when life’s inevitable injuries and other interruptions would give you an excuse to quit – like the many people I have met who have claimed that sore knees or other maladies required them to hang up their sneakers. If you start before you accumulate any major problems with joints, muscles, tendons, or ligaments, you will have a clearer understanding of how such injuries change you, and you’ll be better equipped to figure out what treatments help.

The second rule: don’t overdo it (see above).

The third rule: don’t run to lose weight. That makes it a chore, and we tend to avoid chores. When you get to the point of wanting to run (see rule 4, below), weight control will likely become less of an issue. That may not be true if you’re addicted to Twinkies. It also won’t work if running becomes something that you reward by eating. I’ve been there. I sympathize.

The fourth rule: run because you like it. If you don’t like it, find a way to enjoy it and keep at it. Allow months for this. Simple walking or other outdoor exposure can help with that. I find that, the more I’m outside, the more I want to stay outside. When walking several miles is no longer a big deal, the thought of jogging a city block may be less intimidating. It’s OK to do little sprints. In fact, interval training is supposedly as good for you as continuous running.

Running is most appealing when the location is fun. As discussed in another post, that can mean trail running instead of just staying on the streets. It probably means mixing up the distances you cover – ranging from attempts at a fast quarter-mile up to half-marathons and beyond – and doing your best with each, instead of always plodding through the same three-mile (or whatever) trudge. It can mean running in parks or out in the countryside, instead of the city, and choosing city routes that are interesting, that let you enjoy new places. Bus running is an option: take the city bus out to your starting point, or back from your ending point. Google Maps, Street View, and Earth are your friend, for purposes of finding new places to explore without getting stuck in cul-de-sacs.

I had a really pleasant 18-miler, a few weeks ago, at 5 AM on a Sunday. It wasn’t anything spectacular; I just happened to be on a road that had airport activity (specifically, FedEx and DHL terminals) on the right side, and a freight train waiting at a siding on the left side. I caught up with the train at about the time that it started to move. So as I ran alongside it, it began to make noises and then began picking up speed until I couldn’t keep up. Simple events can be surprisingly entertaining when there’s not a lot going on.

Speaking of which, don’t expect that your mind will immediately find enough stimulation to carry you through a three-hour run without boredom. Music and podcasts are a possibility. I’ve never used them. I don’t want anything preventing me from the occasional social contact with others on the trail, and I sure don’t want to get lost in my head, or otherwise miss warning sounds (e.g., the sound of car tires catching up from behind). I fear that a fair number of fine would-be runners have been buried with their headphones.

Keeping at it means surviving disappointments. I meant well when I donated blood, and I donated regularly for years. But I backed off after one bad experience, when Red Cross personnel deceived me regarding the type of procedure I was experiencing. At my age, that episode seems to have had permanent deleterious effects on my running. The next time I donated blood, years later, was more straightforward – but by then, age and cardiac conditions meant that I lost the entire running season (i.e., the short San Antonio winter, which is the only time when I can run full-tilt) to a very slow recovery of my strength. I lost a year to caution after my experience with atrial flutter, and another year to caution after my knee started aching. And so on.

The really surprising thing is that such things don’t happen so much anymore. You’d think I’m getting older, I should be losing more time to injuries and complications, but it seems to be the other way around: I seem to have accumulated enough relevant experience to avoid most of the events that would impair my running.

Some time back – maybe while I was researching my posts on sleep issues or on heart problems related to distance running – I came across research suggesting that people who slept fewer hours at night – or maybe it was people who slept in the daytime – tended to have more problems with gaining weight. The suggestion at the time, as I recall, was that maybe they were more inclined to snack, late at night.

That could be. But an article in Popular Mechanics (Leman, 2022) cites a study by Mason et al. (PNAS, 2022), investigating the effects of ambient light during one’s sleep. Northwestern University (Paul, 2022) elaborates on that study, explaining that human physiology responds to light at night as it does in daytime:

[L]ight exposure during daytime increases heart rate via activation of the sympathetic nervous system, which kicks your heart into high gear and heightens alertness to meet the challenges of the day. …

Investigators found insulin resistance occurred the morning after people slept in a light room. Insulin resistance is when cells in your muscles, fat and live don’t respond well to insulin and can’t use glucose from your blood for energy. To make up for it, your pancreas makes more insulin. Over time, your blood sugar goes up.

An earlier study published in JAMA Internal Medicine looked at a large population of healthy people who had exposure to light during sleep. They were more overweight and obese ….

The study tested the effect of sleeping with 100 lux (moderate light) compared to 3 lux (dim light) in participants over a single night. …

Tips to reduce light during sleep

Don’t turn lights on. If you need to have a light on (which older adults may want for safety), make it a dim light that is closer to the floor.
Color is important. Amber or a red/orange light is less stimulating for the brain. Don’t use white or blue light and keep it far away from the sleeping person.
Blackout shades or eye masks are good if you can’t control the outdoor light. Move your bed so the outdoor light isn’t shining on your face.

According to Wikipedia (see ScopeCalc), the 3 lux level tested in that study would be similar to the brightness outdoors at the dark limit of civil twilight – that is, when you can just barely see outdoor objects clearly enough to get by without artificial lighting, roughly a half-hour before sunrise or a half-hour after sunset (in a location without light pollution).

The 100 lux level would be comparable to a very dark overcast day, or a little brighter than an office building hallway. Paul (2022) seemed to feel that a TV screen (or, presumably, a computer monitor) would be bright enough to have such effects. Again quoting one of the study authors, “If you’re able to see things really well, it’s probably too light.” Popular Mechanics (Leman, 2022) suggested using a night light rather than a lamp, and arranging things so that no lights are directly visible from the bed.

My thought, upon reading these materials, was that sleeping with too much light – due to either lights in the room or daytime sleeping without blackout curtains – could stimulate weight gain, regardless of snacking, because of the physiological effects of exposure to light. To me, as a person who runs at night during the hot months, and who feels moreover that his metabolism has changed within the past few years, this research did support the common-sense conclusion that I should make sure the bedroom stays dark during sleep hours.

Contents

How Laws Work
The War on Runners
Laws on Using the Sidewalk
Why Run in the Street?
Why Run at Night?
Ticketed for Being a Runner
Ticketed by a Shavano Park Officer Defying the Governor’s Order to Wear a Mask During the COVID-19 Pandemic
Epilogue

.

How Laws Work

I am a lawyer. And as a lawyer, in my years of exposure to the law, if there’s one thing I’ve learned, it’s this: rules are made to be broken.

No, I don’t mean that people should go around deliberately doing illegal things. I mean that it is hard to write a rule that fits all situations. Rules that look simple and obvious are especially likely to have problems.

Here’s an example that everyone has heard of: “Thou shalt not kill.” The rule is clear, right? It is part of the Ten Commandments in the Bible, printed in Exodus 20:13 and reprinted in Deuteronomy 5:17. And it is accompanied a number of Bible stories in which the ancient Israelites did exactly what the commandment said not to do: they went forth and killed.

Joshua Fighting Amalek (from Wikipedia)

For instance, we have Deuteronomy 20:16-17:

However, in the cities of the nations the Lord your God is giving you as an inheritance, do not leave alive anything that breathes. Completely destroy them – the Hittites, Amorites, Canaanites, Perizzites, Hivites and Jebusites – as the Lord your God has commanded you.

Regardless of whether a person believes that the Israelites should have killed the Canaanites, the reported fact is that they did — and, moreover, that they were ordered to do so, by the same God who gave them the commandment carved in stone.

A humble person might receive that perplexing information as a call to learn, and to think, not only about God, but also about seemingly simple rules. No doubt many Bible readers, being truthful with themselves, have recognized that there is a problem here, and have sought to learn about it and to become better practitioners of their religion.

But that is not how the careerists see it. What I saw, during my pre-ministerial studies in college — this was before I became a lawyer — was that the minister feels compelled to make excuses for God, because God does so much stuff that just doesn’t fit within what the minister wants the Bible to say. And so we have an endless supply of theologians doing exactly that. We have, for instance, William Lane Craig, who says, “God has the right to take the lives of the Canaanites when He sees fit.” Which, I guess, means that the Israelites weren’t actually killing them. We have Markus Zehnder‘s argument that this was just “ordinary warfare, with the initiative for the violent conflict generally lying on the side of the Canaanites.” In other words, the Canaanites could legitimately be killed because they defended themselves against the Israelite invaders. We have myriad Bible translations, some of which say it is actually a commandment against “murder,” not “killing,” and then lots of people explaining that war isn’t murder, it is just killing, and that is OK. Which makes sense, right? Wasn’t Jesus the one who said, Kill your neighbor?

You get the idea. You can start with a very simple four-word command, and wind up with people spending their lives writing circles around it, and persuading others to do just the opposite of what it says — and them believing that this was exactly what the lawgiver wanted them to do.

Well. If you can get that kind of snafu in something as important as the foundational text for several of the world’s major religions, you can sure as hell get it when legislators sign off on some minor law without even bothering to examine what it might mean.

The War on Runners

Which brings us to the war on runners and bicyclists. In previous posts, I have noted that the American automobile pathology basically ruins bicycling in this country. In this post, I turn to the situation of the runner. Running, I have said, is safer, partly because bicyclists are more vulnerable to psychopathic drivers.

On the other hand, most drivers have at least ridden a bicycle, whereas most have not done any real running since (maybe) a few required laps on a nice, level track in high school. If you think it is difficult to get someone to move their butt from the couch to a bicycle seat, you should try persuading them to strap on the shoes and do the hard work of becoming a runner. Every now and then, you might encounter someone like an ex-girlfriend of mine, who decided to give running a try and — wow! it actually reduces my blood pressure! But for the most part, there are the runners, and then there is the rest of America, telling us how to do it properly.

But one thing at a time. For starters, let me not take for granted that everyone knows running is good for you. Some people may not be too sure about that. How about the old idea that running is hard on your joints? Not true! Experts no longer believe that the impact of running injures your knees. In fact, for an older guy like me, regular running actually keeps the joints working. I have a left knee injury from being T-boned by a driver in New York City in 1987, and I have a right ankle injury from stepping off a tailgate while carrying 75 lbs. of asphalt shingles in, I think, 1971. I find that these old injuries become more painful and obtrusive when I do not run. By this age, my father — not a runner — had already had dual knee replacements. My brother — not a runner — has had surgeries on his feet. So far — knock on wood — despite my old injuries, my legs and feet are in much better condition than theirs were at the same age.

According to Healthline, health benefits of running (ideally, 2.5 hours per week) include improved sleep and mood and reduced risks of cardiovascular disease, cancer, neurological diseases (e.g., Alzheimer’s, Parkinson’s), and death from heart attack or stroke. Business Insider (Loria, 2018) says, “Many experts consider exercise to be the closest thing to a miracle drug” — noting, along with the benefits cited by Healthline, that running not only seems to improve knee health but also makes the brain more resistant to stress.

In a nation that is trying to help its people become healthier and cut spending on healthcare services, it makes no sense to pass laws and pursue policies that penalize running and endanger runners.

Laws on Using the Sidewalk

An example of a law that penalizes running and endangers runners: the one that requires runners to use the sidewalk, regardless of whether that makes sense in the particular situation. This law varies from state to state. Here’s the version found in Texas Transportation Code 552.006:

A pedestrian may not walk along and on a roadway if an adjacent sidewalk is provided and is accessible to the pedestrian.

It looks pretty simple, right? But let us learn from the Israelites. The simple law may not be so simple, when you stop reading it and start living it. Go out for a run, on the sidewalks in your neighborhood, and you might find that the seemingly simple rule becomes confusing and even dangerous. Consider:

  • What does “pedestrian” mean? Should it include sprinters? (You might want to watch the accompanying video before deciding.) How about little kids riding little tricycles? Bigger kids riding little bikes? Does it include scooters? What if they have motors?
  • What does “adjacent” mean? For example, many streets have a sidewalk on one side but not on the other. Must a pedestrian cross a potentially dangerous street in order to get to the sidewalk on the far side, or is that not considered “adjacent”?
  • What does “accessible” mean? It could mean, are you physically able to walk over and put your feet on the sidewalk? Or it could mean, does the sidewalk offer safe and practical accessibility — does it work for the purposes intended by a runner, a skater, or a wheelchair operator?
  • What does “sidewalk” mean? One might consider this obvious: it is the line of pavement, usually concrete, that runs alongside the roadway. But in some states — including Florida, according to BikeWalkCentralFlorida — the “sidewalk” is considered the space between the curb and the adjacent property line, even if “tall grass, landscaping, and other challenges” render it unusable for pedestrians.

In the legal world, there are different ways to get answers to such questions. Sometimes you can just open a book or webpage that discusses the legal issues in detail. This is especially likely where many lives and/or many dollars hinge upon the outcome. On the question of running for exercise in Texas, trust me: nobody is researching, writing about, and preparing books and webpages to explore these sorts of legal issues in any detail.

It is much easier to make rules than to think about their possible consequences. Thus, for the most part, the primary way for ordinary citizens to get answers to such questions is to get arrested, spend thousands on a lawyer, and let him/her dig up obscure precedents or invent arguments on your behalf (see “ministers,” above). This is why everyone praises the rule of law: it is simple, practical, and cost-effective. (Pardon the sarcasm.)

The unfortunate reality is that cities and states know we are in this situation. So they don’t fine us to the point where we pretty much have to hire a lawyer and really fight their rules. They’re content to shake us down for a couple hundred bucks and send us on our way. So, for instance, we have the case of Tommy Bice, who was fined $245 by the City of Bryan for violating the Texas sidewalk law quoted above; and then we have the case of Romel Henderson, who was fined $409 by the same city for the same thing. Why the difference? Good question. Add it to the list of other questions about this law.

On the positive side, the laws in some states are less hostile to pedestrians. For instance, Ohio Revised Code 4511.50 says it is unlawful to walk along the road “Where a sidewalk is provided and its use is practicable” (my emphasis). Likewise Maine Title 29-A, ch. 19, sec. 2056. And, even in Texas, some cities have exercised their option to supplement the state law. Here, for instance, are excerpts from San Antonio’s ordinance:

WHEREAS, bicyclists and pedestrians are allowed to use the roadway by law in Texas, but these users do not have the same physical protection as motorists and are at greater risk of injury or death; and

WHEREAS, approximately 50 cyclists and 400 pedestrians are killed every year in Texas; …

NOW THEREFORE:
BE IT ORDAINED BY THE CITY COUNCIL OF THE CITY OF SAN ANTONIO: …

[A] Vulnerable Road User means … [among other things] a pedestrian, including a runner, physically disabled person, child, skater, … a person operating … a bicycle ….

An operator of a motor vehicle passing a vulnerable road user operating on a highway or street shall:

vacate the lane in which the vulnerable road user is located if the highway has two or more marked lanes running in the same direction ….

An operator of a motor vehicle may not maneuver the vehicle in a manner that is intended to cause intimidation or harassment to a vulnerable road user; or threatens a vulnerable road user.

This ordinance appears to say that it may be illegal to walk along the edge of the roadway if there is an adjacent sidewalk — but that’s no excuse for motorists to threaten you. Regardless of whether your behavior is legal, the fact remains that you are a vulnerable user — for all they know, you may be a person with Alzheimer’s, or a visitor from another state or country, where laws are different — therefore drivers have to take common-sense measures to avoid hitting you.

That should be the law nationwide. It isn’t. Thank your state legislature. By voting or not voting, you elected them!

Sadly, city mayors cannot overrule state law. The San Antonio ordinance shows that they can only penalize some behaviors on the part of distracted, incompetent, and mentally ill drivers who use their two tons of steel to kill walkers and riders. Further, ordinances don’t matter if the police are on the side of the psychopaths. That, unfortunately, is the reality in America. As discussed in another post, police nationwide commonly fail to charge drivers even when they are blatantly responsible for hitting and killing cyclists and pedestrians.

Why Run in the Street?

To the large majority of Americans, driving down the street, the situation is obvious: “We have paid good money to lay down perfectly good sidewalks; you need to use them.” People saying this sort of thing tend to be those who rarely use sidewalks beyond their own front door. Generally speaking, they have no clue as to why they might be wrong.

People who actually use the sidewalks are likely to come into contact with reality soon enough. It only takes one encounter with a driver who comes shooting out of a driveway, staring hard to his/her left, to see if cars are coming, as s/he rolls right across the sidewalk and any pedestrian who happens to be on it. I’ve had those experiences. Like, once, on the Indiana University campus. Sweet young thing, driving, talking on her phone, looking everywhere except right in front of her. I was running on the edge of the street, so she didn’t hit me before she came to a stop. I smacked her car hood and her head turned, eyes opened wide, jaw goes slack, and I can just hear her thinking, “Oh, I almost knocked that man out into the street in front of that delivery truck.” A few experiences of that type will teach the sensible runner to run along the edge of the street, so as to be beyond the point where most drivers stop before proceeding into the roadway.

But you need not be a runner, or experience that particular situation, in order to learn what’s the matter with sidewalks. You can get to the same place by just putting yourself in the shoes of people who might not be exactly like you.

The wheelchair user is a good example. I wouldn’t advocate that wheelchair users go riding down the edge of the street if they have an alternative. Unlike the runner, wheelchair riders are generally unable to hop up on the curb and wait until a car passes.

Nonetheless, the wheelchair is a great device for awakening people to what others experience on our sidewalks. Trying to use a wheelchair on a sidewalk is one example of what we taught fourth-graders in the disability awareness workshops that I participated in during my social work education. In these workshops, the kids tried to read things that imitated what a dyslexic person would see; they tried to engage in everyday activities while sitting in a wheelchair.

If we were to put you in a wheelchair on an American sidewalk, you would quickly get up to speed on the rather large number of little barriers in what you thought were perfectly flat and smooth sidewalks. Suddenly you discover that sections of the sidewalk are uneven: you are struggling against an angle. One section is higher than another; it is like a little wall that your wheelchair must climb over without tipping. There are holes. There are fallen branches. Your wheels get stuck in gravel and dirt, turned by sticks, and stopped by twigs.

Other problems should be more obvious to everyone. Often, city employees fail to keep them clear. The police do not ticket people for blocking sidewalks and bike lanes with trashcans and with illegally parked vehicles. Street crews do not keep sidewalks clear of vegetation: branches hang down, twigs stick out from bushes alongside, weeds take over down below. There can be broken bottles in those weeds. The sticks poking out of trees and bushes are often dry, hard, and leafless. They can be hard to see even in daylight. But that won’t prevent them from giving you permanent eye damage. And then there’s the fishing line and the wire that you’ll never even see. In some spots, vegetation completely takes over the sidewalk. You have to break the law — you have to step out into the street to get around it.

A San Antonio bike lane

In these regards, the situation for runners is much like the situation for bicyclists: the only safe place to travel is out in the traffic lane. Out there, cars smash, pick up, or blow aside the nails, broken glass, sticks, cardboard boxes, and other debris. Sure, streets have holes and cracks and debris too. But runners quickly learn that streets tend to be much, much better funded, better lit, and better maintained than sidewalks. Your odds are much better out there.

In other words, if you want a safe biking experience, do not ride in a bike lane. That’s where all the rocks, random pieces of steel, plastic bottles, discarded mattresses, and raccoon skulls accumulate. Riding in a bike lane invites a crash. I have a five-inch scar on my right shoulder due to surgeries to repair bone fractures incurred during a bike crash. I would rather not have another.

Yet even these remarks may fail to convey just how alien it can be, in Texas, to use the sidewalks. For example, imagine trying to ride your wheelchair down the sidewalks in this photo:

Sidewalks in San Antonio

As you see, it is physically impossible to run along the sidewalks, in many neighborhoods, because residents and/or cities have insisted on almost completely blocking them with stone monoliths dedicated to the mailbox. So if you live in this sort of neighborhood, you invite a traffic ticket from a hyperactive cop if you even try to use the sidewalk.

If you want to know why runners prefer the street, the San Jose Mercury News (Richards, 2014) provides a list of reasons submitted by readers. Excerpts:

There are virtually NO “perfectly good sidewalks” in the 3-mile radius of my home where I run. The sidewalks are in disrepair with raised edges that can trip you up no matter how careful you are. Also, many residents do not sweep their sidewalks. Leaves and needles make for slippery surfaces, especially after it rains. …

Sidewalks are simply not safe for running. The uneven sections are trip hazards for runners. I have scars on my knees and elbows from falls, and every one happened when running on a sidewalk.

When I walk in the streets, this is what I am thinking: There are too many uplifted sidewalks waiting to trip me, resulting in broken body parts. … Williams doesn’t realize that the “perfectly good sidewalks” may look perfect from her driver’s seat, but not up close. It doesn’t take much to catch a toe when walking, and I am not that old.

I’m particularly tall (6-foot-7) and the various trees/bushes along sidewalks around Berkeley very often are not trimmed high enough for me to walk without ducking a lot. It often feels like I’m almost doubling over. So walking in the street means I greatly reduce getting hit in the face with a branch and don’t have to duck every few steps.

Quora (MacDougall, 2019) offers some more:

There are driveway aprons you have to go down and up without tripping. There are lamp posts, sign posts, fire hydrants, utility boxes, trees and the planter boxes around them, trash bins, ash cans, newspaper racks, vehicle bollards. …

Tree root cracks, and other cracks, are big hazards. I still have scars from a fall tripped by a tree root crack many years ago. My wife broke a rib tripped by one. …

There may be slow pedestrians who may move in unpredictable ways. Dogs on leashes are a major hazard …. Trying to run past an elderly pedestrian delicately balancing with a cane, or a toddler meandering, without hurting someone is risky.

Cars can pull into or out of driveways across the sidewalk, often from hidden locations. They often assume the sidewalk will be empty. …

Part of the problem is that roads are generally better maintained than sidewalks, because roads get transportation funding. Sidewalk maintenance is not well funded.

They left out one of my favorites: skunks. Where I live, there are always skunks. They come out at night. They root around in the dirt, sometimes right next to the sidewalk or street. They seem to be half-deaf and nearly blind. You can walk or run right up to them before they register you’re there. I’ve come close enough to kick them. Fortunately, they are passive. They lift the tail and run away. All except an aggressive one who would charge me as I walked down a nearby street. Not rabid: he lived too long for that. Just unfriendly. Regardless, I would rather give them a few extra feet of breathing space.

Complaints about the risk of tripping and falling on a sidewalk may seem trivial. I can assure you they are not. I echo the runners, just quoted, who spoke of injuries due to falls while running. In addition to scars and banged-up knees and elbows, two of my falls have resulted in broken ribs. The worst falls are the ones where your foot gets stuck, like when your foot gets snagged by a hole or branch. Then you don’t go bouncing along the pavement, just getting scraped up: you fall flat on your face. That’s how I broke my ribs.

The problem is compounded as I approach age 65. According to the CDC (2020), falls are the leading cause of injury-related death among adults age 65 and older. Presumably lethal falls occur especially among those who are especially old, aged 75 or 80 or more. I hope my running is keeping my bones and joints relatively strong, so that doesn’t happen to me.

Why Run at Night?

The problems just described are multiplied at night. When it’s dark out, you can’t see where the sidewalk is uneven, or choppy; you can’t see tree roots that will trip you, or potholes that will break your ankle. You can’t see those dead sticks poking out of the trees and bushes that the city fails to maintain. Streets can be uneven too, but there are far fewer pavement irregularities, and even a distant streetlight or vehicle headlight can assist in spotting them.

To those who have no clue about running, it must seem ridiculous that I would run at night and risk such injuries. Any person with a whit of common sense would run in the daylight, right?

Let me address that thought. First, as just explained, the sidewalk hazards are there even in daytime. I have tripped and fallen in daylight too, due to hazards that I did not see. The branches and vegetation remain in place, 24 hours a day. People in colder climates often have the additional problem that sidewalks are often just as full of ice and snow in daytime as at night.

These days, there is an additional problem. At present, in July 2020, the United States is in the grip of something known as COVID-19. It is a potentially lethal disease caused by a coronavirus. While experts remain unsure of many things about this virus, it does seem clear at this point that the virus is spread by people coming into close proximity with one another. Experts believe that it is more dangerous to be around people indoors, where air does not necessarily circulate well, but there have also been cases of infection due to being too close to others outdoors. As reported by the New York Times (Barkhorn, 2020),

Increasingly, when I leave the house I find myself not relaxed and rejuvenated by exercise and fresh air but anxious and frustrated at the terrible social distancing job my neighbors are doing. I see people walking in the middle of the sidewalk; families out together en masse, taking up the entire width of the path ….

All of these behaviors make it impossible to keep six feet distance. …
Some walking and running paths have recently been closed by local governments because they got too crowded, including Chicago’s Lakefront Trail and all public trails in Los Angeles.

Running at night resolves those problems. When you run in the middle of the night (in my case, typically between 1 and 5 AM), as I do, you pretty much have the place to yourself.

Well, but what about wearing a headlamp while running, so as to be able to see where you are going? There are several things to consider. First, no headlamp will provide the sort of lighting that you get from your car headlights: they draw upon an electrical system far more powerful than the batteries in a headlamp. Moreover, cars have two headlights, several feet apart: this greatly reduces shadows and provides a much better sense of physical location and distance.

You can buy a heavy headlamp with strong batteries and a strap going over your head. I have adapted that kind of headlamp to my bike helmet. As shown here, it tends to involve more weight and hardware than most runners will want to have bouncing around on their heads, and it is at risk of getting tangled in overhanging tree branches — which, in the worst case, could break your neck:

Headlamp straps can be uncomfortable in the heat, can interfere with hats in the cold, and can give you a headache. A headlamp also draw bugs right into your eyes; and the brighter it is, the more bugs it draws.

You’re putting up with all this in order to have illumination — and yet, as you may have noticed if you’ve ever used a flashlight in a campground, the bright circle of light created by your headlamp suddenly makes everything else darker. That is, it significantly reduces peripheral vision. Your headlamp can’t be pointed everywhere at once. While you are dodging the tree branch in front of your face, shadows dancing among your feet conceal the tree roots lurking there.

Especially if you’re running at any speed, no headlamp is going to provide enough illumination to give you good protection. In the accompanying video, you can see how little illumination a runner will get, even from the powerful headlamp shown above. If you want to get aid from a headlamp, run in the street, because out there you don’t have to worry about branches and other obtrusions: you can focus on spotting pavement irregularities, and for that focused purpose the headlamp may help.

In other words, people who have spent years doing something — in this case, running — have probably already thought of the solutions that might come to the mind of someone who knows nothing about it. Believe it or not, runners are not actually looking for ways to make life complicated and unpleasant. We are actually interested in good solutions. That’s why, when we find a relatively good solution, we write blog posts like this one, to try to explain it to people who are not familiar with it.

I realize that some people are not good at putting themselves in someone else’s shoes. To them, the solution to every problem is just to do what they say — to live your life as they think you should. I guess this blog post is not written for someone who refuses to try to understand it.

For me, the single biggest reason to run at night is heat. I have a cardiopulmonary condition that, so far, the doctors haven’t quite figured out. Nobody seems to think I should quit exercising; it’s just that some exercise conditions are better than others. The problem is much worse in hot weather. Basically, I have problems when I run in the daytime in the heat. San Antonio is an especially bad place for me in this regard, because it gets so damned hot, as it is right now.

For me, during San Antonio’s many hot months, the difference between running in the daytime and running at night is the difference between running or not running at all.

To alleviate that problem somewhat, in hot weather I have gravitated toward doing more interval running. I find that, depending on the temperature and humidity, I may have cardio issues even after running a single mile. But interval running — that is, alternating sprints and walks, each a block or two long — reportedly produces a good workout; and, for me, the cooldown walks between sprints seem to eliminate cardio issues.

Air pollution is yet another issue. The Texas Commission on Environmental Quality (TCEQ) has indicated that ozone pollution reaches its highest concentrations in afternoon and early evening. Particulate matter is also a problem. Research Pipeline concludes that air pollution drops pretty consistently overnight, reaching its best level at around 5 to 10 AM. For those who run along busy highways, of course, the earlier (and, most of the year, the darker) hours are better.

On a more subjective level, I simply prefer the quiet of the wee hours. There’s nobody out. Go after the bars close, and you can spend several hours biking with relatively few threats of getting killed. You can go for a two- or three-hour walk under the stars or the full Moon, with hardly anybody but your own thoughts to disturb you. It’s as close to the countryside as you can get in many city environments.

Ticketed for Being a Runner

I was moved to write this post due to an event that occurred yesterday morning — that is, about 4:30 AM on July 14, 2020. At that time, a police officer in the city of Shavano Park, Texas gave me a ticket for running along the edge of the street.

I have been running for nearly 40 years. I have run in a number of different cities. This was the first time that any police officer even bothered to say anything about it, much less ticket me for it.

It was only a warning ticket. I appreciate that the officer did not formally charge me with a crime, costing me hundreds of dollars. But in terms of my running, the effect was the same: the officer’s warning makes clear that I cannot run in Shavano Park anymore. I can’t run where there are real sidewalks, because they aren’t adequately lit and designed for running; and I also can’t run where there are no sidewalks, because suddenly I cannot be sure how Shavano Park officers will interpret the law in that kind of location.

It was really a surprise. I have been walking and running through Shavano Park for the better part of six years. I would have thought that most of the police officers working the night shift in that little city had become familiar, by now, with my presence on that city’s streets at night. On several occasions, I have exchanged a friendly word or two with some of them. As I say, none has ever suggested that I was walking or running in the wrong place.

A brief review of the Shavano Park policing situation may underscore just how heavily surveilled I have been, over these years. Shavano Park consists of a few housing developments stemming off from several larger (mostly four-lane) streets. The population of Shavano Park is only 4,138 (WPR). There are, I think, no bars or restaurants, generating nighttime activity; there are hardly any businesses at all.

To patrol this place, the police department of Shavano Park employs (would you believe) 19 officers (Wikipedia). That gives Shavano Park the equivalent of about 46 officers per 10,000 population. Thus, the town has about three times as many police officers per capita as the average American city (Governing.com, 2016). This relatively massive police force is hired to patrol a total of about nine miles of primary roadway. To some, the overkill will seem almost comic. But apparently the city can afford this, and more, given a reported median household income of $208,021.

The police vehicle parking lot at the Shavano Park police station (click to enlarge)

To assist in patrolling — as you can see if you pass the parking lot at the unexpectedly large police station at night — the city appears to have about a dozen police SUVs. Even during the daytime, at least a third of them remain parked. Prices vary; but if they are the Ford Interceptors that have proved popular among police departments, they cost over $35,000 each, and can hit 137 MPH, according to the Detroit Free Press (Howard, 2019).

I haven’t kept count, but I would say that, on the large majority of occasions when I have walked or run through Shavano Park in the middle of the night, over these past five or six years, I have been passed by Shavano Police vehicles not just once, but several times. On a few occasions, those SUVs (sometimes more than one) have gone racing past me at, I would estimate, somewhere around 80 MPH. For the most part, they have just rolled past, apparently observing the 35 to 45 MPH speed limits governing most of Shavano Park’s main roadways.

During those many passes, the Shavano Park police could hardly have failed to notice me, running along the roadway: there was simply nothing else going on. To emphasize, these are major four-lane streets running through a substantial chunk of San Antonio; but at those hours, there have been numerous times when not a single vehicle has passed me for ten minutes or more. Unless the officer who ticketed me is new to the force, he has surely seen me out there any number of times.

On this particular occasion, I waved as he passed me. The last thing I expected was for him to do two U-turns and come back to ticket me, lights flashing. I had to wonder whether maybe he did so because the wealthy residents of Shavano Park have suddenly decided to discourage people from walking or running through town, for fear that we might somehow spread COVID-19 to their city. If so, there would not be many of us to intimidate: I don’t think I have ever seen another nighttime runner in Shavano Park.

This all seemed very strange. When I was a kid, one of my friends said that R.D. (full name withheld), whom I didn’t know personally — a state police officer or county sheriff or something — used to turn on his siren and lights just because he wanted to go ripping through a certain small town at high speed, and didn’t want to get in trouble for it. There is that old saying about how idle hands are the devil’s workshop. It did seem like the officer on Lockhill-Selma must have been pretty bored.

After he wrote me that ticket, I realized that I had better call the San Antonio police, to find out whether there was perhaps a Texas police campaign to control a troubling rise in suburban jogging. The answer seems to be no, there isn’t. The officer I spoke with said that San Antonio police might stop a person if they wanted to find out what was going on. If they did stop a person for that purpose, they would probably want to document the encounter, in case there was some later report of criminal activity in the area. He said that a warning ticket could serve as documentation for that purpose. But he also said there are other forms of documentation which, apparently, would not require the officer to intimidate people.

I explained that, in this case, the Shavano Park officer did not seem to be investigating suspicious behavior. He didn’t appear to be trying to document my presence in connection with any other activity in the area: there was nothing going on, and he didn’t ask what I was up to, or where I had been. He also wasn’t protecting anyone. I was not going to get hit, and I was also not going to distract any drivers. There were no drivers. It was 4:30 AM on a Tuesday. Lockhill-Selma was almost completely silent. In the ten minutes (or so) that he had me standing there on the sidewalk, only two vehicles passed.

The officer was clearly stopping me for only one purpose: to make sure that I would always limit my running to a surface that he could consider a sidewalk, regardless of its condition. After I described the situation, in our phone conversation, the San Antonio police officer replied that he, personally, had never issued a ticket for that. He said it was up to every officer’s individual discretion, but in his view the police had more important things to worry about.

As indicated in the accompanying video, the Shavano Park police officer felt that the law does not care why someone might violate it. The law simply insists that there must never be a violation. Needless to say, an officer with views like this will be writing a great many tickets, for all sorts of offenses, large and small. One mile per hour over the speed limit — off to traffic court!

That doesn’t seem to be what they teach in cop school. It also doesn’t seem to describe the behavior of most police. In the words of Police Chief Darrell Volz of Balcones Heights (another San Antonio suburb), “As police officers, we have a tendency to not enforce things unless they become an issue” (NEWS4SA, 2018).

Unless you’re talking about a bad cop, who is just looking for excuses to harass someone, most people (and certainly most police officers) seem to understand that there are bad laws. There have definitely been enough articles about such laws. Business Insider (2020) offers a number of examples, such as the Massachusetts law that subjects you to a $100 fine for playing only part of the national anthem. Most people also understand that there are laws that can do real harm if they are enforced inappropriately. A Quora discussion offers examples of instances in which the police would be doing more harm than good if they enforced every law in every possible situation.

So, as far as I can tell, it is no longer safe to assume that the police of Shavano Park are reasonable. If I run through their jurisdiction, I am at risk of being fined — up to $400, apparently — for trying to avoid potentially serious injury, on sidewalks (and perhaps dirt margins) that are unsafe for running at any hour, and especially at night.

Ticketed by a Shavano Park Officer
Defying the Governor’s Order to Wear a Mask
During the COVID-19 Pandemic

As indicated in the video, I would have been willing to discuss these matters with the police officer, at a suitable distance, but he was not interested. He cut me off after I told him that I have had the experience of falling and breaking ribs, by tripping while running on sidewalks at night. He made very clear that he didn’t care about that at all.

His philosophy seemed to be that the job of a police officer is not to write or interpret the law, but only to enforce it. He had a funny way of enforcing the law, though. On July 2, 2020, Texas Governor Greg Abbott issued the following order, effective statewide at 12:01 AM on July 3:

Every person in Texas shall wear a face covering over the nose and mouth when inside a commercial entity or other building or space open to the public, or when in an outdoor public space, wherever it is not feasible to maintain six feet of social distancing from another person not in the same household ….

The governor’s order followed a similar order by Bexar County Judge Nelson Wolff (June 25, 2020).

Contrary to these orders, this Shavano Park police officer failed to wear a face mask at any point in this encounter. I wasn’t wearing one either — but that’s because, under the orders of the governor and the judge, I was exempted from doing so, as I was “exercising outdoors.” I really didn’t expect to be having many conversations on Lockhill-Selma at 4 AM. Anyone who has engaged in strenuous exertion while wearing a mask, in temperatures of around 80 degrees, in highly humid conditions, will understand why a mask was not a realistic option. I am usually soaking wet with sweat by the time I finish my summertime runs. A mask would be essentially glued over my mouth.

For the officer, unlike me, the governor’s order contains no exemption. To emphasize, there is no exemption for police officers. To the contrary, police officers are among those categories of individuals who are most likely to encounter many people, in the course of a day. As such, the police are at high risk of becoming infected with the virus and spreading it to others.

Thus, after more than five years of undisturbed walking and running through and around Shavano Park, during which that city’s officers have seen me traveling along the edge of the roadway on countless occasions, this Shavano Park officer chose to ticket me in the middle of a pandemic, while defying an express order from the state’s governor to wear a face mask “wherever it is not feasible to maintain six feet of social distancing.”

To emphasize: I am an elderly man with a cardiopulmonary condition that puts me into the high risk category of people most at risk of being killed by the virus. According to the Centers for Disease Control (June 25, 2020), the risk of death from COVID-19 is very much higher with rising age and underlying cardiopulmonary conditions.

I went out to run in the middle of the night precisely to avoid this sort of dangerous interaction. Of all the times when this officer could have stopped me, and of all the ways in which he could have conveyed a general warning or concern (e.g., yelling or using his loudspeaker from his driver’s seat), he chose to put my life in danger by coming over to stand upwind, four feet away from me, talking to me without wearing a mask, and demanding physical contact with me through a request for my identification. I can only shake my head at this photo from the Shavano Park police department’s Facebook page:

The officer on the right, in this photo, bears some resemblance to the one who stopped me, but I am not certain it is the same person. Regardless, it seems the Shavano Park police are aware of the mask requirement when there’s a camera around, but they are allowed to disregard it at 4 AM.

This post may be viewed by readers at various times in the future, when the current situation may no longer be as clear as it is now. So I will insert, here, a New York Times chart summarizing the present death rate in Texas due to COVID-19:

Focusing on this metropolis in particular, the San Antonio Express-News (Christenson, July 8, 2020) reported, a week ago, that San Antonio hospitals were nearing capacity due to a surge in COVID-19 patients. KSAT.com reports that, as of yesterday, San Antonio hospitals have started to use refrigerated trucks to hold the bodies of people killed by COVID-19, because morgues can’t keep up with the death rate. Here is a COVID-19 Watcher graph indicating that the number of cases in this metropolitan area has quadrupled in the past four weeks:

After all these months of watching New York City and other parts of America struggle with this virus — after seeing 136,466 Americans killed — this officer’s behavior is simply inexcusable.

The encounter could have been worse — he could have pinned me to the ground and then thrown me in jail — but, considering what we have learned about the virus, and the numbers of deaths we have seen among ordinary people who didn’t really believe what everyone has been trying to tell them, the risks he imposed upon me were pretty bad, and they were completely unnecessary.

I am retired. Aside from exercising and trips to senior hour at Walmart (6 AM Tuesdays) every few weeks, I have pretty much stayed home. In the past several months, this encounter with the officer was the only time when I have had an interaction with anyone outside my household, where neither I nor the other person was wearing a mask. In fact, due to considerable concern about the virus, I have devoted a very substantial amount of time to maintaining a blog post that seeks to understand and offer related safety advice.

Obviously, we can dispense with the fiction that this officer stopped me because of his dedication to law enforcement. The more accurate statement seems to be precisely the opposite: he is deliberately flouting executive and judicial orders.

In that, he is apparently not alone. CBS News (Lewis, July 8, 2020) says, “Police officials in at least nine [Texas] counties … said they will not impose” the governor’s mask order. And the governor’s order grants them that leeway, if they have had minimal cases of COVID-19. But where the county does impose the mask requirement — and certainly where the police department’s Facebook page acknowledges that officers are expected to wear masks — there is no latitude for rogue officers to jeopardize public health.

Needless to say, the lives placed most at risk by such behavior may be those of the city’s own residents. This officer had no way of knowing whether I am perhaps an asymptomatic carrier of COVID-19 — in which case he was the one at risk of being infected, and potentially infecting others within the city.

It is perhaps understandable that police in some remote, rural counties have decided not to impose the mask order. Maybe they don’t need it, or maybe they will just have to kill their people in their own way. We shall see. But Shavano Park is not out in the middle of nowhere, nor is it populated by people who don’t know any better. Shavano Park is completely surrounded by a city of 1.5 million people.

Having just seen four Fort Worth police officers make national news for failing to wear masks inside a gas station (e.g., Newsweek, July 11), the question is, how can Shavano Park spend such substantial amounts of money on its police force, and still wind up with policing that imposes a higher public risk than one would find in the majority of rural Texas counties?

Epilogue

I posted this item on July 15, 2020. I mailed a complaint to Shavano Park on July 17. On July 27, Shavano Park’s police department composed a letter, postmarked July 28, notifying me that the department had opened an investigation.

It appears that the department may have notified one or more of its officers of my complaint at that point. On July 29, this post received a sudden spike in page views. Also, on that date, someone attempted to post an anonymous comment in response to this post. That anonymous comment read as follows, in its entirety: “What a whiny law-breaking jag-off…”

The timing of that comment, and its reference to law-breaking, suggested that its author might be a member of the Shavano Park police department. If that is the case, it would be unfortunate. One would normally expect a public officer to have the courage to express his/her view clearly and forthrightly, as I have done, rather than toss out obscene remarks while hiding behind the cover of anonymity.

The content of the comment was also unfortunate. I am surprised that it should be necessary to reiterate that most people, including most police officers, are not so fixated on petty infractions. It is bizarre to insist that running along the edge of an empty roadway is “law-breaking” in any significant sense of the term. The comment does seem consistent with the impression of deep boredom on the part of some members of the Shavano Park police force.

It was baffling that the author of that remark would consider me the criminal (a/k/a “law-breaker”). Apparently s/he still did not understand that the Governor had ordered police officers to wear a mask during that phase of the COVID-19 pandemic. A grasp of that basic point would have made clear that the officer’s conduct was the real threat to public safety.

It seems, in short, that the author of that comment may be a Shavano Park police officer with a resentful attitude. If that is indeed the situation, it appears that I may be at risk of retaliation. That would represent a shocking departure from the friendly tone that I had experienced in previous encounters with members of that police force, going back years.

It did appear that my complaint achieved something. Shortly after I filed it, they moved the junk out of the bike path on George Road and trimmed some of the branches blocking one part of that trail, and apparently asked that driver to please stop parking in the bike lane. Also, somebody finally got out there and fixed the streetlight above what was the nearly invisible pole, shown in my video, directly in the path of the person running down the sidewalk on Lockhill Selma. So now, after months of invisibility, that pole is once again visible at night. Of course, that doesn’t do anything for the fact that sprinting remains impossible on that and other stretches of the sidewalk. Nor does it change the reality that many sidewalks, throughout the metropolitan area, are not suited for a variety of normal uses, at night or even in the daytime. In the real world, where people have to find a way to get down the road, punishing them for attempting reasonable workarounds is simply overpolicing.

MY SOLUTION: I started this post several years ago. To anyone who might have benefited from it, I’m sorry I let it sit. I meant to come back and do a more complete job. But for the past few years (as of this writing in February 2020), I have had a working solution to my calf problems. I simply do a ~15-minute warm-up walk before each run, and I also do another brief (~5-min.) walk anytime my run is interrupted for more than 60 seconds or so. I don’t seem to need any of this when I’m out of shape. But when my calves are tight, this has been the solution for me. See the Updates section, toward the end (below), for recent additions.

I plan ahead, so as to prevent my route from requiring me to stop. For example:

If that short answer doesn’t work for you, then read on. I never did finish the research in this post. In several spots, especially toward the end, the text is disjointed and unfinished. I hope it helps nonetheless.

* * * * *

I had my first calf attack — that is, a sharp pain in my calf while running — in 2006, when I was 50. At this writing in 2017, more than eleven years later, I was still dealing with it. This post presents information I accumulated and conclusions I reached, in the process of attempting to understand the problem and its solution.

The term “calf attack” is my shortened version of the “calf heart attack” term suggested by Runner’s World (Parker, 1996). Having experienced it, I could see why someone would compare it to a heart attack. It was a stabbing pain, like a heart attack, and, for purposes of running, it could be terminal. In Parker’s phrasing, you could “diddle around” with this for months, trying various cures that did not fix the problem. Although I usually had it in my right calf, sometimes I would also have it in my left calf. The two seemed independent; that is, having it in one calf did not seem to influence the other.

Note: I am not a medical professional. This post represents only a writeup of my efforts to understand my own calf pain.

Differential Diagnosis: Less Plausible Possibilities

I believed I had a simple muscle problem. Therefore, at first, I did not attempt to distinguish and rule out alternative possible explanations for my calf problems. This section came into existence when, in the interests of thoroughness, I went back and looked at other potential diagnoses.

A search for sources of information on possible causes of calf pain led to a seemingly endless variety of seemingly relevant materials. Brewer & Gregory (2012), Bonasia et al. (2015), and others (e.g., Goom & Pope, 2017; BMJ Best Practice, 2016; Nsitem, 2013; Medscape, 2015; Physiopedia, n.d.) identified many potential diagnoses.

Given the welter of possibilities and the inability to assess them without the aid of an MRI machine, I sympathized with the statement, by McCrory et al. (2002), that “Even for an astute clinician, distinction between the different medical causes may be difficult given that many of their presenting features overlap.” Nonetheless, at least the ones listed did not seem to fit very well with my impression of my problem. Note that I did not attempt a complete catalog of the maladies that may affect runners’ calves. This was just a summary and response to those that came up during my browsing.

  • Stress fracture. There were two lower leg bones. The tibia (i.e., shin bone) was larger and located at the anterior medial side of the leg. (Anterior = front, as opposed to posterior, rear; medial = middle, inside, where the legs rub together, as opposed to lateral, outside, where the vertical stripe on a uniform would be.) The fibula was buried in the center of the leg, somewhat lateral and posterior to (i.e., outside and further back from) the tibia. Apparently the tibia and the fibula were both capable of sustaining stress fractures. OrthoInfo (2007) said stress fractures resulted from overuse — from, that is, continuing to engage in an activity “when muscles become fatigued and are unable to absorb added shock . . . often the result of increasing the amount or intensity of an activity too rapidly . . . [or] by the impact of an unfamiliar surface . . . [or] improper equipment.”
  • Medial tibial stress syndrome (i.e., shin splints). Runner’s World (n.d.) said these, too, tended to result from increasing mileage too rapidly or abruptly changing an established workout regimen.
  • Metabolic bone disease. Wikipedia characterized this as an umbrella term for a spectrum of disorders, most commonly resulting from abnormalities in levels of key minerals (e.g., calcium, phosphorus, magnesium, vitamin D).
  • Arterial endofibrosis. A rare condition, with 90% of cases arising in the external iliac (i.e., groin) artery, occurring most often in the left side for competitive cyclists, in which pedaling eventually lengthens the artery and then causes it to kink or harden, resulting in weakness, cramping, and/or pain during maximum exertion (Fredericson & Tenforde, 2015, p. 103; Briscomb, n.d.).
  • Saphenous nerve neuropathy. The saphenous nerve was a cutaneous (i.e., skin-oriented) sensory (i.e., not motor) nerve, running from the upper leg to the foot (Wikipedia). Damage to this nerve could result in anything from minor numbness to severe pain. Such damage could be caused by surgery (as in e.g., fasciotomy to relieve compartment syndrome; see Pyne et al., 2003) or entrapment syndrome.
  • Popliteal artery entrapment syndrome. A rare condition (estimated 0.16% of population), existing from birth or developed over time, especially afflicting male athletes under 30, in which enlarged calf muscles compress the popliteal artery — that is, the main artery for the lower leg. Symptoms include aches, numbness, fatigue, and/or cramping in the calf, sometimes with swelling, arising at the same point (i.e., distance, time, level of exertion) in exercise, and fading a few minutes after exercise. See Cleveland Clinic; Wikipedia. Not to get ahead of the story, but this condition seemed most likely to involve the medial head of the gastrocnemius muscle (Wikipedia).
  • Adventitial cystic disease. According to the Cleveland Clinic (n.d.), this was a rare, overwhelmingly male (generally young to middle-aged) condition in which a cyst would form in an artery (especially the popliteal artery) and block blood flow. Symptoms would include the symptoms of popliteal artery entrapment syndrome (above), along with leg pain or heaviness that would remain for up to 20 minutes after the end of walking or other exercise.
  • Popliteal artery occlusive disease (PAOD) and peripheral arterial disease (PAD). Medscape (Shortell, 2017; Dominguez, 2016) and other sources did not make clear whether these two diagnoses were identical, related, or distinct. For example, in her article on PAOD, Shortell made several remarks about PAD, suggesting it was the same as PAOD. Either way, the general concept seemed to be that ischemia (i.e., insufficient blood flow) due to occlusion (i.e., blockage) could cause claudication (i.e., pain and/or cramping due to inadequate blood flow). According to the National Institutes of Health (NIH, 2016) and the Mayo Clinic (n.d.), the occlusion would usually be caused by atherosclerosis (i.e., the buildup of plaque) inside an artery, and it could be severe enough to result in gangrene and amputation. People especially at risk included the elderly, smokers, and those with cardiovascular diseases. Dominguez (2016) distinguished PAOD from several other maladies discussed here, and also from venous disease (characterized by dull ache at day’s end, not exacerbated by exercise), reflex sympathetic dystrophy (often related to a past trauma in the leg), and diabetic neuropathy.
  • Intermittent claudication. As just indicated, claudication was a symptom, not a disease. Following the lead of the Mayo Clinic, I discuss it separately, here, for clarity. Sources distinguished chronic from acute claudication: the former would continue even when the person was at rest, and could include skin that looked bluish or felt cold; while the latter, more commonly called intermittent claudication, would tend to occur only during exercise. WebMD (n.d.) described the pain of intermittent claudication as a “tight, aching, or squeezing [or, according to the Mayo Clinic, weakness or burning] pain in the calf, foot, thigh, or buttock that occurs during exercise,” usually occurring after the same amount of exercise. That is, more strenuous exercise would tend to bring on the pain more quickly. WebMD said, “The average person with blockage of one major arterial segment in a leg can walk 90 to 180 meters (a football field or two) before pain starts.”
  • Popliteal artery aneurysm. The University of Virginia (UVA) Heart & Vascular Center, n.d.), described an aneurysm as an outward bulge in the wall of an artery. The risk was that the weakened artery would rupture, introducing a blood clot that could require an amputation and/or potentially fatal bleeding. A popliteal aneurysm was a risk factor for those who smoked, had high cholesterol or blood pressure, had a bacterial infection, or had a previous blood-vessel reconstruction. If there were any symptoms, they would typically include pain behind the knee, edema (i.e., fluid buildup) in the lower leg, foot pain, or foot ulcers that did not heal.
  • Popliteal artery dissection. UVA (n.d.) noted that arteries (including the popliteal) can be described as “dissected” when damage to their inner lining allows blood to separate their inner and outer layers, making them prone to burst. Ansari et al. (2016) said the cause of (in their case, abdominal) arterial dissection was not certain, but that it had been linked with a variety of conditions (e.g., hypertension, trauma, elastic tissue disorders).
  • Entrapment syndromes generally. Medscape (Hollis, 2017) observed that the saphenous nerve was but one of many leg nerves that could become entrapped. For example, tarsal tunnel syndrome could result in heel pain. McCrory et al. (2002) proposed that dysfunction of the fascia (i.e., the fibrous tissue forming four compartments in the lower leg; see below) could be responsible for a variety of situations in which muscles, arteries, or nerves could be trapped and compressed, impairing their functioning.
  • Deep vein thrombosis (DVT). According to the Mayo Clinic (2017), DVT could feature cramping or soreness, often starting in the calf; leg swelling; red or discolored skin; a feeling of warmth; or no symptoms at all. DVT would be caused by a blood clot that could break loose, float away to your lungs, and kill you. Often, it resulted from sitting or lying still for a long time (e.g., after a long plane flight, after surgery, during a long sickness), though there were many other possible causes (e.g., pregnancy, birth control pills, obesity, smoking, cancer, bowel disease, age over 60). Warning signs could include chest discomfort, dizziness, shortness of breath, and rapid pulse (tachycardia). DVT could be impossible to detect without an MRI, ultrasound, blood test, and/or venography.
  • Neoplasm. Definition: a new and abnormal growth of tissue in some part of the body, especially as a characteristic of cancer. A search led to indications that growths could appear throughout the lower leg, in or adjacent to bones, muscles, and tendons. The University of Rochester (n.d.) divided the possibilities into four groups: benign and malignant, appearing in bones or soft tissue. Generally speaking, those possibilities occurred in young people; appeared in specific (not necessarily relevant) locations (e.g., thigh); involved a mass (e.g., lump) or swelling; grew aggressively; and/or resulted in consistent pain, a fracture or other bone dysfunction, or otherwise became obtrusive.
  • Infections. Sources indicated that this bone infection could originate in an open injury to the bone, an infection elsewhere in the body (e.g., pneumonia, urinary tract), or a chronic open wound or soft tissue infection. In adults, osteomyelitis was found most often in the vertebrae and pelvis. Risk factors included old age, intravenous drug use, sickle cell disease, weakened immune systems, hemodialysis, and diabetes. Symptoms could include pain, tenderness, swelling, or warmth in the infected area; fever, nausea, or general discomfort or ill feeling; limping; and (in the case of open sores) draining of pus through the skin.
  • Myopathy. Wikipedia said that a myopathy was “a disease of the muscle in which the muscle fibers do not function properly.” Symptoms included muscle weakness, cramps, and stiffness. Myopathies could be caused by, or related to, a variety of inherited or acquired conditions and diseases (e.g., endocrine, inflammatory, infectious, metabolic, mitochondrial, drug-induced). Medscape (Bethel, 2016) said that symptoms of a myopathy could include muscle weakness, malaise or fatigue, dark-colored urine, fever, and/or scaly areas at joints, among others. As an example of one such myopathy, Medscape (Kedlaya, 2015) said that muscle cramping was one symptom of hypothyroidism.
  • Dystonia. Cutsforth-Gregory et al. (2016) described an uncontrolled muscle contraction causing abnormal postures that occurred, rarely, in distance runners and others who regularly engage in cycling, elliptical training, and other repetitive lower-body exercise. Most frequently, in the 20 cases they examined (mostly aged 40-70), the disorder manifested in an unwanted, persistent bending of the foot inward or downward (i.e., toes pointed). In most cases, as one would expect, this symptom eventually impaired the ability to walk.
  • Complex regional pain syndrome. The National Institute of Neurological Disorders and Stroke published a Complex Regional Pain Syndrome (CRPS) Fact Sheet. This webpage described CRPS as a pain condition, lasting more than six months, usually arising after an injury, usually affecting just one limb, resulting in prolonged, severe pain (often described as a burning or pins-and-needles sensation) and changes in skin color, temperature, and/or swelling. Often, there would also be high sensitivity, such that normal contact with the skin would be very painful. The peak age for CRPS was 40. It was rare in children under 10 and in the elderly.

In most of the foregoing diagnoses, my situation simply did not seem to match with the causes and/or symptoms just described. Among other things, I did not seem to have an infection, a tumor-like mass, swelling, weakness, cancer, venous plaque, or prior trauma; my pain was not constant, but rather was related directly to the act of running; I didn’t have the sick feeling of a loss of body integrity that I had noticed with previous bone breaks; the pain was not in the expected place (i.e., in my calf), but was instead said to appear in other places (e.g., shin, ankle, thigh, behind the knee); the pain did not consistently arise at a relatively consistent point during exercise (e.g., after a few minutes of running); and/or I was not the right age. There did seem to be at least a possibility that a few of these diagnoses might apply to me, but the connection seemed weak enough that I was inclined to exhaust other possibilities first.

Tendinopathy

For my purposes, it was relatively easy to dismiss most of the foregoing possible diagnoses. But a few others called for a closer look, starting with tendinopathy.

MedlinePlus (2016) and Wikipedia explained that both ligaments and tendons were fibrous tissues, made mostly of collagen, that tied certain body parts together. The difference was that a ligament would connect one bone to another bone. For example, the anterior cruciate ligament (ACL) connected upper and lower leg bones at the knee. By contrast, a tendon would connect a muscle to a bone or to some other structure (e.g., the eyeball). The tissue connecting bone to tendon or ligament was called the enthesis (plural entheses). Researchers observed that some tendons could stretch; for example, the Achilles tendon seemed to add a springlike energy to the stride. To the extent that tendons were able to provide elasticity needed for various motions, it appeared that muscles were spared from having to stretch; apparently this helped them to generate more force.

Wikipedia said, “As of 2016 [tendinopathy] is poorly understood . . . there are several competing models, none of which had been fully validated or falsified.” Under the “tendinopathy” umbrella term, the Cleveland Clinic (2016) distinguished tendinitis, involving “an acutely inflamed swollen tendon that doesn’t have microscopic tendon damage,” from tendinosis, which involved “a chronically damaged tendon with disorganized fibers and a hard, thickened, scarred and rubbery appearance.” In tendinitis, the focus was on inflammation; in tendinosis, it was on degeneration.

Bass (2012) said that tendinitis typically resulted from heavy or sudden overload, while tendinosis was a matter of chronic overuse. She said that, typically, the tendon was twice as strong as its associated muscle; therefore, injury to the tendon (rather than to the muscle) would suggest that the tendon must have been greatly weakened. In her argument, tendinitis tended to be secondary to tendinosis. The practical difference was that treatment for tendinitis would merely seek to reduce inflammation over a period of up to six weeks, while tendinosis rehabilitation would take three to nine months.

Tendon rupture (also called tendon tear) could apparently occur without prior tendinopathy. A search led to various indications (by e.g., Wikipedia, eMedicine) that this would most commonly occur during sports activity, especially when attempting explosive acceleration (e.g., pushing off, jumping), but could also result from direct trauma, from other atypical motions (e.g., twisting, jerking, stumbling, falling), from simply using the tendon after a long period of inactivity, and also from certain medications (notably quinolones) and illnesses (e.g., arthritis, diabetes).

This image from Radsource (Bodor, 2016) showed a cross-section of the two largest muscles of the calf — the gastrocnemius and the soleus — and their tendons (in white), with particular focus on the broad, flat kind of tendon known as an aponeurosis:

According to O’Rahilly et al. (2008), “gastrocnemius” (commonly shortened to “gastroc”) is a combination of the Latin terms gaster (“belly”) and kneme (“leg”), while soleus is the Latin word for a type of flat sandal. As shown here, a single tendonlike feature starts out as the anterior (i.e., front) gastroc aponeurosis, goes down to become a part of the posterior (i.e., rear) soleus aponeurosis, and ends as the Achilles tendon.

My searches for tendinopathy related to these features yielded some discussions of gastrocnemius tendinopathy, and many pages on Achilles tendinopathy, but virtually nothing on soleus tendinopathy. It appeared that “gastrocnemius tendinopathy” referred to problems with the tendons at the upper end of the gastroc, and that “Achilles tendiopathy” referred to problems with the (Achilles) tendon at the lower ends of both the gastroc and the soleus. It seemed that most references to the soleus tendon were atypical if not confused references to the lower (i.e., Achilles) tendon. If the tendon at the upper end of the soleus rarely had problems, presumably that was because stress on the soleus would be absorbed or mitigated by the Achilles, the gastroc, and the soleus itself, leaving the (upper) soleus tendon mostly unscathed.

My pain was not behind the knee. That ruled out the gastroc tendons. For problems with the Achilles, a search led to articles by MedlinePlus (2016) and the Cleveland Clinic (2017) indicating that causes could include sudden increase in activity (e.g., running notably longer distances); sports that have quick starts and stops; bad footwear; running too often, or on hard surfaces, or uphill, or on uneven ground; tight calf muscles; flat arches; heel spurs; and not warming up before exercise. Symptoms could include swelling or pain in the back of the heel, limited range of motion in the ankle, lower leg weakness or pain, stiffness especially in morning, bad pain the day after exercising, and pain when climbing stairs or going uphill.

Sources generally seemed to agree that Achilles tendon problems would tend to be manifested below the calf muscles. That was one reason why I ruled it out in my case: my pain was squarely in the calf muscles, much closer to the knee than to the ankle. As with the soleus tendon, it seemed the upper Achilles and particularly the aponeuroses were generally not problematic.

I also ruled out the Achilles because some of the symptoms seemed directly opposed to what I was experiencing. I noticed, in particular, that running uphill was the one kind of running that never resulted in serious calf pain. If anything, running uphill felt like therapy: it often seemed to reduce calf tightness or soreness. Also, I did not have pain when climbing stairs; the pain was never worse the next day; and I did not have “a slow progression of pain” (AOFAS, n.d.).

Chronic Exertional Compartment Syndrome (CECS)

Compartment syndrome was mentioned by many, and favored by several, of the sources I reviewed (e.g., Parker, 1996; PerformancePlace, n.d.). The general idea was that calf pain was due to the expansion of a muscle during exercise, as the muscle filled with blood, to the point that the limited size of the “compartment” containing that muscle would interfere with normal muscle functioning. According to Tucker (2010), “Muscle volume can increase up to 20% of its resting size during exercise.”

As shown by this diagram from AAOS (2009), there were four muscle compartments in the lower leg: anterior (i.e., up front, by the shin), lateral (on the outer front side of the leg), deep posterior (in the vertical center of the leg, immediately behind the bones), and superficial posterior (at the rear of the leg). Compartment walls consisted of “fascia,” which WebMD (2016) described as “[s]trong webs of connective tissue.” Duke University School of Medicine indicated that the large muscles of the lower leg (notably, the gastrocnemius and the soleus) were in the superficial posterior compartment.

Acute vs. Chronic CS

Compartment syndrome (CS) could be either acute or chronic. Medscape (Rasul, 2017) said that acute CS would typically follow a traumatic event, especially a fracture. Somewhat like crush syndrome, the trauma would impair blood flow through the muscles in a compartment. Often, this impairment would be limb- and even life-threatening. The standard response to acute CS would be a fasciotomy (i.e., relieving pressure by cutting the fascia that formed the affected compartments). In a study of 36 patients who underwent acute compartment fasciotomies, Heemskerk and Kitslaar (2003, p. 747) found that 45% of patients recovered from surgery with good limb function, 27.5% kept their leg with reduced function, 12.5% underwent amputation, and 15% died.

Chronic (i.e., ongoing) CS was similar to acute compartment syndrome, in the sense that it would entail constriction of blood flow, but the constriction was not so extreme; hence, chronic CS was not a matter of emergency medicine. Chronic CS would commonly result from exercise, and was thus often referred to as chronic exertional compartment syndrome (CECS). WebMD (2016) elaborated:

[B]lood or . . . [fluid] may accumulate in the compartment. The tough walls of fascia cannot easily expand, and compartment pressure rises, preventing adequate blood flow to tissues inside the compartment. . . .

[C]hronic compartment syndrome develops over days or weeks. Also called exertional compartment syndrome, it may be caused by regular, vigorous exercise. The lower leg, buttock, or thigh is usually involved. . . .

Symptoms of chronic compartment syndrome . . . include worsening aching or cramping in the affected muscle (buttock, thigh, or lower leg) within a half-hour of starting exercise. Symptoms usually go away with rest, and muscle function remains normal. Exertional compartment syndrome can feel like shin splints and be confused with that condition.

Tucker (2010) cited fascial defect as an alternate, related diagnosis. The concept here was that there could be a hole or weak spot in the fascia, allowing muscle to bulge through and resulting in nerve compression. But I, myself, did not have the pain radiating to the foot that Tucker said would typify that malady.

Prevalence of Superficial Posterior CECS

CECS appeared to be fairly rare. Orlin et al. (2016) contended that “a large proportion of those presenting with muscular pain actually have [chronic compartment syndrome].” Yet this conclusion was possible only through relaxation of the diagnostic standard; none of their study participants’ legs had compartment pressures meeting the conventional standard. As Orlin et al. acknowledged, the symptoms for patients without markedly elevated compartment pressure could be “very mild.”

During a period of eight years (2003-2010 inclusive) when an estimated four million Americans served in the U.S. military (see Pew Research Center, 2011; the average number of Americans in uniform at any specific point was apparently about 1.4 million), Waterman et al. (2013) found a total of only 611 service members who underwent fasciotomies for chronic CS in any lower leg compartment. Elsewhere, acknowledging that military service members constituted “an idealized subset at risk” of CECS, Waterman et al. (2013) found an incidence rate of about one case of CECS per 2,000 person-years.

Among the few who did suffer from CECS, only a small fraction involved the posterior compartments. A glance at the AAOS diagram (above) showed why: the anterior compartment was especially small and tightly bound. Various sources (e.g., Gross et al., 2015; Duke Medicine) considered CECS rare to nonexistent in the superficial posterior compartment, where the big calf muscles were.

For that matter, CECS hardly seemed to occur in the deep posterior compartment. Over a 3.5-year effort to sign up study participants at the second-largest medical center in a region comprised of nearly three-quarters of a million inhabitants, Winkes et al. (2016) diagnosed only 91 individuals with deep posterior CECS (dp-CECS). In a study of 36 patients with CECS, Edmundsson et al. (2009) found only four who appeared to have compression in both the deep posterior compartment and the anterior compartment; none with compression only in the deep posterior compartment; and none (or perhaps one — the account is unclear) with compression in the superficial posterior compartment. Among the 611 U.S. military CECS patients identified by Waterman et al. (2013), only 19.4% of fasciotomies involved an unspecified (but apparently the deep) posterior compartment, along with the anterior compartments, and only 2.2% involved a posterior compartment without an anterior compartment.

Fasciotomy Outcomes

I ran a search to learn more about fasciotomy outcomes. Starting with articles already cited (above), I saw that, among Waterman’s et al. (2013) 611 U.S. military CECS patients, many experienced less-than-ideal post-fasciotomy outcomes: for 45%, CECS symptoms recurred; 28% were unable to return to full duty; 16% had surgical complications; 6% underwent surgical revision (i.e., one or more additional surgeries to reduce scar tissue or otherwise clean up undesirable aspects of the previous surgery); 17% were ultimately referred for medical discharge from the military due to continuing CECS rendering continued service infeasible; and only 14% experienced complete recovery.

In an article published about the same time as (and not citing) the work of Waterman et al. (2013), Winkes et al. (2013) contended that prior research was of poor quality, for purposes of determining the effectiveness of fasciotomy for deep posterior CECS (dp-CECS). Winkes et al. acknowledged that the previous literature concluded that “outcome for dp_CECS is traditionally considered unpredictable.” For example, Edmundsson et al. (2009) found that, of 57 legs on which fasciotomies were performed, only 41 (72%) yielded outcomes that could be considered good or excellent.

In evaluating prior studies, Winkes et al. (2013) were willing to consider only seven (26%) of 27 prior papers; they excluded Edmundsson’s research from consideration on grounds that it was not specifically oriented toward dp-CECS and did not state postoperative outcomes with sufficient clarity. I appreciated that, for legitimate reasons, one could select criteria that would exclude most prior research. Aweid et al. (2012, p. 356) agreed that “the quality of [prior] studies was generally not high.” Nonetheless, it seemed glib to claim, as Winkes et al. did (p. 5), that “Surgery for most types of CECS . . . is successful” when Edmundsson et al. reported that, post-surgery, one-third of patients still had pain during exercise.

In subsequent work, Winkes et al. (2016) performed fasciotomies and studied outcomes for 44 athletes diagnosed with dp_CECS. Winkes et al. (p. 1) claimed that, “Based on their outcome, 76% of [those] patients would opt for surgery again.” But given the alleged precision of this team’s work, I was disappointed to see that the details of this post-operative survey were not provided. It seemed fair to wonder whether the outcomes had been in any sense skewed, intentionally or otherwise, given the admission (p. 2) that Winkes himself had performed more than 500 fasciotomies, including these 44. Bias is a widely recognized and significant risk in most varieties of research (e.g., Pannucci & Wilkins, 2010). It would be expected that many people in such a position would interpret evidence in ways supportive of their own choices.

Winkes et al. (2016, p. 5) said that, as of May 2015, 37 of the 44 patients had been out of surgery for more than a year (median = 26 months), and at that point were asked about four topics: their surgical complications, time to full recovery, time to return to sports, and residual symptoms. Two of the 44 did not respond to contact attempts. It was not clear why Winkes et al. did not wait to administer these questionnaires to the remaining five patients, nor why three others were not included. Of the 34 whose long-term reports were used, only 12% reported excellent results. Another 35% reported good results, and 24% reported moderate results, leaving 18% reporting only fair results and 12% reporting poor results (total = 101%; presumably rounding error). Only 29% returned to their preinjury level of sports activity; 47% were able to exercise only at a lower level, and 23% ceased to be engaged in sports. Wilkes et al. did not explain how questions about those four different topics (e.g., surgical complications) were combined to produce those simple percentages, nor why patients would be asked for a subjective evaluation of, say, their time to full recovery, instead of specifying a number of months. Winkes et al. (p. 4) arbitrarily decided that patients who did not rate the results of their fasciotomies as either excellent or good — specifically, those who rated the results as only moderate — would nonetheless be considered part of “the success group.” Lavery et al. (2017) did not share that enthusiasm. Even then, such a claim implicitly acknowledged that fasciotomy was a failure for at least 30% of these carefully selected patients.

Packer et al. (2013) compared outcomes for 71 fasciotomy patients against those of 27 patients given nonsurgical treatment. The former reported higher success (81% vs. 41%) and satisfaction (81% vs. 56%). Contrary to some reports, the measured pressure within the targeted compartment did not correspond to the degree of operative success. What did matter was choice of compartment and age of patient: failure rates were 0% for fasciotomies limited to the anterior compartment, but 31% for fasciotomies on both the anterior and lateral compartments; and satisfaction rates were 89% for high school-age patients, 94% for college patients, but only 66% for post-college patients.

Pasic et al. (2015) reported results from fasciotomies on 46 patients. The authors found that 11% of patients required a revision fasciotomy. In long-term follow-up (average = 55 months), 78% reported being satisfied or very satisfied with the results of the surgery. Patients also provided high ratings regarding their ability to return to sport and to pre-surgery activity levels generally; 76% reported that their expectations were met; 87% said that, with the benefit of hindsight, they would choose the surgery; and 91% said they would recommend it to others. Unlike some other studies, Pasic et al. found that dp-CECS patients were just as satisfied as the those without dp-CECS. The authors credited this to the use of a surgeon experienced with this procedure. But there was one odd thing in the Pasic et al. (2015) report: an indication that, among those 46 patients, with a total of 80 legs having one or more affected compartments, there were 42 legs with superficial posterior CS. I had encountered no other study suggesting that more than half of studied patients experienced sp-CECS. I noticed, too, that Pasic et al. (p. 710) claimed that exactly the same number (i.e., 42) also had dp-CECS. Likewise, Pasic et al. said that 80 legs had anterior CECS, and also 80 legs had lateral CECS. The article did not seem to explain these numbers.

Reading these research articles, I felt myself drawn somewhat to the medicine man hypothesis: what he believes may not be as important as how good he is at it. Having become personally acquainted with the possibility of a poor surgeon, I was willing to contemplate that maybe fasciotomy was a delicate matter, involving deep meddling into one of the most important things you will ever own, and maybe the Army was just not the best place for that sort of thing. As Lavery et al. (2017) put it,

Historically, deep posterior fasciotomy has resulted in consistently poorer surgical results than anterior and lateral release, with success rates reported from 30% to 65%. . . . The reason for less predictable outcomes after the surgical treatment of deep posterior CECS is unclear. Causes may be attributed to improper diagnosis, treatment, or both. . . . [T]he clinical presentation of deep posterior CECS can be vague, often consisting of nonspecific pain or cramping. The extensive differential diagnosis combined with an often nebulous presentation, lack of physical findings, and unreliable objective diagnostic testing results in the increased potential for misdiagnosis or unrecognized concomitant pathology. There is also a lack of consistency among surgical techniques . . . . [I]t is clear that posterior fasciotomy presents a more challenging surgical dissection than anterior and lateral releases.

Perhaps it wasn’t surprising that even these supposed wizards of the process seemed to be turning out rather alarming failure rates. This was not like getting a tooth filled. Those who have witnessed plastic surgery gone wrong may share my sense that some might want to consider alternative approaches (e.g., Isner-Horobeti et al., 2013).

Ruling Out CECS for Me

In the first draft of this post, I came rather quickly to the conclusion that I probably didn’t have CECS. But when I revisited the matter, I decided that this was the point at which I should explore the calf’s structures in more detail. It also seemed, upon review, that before proceeding in other directions, I should have a good sense of how strongly I was going to resist CECS as a possible diagnosis. The foregoing exploration made me pretty firmly inclined to explore other possibilities first. That inclination was consistent with Tucker’s (2010) advice to consider other diagnoses because detection of compartmental pressure buildup would require invasive measures. I was even more doubtful of the CECS concept after reviewing Tucker’s indication that (at least as of 2010) experts disagreed as to what was actually happening in CECS.

Some of the arguments against CECS have already come up. For one thing, CECS often felt like shin splints because 95% of cases of CECS involved the small forward (i.e., anterior and lateral) compartments of the lower leg (Tucker, 2010). Even when the pressure was in the deep posterior compartment, the pain was evidently most noticeable up front. Winkes et al. (2013, p. 7) characterized medial tibial stress syndrome (MTSS) as “the greatest mimicker of dp-CECS” because “a substantial portion of patients with dp-CECS do demonstrate signs associated with MTSS such as distal tibial bone tenderness.”

In other words, it seemed that, even within the minority of a minority that had CECS in the deep posterior compartment, very few would have calf pain without also having shin or other anterior pain. Since I did not have shin pain, this seemed to be an argument against a diagnosis of dp-CECS in my case. Superficial posterior (i.e., sp-CECS) seemed to be virtually nonexistent, for a logical reason. When you exercise your calves, they get bigger. The soleus and gastroc are not locked into a compartment; they are able to expand outwards. No doubt smaller muscles in other compartments could develop too, but they would tend to result in pain up front, and I wasn’t having that. Besides, I was getting this pain early on, when my muscles were relatively undeveloped, after taking time off from running. If anything, I felt that the calf problem diminished as my legs became more conditioned.

And then there was the fact that I was an older runner. According to the Mayo Clinic (2017), CECS was most common in people under 30. At my age, the problem was not that muscles were swelling out beyond the city limits; it was that muscle would tend to shrink. As far as I could tell, this was a case of surplus storage room, where my leg compartments and I were waiting and hoping that those muscles would come back and take up residence once again. Compression? Probably not.

Another classic sign of CECS, according to Lavery et al. (2017): “Symptoms occur after a predictable duration and intensity of exercise.” Bonasia et al. (2015) and the Mayo Clinic (2016) said the symptoms would start, each time, after about the same time, distance, or intensity of exertion, and would subside within 10-20 minutes after stopping. Mine was not a gradually increasing pain or discomfort. It actually had two parts. There was an enduring ache that might come and go at various times during a run; and then there was a sharp pain that could come on quite suddenly, at any point during a run (although especially when I was first starting out, especially if I did not take a warmup walk or bike ride first), and could also go away very quickly, almost as soon as I stopped running.

Those sources also said that the symptoms in question could include aching, burning, cramping, tightness, numbness, tingling, or weakness (e.g., “floppy foot”). That made sense, if the problem did involve a cutoff of blood to the muscles. But as noted in connection with other possible diagnoses (above), I did not have most of those symptoms, and the symptoms I did have were not spread across an entire posterior compartment. I would find no pain, swelling, or discoloration if I probed with a firm finger anywhere in my calf, except in the one specific spot where I felt the dull ache or the sharp pain.

Historical Review of Muscle Injury Grading

I started this post with a belief that I had a muscle problem. I went through a number of other possibilities, involving other leg components (e.g., bones, tendons, compartments), to make sure I wasn’t overlooking something. I hadn’t gotten into those alternative diagnoses in great detail, so it was still possible I had missed the real explanation, but now at least I could have some confidence that the muscle focus made sense.

In looking at those other possible diagnoses, I had been pretty much on my own. I had found several lists of things that could cause calf pain, but there was no real structure or organization to those lists; they were just haphazard collections, most of which mentioned some but not all of the things that appeared on other lists. It was actually kind of crazy that people had been having problems with legs for as long as there had been people, and yet it seemed nobody had sat down and come up with an organized plan or flow chart that would take you through the options.

Now that I was in a position to focus on muscle problems, I sympathized with Hamilton et al. (2014) when they bemoaned “the lack of a uniform approach to the categorisation and grading of muscle injuries.” But here, at least, people had tried to come up with an organized system. Hamilton et al. offered a brief review of efforts, especially during the past half-century, to classify muscle injuries and to grade their severity. Having seen so many different alleged classifications of injury, it seemed advisable to try to understand what Hamilton et al. were saying.

Based on a substantial historical literature review, Hamilton et al. (2014) Supplementary Table One offered a remarkable chronology of attempts to classify and grade muscle injury, from Marsh (1896) to Pollock et al. (2014). I was particularly interested in that list because Hamilton et al. included what appeared to be the key classificatory terms used by those sources. For example, Heald (1931) was the first listed source to use the word “strain” to describe a kind of muscle injury. I was particularly interested in that word because I wanted to verify that it was a synonym of a muscle “pull” or “tear,” as WebMD (2016) and Wikipedia indicated. Generally, the listed sources did seem to treat muscle pull, strain, and tear as synonymous. As I was about to see (below), the Munich Consensus Statement (Mueller-Wohlfahrt et al., 2012) recommended not using “strain,” because that term “is used with a high degree of variability between practitioners,” preferring “tear” instead.

From that literature review, Hamilton et al. (2014) posited a Clinical Era (roughly 1900-1980) in which clinicians indirectly evaluated the degree of muscle damage according to symptoms. For example, Featherstone’s (1957Sports Injuries: Their Prevention and Treatment (pp. 31-34) used the knee to illustrate the desired clinical method: start by taking a history of what has been happening; examine for visible signs (e.g., swelling, bruises); identify what is painful by probing and by having the patient move it; conduct diagnostic tests (e.g., “spring” the knee by bending it slightly in ways it was not meant to go, so as to stretch the suspected ligaments); and examine the “voluntary, passive, and resisted movement” of related muscles (e.g., quads).

Whatever the merits of such procedures, Hamilton et al. (2014) said that, during the Clinical Era, there was virtually no research linking the clinician’s observations to specific outcomes — and yet “historical (clinical) grading systems of muscle injury . . . have been recycled in various modified forms and continue to appear in the literature.” As an example, Hamilton et al. cited Maquirriain et al. (2007, p. 844, Table 1), who used a pain-based clinical grading system for strains of the rectus abdominis muscle proposed by Lehman (1988). The point appeared to be that nobody had established that pain levels had anything to do with how long it would take to recover, or how satisfactory the recovery would be.

Altogether, in a quick look at Hamilton et al. (2014) Supplementary Table One, aside from very simple distinctions (e.g., minor vs. severe), I counted a total of 28 different schemes by which to divide muscle injuries into (typically, three or four) grades, types, or degrees of injury. In that light, it was not surprising that I had encountered a bewildering assortment of muscle injury gradations in various webpages.

Hamilton et al. (2014) suggested that the Clinical Era was followed by the Imaging Era of the 1980s and 1990s, when ultrasound and MRI imaging facilitated direct viewing of muscle injury; but here, again, researchers generally failed to link such observations with actual outcomes. Hamilton et al. cited the exception of Pomeranz and Heidt (1993), who studied the correlation of injury size to progress during rehabilitation.

Finally, according to Hamilton et al. (2014), for present purposes the medical world entered the Modern Era (circa 2000-present), characterized by three key features:

  1. Accumulation of evidence demonstrating the extent to which various injury symptoms (i.e., the patient’s subjective experience, e.g., pain) and signs (i.e., outwardly observable indications, e.g., MRI imagery) were useful for predicting outcomes.
  2. Use of continuous variables. The focus here seemed to be on precision. If you have an MRI that can determine that one injury is 1.2 centimeters long and another is 2.4 centimeters long, you might be able to demonstrate that, say, an injury twice as large can require three times as long to heal. In addition, precise measurement eliminates the gray areas that can arise when, for instance, an injury is right on the boundary between so-called Grade 2 and Grade 3 injuries.
  3. Hamilton et al. said, “The past 5 years have seen a range of publications touting ‘new’ muscle injury classification and grading systems,” but only two provided supportive clinical data. Of those two, Hamilton et al. were particularly interested in the Munich Consensus Statement (MCS): they described it as the first time, in more than 100 years of muscle injury grading, when large amounts of data were being used to test a system of classifying and grading muscle injuries.

Hamilton et al. (2014) concluded,

To date, there remains minimal pathological or prognostic validity to the majority of classification and grading systems utilised. . . . [I]t seems unlikely that any categorical grading of muscle injury severity will accurately predict an individual’s healing time. . . . [I]t is time to recognise the complexity of muscle injury.

In short, Hamilton et al. conveyed, to me, the impression that it could make sense to classify types of muscle injuries, but that simplistic and discrete muscle injury gradings were better replaced with continuous and nuanced analyses. As I was about to see, this impression would prove inconsistent with Hamilton’s later suggestions.

Differential Diagnosis via the Munich Consensus Statement

Since at least 2012, several authors (notably Hamilton, Valle, and Tol) have been prominent in the evaluation of proposed muscle injury classification systems. As just noted, Hamilton et al. (2014) considered the Munich Consensus Statement (MCS) (Mueller-Wohlfahrt et al., 2012) a step in the right direction. As described by Mueller-Wohlfahrt et al. (2013), the MCS arose from responses to questionnaires completed by 19 English-speaking scientists and team doctors of national and first-division professional sports teams, as evaluated by 14 sports medicine experts from a number of Western countries.

Context of the MCS

Recently, Valle et al. (2017) proposed an MLG-R system with the potential to rectify several problems that Tol et al. (2012) identified in the MCS. The letters in the name of this system referred to Mechanism of injury, Location of injury, Grading of severity, and (number of) Re-injuries. While Hamilton et al. (2017) did not evaluate this MLG-R system, they did convey several features of the MLG-R system that, to me, appeared problematic:

  • As its authors acknowledged, the MLG-R system so far had been developed only for use with hamstrings: it remained “only a theoretical model” that would require “[s]ubsequent studies . . . [and probable] modification . . . to include other muscle groups and validate its content.” There was no guarantee that its content would, in fact, be validated.
  • Hamilton et al. (2017) criticized existing systems (including the MCS) for failing to provide an effective prediction of when an injured athlete could return to play (RTP); and yet, in the end (for understandable reasons), the MLG-R writeup likewise offered only a hope that the MLG-R system would assist in RTP decisions.
  • While the MLG-R authors contended that their system offered “easy clinical application” for physiotherapists and trainers, the words of Hamilton et al. (2017) seemed to apply here as well: after the MCS, proposed classification systems had become “increasingly complex.” This was true particularly of the proposed injury severity grading. For instance, the MLG-R described a grade 3 injury in terms that would be “easy” only for trainers fluent in MRI-speak:

Any quantifiable gap between fibers in craniocaudal or axial planes. Hyperintense focal defect with partial retraction of muscle fibers ± intermuscular hemorrhage. The gap between fibers at the injury’s maximal area in an axial plane of the affected muscle belly should be documented. The exact % CSA should be documented as a sub-index to the grade.

  • The MLG-R system seemed to achieve a degree of simplicity primarily by dispensing with concepts that could help the clinician to zero in on the most likely diagnosis. As illustrated in my own case (below), these included the distinction between structural and non-structural disorders, and the possibility of neuromuscular disorders.

Among the muscle injury classification systems that had been developed to a relatively complete degree, Hamilton et al. (2017, Table 2) seemed to indicate that the MCS (Mueller-Wohlfahrt et al., 2012) offered the best available guidance, for purposes of achieving a practical, relatively simple differential diagnosis. (See also Grassi et al., 2016.) Indeed, rather than replace the MCS, it seemed that the MLG-R might complement it. The MCS offered someone like me some assistance in guessing how I might best proceed in my own self-treatment, as an alternative to the presently nonexistent option of sports medicine for less-than-wealthy residents in certain American jurisdictions.

MCS Top Levels: Direct vs. Indirect, Functional vs. Structural

As just described, I concluded that the Munich Consensus Statement (MCS) (Mueller-Wohlfahrt et al., 2012) offered helpful guidance for a runner seeking the guidance of leading clinicians on the question of what might be wrong with his calf.

Table 2 of the MCS started with the question of whether the injury was direct or indirect. For this purpose, “direct” meant either a contusion (most commonly a bruise) or a laceration (i.e., a cut or tear, from the surface of the leg down into the muscle). The MCS said direct injuries would be caused by external rather than internal forces — by, for example, a blow from an opponent’s knee or, for runners, a fall or a collision.

Plainly, the calf attacks I was experiencing were indirect injuries. In that case, the MCS offered a choice between functional and structural. Structural muscle injuries consisted of total or partial muscle tears. WebMD (2016) explained that symptoms of muscle or tendon strain — or tearing, to use the term preferred by the MCS — could include swelling, bruising, or discoloration; pain at rest; pain when using the related muscle or joint; weakness of the muscle or tendons; and/or inability to use the muscle.

Most of those symptoms did not apply to me. At times, I did have pain or inability when trying to use the specific muscle for running. In those instances, there might have been some tearing. But that wasn’t a core, consistent aspect of the problem. Therefore, I suspected that the calf attack was an indirect (not direct), functional (not structural) muscle disorder. MCS Table 3 said that MRI and ultrasound would see problems in direct muscle injuries, and also in the structural kinds of indirect injuries (i.e., muscle tears), but would not show anything (other than possibly finding some fluid buildup) for functional muscle disorders. That was the case for me: at one point, early on, I went for an ultrasound and a series of physical therapy sessions, but the therapy seemed ineffectual and the ultrasound showed nothing.

MCS Type 1 (Overexertion) and 2 (Neuromuscular) Disorders

Within the sphere of indirect, functional muscle disorders, MCS Table 2 (Mueller-Wohlfahrt et al., 2012) offered a choice: my muscle disorder was either Type 1 (overexertion) or Type 2 (neuromuscular). MCS Table 3 divided each of those into two subtypes. I started with a look at subtypes 1A and 1B.

Subtype 1A involved fatigue-induced muscle disorder. This appeared to be the simple and common muscle soreness and/or tightness that would occur during or shortly after strenuous activity, resulting in “dull, diffuse, tolerable pain.” Subtype 1B involved delayed-onset muscle soreness (DOMS), arising 24-48 hours after the activity ended. This, too, was familiar: it was the fatigue-induced soreness that a person might experience when s/he participates enthusiastically in some sporting activity, for the first time in a long time, and then awakens the next morning to discover sore muscles s/he didn’t even know s/he had. I had experienced both of these, but neither captured what was unusual and most problematic about the calf attack.

That left me with Type 2 disorders. These were described as “neuromuscular” because they involved not only the sore muscle, but also nerves related to it.

Ordinarily, it seemed, “neuromuscular disorder” would mean a serious disease. Among the many (often incurable) examples listed by MedlinePlus (2017) and Johns Hopkins (n.d.), I saw multiple sclerosis, Parkinson’s disease, and myasthenia gravis. But those were surely not the kinds of maladies intended by the MCS article (Mueller-Wohlfahrt et al., 2012), when it indicated that its concept of Type 2 disorders would be related to specific muscles. This was, after all, an article whose title referred to “muscle injuries in sport.” I inferred that, when the article spoke of neuromuscular disorders, it meant a type of problem that could be fixed or at least ameliorated, sufficient to allow the patient to return to some level of sporting activity.

In the MCS article’s subtype 2A neuromuscular disorders, the nerves in question were those of the spine, not of the calf. The spine could be implicated because, according to that article,

[T]heoretically any pathology relating to the lumbar spine, the lumbosacral nerve roots or plexus, or the sciatic nerve could result in hamstring or calf pain. . . . Thus, it is important that assessment . . . should include a thorough biomechanical evaluation, especially that of the lumbar spine, pelvis and sacrum.

Medscape (Shortell, 2017) said that spinal issues related to the lower leg could include pseudoclaudication, lumbar disc disease, and spinal stenosis. The MCS article said, “[B]ack injuries are very common in elite athletes.” I looked at the article they cited in support of that view. That article (Ong et al., 2003) examined 31 athletes treated for lower back pain and/or sciatica during the Sydney 2000 Olympic Games. Notably, that article said 21 of those 31 athletes were from track and field. In my brief glance, the article did not seem to specify how many of those might have been runners, but presumably some were: running was quite commonly associated with lower back pain.

The concept appeared to be that I might be able to probe deep into the calf muscle and identify the injured spot, and yet the actual (or at least primary) problem would be found in the spine. I could not absolutely rule that out. But, to my knowledge, I did not have back problems. Thus, before looking for spooky action at a distance of several feet away from the sort spot, it seemed advisable to make sure I had exhausted the remaining and, to my mind, more likely alternative.

The remaining alternative was subtype 2B. MCS Table 3 said that subtype 2B consisted of neuromuscular functional disorder related, not to the spine, but rather to the nerves in the calf itself. What I found particularly relevant, in Table 3, was that they said a subtype 2B disorder would involve “gradually increasing muscle firmness and tension,” along with “[c]ramp-like pain” extending across the entire muscle. That did describe part of what I was experiencing. They also said, “Therapeutic stretching leads to relief,” but in my experience that was not particularly true. Stretching the tight calf did not feel bad — it felt like something that it might be helping — but I had not yet found a form of stretching that seemed to have any significant effect on that tightness.

Understanding the Calf Muscles

At this point, I had exhausted the categories of disorder shown in Tables 2 and 3 in the MCS article (Mueller-Wohlfahrt et al., 2012). I had a clues that perhaps nerves in the calf were responsible for my symptoms, but I was not sure what to do with that. It seemed I would need to learn more about the operation of calf nerves and muscles. I started with the muscles.

Overcontraction in Antagonistic Muscle Pairs

The MCS article provided a useful starting point, for purposes of investigating learning more about MCS subtype 2B injuries. Specifically, I was interested in that article’s cryptic reference to muscle overcontraction:

Dysfunction of . . . neuromuscular control mechanisms can result in significant impairment of normal muscle tone and can cause neuromuscular muscle disorders, when inhibition of antagonistic muscles is disturbed and agonistic muscles overcontract to compensate this.

To understand that statement, I had to understand agonistic and antagonistic muscles. Wikipedia explained that the agonist muscle would be the one causing movement. In a dumbbell curl, for example, the elbow flexor muscle group (including the biceps) was the agonist: those muscles would curl the wrist back toward the shoulder. Meanwhile, the elbow extensor muscle (i.e., the triceps) was the antagonist. Antagonist muscles would also be active during a dumbbell curl, providing opposing force to help control the movement, and also returning the arm to its original (extended) position after the curl. Together, the flexor and extensor muscles (i.e., biceps and triceps) formed an antagonistic muscle pair.

Hence, the MCS quote seemed to be describing a dysfunctional situation in which the nerves would fail to restrain the antagonist muscle properly. It would be like driving while pressing both the gas pedal and the brake: the two would fight against each other in an inefficient and potentially destructive manner. Specifically, the antagonist muscle would not be properly inhibited — it would oppose the agonist muscle too strongly — and that would require the agonist muscle to overcontract (i.e., to work too hard) in order to complete the desired motion. In the dumbbell curl example, the triceps would impose excessive resistance, and the biceps would therefore have to work harder.

That might not seem like a bad thing in the case of a dumbbell curl. It might make the biceps stronger. But you’re not doing five thousand bicep curls within a single hour. If this was happening every time I took a step, at a rate of more than 1,400 steps per mile, it would be no surprise if the calf muscles started to degrade — resulting, as the quote says, in “significant impairment of normal muscle tone.” It seemed that, paradoxically, further exercise could actually make the affected muscle weaker, as its antagonist gradually wore it down.

In the upper leg, Elias et al. (2003) said, the hamstring muscles were agonists, and the quadriceps (quads) muscles were antagonists. The hamstring (on the back of the leg) would pull, to power a runner’s step. The quads would also pull slightly, to control the angle of hamstring pull during the step. Then, to return the leg to its original extended position, the quads would pull, and the hamstrings would help to control the angle. The quads and the hamstrings were on opposite sides of the leg, so it did seem reasonable that one would have to loosen up when the other tightened.

The quads and hamstrings would pull both the upper and lower sections of the leg. This was possible because, while those muscles were located on the upper leg, they (with their associated tendons) were long: they ran from above the hip joint to below the knee joint. So they were involved with bending at the hip as well as the knee.

The situation was somewhat similar for at least one of the largest calf muscles. As shown in this Duke Medicine image, the gastroc ran down from its two heads, above the back of the knee, to form the Achilles (calcaneal) tendon, which was attached to the back of the heel bone. Thus, just as the upper-leg muscles were involved in bending at both knee and hip, the gastroc was involved in bending at both knee and ankle.

The soleus was not like these other upper- and lower-leg muscles. For one thing, it was not on the opposite side from the gastroc, and thus did not operate as its antagonist. Also, according to Gray’s Anatomy for Students (Drake et al., 2009, p. 589), the soleus did not span the knee joint, but rather was anchored to the top ends of the lower leg bones, and thus did not play a role in knee bending. At its lower end, the soleus joined the gastroc in forming the Achilles tendon. Perhaps for that reason, as evidenced in numerous sources, some anatomists viewed the gastroc and soleus as forming, in effect, a single muscle, referred to as the “gastrocnemius-soleus complex” or (with the plantaris muscle) the “triceps surae” (e.g., Wikipedia). Or perhaps one could call it simply the gastroleus. One would not want to overstate the unity of these two, however; they were not simply identical or parallel. For instance, Suzuki et al. (2014) found that straightening the leg and pointing the toes would entail increased activity by the soleus but decreased activity by the gastroc.

Plantaris Tendon and Tennis Leg

The Duke Medicine image (above) shows the plantaris tendon. I looked into that briefly, while the image was fresh. Wikipedia said the plantaris (not found in an estimated 7-20% of the population, according to other sources) was a long, thin tendon with a relatively short (~4″) muscle, running from above the knee down to the heel.

The New York Daily News (Maharam, 2014) characterized the plantaris as “one of evolution’s leftovers,” a muscle whose former function of helping to point the toes has been taken over by other calf muscles. Maharam linked the plantaris with “tennis leg,” a frequent malady of aging (40+) athletes who get a sudden, sharp pain in the calf, akin to getting “shot with a BB gun” or, in other accounts, being kicked or hearing a “pop” in the calf. What causes rupture of the plantaris is, as one would expect, a motion that stretches it as much as possible: the leg is locked straight at the knee, and the foot flexes upward toward the shin.

Burdett (2006) said that “tennis leg” is a general term that could also refer to strain to the soleus, or to the medial (i.e., inner) head of the gastroc. (Note: in the Duke Medicine image (above), those are two right legs, not a right and a left. InnerBody offered a useful interactive graphic to clarify.) While Maharam (2014) said that the two ends of a ruptured plantaris would “shrivel up and go away — in a couple of weeks with a little physical therapy and warm water soaks,” Burdett remarked that gastroc and soleus injuries would generally be more severe, would take longer to heal, and could require splinting and dedicated rehabilitation.

Well. If Burdett was right, that would be one more way in which Indiana University screwed me, and it could explain why the calf pain that commenced during a run there in 2007 never went away: instead of getting the kind of proactive, sports-aware treatment (e.g., a doctor; an MRI) that a PhD student buying student healthcare at a Big Ten university might expect, I got inconclusive ultrasound and massage from a therapist. It was nice, as far as it went, but it didn’t help at the time and, as I say, the problem was still here. In Burdett’s (2006) words,

Plantaris tendon rupture and medial head of the gastrocnemius muscle rupture may also occur together, in which case MRI would demonstrate edema of the medial head of the gastrocnemius muscle, fluid between the soleus and medial gastrocnemius muscles, and a visible torn plantaris tendon. Visualization of the torn plantaris tendon is important, since fluid between the soleus muscle and medial gastrocnemius muscle is non-specific, and can be seen with plantaris tendon rupture, medial gastrocnemius muscle injury, or a ruptured popliteal cyst. The differential diagnosis of calf pain includes the more serious clinical entities of deep venous thrombosis (DVT) and compartment syndrome.

I mean, during the present writeup, when I saw the description of DVT (above), I did not have clinical grounds or medical opinion to tell me why I did not have it; I only had the fact that I wasn’t dead yet. There certainly had been times, in the intervening decade, when I would and possibly could have gotten an MRI scan, if I had thought it was anything more than just a generic sore calf. Now that I was aware that a calf injury could be life-threatening, of course, I did not have health insurance. If I did have DVT, then apparently it was another one of those things that I would just have to deal with.

In an article Burdett cited, Delgado et al. (2002) examined 141 patients diagnosed with “tennis leg,” using MRI scans, and evaluated the legs of four cadavers, to study the involvement of the gastroc and the plantaris tendon in that diagnosis. The authors concluded that plantaris tendon rupture was responsible for only 1.4% of cases, and partial soleus rupture was responsible for less than 1%. By far the dominant diagnoses were rupture of the medial head of the gastroc (67%), fluid collection between the soleus and medial gastroc aponeuroses (21%), and DVT (15%). In response to that last finding, the authors recommended routine examination of leg veins to rule out DVT in cases of tennis leg.

More recently, Spang et al. (2016, p. 1315) summarized literature finding that a small percentage (4-10%) of athletes sustained a plantaris injury each year, of which one-quarter were ruptures and the rest were tendinopathy; that running and jumping were the primary causes; and that ruptures require only a short period of rest before returning to full activity. Harwin and Richardson (2017) said that, even for gastroc rupture, surgery would only be indicated for tennis leg only when associated with compartment syndrome.

Tennis Leg and the Musculotendinous Junction

As I read various accounts of tennis leg, it was not always entirely clear which part of the calf they were talking about. This uncertainty or confusion was perhaps epitomized in a report by Nsitem (2013). That report said, “Muscle injuries in the calf are a relatively common clinical condition, and are also termed ‘tennis leg’ in general because of the prevalence in that sport.” Nsitem focused particularly on “the musculotendinous junction of the medial head of the gastrocnemius, and . . . the medial belly of the gastrocnemius just above the musculotendinous junction.”

As its name suggested, the musculotendinous junction was simply the place of connection between a muscle and its tendon (Oxford Reference). If Nsitem hadn’t referred to the gastroc “above” that junction, it might not be clear whether she was talking about the gastroc’s upper (proximal) or lower (distal) musculotendinous junction. But with that hint, it seemed plain that she was talking about the point where the gastroc transitioned into the Achilles tendon, as shown in this diagram (from an article focused on Achilles tendon injury) provided by Singapore Osteopathy:

 

It was confusing, though, when Nsitem said that she had measured the man’s calf swelling at a point just four inches below the kneecap. That’s about as high as you could go, to measure the calf, if the person was sitting. The answer seemed to be that his pain extended throughout “the entire medial gastrocnemius muscle.”

It seemed clear, in particular, that I was not experiencing so-called “tennis leg.” For instance, reported a classic case in which the injury to the medial head of the gastroc was measured at a distance of about four inches below the kneecap — well above the sensitive zone in my case. Similarly, De Cree (2015, p. 3) described a case of tennis leg in which “the entire upper and mid-portion of the right calf was found painful, tight and cramped up, with significant diffuse swelling, muscle weakness, and loss of range of motion.” (See also Bergman, 2013.)

Gastrocnemius Location and Functioning

I had concluded that the gastroc and/or soleus were not antagonistic to each other. But this was not to say that they had no antagonists. To identify their possible opponents, it seemed I would have to learn something about what those two muscles did. (In this exploration, by the way, it was interesting to glance at progress in developing mechanical models of human running.) Key terms here included dorsiflexion (i.e., bringing the toes closer to the shin, as when walking on one’s heels) and its opposite, plantarflexion (as in pointing one’s toes) — so named because the front side of the leg was its dorsal side, and the back side of the leg was its plantar side.

Starting at the top, the gastroc had two heads, medial and lateral. I had seen one or two non-expert sources describe those two heads as separate muscles. However characterized, there was the question of how they differed in function. My impression was that, as with other antagonistic muscle groups, they would have the capacity to pull the joint in slightly different directions — a little to the left, a little to the right — in concert with allied and opposing muscle groups.

As a knee flexor, in lay terms the gastroc was allied (i.e., synergistic) with the hamstrings and antagonistic to the quads (Wellness Digest, n.d.). This would suggest that the gastroc could be strained if the hamstrings were failing to counteract the quads sufficiently, either because the hamstrings were too weak or because the quads were too strong. Such reasoning, if correct, could raise a question of whether running — by itself, or in connection with general (e.g., otherwise sedentary) lifestyle factors — could result in imbalanced muscle development. Hypothetically, imbalance could be prevented if I had been spending the same proportion of my time running, walking, jumping, skipping, cycling, wrestling, and otherwise using a variety of leg muscles, as an adult, as I had spent when I was a kid. There was, in other words, a question of how much cross-training would be needed to restore balance, in the case of someone who spent hours running each week.

Again, that was all hypothetical. I could perhaps explore its relevance to me, personally, by investing some time in hamstring-strengthening exercises. But that sounded like a lot of work, I had no particular reason to think my hamstrings were atrophied, and there were other possibilities that, at this point, seemed likely to be closer to the mark.

If I quit running for a while and then resumed, I would usually have occasional minor aches and faint twinges around the knee. I assumed that was because the muscles and tendons and ligaments were all getting back in shape and learning to work together again. The aches and pains tended to go away after a while. Not to make too much of that, but my first guess would be that the knee and its attendant muscles were mostly doing OK.

I was not having much calf pain at this writing. But from memory and from the bit of pain that persisted, it seemed to me that my calf pain occurred along a line, perhaps the length of my index finger, starting in the center of the calf, or maybe a bit lower, and running down past the bottom of the gastroc bulge. I did not have the extremely clear muscle definition that I had seen in some pictures of calves, so I could not verify the conclusion visually, but it seemed probable that I was not having pain in either head of the gastroc. I was inclined to say, rather, that the location and the depth of the pain tended to rule out the gastroc, consistent with this great image from The Daily Bandha, incidentally showing the lesser calf muscles (right-hand image) anterior to the Achilles:

I was also inclined to doubt the gastroc was the primary issue after reading what Medscape (Saglimbeni, 2016) said about gastroc strain. He said gastroc pain, bruising, and swelling could radiate to the knee or ankle; there could be tenderness across the entire gastroc, but especially at the medial head, along with moderate to severe pain when dorsiflexing the ankle or resisting plantarflexion. This was largely not a good description of my sore calf experiences.

Wikipedia said the gastroc functioned not only to bend the knee, but also to pull on the heel — that is, to plantarflex the ankle — and, as such, was at risk of being torn by a severe dorsiflexion. Medscape (Saglimbeni, 2016) said injury was most common when the gastroc tried to contract while the leg was extended and the foot was dorsiflexed. In other words, all other things being equal, the gastroc would tend to be more stretched and at risk when I was running uphill. This, too, was pretty much the opposite of what I experienced. Running uphill, when the ankle was most strongly dorsiflexed, was the one kind of running that had never produced my calf pain. As mentioned earlier, running uphill was therapeutic: it seemed to reduce what I was coming to consider my Phase 1 tightness, and also to prevent my Phase 2 sharp pain. It seemed, then, that my pain probably did not arise from stretching an overly tight gastroc.

There was another factor to take into account: muscle type. Wikipedia distinguished skeletal muscle, of the kind appearing in the leg, from the smooth muscle found in various organs (e.g., trachea, arteries, digestive tract). According to Neunhäuserer et al. (2011), skeletal muscle fibers were of two types: Type I, also called “slow twitch,” and Type II, also called “fast twitch.” (There were two subtypes of fast-twitch fibers.) According to Scientific American (Greenemeier, 2012), “The fast-twitch fibers contract many times faster and with more force than the slow-twitch ones do, but they also fatigue more quickly.” It was reasonable to believe, and Runner’s World (Magill, 2010) did believe, that one’s body would use fast-twitch fibers for the shortest and most intense workouts, but would switch to using more slow-twitch fibers as the focus switched from speed to stamina.

That was interesting because of the longstanding awareness that the gastroc and the soleus tended to contain different percentages of fast- and slow-twitch fibers. Edgerton et al. (1974, p. 261) studied cadavers and found that, in people who had died of various illnesses (mean age 59), the gastroc was typically divided, about 50-50, between fast- and slow-twitch fibers, while the soleus was about 70% slow-twitch. More recently, as summarized by Clippinger (2007, pp. 39-40), researchers had found that the two muscles could vary considerably from Edgerton’s percentages. It appeared that genetics and training were responsible for observations that elite sprinter gastrocs contained as much as 73% fast-twitch fibers, while in some cases (e.g., distance runners) the slow-twitch percentages could range to, and beyond, 70% for the gastroc and 85% for the soleus.

It seemed this information might help to explain some calf pains. It was conceivable, for instance, that an emphasis on the long, relatively slow slog of distance running could yield an imbalance favoring slow-twitch fibers. This could matter if the remaining fast-twitch fibers were not sufficient to handle the stress of propelling a body rapidly, when speed was needed. Some of my sharp calf pains had occurred when I had attempted longer strides, and I had assumed that was just because I was stretching. And maybe it was; but maybe fast-twitch fibers were better at stretching, and maybe I needed a certain number of them to avoid straining the rest. The theory here would be that walking tended to reduce calf aches because walking put less emphasis on fast-twitch fibers.

Not that I wanted to overstate how much was actually known about the functioning of these muscles and their fibers, nor to oversimplify what did truly seem to be understood. For instance, Lenhart et al. (2014) grappled with the seemingly straightforward question of what the gastroc and soleus did while a person walked, and found that both muscles affected flex angles in everything from ankle to hip, and also that their functioning varied at different parts of the stride.

In short, while it seemed I might have arrived at a partial explanation of my situation, I felt there was surely more to it than this. My spreadsheet demonstrated, among other things, that my calf aches had started before I began running distances longer than three miles — though now it seemed three miles was probably long enough to count as distance (i.e., soleus-heavy) running, for these purposes. I had never done much sprinting; perhaps I should have been doing more.

Soleus Functioning

Unlike the gastroc, the soleus was not involved in bending the knee; but like the gastroc, it was involved in ankle plantarflexion. Wikipedia seemed to say that, by plantarflexing (i.e., keeping the front of the foot pressed against the ground), the soleus was vital for the act of standing.

Possibly both the soleus and the gastroc would prefer running uphill, as mentioned above, because the angle of the roadway would make it easier for them to do the job of plantarflexing. This suggested that it might be a struggle, relatively speaking, for these muscles to keep the front of the foot pushing against the ground with the requisite pressure when I was running on a level surface — not to mention running downhill, which in my experience was a prime source of calf attacks.

Several years after my first calf attack, I switched from heel striking to midfoot landing, and also switched from standard running shoes to a minimalist shoe, in a bid to reduce heel and arch soreness. I believed but was not certain these measures helped.

As just indicated, the soleus consisted predominantly of slow-twitch muscle fibers — 60% to 100%, according to Wikipedia — and was thus more oriented toward toward standing, walking, and distance running rather than sprinting. Presumably the soleus would have shared in an overemphasis upon slow-twitch muscle fibers, as described above.

According to Wikipedia, “The gastrocnemius muscle is prone to spasms, which are painful, involuntary contractions of the muscle that may last several minutes.”

Wikipedia said the soleus had two primary functions: plantarflexion and pumping blood.

Lenhart et al. (2014) found that, during walking, the gastroc functioned …

Non-Antagonistic Muscle Overcontraction

The MCS quote (above) referred to muscle overcontraction involving antagonistic muscles. But it was also possible for muscles to overcontract even when there were no opposing muscles. For instance, addressing the problem of “muscles responsible for excessive destructive forces” in dentistry, Rao et al. (2011) described the use of Botox (i.e., botulinum toxin) to counteract “muscular over-contraction” in the upper lip; others likewise described bruxism (i.e., tooth-grinding) as a matter of muscle overcontraction. Thus, it seemed that the gastroc and/or soleus could overcontract despite the absence of …

Overcontraction Due to Spasm

An agonist-antagonist pairing was not necessary, in order for a muscle to overcontract. For example, Schultz (2015) said, “Spasticity is a factor in over-contraction of muscles. A spasm is an uncontrolled muscle contraction.” MedlinePlus (2016) similarly equated spasticity with the condition of having muscle spasms. Other sources were more inclined to distinguish spasm from spasticity. For instance, Wikipedia said, “Spasticity mostly occurs in disorders of the central nervous system.” WebMD (2017) cited cerebral palsy, traumatic brain injury, stroke, multiple sclerosis, and spinal cord injury as common causes of spasticity.

As with the possibility of spinal pathology (above), it seemed unlikely that my calf pains were due to brain problems. I didn’t have any such diagnosis (e.g., stroke), and I also saw that my calf problems arose directly from my running. It seemed, in other words, that spasms (or, if you prefer, spasticity) was relevant only on the local level, involving spasms within one or more calf muscles due to some aspect of running activity.

According to WebMD (2017), muscle spasms could cause muscle cramps. But WebMD (n.d.) also said cramps had many other possible causes, including muscle overuse, shortage of minerals (e.g., potassium, magnesium, calcium), dehydration, use of certain medications (e.g., antipsychotics, statins), and unhealthy postures (e.g., sitting, lying, or standing for a long time, or in an awkward position).

 

or the various conservative approaches listed by Tucker (2010), such as using arch supports, icing the soreness, or not running on hard surfaces. Unfortunately, according to Wuellner et al. (2017), such techniques are “generally ineffective in controlling symptoms if the patient continues to engage in the inciting activity.”

Gross et al. (2015) offered the reasonable suggestion that compression of different compartments could have divergent, externally visible symptoms. Compression of the anterior compartment could result in weak ankle dorsiflexion – also soleus …

For years, I thought it was just a pulled muscle. And that first time, maybe that’s what it was. I had noticed that my right calf was tight, during a three-mile run; and then later that day, walking to my car after a meeting, I jumped over a flowerbed and came down feeling like my leg had been stabbed. I had a sharp pain that left me limping.

Eventually, though, I realized that this problem was not behaving like a simple muscle injury. It would come back when I had not done anything particularly strenuous; sometimes it would disappear the next day, and I could resume running (which would be unlikely if I had actually torn something); and yet, on the other hand, I could take months off, and it would be back almost immediately when I did start again.

I did learn, the hard way, that this was not one of those pains you could just run through. It was not something that would gradually die out. This was the kind of pain that, if I kept running — if I could even stand to keep running — it would only get worse, and the recovery would be longer.

Calf attacks rarely kept me from other forms of exercise. There were a few instances when, in the first minutes (or, rarely, hours) after the injury, I would barely be able to use the leg; but for the most part, I was free to bike, walk, or swim, starting almost immediately. The pain was highly specific to running. It also seemed that sometimes, when I felt the calf stiffening and feared an attack was imminent, I could prevent an attack by switching from midfoot to heel strike, or by reducing stride length or speed.

Note: I was not sure that I was having only one kind of calf problem. It just seemed advisable to focus on calf attacks as the most painful and crippling problem I was experiencing. It seemed that some of the following material would also be useful for purposes of understanding and responding to other kinds of calf problems as well.

The reader may notice that my own story changed somewhat, as I worked through the information provided in this post. That happened because I was not experiencing any calf pain at this particular moment, and thus had to rely on my notes and recollections. As I got more into the subject and had to focus more carefully on the sore calf experience, I was reminded that there were at least two different phases in the progression to the kind of injury that would prevent me from running.

As I say, there were times when I was able to resume running more quickly than a tear would warrant, and there were also times, in the middle of a run, when a shift of pace, posture, stride length, or strike would reduce or even eliminate a growing feeling of calf tightness presaging an attack.

For most of these years, I would have said that MCS Type 1 was the most likely candidate. It seemed that I would get calf attacks just when I was starting to get into shape again. I saw it as a situation where the calf muscle was growing strong once more; I thought maybe I was overdoing the training in my eagerness to get back on the road.

For me, not all aspects of subtype 2B were precisely on target; but as I thought about it, subtype 2B did seem to apply to the early phase of my calf attacks. I did have the sharp pain noted above; but before I experienced that sharp pain, I usually had a general feeling that my calf muscle was knotted or tight.

I might start with that tightness, or it might come on during a run. If it got too intense, I knew that the sharp pain might arrive at any moment. At that point, I would attempt mitigation. That could mean slowing my pace, shortening my stride, or switching from midfoot to heel landing. Sometimes those would reduce the knotting; sometimes the dull ache would get worse, and I would start walking; sometimes the sharp pain would

This part was a little confusing. I noticed that I could have minor sharp calf pains from just standing up from my desk, even when the calf had not otherwise been sore; and I also noticed that calf tightness could appear, grow stronger or weaker, and disappear entirely during the course of a run. Moreover, during a run, the calf attack could come on very quickly after the feeling of tightness first appeared.

Of course, it would help to have a clear understanding of the problem before attempting a solution.

The concept I was developing, at this point, was that the calf attack could consist of two phases. First, in the usual situation, there was the neuromuscular cramping; and if that became severe, it could result in a structural injury (i.e., a pulled or torn calf). Or perhaps the end product would not be an actual tear: after all, my ultrasound had shown no physical damage, even when the pain had been sharp. Maybe it was just that the cramping would switch into an aggravated mode, where continued running was painful because the muscle was too tight to use. I think I had always stopped running immediately, when I got to the point of sharp pain, because at that point injury seemed imminent. Maybe I had always stopped before that cramping could result in an actual tear.

In addition to the gastroc and the soleus, the calf had several minor muscles. It was possible that one of them was responsible. But I doubted it. If I was correct — if this was a problem of the gastroc and/or the soleus — the foregoing remarks suggest that I was probably not experiencing overcontraction due to agonist-antagonist muscle imbalance.

Updates

In normal times, when there had not been any recent calf trauma, I found that I was able to run down longish hills without a problem if, before attempting that, I began with a warmup walk and then an initial run on a largely level or uphill track, each extending more than a mile.

Although the Mayo Clinic (2022) said that a young runner could recover in six to eight weeks, but that an over-50 runner might require 12+ weeks, that was not my experience. Presumably their error was due to the assumption that the runner to whom they were responding was certain that he had experienced an actual “torn” muscle, as he said, when instead it might have been merely the intense cramping described above. I found that sometimes I could actually resume running within the same run. For example, on one run, I had the acute calf pain; I walked for a mile or two; then I ran mostly on uphills and walked the rest, during the remainder of that outing.

During a period of several years ending in late September 2023, I had only the sort of experience described in the previous paragraph: cramps that were sharply painful during the run, but that would go away within a few days or maybe a week if I made sure to warm up well and didn’t push it. But in late September 2023, I had a sharper attack. This one was actually not associated with a downhill run of any significance: I had just crossed a bridge, but it was only very slightly downhill. Despite a few longer warmup walks and then a week or two of doing nothing but walking, it didn’t go away. In this case, I noticed two associations: I had just stopped taking magnesium supplements (just the ordinary, cheap Walmart “Spring Valley” brand) a week earlier, and I drank a moderate amount of alcohol (which I didn’t do much anymore) within about 24 hours earlier. I resumed the magnesium supplements and, with gradual increases in walking and running, I resumed my usual three-mile runs in late October, about a month after the initial attack. At least within the first week, at this writing, it appeared that the magnesium had made a difference: the attacks had not resumed.

Starting at age 53, I began to have two different heart-related problems that I thought were related to age and/or distance running. Now I’m not sure that either of those possible causes explains the cardiac symptoms.

Contents

Is It Atrial Flutter?
Dealing with Cardiologists
Concerns About Ablation
Alternate Theories: Air Pollution and/or Humidity
Another Possibility: Atrioventricular Block
Update (2022): Vasodilation

.

Is It Atrial Flutter?

As detailed in an earlier post, I had experiences of persistent atrial flutter (often called simply “AFlutter”) in 2014 and 2017. AFlutter is an arrhythmia — that is, your heart is not beating right — but it is what you might call a rhythmic arrhythmia: there is a pattern to it. In AFlutter, there are the regular beats (BOOM) punctuated by several weaker beats (boom). So instead of a normal heartbeat (BOOM BOOM BOOM BOOM) your heart goes BOOM boom boom boom BOOM boom boom boom. (Atrial Fibrillation, or AFib for short, is different again: it is irregular. It is apparently much more common than AFlutter. Medical personnel can assume that references to AF mean AFib, even if what you actually have is AFlutter.)

Each of those two experiences of AFlutter was terminated with electrical cardioversion: that is, a cardiologist shocked my heart, and it went back to what they call normal sinus rhythm. Neither of those two episodes started during an exercise session. I would have known if it had, because the effects of AFlutter were dramatic: this guy who could run ten miles was suddenly unable to run a quarter-mile.

Then there was a very different set of cardio symptoms. What I experienced, starting at age 53, in 2008, was an episode of chest tightness, rubbery legs, and dizziness or reduced consciousness while running. I didn’t have “shortness of breath” in the sense of being out of breath (i.e., breathing harder than expected under the circumstances), but with the tight or full feeling in my chest, it wasn’t as though I was breathing calmly. By 2012, those episodes had become common enough to induce me to see a cardiologist. These did not seem to be related to any cardiac arrthythmia. I could produce a normal electrocardiogram (normally abbreviated as EKG or ECG), and then go out for a run and experience one of these episodes.

For some reason, cardiologists seemed unwilling to consider that these two sets of symptoms might be rather distinct. It appeared that medical training inclined them to focus on the most obvious or obtrusive problem, and to assume that the less obvious or more minor problem would then go away. That would be logical, except that the evidence in this case did not seem to support it. There did not seem to be any clear link between the two obvious instances of AFlutter, in 2014 and 2017, and these much more frequent and yet fleeting instances of exercise-induced chest tightness. Certainly the former was not causing the latter: the chest tightness had started years earlier. Nor did the two sets of symptoms seem to accompany or contribute to one another. In my reading, and in my conversations with cardiologists, I did not encounter explanations of how the episodes of chest tightness would relate to AFlutter.

In a recent conversation, a cardiologist suggested that the chest tightness was due to paroxysmal AFlutter. The difference between persistent AFlutter (as in those two episodes in 2014 and 2017) and paroxysmal AFlutter was that the latter would last for hours, at most; it would not continue for days, weeks, or years (if you lived that long). Paroxysmal meant that it comes and goes. The problem here was that we had no evidence of paroxysmal AFlutter.

We did have one very short burst of tachycardia (i.e., very rapid heartbeat), captured on something called a Holter monitor, that I was wearing while I went on a bike ride. I was biking along, at a relatively strong but not strenuous rate. Then I got to a big intersection, and I needed to pump it to get across before the traffic light changed to red. So there was a sudden burst of strenuous exertion. Within seconds, I was having one of those chest tightness episodes. The monitor’s five electrodes on my chest captured it. But what the Holter monitor displayed was just a few very rapid heartbeats: a very short instance of tachycardia. There did seem to be a problem, but it was not an arrhythmia — that is, neither the regular pattern of AFlutter nor the irregular pattern of AFib. There was no mix of strong and weak beats.

It was apparently not surprising that those few rapid heartbeats were the only tangible evidence, so far, of a current heart problem; apparently this was not just a problem of sports medicine, as I had supposed. According to Barrett et al. (2013), “Cardiac arrhythmias are remarkably common and routinely go undiagnosed because they are often transient and asymptomatic.” It seemed that, for a variety of patients, it could be difficult to figure out what was going on, in an organ as complex as the heart. One would want to make sure that the proposed treatment was relevant to the actual problem.

Dealing with Cardiologists

My cardiologist did not show me those actual Holter monitor results, nor did she tell me that she interpreted those results as suggesting paroxysmal AFlutter. I learned these things during a session with someone else at a later date. I also saw that she had added notes, apparently written for other medical personnel and not shared with me, suggesting that I had burdened her with an excessively long consultation. Her notes did not mention that the problem, during that session, was that she kept interrupting me. I did finally insist that she allow me to finish.

The problem, I said, was that the Holter monitor may have captured what happened when I crossed that busy intersection. But, as far as I could gather from her remarks, it provided no explanation for the fact that I continued to experience varying degrees of chest pressure and other symptoms throughout the 20-minute period thereafter, as I turned the bike around and headed for home. If AFlutter was the explanation, surely that would have been evident in the record from the Holter monitor throughout that ensuing 20-minute period. I expected the cardiologist’s theory to account for that 20-minute period because the notes that I handed over, when I returned the Holter monitor, did make clear that I was having continuing symptoms throughout that period.

I belabor those interactions with the cardiologist because I think it is important to recognize that diagnosis of medical problems can be complicated by the behavior of clinicians who view patients’ objections as interference. This cardiologist, who seemed to hail from one of the upper castes of India, worked in a practice that treated mostly Hispanic patients, many of whom had little money or education. In my impression, these patients did not tend to research their heart issues in the English-language medical literature, much less challenge the interpretation put forth by the learned doctor.

The cardiologist referred me to two cardiac specialists within her medical organization. Like her, they seemed to be relatively young medical professionals, from developing nations, who were completing their residency requirements to graduate from med school. One, a structural interventionalist, observed that I did seem to have a hole between my heart’s two upper chambers, but this was apparently pretty common and, in his view, did not seem to explain my symptoms. The other, an electrophysiologist, was concerned with the heart’s electrical wiring rather than its plumbing. One of these specialists asked if I had medical training. (I don’t.) I gathered that, like the cardiologist, they did not often encounter patients who posed informed questions about their diagnoses.

The electrophysiologist recommended ablation, which he described as a process of burning a tiny part of the heart, so as to prevent it from transmitting unwanted electrical signals resulting in AFlutter. I found it remarkable that he indicated that he was not focusing primarily on the recurrent episodes of chest pressure, but was rather concerned with AFlutter. As far as I could tell, I had not experienced AFlutter in more than two years. I was there because I was seeking a solution to the recurrent episodes of chest pressure. As one would expect for a problem that has not yet been diagnosed, he did not seem to have any explanation for how ablation would be relevant to those episodes.

I asked for a second opinion. For a second opinion, the organization sent me back to the cardiologist. She said she agreed with the electrophysiologist. Unfortunately, this was not one of those sessions where the physician sits down with the patient, goes through the possibilities, and explains why alternative diagnoses are inferior. This was, rather, a situation where the cardiologist simply handed out her opinion. She might as well have said, “I know you are a lawyer, but I don’t want to be sued, so my opinion is whatever the expert recommended.”

Concerns About Ablation

In my reading, I had encountered mentions of ablation as a possible cure for AFlutter. But as one would suspect, it seemed that the act of destroying heart tissue could entail problems and risks. After meeting with the electrophysiologist, I took a closer look. To prepare for that second-opinion meeting with the original cardiologist, I copied some quotes from 1 2 3 articles, and highlighted key lines on a paper that I handed to her when we met:

In other words, these articles seemed to say several things: before any ablation, it was necessary to study the heart, to identify the exact spot that needed to be burned, in order to prevent AFlutter without doing unnecessary damage; identifying the correct spot could be difficult; a pulmonary (i.e., lung) function test might be advisable; and the consequences of even a successful ablation could be severe. In apparently large numbers of patients who had undergone ablation, those consequences could include the need to implant a permanent pacemaker, lifelong follow-up to avoid risk of stroke, poor quality of life, multiple returns to the hospital, a high incidence of tamponade (i.e., life-threatening fluid buildup around the heart), and fibrosis reducing the heart’s ability to pump blood. Another study noted that, after all this, the long-term odds of progressing into atrial fibrillation after ablation could exceed 50%.

The cardiologist said that the electrophysiologist would conduct a study at the start of the ablation procedure, to identify the spot that he felt should be burned. The electrophysiologist himself had not said this. He had said, rather, that he would conduct a separate study in another part of the heart, to learn more about the possible cause of AFlutter. When I inquired further into that, to try to understand it, he declined to provide further information.

The cardiologist said that the electrophysiologist would be able to determine, during his study, precisely which spot was responsible for my symptoms. This seemed dubious, as we had not even established that my symptoms were due to AFlutter. I expressed doubt that he would be able to simulate cardiac behavior that arose only under certain conditions — if indeed my symptoms were purely cardiac, not involving any pulmonary mechanism. No doubt he could make my heart beat faster. But we had already established that mere exertion and elevated heartrate were not the issue. The cardiologist had personally overseen a “stress echo” (i.e., echocardiogram conducted along with a workout on a treadmill) in which she avoided the sudden exertion that I had said was necessary to trigger the symptoms, preferring instead to coach me through a gradual increase in exertion that, as I had predicted, did not trigger the symptoms.

The game plan, according to the cardiologist, was that the electrophysiologist would do a preliminary study and then, while I was under moderate sedation, he would give me an opportunity to consent to his plan to continue with the ablation. I pointed out that, aside from the fact that a person under sedation might not be especially sharp, I would obviously not be able to research his specific plan as I lay there in the operating room. If I withheld consent at that point, it was not clear whether my insurance coverage would allow me to return for the ablation at a later date.

After that conversation with the cardiologist, I followed up with the the electrophysiologist, to determine whether he could conduct the promised study in a separate procedure, prior to a separately scheduled ablation, so that I would have an opportunity to review his findings, and could consent (if appropriate) at a time when I was not under any sedation. A few weeks later, his assistant let me know that he would be willing to do that.

I didn’t mean to be a pain in the neck. Maybe I was misunderstanding something about the materials quoted above. Maybe my interest in a prior study was not merely atypical for this healthcare organization; maybe it was atypical in cardiology altogether. I’m sure it could be frustrating for a cardiologist to deal with a layman such as myself, who might know a few terms but would still fall far short of understanding the heart. No cardiologist was going to have an hour to sit around and go through the nuts and bolts of the whole thing with me.

But I didn’t think I was expecting that. I was grateful for these experts’ helpful efforts. The problem, as I saw it, was that we were talking about an extremely invasive procedure, based on what seemed to be grossly inadequate information, with frightfully high risks that the operation would leave me dramatically worse off. Bear in mind that other physicians in this organization had already twice ordered me to take medications with potentially permanent adverse consequences — orders that other physicians promptly countermanded. The stress echo was, moreover, not the first completely pointless cardiac investigation I had endured. By this point, experience suggested that I had better have an informed understanding of what they were proposing to do to my heart, and why. In my reading, I had encountered stories of others who blindly trusted the doctors, and who wound up with new problems, apparently because the recommended solution was not on target.

Alternate Theories: Air Pollution and/or Humidity

I had noticed some interesting things about the chest pressure symptoms. The first time I got them, in 2008, was in Indianapolis. When they returned and intensified in 2012-2013, I was in Fayetteville, Arkansas. In the past few years, when they seemed to be impairing my running and biking at even less strenuous levels, I was in San Antonio.

Those were all relatively urban or at least suburban locations. By contrast, during the years since 2008, I experienced such symptoms rarely, if at all, in rural northern Indiana, rural Wisconsin, and rural western Kansas. The contrast suggested that something about the urban or at least suburban environment could be provoking such symptoms. Pollution would be an obvious possibility. Indianapolis did have a big coal-burning power plant, intelligently located on the windward side of the city, but its location was at a distance and angle suggesting that it was probably not much of a factor for me personally. Automobiles seemed to be a more consistently available source of pollution in such locations.

There was another factor: heat. The Indianapolis incident occurred in summertime. I had been running on hot days in rural Indiana and Kansas too, so this connection was not as clear. But in the past few years in San Antonio, which tended to be a relatively hot place, there was a great difference between my running experiences when the temperature was at or below ~55°F and when it was above 70°F. Below 55°F, cardiac symptoms virtually ceased. But above 70°F, chest pressure was almost always the reason why I had to back off, when I tried to run a faster three miles.

It appeared that pollution could also have been the cause of the AFlutter episodes. I had no specific evidence or precise starting date for the 2014 episode. But in 2017, at a time when I was running or biking every couple of days, my experience of AFlutter occurred shortly after a relatively intense bout of fumigating. That is, I sprayed bug spray around my living space, and wound up in a coughing fit when I inhaled a bit of it; and then, later the same day, I was shocked to see that I could barely get my bike up a hill that I would normally ride up without too much difficulty. AFlutter was diagnosed in an EKG a few days later. Research by Link et al. (2013) suggests that, if the insecticide did cause the AFlutter, then the AFlutter may have commenced within about two hours after the spraying. As in the 2014 episode, I didn’t notice it until I went out to run or cycle.

A New York Times article (Gardiner, 2019) suggested a possible link between air pollution and my symptoms while running (see also e.g., Stieb et al., 2017; Link & Dockery, Aung et al., 2018). Gardiner said, “Hot summer days can bring spikes in air pollution, as traffic exhaust and other emissions bake in the sun.” That seemed to imply that heat could foster chemical reactions that would make pollution more toxic. The link with heat seemed to underscore that my problem was not due to pollutants produced by wintertime emissions from furnaces.

I wondered whether heat was important, not (or not only) because of chemical effects on pollutants, but because warm air tended to hold more moisture. Possibly warm air was able to hold more pollutants as well; possibly those pollutants were held by the moisture in the air. Or possibly the moisture itself was the problem. Consistent with my experiences of running without symptoms in the summertime in western Kansas, this line of thought suggested that my symptoms might be more pronounced in a humid place than in a dry place, even at the same heat index level. Humidity was particularly high at night in San Antonio in the summer. Unfortunately, with daytime highs reaching and exceeding a humid 100°F almost every day during the past August and September, the nighttime — with temperatures dropping as low as 77-82°F at 4 AM — was the only time when I could stand to run.

The air pollution hypothesis (as distinct from the moisture hypothesis) had at least two problems:

  • In the past several years and perhaps before, I tended to experience the chest pressure near the end of my three-mile running route, when I was pushing to try to improve my time. This was a problem because the last half of that route was in a park. That is, before experiencing those symptoms near the three-mile mark, I had spent at least 12 minutes away from traffic. According to one physician quoted in Gardiner’s (2019) article, the air along a busy street could hold twice as much pollution as a quiet street just one block away. In the second half of my run, depending on wind direction, the nearest busy street was at least a quarter-mile away, and could be as much as a mile distant.
  • In midsummer, to avoid the daytime heat, I would run down deserted streets at 3 AM. By then, traffic had long since subsided. Moreover, conditions were often breezy; presumably the bulk of the air pollution had long since been blown away. Yet my symptoms were intensified: when the temperature reached 75° to 80°F, I would experience chest pressure, not only near the end of my run (even when my pace was more than one minute per mile slower), but also in the second mile and, increasingly, even at the start of the run. So it did not appear that air pollution from traffic was an immediate cause of chest tightness and other symptoms I experienced while running.

Those observations were consistent with another hot-weather observation: I would have symptoms when I switched from relative inaction to sudden (including moderate) exertion. For instance, after stepping out of the house, before I even commenced my 15-minute warm-up walk, I would often use two trees to help me climb over a wall. That is, I would step up from a bench, putting one foot on a knot in the tree’s trunk; I would pull myself a short distance up the tree; I would perch momentarily atop the wall, to shift my weight; and then I would step down onto a branch on another tree, on the other side of the wall, and swing to the ground. Within a few seconds after this bit of exertion, I was often feeling chest pressure, dizziness, and other symptoms. This, too, would happen only in hot weather, and it seemed to happen regardless of time of day or wind conditions.

These thoughts suggested that what I was experiencing was not the immediate effect of a pollutant that I was absorbing as I ran along a busy street, not even a pollutant emerging from the asphalt: the trail in the park was concrete, not asphalt. It seemed, rather, that some factor in my physical condition and/or ambient conditions left me more or less constantly at risk during warm weather. That factor could be a pollutant floating on the air throughout the daytime (I kept the windows open and did not use air conditioning) or seeping out of the walls of several different residences, in these several different cities. Or it could be an aspect of my lung condition that would become operative only in humid conditions.

Whatever it was, I seemed to be on my own in searching for it. The cardiologist had no relevant suggestions. The physician’s assistant (PA) at the clinic was willing to order an X-ray, and to proceed with a lung function test if the X-ray supported it. This may not have been consistent with the article, quoted (above) on the page that I handed to the cardiologist. That article seemed to suggest proceeding directly to a lung function test in some AFlutter cases. Not that I could be optimistic about what a lung function test might reveal in the clinic, because I was not experiencing any symptoms as I sat there in the waiting room. I doubted that any medical personnel would be willing to hang out by the trail at the end of my three-mile route, so as to conduct a lung function test on the spot.

Apparently the X-ray did not reveal anything, unless possibly its interpretation required specialized skill. I add that caveat because, 30 years earlier, a specialist had observed my chest X-ray and asked whether I had ever lived in the Ohio River Valley. He asked that, he said, because some pathogen — something like histoplasmosis, maybe — had left small nodules in my lungs. I didn’t know whether those nodules were still there, all these years later. But possibly something like that would have adverse effects in hot, humid weather. Unfortunately, neither the cardiologist nor the PA was willing to refer me to a pulmonologist within this organization. The Stack Exchange Medical Sciences website deleted my question on this situation. My searches had otherwise not led to any additional insight. So this remained something of a puzzle.

Another Possibility: Atrioventricular Block

So far, we had only one very brief instance of tachycardia, captured by the Holter Monitor when I bike-sprinted across that intersection. That wasn’t AFlutter, and AFlutter was what the electrophysiologist was proposing to fix with his ablation, so I was stuck. The cardiologist looked into the possibility of wearing a longer-term (I think it was 14-day) Holter Monitor, as distinct from the 24-hour version I had worn previously, but found that it would cost me $375 to run that study. As a man on a rather tight budget, I opted for her alternative, which was to wear a much simpler (two- rather than five-lead) 14-day monitor. I didn’t expect much from this thing — I mean, if the five-lead Holter Monitor didn’t capture most of my actual symptoms (i.e., on the bike ride home, after that brief burst of tachycardia), what was this little old two-lead monitor going to achieve?

Well, don’t judge a book by its cover. What to my wondering eyes should appear, a week later, as we approached the Christmas season, but the discovery that some technician had reviewed the results of that stupid old 14-day monitor, and had reported that it revealed the presence of a first-degree atrioventricular block (AVB). I wasn’t sure if maybe this tech was just imagining things, or maybe the one who read the Holter Monitor’s results had overlooked evidence of AVB in those earlier results, or maybe the AVB was a brand-new development. But here it was, and it certainly was intriguing. Aro (2016) said that AVB “is not always a permanent finding, but a transient phenomenon in a significant number of healthy individuals.” Unfortunately, I was not going to be able to check it very often, so it seemed I would have to treat it as potentially enduring.

According to Cleveland Clinic, “Symptoms of second- and third-degree heart block include fainting, dizziness, fatigue, shortness of breath and chest pain.” So we had electrophysiological evidence, from the 14-day monitor, and the symptoms matched. This seemed promising. The general concept, as explained by that Cleveland Clinic webpage, was that each heartbeat began as an electrical signal from the right atrium to the ventricles, but an AVB would interfere with that signal. In first-degree AVB, the heartbeat was merely delayed. This, they said, was “common in highly trained athletes.” So there. I had just graduated from being an ordinary old guy, stumbling along, to an elite performer. Second- and third-degree AVB entailed longer delays and actual skipping of heartbeats.

Assuming I did have an AVB, it was not clear whether I had only a first-degree AVB. This 14-day test had come late in the season. Temperatures were cooling down; humidity had dropped; the spores I imagined free-riding in the hot and humid air were now presumably falling to the ground instead of entering my lungs. Now I was finding that even when the temperature was in the upper 70s Fahrenheit, it was hard to reproduce summertime’s more intense symptoms for the monitor, perhaps because the windows in my home were mostly closed, giving my lungs a chance to start clearing the pollutants responsible for those symptoms. So maybe the monitor’s report of a first- rather than second-degree AVB was consistent with the fact that my symptoms were milder now.

The Cleveland Clinic webpage said beta blockers could cause an AVB. This prompted me to wonder whether my use of inderal for stage fright had permanently corrupted my heart’s electrical timing — merely from that drug’s normal operation, or possibly during one specific instance when I went out for a run, forgetting that I had taken it just a few hours earlier. I imagined that the timing circuits could have been permanently fouled, during that run, by the conflict between the beta blocker’s heartrate control and my heart’s attempt to speed up. But that run had occurred, I think, a year before my first experience of these AVB symptoms. Perhaps more likely, Cleveland Clinic said that an enlarged heart could also cause AVB. On that, another Cleveland Clinic webpage offered cautionary words: “A diagnosis of an enlarged heart in athletes may be a serious medical issue – or just a byproduct of an active lifestyle. The challenge for physicians is to differentiate between the two.” Aro (2016) likewise found AVB characteristic of athletes, and thus perhaps just “a marker of physical activity and healthy lifestyle,” but said AVB also appeared in elderly patients, where it could accompany “higher risk of atrial arrhythmias and heart failure.”

The AVB diagnosis seemed to tie some threads together. According to Nikolaudou et al. (2016), first-degree AVB “is associated with an increased risk of atrial fibrillation.” This raised the possibility that a permanent AVB could create a setting in which additional stressors would trip the heart into persistent AFlutter. In the 2017 episode of AFlutter described above, maybe the bug spray would have been enough of a stressor for this purpose. This interpretation suggested that treating AFlutter with ablation could be merely treating a consequence of AVB. If the heart’s natural response to AVB + unusual stressor (e.g., bug spray) was to flip into AFlutter, and if ablation prevented a recurrence of AFlutter, then maybe my heart would react, next time, by putting me into AFib instead. That would be consistent with the impression that AFib was one possible adverse consequence of ablation. This would not be an improvement.

As indicated above, my observation was that the cardio symptoms cropped up primarily during exertion in the hot and humid season. Lacking a better explanation, the bug spray episode prompted me to theorize that irregularities in my heartbeat could have a pulmonary origin. This could fit with the scenario where spores or pollutants capable of producing cardiac symptoms would float on the humid breeze until they found me; that their irritating characteristics could take hours if not days to accumulate to the point of affecting my heart during exercise; and that this effect would tend to endure until the hot season started to wind down. Thus, at this writing, daily high and low temperatures had been dropping by about 20°F per month, for the past two months; my three-mile running time had improved by two minutes from just one month earlier; and I felt the way was open for further improvement. In response to AVB, Nikolaudou et al. (2016) said that “the optimal method for atrioventricular resynchronization remains unknown.” But in my case, it presently appeared that one possible response was merely to avoid San Antonio in the hot season.

Update (2022): Vasodilation

The leading theory, in the past year or two, has been that my symptoms are due to vasodilation. The general idea seems to be that, in older people, blood vessels are not as flexible, and thus (somehow) more blood is used for cooling, resulting in a loss in blood pressure (e.g., Holowatz et al., 2010). At this writing, the cardiologist had me looking at calf compression sleeves (at least 30 mmhg) for a possible assist.

Running is a great sport for being skinny. But it’s not magic. It’s also not necessarily hard work. For those who may find it helpful, this post contributes my own observations on that.

1. Luck

I have always been thin. If obesity is caused by a virus, I don’t have it; if it is caused by a certain kind of metabolism, I don’t have that either. If it is caused by less-than-ideal heredity, or by a curse that makes other people blow up when they eat the things I eat, I must be blessed. If it is caused by a sweet tooth, I’m lucky there too: at a certain point, I feel I’ve had enough sugar. Whatever causes obesity, it isn’t happening in me. That’s not due to my superior self-discipline or diet or anything other than luck. I know that; I am grateful that I got lucky; and I am sorry for those who find it much tougher to get to a place where running is even an option.

2. Love the Outdoors

Anybody can tie on the shoes and try to run down the street. I don’t think that’s the way to start running. If you want to run, and keep running, I suggest that, for now, you forget about running. Focus, instead, on loving the outdoors. Find pleasant things to do or places to go, outside. I find that, the longer I’m outdoors, the more I want to stay outdoors. So walk, work in the garden, go hunting, play in the mud, anything to build up your addiction to the outdoors. The work and fresh air are good for you in any case; you’re more likely to meet people and have experiences that are part of an actual life, as distinct from whatever is going on indoors; you’re being saved from the real possibility that sitting is dangerous. Most important, for present purposes: you are acquiring a reason to want to run and keep running. If you want to be outdoors, running can help you do that at times (e.g., midnight, midwinter) and in places (e.g., cities) where interesting outdoor alternatives are limited. Ultimately, even if you don’t stick with running, you should at least stick with an effort to experience the outside as a great place; you should always try to find ways to enjoy being out there.

3. Find a Kind of Running That Works for You

Here’s how running works. You get motivated to lose weight; or if you’re already skinny, you get excited about running farther or faster; you take the plunge; you get tired of it, or you get injured; and then you spend weeks or months (or years) starting over. So don’t do that. Control your enthusiasm. Be aware of the number of things that can go wrong, ranging from stress fractures to strained joints to the heart conditions that can result from too much distance running. If you’re the very obese man I saw — once — trying to run on the nearby trail, realize that that probably will be your one and only stab at it. Because it’s going to be hot, uncomfortable, hard, and quite possibly damaging to your feet, ankles, knees, back, and so forth, and you probably won’t try it again. Instead, listen to what people tell you online, about starting gradually. Just see if you can walk a short distance.

But don’t do that if you can’t find a way to enjoy it! For most of us, willpower doesn’t work over the long haul. Instead of relying on self-discipline, find a kind of walking that you like. Maybe it’s a game, where you walk a block and then you get to sit and talk on the phone or drink another beer. (Kidding, sort of.) Maybe it’s an exploration, where you make a point of going down different streets and alleys at different times of day and night, just to see if there are interesting or spooky things happening. Maybe it’s window-shopping at the mall. Maybe there are friends to visit, or local errands that are actually more pleasantly run on foot. Maybe you would like the habit of going out for a quiet stroll before starting your day, or around sunset. Maybe there are Pokemon-type games online, where you can use your cellphone to help you wander into traffic because you weren’t paying attention. Whatever. It doesn’t necessarily take much. For instance, one recent study found that, for older people with functional limitations, exercising just seven minutes each day (alternately, 15 minutes per day, three times a week) yielded significant health improvements. So find some way to enjoy the feeling of your feet moving you down the street — and to enjoy the feeling that you are starting to become stronger. That is the sort of encouragement that might get you walking regularly.

And then, someday — a month from now, a year from now, whatever — when you’ve built up your ambulatory equipment, to the point where it can handle some twists and stresses, and you feel pretty good about your walking, apply the same way of thinking to the project of becoming a runner. You’ll have started to see which shoes, clothes, locations, and levels of effort work for you. You’ll begin to know a little more about yourself — about the methods, distances, and places where it’s fun. Now you can experiment. If you can move, you can improve. So try running 30 steps at your fastest possible pace. Or alternate walking and jogging through the woods. Or walk (or even run) sideways, or backwards. Or find a partner and try some dancing. Or do qigong or tai chi. Whatever helps you acquire some confidence and desire to get better on your feet. And, again, remember: what’s important is not the running; what’s important is just moving around — outdoors, if possible — in a way you like. If you’re lucky, it might eventually develop into a real interest in running. Then you’ll be ready for something like the run-walk method advocated as a starting point by the New York Times, among others.

For most of us, the hardest part of becoming a runner is the start: getting moving, finishing the first few blocks, staying with it the first few months, getting outdoors when it’s cold (even if you know you’ll warm up within the first half-mile). There is that to it: you do have to put on one running shoe, and then see if you can bear to put on the other one. As you see here, I suggest starting by just getting outdoors. Maybe someday you’ll catch the running bug, or maybe you won’t, but at least you’ll (almost) always have your walking.

4. Don’t Focus on Weight Control

Yes, of course, a successful running program will tend to reduce weight. But there are no guarantees. I remember speaking with the father of a young woman who had recently taken up distance running. He said she liked it because it allowed her to eat more. And that was true: it would. But there are times when a runner is injured, or too busy to run, or just doesn’t feel like it. If you’re eating like there’s no tomorrow, that can easily catch up with you. Ultimately, I think, you have to take up walking, and running if it comes to that, because you have learned to like the outdoors and you have come to enjoy the feeling of running down a trail, or through the woods, or traveling through the countryside with your thoughts and with that lulling steady noise of your feet, your breathing, and the wind. You may find that the desire to keep running will discourage you from eating too much. In any case, if your walking or running has a beneficial effect on your weight, that’s to be hoped for, but it may not be a substitute for trying to eat sensibly.

One Sunday morning, when I was living in New York, I came up out of the subway onto Central Park West. There, I found myself in the middle of the L’eggs Mini-Marathon. L’eggs is, of course, a brand of women’s hosiery, and the mini-marathon was a 10K run that, as I discovered, featured thousands of women of all heights and weights, running at all speeds. They were everywhere. I suppose the truly obese were not present, but it was remarkable to see how short and tall, heavy and slender women could all be running at about the same pace. Maybe I was near the start. Not sure. But I’ve seen that in joggers, too: the ones with the thin or athletic builds are most common, and they may tend to be fastest; but there is quite a variety of body types, among those who run regularly. It does appear to be possible for hefty people to become comfortable with running.

Worrying too much about weight can lead people to do foolish things. I’ve seen overweight people running on hot days, wearing dark (i.e., sun-absorbing), heavy sweatshirts and pants. It is possible that they don’t realize how much they are going to warm up, once they start moving; but sometimes I know they are hoping to lose weight by sweating a lot. One time, I saw a guy dressed like that, on a day with a heat index in the 90s. I commented that he was going to cook. He said he was trying to lose some extra pounds. That’s known as water weight. It comes right back. But when you sweat it out, you lose nutrients, and too much of that can be unhealthy. In that heat, the only thing he was going to accomplish was to teach himself to hate running, and possibly put himself in the hospital with heatstroke. So don’t count on sweat making any difference. You’re going to sweat, and then you’re going to rehydrate. I was seeing a loss of up to four pounds for every hour of running, when I was doing distances, but I didn’t expect that the weight would still be gone the next day.

Running has benefits that have nothing to do with weight. One has to do with longevity. Running (or biking, even at 105 years old) can lower your blood pressure and, in other ways, contribute to cardiovascular health. Another has to do with aging well. If you reach the age of 60 (or even 50) and you aren’t already a runner, you are very unlikely to start; but if you already are, you are unlikely to want to quit. In your later years, you have fewer opportunities for play, fewer chances to put a little pressure on those bones and keep those joints moving. So then you’re more at risk of having joint problems and falling; and if you haven’t had my experiences of recurrently tripping and falling in the dark because you run at 3 AM and can’t see where you’re going, you’ll be out of practice: you won’t remember how to fall. In short, you know the rule: use it or lose it. Your older years may seem like a lifetime away. But they aren’t. You may be surprised, how quickly you can reach the feeling of being old, weak, frail, and vulnerable.

5. Fat Is the Enemy

My theory: fat wants to be fed. If you have fat on your body, it changes your appetite. I don’t know that to be a scientific fact; that’s just my self-observation. I am really not knowledgeable about various diets, medications, and medical procedures that a person might use, in a bid to lose weight. I have the general impression that some of them work, and most don’t. But I know that, if I were really overweight, and if I wanted to be a runner, my first question would be, Is there a reliable and affordable way to get rid of weight, at least for a respectable amount of time? I would want to do that so that I could get a running start, so to speak, on this project of becoming a walking or running outdoorsman. Just give me some weeks or months where I don’t constantly have fat (whether visible on the outside or hidden in my belly) screaming out for food that I really, really want to give it.

That’s it. That’s how I stay skinny. Not through diet and self-discipline; just through luck and, especially in recent years, in learning to want to be where I should be — by discovering that, in certain ways, the outdoors is where I belong, and that sometimes walking and running and biking are particularly rewarding ways to be there. I don’t know if it’ll work for you. But at least it can be pleasant; it can be a positive experience that might evolve into something more.

This post discusses my first (and hopefully my only) experiences with heart problems related to distance running. (Update: spoke too soon: second episode came three years later. See below.)

I hope it is helpful. Please feel free to add comments as appropriate.

Contents

Background: Prior Adverse Experiences
A Visit to an Arkansas Hospital
Solution to an Intensifying Situation: Atrial Flutter
Two Distinct Problems?
What Caused the Atrial Flutter?
Distance Running as a Potential Cause
Conclusion
Updates
Alcohol and Atrial Flutter
Distance Running
Self-Cardioversion Through Exercise
Self-Cardioversion via the Light Socket
Research Report Update (July 2017)
Subsequent Research

.

Background: Prior Adverse Experiences

One day circa June 2009, I was running in Indianapolis. At that point, I was 53 years old. The temperature was somewhere in the mid-80s, and it was probably pretty humid. I had only gone a mile or two from home. In those days, I was used to running distances of at least six to eight miles. Suddenly I felt uncomfortable. The discomfort was in my chest. It wasn’t super-alarming. It didn’t feel like a sharp pain or a crushing pressure; it wasn’t radiating out to my arm. There’s no evidence that it was a heart attack, and it didn’t feel like a heart attack. It just felt unusual, a sort of full feeling. It didn’t feel right at all. It was odd enough that, as you see, I remember it. On that occasion, I turned around and walked toward home, resuming a jog after a few minutes.

For a long time, I thought that experience must have been due to the heat. But then I ran on plenty of other hot days after that. In fact, during 2011-2012, I was living in rural northern Indiana and doing runs of 10 to 15 miles, two or three times a week, along with a fair amount of biking. Some of those runs were in temperatures over 80, with heat index readings well over 90. I was fine. There was no recurrence of the chest issue.

I believe the next time I experienced it was in fall 2012. I was in a very stressful situation of teaching a course in statistics to approximately 30 recalcitrant undergraduates at the University of Arkansas.  I was taking Zoloft (sertraline), an SSRI (a common type of antidepressant). There was a possible parallel here:  I think I had also been taking Zoloft or Prozac around the time of that chest event back in 2009, give or take a few months, due to experiences of significant harassment during my PhD studies at Indiana University. I had also taken Inderal (propranolol), a beta blocker used off-label for stage fright, in both of those time periods. I was not taking such medications during that 2011-2012 period of happy running in northern Indiana. In other words, it seemed that extended, intensive stress and/or use of beta blockers or SSRIs may have been responsible for inducing that experience of chest pressure while running. (I did not run on the days when I took propranolol.)

In Arkansas in fall 2012, the problem was more obtrusive than it had been back in Indianapolis. I mean it was happening repeatedly now, and sometimes the symptoms were somewhat more worrisome. There was, I think, only one occasion when it seemed that this pressure in my chest was accompanied by a bit of pain near my upper arm. But there were multiple occasions when I had the same basic sensation of my chest being tight. As in the Indianapolis setting, it would set in within a mile or two after I had left home. But for the most part it was still not happening regularly; there were just a few incidents here and there.

The situation continued intermittently into 2013, after I stopped teaching and stopped taking Zoloft and propranolol. So if intensive stress and/or these medications were the cause, it would seem they were the cause only in a precipitating sense: they may have started the cart rolling downhill, but were perhaps not necessary to keep the thing rolling thereafter.

Note that I have never had heart problems otherwise. The chest tightness feeling did not occur when I was going about my ordinary day. If I hadn’t been running, I might not have experienced it at all. I would occasionally get lightheaded from standing up too fast, but I had had that previously. I attributed that to somewhat low blood pressure brought on by athletic conditioning.

A Visit to an Arkansas Hospital

My doctor at the Pat Walker Health Center at the University of Arkansas was a married Muslim woman named Dr. Huda Sharaf. Now, I have nothing against doctors, Muslims, or married women. But why they assigned me a doctor who was neither willing nor religiously able to perform a physical checkup on a male patient, I am not sure. If you want to be a doctor, you have a job to do. I would have been glad to let the health center restrict her practice solely to women, if that was the only practice she was able to undertake competently. It seemed that the health center was promoting a message of diversity at my expense. Thus I went for some additional months without a physical checkup, having already gone several years without one.

I mention Dr. Sharaf because, as in the physical checkup, so also in this matter of chest pressure. Instead of getting her hands dirty, metaphorically speaking, she simply told me that I should take my heart and go to the hospital emergency room. I seemed to be on my own.

So that’s what I did. This was in fall 2012, during that stressful teaching semester. When I arrived at the emergency room at Washington Regional Medical Center in Fayetteville, they wouldn’t let me in. I mean I walked up to a door and couldn’t figure out how to open it, and the people on the other side ignored me. Finally I hit a red button and a very loud buzzer went off. Doors opened and everybody stopped in their tracks and stared at me. Oops: it seems I had come in through the ambulance bay. Well, they could have benefited from a sign, or at least from the courtesy of directing me toward the preferred door.

Having survived that initial entry, I sat around and waited, and then eventually they had me do an exercise stress echocardiogram, commonly called a “stress echo.” The idea here is that they wire you up, put you on a treadmill, and make it go faster and/or at a progressively steeper climbing angle, until your heart begins to misbehave. At that point, they can see what’s going wrong, there on their screen, and anyway you are fainting or clutching your chest or whatever. When that happens, the technician yanks you off the treadmill, plops you down on the bed, and rubs your chest with an ultrasound probe, comfortably massaging your groin with her elbow in the process, as the technician did on the one previous occasion when I’d had a stress echo, in the hospital at Indianapolis after that first episode.

In this E.R., they did not massage my groin. They also did not keep me on the treadmill long enough for anything to happen. I told them that it was too soon to quit, that I just needed to get a little more warmed up. They could have increased the climbing angle on the treadmill.  At this particular point in the semester, I was having these episodes often enough to be reasonably confident that a serious workout would soon give me that experience of chest pressure. As a doctor in that hospital later admitted, those E.R. technicians should have stuck with it. But they didn’t have to. Apparently they had done what the rule book required, and were now entitled to a coffee break. So the stress echo showed nothing amiss.

The next step in their treatment was, of course, to keep me under “observation” for hours, attempting if possible to stretch it out into an overnight stay, so as to maximize insurance reimbursement. A nurse (paid on commission, it would seem) was virtually pleading with me to remain there, warning me in stern terms that I was risking my life by leaving. I did not see how that would be the case, given that I had actually been living for a number of years at this point, mostly without medical supervision, and even the chest pressure thing was only an issue when I was running, which I did not plan to do that evening anyway. It might have been different if the stay had been comfortable, but lying around on a gurney with things stuck in your arm is not ideal.

In short, the visit to the E.R. was a complete waste of time. Or it would have been, but for one thing: I learned something. I had learned the word “bradycardia” or simply “brady” while watching the “E.R.” television series, back in the ’90s. The nurse, intermittently glancing at my instrumentation during those hours of semi-napping on the gurney, said “brady” at one point, reminding me of the word, and her observation was accurate: my pulse was dipping down below the 40-beats-per-minute level. I was used to a resting heartrate of between 45 and 55, from those years of running, but a heartrate approaching 35 was new. So when I got home, I did a search, and learned more than they seemed to be registering at that hospital: my bradycardia might be a side effect of my SSRI usage, raising in turn the possibility that the Zoloft was also complicit in the chest pressure issue. None of the doctors in Arkansas had showed any sign of considering that, even though I had repeatedly told them that I was taking Zoloft.

Although one can’t be sure, I had to wonder whether any of those doctors were deliberately avoiding the potentially low-tech solution of telling me to find an alternative to Zoloft. That question came to mind because of what happened next. I called the hospital and insisted that they give me another stress echo and, this time, do it right. They refused. Instead, the lady recommended that I speak with Dr. Brandon Scott (would you believe B.S.) Chism. Dr. Chism felt that the test had been a false negative — that is, it failed to detect the existence of a real problem. I agreed with that; this is why I wanted it redone. His solution was, instead, to insert a needle into my groin (what is it with my groin, anyway?) and snake a camera up into my heart and look around. And that is what he did, in January 2013.

By that point, I should have demanded a change of primary care physician in the university’s health center. Because when I did finally get transferred to another doctor there, his reaction was that Chism’s procedure was extremely invasive and, you guessed it, unnecessary: Chism did not, in fact, find the “right coronary artery disease, with significant collaterals” that his records say he expected to find. Oops. Well, fortunately that fishing expedition only cost twenty thousand dollars — which I might have been willing to overlook, but for the other problem: we had still not made the first step toward figuring out why I was getting chest pressure while running. His focus on the right side of my heart seems to have been complete fantasy: as far as I know, nothing suggested anything wrong on the right side.

I might have been even less happy with Chism’s approach if it had resulted in a MRSA infection, heart or kidney damage, or other side effects that people can get from that specific cardiac catheterization procedure or from invasive procedures generally. Or perhaps I did develop a serious side effect . . . but let us not get ahead of the story.

Solution to an Intensifying Situation:
Cardiac Arrhythmia: Atrial Flutter

What happened next was that, basically, I went back to life as usual, with occasional chest pressure that would interrupt a day’s run. This happened now and then through 2013. I did not, and do not, know why it would happen on some runs but not others.

In mid-November 2013, I found myself in San Antonio, Texas, and now suddenly I had major back-to-back interruptions of my runs, two or three in a row. Possibly I would have learned more about that if I had continued running, but at this point I inconveniently pulled a calf muscle, forcing me to walk (at best) for six weeks.

When I did finally resume running, around Christmas 2013, the world changed. On my first attempt, I discovered that this guy who had been able to run 20 miles was unable to run a quarter-mile without being very short of breath, to the point of being on the edge of passing out. Something was very wrong.

Given my underwhelming experience at Arkansas, it seemed potentially counterproductive to go to the hospital. Instead, I attempted to work through this on my own. I changed my diet, which was probably just as well. I started taking iron pills again, reasoning that it seemed my brain was not getting enough oxygen. I thought, well, I’m getting older; maybe I am just learning that in the future it will be harder to bounce back from interruptions, such as this recent six-week layoff due to a sore calf. I got a health club membership and started walking on the treadmill, trying to make a comeback.

Wrong hypothesis. I was not a creaking old man who needed to tiptoe his way back into the pink. In March 2014, having exhausted my various hypotheses and experimental efforts to resolve the problem myself, and fearing that the situation might actually be getting worse, I checked into the emergency room at University Hospital in San Antonio. There, the diagnosis was quick and convincing: I had atrial flutter.  (Note that this is not the same as atrial fibrillation. I say that because I ran into a hospital technician or nurse, can’t remember now, who seemed to be confusing the two. They do not necessarily call for the same treatment or have the same outcomes.)

The flutter was obvious immediately: I told the people in that E.R. that I was having mild chest pain (which had been the situation, off and on, throughout recent weeks); they hooked me up to an EKG; and there, sure enough, was what someone called a textbook case of atrial flutter’s sawtooth wave, illustrated in this image from someone else’s EKG.

x

This explained why the heartrate monitor that I had borrowed from a friend was reporting that my heartrate shot up to 160, 200, even 240 (which was, I think, as high as it would go) after a few minutes on the treadmill: it was counting many of the little sawtooth points as separate heartbeats, when only the big pulses should have been counted. Possibly a better monitor would be able to differentiate that.

Two Distinct Problems?

When and why did I get this? The answer to that question depends on what “this” is. If we are asking about the whole collection of chest episodes, going back to Indianapolis, that’s one thing; but if we are asking about just the onset of atrial flutter, that is a different matter.

In other words, it seems I may have had two different problems. First, there was a problem, presumably with my heart, that started in Indy, went unresolved in Arkansas, and continued into 2014. That problem did not absolutely prevent me from running; it would just crop up when I was a mile or two from home, forcing me to abort my run and instead walk or jog back home. Then, sometime after I pulled that calf muscle, in the last weeks of 2013, I got a second and more threatening problem, or perhaps I entered a more aggravated state of the previous problem, where now I could not even get a quarter-mile from home, never mind several miles, without being lightheaded and extremely short of breath.

Between those two problems, the second one was due to atrial flutter. Whether the first problem was also due or related to atrial flutter, I was not sure. It could be that what I experienced in Indy was just the first hint of what would later become atrial flutter; or it could be that the emergence of the atrial flutter pushed the earlier problem into the background.

Once I received treatment for the atrial flutter, the question was whether the prior, possibly underlying condition had been fixed too, or whether it was still lying in wait, ready to return when the conditions were right. If there were indeed two problems, it seemed that, one day, I might once again have that chest pressure issue. At this writing, I was not sure how that might turn out.

So let me wrap up the story about atrial flutter. As I understand it, those mini-heartbeats frustrate the heart’s effort to clear the left atrium (i.e., the upper left chamber of the heart) with each beat. Some blood can linger. Over time, it can form a clot; and if things go wrong, pieces of that clot can go drifting around and cause a heart attack, stroke, or pulmonary embolism.

For atrial flutter, the recommended solution is electrical cardioversion (i.e., defibrillation) — shocking your heart with paddles, like on TV — so as to reset its rhythm. They do this in concert with (a) blood thinners and (b) a periscope, which they put down your throat while you are under sedation, so as to conduct ultrasound observation before, during, and after the cardioversion procedure.

Somewhere, I saw an indication that the odds of success — of your heartbeat remaining normal after being shocked — diminish as time goes by. The concept seemed to be that the flutter wears your heart down and introduces potential complications. You are apparently best advised to jump on it immediately, within hours or at least the first few days after the flutter begins. If you do that, your cardioversion procedure would apparently have somewhere around a 70% chance of fixing the problem for a year or more, if not permanently. But if you let it go more than several days before seeking treatment, as I did, your odds would drop to around 50%.

In my case, unfortunately, I wasn’t sure when the atrial flutter had begun, because I wasn’t running due to that pulled calf problem. I never noticed the flutter per se — no palpitations or anything like that — and I didn’t notice any effects, either, when I was just going through an ordinary day. It took exercise to bring it out. And then, when I did finally see that something was seriously wrong with my running ability, I tried home remedies instead of dashing off to the E.R. (Note that I did not have insurance, Texas did not have Obamacare, and thus, given my budget, a medical emergency sufficient to attract the attention of the E.R. was needed before I could get treatment.)

There was an alternative to the electrical approach: I could have sought cardioversion via medications. But it sounded like they were less effective and had more pronounced side effects. If the flutter returned after cardioversion, the next step would apparently be cardiac ablation, where they zap a tiny part of your heart so that it cannot flutter anymore. Some kinds of ablation can apparently require the person to wear a pacemaker, but it sounded like the kind they would use on me would not tend to have that effect.  Incidentally, links between arrhythmia and mental health could also call for the use of yoga and other mind-body treatments (see e.g., Lakkireddy et al. 2013; Patel et al. 2013).

My cardioversion procedure went swimmingly. They did an excellent job, with no apparent side effects. I came up to a new start in life. After a few post-procedure weeks on blood thinners, I was back to running, and once again it was the old familiar feeling of floating along, not that ragged struggle for breath. Two months after the procedure, I achieved my fastest time ever for a 16-mile run. (The longer runs were harder in a sense, but less stressful. I was still in 24- and 25-minute territory for three-mile runs, a far cry from the 22-minute pace I had been running a year earlier.)

What Caused the Atrial Flutter?

Again, then, the question: why did I get this? To answer the question the Texas doctors kept asking, there was no history of heart disease in my family. There was a question of whether the pulled calf muscle was somehow the cause of, or otherwise related to, the heart thing — whether, I think, the muscle may have generated a damaging clot; but apparently there was no finding of clots anywhere. (Later, I would wonder whether malfunction within the calf — in its role as a sort of secondary heart, contributing to blood circulation through the legs — was somehow responsible for corrupting the heart’s own rhythm.)

There are numerous possible causes and risk factors for atrial flutter. A search led to websites naming heart disease and abnormality; heart surgery; causative disease (e.g., lungs, thyroid, lymphoma); various substances; stress, anger, and anxiety; age; and high blood pressure. In the area of substances, the focus is on smoking, binge drinking, alcoholism, certain drugs (e.g., amphetamines, cocaine, marijuana), excessive caffeine, and certain medications. Olshansky and Sullivan (2014, p. 5) added several items to these lists, including steroids, hormones, marijuana, and diuretics. Van der Hooft et al. (2004) added reports of many others, including pseudoephedrine (e.g., Contac, Sudafed), sildenafil (e.g., Viagra), steroids, niacin, and calcium. MedFacts offered reports on many medications as possible causes of atrial flutter (e.g., Cialis). One intriguing addition not mentioned in those sources: air pollution. Somewhere, I also saw indications that shortages of certain minerals, notably magnesium and potassium, could be contributing factors.

As hinted above, the only items from those lists that had any apparent relevance were age, stress, Dr. Chism’s heart procedure, medications and minerals, and possibly air pollution. I started taking magnesium and potassium; no clue as to whether they would actually help. Stress did not seem to be the obvious cause of the severe breathing problem around Christmas 2013. Maybe stresses that would not have affected me at a younger age did have unusual impact at my advancing age. I was having some stresses around that time. But no specific incident came to mind as the likely cause of the atrial flutter.

I did wonder whether an adverse encounter with double red blood cell donation, back in March 2013, might somehow have caused some damage or imbalance that would have resulted in a more intensified heart problem eight or nine months later. It seemed unlikely; I mention it merely because, at this writing, I did not yet have good answers. I did not want to rule anything out prematurely.

I do not know whether Dr. Chism’s procedure in Arkansas, occurring in January 2013, could have been a contributing factor. There were websites (from e.g., U.S. News and Florida Hospital Medical Center) indicating that his cardiac catheterization procedure could introduce new and potentially serious cardiac arrhythmias (i.e., departures from sine-wave (a/k/a “sinus”) rhythm). I don’t know whether Dr. Chism’s team took an EKG after completion of his procedure (the hospital declined to include EKG printouts when responding to my request for medical records), or how long after such a procedure one would have to wait to be certain that there were no lingering effects from the procedure. My guess is that it would be possible to introduce an irregularity in the heartbeat that would remain latent or ineffectual until compounded by some subsequent stressor. If any portion of the heart or its rhythm was impacted by the procedure (regardless of whether that damage would have been minor or unnoticed at the time), it seemed that might later ratchet up into full-blown flutter if provoked.

Turning to the question of medications, it had been a year since I had taken any SSRIs. I took Cialis just a few days before the running episode around Christmas 2013, when I was unable to run a quarter-mile without being short of breath.  As noted above, that episode was the first time I had tried to run since pulling the calf muscle in November. I don’t know whether I would have had a similarly severe breathing problem if I had tried running a week or two earlier — on, say, December 15.

I took the Cialis, around Christmastime, because of erectile dysfunction, of course, and that was unusual: it had been a half-year since I had previously taken it, and I took it on that earlier occasion due to unrelated issues in a particular relationship, not due to chronic erectile dysfunction per se. When I took it around Christmas 2013, there was a question of whether my erectile dysfunction and loss of libido were due to a possible worsening of the medical condition that had given me that feeling of chest pressure intermittently throughout the past year — worsening, I say, because of those back-to-back aborted runs in November. I would have been more convinced of a role for Cialis if (a) it had been involved in those earlier episodes and (b) it had better odds of being a real factor. MedFacts indicated that there was only about one case of reported atrial flutter for every thousand men taking Cialis, and those were self-reports, not generally investigated.

Air pollution (or perhaps some kind of dust or pollen) would have been a more plausible cause if I had had the adverse running experiences only in one area, or only in large cities; but the sources I saw required the pollution to be intense, and that did not seem to be the case in any of my residences in recent years. Moreover, I had had such episodes in Indianapolis, northwest Arkansas, and San Antonio, representing three substantially different kinds of climate. There was nonetheless a considerable contrast, in that regard, between those experiences and the experiences I had while running in rural Indiana (above) and also in rural Kansas in fall 2013: in the latter, I had no adverse cardiac episodes. So it was possible that the more built-up areas did share an airborne aggravant, such as a particular emission from car exhausts, that was absent in those rural runs. Here, again, it remained up to me to figure it out; Dr. Chism showed no signs of investigating such factors.

In the second episode of atrial flutter, three years later, I did have a potential cause not related to distance running. Indeed, its timing made me wonder whether distance running was actually protective. In both cases, I first noticed the atrial flutter after weeks in which I was not engaging in physical activity. This downtime was due to running injuries — specifically, to calf problems. I wondered whether the running was actually protecting me from heart problems. It may have been insulating me from stress; it may have been helpful in regulating the timing of my heart, possibly through the calf’s function as an assistive blood pump (see other post). Or possibly I had developed a physical addiction, such that stopping running was dangerous as in some other addictions. It did seem mildly suspicious that, after periods of years of running with no heart problems, I had heart problems during two periods (among many) when I was not running.

It was difficult to know exactly when these two episodes commenced because, as I say, I was not running at the time. First time around, I was not able to confirm a specific date when the atrial flutter commenced, in the period of perhaps six weeks before I made a first post-injury re-try at running and did finally notice that something was seriously wrong with me. The same is true of the second episode, except that one thing did catch my attention. I went for a bike ride one night, for the first time in several weeks, and that’s when I noticed the unusual weakness, lightheadedness, and breathlessness that, again, would turn out to be atrial flutter. Later, as I attempted to reconstruct events preceding that incident, I recalled that, on that very day, I had used Black Flag Flea & Tick Spray rather intensively, to spray down a staircase in a house that had been infested by fleas. I was coughing throughout the entire spraying. I looked up the ingredients on that product. They included Nylar, lambda cyhalothrin, and pyriproxyfen. I did not investigate this extensively, but a brief search led to a Cornell webpage that said this:

In addition to the corrosive effects to skin and eyes, other acute effects due to exposure to lambda cyhalothrin, like those of other pyrethroids, will be mainly neuropathy (effects on the nervous system). Cyhalothrin may act on ion channels within the nerve cells (neurons) to disrupt proper function of the cells of both the peripheral and central nervous systems.

Since atrial flutter is an electrical rather than plumbing problem, so to speak — involving a problem with the nerves, that is, rather than the valves and arteries — it did seem that the spraying could have triggered the atrial flutter in that instance. If so, there would remain the question of whether exposure to some similar pollutant was responsible for the first instance.

Distance Running as a Potential Cause

During my research into this issue, a Google search led to multiple articles raising the question of whether excessive exercise can be unhealthy. One such article, appearing in the Wall Street Journal in May 2013, alluded to a recent study suggesting that the health benefits of running may be reversed when one exceeds 30 miles per week, and that serial marathoners may accrue elevated levels of coronary plaque. Gallo et al. (2012) said that injury rates rose significantly above 40 miles per week. My own running was not at that level: my longest run, 23 miles, had been back in 2011, and more recently I was tending toward one run of 12 to 15 miles every five days or so, with shorter runs of one to three miles on most other days.

In a study cited in that WSJ article, people who survived heart attacks were found to benefit from increased running, but only up to a limit of 4.4 miles per day. Another article, in Science Daily, summarized a study finding that marathon running introduced reversible damage in amateur marathon runners who were not especially fit or prepared for that long run. Taking a more antipathetic stance, Jang and Park (2016) offered a veritable laundry list of pathologies arising especially for marathoners:

Long-distance running has been implicated as a cause of various cardiovascular and gastrointestinal disorders or abnormalities, such as iliac artery endofibrosis [7,8], lower leg artery stenosis or occlusion [9], arterial dissection [10], left sided ventricular hypertrophy [11], increased vascular compliance [12], ischemic colitis [13,14], hyponatremia [15], myoglobinuria, increased troponin, leukocyte abnormalities [16], coagulopathy and sudden death [17]. . . . Arterial wall ischemia as a result of long-distance running may cause lysis of the media or an actual vascular necrosis with eventual aneurysmal change [18].

The WSJ article also acknowledged, however, that other studies — “compelling evidence,” in the words of one researcher — showed steadily increasing benefits from increased exercise. An article in Runner’s World contended that, in fact, the research underlying the WSJ article did not at all support that article’s negative remarks about distance running. While this sort of bias might be expected from Runner’s World, the argument did convincingly quote the authors of that underlying research for this statement: “We were not able to identify an upper limit of physical activity, either moderate or vigorous, above which more harm than good will occur in terms of long-term life expectancy benefits.” That seemed to be a fairly damning rebuttal.

But could running generally, or distance running in particular, be a cause of atrial flutter? One blogger seemed to think that “a quick five-mile run in the thirty-third day” after electrical cardioversion (i.e., having his heart shocked, above) was the cause of his return to a permanent condition of atrial fibrillation — which he thereafter just ignored, reconciling himself to a slower running pace (!). Another runner said, “I found that running a slow 6 miler on 2 consecutive days would convert me back to NSR (normal sinus rhythm) during or within a few hours after the second run.” Undeniably hardcore. (See also McCullough, 2014.)

More scientifically, a study by Mont et al. (2009) concluded that, after adjusting for other risk factors, long-term endurance sport participation increased significantly (up to 7x) the probability of experiencing atrial flutter. The left atrium, which Mont et al. said was enlarged in up to 20% of competitive athletes, was the one that was fluttering in my case. On the other hand, Barry and Franklin (2013) found no significant cardiac arrhythmia risk increase for increased running distance or intensity. (The Arkansas doctors recorded that my heart was enlarged, not specifying a particular atrium or ventricle. To my knowledge, they did not draw any useful conclusions from that observation.)

An American Heart Association webpage made the enlarged heart condition sound pretty dire, with remarks about heart failure and pacemakers. It didn’t really seem applicable. One part that did seem relevant to me was the statement that an enlarged heart is likely to experience arrhythmias. Atrial flutter is a kind of arrthythmia. The idea would apparently be that I had an enlarged heart, presumably due to running, and that caused the atrial flutter. A Mayo Clinic webpage said that the cardiologist’s mission would be to treat the enlarged heart as a symptom of an underlying cause, and address that cause; but I thought I had seen somewhere that the cause is often unknown.

It sounded like I had an enlarged heart because I was an athlete, as that term may be defined in one’s mid- to late 50s, and thus the underlying cause did not need to be treated, because athleticism is generally healthy. So in my case, evidently the doctors were just going with it, leaving the heart to do its thing, and treating any ensuing arrythmia as a by-product of generally healthy exercise habits. I could not easily gainsay that logic. I had no way of knowing whether my heart would stop being enlarged if I stopped running, or if I pared the running back to shorter distances or slower paces. Some sources did seem to find real benefits from strenuous exercise, not that my long runs were usually very strenuous.

Conclusion

My reading suggested that I was surely in a different category from, say, Dean Harper, whom one website described as a world championship triathlon winner in the 55-59 age group who engaged in more than 25 hours of intense training per week, and who had been reaping adverse heart-related consequences for more than 20 years. My running was for the purpose of going out and cruising around, enjoying myself and seeing new sights, or just being among the wheat fields and woodlots for a few hours now and then. I did have some heart issues, but (a) even at their worst, while impairing my running, they had not otherwise impacted daily life, and (b) they seemed, at this writing, to have been resolved.

In the end, I didn’t particularly want to run marathons. I wanted to get a good running backpack and go camp-running, heading down the road for a few days or weeks, reminiscent of my camping trip, so as to sleep in my tent, read, meet people now and then, and simply be outdoors. For that purpose, I learned something from this research. For some of us, the end of competitive or even respectable athletic performance may come, not because we are at all out of shape, but just because aging brings a greater likelihood of things going wrong, whether because of our own deterioration or because of the cumulation of helpful and harmful medical interventions. Termination of one’s strenuous exercise potential may be regrettable and undesirable, but in this light there is at least a certain normalcy or probability in it.

Updates

Further research (in some cases stimulated by readers’ comments, here and in a related post) has encouraged the following additions and corrections to some of the foregoing remarks.

Alcohol and Atrial Flutter

I said (above) that causes of atrial flutter could include alcoholism and binge drinking. But other sources expand upon that. Dr. John M (2010) suggests that

Some patients develop arrthythmia after only one drink . . . . For some, even small amounts of alcohol can induce firing [of trigger sites in the heart’s atria as well as] . . . an “on alert” state of high adrenaline, as well as impaired sleep [all of which favor atrial fibrillation (AF)] . . . . Alcohol is clearly associated with AF. The threshold amount of alcohol is not known. . . . [A] trial of abstinence from alcohol seems to be a good idea. (As well as other important lifestyle modifications, like improved sleep and stress reduction.)

A search led to an article by the American College of Cardiology (2014) that said, “Any disturbance of atrial architecture potentially increases susceptibility to AF [i.e., atrial fibrillation]. . . . Extracardiac factors that promote AF include hypertension, sleep apnea, obesity, use of alcohol/drugs, and hyperthyroidism.” Among the three sources cited in support, two were older, but one was a relatively recent meta-analysis by Kodama et al. (2011). That article said,

AF risk increased with increasing levels of alcohol consumption. . . . [Our] analyses suggest no evidence that moderate alcohol consumption is beneficial in ameliorating the risk of AF . . . . If anything, moderate alcohol drinkers may have a greater risk of AF than nondrinkers, although the AF risk is not as large as that for heavy drinkers. . . . [N]ot consuming alcohol at all is the most favorable behavior for avoiding AF . . . .

The search turned up another meta-analysis, by Larsson et al. (2014). As a nonsubscriber, I did not have access to the full text, but the abstract said this: “These findings indicate that alcohol consumption, even at moderate intakes, is a risk factor for atrial fibrillation.” While these studies focused on atrial fibrillation rather than flutter, a WebMD page said, “Atrial flutter is closely related to another arrhythmia called atrial fibrillation.”

Distance Running

On this, Dr. John M said, “[I]t is now clear that endurance athletes are at increased risk for AF.” A search led to an article by Leischik et al. (2014) reviewing many possibilities and unknowns in heart issues for endurance athletes and noting that “There is strong evidence that athletes have higher incident of atrial fibrillation and bradyarrthythmias increasing with age.” Redpath and Backx (2015) found, moreover, that

Endurance exercise, despite a plethora of proven health benefits, is increasingly recognized as a potential cause of lone atrial fibrillation. Moderate exercise reduces all-cause mortality and protects against developing atrial fibrillation. However, more intense exercise regimes confer modest incremental health benefits, induce cardiac remodelling and negate some of the cardiovascular benefits of exercise. . . .

Repeated strenuous endurance exercise overloads atria, resulting in stretch-induced ‘microtears’, inflammation and endocardial scarring. . . .

Currently, it is not known whether a ceiling for endurance exercise exists, and, if so, what factors determine the threshold of harm.

Myrstad et al. (2014), studying 3,545 men aged 53+, concluded that “cumulative years of regular endurance exercise were associated with a gradually increased risk for AF and atrial flutter.” It appeared, in short, that risks of cardiac arrhythmia probably did increase with age, running distance, and running intensity. Not to downplay that: in these and other materials, there were occasional references to sudden death episodes. Given the indications that the exercise benefit curve might turn negative beyond a certain point, it seemed that I might want to think of distance running as being a little less like exercise and a little more of an extreme sport, indulged not for its health consequences but, rather, despite them.

Self-Cardioversion Through Exercise

Some may be interested in a letter to the New England Journal of Medicine (Ragozzino, 2002). This letter describes the case of a physician who experienced atrial fibrillation (AFib) at age 45 and fixed it, by himself, through exercise. On 30 different occasions over the following eight years, he brought himself out of AFib by working out, using either a cross-country ski machine or an elliptical trainer. Each of these workouts lasted between 20 minutes and 240 minutes. He commenced each of these workouts within 48 hours (in some cases, as soon as one hour) after going into AFib. To get out of AFib, he apparently had to bring his heartrate to at least 160 beats per minute. It is not clear, from the article, how long he had to sustain that heartrate; presumably he was not able to maintain it for four hours straight. The article does say that he continued despite dyspnea (i.e., labored breathing). Note that his was paroxysmal lone AFib, which one source describes as AFib without any heart abnormalities or heart disease. Possibly this treatment was one way of bringing about what another source mentioned: “Speeding the heart rate can sometimes pull a vagal afibber out of AF.” This would not necessarily relate to atrial flutter, though.

Self-Cardioversion via the Light Socket

A report from the Brits:

A 64 year old man had been treated for six years for [irregular heartbeat] . . . .

He decided to put up some shelves at home. As he drilled the necessary holes in the wall, the tip of the drill bit came into contact with a mains electric cable (240 volts AC) within the wall. The shock lifted him off the stool on which he was standing and deposited him in a dazed state on the floor. His wife, a nursing sister, found his pulse to be present and regular. . . . The drill bit was ruined. . . .

We recommend that, even where there is a waiting list for elective DC cardioversion, this is not something that patients should try at home.

Research Report Update (July 2017)

Allan et al. (2017) unexpectedly found “some evidence that white ethnicity, taller height, lower total cholesterol and lower diastolic blood pressure might confer a higher risk of incident [atrial fibrillation], which is in the opposite direction to their known associations with incident [coronary heart disease].” In other words, being a tall, skinny white guy with low total cholesterol and a blood pressure reading below 80 on the second of the two (e.g., 120/79) could increase your risk of having at least an AFib episode. Seemingly contrary to that, Foy et al. (2016) found that obesity is associated with atrial fibrillation.

The Mayo Clinic said other cardiac and even non-cardiac (e.g., lung, kidney) conditions were also associated with AFib, as were alcohol and family history. Another factor: long work hours, according to Kivimäki et al. (2017). They found that people working 55+ hours per week were 40% more likely than people working 35-40 hours/week to develop AFib.

On the question of whether distance running or other endurance sports could contribute to heart arrhythmias, a search led to a seemingly increasing number of studies raising concerns. Rosin (2017) provided his own account of a 45-year observation of his own group of older distance runners, concluding that

[A]t least in some populations, years of high-intensity, prolonged exercise may not be as toxic as suggested by others. Whether this is due to self-selection or predisposition is not well understood but merits further study.

In other words, maybe intense running over a period of years is not problematic, or maybe it’s just that the strong survived. Calvo et al. (2012) said,

There is growing evidence that long-term endurance sports participation can result in cardiac structural changes and alterations in the autonomic system, which can result in the initiation and maintenance of [AFib and AFlutter] . . . . Reducing sports activities may need to be considered as part of the therapeutic advice to minimise the risk of AF or AFl development in endurance athletes.

Similarly, Lee et al. (2016) concluded,

Some evidence suggests that years of endurance training can lead to long-term adverse consequences, including myocardial fibrosis, atrial fibrillation, an exercise-induced acquired form of arrhythmogenic right ventricular cardiomyopathy, ventricular arrhythmias, and coronary atherosclerosis. The law of diminishing returns appears to apply as exercise extent increase, and it is likely that an upper limit exists where additional physical activity provides no further mortality benefit.

In another article, Lee et al. (2017) said,

There is compelling evidence that running provides significant health benefits for the prevention of chronic diseases and premature mortality regardless of sex, age, body weight, and health conditions. . . . It is not clear, however, how much running is safe and efficacious and whether it is possible to perform an excessive amount of exercise.

The authors noted some research suggesting that 30 miles of running (or 47 miles of brisk walking) per week might be an upper limit, beyond which the costs start to outweigh the benefits — “although most studies indicate no harm or excess risk of mortality even at the extreme amount of running or aerobic exercise.” More worrisome was the remark of Gerche (2016):

[T]here is fairly compelling evidence to support the association between long-term sport practice and an increased prevalence of atrial fibrillation . . . . This article was designed to challenge the reader with speculative science that suggests that exercise might promote permanent structural changes in the myocardium which can, in some individuals, predispose to arrhythmias. . . . [S]ome recent results have brought into question whether the protective benefits of exercise on vascular events also extends to high-intensity exercise training.

The general conclusion seemed to be, in the words of one researcher quoted by the New York Times (Reynolds, 2017), “If you want to run a marathon, fine, run a marathon. But if your goal from exercise is simply to be healthy, a half-hour of jogging will do.” A half-hour of jogging, for most runners, would mean three to four miles per day, at varying degrees of intensity. Not to let an addiction make false excuses, but it did seem that, at least to somewhere around the 30-mile mark, running could actually help to reduce the risk of cardiac arrhythmia, at least to the extent that it would reduce stress and discourage overwork.

Subsequent Research

The New York Times (Kolata, 2017) reported that medical researchers (Cuculich et al., 2017) had successfully used radiation to provide relief to persons with atrial fibrillation that had resisted multiple ablation treatments. It appeared this treatment was only in the preliminary stages of being tested and refined.

A few years down the line, in 2019, my ideas and experiences on these matters had evolved somewhat, as outlined in another post.

I had been using a spreadsheet to log my running times and distances and to calculate related values. I was going to share it, and then it occurred to me that others have probably developed spreadsheets that might be superior to mine. I decided to look into that briefly. This post reports what I found.

A search demonstrated that, indeed, there were running log spreadsheets to be had.

My search led, first, to Minh Tan’s Advanced Excel 2003 Running Log, which looked pretty complicated (note the tabs across the bottom) and which his article explained in some detail. Next, I found an Excel 2013 Running Log template offered by Microsoft. Unfortunately, I did not have Excel 2013, so I passed on that one. Another option: Vertex42 Running Log: pretty, simple, and suitable for Excel 2003 and above. Then there was David Hays’ Running Log (password: dead), said to be in an older format, but which I had to save in Excel 2010 to avoid incompatibility errors. This one was extensive, with 17 tabs. Nuke Runner offered a modified David Hays spreadsheet and other tools in addition. Serpentine offered logs in Excel and in other formats for running and, like some of these other tools, for other purposes as well (e.g., diet, exercise). In a post on Runner’s World, Rob provided a relatively clean and simple Excel running log. Jill Barville provided a description of how to set up her running log, but not the actual Excel file. Spreadsheet Library offered a spreadsheet and also a pre-populated example and (would you believe) a training log and analysis video. Snikt Running offered an Excel download. So did David Underhill, with instructions on how to exchange data with Map My Run.

Speaking of which, I noticed that a friend used Map My Run. Note also the accompanying apps to automate the mapping process. (See e.g., Runtastic.) In a similar vein, Minh Tan (above) pointed me toward the Gmap Pedometer (a/k/a Milermeter), which I hadn’t used before. Now, testing it, I found it potentially more useful than Google Earth for offroad (e.g., trail) running, as long as I clicked on the Satellite option in the upper right corner of Gmap. I was not sure if this tool had a database that would save my results from one day to another: I tried setting up an account, but for some reason I was not able to log in, and I did not pursue it.

So those were a few of the results of my Google search. The search found about 6.8 million hits. I decided not to explore them all. It seemed, however, that there were dozens, probably hundreds, possibly thousands of running spreadsheets out there. The foregoing were only the top dozen or so entries in the search. In response to a comment (below), I have combined those spreadsheets into a single download available at the recommended SourceForge page and also at Box.com and MediaFire. See also my main downloads page.

Probably like most other spreadsheet composers, none of these other spreadsheets seemed as good, for my purposes, as the ones I had composed for myself. Mine were not nearly as good-looking as some of theirs. Also, mine could require duplicate entry of a few items, because each spreadsheet had a different purpose, somewhat incompatible with the others. There may have been a way to automate that, but I hadn’t gotten there yet.

What seemed to be needed was a group effort, a running log spreadsheet project, where features of different spreadsheets would be combined into one simple-for-the-public (and yet, perhaps, easily customizable) spreadsheet or database tool. So far, though, I was not aware of any such thing.

A few years back, I did a search for backpacks for runners.  I read a number of discussions on the subject, and then narrowed it down.  Since there are hundreds of models, I excluded packs with a wide hipbelt, women’s packs, packs over 30 liters, and packs over $100.  I eliminated heavy packs; the ones listed below are all in the one-pound range.  I eliminated most packs without at least a thin waist or tummy belt, on the theory that a load of stuff could swing around otherwise.  (I was not yet sure how much stuff I would ever want to carry while running, but decided to keep my options open.)  I tended to favor packs that someone – in the ad itself or elsewhere – described as a runner’s pack.  I searched out the Amazon.com listings for each pack, in hopes that this would give me more of a consumer’s perspective.

I eliminated most hydration packs, though possibly they would be fine with the bladder removed.   If I had needed to broaden my search to include hydration packs, I probably would have chosen either a CamelBak or a Salomon.  I also eliminated climbing packs.  The drawback of a typical climbing pack, for my purposes, was its lack of pockets to reach into while running. But I did consider these:

Black Diamond Flash
Black Diamond Bullet
Black Diamond Hollowpoint

I considered two Lowe Alpine packs, primarily when I was thinking I might want to carry a lot of stuff.  I rejected them because I had read several positive remarks by runners who had used Deuter Speed Lite packs.  I had already decided that Deuter would be the kind I would buy.  The two Lowe Alpine packs were:

Lowe Alpine Edge 20 Day Pack
Lowe Alpine Argon 25 Day Pack

The two Deuter choices were:

Deuter Speed Lite 10 Daypack
Deuter Speed Lite 20 Backpack

Between the two, the larger 20 still seemed suitable for running.  It would also hold more.  That would mean more fabric on my hot and sweaty back, but would also extend the tummy strap somewhat lower.  Its dimensions were only slightly larger:  19 x 10 x 7 inches, as compared to 16 x 9 x 5 inches for the smaller 10 Daypack, and presumably not all of that extra length and width would be against my back.  The manufacturer’s webpage showed its straps, with padding down most of the shoulder (a principal disadvantage of the cheap pack I was planning to replace).  The pockets looked a bit high, but accessible if I loosened or unclipped their water-bottle straps.  The other drawback of the larger pack was that it cost $20 more.

I wound up buying the Deuter 20.  I had it for a year or two.  It was a really nice pack.  I sold it just because I wasn’t likely to use it much in my new location.

I never did get around to camp running.  But I did try it out fully loaded and with additional gear bungee-corded to the outside of it, and it worked.  I was impressed with how well I could get it to lie snug up against me, not swinging around and yet not choking me with inconvenient tight straps across the chest.  Somehow it just fit.  I used it for hauling groceries from a store one mile away — carrying, for example, a gallon of milk along with a random load of other items.

* * * * *

Update (January 2023)

I recently tried a distance run with a loaded backpack. It wasn’t one of the models listed here – it was just a basic Outdoor Products pack from Walmart – but I was able to keep it from swinging around. It seemed to provide approximately the experience that I would expect from one of the packs listed above.

Things were fine for a while. Unfortunately, the route I used began with several miles of slight but mostly steady downhill. I had run this route many times before. The grade was slight enough not to cause problems. With the pack, however, problems did ensue.

About four miles out, I got a sudden, stabbing calf pain. I had to walk the rest of the way. As discussed in another post, downhill running was a prime cause of these calf pains.

As with those many previous runs, there was no such attack in a later run on that same route without a pack. It seemed clear that the pack was the cause.

What was less clear was exactly why. I did not think it was the weight. The pack did weigh about nine pounds, so that was possible. It also could have been that the pack induced a change in my running motion – though I think that would have manifested, first, in a joint (e.g., knee) ache.

My best guess was that the problem lay in the slower pace. I definitely was running slower with that weight on my back. I had noticed, in the past, that sprinting down hills tended to minimize calf attacks. I suspect there would not have been a problem on a more mixed route, as distinct from that steady downhill grade. If this was the explanation, a solution might be to walk on the downhill segments, continuously or at least at intervals, or to try to speed up on those segments despite the weight.