PDA

View Full Version : wish list


edster42
12th August 2011, 10:24.40 AM
Ken,

1) nPSF in race - robot and export

2)Donnies Fig2 screen - TPGM at the top of the PAR line

thnx
ed

jack
12th August 2011, 11:37.16 AM
Where is Donnie's fig2 screen now ? Jack.

edster42
12th August 2011, 12:00.48 PM
FIG2 + <F8> hot key

km
12th August 2011, 12:02.11 PM
edster, thanks for suggestions, do you have the latest versions? --

RACEFILTERS module in Robot2, July versions added the "PSF in Race"/ "NO PSF in Race" (bottom middle). Export HX4 added nPSF (though you will have to derive the 'in race' on your own)

Donnie FIG2 is accessed by pressing the <F8> while viewing FIG2. Sure, the TPG grade can be added next to the trainer name as it is in the regular FIG2.

edster42
12th August 2011, 12:30.43 PM
Thx Ken, i didn't notice it in the robot. The export request would be used to test my present spot plays with npsf in race.

having the tpgm as close to the middle of the fig2 screen (i use the Donnie version) would allow my eyes to focus on the figs while scrolling.

km
12th August 2011, 01:06.36 PM
edster

1) The HX4 data field file output specifications have been finalized for 2011. At this point i can only fix bugs or adjust the existing data contents with an update. Start a thread in the Access forum and ask how you can ascertain "PSF in race" from the nPSF = 1 data field.

2) The header lines in the FIG2 screens are difficult to re-format. That's because each character position has to be slotted and spaced one at a time. It takes many hours to do it. I thought you wanted to add the TPG (Trainer Grade) to the Donnie FIG2, which would have been a cut-and-paste from regular FIG2 header top line. But to put the tPGM (program number) on the bottom par line would be a lot of extra work to insert and I'll have to decline for now.

edster42
12th August 2011, 01:23.14 PM
thnx for looking in to it.

jack
12th August 2011, 03:12.57 PM
Thanks everyone. Jack.

ClockerQ
12th August 2011, 05:35.15 PM
Can somebody send me the link that explains Donnie's Fig2? I noticed the solid line that seemed to mean a long layoff but on the first race I looked at it was there for a 17 day break. No trainer/jock or any other major changes apparent. So I'm confused already. :confused:

km
12th August 2011, 06:28.44 PM
I don't remember the nuances either 'Q, we better invite Donnie to get involved in this, it was his screen developed for the seminar one year, i use regular FIG2.

David-LV
13th August 2011, 11:20.34 PM
I think you have to press F7 to turn on Donnie's Fig2 screen. When you press F8 it takes you back to the original F2 screen.

________
David-LV

km
13th August 2011, 11:28.43 PM
<F7> = DFIG, <F8> Donnie Custom

True that both are Donnie's idea - his footprints are all over HTR :D

bbopjz
14th August 2011, 01:29.10 PM
what exactly does the header "BET" mean?

Rick
14th August 2011, 01:43.55 PM
Check out the July/Aug 2008 Newsletter. That should be in the HTR Library.

BET = perhaps the most important grade on the sheet. Reveals what the trainer is returning to bettors.
A or B = exceeding expectations and returning fair value or even flat bet profits to bettors.
C = average returns to bettors.
D or F = the bettors are being shortchanged wagering on this trainer’s horses, odds are underlayed.

DanG
15th August 2011, 10:39.13 AM
Down the road perhaps… :)

Preface: I know this has been discussed before and is no doubt a programming logistical nightmare. :eek:

With more then 1,000 races being taken off the grass each year the ability to somehow manually override the dist would just be tremendous. These tracks who card turf distances that don’t exist on their main (I.e. Saratoga 8f or 8.5f etc) cause the 'wizard to blank, PL-5 can seek a better match etc.

Changing the dist through the auto-scratch would be the best case scenario, but I don’t believe Equibase can be relied on for that detail as of yet.

BillW
15th August 2011, 12:31.11 PM
Down the road perhaps… :)

Changing the dist through the auto-scratch would be the best case scenario, but I don’t believe Equibase can be relied on for that detail as of yet.

Equibase has their own people (chart callers) maintaining the scratches and changes data now and not the tracks as was the case a few years ago. I wrote Chuck Scaravilli and asked him this specific question and will report back when I hear from him.

BillW
15th August 2011, 12:39.00 PM
I just got an affirmative answer back from Chuck. This is one of the data points included the the real time changes that they maintain. I would assume this data is included in the feed to HDW, but Ron would have to chime in on that.

http://www.equibase.com/static/latechanges/html/latechanges.html

DanG
15th August 2011, 12:51.09 PM
Thank you for that information Bill. Once again the Horseplayer association working unselfishly behind the scenes for all of us. :cool:

Huguenot
16th August 2011, 01:45.45 PM
"Sloppy" tracks as their own category.
Right now I feel "wet dirt" is fairly useless as there are so many iterations of "wet." Seems to me, sloppy is the most common.

del_dog
16th August 2011, 02:48.34 PM
there is no way to know.

get a price or no play imo.

km
16th August 2011, 05:56.06 PM
We have two sources in HTR that output the actual labeled track condition;

1) Comma delimited Chart files (must be downloaded with File Rat)

2) HXT export (requires 30day or 1yr Track Profile download)

These two can be used to separate "wet" into "sloppy", "muddy", "wet fast" or "good" ("heavy" and "muddy" are almost extinct)

Scroll to bottom of HTR Library for the file specs.

There is too much ambiguity with track condition labeling to go beyond "wet" in Robot2 or HTR2. The labels are no longer applied by management for realistic surface assessment, but rather to appease bettors and trainers that things are not as bad as they look. Scratches and handle drops are severe with any "wet" conditions, so they try to mask it to save the day. Thus the invention of "wet fast".

pilot12321
10th September 2011, 03:44.36 PM
I would love to see a hide feature, I know I can use the scratch button, until the results are in.


Thanks Wayne

km
12th September 2011, 01:05.24 AM
Wayne, thanks for the feedback, we tried a "hide" feature years ago, it caused some unexpected problems that I won't go into. Suffice to say that HTR has mountains and valleys of code that are connected horse to horse. Simply 'hiding' a horse or blanking from the screen seems like a simple task, but in reality, it causes a domino chain of events to occur. We have to go one way or the other - scratch (remove from all computation) or "hide" (simply remove from view) - not both. Obviously we need the option to Scratch as priority.

pilot12321
12th September 2011, 01:29.46 AM
Thanks Ken


Wayne