|
|
|
|
|||||||
| Google Site Search | Get RDSSGet RDSS | Sartin Library | RDSS FAQs | Conduct | Register | Site FAQ | Members List | Search | Today's Posts | Mark Forums Read
| RDSS 1: Bug Reports Historical Bug problems and solutions for the first version of RDSS (through V0.99.2) |
|
|
Thread Tools | Display Modes |
|
|
#1 | |
|
Grade 1
Join Date: Jun 2005
Location: Nanaimo, British Columbia, Canada
Posts: 9,264
|
Quote:
Robert, I think Froggy and you got the workaround for this bug working. I apologize that it has persisted so long - I should be able to swat it any minute (or week) now. Here's a poll, please: when we can't figure out velocity due to lack of 1 call time (let's start with just 1 missing call time), what should RDSS do: 1. 'invent' the missing call time based on standard deceleration tables, and flag the line as partly 'invented', but end up with some kind of figures for it, OR 2. mark the line as UNUSABLE, as per Val and Spec Ted
__________________
RDSS - Racing Decision Support System™ Last edited by Ted Craven; 06-11-2007 at 08:45 PM. |
|
|
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Intuition and the 1st Call Projected Pace | RichieP | Hat Check - How Can We Help You? | 12 | 10-10-2006 02:12 PM |
| Post times | admin | General Discussion | 0 | 07-14-2006 07:40 PM |
| F3 Times | shoeless | Classic Sartin Programs - Support, Discussion | 6 | 07-14-2006 12:14 PM |
| Evaluating Shippers/ Pace call | RichieP | Speculator | 4 | 04-24-2006 02:32 AM |
|