Export beta-test

[Rick]

If you would like to help beta-test the JULY 2007 version of HTR2 Export

= be sure you know how to handle an .exe file (HTRBETA) and place it in your data folder
otherwise wait for the completed HTR2 update in the coming weeks and forget this beta test

= HXD and HX9 are the new output; refer to the companion download PDF files for details

= our data on the Aritificial (Poly) tracks is not yet included in the daily Racefiles and the Dirt
and Poly information in the HX9 will not be 100% accurate yet those categories - in fact it may
be distorted because Dirt and Poly are combined in the data right now - all other categories are fine

= PL6 and PL7 have been added
PL6 chooses ONLY the specific surface
PL7 selects EVERY line within the last 365-days, regardless of dist/surf or anything else

= you may also beta test the Robot LEARN MORE and the new DOWNLOAD Screen which has been expanded

= many screens in HTR2 are disabled as i continue to work on them

If you find apparent errors in the export HXD or HX9 (aside from the Poly/Dirt data problem mentioned above) or if it
does not function, or if it crashes please let me know asap

no details on anything new provided yet, please wait for newsletter before asking questions

thanks for your help!

ken

Download HTRBETA.EXE (http://www.homebased2.com/km/dnl/HTRBETA.EXE)

Download HX9.pdf (http://www.homebased2.com/km/pdf/HX9.pdf)

Download HXD.pdf (http://www.homebased2.com/km/pdf/HXD.pdf)

[njcurveball]

Christmas in July!

Thank you Ken, Ron, Rick, Santa, Rudolph, Dasher, Dancer, et al

[DanG]

Christmas in July!

Thank you Ken, Ron, Rick, Santa, Rudolph, Dasher, Dancer, et al

Ditto Jim!!!

How many things in life can you honestly say improve every year? (Certainty not our local baseball team!!!) :eek:

HTR, improves TWICE a year!!! :) :)

Outstanding work Ken. Your efforts are greatly appreciated.

[km]

thanks NJ and Dan

Known issues so far

"d" items
= blanks need to be renumerated as -999
= 0 is a tie between the top ranks
We will correct the PDF to note this

dFC = error needs fix

tPSELECTED = error

ROBOT
has problems with retrieving spot plays, previous saved plays should work, but there is a new racetrack added to the list (PID: Presque Isle Downs) that extended the list of tracks and crashes when pulling out spot plays as the list is out of sync.

[Donnie]

one quick ?? Ken----
If the #1 horse scratches out, before the files are finalized, will we lose the conditions....you stated that they are tied into the horse with program #1, or do you mean the first record listed for the race?

[km]

You are correct on the latter Donnie; one of the horses will always end up with the conditions text. The PDF states "1-post";

nPPO = ALWAYS has a "1", scratches just push someone else to the inside post regardless of its orginal program#; every race has an nPP0=1

[Donnie]

FYI--
When a person imports the first time into a new table, the Conditions field is set to text and 255 characters. This is gonna be to small for the size being set at 255 max for a text field. Access will throw up an error message and throw an errors table into the database. The field will need to be reset to the memo data type and then the records deleted out and reimported. Ken's exporter puts the field size at 300 and that is too large for a text field in Access.

[MikeDee]

In all_hx9:

The tPGM field contains the horse name and tHOR field contains the program number.

It appears that the data values for these 2 items are reversed.

[MikeDee]

In regard to the condition field.

I can set the file spec in the access template to memo for this field and it should import OK as long as you use the file import spec for hxD table.

One problem with a memo field is that about the only thing you can do with it is to print it out on a report.

Unless I hear other wise I will set the file spec for this field to memo.

[DanG]

In all_hx9:

The tPGM field contains the horse name and tHOR field contains the program number.

It appears that the data values for these 2 items are reversed.

Donnie ~ FYI--
When a person imports the first time into a new table, the Conditions field is set to text and 255 characters. This is gonna be to small for the size being set at 255 max for a text field. Access will throw up an error message and throw an errors table into the database. The field will need to be reset to the memo data type and then the records deleted out and reimported. Ken's exporter puts the field size at 300 and that is too large for a text field in Access.

The service you gentleman provide in beta-testing is sincerely appreciated. :)

