|
|
|
|
|||||||
| Google Site Search | Get RDSSGet RDSS | Sartin Library | RDSS FAQs | Conduct | Register | Site FAQ | Members List | Today's Posts | Search |
| RDSS - Leverage/Pace Discussion about a NEW RDSS approach to identifying Key Contenders, the Pace Bias and a structured betting approach |
![]() |
|
|
Thread Tools | Display Modes |
|
|
#1 |
|
Grade 1
Join Date: Jun 2005
Posts: 4,587
|
Perceptor
I agree with LT1 about the use of perceptor as a pace line selector. It
is good as a general tool but in certain instances needs to be adjusted A glaring example of this is in turf races, by using a dirt line that the perceptor picks it skews the readouts. I have gone back and redone quite a few races and seen where this is the case. Actually, the program works quite well on turf where you change it. Especially in NP and blue arrow horses. Jeff |
|
|
|
|
|
#2 |
|
Grade 1
Join Date: Jun 2005
Posts: 4,587
|
I spoke out of turn here
I went back and did some more races with perceptor and found that in the end was not much difference at all using it. Also found me agreeing with the pick most of the time. So now decided to just use perceptor lines, who says you can't treat an old dog new tricks. Jeff |
|
|
|
|
|
#3 |
|
Grade 1
Join Date: Jun 2005
Location: Nanaimo, British Columbia, Canada
Posts: 9,238
|
The thing about Perceptor, which Doc recognized though which ended up implemented more prominently in Speculator and then RDSS, is - for better or worse - all lines are attempted to be equalized (to today's race), regardless of distance, surface, track variant. Agreed, it's a bit of an imprecise adjustment formula, but it works well enough until you develop better and more consistent skills that the program
(and even then ...). The whole purpose for that is so you can use non-comparable lines to represent the horse today if you have to, or if you want consistency and good-enough line selection in your analysis. I never tell folks not to go back to a way-back line if the horse is running well today, or had excuses like returning from a layoff, faced too strong pace recently, ran somewhat competitively against stronger competition, etc. Also FWIW, there is a setting you can make in the Config File (which I will add to the Config Screen) to tell the formula to use the last 'n' lines instead of last 3 (e.g. last 4, last 5, last 99 or all lines). But I still (as a dream fantasy) would like to see an outcome study (both win rate AND $ROI) comparing the software's line selections and a 'you-pickem' strategy. I predict the software will not fare much worse (and maybe better) ... ![]() Ted
__________________
RDSS - Racing Decision Support System™ |
|
|
|
|
|
#4 |
|
Grade 1
Join Date: Jun 2005
Posts: 4,587
|
Thanks Ted for explanation on that
Jeff |
|
|
|
![]() |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Perceptor Usage Question | Ted Craven | RDSS Documentation -- All Versions | 1 | 07-20-2019 11:14 AM |
| Backup & Release Notes and Best Perceptor | Because I Can Jim | General Discussion | 1 | 10-05-2013 01:11 PM |
| TAM 03-21-12 Using RDSS (Perceptor & KGEN) | partsnut | Selections | 3 | 03-21-2012 12:17 PM |
| The Perceptor - What Is It's Purpose And Function? | partsnut | RDSS | 8 | 11-09-2011 07:34 PM |
| PRX 11-09-11 Race 1-5 (Using RDSS Perceptor) Top 2 | partsnut | Selections | 11 | 11-09-2011 06:48 PM |
|