New beta version of Bet Angel v1.61.0 - Now on general release

[Bet Angel]

"'The Predicted Goals for the Match' data item has been added. Note: requires the match's Correct Score market to be added to Guardian"
I'm curious about this one. How is this being calculated ?

Can't go into specific details, but it's derived from the pricing of the correct score market before the start of the match.

[sniffer66]

"'The Predicted Goals for the Match' data item has been added. Note: requires the match's Correct Score market to be added to Guardian"
I'm curious about this one. How is this being calculated ?

Can't go into specific details, but it's derived from the pricing of the correct score market before the start of the match.

Thanks BA. I've been using Poisson for a while to look at predicted goals, so will see how this compares

[ShaunWhite]

"'The Predicted Goals for the Match' data item has been added. Note: requires the match's Correct Score market to be added to Guardian"
I'm curious about this one. How is this being calculated ?

Can't go into specific details,

Is it an integer? Or could it be 1.6 vs 2.3 etc

Does it change as the gane progresses?

Maybe you can say if its only derived just from the CS market? Or why it might not be the shortest CS which on the surface could be seen as the predicted score?

[Bet Angel]

Is it an integer? Or could it be 1.6 vs 2.3 etc

Does it change as the gane progresses?

Decimal value based on the prices before the match starts - not recalculated during the match.

[sniffer66]

Is it an integer? Or could it be 1.6 vs 2.3 etc

Does it change as the gane progresses?

Decimal value based on the prices before the match starts - not recalculated during the match.

Was just about to post results of a test. With the 1st watch list header row containing the decimal (2.23****)

Capture.JPG

Given I only applied that test after the match started (but had the CS market loaded pre KO) does BA only calculate that value if the CS market IS loaded pre off ?

[decomez6]

Make market above _below VWAP.baf

store the number of unmatched bets when the price is above OR below the VWAP /( 2 seperate files)

-then use the stored value to run the bot , only when the number of unmatched for the selection is equal to the above , even when the condition is no longer met.

- aim is to make market above and below vwap with a bias towards the direction of the flow.

Problem :
the number of unmatched bets being stored even when the conditions are not being met , causing the bot to fire constantly.

could it be the version or is just me and my version of cock-ups

-

[Bet Angel]

Given I only applied that test after the match started (but had the CS market loaded pre KO) does BA only calculate that value if the CS market IS loaded pre off ?

Yes, otherwise it'll log an error message

[Bet Angel]

Problem :
the number of unmatched bets being stored even when the conditions are not being met , causing the bot to fire constantly.

Based on your conditions you are going to either set the 'unmatched backs above vwap' or the 'unmatched lays below vwap' Stored Value, as at any time the VWAP is likely to be either above or below the LTP. So one of those gets set to zero when there aren't any unmatched bets. Your bet triggers because 0 = 0 in one of the later conditions.

So from what I can see, the rules are doing what you've asked.

I'm not quite sure what you are trying to set in 'unmatched backs above vwap', but currently you are setting it with the total number of unmatched back bets. Perhaps you actually wanted to use 'The number of unmatched bets on the selection above a price' option when setting the stored value?

[decomez6]

Problem :
the number of unmatched bets being stored even when the conditions are not being met , causing the bot to fire constantly.

Based on your conditions you are going to either set the 'unmatched backs above vwap' or the 'unmatched lays below vwap' Stored Value, as at any time the VWAP is likely to be either above or below the LTP. So one of those gets set to zero when there aren't any unmatched bets. Your bet triggers because 0 = 0 in one of the later conditions.

So from what I can see, the rules are doing what you've asked.

yes, to have them trigger when 0=0 or at any time X=X was intentional.

prevent further triggers whenever X is not equal X ... essentially only allowing one bet through until the balance met( net stake 0) hence making market.
.....just wondering how a file with conditions will return the same outcome as one with no conditions..

much thanks , will look into it.

[chluke]

Looks good!!!

Some ideas )

Automation - Stored Values
- Easily check for blank values. E.g. form data . Currently using form = # #, and then another "text contains" check
- "Replace with". e.g. form = " 234x-q0". Extract last 8 chars and convert text to numbers & 1) Replace 0 with 10. 2) Replace x & - with 1. 3) Replace all others including blanks with 20.

[decomez6]

I'm not quite sure what you are trying to set in 'unmatched backs above vwap', but currently you are setting it with the total number of unmatched back bets. Perhaps you actually wanted to use 'The number of unmatched bets on the selection above a price' option when setting the stored value?

Make market above _below VWAP (correct).baf

correct , working as intended.
thanks again.

[ilovepizza82]

Nice but how can i send a request to get info about specific runner's odds ?
Say the dog's name is "Scooby" and I would like to know:
- 3 best back odds and
- 3 best lay odds.
- and how much money each odds currently have eg. @3.25 £33, @3.3 £64, @3.35 £45 (is it even possible with this release?)

Wish there were more examples in the api guide.

[Bet Angel]

Nice but how can i send a request to get info about specific runner's odds ?
Say the dog's name is "Scooby" and I would like to know:
- 3 best back odds and
- 3 best lay odds.
- and how much money each odds currently have eg. @3.25 £33, @3.3 £64, @3.35 £45 (is it even possible with this release?)

Wish there were more examples in the api guide.

The best way to see the capabilities in action is to use the HTML / Javascript test page linked from the Settings window. You can manually edit the Raw Request for a chosen API Test if you want to experiment.

If you call

Code: Select all

http://localhost:9000/api/markets/v1.0/getMarketPrices

with

Code: Select all

{"dataRequired":["BEST_THREE_PRICES"]}

as the request you'll get the best three back and lay prices with size of money available for each selection.

If you want to make that specific to a single market you'd add the market Id as a filter so the request would be something like

Code: Select all

{"marketsFilter":{"filter":"SPECIFIED_IDS","ids":["1.216466957"]},"dataRequired":["BEST_THREE_PRICES"]}

[xtrader16]

These new upgrades look amazing...LOL.. looking forward to using them....

[Bet Angel]

You can have multiple stored values in a single rule and they are processed in order, so you can chain calculations together.
So first use stored values to convert the price to ticks and store as a name, so for instance you may have two prices stored as TickA and TickB.
Then have another Stored Value that calculates the difference by having a row that sets the Stored Value ‘Diff’ to be ‘TickB’ minus ‘TickA’