[km]

Good catch Dee, thanks, i already fixed it for the final version

A new version with all the fixes will be available as soon as we accumulate all the errors

[Donnie]

Maybe I don't understand this properly.....
here is what I am getting for the VEL numbers in the db...

tTRK nRACE tPGM tHOR nVEL rVEL dVEL
AP 4 9 Small Field 0 0 0
AP 4 7 Bureau Chief 21.3675 1 30.9946
AP 4 8 Bold Caper 21.3675 1 0
AP 4 2 Gray Star 14.5299 3 28.7429
AP 4 10 Coin of Truth 13.6752 4 29.7241
AP 4 5 Louie de Plus 10.2564 5 31.6047
AP 4 6 Canyoudoonemore 8.547 6 30.3285
AP 4 1 He's a Riot 7.6923 7 31.2455
AP 4 3 Metts Ready 1.7094 8 31.0406
AP 4 4 Crimson Mike 0.8547 9 29.5449

Should the first horse get a 0 for nVEL?? In the HTR2 program he got a 9. Also the 2 ranked #1 in rVEL, one is showing a dVEL, the other is 0...??

[Rick]

Looks like you exported using PL6.

At least that is what it looks like in HTR2 PL6.

[Donnie]

thanks Rick...I'll try again...using 5.

[km]

VEL section messed up, good catch Donnie, i just fixed - keep em coming, ignore that data for now, it got mixed up with L/P

remember that i did not get the zeroes right in HXD, blanks = 0 right now, i have recoded to -999 for blanks and zeros (0) in the "d" field will indicate a tie for top rank

this is what beta testing is all about; and the primary reason why it would be difficult to produce an "all burger" export with 1000 data fields or something, the accuracy is much easier to scrutinize when this data is compartmentalized into separate export options.

[Donnie]

Rick was right I exported using PL6 for that one, but it still was not calculating the dif correctly....looks like KM caught that one....back to testing....

[Bob]

...when I run "learn more" for my spot play. I confirmed that there were about 50 plays in February.

Just wanted to alert you to a possible "beetle"!

[km]

thanks Bob, yes i fixed the FEB
It was getting mixed in w/ MARCH !

let me know if you see any other problems with the Robot - i'm sure there will be some with the spot play extraction because of the addition of PID to the list of tracks which might throw everything out of sync

[Bob]

By the way....

Fantastic improvements!

You are the MAN!

[Huguenot]

Ken,
I thought you going to 86 to "Fig2 =1" factor. Or am I confused?

Also will you be able to fix that tiny bug I noted on the KM page? (When you print out the final odds, they all convert to the first race you looked at.)

Overall I love the new Learn More in the Robot -- why did you go with 29-65 days? Just curious.

[km]

Hug read the newsletter last month for the Layoff zones and a detailed explanation of each of those categories.
29-65; "Freshening" zone. Previous item "1st after LO" is still in the trainer stats refers to any layoff 45 days or more.

I thought i had fixed that bug on the KM with the odds, will double check, it's possible i only fixed it in one of the print options, but not all of them.

I wanted to replace the FIG2=1 but users begged for it to remain. Also, it was better not to disturb the existing filters for preservation of Spot Plays that people have saved.

[Huguenot]

Hmm I guess I should have double-checked the new KM screen before asking. :eek:

You're way ahead of me as usual, Ken.

[Huguenot]

1. Found a possible bug. In the Fig 1 and 2 screens on the artificial turf tracks, the Easter Egg <f> feature does not work on the polytrack races. None of them show up on the PPs when you hit the <F>. I checked this out at Woodbine, Hollywood and AP.
The turf races are fine.

2. It seems to me the downloading screen is now slower than it was before. I love the new features on it and this is not really a complaint but the newsletter noted that the new screen should download more quickly. I have not found that to be the case. In fact my downloads are taking considerably longer.

Overall, tho, the upgrade is great.

[km]

Thanks hug

re: hot key
That's not a bug - it was that way in the previous version too. I'll adjust it so the hot-key will select Poly (only) if that's what people want. No one ever mentioned this to me prior - nothing has changed since the previous update in relation to that function. Older version did the same thing.

