1

Race Time Predictor (Read 54 times)

Fredford66


Running Musician

    Can someone clarify how to properly use the race pace calculator works with two races/distances?  The page says using a second distance will calculate a personalize coefficient, but when I use a second distance it seems to me that the calculator simply ignores the first one and uses the second one.  Am I doing something wrong or is there a glitch in the calculator?  I've tried multiple 2-distance scenarios and the result I get is always the same is if the second distance was the only one used (after tabbing through all the input fields to get the calculation to run).

     

    Thanks.

    5k 23:48.45 (3/22); 4M 31:26 (2/22); 5M 38:57 (11/22); 10k 49:24 (10/22); Half 1:48:32 (10/22)

    Upcoming race(s): Winter Series #5 Trail 10k, 2/4; E. Murray Todd Half, 3/12


    an amazing likeness

      I may not be understanding your description, but in doing some experimenting the predictions are changed by either of the 'predictor' race times changing.  Just as an example, using a 5K and 5mi set to predict for a half marathon:

       

      Race 1 = 5K in 24:05  (7:45/mi)

      Race 2 = 5mi in 40:00 (8:00)

      Enter 13.1 in the Predict Time For.

      Predicted time if calculated at 1:51:43 / 8:32/mi

       

      Change Race 1 time to 21:00 and the calculator sees the 'massive' fall-off from D1=5k to D2=5mi and now the 13.1mi prediction falls to 2:27:35 / 11:16mi

       

      Put everything back to the baseline scenario and change Race 2 time from 40:00 to something faster, like 37:30 and the calculator sees the (now slower) 5K time as irrelevant and predicts the 13.1 way faster than baseline scenario.

      Acceptable at a dance, invaluable in a shipwreck.

      Fredford66


      Running Musician

        I may not be understanding your description, but in doing some experimenting the predictions are changed by either of the 'predictor' race times changing.  Just as an example, using a 5K and 5mi set to predict for a half marathon:

         

        Race 1 = 5K in 24:05  (7:45/mi)

        Race 2 = 5mi in 40:00 (8:00)

        Enter 13.1 in the Predict Time For.

        Predicted time if calculated at 1:51:43 / 8:32/mi

         

        Change Race 1 time to 21:00 and the calculator sees the 'massive' fall-off from D1=5k to D2=5mi and now the 13.1mi prediction falls to 2:27:35 / 11:16mi

         

        Put everything back to the baseline scenario and change Race 2 time from 40:00 to something faster, like 37:30 and the calculator sees the (now slower) 5K time as irrelevant and predicts the 13.1 way faster than baseline scenario.

         

        If I take your inputs, as soon as I input 13.1, I get the result 1:51:34.  However, if I hit Tab twice, getting to the Coef: field, the prediction changes to 1:53:12 and after that it stays at 1:53:12 no matter what I input for the first race.

         

        My guess is that by tabbing to the Coef: field, I'm telling the formula to use the default 1.08 value no matter what it has calculated internally. and it keeps that override.

         

        Thus, it seems you have answered my "How do I do this?" question.  I simply avoid tabbing into the Coef: field.  Thank you.

        5k 23:48.45 (3/22); 4M 31:26 (2/22); 5M 38:57 (11/22); 10k 49:24 (10/22); Half 1:48:32 (10/22)

        Upcoming race(s): Winter Series #5 Trail 10k, 2/4; E. Murray Todd Half, 3/12


        an amazing likeness

          Ok, I see what you're describing: once you make an entry in, or tab through, the coefficient field, the calculator 'ignores'  updates to the Race1 fields.

           

          To me it looks like a bug in calculator code.

          Acceptable at a dance, invaluable in a shipwreck.

          Fredford66


          Running Musician

            Ok, I see what you're describing: once you make an entry in, or tab through, the coefficient field, the calculator 'ignores'  updates to the Race1 fields.

             

            To me it looks like a bug in calculator code.

             

            Yes, but at least it's a bug with a workaround. 

            5k 23:48.45 (3/22); 4M 31:26 (2/22); 5M 38:57 (11/22); 10k 49:24 (10/22); Half 1:48:32 (10/22)

            Upcoming race(s): Winter Series #5 Trail 10k, 2/4; E. Murray Todd Half, 3/12