By |
Canrun/Cantrun |
PhilCVG 8/5/2013 10:44:38 PM | Anyone else unable to use the canrun filter to filter out the cantrun horses? Whether I use it in UDMs or Apply Special Filters in the data window, the cantrun horses continue to be included in the UDM.
|
Caveat 8/6/2013 10:26:24 AM | just ran it in SQL mode...working OK
in playlist mode..
did you click "add filter" and then click
"save and close"
the filter is "CLEAN avoid DIRTY horses"
?
~Edited by: Caveat on: 8/6/2013 at: 10:26:24 AM~
|
PhilCVG 8/6/2013 11:48:27 AM | I beleive so. I've even run it through the data window "apply special filters" and it still gives me the cantrun horses. The XForm horses are excluded, but the cantruns are still included. I gave it about a half an hour last night trying to figure it out, even did a google search of the JCapper message board and found an old post by someone having the same issues.
I'm running the Silver Program in playlist mode.
|
jeff 8/7/2013 5:41:15 PM | Looks like you found a bug Phil...
Before going any further I want to point out the following:
• The bug is limited in scope to the Silver program only - and in Playlist File Mode only. Those of you operating the Silver program in Sql Mode are not affected by it. Also, those of you using the Platinum program (no matter what mode you are using) are not affected by it.
• A practical work-around is presented below. Read through my screenshots and explanation first. (It'll make sense once you do that.)
Replicating the bug in the Silver program I logged into the program as a Silver user, launched the Data Window, navigated to a Silver folder, and ran some queries with the data broken out by CANTRUN/XFORM Attribute.
Screenshot #1 - Playlist File Mode: CLEAN preset filter code applied
The above linked to screesnhot clearly shows the nature of the bug. The CLEAN preset filter code is designed to remove XFORM starters from the results set (which it did.) In addition, the CLEAN preset filter code is designed to remove CANTRUN starters from the results set (which it did not.)
Screenshot #2 - Playlist File Mode: CLEAN-CANRUN preset filter codes applied
The above linked to screenshot shows the same results set... However, this time I've applied both the CLEAN and CANRUN filter codes. (Note that the filter codes are separated with a dash character.) Same bug in play... The CANRUN filter code failed to remove the CANTRUN starters from the results set.
Screenshot #3 - SQL Mode: SQL Mode Equivalent of CLEAN preset filter code applied
The above linked to screenshot shows me executing a sql expression designed to return CLEAN starters only against a Silver StarterHistory table for the same time period. Note that in sql mode everything works as designed.
The bug explained: After giving the bug some thought I realized what's going on internally within the Silver program.
CANTRUN horses are those that, among other things, have a JPR rank greater than 5.
JPR is not available as a factor in the Silver program.
For sql mode - I did address the CANTRUN part of things in the Silver program at database build time by adding logic in the program to replace JPR rank eval at 5 with SilverRating rank eval at 5. That's why it works in sql mode in the Silver program.
However, in Playlist file mode CANTRUN is handled differently. A separate evaluation (using JPR rank) is made in the Data Window. The CANRUN preset filter code fails in the Silver program because it relies on JPR rank - which doesn't exist in the Silver program.
A Practical Work Around:
Screenshot #4 - UPR Rank: CLEAN preset filter code applied
The above linked to screenshot shows the results set with the CLEAN filter code applied - which removes XFORM starters but not CANTRUN starters - with the data firther broken out by UPR rank.
Note: In the Silver program UPR and SilverRating are one and the same thing.
Look at the individual rows for each UPR rank. Note what happens to win rate and roi (they are noticeably weaker) when UPR rank is >= 6.
Screenshot #5 - Silver UDM Equivalent to CLEAN: CLEAN preset filter code applied
For this screenshot, I created a UDM that has two factor constraints only:
1. I added the CLEAN preset filter code.
2. I added max rank = 5 for UPR.
The screenshot shows the results set returned by running that UDM through the Data Window - with the data broken out by the CANTRUN/XFORM ATTRIB.
Note: The results set does show a row designated by the program as CANTRUN.
However, look at the win rate and roi of the starters in that row. Hint: Both are considerably stronger than CANTRUN starters as a whole.
The above UDM makes for an equivalent or better replacement for the (broken) CLEAN preset filter code in the Silver program.
-jp
.
~Edited by: jeff on: 8/7/2013 at: 12:33:13 PM~
~Edited by: jeff on: 8/7/2013 at: 5:41:15 PM~
|