Database Handicapping Software- JCapper

JCapper Message Board

          JCapper 101
                      -- UDM question

Home Register
Log In
By UDM question
Tom C
4/17/2012
11:33:50 PM
I think I know the answer to my question, but I am going to ask it anyway.

Does anyone know how to write a UDM that shows a maiden race win 2 starts back followed by a loss in the horse's last start.

Thanks for your help.

Tom C

Reply
jeff
6/3/2019
10:33:33 AM
The table schema for the StarterHistory table gives you ClassDescriptor for today's race and ClassDescrLast for the most recent running line.

If a maiden win happened in the most recent running line it's currently doable in the program:

AND (CLASSDESCRLAST = 'M' OR CLASSDESCRLAST = 'S')
AND POSFINCALL = 1

The above lines would be one example of how to do this.

To delve further back in the running line history looking for a maiden win would require that I create a new factor and call it something like XthStartMaidenWin.

From there, I would then make it available as a valid selection in the ImpactValues Table Wizard so that it could be used or translated/replicated when creating a UserFactor.

I'm willing to do the above.




However, development on XthStartMaidenWin has to stop there.

Adding it as a new factor and making it directly grab-able in the UDM Wizard requires making a format change to both of the daily text export files as well as the pl_profile.txt file.

The fastest growing segment of the JCapper user community are those who are actively parsing those files using their own self written apps.

Any change that I make to the published text file formats is going to "break" those apps.

In addition, those who download a new program update that forces a pl_profile.txt file format change are also forced to rebuild every single one of their databases from scratch.

Unless the purpose for publishing a file format change is to make some compelling new factor available... something that R&D suggests falls into the category of being a game changer:

My experience as a program author has been that forcing a pl_profile.txt file format change is something that makes a quite a few people unhappy.

That's why I purposely haven't gone there with any of the recent published new program updates. (And why I prefer not to go there at all.)

I hope I managed to explain most of that in a straightforward way that makes sense.


-jp

.


~Originally posted by: jeff on: 4/18/2012 at: 2:03:45 PM~

~Edited by: jeff  on:  6/3/2019  at:  10:33:33 AM~

Reply
Tom C
4/18/2012
6:32:43 PM
Jeff,

This was not something that I had to have, only curious if it could be done easily within the program.

Thanks,
Tom C

Reply
Windoor
4/19/2012
10:55:19 AM
I have an Excel program that will do this.

If fact it goes back six racing lines and can filter on many things, including, surface, Race type (your question) class, if claimed, all calls, (with position on track and lengths behind, you would want final call) and track condition.

Along with about 42 other filters.

In order to get it into J/Capper, I have to assigned the filtered results a name, and then change the name of a field in J/Capper file, so I can filter on it there.

I use fields in J/Capper that I do not use, such as Owner, sire, siressire, etc.

So, it can be done, it's just a lot of work.

Regards,

Windoor

~Edited by: Windoor  on:  4/19/2012  at:  10:55:19 AM~

Reply
Tom C
4/20/2012
4:14:41 AM
Windoor,

Thanks for your comments.

I was looking for an easy way to do this as a fellow race player suggested it. I am at an age where I don't want to spend a lot of time constructing UDMs. I have been using JCapper since 2005 and am probably one of a few that still uses the program in its basic state. I use Bris files, playlist mode not SQL, and have never even tried to make a UPR. I am computer literate but also have become very lazy in my approach to handicapping. I have had sporadic success with JCapper and am grateful for all the help and updates Jeff has provided.

Again, thanks for your comments.

Tom C

Reply
jeff
6/3/2019
10:47:07 AM
Note: I edited post #2 in this thread because I misspelled a field name in the sql that I (originally) posted.

The original sql (which was wrong) was posted as follows:

AND (CLASSDESCRIPTORLAST = 'M' OR CLASSDESCRIPTORLAST = 'S')
AND POSFINCALL = 1


CLASSDESCRIPTORLAST is not the correct fieldname - and causes an error.




The sql (which has now been corrected) reads as follows:

AND (CLASSDESCRLAST = 'M' OR CLASSDESCRLAST = 'S')
AND POSFINCALL = 1


CLASSDESCRLAST is the correct fieldname - and works just fine.



-jp

.



Reply
Reply

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