Database Handicapping Software- JCapper

JCapper Message Board

          General Discussion
                      -- Missing internal fractions for mvr ?

Home Register
Log In
By Missing internal fractions for mvr ?
kingfish
4/17/2019
10:18:55 PM
Was looking at mvr for april the 16th . And some of the horses had missing internal fractions for race 5 and race 8 . If their is no internal fractions showing . How does hdw compute pace and final figures . All that is showing is the letters na . Does that mean not available .



Herman King

Reply
jeff
4/21/2019
10:36:24 AM
Here's a link to a screenshot of the PPs for the #8 horse Artavia for MVR 04-16-2019 in R8:





And here's a link to a screenshot of the Equibase PDF Chart for the race in question that the #8 horse Artavia (above) came out of - MVR 12-26-2018 R9:




My comments:

The internal fractions for the race in question are missing and are listed as NA (highlighted in yellow) in the above screenshot of the Equibase chart. Note that this applies to all horses coming out of that race when they show up to race again.

The running line for the race in question (highlighted in blue) in the screenshot of the PPs for #8 Artavia MVR 12-26-2018 R9 also shows the internal fractions as NA.

HDW did not make pace figs for that race. The F1, F2, and Late Pace Figs are displayed as NA.

That's because the internal fractions failed to make it into the chart data.

Fyi, in cases where the chartcallers can't see the horses (for example because of fog) the internal fractions, positional calls, and beaten lengths (all three) will be missing from the chart data.

But here, the positional calls and beaten lengths did make it into the chart data for the race - but not the internal fractions.

For that reason - my first best guess at a root cause would be a timing error at MVR for that one race.

All of that said, I'm going to ask Equibase to give me their explanation as to what happened --

And I'll come back to this thread and post an update once I know more.


--EDIT 04-21-2019:

Confirmed. (Root cause was a timing error at MVR.)



-jp

.


~Originally posted by: jeff on: 4/18/2019 at: 2:27:03 PM~

~Edited by: jeff  on:  4/21/2019  at:  10:36:24 AM~

Reply
Reply

Copyright © 2018 JCapper Software              back to the JCapper Message Board              www.JCapper.com