The Running Thread - 2018

Fun Friday QOTD: Should I bring DD on Tower of Terror? She is 4, meets the height requirement, and depending on the day, said she wants to ride it. Those of you with children when did you introduce them to rides like this?
ToT is my all time favorite ride, so I want to give a resounding YES! But... I think you are smart to gauge her reaction on other thrill-type rides before making the final call. I would have been fine at 4, but my sister would not be fine riding at any age. ;)
 
I still don't really like riding ToT but I felt a lot better about it after watching a behind the scenes thing on TV at some point (like on TLC or Discovery or something) about how it is actually pulling you down, you aren't free falling. For some reason that made me feel better about it knowing something was just pulling me, I wasn't depending on some brakes to catch us. :D
 
Fun Friday QOTD: Should I bring DD on Tower of Terror? She is 4, meets the height requirement, and depending on the day, said she wants to ride it. Those of you with children when did you introduce them to rides like this?

I vote yes, but do it closer to the end of your trip - just in case it scares her and she refuses to go on any rides after that.
 

My nieces from the time they were tall enough rode Tower & loved it. My nephews on the other hand did not like it and were scared of it. Of course they have outgrown that, but my olest nephew literally would refuse to ride it for a long time when he was younger, at least at 15 now he has overcome that. So, I say let her ride it if she wants too. Me & Tower though man that ride does not like my stomach anymore :( The themeing though is so cool.
 
Question: If you want a certain time for whatever reason, how do you set the target paces to achieve it?
I understand the concept of a race time predictor, and that it assumes you slow down as you go farther. For example my 10K would not be double my 5K time. I keep seeing simple math for printing wristbands or calculating the pace you need to hit to make the time. I can do that math, but is not helpful. Is there some sort of reverse calculation closer to what you get from McMillians or other free online things?
 
ATTQOTD: I'd first go through the pre-TOT scariness checklist of acceptability.
Are froghoppers ok?
Barnstormer type rollercoasters?
Mine train?
Haunted Mansion?
Pirates (dark and a drop)?
How does she handle being in really tall buildings or on balconies?

I'd agree to go for the end of a trip. Because there's a good chance that every ride from then on out will be a "is the floor gonna drop???" Q&A session. Even if the ride goes well. Just wait for the arm holding "when's the crazy drop gonna come?" anticipation even on tame rides. Which may not happen....but gotta hedge your bets :)

My kiddo is more brave now at 5 then I was at 20 so the #1 answer is "you know your kid better than anyone else"
 
Question: If you want a certain time for whatever reason, how do you set the target paces to achieve it?
I understand the concept of a race time predictor, and that it assumes you slow down as you go farther. For example my 10K would not be double my 5K time. I keep seeing simple math for printing wristbands or calculating the pace you need to hit to make the time. I can do that math, but is not helpful. Is there some sort of reverse calculation closer to what you get from McMillians or other free online things?

If you try this link https://www.calculators.org/health/mcmillan-running.php

