by Gavin » Mon Jan 01, 2018 3:52 pm
Hi hedgeupgreen,
Thanks for your messages.
The Bet Summary columns in Excel provide a way to see the progress of bets being matched, albeit in an aggregated format. For most strategies, those columns can even be used to deduce whether a particular single bet has been matched, assuming that your strategy only places one bet on each side of the market at a time, on each runner and doesn't place any more bets until the first bets have been matched or cancelled. That way you can work out if the most recent bet has been matched by looking at whether the total matched has changed in the bet summary columns and in also by watching if the two sides of the market has an equal matched amount in the bet summary columns.
I'm not sure what caused the error that you mentioned. Did you see anything else unusual? For example was a runner removed (non-runner) during your betting session on that race?
I wonder if it occurred during the moment when the autopilot tried to jump forward and therefore as the number of runners changed in that moment and had to be re-populated in Cymatic and Excel. Perhaps during that brief moment some overlapping data from the previous race might have caused Cymatic and Excel to get that error, although that shouldn't really cause a problem and I am just wondering aloud if something like that might have caused it.
It would help me to know which Autopilot trigger setting you were using. Was it the one that moves the autopilot forward at the end of the race or at the scheduled start time?
Kind regards,
Gavin