re: Downloader
All the beta-testers and my own experience is that it saves time overall for these reasons mentioned in the newsletter =

1) combo file is downloaded now instead of separately (Racefile + Trainer file) saving 50% of the time to extract a second file.

2) When on the Internet site and using the multi-file 'download cart' - it can take forever to wait for "Hold Your Horses" screen to get to the java applet load. Especially if you have a lot of files in the HTR folder.

3) The time for download itself would be no different once the file is acquired, that depends on your connection, but direct access without the browser and security software layers saves time.

4) Many people cannot use the Internet site at work or on computers that are security protected. But the HTR2 utility does not use the Internet or a browser which speeds up access initially as well.

Try clocking the time it takes you to go from step one (opening the browser) to downloading with the 'Download Cart' on the Internet..

vs. downloading all the same files with the HTR2 utility, it wouldn't be close in my case as the "Hold Your Horses" screen takes 3-4 minutes to load after I select my files.

[DanG]

These are great updates IMO. Sliced and diced all kinds of time with the new exports while adding killer new features.

Ken; one observation;

Did the Pedigree stats for artificial surfaces begin on the 11th? I ask, because pulling up Arlington the counts seem very high on the sires. I don’t think the sample size could be that large yet for Arty’s.

Among many other things…

• The new TJ display is very cool…”Hot stats” is a great alert to a key situation.
• Exporting which paclines (PL5) selects is very nice also.
• Etc…Etc…Etc!!!

BTW: For those importing HX4. On the new PDF file specs I saw the two fields…”nBadFav” and “nLayZone” were not on there. You might want to add them to your import file specification before making a run.

Also don’t forget Donnie’s reminder on the “tRACECOND” now being a memo field.

Thank you very much Ken; you accomplish more while we sleep than many do awake!!! :) :)

[km]

appreciate that Dan -

correct - PED stats start Jul11th Thursday races - you'll notice smaller sample sizes with th new sire ratings on Poly, but we had to make this transition at some point, so there will be discrepencies between older races and those going forward. In time, the PED ratings will iron out as more Poly races are added to the database. Previous PED ratings combined Dirt and Poly, now the surfaces are separated.

Does this separation make sense? In my view, ratings for routes and FTS are not a matter of surface but stamina and early maturity respectively. On the other hand, Poly tracks are distinct and horses may react differently as they do on grass; we have no way of knowing the effect unless we keep separate stats and find out. What outcome it will produce with the PED rating is unknown for now.

to all export users =
all the exports including HX4 were expanded and repaired after the beta version, so be sure to look at the PDFs and check the data fields carefully before exporting from newest HTR2

[Huguenot]

Thanks hug

Try clocking the time it takes you to go from step one (opening the browser) to downloading with the 'Download Cart' on the Internet..

vs. downloading all the same files with the HTR2 utility, it wouldn't be close in my case as the "Hold Your Horses" screen takes 3-4 minutes to load after I select my files.

Ah, that makes sense. Like I said I love the new downloading screen and was just wondering if maybe it was my PC. But yes, all told it probably is faster.

[Huguenot]

I'm not sure it would be an improvement to change the <f> Easter Egg to reflect only polytrack. No one really knows yet what to do with dirt/grass races in those PPs.

[DanG]

Does this separation make sense? In my view, ratings for routes and FTS are not a matter of surface but stamina and early maturity respectively. On the other hand, Poly tracks are distinct and horses may react differently as they do on grass; we have no way of knowing the effect unless we keep separate stats and find out. What outcome it will produce with the PED rating is unknown for now.

Yes,

The separation sounds perfect.

One issue…Exporting HX3 is crashing.

(I will say it eventually won’t be an issue with your new exporting fields. Everything I was using this table for is now in another export.)

I export HX4, HX5, HXV, HX7, and now HXD AND HX9. All worked correctly BTW. :)

[Rick]

I just tried exporting Jun 07 in HX3.

It crashed on me on BEL, 06/29/2007, 2nd race, 1st horse.

I next was able to export BEL for Jun 07 as single track.

Tried exporting All tracks again and it crashed on AP.

[DanG]