(Don't use this one...use the one that FlashAM7 posted below...kthanks!)

You can plug in a recent race where you think you were running at your best effort. Or maybe a training run at your best effort. It will show the McMillan times for a whole bunch of distances. Divide by the mileage to get the pace at that distance.
I use a dopeybadger plan where he does a lot of the math for me, but he does use my most recent good race efforts as a jumping off point.
 
Last edited:
If you try this link https://www.calculators.org/health/mcmillan-running.php

You can plug in a recent race where you think you were running at your best effort. Or maybe a training run at your best effort. It will show the McMillan times for a whole bunch of distances. Divide by the mileage to get the pace at that distance.
I use a dopeybadger plan where he does a lot of the math for me, but he does use my most recent good race efforts as a jumping off point.
Is that right? I put in my 10k time of 51:54 and it says my 1 mile and Marathon paces are exactly the same (8:21/mi)
 
Is that right? I put in my 10k time of 51:54 and it says my 1 mile and Marathon paces are exactly the same (8:21/mi)

I guess not. There's one I used to use all the time and I thought it was this one....but that's way not right.

Everyone disregard!!! #mathfail
 
Another vote for doing it at the end of the trip! Both of my girls went on the DLR ToT (I'm assuming it's pretty similar to WDW) at a young age. My oldest loved it, but my youngest hated it. My youngest loves it now with the GotG theme. She's a strange one with rides though. She loved FoP at AK this past January, but still absolutely hates Soarin' at DCA when we asked her to try it in February now that she is older and braver....:confused3
 
Question: If you want a certain time for whatever reason, how do you set the target paces to achieve it?
I understand the concept of a race time predictor, and that it assumes you slow down as you go farther. For example my 10K would not be double my 5K time. I keep seeing simple math for printing wristbands or calculating the pace you need to hit to make the time. I can do that math, but is not helpful. Is there some sort of reverse calculation closer to what you get from McMillians or other free online things?

Do you mean the paces you should run in training or the pace you should run in the race itself?
 
Do you mean the paces you should run in training or the pace you should run in the race itself?
I'd settle for either as I know neither. I do not currently target a pace, nor do I really know how to do so, but I am curious what paces would reasonable to achieve a random time.
 
ATTQOTD: I say go for it if she wants to and echo others who recommend waiting till the end of the trip. We had our oldest on test track on our first day when he was four and it really freaked him out. He freaked out about most rides after that for the rest of the trip. Telling him that he rode the fastest ride in all the parks meantime nothing to him at that point. Also recommend showing ride videos before you go in case that might help.
 
Catching up some:

Regarding motivation, definitely my running partner and husband @Chris-Mo is my motivator. His latest motivational phrase when we are running a race and I'm getting tired is

F**k Tired
Crass perhaps, but it seems to work for me. :D

I think my kids were around 7 when they rode ToT for the first time. One was willing to ride a second time and the other was not, so it definitely depends on the kid (it's one of their favorite rides now as teenagers, so clearly didn't scar her for life. LOL) . If they say they want to do it, go for it.
 
I'd settle for either as I know neither. I do not currently target a pace, nor do I really know how to do so, but I am curious what paces would reasonable to achieve a random time.

The target pace during a race is fairly easy to calculate. As you pointed out earlier, it's really just simple math, and any number of online running calculators can do that for you. Here's an easy one for half and full marathons. http://www.smartpacing.com/index.php?page=PacePrediction The one thing I always tell people to be cautious of is that the pace charts assume you run exactly the race distance. Since most people can rarely if ever do that, you need to run a bit faster than the mathematical pace. For example, a 9:07 pace will get you in 30 seconds under a 2-hour half. That's cutting it a bit close since if you run only a few hundred yards more than 13.1 miles due to weaving or not following the exact tangents, you'll be over 2 hours. That's why for whatever your distance and calculated pace, you should run 5-10 second per mile faster to make sure you hit your time goal.
 
The target pace during a race is fairly easy to calculate. As you pointed out earlier, it's really just simple math, and any number of online running calculators can do that for you. Here's an easy one for half and full marathons. http://www.smartpacing.com/index.php?page=PacePrediction The one thing I always tell people to be cautious of is that the pace charts assume you run exactly the race distance. Since most people can rarely if ever do that, you need to run a bit faster than the mathematical pace. For example, a 9:07 pace will get you in 30 seconds under a 2-hour half. That's cutting it a bit close since if you run only a few hundred yards more than 13.1 miles due to weaving or not following the exact tangents, you'll be over 2 hours. That's why for whatever your distance and calculated pace, you should run 5-10 second per mile faster to make sure you hit your time goal.

This is so important to remember!!!!
When doing training runs you hit stop on your watch or phone when you hit the exact mileage you want to run. But often in races I've already hit that mileage before I actually cross the finish line.
I was such an insane stickler for my tangents and not weaving a bunch the one time I was trying to get a good POT for a Disney HM. Because I knew I could easily add more mileage than I wanted to if I wasn't paying attention. And I still was a bit over, but I really can go over when I don't care about my time and just run wherever.
 














Save Up to 30% on Rooms at Walt Disney World!

Save up to 30% on rooms at select Disney Resorts Collection hotels when you stay 5 consecutive nights or longer in late summer and early fall. Plus, enjoy other savings for shorter stays.This offer is valid for stays most nights from August 1 to October 11, 2025.
CLICK HERE







New Posts







DIS Facebook DIS youtube DIS Instagram DIS Pinterest

Back
Top