Sandra Vi going for record across America

So far today wrote:

Results wrote:

I've given up on paying much attention to Garmin since she decided not to use it properly.

Garmin is still useful because it shows when they start and stop running for a day. Yesterday, Mimi started an hour earlier than Sandy and ended a half-hour later. That is important to note.

Yes, and it's good for people who want to meet up with her. I didn't mean to suggest it's useless, just that it was better when she was using it to its full potential.

I see how you can tell the stopping and starting from breadcrumbs, but how are you getting distance? It doesn't record the mileage at a breadcrumb from what I can tell. So then you just plug the points into Google Maps or something?

Edit: Oh I see she's back to starting and stopping the Garmin. I stopped looking around the time she let it run for three days straight.

Results wrote:

Don't we have the overall times in the early runs with the Strava data? We could compare the two. it seemed to me that Marina got out of the gate very quickly. If memory serves, she was spending less time running and going very fast. It's true that no longer seems to be the case.

The Strava data only shows moving time, not overall time but we should be able to find the overall time on Movescount. It would be interesting to see some of the overall times for the earlier runs.

Results wrote:

If memory serves, she was spending less time running and going very fast. It's true that no longer seems to be the case.

Longer days and slower pace. And to keep the miles up she is taking shorter nighttime sleeps.

Scam_Watcheroo wrote:

Results wrote:

Don't we have the overall times in the early runs with the Strava data? We could compare the two. it seemed to me that Marina got out of the gate very quickly. If memory serves, she was spending less time running and going very fast. It's true that no longer seems to be the case.

The Strava data only shows moving time, not overall time but we should be able to find the overall time on Movescount. It would be interesting to see some of the overall times for the earlier runs.

Strava has moving time and elapsed time. From this morning's run:

33.2mi

Distance

8:15:02 Moving Time

14:54/mi

Pace

Elevation 2,293ft Calories0

Elapsed Time 9:01:14

Scam_Watcheroo wrote:

We don't have the overall times Mimi took to do her distances from the first 2.5 weeks for obvious reasons with what they did with Race Drone but it's hard to believe Mimi was running hours longer each day than Sandra was.

You can get the true times for all of Mimi's runs from Movescount, all the way back to her very first run out of downtown Los Angeles:

Just glancing through, it does indeed appear that her average pace in the past 3 days has been a little slower than it was earlier. Four of her last six run segments were at under 6.0 km/hr, but prior to this there were only a few segments under 6.0 km/hr.

I don't necessarily find it suspicious, but she does seem to be slowing a bit.

Results wrote:

Strava has moving time and elapsed time. From this morning's run:

33.2mi

Distance

8:15:02 Moving Time

14:54/mi

Pace

Elevation 2,293ft Calories0

Elapsed Time 9:01:14

Jesus! Don't know how I keep skipping over that in Strava.

Results wrote:

I see how you can tell the stopping and starting from breadcrumbs, but how are you getting distance? It doesn't record the mileage at a breadcrumb from what I can tell. So then you just plug the points into Google Maps or something?

Edit: Oh I see she's back to starting and stopping the Garmin. I stopped looking around the time she let it run for three days straight.

If you want to get a distance from Garmin it takes a little bit of effort because the Garmins are being run continuously. Pete was posting daily trips. Sandy and Mimi are using start of day 1 to end in NYC.

For those who are interested this is a way to measure mileage for Garmin breadcrumbs using Google Maps.

- If you click on a breadcrumb and click the more button it shows latitude and longitude. I take the values for two breadcrumbs (numbers only separated by a space or comma) and then use Google Maps to search for the first breadcrumb, then select Directions, and then add the second breadcrumb. You can choose the walking option Google provides you with an elevation profile unless the run is "fairly flat". If the Google Map route does not match the Garmin route you can click on the route line at the place it is wrong and drag the line to the correct road.

Sandy? wrote:

... but she [Mimi] does seem to be slowing a bit.

Her run day is getting longer. Yesterday was 15.5 hours.

