|If you name your A, B, and Neg UDMs according to the naming schema in the help doc, when you generate reports in the WagerHistory Module, the module has the ability to break your WagerHistory data out by the number of A, B, and Neg UDMs flagging the primary horse persisted for each ticket.|
Link to the WagerHistory Module Help Doc:
"UDM Count Data Fields--end quote
A well thought out set of UDMs can paint a very accurate picture about the strengths and weaknesses of horses flagged by them. The interface enables the player to persist a hard count of each UDM type to the WagerHistory table. Once enough data has been recorded, the interface enables the player to gain valuable insight about the way his or her UDMs interact with one another for the horses bet by the player.
The interface was designed around the following UDM types:
A UDMs These are your best business UDMs the ones you (should) put most of your focus on.
B UDMs These are good UDMs (that under the right conditions) can point out playable horses. But they are not as good as your A UDMs.
Negative Expectation UDMs These are UDMs designed to point out weaknesses in horses flagged by them.
UDM Count A
Use this (optional) data field to record the number of A UDMs flagging an individual horse.
UDM Count B
Use this (optional) data field to record the number of B UDMs flagging an individual horse.
UDM Count Neg
Use this (optional) data field to record the number of Negative Expectation UDMs flagging an individual horse.
UDM Count Auto Populate Feature:
When a new record is created for a horse, the interface assembles and displays the UDM profile for that horse. To relieve the player of the (tedious) need to manually determine (and key in) the count of UDMs by UDM type for each horse, the interface contains an algorithm that robotically counts the number of UDMs (by UDM type) found in a horses UDM profile. When the UDM profile is first pulled up by the interface, the player is prompted by the interface (Y or N) whether or not to auto populate the UDM count data fields. Answering Yes when prompted will cause the interface to auto populate the UDM count data fields.
UDM Naming Schema:
The following UDM Naming Schema will enable the Auto Populate Function to identify UDMs according to UDM type:
A UDMs First 4 characters: 0_A-
B UDMs First 4 characters: 0_B-
Neg UDMs First 2 characters: X_
Neg UDMs First 2 characters: Z_
Neg UDMs First 3 characters: XX_
Neg UDMs First 3 characters: ZZ_