JCapper Message Board

JCapper 101
-- UserFactor Choices

Home	Register Log In

UserFactor Choices

Hdcper
5/12/2008
1:17:37 AM

Jeff,

I looked at the dropdown window of factors that can be used in a Userfactor/UPR. Is it possible to print out the choices or could you post a listing for ease of printing them out?

Further, is is possible to add UPR as one of the factors or do we need to clone our existing UPR as Userfactor 1 to apply it to another userfactor?

Anyway to also add Compound Pace Fit as a factor of choice too?

Thanks,

Hdcper

jeff
5/12/2008
12:56:40 PM

quote:
Further, is is possible to add UPR as one of the factors or do we need to clone our existing UPR as Userfactor 1 to apply it to another userfactor?

UPR isn't a valid factor choice and can not be used to create UserFactors.

This is by design.

Undertanding that design is important because it makes UPR the top (and potentially the most powerful) factor that you can create.

Here's how it works:

The program creates the factors one at a time in a predefined sequence - in the following order:

1. JPR
2. UserFactor1
3. UserFactor2
4. UserFactor3
5. UserFactor4
6. UserFactor5
7. UPR

The sequence in which the factors are created produces some rules (based on logic) that define what can be used and when.

At the point in time when the program reads IV Table entries to create any one factor, all factors in the sequence that come later (those that have not been created yet and will be created later) do not exist yet - and for that reason can not be used in the factor mix.

Factors that already exist CAN be used in the factor mix.

Some examples:

You are creating JPR. UPR and UserFactors 1-5 have not been created yet. Because none of them exist they are NOT available for use in the factor mix.

You are creating UserFactor2. JPR and UserFactor1 have been created. Because they already exist you CAN use them in the factor mix. UserFactors 3-5 and UPR have not yet been created. Because they do not exist yet, you CAN'T use them in the factor mix.

You are creating UPR. JPR and UserFactors 1-5 have all been created. Because all of them exist ALL of them ARE available to you in your factor mix.

This is an important point in the design. UPR is the last factor in the chain to be created. There is a reason for this. Because UPR is the last factor to be created, any and all factors previously created are available to you in the UPR factor mix. This is not the case with factors created earlier in the chain. This makes UPR (potentially) the most powerful factor you can create.

I hope that makes sense.

quote:
Anyway to also add Compound Pace Fit as a factor of choice too?

Open up the factors drop down in the IV Table Wizard and scroll down. The Compound Pace Array Factors are listed separately towards the bottom. The individual factor selection is PACEFIT.

quote:
I looked at the dropdown window of factors that can be used in a Userfactor/UPR. Is it possible to print out the choices or could you post a listing for ease of printing them out?

So far as a printable list I'll try to get the Help Doc updated as time allows.

-jp

.

~Edited by: jeff on: 5/12/2008 at: 12:56:40 PM~

Hdcper
5/12/2008
1:54:04 PM

Thanks Jeff, makes perfect sense to me.

I must of missed Pacefit when I looked at the dropdown.

Time to do some research and testing.

Bill

jeff
5/13/2008
12:53:16 PM

--quote:

"Hey Jeff,

Thought about posting this on Jcapper board but thought maybe you would rather have me email.

There are three factor choices for Upr/Userfactor wizard that I am not familiar with: Classcompos, Clshift2 and Claimraces

I don't see anything in the data window to look at these factors, except for Cls2 in the dropdown section.

Can you give me an overview of what each is and how to research them in the data windown?

Any insight would be helpful,

Bill"

--end quote

Bill,

ClassCompos is identical to ClassRating - This number represents a class rating derived from the Bris pars found in each running line of a horse's past performance record.

Note: ClassRating is only possible when Bris files are used. In TSN data files the fields that contain par for the level info driving ClassRating are left empty and contain no data. When TSN files are used all horses in each race are given a ClassRating of zero.

ClShift2 is identical to Class Shift (Par vs Race Strength) - This number represents a change in class based on the difference between the Standard Race Strength of a horse's most recent race compared to the Bris Par for the Level of today's race. When Race Strength is higher than Par for the Level, Class Shift (Par vs Race Strength) will have a positive number and the horse will be dropping in class. When Race strength is lower than Par for the Level, Class Shift (Par vs Race Strength) will have a negative number and the horse can be thought of as rising in class.

Claimraces is identical to ClaimRacesBack - This is a number that represents the most recent running line looking backwards through a horse's past performance record that shows a horse was claimed out of that race.

Hope that helps...

-jp

.

Hdcper
5/13/2008
3:45:16 PM

Thanks,

Bill

bill uminn
5/27/2008
8:47:46 PM

Jeff, or anyone,

I believe I understand the logic above, but I am having some diffuculties with building UFs. I built a UF1 and UF2 fine, but wanted to combine UF1 and UF2 in my UF3 etc...I am getting all zeroes in the data window for UF3.

Wondering if anyone has an idea of what I could be doing wrong? Or am I misunderstanding something and UFs can't be built that way.

In my UF3 I put USERFACTOR1 with Impact values etc...just like i would with any other factor.

Thanks

jeff
5/27/2008
11:15:25 PM

Bill, Two possible cases...

Case 1.
If final calculated values for your UserFactor3 normally would be < 1 (as would be the case for rider and/or trainer win pct) then you'd expect to see zeroes for UserFactor3 on the HTML Report as described earlier in this thread... UNLESS you've installed the latest program version - In that case you should see the decimal pct values converted/multiplied by 100 before they are displayed on the HTML Report.

Case 2.
If final calculated values for your UserFactor3 normally would be >= 1 (as would be the case for normal IV values and factor combinations) then you'd expect to see whole numbers and not zeroes for UserFactor3 on the HTML Report and in the Data Window - with or without the latest program version.

If this is the case and you are seeing zeroes on the HTML Report or in the Data Window - double check to make sure that you've:

1. Defined a surface requirement for each factor that you've grabbed. (Hint: The surface requirement field can not be blank.)

2. Defined a non zero factor weight for at least one of your factors. (Hint: The factor weight field can not be blank.)

3. You are not using multiple factors where one of those factors has a 3 Translate behavior. (Hint: Translate is a single factor function only. If you ARE using a 3 Translate behavior make sure that your UserFactor3 GroupName grabs only one factor.)

4. Dumb as it may sound make sure that the Active box is checked for at least one of the factors you are grabbing.

5. Dumb as it may sound make sure that the factor names for the factors you are grabbing are spelled correctly as listed in the factors drop down and the Help Doc.

Those are probably the most common errors I have seen users make.

If you think you've done everything right and are still seeing zeroes shoot me an email. Attach your c:\2004\JCapper.mdb file or a cut & paste of the IVTable Detail Reports for your UserFactors. I'd be happy to take a look and get it figured out for you.

-jp

.

jeff
5/28/2008
2:59:30 PM

Bill, Received your email. It turns out you were doing everything correct on your end. Stepping through the source code of the UserFactor building block algorithm I spotted the problem - which turned out to be simple human error on my part. A free program update addressing the problem is now available in the Downloads & Tech Suport Forum.

THANK YOU for discovering this and bringing it to my attention.

-jp

.

JCapper Message Board

JCapper 101 -- UserFactor Choices

JCapper 101
-- UserFactor Choices