OK, so you are plugging it into Google Maps. Thanks for keeping track of the mileage. Did you notice her slowing down before three days ago? From what I can tell the trouble started on the afternoon of October 2nd.

So far today wrote:

Sandy? wrote:

... but she [Mimi] does seem to be slowing a bit.

Her run day is getting longer. Yesterday was 15.5 hours.

This morning alone was 9 hours. I went back to her other morning runs...similar distances but nothing close to taking that long from what I saw.

Scam_Watcheroo wrote:

Results wrote:

Strava has moving time and elapsed time. From this morning's run:

33.2mi

Distance

8:15:02 Moving Time

14:54/mi

Pace

Elevation 2,293ft Calories0

Elapsed Time 9:01:14

Jesus! Don't know how I keep skipping over that in Strava.

Looking back through some of the overall times on Mimi's Strava on earlier runs, I think it does indeed show that her performance over the past few days have dropped significantly compared to before. She only took 7:18 overall time to do 30.5 miles over hilly terrain compared to the 9:01 she takes now to do 33.2 miles. You would expect her to be at least an hour faster.

Results wrote:

OK, so you are plugging it into Google Maps. Thanks for keeping track of the mileage. Did you notice her slowing down before three days ago? From what I can tell the trouble started on the afternoon of October 2nd.

There is not enough data to see yet. But yes, the short day was Oct 3rd, and it was the Asher day. Either Oct 2nd or 3rd is when she passed the halfway point.

Results wrote:

So far today wrote:

Her run day is getting longer. Yesterday was 15.5 hours.

This morning alone was 9 hours. I went back to her other morning runs...similar distances but nothing close to taking that long from what I saw.

Your are seeing what I am seeing. That distance run is more important than the amount of time it takes. Rest becomes optional. This is not good because she still has 20 days to go.

Scam_Watcheroo wrote:

Scam_Watcheroo wrote:

Jesus! Don't know how I keep skipping over that in Strava.

Looking back through some of the overall times on Mimi's Strava on earlier runs, I think it does indeed show that her performance over the past few days have dropped significantly compared to before. She only took 7:18 overall time to do 30.5 miles over hilly terrain compared to the 9:01 she takes now to do 33.2 miles. You would expect her to be at least an hour faster.

https://www.strava.com/activities/1184542317

Yes, I think something's going on. I would suspect fatigue or injury ahead of cheating, but something has clearly changed the last few days. I'm going to see if I can pull numbers for the afternoon run to this point unless So Far Today already has it handy.

There's a gap in the breadcrumbs (very small) but it looks like she started the afternoon run here:

Oct 5, 201712:29:45 PM

Speed: 3.74 mph Course: E

Elevation: 1,015.75 ft.

Lat: 38.490836 Lon: -94.693801

To here:

Oct 5, 20171:58:30 PM

Speed: 2.49 mph Course: S

Elevation: 988.58 ft.

Lat: 38.480193 Lon: -94.612198

That's a little under an hour and a half to go 5.1 miles

Results wrote:

There's a gap in the breadcrumbs (very small) but it looks like she started the afternoon run here:

Oct 5, 201712:29:45 PM

Speed: 3.74 mph Course: E

Elevation: 1,015.75 ft.

Lat: 38.490836 Lon: -94.693801

And she stopped for the break at 12:10. A sub 20 minute break. Her prior breaks were 30 minutes.

Results wrote:

Yes, I think something's going on. I would suspect fatigue or injury ahead of cheating, but something has clearly changed the last few days. I'm going to see if I can pull numbers for the afternoon run to this point unless So Far Today already has it handy.

The old woman is slowing up. She must rattle with painkillers with that knee. She could end up doing long term damage.

She knows this is the area more likely that people will put boots on the ground so maybe now we are seeing a legit stretch, but not at the start?

Mimi too a wrong turn when she reached the Missouri border. She should have gone north of Drexel MO (according to her route map) but went south. She can get back on course but it will add a couple of miles to the overall run. Not a disaster, but it seems she won't like it at all.