Auto scratch slow for anyone else?

[njcurveball]

Phila Park just ran their first race, I still don't have the track coming up in auto scratch.

Many other examples, but if others were getting scratches from this track before the 1st race, I will look elsewhere for my problems.

*** OK, after I posted this, the track came up, which is nice, but it wasn't there in time for the first race. ***

thanks,
Jim

[rags]

I have had many instances of it running behind the start of races.

[Ron Tiller]

I'm back from California and saw this thread, so I'll give it a whirl. I'm sorry, Jim, that the scratches don't always get up quickly enough. Everything is automatic, so there is no question of forgetting or being late to hit the button - they go up when they're on our server.

As a general matter, we cannot make any assurances that scratches will always be available before the start of the 1st race for a given race card. The scratches data is entered into the Equibase system at the track and we publish the scratches in the Equibase system every 5-10 minutes throughout the day.

So there is the issue of
1) the data being entered at the track,
2) the latency (small time delays) in the replication from Equibase to us,
3) the processing time on our end.

Before making the auto scratches feature available on HTR, Ken and I discussed the various problems and limitations of doing this, including the problem that sometimes the scratches would not be available in as timely a manner as we all want (that is, before the first post). And some tracks might be persistent problems. We decided that it was reliable enough to implement, but it is what it is.

Regarding the accuracy of the scratches, we have no independent pipeline - we publish whatever Equibase has in their system.

Ron Tiller
HDW