Database Handicapping Software- JCapper

JCapper Message Board

          JCapper 101
                      -- TrackWeight Table Interface

Home Register
Log In
By TrackWeight Table Interface
TPW
2/8/2009
10:20:22 AM
Jeff,

Interested in experimenting with this table and hoped you could define each of the columns in the table and how they are best used.

Can anyone on the board tell me if they are using this table and give me some insight in how they may be using it?

Thanks,

Terry

Reply
jeff
2/9/2009
4:32:36 AM
Terry,

I'll have to do some digging for a write up I started when I first created this.

The short version is...

For those looking to do so, the interface provides a quick way to adjust for changing track conditions on the fly.

It provides a way for you to adjust the imnportance of both early speed and late speed upwards or downwards based on how a track-surface-distance category is playing and have the effect be reflected in your UPR.

The interface itself works in a manner very similar to the Profile Table Interface. You make one entry for each separate Track-Surface-Distance category and activate or deactivate entries using the Active field.

Let's say you are playing live and you notice that a given track-surface-distance category (TPX Sprints for example) is speed favoring today as opposed to normally being speed tiring.

Without changing any of the entries in the IVTable driving your UPR you could write a quick entry to the Track Weight Table Interface as follows:

Active: -1

Track: TPX

Surface: D

Min Dist: 0

Max Dist: 6

Track Weight: 2
(Note: doesn't affect anything - this field is just a label to help individual users categorize degrees of track weight.)

CPaceWtAdj: 1.30

CompoundLateWtAdj: 1.00


The next time you run a Calc Races you should notice a different UPR.

What changed?

The weight for/importance of CPace in your UPR was bumped up by 30 percent.

The weight for/importance of CompoundLate in your UPR was kept the same.

The idea behind this is to allow users to adjust for different track conditions on the fly.

Conceivably, you could keep a set of inactive entries in the table for the circuits you play... where you'd have inactive entries emphasizing both early speed and late speed... allowing you to adjust your UPR on the fly by activating (or deactivating) Track Weight entries based on what you see happening on the track in front of you.

Ideally, you'd want to revisit UPR to reflect any long term effects of track weight. But that's hard to do on race day.



Oops... I think that write up is actually longer than the original.


-jp

.



~Edited by: jeff  on:  2/9/2009  at:  4:32:36 AM~

Reply
TPW
2/9/2009
8:21:45 AM
Thanks for the explanation Jeff.

Terry

Reply
jager fury
2/17/2009
10:53:43 AM
Just another insane, profit generating angle possible with Jcapper, with the usual endless possibilities. Brew another pot of coffee:)

Reply
Jens
2/22/2009
11:04:05 PM
Jeff,

Just checking to make sure I'm not missing something. Based on both your explanation and some testing I did it appears the use of the trackweight table interface requires the use of both CPace and CompoundLate (which I didn't use) as factors in your UPR. Is that correct?

Reply
jeff
2/23/2009
1:38:28 AM

quote:
Jeff,

Just checking to make sure I'm not missing something. Based on both your explanation and some testing I did it appears the use of the trackweight table interface requires the use of both CPace and CompoundLate (which I didn't use) as factors in your UPR. Is that correct?

Yes. That's correct.

If your UPR doesn't use either factor and you want to take advantage of a noticeable track bias, then you'd need to use some other means of adjusting UPR to either elevate or reduce the importance of early speed on race day.

-jp

.

~Edited by: jeff  on:  2/23/2009  at:  1:38:28 AM~

Reply
Reply

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