UPDATE trigger on same horse ?

[woods]

I was running BA BetDaq today with two workbooks attached. I noticed that in the special event that I have the same selection on both workbooks, only one of the bets will be updated (seems to be the bet that fired first).

I have the excel workbooks set up to initially BACK the selection, then on subsequent refreshes UPDATE the price to follow the market (inspired by the "Keep at front of queue using UPDATE trigger" example spreadsheet).

The BACK part fires fine, but one bet just stays at the initial back odds.

Is this a bug, or just how it works ? Maybe a limitation somewhere.

[woods]

It must be a bug. Did a couple of further tests to confirm whats happening.

1. Place two bets on separate horses - UPDATE works fine.

2. Place two bets on same horse - UPDATE works for one bet.

[GaryRussell]

I'll look into it.

[GaryRussell]

It's working OK here. Are you sure your spreadsheet is actually populating the UPDATE trigger correctly in this instance? Could the fact they are on the same selection be interfering with the logic in your spreadsheet that inserts the UPDATE trigger?

I did the following test.

1. Open the same market in two tabs.
2. Link first tab to sheet1 and second tab to sheet2.
3. Manually entered the BACK triggers on both worksheets.
4. Manually entered UPDATE triggers on first worksheet then second worksheet. Also tested with UPDATE on second worksheet then first.

I've checked the code and can see no reason why they should interfere with each other just because they are on the same selection. I am confident this is not a bug.

[woods]

Hi Gary

You're right. There is something weird going on in my spreadsheet. I actually tried manually entering the triggers yesterday, and then concluded that my spreadsheet was fine, when that didn't work either.

I tried just now to enter both odds and trigger manually, and it does work.

For some reason when I let excel update the odds cell, and only in the specific instance when I have the same horse and therefore also the same calculation in both workbooks something goes wrong.

I get this 1193369567_OrderAPIInProgress, on the spreadsheet that doesn't fire the update right. The BACK is always fired.

My odds is updated by:
=IF(AA5="BACK",IF(I5>(S5*2),minusTicks(H5,1),minusTicks(J5,1)),AI5)

Where I5 is the money on the best offer, and S5 is my own stake. (To avoid continuously underbidding my own offer).

As far as I can see, it is an excel optimization thing, caused by the exact same calculation appearing twice. I guess the odds on the second sheet isn't updated "correctly" for the UPDATE trigger to handle it. But it is just a guess at this point.

[woods]

Okay, change of mind again..

I had time to investigate a little further, and I think I see what is going on now.

This is how to trigger the problem:

1. The UPDATE must be from two different workbooks.
2. Both UPDATE events must fire in the same refresh.
3. There must be a change in the odds for both selections.

For my tests, I have entered everything, odds, trigger, stake, manually.

It turns out that the selection being the same horse, actually does not matter after all. Just never noticed it, when I have bets on different horses. Which makes sense really, as typically I will have either one of the bets matched quickly, or the odds will only change for one horse during a refresh.

It would be great, if you could make another try of this Gary.

[GaryRussell]

Okay, change of mind again..

I had time to investigate a little further, and I think I see what is going on now.

This is how to trigger the problem:

1. The UPDATE must be from two different workbooks.
2. Both UPDATE events must fire in the same refresh.
3. There must be a change in the odds for both selections.

For my tests, I have entered everything, odds, trigger, stake, manually.

It turns out that the selection being the same horse, actually does not matter after all. Just never noticed it, when I have bets on different horses. Which makes sense really, as typically I will have either one of the bets matched quickly, or the odds will only change for one horse during a refresh.
It would be great, if you could make another try of this Gary.

Betdaq's API does not accept two bet requests at exactly the same time which appears to be the problem. BA is supposed to handle this but clearly isn't because you get that error message. I shall fix this.

[GaryRussell]

I have released version 1.0.7.9 of Betting Assistant for Betdaq. This should solve your problem.

[woods]

Thanks Gary