First pass, i'm going to replace the equivalent BRIS numbers with his (if the option to do so is selected), and make non-equivalent info available via Formula View. I don't know if his figs will work well with the simulator or not, but they will be tracked as Dom/Best/Weak, etc figs in the Profiler

Nathan, I previously requested 3 categories to select on the CXN report, but I was wondering how much trouble it would be to put 4. I believe that with 4, you would have an infinite number of possibilities. Example: Trainer, Jockey, Surface, Distance. or Jockey, Surface, Distance, Run Style. etc. etc.
Thanks for your consideration.

Tom

Hi Tom,

I looked into this the other day. Unfortunately, it doesn't look feasible. I knew there had to be some reason I didn't do it to begin with.

The reason is that the connections stats are stored in the database on a cumulative basis. That is, a record consists of a track, cxn name, cxn type, the cxn ability, the ability type, and then the number of occurrences, wins, places, shows, earnings, etc..

This was done to save space in the database. In order to add the ability to query by date range, surface, etc, a record would need to be added for each occurrence of the stat. This isn’t very feasible with 1 gig limits on jet 3.5 databases and the amount of non-cxn data already stored per race.

The only alternative I have at present would be a custom DB created using DB Direct. Beyond V6, there is the possibility of updating ES's db capabilities, or creating a separate application to tackle connections independently.

Best,
-Nathan

Nathan, Thanks for your quick response. I didn't realize that it was that involved. I only suggested it as I rely heavily on the CXN search capabilities. Anything you can do to improve what you have, would be great.
Thanks again.

Nathan,

How about an option in the Sim Tuning Wizard to allow for turf "off" tracks to be included? I understand the reason to not include dirt off tracks in a "fast" tune, but with fewer turf races being run it would (might?) be beneficial to have the option to include all turf races no matter what the condition.

Or, if your really up to coding how about the ability to specify the number of races in the Tune as opposed to the number of cards?

HH

I would like to see an ES proprietary early speed and late speed number. Something generated by ES that no one else has. Sort of like CJ's Early Speed Number and his Late Speed Number based on the last 3 or 4 or 5 races. And have those number pop up in the form view and also be Profile Numbers.

How about some odds information in the Profiler View. Sometimes we see something like

Weak E2
10 races
35 starters
10% Win
75% ROI

It would be nice to see

15 @ .5:1 to 2:1
9 @ 2.1:1 to 4:1
10 @ 4.1:1 to 6:1
1 @ 108:1

to see how many big odds winners have skewed the results.

Interested in querying the first 2 call positions from today's race. Which can be done if using the BRIS Comprehensive Charts.

The reason is that we can test ROI wise how effective certain factors perform, but what can't be tested is how effective an algorithm is at determining the leaders at the first 2 call positions.

For example, how effective are the Quirin Speed points at determining the 1st call leader or the 2nd call leader. Or, How effective is the Running Style lableing .........

This would also allow for proprietary algorithms which IMO would be very beneficial to anyone's bottom line.

This message has been edited. Last edited by: Holding Pattern,

Hi Nathan, Happy Holidays

Don't want to be a P.I.T.A., but I hope that you might be able to provide us some more FV variables from the Bris data fields.
They would be the race fractions from fields 876 to 985 (although the 12f + up times are hardly necessary).

I know that we have the race variables $ppFractOne, $ppFractTwo, $ppFractThree, and horse variables $ppHFractOne, $ppHFractTwo, $ppHFractThree and $ppHFract2 thru $ppHFract16, but presently there are many route races where you can't get a horse's correct split times.

With Bris now giving us the beaten lengths at the first quarter in races at a mile and over ($ppStartBtnLengths), I think it makes sense that we should use them to get accurate quarter times. Right now if you use $ppHFract2 in routes, ES is calculating the 2f time by using the 4f beaten lengths (or an imprecise algorithm) and it will frequently give the wrong time. If we had a $ppFract2, in those races we could easily get the correct 1st quarter by using it with $ppStartBtnLengths.

Other errors include wrong closing fractions....looking at CRC12/26 race10 #10 Presious Passion....if you want to get his last quarter, it should be ($ppHFinalTime[0] - $ppHFract10[0]), but FV then gives that time as 27:57 (actual is 24:11). You can get it correctly by using ($ppHFinalTime[0] - $ppHFractThree[0]), but if you use only the three fractional splits, you then can't see his 1st quarter was 23:08 (using $ppHFractOne will tell you that he ran the 1st half in 45:14).

Redoing the $ppHFract variables would be another way to get there, but I'm sure that it will be a big pain rewriting those algorithms, and personally I'd rather just have access to the race leader fractions.

Here's hoping that you'll be able to squeeze these in.

Thanks
W

Nathan,

Nice work on the FV export ! So much easier now that all can be exported into one file !

Thanks,

Z