If you are using Brisnet data: Bris3 is the best Brisnet final time speed fig from the horse's 3 most recent running lines.

If you are using HDW data: Bris3 is the best HDW-Cramer final time speed fig from the horse's 3 most recent running lines.

Fyi, all of the factors with Brisnet names behave that way.

If you are using Brisnet data: Bris10 is the best Brisnet final time speed fig from the horse's 10 most recent running lines.

If you are using HDW data: Bris10 is the best HDW-Cramer final time speed fig from the horse's 10 most recent running lines.

If you are using Brisnet data: Prime is Brisnet Prime Power.

If you are using HDW data: Prime is HDW PSR (or Projected Speed Rating.)

The Preset Filter Tool allows you to define min and max ranges for Bris3 rank. (The filter codes for this all begin with the characters "B3" (without the quotes.)

Screenshot:

If you are operating JCapper in Playlist File Mode: There aren't any filter codes that enable you to use Bris3 numeric value or gap in a UDM.

You DO have the ability to add Bris3 to a UserFactor.

And as soon as you do that:

You get to use rank, numeric value, and GAP for the UserFactor in your Playlist File Mode UDMs.

--Example:

Suppose you are operating JCapper Platinum in Playlist File Mode - and you see something in the Data Window that makes you decide you really need the ability to get rank, numeric value, and GAP for Bris3 into a UDM.

Imo, the best way to do that in Playlist File Mode is to make one of your 8 UserFactors be a direct translation (or replication) of Bris3.

If you aren't yet using all 8 Userfactors - getting this done is fairly easy. You would create a new UserFactor and use the next available number in the sequence.



If you already have all 8 UserFactors in use - your job is a little harder. You first have to decide which UserFactor you want to get rid of.



With that out of the way, still working in the Classic View of UPR Tools:

1. Click the New button.



2. Key the name of the Userfactor into the GroupName field. (Use all caps.)



3. Check the Active Box.



4. Select the factor you want from the factors drop down. (In this case Bris3.)



5. Select ALL * from the surface-dist drop down. (This will auto populate the min and max dist fields as well the surface field.



6. Use a 3 Translate for your Behavior. (3 Translate tells the interface to turn your UserFactor into a direct translation - or exact replication - of the factor you are using.



7. Use a 1 for factor weight.



8. Use 0 default for your method.



9. Use 9999 for high score and -9999 for low score or default impact.



10. Double check your work and hit the Save button.

Screenshot -- Classic View in UPR Tools after creating USERFACTOR4 in such a way that it acts as a direct translation or exact replication of Bris3 just before clicking the Save button:

• If the UserFactor uses a 3 translate behavior so that it behaves as a direct translation or exact replication of Bris3 as shown in the above screenshot:

You now have the ability to bring up any Playlist File Mode UDM in the Modify screen of the UDM Wizard -- and from there select the UserFactor from the factors drop down -- check the test box to make the current factor active -- key constraints for rank, numeric value and gap -- and hit the save button.

Immediately after that, the next time you click the Calc Races button: The UserFactor behaves exactly the same as Bris3 and your UDM will flag horses on your reports based on the factor constraints in the UDM.

• BUT -- creating the UserFactor does nothing to change existing data in your pl_profile.txt file and/or starterhistory table.

After creating or modifying a UserFactor or UPR:

You have to rebuild databases from scratch (to change the data sitting in your databases) before you can evaluate your new UserFactor and new or modified UDMs in the Data Window.