Log Stake Amount Same but Different When Killed Excel

[CallumPerry]

Evening.

Hoping one of you lovely gents could help me out with something I've seen in a log tonight? I have added some fill/kill logic into my VBA code and when I was testing (on practice mode) I saw the following happened...

A lay bet was made on the 4th selection on my sheet and cell O15 showed "PLACED". The first line of the log confirms this. I wanted to try and catch a movement so tried again seconds later, sure enough a lay bet hit the market unmatched as confirmed in the log, perfect!

My system then doesn't fire in another bet as it should when it notices a string containing "was killed." in cell L16. This is my trigger to try again but it didn't work so I checked the log. I now realise I need to add something to my system to deal with partially matched bets which can return the last line in the log but what is strange in this example is the amount. £2.00 staked reached the market but £2 was matched and the remainder was killed??? What remainder?

Why is the same amount shown to two decimal places and then rounded a line later? What is left over? Is this just a rounding error? Is it just a glitch in practice mode or is there some other underlying reason why it didn't just show "was filled"?

************************************************************************************

04/03/2020 21:22:06: Market changed to Donc 4th Mar - 21:26 B4 450m
04/03/2020 21:25:29: [Excel] : £ 2.00 Lay bet placed on 4. Diggin Deep at 15.5. Fully matched at 15.5. Ref: 10007 ( Fill or kill bet with 2 seconds delay. )
04/03/2020 21:25:36: [Excel] : £ 2.00 Lay bet placed on 4. Diggin Deep at 15.5. Entirely unmatched when it initially reached the market. Ref: 10008 ( Fill or kill bet with 2 seconds delay. )
04/03/2020 21:25:38: [Excel] : £ 2 of unmatched bet (Ref:10008) was filled before remainder was killed.
04/03/2020 21:26:14: Market has been suspended

[Anbell]

04/03/2020 21:25:38: [Excel] : £ 2 of unmatched bet (Ref:10008) WAS FILLED BEFORE remainder was killed.
04/03/2020 21:26:14: Market has been suspended

I can partially help here, I think.

When BA initiates a fill/kill bet it sets a reminder to itself to kill the bet in X seconds. IF the bet is still there it gets killed, if it is no longer there then BA reports that the bet has been filled before it could be killed. (and there's the 'partial' scenario)

So you can't use "was killed." in your search string, but you could possibly use "remainder was killed" (depending on how you handle 'partial')

[Anbell]

Is it just a glitch in practice mode or is there some other underlying reason why it didn't just show "was filled"?

BTW: AFAIK Betangel doesnt normally ever track whether a bet "was filled" so you won't see that in the logs, UNLESS it is a Fill/Kill bet in which case it has to try to Kill it, and either finds all/some/none of the stake remaining.

It seems weird but there must be a good explanation for it.

ETA: Actually, the bets appear in MATCHED BETS, so the above is probably nonsense (except for the part where the matched bets dont appear in the logs). Excuse me.

[CallumPerry]

So why are the matched amounts showed in two different ways, £2 and £2.00? It shouldn't have said 'the remainder was killed' at all since there clearly is no remainder. If it's a rounding issue then is it also the case in live mode has anybody noticed?

[Anbell]

So why are the matched amounts showed in two different ways, £2 and £2.00? ... If it's a rounding issue then is it also the case in live mode has anybody noticed?

There's no rounding 'error' - it is just reporting it that way.

From my logs: "$ 12.12 of unmatched bet (Ref:10096) was filled before remainder was killed."

2.00 = 2 - so the reporting rule for that part of the logs is presumably "Use as many decimal points as needed."

It shouldn't have said 'the remainder was killed' at all since there clearly is no remainder.

Again, it's just the way that the log logic is structured. There is an "entirely unmatched" bet when it hits the market, and it tries to kill the entirety of it X seconds later,then it reports:
"(Initial stake - remaining stake when killed) was filled before remainder was killed."

If the bet has been filled in entirety, then 'remaining stake when killed' = 0

It looks weird, and is a bit clunky, but it is 'accurate.'