I just tried exporting Jun 07 in HX3.

It crashed on me on BEL, 06/29/2007, 2nd race, 1st horse.

I next was able to export BEL for Jun 07 as single track.

Tried exporting All tracks again and it crashed on AP.
Thanks for the verification Rick.

[DanG]

While we are in “bug” mode, one little minor deal…

I think Ken was in a tournament when Tom mentioned a while back that Arlington’s “dirt” races should be changed to “Artf” in the track profile.

Start date = 5/4/2007

[km]

i'll fix those bugs for the next version to be released night before the seminar

didn't do anything to HX3, so that is a mystery i'll check it out - the BEL horse Rick tagged is a FTS, but nothing seems out of the ordinary for it to crash the export

AP in the Track Profile was definitely addressed, not sure why the Artif isn't displaying, but will fix for sure, probably a calendar boner as Dan alluded

[njcurveball]

probably a calendar boner as Dan alluded


If it lasts for more than 4 hours, you better see your Physician! :D

[DanG]

If it lasts for more than 4 hours, you better see your Physician! :D
LOL… :D

Insert rim shot here…

Jim will be at the Comedy Stop in AC all week opening for Gallagher! :p

[DanG]

Ken,

File this under…”Are they ever satisfied!!!” :D

If at a future date the “comma delimited” charts could be included in the new and improved auto-downloader app it would be a tremendous help for 'us fanatics who grab those daily.

Nothing pressing and I know that 3rd party downloader app has given you many a sleepless night. :eek:

Thanks again for all the new tools & toys. This is a great summer adrenaline shot as we head into the guts of our season. :)

[km]

re: Track Profile and AP
I could not see a problem with the Track Profile and AP, all categories showing "Artif" in the most recent (July 2007) version of HTR2 and Dirt and Artif are clearly separated in the 1yr profile. Current profiles (30d) are in perfect order - no "boner" :o I even coded the Track Profile for start dates at DMR and PID this summer.

re: Com Charts in the auto-Download
The majority of users do not need access to those files, or even know what they are for - i don't even download them myself. So adding it to the auto-download menu might be confusing to some members. Adding it to a custom version (fee donated to Rick) is possible though.

[DanG]

re: Track Profile and AP
I could not see a problem with the Track Profile and AP, all categories showing "Artif" in the most recent (July 2007) version of HTR2 and Dirt and Artif are clearly separated in the 1yr profile. Current profiles (30d) are in perfect order - no "boner" :o I even coded the Track Profile for start dates at DMR and PID this summer.

re: Com Charts in the auto-Download
The majority of users do not need access to those files, or even know what they are for - i don't even download them myself. So adding it to the auto-download menu might be confusing to some members. Adding it to a custom version (fee donated to Rick) is possible though.
Very odd…

I am apparently mistaken on the AP surface in the track profile. I just added a year’s worth of files a few days ago and had to write a script to correct the surface. I just downloaded a month and it is all correct. My bad and yet another sign of age!!!… :eek: :D

Thanks for the response.

[Donnie]

Anyone having a problem exporting tomorrow's races? My program crashes at CNL.

[Rick]

Which exporter?

I just did HX4 and it sailed on through.

[Donnie]

Should point out this happens exporting PL1...HX2

[DanG]

Should point out this happens exporting PL1...HX2
Donnie…

I have had certain tracks crash exporting HX3…I don’t export HX2, but there could be a connection of what is now segregated as “Old options”. :confused:

[Donnie]

if ity's any relief to Ken, I am converting evrything over to HX4 and HX9.

[Rick]

I just exported all races for 14 Jul 07 in PL1 HX2 and it crashed on me around GRP.

Sailed right through CNL.

[km]

sorry about that

HX2 & HX3 were both crashing on the same data field #54; PL mode had no meaning, it crashes on all of them

All the bug fixes will be repaired with the July 24 version

Bug reports from users w/
HX3 = 4
HX2 = 1 (Donnie)

I guess we are done with HX2? and HX3 is on its death bed?

[dehere]

Did I read it correctly somewhere that the long comments field that was previously only available in HX3 is now available somewhere else? If not I would really hate to see HX3 go away.

[Rick]

