JCapper Message Board

JCapper 101
-- Enforce Paceline Logical Surface

Home	Register Log In

Enforce Paceline Logical Surface

busseb
2/27/2011
1:17:33 PM

Does checking this box in the System Definitions enforce
to surface condition also - dirt fast to dirt fast or is it just
any dirt (sloppy) to any dirt condition(fast)?

Seems like the numbers on sloppy tracks are usually inflated
and I'd like to eliminate them in paceline selection.

Also, do I need to do a database rebuild after checking the box
or is paceline selection done during calculate races?

ElPaso

~Edited by: busseb on: 2/27/2011 at: 1:17:33 PM~

jeff
2/28/2011
5:38:24 AM

--quote:

"Does checking this box in the System Definitions enforce to surface condition also - dirt fast to dirt fast or is it just any dirt (sloppy) to any dirt condition(fast)?"

--end quote

The algorithm separates running lines into two categories:

1. dirt

2. turf

Checking the Enforce Logical Surface box causes the following:

1. If today's race is on a dirt course, the algorithm will select the horse's best dirt race from within the user's number of races back and time frame constraints.

2. If today's race is on a turf course, the algorithm will select the horse's best dirt race from within the user's number of races back and time frame constraints.

--quote:

"Seems like the numbers on sloppy tracks are usually inflated and I'd like to eliminate them in paceline selection.
"

--end quote

Believe it or not, I've been working on a more robust set of options for defining paceline selection rules on the User Sys Defs Screen. The expanded rule set includes options for dry to dry lines, wet to wet lines, etc.

Screenshot here:
http://www.jcapper.com/messageboard/avatars/usersysdefs02282011.jpg

Keep in mind, my own R&D very clearly indicates very little long term roi boost potential exists in the "If I had only selected the right paceline" area of things... I'm mainly adding the new drop downs because I'm tired of hearing the "But picking pacelines is important" objection from new/would be software customers.

A glance at the current Paceadvantage.com PAIHL contest standings after 8 weeks - not just points but total $$$money returned - shows some JCapper teams to be prominent -- while at the same time quite a few others who demo'ed JCapper within the past 6-12 months and then gave me the "paceline selection is king" objection when the demo expired aren't nearly as prominent in the results... I get a smile from that because it kind of confirms all those R&D hours. Just because you read it in a book doesn't mean it's true.

Just because you read it in a book doesn't mean it's true.

--quote:

"Also, do I need to do a database rebuild after checking the box or is paceline selection done during calculate races?"

--end quote

Any time you change your paceline selection rules, those rules take immediate effect for the next number crunching routines that you run: Calc Races, Build Database, etc.

If you persist new rules on the User Sys Defs Screen then the very next Calc Races routine you run will cause the effect of your new rules to be reflected on your next html report.

However, the act of persisting new rules does not change existing data content sitting in pl_profile.txt files and/or the starterhistory table.

After persisting new rules, you would need to rebuild any folder from scratch and repopulate the starterhistory table for that folder before you would be able to see the effect of your new rules in the Data Window for the starters in that folder.

-jp

.

busseb
2/28/2011
5:21:05 PM

"There you go again!"

Always one step ahead of us as usual.

Thanks!!

JCapper Message Board

JCapper 101 -- Enforce Paceline Logical Surface

JCapper 101
-- Enforce Paceline Logical Surface