New beta version of Bet Angel v1.62.0 beta3

[elofan0]

saw something like on you tube but not for exchange markets

https://www.youtube.com/watch?v=DMZ4Lep0AAk

[Kermy74]

saw something like on you tube but not for exchange markets

https://www.youtube.com/watch?v=DMZ4Lep0AAk

The correlation table in BA makes more sense now after watching this. Thanks

[elofan0]

Your welcome still trying to workout how to use it to its best by screen recording .. the excel buffs will be able do their own charts but tried and failed on that one.. as being an excel novice

[sniffer66]

Even with the new Beta, I'm still getting the ongoing issue where removing markets via the BA API leaves 'invisible' markets still listed via the API

Market 1.229481584 closed and added for removal
Removing markets: ['1.229481584']
Successfully removed markets: ['1.229481584']
Processing market 1.229481584 with 5 selections
Selection 45551105: 1. gibbys girl - Result: Loser
Selection 45032087: 2. drumdoit al - Result: Loser
Selection 67542912: 3. fire lucy - Result: Loser
Selection 69684984: 5. congress bell - Result: Winner
Selection 65710582: 6. signature lee - Result: Loser
Market 1.229481584 closed and added for removal
Removing markets: ['1.229481584']
Successfully removed markets: ['1.229481584']

Processing market 1.229481584 with 5 selections
Selection 45551105: 1. gibbys girl - Result: Loser
Selection 45032087: 2. drumdoit al - Result: Loser
Selection 67542912: 3. fire lucy - Result: Loser
Selection 69684984: 5. congress bell - Result: Winner
Selection 65710582: 6. signature lee - Result: Loser
Market 1.229481584 closed and added for removal
Removing markets: ['1.229481584']
Successfully removed markets: ['1.229481584']

The request successfully removes the market from Guardian, but a further getMarkets request still lists the market , and then on every loop tries to remove it again

I did log this before (and I think someone else did), and the only way I can cleanly remove the markets is to restart BA. Those race Winner\Loser strings are being set by an SV in Guardian and are still being retained as well as the market itself

Edit: Just to add to this: 2 out of 3 listed markets were successfully removed just now:

Processing market 1.229481584 with 5 selections
Selection 45551105: 1. gibbys girl - Result: Loser
Selection 45032087: 2. drumdoit al - Result: Loser
Selection 67542912: 3. fire lucy - Result: Loser
Selection 69684984: 5. congress bell - Result: Winner
Selection 65710582: 6. signature lee - Result: Loser
Market 1.229481584 closed and added for removal
Processing market 1.229481588 with 6 selections
Selection 69913373: 1. lightfoot shine - Result: Loser
Selection 51585125: 2. sandwood ollie - Result: Loser
Selection 49201920: 3. jacobite - Result: Loser
Selection 36549672: 4. easy george - Result: Loser
Selection 56184392: 5. clonearls best - Result: Winner
Selection 67571254: 6. trigger in paris - Result: Loser
Market 1.229481588 closed and added for removal
Processing market 1.229481589 with 6 selections
Selection 69913373: 1. lightfoot shine - Result: Loser
Selection 51585125: 2. sandwood ollie - Result: Winner
Selection 49201920: 3. jacobite - Result: Loser
Selection 36549672: 4. easy george - Result: Loser
Selection 56184392: 5. clonearls best - Result: Winner
Selection 67571254: 6. trigger in paris - Result: Loser
Market 1.229481589 closed and added for removal
Removing markets: ['1.229481584', '1.229481588', '1.229481589']
Successfully removed markets: ['1.229481584', '1.229481588', '1.229481589']
Processing market 1.229481584 with 5 selections
Selection 45551105: 1. gibbys girl - Result: Loser
Selection 45032087: 2. drumdoit al - Result: Loser
Selection 67542912: 3. fire lucy - Result: Loser
Selection 69684984: 5. congress bell - Result: Winner
Selection 65710582: 6. signature lee - Result: Loser
Market 1.229481584 closed and added for removal
Removing markets: ['1.229481584']
Successfully removed markets: ['1.229481584']

So it would appear there's something different in marketId: 1.229481584, and others that are not cleanly removed

[Bet Angel]

When using streaming, when you remove a market it is just marked for removal rather than being removed immediately. That buffering is to prevent us having to constantly make new subscription requests to the betfair stream (which would annoy betfair and potentially stutter the price feed for the current markets).
From what I remember a new subscription request will be made if you add a new market, so at that point markets that have been marked for removal would go too. However, switching off streaming and switching it back on would probably force a resubscription too.

