As usual, great wish Tek. Thinking about the storing of the charts in this light makes me wonder why I ever did it the way I did it.... It's so bizarre that its stuck out there in left field that I'm assuming there was a reason, but can't think of one. Sometimes you can out-design yourself....

[QUOTE]Originally posted by TekCapper:

(5) Have a paceline selection criteria which is customizable, not just for simulation bias settings but for general use,... allowing for use last race with no excuse, find most suitable race, ignore trip trouble in selection, etc.

(8) Add the ability to "hide" columns in the formula view so that they do not print.[QUOTE]

Tek,
Great Ideas for sure... I know you can force the program to choose the last race, but I would also like to see in #5, Especially from the FV filtering list, the ability to automatically select last 2, last 3, last 4 races etc. without have to select them manually from the form window.

Hiding columns would deffinately be a + since I export FV to CSV & Excel almost always.

Here's something that I'm sure everyone would like to see... A MAJOR WISH FOR ME... Is not having to go back and re-select the template I was using when I change from one race to the next... Im not sure if this is a bug or what. But it sure is annoying!

These updates would truly be a big help for me.

Excellent posts guys...

John

~¿o

Nathan,

Now that I have DB DIRECT... here's another one to add to the wishlist:

(30) This is especially useful for users of DBDirect who have "Store Profiler Values" checkboxed in the Profiler Preferences and what to run FV templates through a DB using DB Direct and reference stored profiler values: Have a new series of FV variables which can pull the stored profiler values from the connected Profiler Database. Something like: $hrSimFinishDB, $hrProfValDB, $hrProfRankDB, $hrCompValDB, $hrCompRankDB, $hrTrainerValDB, $hrTrainerRankDB, $hrJockeyValDB, $hrJockeyRankDB, $hrOwnerValDB, $hrOwnerRankDB, $hrSireValDB, $hrSireRankDB, which would pull these stored values (as shown in the chart viewer), otherwise return zero or -1000.

Nathan,

Is there anyway you can supply functionality that will parse the race classification into 3 parts:

classClass
classAmt
classCond

For example, some race classes:

Md12500
Clm5000n1y
fMdSpWt
fClarkcnty75k

would parse out as

classClass classAmt classCond

Md 12500
Clm 5000 n1y
fMdSpWT
fClarncnty 75 k

Or if you have a way to do this with FV: I'm stumped. I'm trying to do something with movements between classes and not having any luck figuring out how go go beyond what ES provides. The up/down profiler seems to be limited to the last race.

Thanks,

Scott

I've attempted to do this in the past but stopped due to the "un"standard way in which the race names may be implimented across tracks and data providers.

You could get class in Formula View:
rrClass (or ppClass for past perfs)

Amount is difficult because some races don't indicate this - mdspwt, for example. Purse maybe a better indicator anyway:
rrPurse

Condition/Restrictions is a real pain - often the name of the race is not a good indicator -- and it would only be available for past perfs. The info is usually embedded in the textual description of the upcoming race. I haven't had much luck doing anything with it.

Yes, I feel the pain on this. Let me expand a bit more however. This likely pertains to only claiming and allowance races. For listed stakes races the purse should be enough to determine a higher class - I would think a 100K stakes race is of a higher class than a 75K race. The PP's indicate the graded stakes levels so that's easy.

Maidens are also simple: MSW is higher then MDN. But would MD10000 be higher than MD7500? Probably. Even so, for maiden claimers the pp have the claiming price in another field so that could be accomplished with the available FV logic.

But for claiming and allowance, it's the n2x or similar conditions that have me stumped. I'm really looking for a way to grap a hold of these conditions to determine class. Steve Davidowitz points out in "Betting Thoroughbreds" that class movement at lower class tracks (the kind of tracks I usually play) is widespread so a CLM1000 is not the same class as a CLM1000n2y; and this race could be a much tougher race, by lengths, than CLM1000n2x

So, to net this out, I'm trying to figure out how to grap the condition part of the class out of the PP. In this way I could tell based on the last X number of races that pp classes like this:

CLM1000n2y
CLM1000
CLM1000n2x

the horse appears to have, for now, reached a ceiling of open 10k claimers and needs some easier competition by running with horses that have not won twice in the last Y period of time.

Scott

Nathan,

Any idea on when you can make some of our "wishes" come true? This list is almost 2 years old.

Sort the races in Match-up screen chronologically from most recent down. Now it seems kind of random. It's usable, but a little frustrating since I'm only interested in the match-ups if they occurred in the last one or two races in a horses PPs.

-KG