Welcome to JCapper
Author:
Jeff Platt
Last Updated: 10/01/2025
Introduction
Whether you are
just checking out the Demo Version for the very first time or are a long time Registered
Program Owner, let me be the first to say it. Welcome! It is my sincere hope
you will find yourself using JCapper in a way that fits your handicapping
style. JCapper has many features and factors spanning almost every area of the
game. Even so, as of this writing, it is very far from complete. I'm striving
to make JCapper the very best handicapping software package available anywhere
- at any price. To that end I am constantly testing out new ideas, creating new
factors and features, and adding them to the program. Truth be told, JCapper
really is a work in progress - an attempt to achieve the impossible using
vision, the gray matter between my ears, data science, and determination to
create the perfect handicapping program.
Shortening the Learning Curve
There is a world
of information presented within JCapper. As the program's author, I can see
where it might be easy for new users to be overwhelmed. The purpose of this
Help Doc is to outline a path for you to get the most out of the JCapper program
in the shortest amount of time possible.
Where to Begin
Start by working
through the JCapper 101 Class Outline below.
Learn the
material in the order presented. I’ve been teaching new users how to use
JCapper for more than 20 years. In my opinion, following the Class Outline is the best way to shorten
the learning curve.
Demo User
Licenses
Demo Users can do
everything in the program except run Calc Races routines to generate same day
race reports for live play. That privilege is reserved for Registered Program
Owners only. Demo User Licenses are issued to players who are giving JCapper a
try while using the Free Back Data Downloads. Demo User Licenses expire after
90 days.
Temp Eval User
Licenses
Temp Eval Users
can do everything in the program including run Calc Races routines to
generate same day race reports for live play just like Registered Program
Owners. The key difference is Temp Eval User Licenses have an expiration date
just like Demo Licenses whereas Registered Program Owner Licenses are permanent.
Temp Eval User Licenses are issued to players who are giving JCapper a try
while paying for HDW Data.
Registered
Program Owner Licenses
Registered
Program Owner Licenses are permanent (no expiration date) and are issued to
players who purchase the JCapper program outright or who meet the terms of a
Software as a Service Agreement by purchasing 12 or more months of data under
the HDW Monthly Unlimited Data Subscription Plan.
Live Play
As a Temp Eval
User or a Registered Program Owner you have access to all parts of the program.
Even though you have the ability to load data files into the program, get
scratches and changes, and run a Calc Races to generate reports for today’s
races… and even launch the Live Play Module and use it to bet today’s races… I
strongly recommend that you work your way all
the way through the JCapper
101 Class Outline first!
Learn the
material in the order presented.
Once you know
what you are doing and the program Basics are second nature: Then consider using the program
for live play.
User Quick Start
Guide
Getting Started
There is a world of information presented
within the Program. The best way to learn is to pick ONE topic and work
"hands on" with the program until you understand that topic. Then
move on to the next topic. It is highly recommended that you learn the material
in the order presented below in the JCapper
101 Class Outline.
JCapper
101 Audio & Video
Shorten the learning curve: Watch the JCapper BASIC VIDEOS to get
relevant background info that you need to know.
The JCapper
BASIC Videos are here at:
http://www.JCapper.com/Podcasts/JCapper_Podcasts.html
Hint: Bookmark the above page – or goto:
http://www.JCapper.com and click the link labeled JCapper 101 Audio Video.)
About
the JCapper 101 Audio Video Page:
There is an Index Section for different
topics presented near the top of the page. When you click the index link for an
individual topic, page navigation takes you to the section for that topic.
Within the section for each of the individual topics you will find links to
Videos and Audios about that topic. To return back to the Index Section at the
top of the page, click one of the links labeled Back to Index. (But watch the
JCapper BASIC Videos first.)
READ
the Help Docs
All of the JCapper Help Docs are available
online at:
http://www.JCapper.com/DemoVersion/HelpDocs.ASP
IMPORTANT Note about Calc
Races routines in the Demo Version of the Program
The
.DAT file is the only file type that can be loaded into the demo version of the
program and used to run a Calc Races so that you can see the program’s race day
output. (That restriction is lifted in the live version of the program.)
FREE Sample Weekend of back HDW Data
– Memorial Day Weekend 2016 (Courtesy of HDW)
The
following link will get you a downloadable zip file that contains a free sample
weekend of data and results files courtesy of HDW. (Memorial Day Weekend 2016)
This download will enable you to work through the JCapper 101 Class Outline
without having to spend your own money on data.
This download includes a complete
pre-built set of comma delimited .JCP, .XRD, and .DAT files. This is
important because .DAT files (which are created by the JCapper program during
its build database routines) is the only file type that can be loaded into the
Demo Version of the JCapper program and be used to run a Calc Races routine -
so that you can see the program’s race day output.
Link to
back data download with install instructions:
http://www.jcapper.com/JCapMemorialDayWeekend2016.html
FREE Sample Day of Demo Data – June
21, 2012 - (Courtesy of HDW)
The
following link will get you a downloadable zip file that contains a free sample
day of data and results files courtesy of HDW. This download will enable you to
go through the JCapper Demo without having to spend your own money on data.
This download includes a complete
pre-built set of comma delimited .JCP, .XRD, and .DAT files. This is
important because .DAT files (which are created by the JCapper program during
its build database routines) is the only file type that can be loaded into the
Demo Version of the JCapper program and be used to run a Calc Races routine -
so that you can see the program’s race day output.
http://www.jcapper.com/SampleRaceDayData_06212012.html
FREE Weekend of Demo Data (Courtesy
of HDW)
The
following link will get you a download that contains a full four day weekend of
back data and results files courtesy of HDW. This data sample includes every
thoroughbred race run in
http://www.jcapper.com/DemoVersion/Article_2011DemoFiles.html
JCapper 101 Class
Outline
Make the most efficient use of your
time and get the most out JCapper. Learn the material in the following order:
1.
Get these Basics Out of the Way
a. Install the Program: – Watch the Install
Videos on the JCapper Program Downloads Page.
·
If you are running Windows 10 or
later pay attention to the part about getting True Admin Rights by first
enabling the hidden Windows Admin Account and then logging into Windows as an
Administrator. (You need to be logged into the Windows Admin Account in order
to register DLLs and OCX files for the first JCapper Install on Windows 10 and
later machines.)
·
Create a C:\JCapperBuild folder.
Then download the latest Full Program Install Package to the C:\JCapperBuild
folder. Then create a Desktop Shortcut naming the Full Program Install Package
that you downloaded as target of the shortcut - Then finally, right-click the
shortcut selecting Run as Administrator – and install the Program by running
the Extractor and the JCapper Installer.
·
Then working hands on with the
JCapper program one topic at a time, work through the exercises in the JCapper
101 Class Outline.
b. Learn how and where to find
JCapper Help Documents:
·
See the JCapper Basic Videos and JCapper
Help Dos Index Links above.
c. Learn how to change the Settings
on the User System Definitions Screen.
·
Watch the Data Vendor Setting Video
at the JCapper Basic Videos link above.
·
Watch the SQL Mode Setting Video at
the JCapper Basic Videos link above.
·
Watch the User Sys Defs Screen
Walkthrough Video at the JCapper Basic Videos link above.
·
Read the User System Definitions
Screen Help Doc (Doc
#6) on the Help Docs Page at JCapper.com
d. Need a Primer on Folders, Files,
and Windows File Explorer?
·
Watch the Downloading HDW Files and using Windows File Explorer Video. It’s
the very first video at the JCapper
Basic Videos link.
2. Processing HDW Files (JCapper Platinum and Silver)
Learn how to:
1. Persist
the Data Vendor setting in the User System Definitions Screen.
Hint: You need to set the Data
Vendor Setting to HDW before processing files from HDW. You need to set the
Data Vendor to Brisnet before processing files from Brisnet. If you have a dual
data enabled version of JCapper, you can process files from either data vendor
- but you need to persist the correct Data Vendor setting before processing
files from either data vendor.
HINT – this is in the JCapper BASIC
Videos. See also the User System Definitions Screen Help Doc.
2. Use the
File Download Tool in the HDW File Manager to download files from the HDW Site.
HINT –
this is in the JCapper BASIC Videos. See also the HDW File Mgr Help Doc.
3. Use the File Build Filter Tool in
the HDW File Manager to run File Build Routines to create .JCP data files and
.XRD results files.
HINT
– this is in the JCapper BASIC Videos and the HDW File Mgr Help Doc too.
Resources
– Videos and Help Docs:
Watch
the JCapper Basic Videos on the
JCapper 101 Audio Video page at JCapper.com
Read
the DFM and DFM Card Loader Help Doc
(Doc #5) and the HDW
File Manager Help Doc (Doc #8) on
the Help Docs Page at JCapper.com
Watch
the Data Vendor Setting and SQL Mode
Videos in the User System
Definitions Screen Help Doc (Doc #6) on
the Help Docs Page at JCapper.com
3. Processing Brisnet Files (JCapper Silver and JCapper Platinum)
Learn how to:
a.
Persist the Data Vendor setting in the User System Definitions Screen.
Hint: You need to set the Data Vendor to HDW before processing files
from HDW. You need to set the Data Vendor to Brisnet before processing files
from Brisnet. If you have a dual data enabled version of JCapper, you can
process files from either data vendor - but you need to persist the correct
Data Vendor setting before processing files from either data vendor.
b.
Learn how to Download and Unzip Brisnet Files.
Resources – Videos and Help Docs
Watch the following
videos in the Demo User Learning Curve Section on the JCapper 101 Audio Video
page at JCapper.com:
1. Data Vendor Setting
2. Brisnet redid their
site after being acquired by CDI.
If you want to use
Brisnet Files you need to figure out manual download of .DRF or .MCP files from
the Brisnet site on your own.
3. Unzipping Files with
the File Unzipper (Brisnet Only. The File Unzipper does not apply to HDW
Files.)
4.
Persisting Data Folders (JCapper Platinum and Silver)
Learn how to:
1. Persist
the current active data folder in the DFM (Data Folder Manager) so that all of
the other JCapper modules recognize and point to that folder when you first
launch them.
2. Persist
inactive data folders in the DFM so that you can use the DFM to quickly toggle
back and forth between your persisted folders.
Resources
– Help Docs
1. Watch the Videos at and Read the
DFM (Data Folder Manager) Help Doc (Doc #5) on the Help Docs page at JCapper.com.
2. Spend some time working hands on
using the DFM to navigate folders on your machine, persist one of them as the
current active data folder, persist others as inactive data folders, and
(quickly) toggle back and forth between them.
5.
Loading Past Performance Data Files into JCapper (JCapper Platinum and Silver)
Learn to:
1. Use
the DFM Card Loader in the DFM to clear previously loaded data files (and
scratches) from the program, find past performance data files for today’s
races, drag and drop today’s data files onto the interface for the 3 folders
persisted in the DFM, and load the data files displayed on the visual interface
(after you have finished dragging and dropping them to the folders where you
want them to be loaded) into JCapper.
2. The
sole reason for loading past performance data files into JCapper: So that you
can Run Calc Races Routines to generate Html Reports and view them in the Html
Report Viewer, a Web Browser, and the SQL UDM Plays Report. Also so that you
can view Past Performances in the Past Performance Generator.
Or put
another way: You load data files into JCapper so that you can generate reports
for today’s races.
3. Understand
that you do not (as in not ever) load past performance data files into JCapper
to run Build Database routines. Database build routines are handled separately
by the Database Builder and you do not (repeat not – as in not ever) load past
performance data files into JCapper for that purpose.
Resources
– Help Docs
1. Click the Help menu on the upper
left of the DFM Card Loader screen to see BASIC OPERATING INSTRUCTIONS for the
DFM Card Loader.
2. Watch the Videos in the DFM Card
Loader section of the DFM (Data Folder Manager) Help Doc (Doc #5) on the Help Docs page
at JCapper.com
3. Spend some time hands on using
the DFM Card Loader to clear previously loaded data files from the program, and
to find and load past performances data files for today’s races into the
program.
6.
Using The Manual Changes Module to persist Scratches and Changes.
Learn how to:
1. Bring up a Race for a Track on
the Current Active Data Folder (as well as the other Data Folders.)
2. Setup and Save Scratches for
individual horses.
3. Unscratch a mistakenly Scratched
horse (uncheck the box and hit Save.)
4. Setup and Save Changes to Track
Condition, Surface, and Distance
Learn when to use The Manual Changes
Module:
1. For Gate Scratches when time is
of the essence.
2. When the Equibase site is down
and/or the Equibase Scratches and Changes XML isn’t available.
Resources
– Help Docs and Videos
1. Watch the Manual Changes Module
Video at the JCapper Basic Videos
link.
2. Read the Manual Changes Module
Help Doc (Doc
#16) on the Help Docs page at JCapper.com
7.
Using Scratch BOT to parse Scratches and Changes from the Equibase Scratches
and Changes XML
Learn how to:
1. Setup an XML Archive Folder.
2. Parse the Scratches and Changes
XML for today’s races in BOT Mode.
3. Manually parse an archived
Scratches and Changes XML File for a prior race date.
4. Find a Track in the
Track_Abbreviations Table Interface, pull up that track and persist the correct
Track_Name to the Notes field of the table so that it matches the track_name in
the xml to re-enable Scratch BOT to parse that track from the XML. You need to
do this whenever a track directs Equibase to change the track_name in the xml.
(NRYA does this for marketing purposes.)
5. Enable parsing Rider Changes from
the XML using the Master ON switch in the Enhanced Settings Module. (The
JCapper.mdb file that ships with JCapper 2025 contains Jeff’s Enhanced Settings
so Rider Changes is enabled when you first download JCapper 2025. But should
know how to do this if you accidentally undo one of the settings in the
Enhanced Settings Module.)
Resources
– Help Docs and Videos
1. Watch the Videos in the Scratch
BOT Help Doc (Doc
#18) on the Help Docs page at JCapper.com
2. Read the Scratch BOT Help Doc (Doc #18)
on the Help Docs page at JCapper.com
8.
Generating JCapper Html Reports (Playlist File Mode and SQL Mode)
Learn how to:
1. Run a Calc Races on a single
Race.
2. Run a Calc Races on a single Race
Card.
3. Run a Calc Races on a single
DataFolder.
Resources
– Help Docs and Videos
1. Watch the Manual Changes Module
Video at the JCapper Basic Videos
link above. A Single Race Calc Races is shown just after the 4:40 mark, and
launching the Html Report Viewer and displaying the SQL Mode Html Report using
the HTML Two Button is shown just after the 5:30 mark.
2. Watch the Processing a Day of
.JCP Files from Start to Finish in JCapper 2025 Video at the JCapper Basic Videos link above. A Calc
Races on DataFolder1 is shown just after the 9:45 mark, and launching the Html
Report Viewer and displaying the SQL Mode Html Report using the HTML One Button
is shown just after the 12:18 mark.
9.
Reading the Playlist File Mode Html Report and Connecting Dots
Learn how to:
1. Read and Understand the Playlist
File Mode Html Report.
2. Start Connecting Dots.
Resources
– Help Docs and Videos
1. Watch the Reading the Playlist File Mode Html Report and Connecting Dots Video at
the JCapper Basic Videos link above.
2. Read the Glossary of Supported Factors Page at JCapper.com
·
Link here: http://www.JCapper.com/FactorsGlossary.ASP
3. Read the Reading the Reports Help
Doc (DOC
#21) on the Help Docs Page at JCapper.com
10.
Generating JCapper Past Performances
Learn how to:
2. Customize the
appearance of JCapper Past Performances using the Enhanced Settings Module.
Resources
– Help Docs
1. Watch the PPs Generator Video at the JCapper
Basic Videos link above. Then read the PPs Generator Help Doc (displayed
inside the Past Performance Generator itself when you first launch it) or click
on the link to the PPs Generator Help Doc on the Help Docs page at JCapper.com.
2. Spend some time hands on
generating JCapper Past Performances using the Past Performance Generator. It’s
easy: Select a track code from the drop down and then select a race number.
3. Read the Enhanced Settings Module
Help Doc on the Help Docs page at JCapper.com.
4. Spend some time hands on with the
Enhanced Settings Module. Change a single setting for customizing the
appearance of JCapper Past Performances and then re-generate PPs for a race or
two. Then put the setting back to its default and regenerate a PPs for the same
race. Work with the following settings: STAT Roi Display Type, Time Zone Hrs
from GMT, Post Time Display, CXN Stats for Trainers and Jockeys, Company Line
Display, and PaceLine Display. The purpose of this exercise is to demonstrate
that JCapper Past Performances can be customized.
11.
Building JCapper Databases (JCapper Silver and JCapper Platinum)
This is what you need to know:
1. Requirements that need to be met
before you can build a database: Unzipped data and results files that match up
by track and date sitting on a target folder.
2. Set the Current Active DataFolder
in the DFM first. When you launch the DBBuilder it will default to the Current
Active DataFolder in the DFM.
3. Understand the 5 Build Modes and
when to use each of them. Click the Help button on the DBBuilder for a quick
primer.
·
Mode 1 – Use this Mode for the very
first DBBuild on a new Folder in Playlist File Mode.
·
Mode 2 - Use this Mode for
subsequent DBBuilds on that Folder in Playlist File Mode.
·
Mode 3 – Use this Mode for the very
first DBBuild on the very first Folder in SQL Mode.
·
Mode 4 – Use this Mode for the very
first DBBuild on subsequent Folders in SQL Mode.
·
Mode 5 – Use this Mode for
subsequent DBBuilds on the current Folder in SQL Mode after adding new race
cards.
4. Run a Recovery Setup Routine
prior to running a DBBuild to create a Recovery Point.
5. Double Check the DBBuilder
Interface (File Type, Build Mode, and Target Folder) prior to clicking the
Build Database Button to run a DBBuild.
6. Access .mdb files have a
Microsoft imposed file size limit of 2.0 Gigabytes (or 2,000 mb) As your
c:\JCapper\Exe\JCapper2.mdb file approaches 1.5 Gigabytes (1,500 mb) in size
it’s time to consider archiving it by renaming it to get it out of the way –
and replacing it with a copy of the fresh blank current version JCapper2.mdb
file that was written to your C:\JCapperBuild Folder during your most recent
JCapper Install.
Resources
– Videos and Help Docs
1. Watch the Building Databases in JCapper 2025 Videos (Part 1, Part 2,
Part 3, and Part 4) at
the JCapper Basic Videos link.
2. Read the Building JCapper
Databases Help Doc (DOC #28) on the Help Docs page at
JCapper.com.
3. Work “hands on” with the Program.
Try it on your own a few times until you get the hang of it. Don’t be afraid to
break a few eggs. You can always Clear a JCapper Database by running a DBBuild
in Mode 1 in Playlist File Mode or by running a DBBuild in Mode 3 in SQL Mode.
4. Read the “JCapper2.mdb file – what you need to know” thread in the JCapper
101 forum on the JCapper Message Board.
-- Update as of
09-26-2025 12:45 Pacific Time US:
I have been working
over the past several days to cut new Videos for JCapper 2025 and get them
embedded into the JCapper Help Docs, the JCapper BASIC Video Index at the
JCapper 101 link above, and get the JCapper 101 Class Outline updated for
JCapper 2025.
I still have
significant work to do.
Everything above the
Dotted Line below represents new work.
-jp
.
Everything below the
Dotted Line above has yet to be updated.
-jp
.
9. Data Window Queries (Playlist
File Mode and SQL Mode)
Learn:
1. How to run basic Data Window
queries in PlayList file mode.
2. How to run UDMs through the Data
Window in PlayList file mode.
3. How to run basic Data Window
queries in SQL mode.
4. How to run UDMs through the Data
Window in SQL mode.
Resources – Videos and Help Docs
1.
Watch the Data Window I and Data Window II videos in the Getting at Your Data
Section on the JCapper 101 Audio Video page at JCapper.com.
2.
Read the Understanding the Data Window Help Doc at the Help Docs page at
JCapper.com.
3.
Watch the Data Window III video in either the Getting at Your Data or Operating
JCapper in SQL Mode Sections on the JCapper 101 Audio Video page at JCapper.com
4.
Spend some time hands on working with the Data Window. Your goal should be to
come away with a basic understanding of how to use the Data Window to query a
database – both in PlayList file mode and in SQL mode.
10. Data Window Exports (JCapper
Silver and JCapper Platinum)
Learn
how to run the following Data Window Exports with the Data Window in PlayList
file mode:
1. CXN Data Window Export so that you
can generate reports for Riders, Trainers, and Owners.
2. Track Profile Data Window Export so that you can
generate track profile reports for your favorite racing venues.
Resources – Videos and Help Docs
1.
Read the Data Window Exports Help Doc.
2.
Watch the Data Window Exports and Reports for Trainers, Riders, and Owners
Video in the Getting at Your Data Section on the JCapper 101 Audio Video page
at JCapper.com.
3.
Work with the Program “hands on.” Run a
Jeff’s Track Profile Data Window Export using your Database as the source.
4.
Generate a handful of Jeff’s Track Profile Reports for your favorite racing
venues. Start discovering “The Demands of the Track.”
11. UDMs (JCapper Silver and JCapper
Platinum)
1.
Learn how to use the UDM Wizard to create UDMs: - Watch the A Simple Trainer
UDM Video.
2.
Listen to the Simple Basic UDMs Podcast.
3.
Listen to the other Podcasts devoted to creating UDMs.
4.
Work with the Program “hands on.” Pick
any one idea you might have (a handicapping premise) and use the UDM Wizard to
create a UDM based on that premise. Keep it simple. It’s all about learning to
use the tools… for the time being.
5.
Pick a second handicapping premise. Use the UDM Wizard to create a UDM based on
it. Again, keep things simple… for now.
Running UDMs through the Data Window
1.
Work with the Program “hands on.” Run
your UDMs against your database with the Data Window’s UDM button.
2.
Run your UDMs through the Data Window broken out by many different factors. See
for yourself where your own UDMs are strong and where they are weak.
3.
Work hands on with the program with the Data Window and UDM Wizard open at the
same time. Run a UDM through the Data Window broken out by a single factor.
Pick a cutoff for that factor based on results you see in the Data Window. Pull
up the UDM in the UDM Wizard and set that factor cutoff and save it. Then run
your UDM back through the Data Window and notice the improvement in
performance. Repeat… repeat… repeat. This is called tuning your UDMs.
12. Daily Reports (JCapper Silver
and JCapper Platinum)
Learn
How To:
1.
Learn how to use the JCapper Past Performance Generator to find and open data
files, and generate past performance data reports for the races in each file –
Read the JCapper Past Performance Generator Help Doc.
2.
Learn how to load JCapper.dat files into the program using the Card Loader: -
Watch the Loading race card Files into JCapper with the Card Loader Video.
3.
Learn how to Calculate Races and View Reports: - Watch the Calculating Races
and Viewing Reports Video.
4.
Work with the Program “hands on.” Use the Card Loader (or Screen Two of the
File Downloader) to load a JCapper.dat file into the Program. Then run a
Calculate Races and View Reports.
5.
Scroll through the Supported Factors Page at JCapper.com. Get a basic
understanding of the factors in the Program.
6.
Learn how to read the Reports and what to look for. Read the
Summary
Follow
the Class Outline. Learn the material in the exact order in which it is
presented. Doing that shortens the learning curve. Skipping steps will only get
you in trouble.
-
End JCapper 101 Class Outline –
Operating the Basic Program
Below is a Daily Quick Start guide to using JCapper each day to Unzip
Files, Load Race Cards, Process Scratches, Calculate Races, and View Reports.
The Daily Quick Start Guide presented here is intended as an overview of the
steps a JCapper user goes through each day in using JCapper to arrive at
potential UDM plays. Keep in mind as you
read this quick start guide that as a Demo user the only thing you can’t do is
generate same day race reports. That privilege is reserved for Registered
Program Owners only. The Demo Version ships with sample reports so that you can
follow along with the info presented in the Help Docs. If you want the ability
to run same day race reports you have to buy the program. That’s just the way
it is.
Here is an outline of what a new user does on a daily basis to operate
the basic program to run and view daily reports.
Outline of New
User Program Operation for Daily Reports
1. Learn
how to use the JCapper Past Performance Generator to find and open data files,
and generate past performance data reports for the races in each file – Read
the JCapper Past Performance Generator Help Doc.
2. Learn to use Screen One of the File Downloader to download and
automatically unzip files onto your Default Data Folder.
3. Learn to use the File Unzipper to find and unzip
files at will.
4. Learn to use the Card Loader (the one inside of
the DFM is the most current) to clear prior day scratches and load today’s race
card files into the program.
5. Learn to use the Manual Changes Module to process
scratches and surface/distance changes.
6. Learn to use the Main Module to run a Calc Races
routine. Demo Users are restricted to
running Calc Races on loaded JCapper.DAT files only.
7. Learn to use the Main Module to launch the Report
Viewer. Get a very clear understanding of exactly what you are looking at.
Learn exactly what to look for. Read the
File
Downloader
The File Downloader (added Jan, 2005) can be used to
download past performance and results files directly from the Bris and TSN
websites. The File Downloader has a second (hidden) screen, available via the
Folder Icon. This second screen provides advanced functionality for both
unzipping and loading past performance data files.
The File Downloader can be reached in the following
manner:
1. From the Main Module, click FILE DOWNLOADER – or -
2. From the Card Loader, click FILE DOWNLOADER
Screen One
Screen One of the File Downloader is a web browser
and is used to download files directly from Bris or TSN (be careful that you connect to the right page.) and save them to
your Default Data Folder. Remember, you have to unzip any files that your
download.
Screen Two
Screen two (it’s hidden at first) of the File
Downloader serves as both a File Unzipper and Card Loader. The interfaces of
both the File Unzipper and Card Loader are a little more user friendly than
screen two of the File Downloader. So I recommend you use those Modules for
unzipping and loading files. But know that you can use screen two of the File
Downloader to do both if you want to.
Resize Button
The File Downloader has the ability upon start up to
communicate with Windows and size itself according to the current screen
resolution. On some machines, most notably those with AMD K-6 chips instead of
Intel Pentium chips, Windows is unable to interface properly with the graphics
card and is therefore incapable of retrieving the correct screen resolution.
Clicking the Resize button will cause the File Downloader to size itself as if
it were running in an 800 x 600 screen resolution environment. If you are
unable to view the entire screen area of the File Downloader give the Resize
button a click.
Unzipping Data Files
The first question new users often ask is: Where do my data files go? When you first install JCapper your
Default Data Folder will be c:\2008. Until you go into System Settings and
change your Default Data Folder, this is where you should put your unzipped
downloaded data files.
JCapper has a pretty handy file unzip tool called the File Unzipper. There is a separate help
doc devoted entirely to using the File Unzipper for finding and unzipping files
at will. If you are a brand new JCapper user I recommend you open and read that
Help Doc once you are finished reading this Quick Start Guide. I also recommend
that you open the File Unzipper and refer to it as you follow along with the
text in the Help Doc.
JCapper also has the same complete unzip functionality on the second
(hidden) screen of the File Downloader.
But I recommend you wait a bit before moving on to screen two of the File
Downloader. Get yourself completely familiar with the File Unzipper first. Then
later, after you have become more familiar with JCapper, you can move on to
using Screen Two of the File Downloader to unzip files and Load Race Card
Files. By the way, File Downloader Screen Two is covered in detail in the
section of this Help Doc devoted to the File Downloader.
Of course you can also use third party unzip utilities such as WinZip
or the PkUnzip tool from BRIS to unzip your data files before you load them in
the Card Loader. If you do use a third party unzip tool, just be sure that you
extract your past performance data and results files onto your c:\2008 Default
Data Folder.
Past Performance Data Reports -
Learn
how to use the JCapper Past Performance Generator to find and open data files,
and generate past performance data reports for the races in each file – Read
the JCapper Past Performance Generator Help Doc.
For
the sake of convenience, the Overview section of that help doc is presented
here:
Overview - The JCapper Past Performance
Generator provides fast easy generation of past performance reports. Simply
point the module at a target folder, click File... click Open Data File, and
then use the dialog box to select the data file that you want. As soon as you
load a data file into the module, the Races Drop Down will auto populate with a
list of available races in the current data file. From there, select the race
that you want and the module will render a past performance report for that
race.
Fast, simple, and effective.
Load Race Cards
–
Click the Card Loader Button. You'll need to first copy
and unzip one or more Bris or TSN past performance data files (or JCapper.DAT
files) onto your Default Data Folder. When you first download the program your
Default Data Folder will be c:\2008. Then, just use the JCapper Card Loader to
load the desired file(s) into JCapper. This is an easy process. You can
navigate through your system's folder and file structure just like in Windows
Explorer. There's even a button that automatically searches, finds, and loads
all data files in your default folder for a given race date. You can also use
the File Downloader (added in Jan, 2005) to download and unzip past performance
and results files directly from the Bris and TSN websites. The File
Downloader's second screen, available via the Folder Icon, also provides
functionality for unzipping and loading past performance data files.
When you open the Card Loader and click on the Folder Nav Tool it will
display the contents of your Default Data Folder. Any unzipped data files with
an extension matching the file type currently selected in the File Type Drop
Down will be displayed in the window. The easiest way for new users to load a
data file is to simply double click each individual file. There is a separate
Help Doc which explains full functionality of the Card Loader in detail. If you
are a new JCapper user, I recommend you read the Card Loader Help Doc once you
have finished reading this Quick Start Guide.
Scratches and Changes –
Use Scratch Bot, Scratch Parser, or the Manual Changes Module to
quickly and easily process any scratches or changes. There are separate Help
Docs which explain all functionality of these three modules in detail. You’ll
be reading these shortly. Again, that’s outside the scope of this Quick Start
Guide.
Calc Races in the Demo Version –
The Demo Version does not allow Demo Users
to run Calc Races routines to generate same day race reports. That privilege is reserved
for Registered Program Owners only. I used to operate on the honor system and
offer people one free 30 day demo. Unfortunately a handful of people abused
this privilege and spoiled what was a very nice offer for everybody else. They
bombarded me with one free demo request after another and never paid for the
program. They used fake names and got free/anonymous email accounts from places
like Yahoo and Hotmail faster than I could track IP Addresses. So in the end,
even though I hated the idea, I adopted the current system. I hope you can
understand why.
Demo users do have the ability to run Calc
Races routines to generate previous day race reports. Doing this is really easy.
Just use the Card Loader to load JCapper.DAT files instead of Bris or TSN past
performance data files.
Q. What is a JCapper.DAT file?
A. JCapper.DAT files are created by the Database Builder during a Build
Database Routine. They include both past performance and results data.
Q. How do I get JCapper.DAT files?
A. Two ways:
1. Use the Database Builder to Build a Database. Refer to the Building JCapper Databases Help Doc for
coverage on this subject in complete detail.
2. Use the sample JCapper.DAT files included with the Install Package.
The install package includes three JCapper.DAT files. You can find these files
in your C:\JCapperBuild folder. All three files will have the .DAT file
extension. You can load them in the Card Loader by pointing the Card Loader at
your C:\JCapperBuild folder or manually copying the sample JCapper.DAT files to
your Default Data Folder.
Q. How do I use the Card Loader to load JCapper.DAT files?
A. Change the File Type Drop Down from the default .DRF file extension
to the .DAT file extension. All .DAT files in the pointed to folder will then
become visible in the Card Loader display. And of course to switch back to .DRF
files simply select .DRF from the file type drop down.
Q. How do I run a Calc Races routine to generate previous day race
reports?
A. After loading JCapper.DAT files in the Card Loader then click the
Calculate Races button. A Calc Races routine will run and you will be able to
view an HTML Report in the Report Viewer based on your loaded .DAT files.
Reports –
The Demo Version comes with sample Reports so that you can follow the
info presented in the Quick Start Guide and Help Docs. You’ll find them in your
c:\JCapperBuild folder. The filenames for the HTML Reports are: Report_1.html
and Report_2.html. The filenames for the Text Reports are: AtAPrice.txt and
AtAPrice2.txt. If you manually copy them to your Default Data Folder (c:\2008
until you go into System Definitions and change it) you will be able to view
both sets of reports in the Report Viewer.
Click the Report Viewer
button. The
JCapper Report Viewer lets the user toggle back and forth between the HTML
Report and the Text Report. The print button on the Report Viewer sends the
Text Report to a printer. The Print Button on the HTML Report itself sends the
HTML Report to a printer.
HTML Report One - (Filename: Report_1.html) The JCapper HTML Report shows the
significant factors with numbers and rankings for every horse in an easy to
follow format. All potential UDM plays are highlighted for easy identification.
There are hyperlinks so that the user can freely navigate from track to track
and race to race. HTML Report One contains information for every race found in
all loaded race card files and is created whenever a standard Calc Races
routine is run using the Calculate Races button.
HTML Report Two - (Filename: Report_2.html) This JCapper HTML Report is exactly
the same as HTML Report One except that it contains information for a single
track only and is created whenever a Calc Races is run for a selected single
track only.
Text Report One - (Filename: AtAPrice.txt) The JCapper Text Report shows all UDM Plays
for the day neatly organized in one place. Here you'll find a header for each
race that contains the Track, Race Number, Surface and Distance, and the class
descriptor and RaceVolatility for the
race. All potential positive expectation UDM plays in each race are laid out
for you. Here you'll find post position, name of horse, name of rider, name of
trainer, the name of the UDM that the horse qualifies for, morning line odds,
and finally, the BettingInstructions
from the UDM definition are shown in brackets. Seeing this report leaves very
little doubt as to what horse(s) should be played or at what odds. It's right there in a very easy to follow
format. Text Report One contains information for all horses that qualify as
potential UDM plays in every race found in all loaded race card files and is
created whenever a standard Calc Races routine is run using the Calculate Races
button.
Text Report Two - (Filename: AtAPrice2.txt) This JCapper Text Report is exactly
the same as Text Report One except that it contains information for a single
track only and is created whenever a Calc Races is run for a selected single
track only.
CSV File One – The JCapper Calc Races
routine also creates a comma delimited CSV file designed for use in third party
spreadsheet products such as Microsoft Excel. The filename is Plays.CSV and can
be found on the Default Data Folder. The information found in this file is
similar to that found in the Text Report file. The major advantage of using the
CSV Report file over a Text Report is that races can be sorted in post time
order. The user also has the ability to rename the file and permanently save
it. Advanced users have used this file as a starting point and have added
custom fields to their own XLS for the specific purpose of tracking betting
results from live play.
CSV File Two – This CSV file is exactly
the same as CSV File One except that it contains information for a single track
only and is created whenever a Calc Races is run for a selected single track
only.
Daily Export Files – The JCapper Calc Races
routine also creates the following comma delimited text files:
1. ForBill.TXT- This file contains information about each horse and includes
rankings, numeric values, and gaps for hundreds of JCapper factors. Some
advanced users use this file as a data source for their own custom handicapping
programs.
2. ForBill2.TXT – This file is exactly the same as ForBill.TXT except that it contains
information for a single track only and is created when a Calc Races routine is
run for a single track only.
3. ForJeff.TXT – This file contains all the information found in the ForBill.TXT
file. In addition, those horses that are found by the Profile Marker to fit
active UDM Definitions are “marked” with mark
characters. Again, some advanced users use this file as a data source for
their own custom handicapping programs.
4. ForJeff2.TXT - This file is exactly the same as ForJeff.TXT except that it contains
information for a single track only and is created when a Calc Races routine is
run for a single track only.
Data Window Exports (and Reports)
Jeff’s Track Profile Export
and Report Generator – After building a database, use the Data Window to run a Jeff’s Track
Profile Export. This will enable you to generate Track Profile Reports. These
reports are essential for understanding the demands of the track. The
information and format found on the Jeff’s Track Profile Report is what I used
to meticulously maintain (using a spreadsheet) until I grew tired of doing it
by hand and decided to make it part of JCapper. Data Window Exports are covered
in detail in the Data Window Exports Help Doc.
CXN Exports and Reports - After building a database, use the Data Window to run CXN Exports. This
will enable you to generate comprehensive CXN Reports for Trainers, Riders, and
Owners. These reports can be essential for getting an understanding of this
game along with who is good (and bad) at what. Want some inspiration (and solid
starting points) for trainer UDMs? The Overlooked Trainers Report is a great
place to start. Data Window Exports are covered in detail in the Data Window
Exports Help Doc.
Note about Artificial Surfaces in JCapper -
In JCapper I have decided for
the time being not to use a separate surface to describe PolyTrack. Users have
the ability to write UDMs and make ImpactValue table entries to require and
avoid specific tracks. At the time of this writing the following tracks are
running races on artificial surfaces: APX-DMR-GGX-HOL-KEE-PID-SAX-OSA-TPX-WOX.
Users wanting to enforce decisions to either require or avoid artificial
surfaces can do so by using these (and future) track codes in combination with
a surface designation of D* or D.
The Live Play Module in the Demo Version –
The Live Play Module is disabled in the Demo Version. It is disabled
for the same reason same day race reports are disabled. You have to buy the
program to use it. That doesn’t mean that you should ignore the Live Play
Module. Read the Live Play Module Help Doc. Get a basic understanding of the numbers
presented (it’s all about value) in the Module and what they mean. Run your own
UDMs through the Data Window broken out by some of the numbers on the Live Play
Module. If you take the time to create viable UDMs, and are interested in
carrying an edge into the long run, you will undoubtedly want to take the time
to see your own UDM cutoffs for factors such as Expected Value BettorsToteProb,
Expected Value UPRZScoreProb, OR3, and MLOR3.
You’ve come to the end of
the Demo User Quick Start Guide.
At this point, after working with the program hands on, you should be
getting a feel for whether or not JCapper might be right for you. If you want
to continue I recommend working with the program hands on in the following
manner:
–
END DEMO USER QUICK START GUIDE for Demo
Users –
Quick Start Guide for
Registered Program Owners
Below is a Daily Quick Start guide to using JCapper each day to Unzip Files,
Load Race Cards, Process Scratches, Calculate Races, and View Reports. The
Daily Quick Start Guide presented here is intended as an overview of the steps
a JCapper user goes through each day in using JCapper to arrive at potential
UDM plays. Here is an outline of what a new user does on a daily basis to
operate the basic program to run and view daily reports.
Outline of New
User Program Operation for Daily Reports
1. Learn to use Screen One of the File Downloader to
download and automatically unzip files onto your Default Data Folder.
2. Learn to use the File Unzipper to find and unzip
files at will.
3. Learn to use the Card Loader to clear prior day
scratches and load today’s race card files into the program.
4. Learn to use the Manual Changes Module to process
scratches and surface/distance changes.
5. Learn to use the Main Module to run a Calc Races
routine.
6. Learn to use the Main Module to launch the Report
Viewer. Get a very clear understanding of exactly what you are looking at.
Learn exactly what to look for. Read the
File
Downloader
The File Downloader (added Jan, 2005) can be used to
download past performance and results files directly from the Bris and TSN
websites. The File Downloader has a second (hidden) screen, available via the
Folder Icon. This second screen provides advanced functionality for both
unzipping and loading past performance data files.
The File Downloader can be reached in the following
manner:
1. From the Main Module, click FILE DOWNLOADER – or -
2. From the Card Loader, click FILE DOWNLOADER
Screen One
Screen One of the File Downloader is a web browser
and is used to download files directly from Bris or TSN (be careful that you connect to the right page.) There is a
checkbox labeled Automatically Unzip
Downloaded Files. The default setting when you open the File Downloader is
that this box is checked. As you download files and if you save them to your
Default Data Folder, the File Downloader keeps each file name in memory. When
you exit the File Downloader, each file
downloaded during the current session is sent to the bulk unzipper.
Resize Button
The File Downloader has the ability upon start up to
communicate with Windows and size itself according to the current screen
resolution. On some machines, most notably those with AMD K-6 chips instead of
Intel Pentium chips, Windows is unable to interface properly with the graphics
card and is therefore incapable of retrieving the correct screen resolution.
Clicking the Resize button will cause the File Downloader to size itself as if
it were running in an 800 x 600 screen resolution environment. If you are
unable to view the entire screen area of the File Downloader give the Resize
button a click.
Unzipping Data Files
The first question new users often ask is: Where do my data files go? When you first install JCapper your
Default Data Folder will be c:\2008. Until you go into System Settings and
change your Default Data Folder, this is where you should put your unzipped
downloaded data files.
JCapper has a pretty handy file unzip tool called the File Unzipper. There is a separate help
doc devoted entirely to using the File Unzipper for finding and unzipping files
at will. If you are a brand new JCapper user I recommend you open and read that
Help Doc once you are finished reading this Quick Start Guide. I also recommend
that you open the File Unzipper and refer to it as you follow along with the
text in the Help Doc.
JCapper also has the same complete unzip functionality on the second
(hidden) screen of the File Downloader.
But I recommend you wait a bit before moving on to screen two of the File
Downloader. Get yourself completely familiar with the File Unzipper first. Then
later, after you have become more familiar with JCapper, you can move on to
using Screen Two of the File Downloader to unzip files and Load Race Card
Files. By the way, File Downloader Screen Two is covered in detail in the
section of this Help Doc devoted to the File Downloader.
Of course you can also use third party unzip utilities such as WinZip
or the PkUnzip tool from BRIS to unzip your data files before you load them in
the Card Loader. If you do use a third party unzip tool, just be sure that you
extract your past performance data and results files onto your c:\2008 Default
Data Folder.
Load Race Cards
–
Click the Card Loader Button. You'll need to first copy
and unzip one or more DRF Single Format Data files onto your Default Data
Folder. When you first download the program your Default Data Folder will be
c:\2008. Then, just use the JCapper Card Loader to load the desired file(s)
into JCapper. This is an easy process. You can navigate through your system's
folder and file structure just like in Windows Explorer. There's even a button
that automatically searches, finds, and loads all data files in your default
folder for a given race date. You can also use the File Downloader (added in
Jan, 2005) to download and unzip past performance and results files directly
from the Bris and TSN websites. The File Downloader's second screen, available
via the Folder Icon, provides functionality for unzipping and loading past
performance data files.
When you open the Card Loader and click on the Folder Nav Tool it will
display the contents of your Default Data Folder. Any unzipped data files with
an extension matching the file type currently selected in the File Type
Dropdown will be displayed in the window. The easiest way for new users to load
a data file is to simply double click each individual file. There is a separate
Help Doc which explains all functionality of the Card Loader in detail. If you
are a new JCapper user, I recommend you read the Card Loader Help Doc once you
have finished reading this Quick Start Guide.
Scratches and Changes –
Use Scratch Bot, Scratch Parser, or the Manual Changes Module to
quickly and easily process any scratches or changes. There are separate Help
Docs which explain all functionality of these three modules in detail. You’ll
be reading these shortly. Again, that’s outside the scope of this Quick Start
Guide.
Calculate Races –
Click the Calculate Races
button and
JCapper goes to work. The program performs basic number crunching, making
thousands of calculations, for every horse, in all loaded data files. A comma
delimited export file is prepared. Some of our users like to import this into a
spreadsheet like Excel for their own purposes. The Profile Marker is launched.
The past performance record of every horse in all loaded data files is compared
against active UDM definitions in the Profile Table. Horses that fit the
definitions for any active UDM become marked so that they appear highlighted on
all HTML Reports. Marked horses are also written to a separate text file that
can be viewed with the JCapper report viewer or opened in Notepad if you like.
The HTML Report Builder is launched. An HTML Report is prepared. This report
can be viewed using the JCapper Report Viewer or the user's browser of choice.
Numbers are formatted in an easy to follow format. All potential UDM plays are
marked for easy identification. All of this happens automatically and it also
happens fast. With seven or eight
loaded race cards and 25-40 active UDMs, the entire process from start to
finish takes no more than 3 minutes on most machines. At the end, the user
simply sees a message that says "Races Calculated."
Reports –
The download package for the Registered Version contains sample Reports
so that you can follow the info presented in the Quick Start Guide and Help
Docs. You’ll find them in your C:\JCapperBuild folder. The filenames for the
HTML Reports are: Report_1.html and Report_2.html. The filenames for the Text
Reports are: AtAPrice.txt and AtAPrice2.txt. If you manually copy them to your
Default Data Folder (c:\2008 until you go into System Definitions and change
it) you will be able to view both sets of reports in the Report Viewer.
However, once you load race card files into the program and run a Calc Races
routine, the reports on your Default Data Folder will be replaced by the same
day race reports from your own loaded race card files.
Click the Report Viewer
button. The
JCapper Report Viewer lets the user toggle back and forth between the HTML
Report and the Text Report. The print button on the Report Viewer sends the
Text Report to a printer. The Print Button on the HTML Report itself sends the
HTML Report to a printer.
HTML Report One - (Filename: Report_1.html) The JCapper HTML Report shows the significant
factors with numbers and rankings for every horse in an easy to follow format.
All potential UDM plays are highlighted for easy identification. There are
hyperlinks so that the user can freely navigate from track to track and race to
race. HTML Report One contains information for every race found in all loaded
race card files and is created whenever a standard Calc Races routine is run
using the Calculate Races button.
HTML Report Two - (Filename: Report_2.html) This JCapper HTML Report is exactly
the same as HTML Report One except that it contains information for a single
track only and is created whenever a Calc Races is run for a selected single
track only.
Text Report One - (Filename: AtAPrice.txt) The JCapper Text Report shows all UDM Plays
for the day neatly organized in one place. Here you'll find a header for each
race that contains the Track, Race Number, Surface and Distance, and the class
descriptor and RaceVolatility for the
race. All potential positive expectation UDM plays in each race are laid out
for you. Here you'll find post position, name of horse, name of rider, name of
trainer, the name of the UDM that the horse qualifies for, morning line odds,
and finally, the BettingInstructions
from the UDM definition are shown in brackets. Seeing this report leaves very
little doubt as to what horse(s) should be played or at what odds. It's right there in a very easy to follow
format. Text Report One contains information for all horses that qualify as
potential UDM plays in every race found in all loaded race card files and is
created whenever a standard Calc Races routine is run using the Calculate Races
button.
Text Report Two - (Filename: AtAPrice2.txt) This JCapper Text Report is exactly
the same as Text Report One except that it contains information for a single
track only and is created whenever a Calc Races is run for a selected single
track only.
CSV File One – The JCapper Calc Races
routine also creates a comma delimited CSV file designed for use in third party
spreadsheet products such as Microsoft Excel. The filename is Plays.CSV and can
be found on the Default Data Folder. The information found in this file is
similar to that found in the Text Report file. The major advantage of using the
CSV Report file over a Text Report is that races can be sorted in post time
order. The user also has the ability to rename the file and permanently save
it. Advanced users have used this file as a starting point and have added
custom fields to their own XLS for the specific purpose of tracking betting
results from live play.
CSV File Two – This CSV file is exactly
the same as CSV File One except that it contains information for a single track
only and is created whenever a Calc Races is run for a selected single track
only.
Daily Export Files – The JCapper Calc Races
routine also creates the following comma delimited text files:
–
ForBill.TXT- This file contains
information about each horse and includes rankings, numeric values, and gaps
for hundreds of JCapper factors. Some advanced users use this file as a data
source for their own custom handicapping programs.
–
ForBill2.TXT – This file is exactly the
same as ForBill.TXT except that it contains information for a single track only
and is created when a Calc Races routine is run for a single track only.
–
ForJeff.TXT – This file contains all
the information found in the ForBill.TXT file. In addition, those horses that
are found by the Profile Marker to fit active UDM Definitions are “marked” with
mark characters. Again, some advanced
users use this file as a data source for their own custom handicapping
programs.
–
ForJeff2.TXT - This file is exactly the
same as ForJeff.TXT except that it contains information for a single track only
and is created when a Calc Races routine is run for a single track only.
Data Window Exports (and Reports)
Jeff’s Track Profile Export
and Report Generator – After building a database, use the Data Window to run a Jeff’s Track
Profile Export. This will enable you to generate Track Profile Reports. These
reports are essential for understanding the demands of the track. The
information and format found on the Jeff’s Track Profile Report is what I used
to meticulously maintain (using a spreadsheet) until I grew tired of doing it
by hand and decided to make it part of JCapper. Data Window Exports are covered
in detail in the Data Window Exports Help Doc.
CXN Exports and Reports - After building a database, use the Data Window to run CXN Exports. This
will enable you to generate comprehensive CXN Reports for Trainers, Riders, and
Owners. These reports can be essential for getting an understanding of this
game along with who is good (and bad) at what. Want some inspiration (and solid
starting points) for trainer UDMs? The Overlooked Trainers Report is a great
place to start. Data Window Exports are covered in detail in the Data Window
Exports Help Doc.
Note about Artificial Surfaces in JCapper -
In JCapper I have decided for
the time being not to use a separate surface to describe PolyTrack. Users have
the ability to write UDMs and make ImpactValue table entries to require and
avoid specific tracks. At the time of this writing the following tracks are
running races on artificial surfaces: APX-DMR-GGX-HOL-KEE-PID-SAX-OSA-TPX-WOX.
Users wanting to enforce decisions to either require or avoid artificial
surfaces can do so by using these (and future) track codes in combination with
a surface designation of D* or D.
Note about PolyTrack: In JCapper I have decided for the time being not to
use a separate surface to describe PolyTrack. Users have the ability to write
UDMs and make ImpactValue table entries to require and avoid specific tracks.
At the time of this writing the following tracks are running races on
artificial surfaces: APX-DMR-HOL-KEE-PID-TPX-WOX. Users wanting to enforce decisions
to either require or avoid artificial surfaces can do so by using these (and
future) track codes in combination with a surface designation of D*.
Now that you’ve finished
reading Quick Start Guide it’s time to work with JCapper “hands on:”
At this point, after working with the program hands on, you should
start to get a feel as to whether or not JCapper might be right for you. If you
want to continue I recommend you work with the program hands on in the
following areas:
–
END QUICK START GUIDE for Registered Program
Owners –
Modules
JCapper is broken up into modules. Each module is
designed to help you perform specific tasks related to your daily workload as a
horseplayer. Here are the current JCapper Modules as of this writing:
The Complete Program and its
Modules
·
Help Doc Viewer
·
File Downloader
·
File Unzipper
·
Card Loader
·
Scratch Bot
·
Scratches Parser
·
Manual Changes Module
·
Profile Marker
·
HTML Report Generator
·
Report Viewer
·
Dutching Tool
·
Live Play Module
·
Database Builder
·
Quick Index File Extract Tool
·
Data Window
·
Bankroll Simulation Module
·
UDM Wizard
·
Profile Table Interface
·
System Settings Interface
·
Impact Value Tables Interface
Help Doc Viewer
The Help Doc Viewer serves two purposes. First, it
provides a user interface for performing and troubleshooting JCapper Installs.
Second, it provides a user interface for opening and viewing JCapper Help Docs.
Viewing Help
Docs
To access the Help Doc Viewer, click the Help Documents button on the JCapper
Main Module. This will open the Help Doc Viewer. To view an index of available
Help Documents, click the JCapper Help
Documents menu item located in the Help Doc
Viewer's left side menu pane. This will cause an
index of available Help Documents to appear in the center window. To enlarge
the center window, click the ">>" double arrow image located
near the upper right edge of the center window.. To return the center window to
its default size, click the ">>" double arrow image while the
center window is enlarged. To open and view an individual Help Doc, click the
Help Doc Title in the center window. To exit the Help Doc Viewer, click the Exit menu item located in the Help Doc
Viewer's left side menu pane.
Help Doc
Formats
Most of the Help Docs are in .doc file format and
are designed to be viewed in Microsoft Word or equivalent word processor. If
your system has a program like Word installed on it capable of rendering .doc
files, the Help Docs will automatically open in that program after the Help Doc
Title in the center window has been clicked. If your system lacks a word
processor capable of rendering .doc files, a word processor named Jarte is
available as a free download from the following URL:
http://www.jarte.com/download.html It's not as full featured as Microsoft Word,
but it will enable you to view and print the Help Docs. Some of the Help Docs
are in html format. These files will render in your web browser after the Help
Doc Title in the center window has been clicked.
-end section on
Help Doc Viewer
Card Loader
The JCapper Card Loader can be accessed by clicking
the Load Race Cards button on the
JCapper Main Module. A separate Help Doc, titled Loading Race Cards with the JCapper Card Loader, covers the operation
of the Card Loader in complete detail. The Card Loader provides a user
interface for loading past performance data files so that reports can be
generated for today's races. For the benefit of users brand new to JCapper, it
should be pointed out that using the Card Loader to load past performance data
files relates to viewing reports for a handful of race cards only (15-20 being
a practical maximum.) The user interested in creating a database and performing
research should look to the Database Builder and Data Window for those tasks.
Scratch Bot
Scratch Bot can be accessed by clicking the Scratch Bot button on the JCapper Main
Module. A separate Help Doc, titled Processing
Scratches with the New Scratch Bot, covers the operation of Scratch Bot in complete
detail. Scratch Bot was designed to give the user/player with direct internet
access the means of downloading and importing fresh scratches and changes as
they occur throughout the race day.
Scratches Parser
I am currently working on completion of a separate
Help Doc titled Processing Scratches with
the Scratches Parser. Once complete, this document will cover the operation
of the Scratches Parser in detail. Other JCapper related projects, such as
adding new features to the program and updating other Help Docs, have taken
precedence and rightly so. Until the time comes when I can complete a separate
doc on the Scratches Parser, the basic operating instructions for the Scratches
Parser presented below should suffice:
Accessing the
Scratches Parser
The Scratches Parser can be accessed by clicking the
button labeled Scratches Parser on
the JCapper Main Module. The Scratches Parser acts as a web browser. It
actually uses the Internet Explorer libraries on your system to navigate to and
render web pages. Upon startup, the Scratches Parser will load and render the
Bris Scratches Index page. This is a page on the Bris website where scratches
for all of today's race cards are made available. Users must have a Bris user
account in order to download scratches from this site. Bris currently offers
scratches from this site to their members at no charge.
Using the
Scratches Parser to Process Scratches
Here are the steps to follow for Processing
Scratches with the Scratches Parser:
1. Start the
Scratches Parser by clicking the button labeled Scratches
Parser on the JCapper Main Module.
2. Select a
Race Card
by clicking the date link for the track you want to get scratches for.
3. Enter your
Bris userid and password in the box and click OK. After authentication, the Bris web page
containing available scratches will appear.
4. Click the
Parse Scratches button. Scratches Parser will then parse the Bris web page listing the
scratches and import them into JCapper.
5. Click the
Home button
to return to the Bris Scratches Index Page and select other tracks as needed.
6. Close the
Scratches Parser by clicking the red X located in the upper right hand corner of the
screen.
Notes on
Scratches Parser
That's all there is to it. Well, almost. Here are a
couple of notes regarding proper operation of the Scratches Parser:
1. Clear Scratches button - Important
- JCapper stores its Scratches on the Default Data folder in a text file
named Scratches.txt. Clicking the Clear Scratches button will clear all
scratches by clearing this file. As a best practice it is recommended that you
click the Clear Scratches button at the start of each new race day before
obtaining new scratches for the day. This will prevent system slowdowns that
can result if the Scratches.txt file grows too large (several thousand
scratches entries.) This will also prevent the file from becoming corrupted.
The Clear Scratches buttons/functions present in the Scratches Parser, Manual
Changes Module, Scratch Bot, Card Loader, and File Downloader all perform the
same task. It does not matter which module is used to clear scratches just so
long as scratches are cleared once per race day preferably at the start of each
new race day.
2. Updating
Scratches during the Race Day
Bris generally makes scratches available starting at
about 30 minutes prior to post time for race one at each track. One drawback is
that Bris very seldom updates the web pages available from their Scratches
Index Page throughout the race day. For scratches updates throughout the race
day I recommend using Scratch Bot or the Manual Changes Module. The purpose of
the Scratches Parser is to give the player who takes his notebook computer or
JCapper printouts to the track or OTB a way to get scratches before leaving the
house.
3. Calculating
Races
Any time any JCapper module is used to import fresh
scratches, and this applies to Scratches Parser, Scratch Bot, and the Manual
Changes Module, you will need to re-calculate races by clicking the Calculate Races button on the Main
Module in order to see the effects of the new scratches and/or race changes.
-end section on
Scratches Parser
The Manual
Changes Module
The Manual Changes Module can be accessed by
clicking the Manual Changes button
found on the JCapper Main Module. A separate Help Doc, titled Processing Scratches with the Manual Changes
Module, covers the operation of the Manual Changes Module in complete
detail. The Manual Changes Module provides a user interface for manually
scratching horses and entering surface/distance changes. The Manual Changes
Module was designed to give the user/player without direct internet access a
means of manually keeping up with fresh scratches and surface/distance changes
throughout the race day.
-end section on
The Manual Changes Module
Using JCapper for Database Research and
Live Play
The next section of this Help Doc focuses on using
JCapper as a research tool and developing your own UDMs.
Outline of
Program Operation for Database Research and Live Play
1. Learn to download matched pairs of data &
results files onto target (Default Data) folder.
2. Learn to Unzip matched pairs of data &
results files on target (Default Data) folder.
3. Learn to point the Database Builder at target
(Default Data) folder and perform a Rebuild Database from Scratch.
4. Learn to use the Data Window to run simple
queries against the database with the ALL button.
5. Learn to use the UDM Wizard to create simple
UDMs.
6. Learn to use the Data Window to run UDMs against
the database with the UDM button.
7. Learn to use the Quick Index File Extract Tool to
create Quick Index Files.
8. Learn to use the UDM Wizard to create UDMs that
are gradually more and more complex as your knowledge of what you are doing
grows over time. Eventually you will find yourself creating Tight Model UDMs.
9. Learn to use your UDMs profitably during live
play.
10. Learn to maintain multiple databases and use
them as development and validation samples.
Database
Builder
The Database Builder can be accessed by clicking the
Build Database button found on the JCapper
Main Module. A separate Help Doc, titled Building
JCapper Databases, covers the operation of the Database Builder in complete
detail. The Database Builder provides a user interface for building a database
using your existing past performance data and results files. The Database
Builder was designed to create files in a format readable by the JCapper Data
Window and give the non-programming horseplayer the ability to perform his or
her own research by running queries against that database.
Quick Index
File Extract Tool
The Quick Index File Extract Tool can be accessed by
clicking the Quick Index File Extract
button found on the JCapper Main Module or the QX button found on the Data Window. You can use the Quick Index
File Extract tool to extract a Quick Index File from any of your PlayList
files. A Quick Index File is identical to a PlayList file, but contains only
those starters in it that match the parameters selected by the user at build
time. The Quick Index File Extract tool allows users to build Index Files by
various combinations of both factor and rank. Index Files can be built that
contain only the starters from an individual trainer, only those starters from
an individual track, and only those starters where rank equals a selected value
for a selected factor. An Index File created where JRating Rank = 1 will only
have those starters that are the top ranked JRating horse from each race. Given
that 8 horses is the average field size for all races, a Data Window query
using a Quick Index File will run approximately 8 times faster than the same
query run using the PlayList file from which the Quick Index File was
extracted.
To create a
Quick Index File, follow these steps:
1. Start the
Quick Index File Extract Tool by clicking the Quick
Index File Extract button found on the JCapper Main Module or the QX button found on the Data Window.
2. Select a
Factor/Extract Type from the Factors/Extract Type Drop Down.
3. Select Rank from the Rank Drop Down.
4. Click the
Folder Icon.
Use the Folder Nav Tool to browse folders on your system and navigate to the
folder where your source PlayList file is located
5. Click the
Build Index button. Select your source PlayList file and open it.
That's it. The Quick Index File
Extract Tool will create a Quick Index File containing only those starters
fitting the parameters for factor and/or rank that you selected.
Notes on the
Quick Index File Extract Tool
Folder Icon - The Folder Icon is used
throughout JCapper to allow directory or folder browsing. Clicking the Folder
Icon will open the Folder Nav Tool. Double Click an individual folder to select
it. Each time a new folder is selected, the folder name will appear on the
Build Index button and on the blue title bar at the top of the module's screen.
Close the Folder Nav Tool at any time by clicking the module screen outside of
the Folder Nav Tool's border.
+Create New
Index -
This is the default setting. When +Create
New Index is selected, the Quick Index File Extract Tool will create a new
quick index file, overwriting any existing quick index file in the same folder
having the same file name. File names are based on the factor selected from the
factors drop down.
-Add to
Existing Index
- When -Add to Existing Index is
selected, instead of creating a new quick index file, the Quick Index File
Extract Tool will append to any
existing quick index file in the pointed to folder. This makes it possible for
the user to create quick index files spanning databases located in multiple
folders.
Quick Index
Files Spanning Multiple Databases - It is possible for the user to create quick index
files spanning databases located in multiple folders. For example, users who
maintain one folder and database for each quarter during a calendar year might
find it desirable to create a single JRating quick index file containing
information extracted from all four databases. Data Window query speed on the
JRating quick index file will be markedly faster than query speed using
quarterly PlayList files.
To create quick index files spanning databases from multiple folders,
use the following strategy: First, point the Quick Index File Extract Tool to
Folder A and create a new Quick Index File in folder A. Then, copy your Quick
Index File from Folder A to Folder B. Then, point the Quick Index Extract Tool
to Folder B, and select - +Add to Existing Index and create the
same type of index for Folder B that you just copied from Folder A. Instead of
creating a new file, the Quick Index File Extract Tool will append Folder B's information to the
Quick Index File that you copied in from Folder A. The resulting Quick Index
File in Folder B now contains data from both Folder A and Folder B. You can now
copy Folder B's Quick Index File to Folder C and repeat the process as
needed...
A Down and Dirty Example –
Q. I have HOL on one large
database and OSA on another. What is the best way to combine them into one
database?
A. Here's how:
1. From inside the Quick Index File Extract Tool, run a #14 Track Index
extract for the first track - in this case HOL. Enter HOL as the track code.
Click the GO button and open the large PlayList file that contains the HOL
cards you want to extract. When the extract is complete you will have the
following file on your target folder and it will only contain data from races
run at HOL: pl_Track_HOL.txt
2. Do the same thing for your second (or third or 4th, etc track) - in
this case OSA. From inside the Quick Index File Extract Tool, run a #14 Track
Index extract for OSA. Click the GO button and open the smaller PlayList file
that contains the OSA cards you want to extract. It's ok if the second Playlist
file resides on a different folder. Just use the Folder Icon/Nav Tool or use
the Folder Navigation Interface within the Open a PlayList File Dialoag Box to
switch folders. When the extract is complete you will have the following file
on your target folder and it will only contain data from races run at OSA:
pl_Track_OSA.txt
Ok, that's how you get data extracted for individual tracks. Now, on to
the second part of your question: How do you combine them?
From inside the Quick Index File Extract Tool:
1. Open up the extract type drop down and scroll UP. Select 0 Complete
History. Then hit the Go button and open up the first track extract that you
ran: pl_Track_HOL.txt. The Quick Index File Extract Tool will create the
following file on your Default Data Folder: pl_Complete_history.txt. It will
contain all of the data that exists in the file that you opened - in this case
pl_Track_HOL.txt. The file named pl_Complete_history.txt created in this step
will actually be a replica of the file named pl_Track_HOL.txt.
2. Use the Quick Index File Extract Tool's Add to Existing Option. From
inside of the Quick Index File Extract Tool change the drop down labeled +
Create New Index to - Add to Existing Index. Then hit the Go button and open up
the second track extract that you ran: pl_Track_OSA.txt. The Quick Index File
Extract Tool will extract data from the file you just opened (pl_Track_OSA.txt)
and append it to the pl_Complete_history.txt file on your Default Data Folder
created in step 1 above.
At this point you have a
file named pl_Complete_history.txt that contains the data from both of your
single track extracts. To preserve that file and prevent it from being overwritten during any
future Quick Index File Extract Tool Complete History routines you might run -
simply rename it. Keep the first three characters "pl_" (without the
quote characters) and name it to something that makes sense to you. Something
like "pl_SOCAL_Poly.txt" (again without the quotes) would do the
trick here.
Once you've done a few of these and understand how the Quick Index File
Extract Tool works, running a Complete History operation is actually pretty
simple. In real life it probably takes longer to find (it's in a help doc
somewhere) and read the instructions than it does to perform the actual
operation.
Common Dialog Control - The Common Dialog Control
used throughout JCapper for selecting and opening files has some functionality
that goes beyond what you see at first glance. The Dialog Control also gives
you access to many of the same libraries available to Windows Explorer. Because
of this, when you open a Common Dialog Control and point to a folder, you can
also perform many of the same functions that you could if you were using
Windows Explorer to point to the same folder. You can right click on any file,
and copy the file to the ClipBoard by selecting copy. You can also delete any
file. You can right click in the white space between file names, allowing you
to perform any number of the same things available to you in Windows Explorer
such as creating/renaming folders and pasting files to the current folder. The
Common Dialog Control also provides built in navigation elements that allow you
to browse to other drives and folders.
-end section on Quick Index File Extract Tool -
The Data
Window
The JCapper Data Window provides a comprehensive
interface enabling the user to perform his or her own research, querying a
JCapper database to discover the performance of any single factor, or
combination of factors, supported by JCapper. The Data Window was designed so
that it can be used by those who have absolutely no knowledge of computer
programming. Individual factors may be included as part of a query simply by
selecting them from Drop Downs. Queries involving combinations of factors may
involve a learning curve, but rest assured, every possible combination of
supported factors found in a JCapper Database can be tested using the Data Window.
A separate Help Doc, titled Understanding the JCapper Data Window, covers operation of the Data
Window in complete detail.
-end section on the Data
Window -
Building UDMs
At some point, most players will want to create
their own User Defined Models or UDMs. A basic understanding of what a UDM
actually is might be helpful to the new user. A UDM is simply a definition of a
spot play stored in the Profile Table of the JCapper Database. A UDM Definition
can be as simple or as complex as the player desires. A UDM Definition consists
of settings for numeric value, rank, and gap for each of the factors being used
in the UDM itself. A very simple example of a UDM might be something like this:
Simple text description: A UDM named Cpace1 that
uses the top ranked CPace horse no matter what the surface or distance.
This UDM, in terms of the definitions of its
factors, can be expressed as follows:
UDM
Name: CPace1
Distance:
*ALL
Surface:
*ALL
Factor:
CPace
Min
Rank: 1
Max
Rank: 1
In this example and this is the case with all UDMs,
the value for each of the settings used is stored in a corresponding field in
the Profile Table for that setting. The actual values found in the Profile
Table for the above UDM are listed below:
Field Name Field Value
Profile CPace1
Active -1
SurfaceReq *
DistReq *
CPaceTest -1
CPaceMinVal
-999
CPaceeMaxVal 999
CPaceMinRank 1
CPaceMaxRank 1
CPaceMinDiff -999
CPaceMaxDiff
999
Both the Data Window and Profile Marker contain
logic having the ability to compare the rank, numeric value, and gap for any of
the supported factors in the program for any horse against the UDM Definition
stored in the Profile Table for every UDM and determine, True or False, whether
or not the horse being considered qualifies as a potential play according to
the UDM Definition of the current UDM. In the case of a Data Window query, the
qualifying horse is listed as a play in the results display while the non-qualifying
horse is simply ignored. In the case of the Profile Marker, the qualifying
horse is marked as a play on the reports and the non-qualifying horse is simply
ignored.
Obviously, the real power of UDMs comes into play
when the user/player performs his or her own Data Window research and then
creates UDMs to take advantage of discoveries made during that research. After
quite a bit of correspondence teaching new users how to set up UDMs, I have
come to the conclusion that there are really five basic types of UDMs. The
really sophisticated user may sometimes choose to blur the lines a little bit
by creating UDMs that use the basic concepts of more than one UDM type - but
for the most part -there are five basic UDM types that I have seen put into successful
play. They are listed below:
1.
Speed and Pace
2.
Track Specific
3.
Trainer Specific
4.
Sire Specific
5.
Negative Expectation
Speed and Pace
UDMs
Speed and Pace UDMs are probably the most common
types of UDMs. Here the user/player attempts to create models that take
advantage of the unique numbers found in JCapper. I tend to think of JCapper's
premier ratings (in no particular order of effectiveness) as: JRating, CPace,
Weighted Figure, Form Rating, Pace Model Index, Optimization Points, Race
Strength, and Race Volatility. It is not very hard at all for the new user to
create break even UDMs (from a flat $2.00 win bet perspective) just by doing a
little Data Window Research and using combinations of these factors as part of
the UDM Definition.
Track Specific
UDMs
Track Specific UDMs are another common type of UDM.
Here, the user/player makes the three character Track Code, Surface, and
Distance part of the UDM Definition and creates models that attempt to take
advantage of the way an individual racing surface might be playing. Some racing
surfaces are deep and tiring. Others are consistently more tightly packed and
less tiring. I like to use the analogy of sand at the beach. I am a runner. One
of my favorite places to run is at the beach. The sand right along the water's
edge, because of the moisture content, is very easy to run on. It has very
little give to it and just the right amount of spring. Because of this, I can
run all day on it. If I change my path and run on the dry sand 50 or 60 feet
from the water's edge, the first thing I notice is that the sand is much
deeper. Each step I take finds my foot sinking well into it. As a result, if I
choose to run there, I'll get tired very quickly. Horses running on the track
are no different. Horses running on or near the lead on a deep and tiring
surface will fade in the stretch. Races on deep and tiring surfaces are most
likely to be won by horses that are not asked to run until the final third of
the race. On the other hand, horses running on or near the lead on a firmly
packed non-tiring surface will continue to run in the stretch. As a result, it
is more difficult for closing horses to get past them.
There are several factors in JCapper that can be
used to measure the tendencies of specific racing surfaces. In no particular
order, they are: CPace, AVGE1, PctE, Closing Ratio, Q Speed Points, PAL, L3,
Rail Position and Pace Index. My two personal favorites are PctE rank and CPace
rank. I like to run an entire race meet through the Data Window broken out by
these two factors to get a general idea - a benchmark - as to how a given
racing surface is playing. Then I run a data summary for the most recent three
days and note any differences. If more winners than expected are coming from
the top ranked positions for PctE and CPace then I know the racing surface is
not deep and tiring and will most likely favor early speed.
The player who pays attention to and studies such
things can gain an edge over the crowd on the individual racing surface(s) he
or she follows. He or she can create UDMs to take advantage of racing surfaces
that are either deep and tiring, hard packed and non-tiring, or that have
either inside or outside path biases. The player who does this can activate or
deactivate UDMs at will with a simple mouse click as the circumstances at the
racing surface being followed dictates.
Trainer
Specific UDMs
Trainer Specific UDMs are another common type of
UDM. Here, the user makes the trainer name part of the UDM Definition and
creates models that attempt to take advantage of the way the individual trainer
preps his or her starters to win races. Some trainers excel under certain
circumstances and have dismal records under other circumstances. With trainer
specific UDMs, the user might want to think
like a trainer. A good strategy for the new user would be to use the Quick
Index File Extract Tool to create an index file containing the starters of a
single trainer only. Then look at that trainer's starters in terms of factors
that trainers might think about when prepping their starters. The following
list of factors can be very useful for creating trainer specific UDMs and
should more than get you started: XthStartAfterLayoff, XthStartAtTheMeet,
XthStartAfterLasix, Claim Starts, Claim Days, Distance Shift, Class Shift,
Surface Shift, Recent Activity Days Last Start, Recent Activity Days Last Work,
Age of Horse in Years, Track Name, and Class Descriptor. Generally, the user
will find fewer plays with trainer specific UDMs than with Speed and Pace UDMs.
But, if the user has been able to measured trainer
intent with any accuracy, the plays found with trainer specific UDMs can be
of a higher quality than those normally found with other types of UDMs.
Trainer Name Matching
One
important note: in order to make Trainer Specific UDMs work it is imperative
that the user get a name match between the trainer name used in the UDM
Definition and the trainer name listed in the past performance data file. A
trainer name listed in a Bris data file will often be different than the
trainer name for the same trainer listed in a TSN data file. It is therefore
important to know how your data provider lists the trainer name in your data
files. You must get a match between the trainer name in your UDM Definition and
the trainer name in the data file. My recommendation along these lines is very
simple. As a best practice, in your UDM Definition, simply use the trainer's
last name followed by a space followed by the first letter of the trainer's first
name. This should provide a proper name match in almost all cases.
Sire Specific
UDMs
Sire Specific UDMs are another type of UDM. Here,
the user makes the sire name part of the UDM Definition and creates models that
attempt to take advantage of tendencies shown by the progeny of specific sires.
The offspring of some sires have historically performed very well under
specific circumstances. Factors that can be of help to the user when creating
sire specific UDMs, in no particular order, are: Age of Horse in Years, Starts
Lifetime, Track Name, Distance, Surface, Track Condition, Recent Activity Days
Last Start, and possibly Recent Activity Days Last Work. Generally, Sire
Specific UDMs yield the fewest number of plays of any UDM type. But in cases
where the user is able to perform research and discover the tendencies of the
offspring of specific sires, it is possible to create UDMs yielding plays with
a very high quality.
To
invoke a SIRE conditional in a UDM Definition, key the characters SIRE into the
Special Filters field of the Profile table and key the Sire Name into the Notes
field of the Profile Table.
Sire Name Matching
One
important note: in order to make Sire Specific UDMs work it is imperative that
the user get a name match between the sire name used in the UDM Definition and
the sire name listed in the past performance data file. My recommendation along
these lines is very simple. As a best practice, in your UDM Definition, simply
use the sire name in its entirety.
Negative
Expectation UDMs
Another type of UDM is the Negative Expectation UDM.
Here, the sophisticated user attempts to create UDMs used to identify horses
with characteristics that research has shown to have dismal historical
performances. Here, any and all factors in the program might be fair game.
There are riders whose records in races run on turf or off tracks are simply
abysmal. There are trainers whose starters never seem to win when entered in
races of a given class descriptor - or never win when first off the claim - or
when stretching out, etc. Many users have reported good success in using both
Preset and Dynamic Filters in their Negative Expectation UDMs. The general idea
of a Negative Expectation UDM is a simple one: Perform Research with the Data
Window and discover combinations of factors that point to horses having very
little chance of running in the money. Then create UDMs to identify those
horses - and avoid them when playing.
Mark Characters
Mark
Characters refers to a two character code stored in the MarkChars field of the
Profile Table. Mark Characters are used by the Profile Marker and HTML Report
Builder as a means of distinguishing between positive expectation and negative
expectation UDMs. Valid Mark Characters for a positive expectation UDM are two forward slash characters: "//" Valid Mark Characters for a Negative
Expectation UDM are two hat characters: "^^"
Negative Expectation UDMs are displayed in gray font on the HTML Report and can
be created in the UDM Wizard by using "^^"
as the Mark Characters instead of "//".
General
Guidelines for UDM Construction
There is a learning curve involved when it comes to
creating UDMs. After teaching many users to create UDMs of their own I have
discovered that there are actually two phases to the learning curve.
Phase One
The first part of the learning curve for UDM
construction is all about learning how the software works, and how best to put
it to work in bringing your ideas for UDMs into reality. This is the easy part.
Experiment a little. Spend some "hands on" time with the software and
create a few UDMs of your own. Pick out a few of the factors and set some ranks
and gaps. Then run your UDM through the Data Window broken out by the factors
you have chosen. Look at the output and see what effect changing the ranks and
gaps has on your results. Pick out a Preset Filter or two and do the same
thing. Leave Dynamic Filters alone until you get a little farther along. The
whole point during this phase isn't so much creating profitable UDMs as it is
learning how JCapper does the things that it does. As you get more and more
experience with JCapper, using it to create UDMs eventually becomes a thing of
second nature.
Phase Two
The second part of the learning curve for UDM
construction involves acquiring the skill it takes to systematically create
profitable UDMs. Learning to do this is the one thing every new user seems to
be most interested in and is probably the reason they signed up for JCapper in
the first place. Systematically creating profitable UDMs is a skill set that
has to be learned. I strongly believe that JCapper does a very nice job of
bringing this skill set within reach of the user - if and only if that user is willing to put in the time. In the
paragraphs that follow I have listed out some general guidelines that, in my
experience, when followed closely,
will help the new user to get there in the shortest amount of time.
Step One:
Finding Contenders
The initial effort
when constructing a UDM should focus on laying
the foundation or identifying contenders. For Speed and Pace UDMs I suggest
using combinations of some of the premier ratings in JCapper. Factors such as
JRating, CPace, Weighted Figure, Form Rating, Pace Model Index, Optimization
Points, and Race Strength should prove very useful during this phase of UDM
construction. For Trainer Specific UDMs, you should focus on combining factors
such as Trainer Name, XthStartAfterLayoff, XthStartAtTheMeet,
XthStartAfterLasix, Claim Starts, Claim Days, Distance Shift, Class Shift, Surface
Shift, Recent Activity Days Last Start, Recent Activity Days Last Work, Age of
Horse in Years, Track Name, and Class Descriptor. The basic goal when finding
contenders during UDM construction should be to identify combinations of
factors that yield: lots of plays, a reasonably
good win rate, and a flat bet win roi that is significantly better than the
general population of horses as a whole. During this phase of UDM construction
it is not necessary to generate
profits. A good target to shoot for during this phase is a flat bet win roi in
the nineties (.90 or higher.)
Step Two:
Filters
In the second phase
of UDM construction, focus your efforts on weeding out the bad ones. Spend some
time running your UDM through the Data Window and test it using some Preset
and/or Dynamic Filters. Here, simple logic prevails. Whenever you are able to
identify and remove a set of horses that are really poor bets, the remaining
set of horses must be an improvement
over the set of horses that you had to start with. During this phase, a good
target to shoot for is and roi improvement of five to ten percent.
Step Three:
Value
In the third phase of UDM construction, focus your
efforts on finding value. There are factors in JCapper that are there
specifically for this purpose. Here's a short list that should be helpful: Race
Volatility, Field Size, PScore, Morning Line Rank, Morning Line Num, Morning
Line Odds Ratio, Morning Line Odds Ratio II, Divisor,
Step Four:
Validation
The fourth step of the process is Validation. It is
surprising to me how few users actually make the effort to do this. This is a
very necessary step. It is very possible, even likely, that you will have
introduced some degree of back fitting or over fitting into your data set
during step one when identifying contenders. This is especially likely if you
spent too much time and effort
refining your results with closely related factors while identifying
contenders.
During Validation, what you do is confront your UDM
with data it hasn't seen yet. Run your UDM through the Data Window using a
sizeable chunk of recent data not used during any phase of its construction.
Data Window output of your UDM run against Validation Data should look very
similar to Data Window output of your UDM run against the sample used during its creation. If this is not the
case, there is a very good chance that over fitting or back fitting was
introduced into the UDM at some point. I personally handle this situation in
this way: I do not to try and re-fit the UDM. Instead, I simply scrap it and
start over.
Live Play
Whenever I am able to validate a UDM, I immediately
add it to those I use for live play. To the new user, let me make one
recommendation. Whenever you place a UDM into live play, start out in a small
way. Take a smallish starting bankroll - you
have to decide what smallish is - and bet a percentage of that bankroll on
each one of your UDM's qualifying plays. If you have success with your UDM -
and there is no way that I can guarantee that you will - the bankroll devoted
to that UDM will grow as you make plays over time. As the bankroll grows the
amount of money bet on each qualifying play also grows, as does your confidence
in the UDM itself, as will your confidence in your own ability to
systematically create new profitable UDMs.
Tracking Your
Results
The public gradually picks up on trends over time.
Therefore, the game is an ever changing one. What works today may not work
tomorrow. UDMs do have a shelf life. How long is that shelf life? Hard to say.
The shelf life of each UDM will be different. It depends on the factor mix of
the UDM itself as well as what trends the betting public is able to pick up on.
Allow me to make one suggestion to both the new and experienced user.
Periodically check the effectiveness of each of your UDMs against current data.
Deactivate or delete those that have reached the end of their shelf life - where
the performance has tailed off significantly over an extended period of time.
-end section on
building UDMs-
System
Settings/System Definitions
The System Settings/System Definitions screen is
accessible from the JCapper Main Module by clicking the System Settings button followed by clicking the System Definitions button.
The following is a list of system settings that may
be defined by the user on the System Settings/System Definitions screen:
Layoff
Definition in Days- The system default for a layoff is 45 days. The user may override the
default by entering a value between 1 and 999 and clicking the SAVE button.
Append to
Database During Database Build- The default setting for database builds is a Build
from Scratch. To override the default and Append to Database During Database
Build, check the box and click the SAVE button.
Include
Payoffs for Entry Mates – The system default for this setting is unchecked. When checked,
during a database build, the Database Builder will include entry mate payoffs
in the results for horses that are coupled in the wagering. Example: A horse is
part of an entry in the wagering. The horse runs and finishes out of the money.
His entry mate wins the race. If the box is checked, the mutuel payoffs earned
by the entry mate will be shown in the Data Window for queries involving the
first horse. If the box is not checked, entry mate payoffs are not shown in
results returned by Data Window queries.
Odds Line
Display Type-
This setting allows users to select from among the various odds lines in the
program. The odds line type selected here is the odds line that will appear on
the HTML Report and is the default odds line used by the Data Window when
evaluating UDMs that have an OL Test as part of the UDM Definition.
Display
Trainer Name on HTML Report- The default setting is to not display trainer names on the HTML
Report. To override the default and display trainer names on the HTML Report
check the box and click the SAVE button.
Display Owner
Name on HTML Report-. The default setting is to not display owner names on the HTML
Report. To override the default and display owner names on the HTML Report
check the box and click the SAVE button.
Page Break After
Each Race –
When this setting is checked, HTML Page Break characters are inserted at the
bottom of the HTML Report for each race. The Page Break characters are not
visible when viewing the HTML Report on computer screens. But whenever the HTML
Report is sent to a printer and printed out on paper the Page Break characters
cause your printer to insert a page break immediately after the HTML Report for
each race has been printed. The result is that HTML Reports will print out one
race per page. When this setting is not
checked and the HTML Report is sent to the printer, your printer will print as
much content on each sheet of paper as room on that sheet of paper allows and
then print remaining content for that race on the next sheet of paper. The
default for this setting when you first download the program is that the box is
unchecked. To override the default and print the HTML Report one race per page
check the box and click the SAVE button.
Display
Available Wager Types – When this setting is checked a list of available wager types for the
current race is displayed in the Race Header for each race on both the HTML
Report and Text Report. A separate field containing a list of available wager
types is also written to Plays.CSV files. The default for this setting when you
first download the program is that the box is unchecked. To override the
default and display a list of available wager types on your reports check the
box and click the SAVE button.
Highlight
Morning Line Overlays on the HTML Report. The default setting is to not Highlight Morning
Line Overlays on the HTML Report. To override the default and Highlight Morning
Line Overlays on the HTML Report check the box and click the SAVE button.
Available
Colors for Overlay Highlight Color I - use this drop down to select a color to be used
with Cutoff 1.
Available
Colors for Overlay Highlight Color II - use this drop down to select a color to be used
with Cutoff 2.
Cutoffs for
Overlay Highlighting –
Cutoff 1 – Color I is applied on the
HTML Report for any horse whose ML Odds Line Ratio is at or above the cutoff
specified.
Cutoff 2 – Color II is applied on
the HTML Report for any horse whose ML Odds Line Ratio is at or above the
cutoff specified.
Notes about Overlay Highlighting –
In JRating enabled versions of JCapper, the
following horses qualify for overlay highlighting:
1. Horses selected by positive
expectation UDMs.
2. JRating rank=1 or 2.
3. CPace rank=1.
In JRating disabled versions
of JCapper (new customers March, 2007 and later) the following horses qualify
for overlay highlighting:
4. Horses selected by positive
expectation UDMs.
5. JPR rank=1 or 2.
6. CPace rank=1.
Data Window Bankroll Settings
Starting Bank
Pct of Bank
Max Bet
The Data Window is programmed to apply the above
user settings to all Data Window queries. Each horse pulled up during a query
results in the Data Window making and keeping track of mythical bets made in
accordance with these user defined bankroll parameters. Bankroll results are
displayed at the bottom of all Data Window queries. This is a great way to see
what would have happened to a bankroll had you been able to play this way.
Advanced users find this feature especially useful when evaluating the strength
of positive expectation UDMs.
PaceLine
Selection Rules- The user has the ability to define a set of rules that the program
will use for selecting pace lines. The system default is to identify and select
the best speed figure in the most recent 5 races and 120 days regardless of
surface or distance. The user may override the system default by creating his
or her own set of rules and clicking the SAVE button.
Enforce
PaceLine Logical Distance- Checking this box will cause the program to make a comparison between
today's distance and the distance of races taken from a horse's past
performance record. When this box is checked the only races considered during
PaceLine selection are those that were run at a distance similar to today's
race.
Enforce
PaceLine Logical Surface- Checking this box will cause the program to make a comparison between
today's listed racing surface and the racing surfaces of races taken from a
horse's past performance record. When this box is checked the only races
considered during PaceLine selection are those that were run on the same
surface as today's race.
Races Back - The system default, as
mentioned above, is to select the best PaceLine in the past 120 days using the
5 most recent starts in a horse's past performance record. The system default
for number of races to go back can be overridden by simply making a selection
from this drop down followed by clicking the SAVE button.
Days - The system default, as
mentioned above, is to select the best PaceLine in the past 120 days using the
5 most recent starts in a horse's past performance record. The system default
for number of days to go back can be overridden by simply making a selection
from this drop down followed by clicking the SAVE button.
Note- In all cases, after making selections/changes
with the System Settings/System Definitions screen, changes become effective only after clicking the SAVE button.
Live Play Module Settings-
Live Play
Enabled –
When this box is checked, during a Calc Races routine info about each horse is
written to the LivePlay table for use by the Live Play Module. When this box is
unchecked this operation is skipped during a Calc Races routine. This operation
adds a little time to each Calc Races routine. If you are not using the Live
Play Module you can speed up your Calc Races routines a little bit by
un-checking this box. Of course you will have to remember to check this box in
order to get your Calc Races routines to write info needed by the Live Play
Module should you wish to use it.
Live Play Only – When this box is checked
the only file written to during a Calc Races routine is the LivePlay table for
used by the Live Play Module. If you are using the Live Play Module exclusively
without looking at the Text, CSV, or HTML Report(s) then checking this box will
speed up your Calc Races routines. Of course you will need to check this box in
the event that you want to start using the other reports again.
Available
Colors and Cutoffs –
Color I corresponds to MLOR3 and OR3 Cutoff1 overlay
highlighting on the Live Play Module. Whenever either MLOR3 or OR3 are at or
above the user selection for Cutoff I, the user selection for Color I is
applied to the individual horse.
Color II corresponds to MLOR3 and OR3 Cutoff1I
overlay highlighting on the Live Play Module. Whenever either MLOR3 or OR3 are
at or above the user selection for Cutoff II, the user selection for Color II
is applied to the individual horse.
UPR GroupName – This user setting is
where you define the GroupName that drives the UPR that will be sent to your
daily reports during Calc Races routines and to your PlayList files during
database builds. The default setting shipped with the program is DEFAULT. As
you make ImpactValue table entries towards creating your own UPR (User Defined
Power Rating) each new UPR GroupName that you create becomes available to this
drop down on the System Definitions screen. Use this drop down to select the
UPR GroupName you want JCapper to use to drive your UPR.
-end section on
System Settings/System Definitions-
Windows Control Panel Regional and
Language Options
Notice to international
(outside the
All of the evaluate days between races and works
algorithms in JCapper are based on the dates themselves being in the format
rendered by Windows when the Regional and Language Options settings is English
(United States).
Some of the other date formats have the ability to
switch the positions of the month and day. For example, the
If that describes the settings on your machine then
in the above example JCapper is picking up the wrong month (09) instead of 10
when evaluating time between workout and race dates. This will adversely impact
the program’s ability to make decisions about form and trainer intent.
To get JCapper to properly evaluate workout and race
dates:
-end section on
Windows Control Panel Regional and Language Options-
Troubleshooting
JCapper Installs
There is a
separate Help Doc titled Troubleshooting
JCapper Installs devoted to this subject. In almost all cases, error
messages related to the install process result when required Windows components
are missing from your machine. The Troubleshooting
JCapper Installs Help Doc explains operation of the JCapper Diagnostics
Tool in detail along with how to use regsvr32 to register OCX and DLLs. If, however, after reading the Help Doc and
running the Diagnostics Tool, you still need help with your install – please
contact me by email. - Jeff