Edit: If the market is open in any window other than Guardian (spawned ladder, one-click, on the main screen, watch list etc) then that market would be deemed as still required and also not be removed.

We'll have a look at the code and retest some scenarios, perhaps we can filter these markets marked for removal from the response given by the API.

[sniffer66]

When using streaming, when you remove a market it is just marked for removal rather than being removed immediately. That buffering is to prevent us having to constantly make new subscription requests to the betfair stream (which would annoy betfair and potentially stutter the price feed for the current markets).
From what I remember a new subscription request will be made if you add a new market, so at that point markets that have been marked for removal would go too. However, switching off streaming and switching it back on would probably force a resubscription too.

We'll have a look at the code, perhaps we can filter these markets marked for removal from the response given by the API.

That would be great - thank you

EDIT: Just seen your edit BA,. I do have a watchlist open with all races for the day, but 99% of them do still get removed. I'll double check next time if I have the ladder open on a stuck market

[Bet Angel]

That would be great - thank you

EDIT: Just seen your edit BA,. I do have a watchlist open with all races for the day, but 99% of them do still get removed. I'll double check next time if I have the ladder open on a stuck market

Just to update on this. We've checked the code and the method used to subscribe/unsubscribe from the price stream will not be causing the issue you've seen as it's already been handled.

As mentioned before, the most likely explanation is that the market is still visible in some element of the UI and therefore still considered as being needed. It could even be as simple as a window showing a runner chart that's hidden behind other windows. It's not impossible that there's a bug and that occasionally the market isn't being released when usage has ended. We'll continue to experiment to try to recreate it, but if you find any patterns with regard to the market not releasing when used in a particular way, then please let us know.

Also, next time it happens and once the market in question has been Closed on betfair, perhaps you could try calling removeMarkets with this request string to see if that forces the market to go:

{"marketsFilter":{"filter":"ALL"},"marketStatus":"CLOSED"}

i.e. A call to ask Bet Angel to remove all Closed markets.
If you don't want to add that into your code, you could manually send the request using the API test page that's linked from Bet Angel Settings.

[sniffer66]

That would be great - thank you

EDIT: Just seen your edit BA,. I do have a watchlist open with all races for the day, but 99% of them do still get removed. I'll double check next time if I have the ladder open on a stuck market

Just to update on this. We've checked the code and the method used to subscribe/unsubscribe from the price stream will not be causing the issue you've seen as it's already been handled.

As mentioned before, the most likely explanation is that the market is still visible in some element of the UI and therefore still considered as being needed. It could even be as simple as a window showing a runner chart that's hidden behind other windows. It's not impossible that there's a bug and that occasionally the market isn't being released when usage has ended. We'll continue to experiment to try to recreate it, but if you find any patterns with regard to the market not releasing when used in a particular way, then please let us know.

Also, next time it happens and once the market in question has been Closed on betfair, perhaps you could try calling removeMarkets with this request string to see if that forces the market to go:

{"marketsFilter":{"filter":"ALL"},"marketStatus":"CLOSED"}

i.e. A call to ask Bet Angel to remove all Closed markets.
If you don't want to add that into your code, you could manually send the request using the API test page that's linked from Bet Angel Settings.

Cheers for checking BA. It's not happened since, but if it does I'll check and report back

[fuzz28]

Nice improvements. Does anyone know how to use stored values to override global settings for tick sizes etc.

[Bet Angel]

Nice improvements. Does anyone know how to use stored values to override global settings for tick sizes etc.

As per this screenshot, the offset number of ticks would be the value stored in the SV 'TICKS' at the time the initial bet is placed.
In this case the SV is expected to have been set at the market level (so one value for the whole market), but you can specify that the SVs are individual for each selection if you wish.

override_ticks.png

[Pogba]

Hi there,

There seems to be a bug when trying to set a marker on the Ladder using horizontal bars above and below. It seems to save the marker however it doesn't show on the ladder and if you go back in to edit it, it always seems to default back to Border as the Style.

Thanks

[Bet Angel]

There seems to be a bug when trying to set a marker on the Ladder using horizontal bars above and below. It seems to save the marker however it doesn't show on the ladder and if you go back in to edit it, it always seems to default back to Border as the Style.

Edit: removed previous message

We couldn't recreate it initially, but yes we've just seen the ladder settings editor revert a style change back to 'Border'.
That bug has probably been there quite a while, but we'll look to debug and fix it. It's a strange one as it doesn't seem to affect all of the marker Style choices.

[Bet Angel]

That bug has probably been there quite a while, but we'll look to debug and fix it. It's a strange one as it doesn't seem to affect all of the marker Style choices.

Now fixed in beta 3. Updated download links in the first post.