It's in the HXD export. Last field. 300 characters max.

Can be a truncated text field or a memo field.

[dehere]

Thanks Rick - then as far as I'm concerned HX3 is no longer needed.

[DanG]

Thanks Rick - then as far as I'm concerned HX3 is no longer needed.
HX3 unique properties were…

WO data, Race conditions, horses records.

All of which are in other tables now and vastly improved!!!
http://www.go-montreal.com/centaur/plays/bye_bye_baby.jpg

[Donnie]

Think I found an error in the pdf for HX9:

Shouldn't fields 22 thru 26 be just Dist and NOT Dist/Surf. Cause the %'s aren't matching what is being brought up in the "Cat" 5's. I think it is just mis-labeled on the pdf's description.

[km]

It's correctly labeled D', that field is for the distance + surface. If the horse has 6.0f races on dirt and turf, and today is a dirt race, only the record for the 6.0D is posted in that field.

The CAT items? Those are trainer specific, field 22-26 is the horse's record. Can't be compared.

You might get a mis-match in that Dist/Surf field with data prior to the July 11 (file change) as our Poly and Dirt data were mixed together. Although, i thought Ron had updated that record item from January 1 this year. But previous year's data for sure would be a mis-match as the Poly tracks were combined in the dirt stats, now they are separated.

[Donnie]

sorry Ken....I.R. Anidiot! I didn't realize those were the horse's stats. Thanks for the explanation!

[MikeDee]

Ken, I have been working with HX9 and I have a question on trainer stats in regard to surface changes.

I see the following categories:
A to D
A to T
D to T
T to A
T to D

I have looked at quite a few files and have not come across any
D to A.

Since I an sure that there are many instances of a D to A, I am assuming that Dirt to Artificial is not one of the categories that is tracked. Is this correct?

[km]

Dee, all those things are certainly in the Trainer STats files, i'll check and see if they are being skipped in the export HX9, but the items are extracted sequencially - skipping something from the same row on the text line is the likely culprit if it is in the same text position every time.

I'll try to figure out if the same row or item from a row is being missed - thanks

[km]

Mike, i just exported one day - today DMR file (July 18) and all the items you mentioned are in the export HX9

"D to A" is there many times, so is "T Rte"

I'm sure T Spr is working too

Don't see a problem, what about your query: spelling, case sensitive, or spacing?

try RTrim if there are trailing spaces on some of these items

[Rick]

Mike,

I did an export of 1-14 Jul in HX9. That includes all tracks.

I have 3923 that have either a T Rte or T Spr.

I just opened the table and sorted on the tTSTAT1_CAT field.

Only came up with 7 races with D to A in tTSTAT13_CAT.

[Rick]

Mike,

After further review the D to A starts as a possible entry under CAT 13 and continues under CAT 14 through CAT 19.

Those could be fun to nail down.

But I bet you will figure out something.

[km]

re: "D to A"
Poly meets in progress for several months will have very few dirt transfer horses, when one starts up, like DMR now, it will be more common, but most of those horses are coming from HOL (Poly) so even that will be infrequent

re: CAT variation
there is no way i can query text for every possibility in that file and make a static export item. they are variable because each horse has different items pertinent to the race

[MikeDee]

T rte and T spr. I am OK on this one pilot error.

Now that I think of it I ran the sample on all races through 7/15/07 D To A is not in prior to the new trainer stats becomming available. So this explains why there are none in my sample.

[dehere]

I have a couple of additional questions to see if anyone else has experienced these issues.

First, with respect to the race conditions field in the HXD export. When I used to get the conditions memo field from HX3 it would show up for each horse entered in a race. That way, when I exported it for use in my PP's, it would show up in an export that was focused on race data, rather than horse data. Now, when I try to do the same with the HXD export is only shows up for the last entry in a race and does not show up at all in my report. Anyone else have this happen to them or think of what I might do to correct the problem?

Second, it seems to take forever for my queries to run when I have both HXD and HX9 added to my access query. It has always taken awhile for my queries to run as they are kinda complicated and, no, I do not use proper indexing procedures, but now it seems to take about 20 minutes for a query to run. Has this happened to anyone else?