Database Handicapping Software- JCapper

JCapper Message Board

          JCapper 101
                      -- UPR Track-Specific Override?

Home Register
Log In
By UPR Track-Specific Override?
crestwood1972
9/1/2012
7:13:41 PM
I have a generic UPR that covers DS, DR, TS and TR for all tracks. If I were to add a specific DS, DR, TS and TR for a specific track (same UPR), would that calculation override the generic one?

I suspect it will but I want to be sure.

Reply
jeff
9/1/2012
10:35:41 PM
How I would do it:

1. Make a backup copy of the c:\2004\JCapper.mdb file before getting started (just in case.)

2. Key the new entries. Make sure each of the new entries has the track code for the desired single track in the Track field.

3. Edit all preexisting entries. Key the track code used for the new entries into the Avoid track field.

4. Check your work (carefully.)

When done, the new entries will only "fire" if the track code matches the track code stored in the Track field. The preexisting entries will "fire" at all tracks where the track code does not match the track code stored in the Avoid field.


-jp

.



Reply
ADAnto
9/6/2012
2:26:07 PM
How I would do it:

1. Make a backup copy of the c:\2004\JCapper.mdb file before getting started (just in case.)

2. Key the new entries. Make sure each of the new entries has the track code for the desired single track in the Track field.

3. Edit all preexisting entries. Key the track code used for the new entries into the Avoid track field.

4. Check your work (carefully.)

When done, the new entries will only "fire" if the track code matches the track code stored in the Track field. The preexisting entries will "fire" at all tracks where the track code does not match the track code stored in the Avoid field.

-jp

Ok. Jeff,

This isn't very clear to me, perhaps a little example would help: point #2 do i start with default UDM and then add new entries w/ track code?

Then #3 Edit the defaults Entries, and enter track codes in the avoid track field, that i just entered?

More i read it and more start to make sense, let me know if I'm right.

Regards, Tony

Reply
jeff
9/7/2012
1:30:39 AM
...point #2 do i start with default UDM and then add new entries w/ track code?...

No. Not a UDM. (A UDM is way off base for this discussion.)




...Then #3 Edit the defaults Entries, and enter track codes in the avoid track field, that i just entered?...

No! The entries under the Default groupname are used to define JPR. If you change those, you change the definition for JPR.

If you've done your homework and are sure you know what you are going, and you really do want to change your JPR definition - go for it!

But for the other 98% of you, best to leave the Default groupname entries alone!

Understand that for purposes of this discussion, that we are talking about UPR - and that edits to UPR are accomplished by editing the table entries under the user's (user defined) UPR groupname.

I'll use this SCREENSHOT as an example. It shows table entries for my own univeral UPR for the factor AFR. Because the Track field is empty, I know at a glance that it isn't track specific.

Crestwood1972, who posted at the top of this thread, started out by creating a UPR groupname. To make that happen he crafted a set of ImpactValues table entries that defined his UPR at all tracks. It's likely that some of the table entries he used look a little bit like the set of table entries I used for AFR in the above screenshot.

Once Crestwood1972 had his entries in place he asked about adding a set of track specific table entries to that UPR groupname. His goal, as I interpreted it, was to have the newly added entries "fire" at one specific track - and have all of the previous entries "fire" at all other tracks.

The way I would do it, using the set of (preexisting) AFR entries in the above screenshot as an example (and using track code TPX for the sake of argument) would be to edit the set of preexisting AFR entries by keying TPX into the Avoid field and hitting the Save button.

From there, I would create a new set of AFR entries designed to handle track code TPX, and I would make it handle TPX by keying TPX into the Track field.

When it's all done, the preexisting entries avoid TPX and the new entries require track code TPX.

Hope I explained most of that in a way that makes sense.



-jp

.


Reply
ADAnto
9/8/2012
8:53:25 AM
Sorry Jeff,
I did mean UPR not udm.

So the way i understand it now, is first create a Universal UPR from scratch fo all distance/surface and then do the editing and avoid the specific Track with the new entries?

Regards, Tony

Reply
jeff
9/9/2012
2:18:58 PM
Tony,

You wrote:

"I did mean UPR not udm."


My reply:

I thought that might have been the case.

Please understand my goal isn't to just get the original poster's question answered. I'm also trying to answer each question in a way so that members of the JCapper user community in the future who have questions about that same topic can search the topic - find my posts - and get their questions answered too.

To make that happen, I have to be literal. If a guy types UDM instead of UPR, my answer has to address what was typed out.




You wrote:

"So the way i understand it now, is first create a Universal UPR from scratch fo all distance/surface and then do the editing and avoid the specific Track with the new entries?"

My reply:

Almost. Yes. First create a Universal UPR from scratch for all distance/surface and then do the editing-

But in the editing part, the strategy I outlined would:

1. Make the preexisting entries use the Avoid field to avoid a specific track code.

2. Make the new entries use the Track field to restrict things to a single track code.


-jp

.






~Edited by: jeff  on:  9/9/2012  at:  2:18:58 PM~

Reply
ADAnto
9/10/2012
9:06:53 AM
Ok. Got it.

Regards, Tony

Reply
Reply

Copyright © 2018 JCapper Software              back to the JCapper Message Board              www.JCapper.com