New beta version of Bet Angel v1.63.0 beta1

[jamesedwards]

On the unmatched bets page, is there any way to save the date sort so it always shows your latest unmatched bets at the top?

[tootall]

Looking at Dutching additions to new version, I can see the log details and an option to Log the Predicated calculations.

Can I get the generated calculation into a stored value.
I am trying to use it to see if dutch profit exceeds my threshold before placing bets.

[Bet Angel]

On the unmatched bets page, is there any way to save the date sort so it always shows your latest unmatched bets at the top?

Not at the moment, but we'll have a look to see how easy that is to add.

[Bet Angel]

Looking at Dutching additions to new version, I can see the log details and an option to Log the Predicated calculations.

Can I get the generated calculation into a stored value.
I am trying to use it to see if dutch profit exceeds my threshold before placing bets.

No, that can't be put into a stored value as stored values are assigned before a rule is executed and the parameters are too complicated in this case to embed them all in the Stored Value page rather than the rule itself.

I assume you must be using the Fixed Stake method rather than Target Profit (otherwise you'd already know the profit was correct), so to filter the trigger based on exceeding your required profit, you'll need to add the 'Dutching condition' to the rule.
In that condition, use the 'Book %' option, test if it is 'less than an entered amount', and enter the percentage you require.
e.g. If you are staking £100 and are looking to exceed £1.50 profit, the rough estimate is that you'd need the Book% to be less than 98.5%. Which leaves you 1.5% of stake as profit. (100.0% - 98.5% = 1.5% * £100 stake = £1.50 profit)
The precise maths is a bit more complicated than that, but that's close enough not to worry.

[tootall]

Looking at Dutching additions to new version, I can see the log details and an option to Log the Predicated calculations.

Can I get the generated calculation into a stored value.
I am trying to use it to see if dutch profit exceeds my threshold before placing bets.

No, that can't be put into a stored value as stored values are assigned before a rule is executed and the parameters are too complicated in this case to embed them all in the Stored Value page rather than the rule itself.

I assume you must be using the Fixed Stake method rather than Target Profit (otherwise you'd already know the profit was correct), so to filter the trigger based on exceeding your required profit, you'll need to add the 'Dutching condition' to the rule.
In that condition, use the 'Book %' option, test if it is 'less than an entered amount', and enter the percentage you require.
e.g. If you are staking £100 and are looking to exceed £1.50 profit, the rough estimate is that you'd need the Book% to be less than 98.5%. Which leaves you 1.5% of stake as profit. (100.0% - 98.5% = 1.5% * £100 stake = £1.50 profit)
The precise maths is a bit more complicated than that, but that's close enough not to worry.

Thanks for that, surprised it cant be written to a value that could be allocated a stored vale as it is written to the log.
I will have to continue using my old method of calculating dutch values.

[Bet Angel]

Looking at Dutching additions to new version, I can see the log details and an option to Log the Predicated calculations.

Can I get the generated calculation into a stored value.
I am trying to use it to see if dutch profit exceeds my threshold before placing bets.

No, that can't be put into a stored value as stored values are assigned before a rule is executed and the parameters are too complicated in this case to embed them all in the Stored Value page rather than the rule itself.

I assume you must be using the Fixed Stake method rather than Target Profit (otherwise you'd already know the profit was correct), so to filter the trigger based on exceeding your required profit, you'll need to add the 'Dutching condition' to the rule.
In that condition, use the 'Book %' option, test if it is 'less than an entered amount', and enter the percentage you require.
e.g. If you are staking £100 and are looking to exceed £1.50 profit, the rough estimate is that you'd need the Book% to be less than 98.5%. Which leaves you 1.5% of stake as profit. (100.0% - 98.5% = 1.5% * £100 stake = £1.50 profit)
The precise maths is a bit more complicated than that, but that's close enough not to worry.

Thanks for that, surprised it cant be written to a value that could be allocated a stored vale as it is written to the log.
I will have to continue using my old method of calculating dutch values.

No it can't be a stored value, but we'll add the Predicted Profit as an option for the Dutching condition to make the trigger filtering a bit easier than using Book%

[tryingtotrade]

Thanks team. Some good additions here.

Seems like we're never going to get customerStrategyRef & customerOrderRef are we.

What is that? Why important?

[ShaunWhite]

Thanks team. Some good additions here.

Seems like we're never going to get customerStrategyRef & customerOrderRef are we.

What is that? Why important?

It allows you to run multiple independent strategies on the same market and to more easily breakdown which bets came from which strategy. Otherwise figures such a number of (un)matched bets or PL are at overall account level.

It would also prevent BA Guardian from including bets you might have placed directly or using other software, and, allows you to use the ladder and automation at the same time without the bets becoming entangled.

[Bet Angel]

Thanks team. Some good additions here.

Seems like we're never going to get customerStrategyRef & customerOrderRef are we.

What is that? Why important?

It allows you to run multiple independent strategies on the same market and to more easily breakdown which bets came from which strategy. Otherwise figures such a number of (un)matched bets or PL are at overall account level.

It would also prevent BA Guardian from including bets you might have placed directly or using other software, and, allows you to use the ladder and automation at the same time without the bets becoming entangled.

Just to clarify, we've already ruled out doing that due to the massive complexity. See viewtopic.php?p=383066#p383066

But this was suggested as a compromise viewtopic.php?p=383105#p383105, which we will look into the feasibility of adding in a future version. So it would not be filtering the display & calculations of Bet Angel, but limited to tagging the bets for later external analysis.

[warnocksbumbag]

When using the Auto-keypress functionality I am coming up against an small issue.

Is there a way to differentiate between say, greyhound WIN markets and Horse Racing WIN markets when using the "apply automation to selected markets" keypress?

Example: I would like to bring in greyhound markets to Guardian, then apply an automation file to those markets, before changing the market filter to horses, importing those markets and then applying a different automation to those. Its all working well apart from the last step because they are both "WIN" markets and "MARKET TYPE" is the only way to add automation rules seemingly? Is it possible to add "EVENT TYPE" to the selection criteria. Or combine the ADD MARKETS and APPLY AUTOMATION commands together?

[jamesedwards]

When using the Auto-keypress functionality I am coming up against an small issue.

Is there a way to differentiate between say, greyhound WIN markets and Horse Racing WIN markets when using the "apply automation to selected markets" keypress?

Example: I would like to bring in greyhound markets to Guardian, then apply an automation file to those markets, before changing the market filter to horses, importing those markets and then applying a different automation to those. Its all working well apart from the last step because they are both "WIN" markets and "MARKET TYPE" is the only way to add automation rules seemingly? Is it possible to add "EVENT TYPE" to the selection criteria. Or combine the ADD MARKETS and APPLY AUTOMATION commands together?

If you were to use the coupon tab to load markets then you can choose to 'add selected markets only (select in Guardian)' which will add the markets and leave them selected.

Or, another way to achieve this differently is to combine your two rulesfiles into one, with the horse relevant ruleslines only triggering for horse racing and the greyhound relevant rules only against the greyhound markets. You could use something like jockey name to differentiate between the two.

[Dabbla]

When using the Auto-keypress functionality I am coming up against an small issue.

Is there a way to differentiate between say, greyhound WIN markets and Horse Racing WIN markets when using the "apply automation to selected markets" keypress?

Example: I would like to bring in greyhound markets to Guardian, then apply an automation file to those markets, before changing the market filter to horses, importing those markets and then applying a different automation to those. Its all working well apart from the last step because they are both "WIN" markets and "MARKET TYPE" is the only way to add automation rules seemingly? Is it possible to add "EVENT TYPE" to the selection criteria. Or combine the ADD MARKETS and APPLY AUTOMATION commands together?

If you were to use the coupon tab to load markets then you can choose to 'add selected markets only (select in Guardian)' which will add the markets and leave them selected.

Good tip, just been testing this with hotkeys.

Could this (select all added) execution be added to the market selections?

Could there be an option for coupon selections not to be added to a watch list? Watchlists just feel like a waste of resource.

[jamesedwards]

When using the Auto-keypress functionality I am coming up against an small issue.

Is there a way to differentiate between say, greyhound WIN markets and Horse Racing WIN markets when using the "apply automation to selected markets" keypress?

Example: I would like to bring in greyhound markets to Guardian, then apply an automation file to those markets, before changing the market filter to horses, importing those markets and then applying a different automation to those. Its all working well apart from the last step because they are both "WIN" markets and "MARKET TYPE" is the only way to add automation rules seemingly? Is it possible to add "EVENT TYPE" to the selection criteria. Or combine the ADD MARKETS and APPLY AUTOMATION commands together?

If you were to use the coupon tab to load markets then you can choose to 'add selected markets only (select in Guardian)' which will add the markets and leave them selected.

Good tip, just been testing this with hotkeys.

Could this (select all added) execution be added to the market selections?

Could there be an option for coupon selections not to be added to a watch list? Watchlists just feel like a waste of resource.

Easiest way will be if they are able to add a hotkey option to select markets using a stored value, as discussed earlier in this thread. This will solve many problems in one.

[Anbell]

When using the Auto-keypress functionality I am coming up against an small issue.

Is there a way to differentiate between say, greyhound WIN markets and Horse Racing WIN markets when using the "apply automation to selected markets" keypress?

Example: I would like to bring in greyhound markets to Guardian, then apply an automation file to those markets, before changing the market filter to horses, importing those markets and then applying a different automation to those. Its all working well apart from the last step because they are both "WIN" markets and "MARKET TYPE" is the only way to add automation rules seemingly? Is it possible to add "EVENT TYPE" to the selection criteria. Or combine the ADD MARKETS and APPLY AUTOMATION commands together?

Another option would be to load up the dogs at say 10am and the horses at 11am

[tryingtotrade]

If you run one instance of Betangel for Horse racing markets and one for Greyhound it will run better anyway as less markets in Guardian so better refresh times?