Well, a Profiler database contains information about the relative abilities of each horse. It is important to note the word “relative” here. Profiler databases do not contain such things as speed figures, pace figures, beaten lengths, and such. They contain information about the analysis EquiSim does on each horse. Who had the best speed figure based on the way EquiSim (and you) saw the race? That sort of thing. In general I refer to these things as factors or “abilities”. They include things such as Best E1, Best Speed Figure, Best Late Pace figure, etc.. In addition to storing this information about each horse, EquiSim ROI 4.0 now cross references these factors with the connections of each horse (trainers, jockeys, owners) and tracks the values via the Profiler. Collectively, this information is referred to as Connection Stats. EquiSim takes this sort of information – these “factors” and “abilities” – and boils them down to a few numbers. These numbers we’ll refer to as the Profiler Values – there are a number of them: the Profiler Value based on a combination of all the horse’s abilities, the Trainer Value, the Jockey Value, the Owner Value, the Sire Value, and the Comp Value that is a combination of all the values together. This information is also stored in the Profiler database.
With that background we can move to talking about configuring the Profiler Database. There are two reasons to configure the database:
A) To control the size of a database, and, in doing so, the time it takes to perform analysis on a database, you may wish to avoid storing certain types of information that you do not care about.
The Profiler Values mentioned above are directly related to the types of
factors and connection stats stored in a Profiler Database.
So - configuring the database lets you pick and choose what factors go
into the making of these values. Since
the Selections Performance Analysis Tool (SPAT) lets you see how well each
Profiler Value is performing in myriad different situations, this is the perfect
way to create your own “system” to find contenders with.
The configuration tool lets you develop the basis of the “system”,
the SPAT lets you analyze its performance.
The fact that there are so very, very many combinations of things to make
up the Profiler Values means that your “system” will likely be different
than anyone else’s.
Here’s how to perform the configuration:
· Get to the Profiler Preferences property sheet. You can do this in a number of ways. Here’s one: go to the PDM and select “Profiler Preferences”
· In the PPR select the “Setup” tab. Here you can switch between the connection types (Horse, Jockey, Trainer, Owner, Sire). With each connection type you can establish whether or not you want to STORE data values for each “ability” AND whether you want to “Use” the ability in the program. If you do NOT choose to use an ability then:
i. The ability will not appear in any of the views, such as the Profiler View
ii. The ability will not be used in the computation of the various profiler values it relates to.
· There are “standard” abilities (std.) and Connection (cxn) abilities. Standard abilities are the ones that are most typically associated with things relating to the performance of a horse in a race (but not always). Cxn abilities are those that are more about the circumstances of a race.
· Note that the Horse Std. Abilities are “always” stored.
· Now click on the More Config tab. The fields on this tab let you further set up the database in the following ways;
i. You can specify the criteria for certain Connection abilities. For example, hat should “low odds” be considered?
ii. You can specify which types of races are allowed into the database you are connected to.
iii. You can tell EquiSim whether or not to STORE profiler values in this database. If you do this, then it will take longer to store races because they must all be profiled before storing. If you do NOT do this, then you can store data faster, BUT, the SPAT will not be able to tell you how well the Profiler Values perform statistically.
iv. You can specify that only NATIVE races should be stored. See – some cards (the ohio 7/7) contain races for more than one track. If you have both race cards, and you store both, you could end up storing the same data twice – and this can lead to problems. NOTE – you can use the “Prevent Restore” option in the PDM to accomplish this very same thing. Personally, I leave both options on.
v. You can tell the program what the minimum races required are to store a race’s profiler values. Imagine the first time you get a set of profiler values – which horse has the best value? The answer is – all of them. And this does not make for very good stats. Profiler values come from statistics derived from data in a database. When you first start out the database is empty and, thus, all the profiler values are Zero – and everyone is tied for first place. This problem continues until there are at least a good handful of races in any particular profile. The ability to set the minimum number of races simply lets you avoid irrelevant data that will appear when not many races match a profile.
vi. You can tell EquiSim how many races to STOP at (most recent first) when generating a profile using the Store By Tracks command. This is important if you are working with a very large database as the more races in a profile, the longer it takes to profile. It can also be useful if you are only interested in getting CURRENT races in a profile (again, the races chosen are from the most recent first).
Questions or Comments? Contact email@example.com
horse racing handicapping thoroughbred software discussion forum race equisim equibase daily racing form thorotech equisimroi simulation