TP Class ratings

[Mark]

left at the gate?

all #'s are identical for each race, 9/6 and 9/7

[km]

Same at WO Mark, so a good guess :rolleyes: - could it have something to do with the "A" (poly) track?

I'll check it out and report back, but that is very odd bug. Thank you.

[km]

Fixed the bug and sent updated SEPT 6 version to Ricks. He'll post a message when they are ready for download.

IOU a beer Mark, thanks for catching that so quickly.

The obvious bug was that the Class rating was processing based on surface, but the code for "A" (Artificial / Poly) had not been applied in the code module for the Class rating.

This is the first time we have clear distinctions in HTR for the Poly track - i'm pretty sure everything else, especially the velocity calcs, have the correct algorithm for the "A" surface, but let me know if you find anything else strange when handicapping WO and TP. Coming soon = KEE Poly.

BTW: our trainer and pedigree stats are still lumping "D" and "A" surfaces together for now, until we can broaden the db. But the Trainer Stats do have a Track Specific stat (Trainer at TP last 365) so the TPG will be more accurate with the Poly right now at TP and then other tracks after a year's time.

[Rick]

Bug fix dated 6 Sep 06.

Download upgrade to HTR2.exe (http://www.homebased2.com/km/dnl/htr2.exe)

Download upgrade to HTR2006.exe (http://www.homebased2.com/km/dnl/htr2006.exe)

[BillW]

FYI: For those keeping databases, if you exported the spring TP meet with the July 2006 version you will need to re-export it also. ;)

[njcurveball]

I downloaded new program.

Opened it and clicked Download. Then I clicked "Get My Tracks".

Run-time error '62': Input past end of file.

Program closed.

[Zaf]

I had the same problem as curve. Also, reviewing some of the woodbine races I noticed , some are listed on the various screens as 6.0 A & and others are litsed as 8.3 D. Should they all be A at this point ?

[km]

NJ - after adding TIM to the track list - it will cause the crash if you try to extract your old saved file. SAVE a new track list and it will work fine when you bring it up again. No bug fix necessary, just do another save to fix it.

ZAF - yes, that is odd, i'll check with Ron at HDW and find out why that happens, perhaps the surface code is in error. I see this on Sept 3 in two route races. But when i go back and bring up the WO for Sept 3 before the results, all the races show a "D" with no "A" listed ????

What date did they begin using the Poly 100% ?

The BEFORE & AFTER files for WO for Mon, Wed are fine and Thursday has the "A" correct as well. So i don't see this as a software error if the surface and course code was correct in the orginal files.

thank you both for reporting the problems

[km]

Here is what i did to figure out the WO error =

I downloaded all the RAcefiles from Sept 1-7 at WO. Without the results.

All the races correctly show the "A".

Then i download the Results + Charts files for the same dates.

Sept 2
Race-9 shows "D"

Sept 3
Races 4, 9 show "D"

??? I'll see if this is a software error first, if not, i'll i contact HDW and see if the course/surface code were implemented correctly.

thanks again ZAF

[km]

Figured it out =

Those WO races were taken off the grass and then raced on the POLY. They were incorrectly listed as "D" after the switch.

This is brand new situation with surface change (Grass to Poly) that we have never had before because Turfway has no grass races.

But maybe no more sloppy tracks will mean fewer scratches when they do take races off grass and switch to Poly.

I'll work on it and fix before KEE starts. Glad it came up now.

[BillW]

Ken,

I am keying off of nCOURSE in HX4 (field 159) for my surface info. In looking at WO 9/04 Race 1 It shows Main Dirt (== 1). It looks like nDS (field 7) shows Dirt Sprint (==1) also. nSURF is fine (==4).

38964,"WO","09/04/2006",1,6,4,1,4


Bill

[km]

Thanks Bill, i'll have to work on the code logic to iron out all the various surface/course scenarios. Can you check the recent TP output from HX4 for me too ?

Does this feel like the beginning of a new transition in thoroughbred racing?!

[km]

FYI: WO began racing on the Poly on Wed August 30. Prior races in august were on the "inner" (harness) track.

Until i get it fixed, and i want to take my time with KEE looming ...

If you use the Robot, test WO since that date with Dirt + Poly checked off.

Export users can do NOT nSURF = 2 (no turf) and get the same results.

both methods will yield 100% Poly races since Aug30.

[BillW]

Thanks Bill, i'll have to work on the code logic to iron out all the various surface/course scenarios. Can you check the recent TP output from HX4 for me too ?

Does this feel like the beginning of a new transition in thoroughbred racing?!

Sure glad to help ...

In looking at race 1 (route) and 2 (sprint) of TP 9/07 it looks like nDS is showing Dirt route/sprint (==2, ==1) in HX3, HX4. and HX7. Otherwise nSURF (==4 in HX3, HX4,HX7 and HXV) and nCOURSE (==5 in HX4) look fine. I also checked nPL_SURF(field40) in HX7 and nPPxSURF(fields 41-50) in HXV and both looked fine.

I did a quick check of WO on the above and except for what I had already reported, all else looked OK (didn't spend time to find example of nPL_SURF or nPPxSURF in WO file).

Bill

[Mark]

Thanks Ken...I also notced turf races from any ship track to poly lacked the usual bracket on the Velocity screen (checked TP only). WO would have few, regardless.

A new era indeed, that usually portends profits.

[km]

Thanks very much everyone.

I'll take my time fixing this to make sure all the bases are covered before KEE begins. I guess every situation could not be anticiapted until it came up. At the time of the seminar release Aug 1st version HTR2, we did not have a Poly track in operation so no one noticed any problems until now when the races actually began.

I guess it's an easy work around for now if you use the Robot or Export knowing that "D" and "A" are the same thing at WO and TP. The only issue would arise if testing all the "A" (Poly) races at once, there would be a few missing "D" races. But since there are only two tracks using it right now, even that would be easy to overcome: NOT TURF at WO and TP since August 30 would do the trick.