Male, 26, 5’9", 130lbs PRs: 5k 17:47 (2022), Half Marathon: 1:17:53 (2021), Marathon: 2:45:27 (2022) Next Races: Boston Marathon, Fall Ultra Future Goals: Sub 1:16 HM, Sub 2:40 Marathon, Sub 17:30 5k Miles = 71.1 Miles Elevation Gain = 1,114 Two workouts, changed my strength routine to a simple routine from Ben Barrows again. Split the Saturday run from a single to a double to get in family time. Feeling back again and at a good healthy weight and mindset for me. Enjoyed the month of serious training from running off and the festivities that usually ensue. Now it's back to the fun real grind. Hoping to get back into the 100s where I felt happiest within the next month or so. Goals coming up are a mile TT and then just keep on grinding towards Boston. Same goal as before, break 2:45. Did not get into Berlin so I'm thinking of foregoing a fall marathon 2023 and focusing on shorter stuff but signing up for a random ultra or two. JFK 50 is close to me and I wouldn't mind trying that or maybe a flat road ultra like Tunnel Hill. But a good friend created a group lottery entry into Leadville 100 and did not tell me . . . did it as a Xmas gift so, there's that possibility.
Monday -Rest Tuesday - PM Run: PM Run: 12 Miles - 7:20 Wednesday - PM Workout: PM Workout = 12 Miles = 3 Up - 7:28 , 12 x 1 min (11.1, 11.1, 11.2, 11.2, 11.3, 11.3, 11.4, 11.4, 11.5, 11.5, 11.6, 11.6) / 1 min (7.5) - 3.8 Miles - 6:19 , 5.2 Down - 7:18 Thursday - PM Run: PM Run: 12 Miles - 7:30 Friday - PM Run: 8.3 Miles - 7:55 Saturday - AM Run: 7.6 Miles - 7:54, PM Run: 5.3 Miles - 7:22 Sunday - AM Workout: 14 Miles = 7 Up - 7:16, 6 Mile Progression - 6:03 = 6:15, 6:10, 6:05, 6:00, 5:54, 5:47, 1 Down = 7:51
Have to ask cause I see it every week, the elevation. Seems rather negligible, at least from looking at my own logs. Columbus is relatively flat and I still get about 1400 ft of elevation over 56.
Wow, and I thought my most frequent route (from my house) was "flat"! According to my Garmin it's about 440 ft over 12ish miles.
Have to ask cause I see it every week, the elevation. Seems rather negligible, at least from looking at my own logs. Columbus is relatively flat and I still get about 1400 ft of elevation over 56.
Wow, and I thought my most frequent route (from my house) was "flat"! According to my Garmin it's about 440 ft over 12ish miles.
I ran every hill in my neighborhood and was able to get 548 ft of climb. Back home I'll get a couple hundred over the first couple miles of a run but I wouldn't call that area hilly either. lol
Wow, and I thought my most frequent route (from my house) was "flat"! According to my Garmin it's about 440 ft over 12ish miles.
I ran every hill in my neighborhood and was able to get 548 ft of climb. Back home I'll get a couple hundred over the first couple miles of a run but I wouldn't call that area hilly either. lol
Haha, nice! I have some massive hills near my house that I purposely avoid. I'm hitting the flattest route I can find without driving somewhere. Perhaps I should hit the steep stuff more often?
By the way, do you have a coach that OTQ'd last weekend? I saw something on reddit about it. If so, you are obviously in good hands!
Are you all using GPS watches to track elevation or measuring it in something like MapMyRun? My Coros seems super unreliable, giving my 12-mile loop with monstrous hills only a bit more elevation than the pancake-flat 7.5 miler
What Coros do you have? I have the Pace 1 and it is terrible with elevation. Typically the total elevation gain is correct but it gives 5x more downhill then actual. I run with my wife often so have a comparison (Garmin). I would hope the Pace 2 is better, I think the elevation tracking abilities of their more expensive watches are a selling point for them so I would hope they are much better.
I went higher end for some of the backcountry navigation features.
Just comparing with MapMyRun (which also isn’t perfect), my 12 mile loop read 771 on Coros, 691 on MMR. The flat 7.5 loop read 410 on Coros, 239 on MMR
i think Coros elevation is based on barometric pressure, so probably the error is relatively large on flat routes and relatively small on hilly routes.
Hills are something I really haven't experienced and ran with. Flat for me has been (for the last 2 years) maybe 100-200ft a 12 mile run. I'm lucky to keep it going and learn what I can consider flat and not flat.
I use my Garmin which must have changed something recently in the latest update because they elevation was always a few hundred feet different than Strava, now it's the same.
The altimeter or elevation measuring aspect of these watches is the least accurate of the functions. I use a Garmin and they are the “original” and so I have stuck with their watches for years. Your body will tell you how hilly a route is. And one does not have to be in the West to run hills. Most of the intermountain West sits on a 5,000 ft (or more) plateau and so there will be significant oxygen deficits to fight. But hills are hills and even those little rollers in the “flat” Outer Banks of coastal NC were giving me some fits. Those dunes are always tough and the running always seems difficult down there…
RS - Have you or Mrs RS ever run Chambersburg? Looks like an interesting spring half…hilly…
We have not, but looking at the last few years of results we have a lot of club-mates who have. I will ask them what they thought about it tonight at practice.
Looks like some decent runners show up, might be running solo for sections but not out of site of others. Last four years number of finishers 2019 to 2022: 226 197 209 135
I asked one of them last night, they said it was a good experience and that they would do it again. Not sure why the drop in numbers in the 2022 race. Looks like Master $ goes three deep.
I just use my Garmin watch and gives me nearly the exact same number everytime I hit a known route.
One BS check is to use Strava's Edit --> "Adjust Elevation". What it does is use the known GPS route to "correct" what the watch recorded. My previous watch was having big trouble recording elevation (it was obvious by looking at the elevation profile) and this "Adjust Elevation" feature brings it into line with what my current watch is now measuring on it's own. Currently using a Forerunner 255. I bought it for the Multi-band GPS feature.
BHV - Perhaps I should upgrade to a 255S, as I currently the 45S. The 45S really is a good watch, and the elevation readings are decent enough, but I never get the exact same numbers from known routes. If I had the $350, I would go for the 255S…
BHV - Perhaps I should upgrade to a 255S, as I currently the 45S. The 45S really is a good watch, and the elevation readings are decent enough, but I never get the exact same numbers from known routes. If I had the $350, I would go for the 255S…
Just looked at the last 3 times that I know that I ran from the same starting spot in my drive way to same ending marking on the road in front of my house (I'm not always that exact in my execution):- 440 ft, 443 ft, 440 ft. So pretty close!!!
I haven't checked the Multi-Band GPS accuracy. I know from some youtube videos some people have shown less "wandering" on the GPS map. That was the main reason I went with the 255. So theoretically, a more accurate estimate of distance and therefore pace. I believe the general idea is that it uses multiple signals and throws out a signal if it appears to be "bad" (collisions with trees, buildings or other objects) and keeps the "good" signal.
I ran every hill in my neighborhood and was able to get 548 ft of climb. Back home I'll get a couple hundred over the first couple miles of a run but I wouldn't call that area hilly either. lol
Haha, nice! I have some massive hills near my house that I purposely avoid. I'm hitting the flattest route I can find without driving somewhere. Perhaps I should hit the steep stuff more often?
By the way, do you have a coach that OTQ'd last weekend? I saw something on reddit about it. If so, you are obviously in good hands!
I'm trying to incorporate more hill running into this block but I can only running my neighborhood hills so much without going insane lol.
Yep! He ran 68:01-68:00. Over a minute PR and qualifies him to his second trials. Known him since our old Dyestat days. Should be jumping in some of the same races as him during this block. Needless to say we're all super happy for him!