Pace and Cap - Sartin Methodology & The Match Up - View Single Post

Ted Craven · 01-03-2021, 01:40 PM

Tom, this came up with another user 2 days ago, different track. Here's what we diagnosed - see if it applies to your situation.

Reason: with tote enabled (checkbox on Config) RDSS checks for tote data on the current race for today's card. When today's races are over - until the next day's tote data begins (say around 4am?) - the current day's race is the final race of the day.

When you work on a race card other than today (e.g. tomorrow) RDSS does not bother checking tote data. However, when you work tomorrow's race card after midnight, then it becomes today and then RDSS checks for tote data! After midnight and until fresh tote data arrives for the next day (or the tote data gets reset and no data is yet available) - since the current tote data available is still the final race of now yesterday (as of midnight), tomorrow's final race is then automatically assembled as usual (RDSS not knowing that current tote data does not apply to what is now tomorrow's final race).

The problem you (and the other person) see is when there are more runners in today's final race than in tomorrow's final race. SA Race 9 Jan 1 had 12 runners, while SA Race 9 Jan 2 had 9 runners. That's why you see 3 blank Entries and a screwy set of PPs. RDSS initializes tote (which affects the set of Entries, when tote is available) based on yesterday's final race, not on today's final race (after midnight).

This only happens for the final race, when one first assembles a race on a card with tote enabled after midnight.

If this also describes your situation, then the solutions are 2-fold:

Solutions:

1. Before opening tomorrow's race card, UNCHECK the tote setting on Config when working tomorrows race after midnight (and restart RDSS). Then the above problems do not occur. If you normally use tote data, remember to switch it back on tomorrow.

2. Don't work tomorrow's races after midnight (and before tote resets early in the morning, say 4am?)

If your situation is different than described, please let me know.

I might be able to perform an additional online data check for what DATE is current (i.e. today/tomorrow's date) to prevent RDSS from accessing tote during overnight hours when current tote data does not reflect the date you are working (i.e. tomorrow).

Ted

01-03-2021, 01:40 PM	#369
Ted Craven Grade 1 Join Date: Jun 2005 Location: Nanaimo, British Columbia, Canada Posts: 9,251	Tom, this came up with another user 2 days ago, different track. Here's what we diagnosed - see if it applies to your situation. Reason: with tote enabled (checkbox on Config) RDSS checks for tote data on the current race for today's card. When today's races are over - until the next day's tote data begins (say around 4am?) - the current day's race is the final race of the day. When you work on a race card other than today (e.g. tomorrow) RDSS does not bother checking tote data. However, when you work tomorrow's race card after midnight, then it becomes today and then RDSS checks for tote data! After midnight and until fresh tote data arrives for the next day (or the tote data gets reset and no data is yet available) - since the current tote data available is still the final race of now yesterday (as of midnight), tomorrow's final race is then automatically assembled as usual (RDSS not knowing that current tote data does not apply to what is now tomorrow's final race). The problem you (and the other person) see is when there are more runners in today's final race than in tomorrow's final race. SA Race 9 Jan 1 had 12 runners, while SA Race 9 Jan 2 had 9 runners. That's why you see 3 blank Entries and a screwy set of PPs. RDSS initializes tote (which affects the set of Entries, when tote is available) based on yesterday's final race, not on today's final race (after midnight). This only happens for the final race, when one first assembles a race on a card with tote enabled after midnight. If this also describes your situation, then the solutions are 2-fold: Solutions: 1. Before opening tomorrow's race card, UNCHECK the tote setting on Config when working tomorrows race after midnight (and restart RDSS). Then the above problems do not occur. If you normally use tote data, remember to switch it back on tomorrow. 2. Don't work tomorrow's races after midnight (and before tote resets early in the morning, say 4am?) If your situation is different than described, please let me know. I might be able to perform an additional online data check for what DATE is current (i.e. today/tomorrow's date) to prevent RDSS from accessing tote during overnight hours when current tote data does not reflect the date you are working (i.e. tomorrow). Ted __________________ RDSS - Racing Decision Support System™ Last edited by Ted Craven; 01-03-2021 at 02:07 PM.