|
|
|
|
|||||||
| Google Site Search | Get RDSSGet RDSS | Sartin Library | RDSS FAQs | Conduct | Register | Site FAQ | Members List | Today's Posts | Search |
| RDSS Beta Testers Questions & Answers - CLOSED Please make new posts in the main RDSS Forum |
|
|
Thread Tools | Display Modes |
|
|
#41 |
|
Grade 3
Join Date: Jun 2005
Posts: 54
|
Hi Ted,
I keep forgetting to ask, is there going to be anything like the F9 key so we can put in our own notes? thank you Tom k |
|
|
|
|
#42 |
|
Grade 1
Join Date: Jun 2005
Location: Nanaimo, British Columbia, Canada
Posts: 9,264
|
Tom,
Sure thing! Pretty much everything on Val and Spec will show up somewhere before we get to Release 1.0. Ted
__________________
RDSS - Racing Decision Support System™ |
|
|
|
|
#43 |
|
Grade 3
Join Date: Jun 2005
Posts: 54
|
Ted,
I really like that check off on the right hand side on the primary screen. I don't know how the other testers feel about it,but for me it's great. If it's too much work to put it on the rest of the screens, I could live without it on them , but I hope you leave it on the primary screen. tom K |
|
|
|
|
#44 |
|
Grade 1
Join Date: Feb 2006
Location: central islip ny
Posts: 1,196
|
Request
Hi Ted:
I have been studying the lines used by the program. They seem to be working pretty well. Is it possible to have those lines selected automatically if one so chooses? |
|
|
|
|
#45 |
|
Grade 1
Join Date: Feb 2006
Location: Escondido CA just 25 minutes from where the turf meets the surf - "...at Del Mar"
Posts: 2,509
|
Ted:
This is just a visual tweak (maybe) and certainly a Matchup related suggestion. In races where the call information for the distance of the line chosen is different from the race distance or where different distances are used by the various contenders, e.g. when a 9F line used in 8F or 8.5F race or 7F in a 6F or 6.5F race, it would be visually easier to evaluate stacked lines if the same point in the race for each horse was in the same column. Another advantage is that the projected pace info could then be shown or highlighted, whereas now a 9F horse working against a pace from a shorter route doesn't get highlighted as fast or slow vs today's pace. route example line: 8F: 23.0 47.0 111.0 144.0 9F: 46.4 110.4 148.2 In this example, if the 8F race were POR the 9F line does not get highlighted as a faster race. sprint example line 6F: 22.0 45.0 110.0 7F: 22.2 45.3 110.1 123.0 Thanks for the opportunity to contribute Bill |
|
|
|
|
#46 | |
|
Grade 1
Join Date: Jun 2005
Location: Nanaimo, British Columbia, Canada
Posts: 9,264
|
Quote:
Ted
__________________
RDSS - Racing Decision Support System™ |
|
|
|
|
|
#47 | |
|
Grade 1
Join Date: Jun 2005
Location: Nanaimo, British Columbia, Canada
Posts: 9,264
|
Quote:
A very good observation (and a normal one). This should get resolved naturally in my planned re-organized Adjusted screen (or whatever that becomes). Greed, it is a weakness of the current implementation on Projected Pace matching on the Original screen. Ted
__________________
RDSS - Racing Decision Support System™ |
|
|
|
|
|
#48 |
|
Grade 1
Join Date: Jun 2006
Posts: 1,138
|
Ted,
Maybe you can also put a Robot Handicapper wherein it incorporates the modeler and what Robot suggest to bet on this particular race based on what's been winning with the current factors.Just an idea... Ray |
|
|
|
|
#49 |
|
Grade 1
Join Date: Jun 2006
Posts: 1,138
|
Ted,
What i meant is the user can configure his own formulas based on the RDSS factors and his own models,and have a set of 'portfolios' for turf routes,dirt sprints or routes,etc....with the HMI money management,this would make it more robust and complete... Ray |
|
|
|
|
#50 |
|
Grade 1
Join Date: Jun 2005
Location: Nanaimo, British Columbia, Canada
Posts: 9,264
|
OK Ray.
From our conversations, I think I grasp what you mean. I think your vision of a Robot is what will gradually accrue by the incremental collection of various tools, as they get delivered: first the flow of Result Charts into RDSS (or at least a spot to manually record race results and mutuels); then tagging Analysis screen pacelines by race finish position and mutuel; then filtering/sorting these lines by track, distance, surface, etc (aka a factor model); then overlaying this model against today's race (e.g. winners E/L range against E/L's in today's race Analysis set); then the toteboard connection to provide current odds and potential wager overlays; then a wager construction tool (including bet sizing like HMI) overlaid against realtime odds; then an assessment of which wagers, given your final contenders, represent value; = a Robot of some sorts... Each one builds on the one before. I can't say when that final one will appear, but all of the previous ideas are at some stage or the other in the works. Thanks for that! Ted
__________________
RDSS - Racing Decision Support System™ |
|
|
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| SR questions | admin | RDSS | 1 | 02-25-2007 02:12 PM |
| Match Up book questions | Secretariat | Matchup Discussion | 7 | 02-12-2007 12:08 PM |
| Energy Program Questions | Houndog | Velocity Programs | 23 | 05-20-2006 12:24 AM |
|