A run not worth running?

I do not travel as much as some friends I know, but I am out of town about three to four times per year for conferences and other meetings.  These conferences have me flying to such far flung places as Washington DC, Asheville, Denver, and for this week, Louisville, Kentucky.  I always bring my running gear, and often use a run or two as a way to do some sightseeing, and get a feel for the city I'm visiting.  One of my favorite places to run while on the road is in DC; to run by and around the monuments, near the Potomac, and to get out to a relatively quiet part of the city (usually on the Rock Creek trail) is usually quite enjoyable.

However, sometimes a run on the road is just no fun.  I may be tired, jet lagged, or not eaten very well while in the hotel room.  This week was just such a run; I only managed 6 miles, and the entire run felt like a struggle.  The setting was nice--a well groomed river front trail provided a good sense of the city, an the footbridge over the river was a nice touch as well.  But, I felt more tired after this run that I usually do--runs usually perk me up and shake me from the work day.  It was not until I took a shower, grabbed a quick bite, and grabbed a quick drink (Kentucky is known for its bourbon, after all), and dinner with an old friend (and a couple new ones) did I perk up again finally.

Despite this struggle in this run, I am still glad I went out and did it anyway.  Why?  At this point, anytime I can spend outside, relaxing from the day, and moving is a good day.  If I learned anything from the Boston marathon incident, you never know when your next run will be your last.  So, I will take every chance to get out there, even if it is not the best run I have ever had.  A bad run is always better than no run at all!

The view of downtown Louisville from the footbridge