Gradual Dribble Greenup

[thelearner]

Currently I place bets and lays prior to a race and use "green all selection" automation trigger before off.

Very bread and butter stuff.

However I want to do a better job as when I green all selections it might have to go over many different ticks as there is not enough volume.

Obviously I can run a lay trigger say ever 10 seconds combined with say lay 10% net stake, to slowly get the money out, likewise with bet trigger, however if accidentaly the horse was actually a lay or vice-versa, using the above code, I presume I could get myself in big trouble.

So is there a way of implement in automation basically a partial green up say 10% on all horses in a race, each time it is run, with horses with large lays or a large bets on them.

[thelearner]

It seems betangel protects you, is this right?

Net Stake is always positive but Net Stake percentage is negative if you have a lay on a horse?

So I have £100 bet at 5.0 and my trigger rule tried to bet 10% of Net Stake it seems to fail.
If I have £100 bet at 5.0 and my trigger rule tried to lay 10% of Net Stake it seems to be fine.

Similar if the trigger tried to Lay

[Derek27]

Are you closing a trade and then greening up or are you greening an open trade?

If it's the former then your profit is just a small fraction of your trade so a few ticks shouldn't matter. If it's the latter it's a question of choosing you're price and what percentage of your profit you want to close.

It's only possible to accidently place a bet with the wrong polarity when manual trading. If you use the greenup rule, BA will automatically back or lay as needed. If you're using your own algorithm to close, just test it in practice mode before going live.

[thelearner]

place_lay_bet.PNG

I am drip laying a back bet instead of a full greenup on the selection.

However betangel on testing seems to deal with net stake percentage differently to net stake assigned to a stored variable (which is always a positive value lay or bet) , just confirming this.

So if I accidentally prior to runnning the trigger placed a lay bet in the market betangel will not keep on laying on that horse, and the vice-versa situation.

[Dallas]

It seems betangel protects you, is this right?

Net Stake is always positive but Net Stake percentage is negative if you have a lay on a horse?

So I have £100 bet at 5.0 and my trigger rule tried to bet 10% of Net Stake it seems to fail.
If I have £100 bet at 5.0 and my trigger rule tried to lay 10% of Net Stake it seems to be fine.

Similar if the trigger tried to Lay

If you use a file/servant with both a back and lay bet rule only one of the two will trigger depending which side you've opened with

I use this servant to reduce my NET stake by 25% each time I run it (doesn't matter if i've backed or layed first)

Reduce Liability.baf

[thelearner]

Thank you Dallas, but can anyone answer my original question.

Will bet and lay in automation using a netstake percentage logic always protect you, in that if you already have a huge lay and run the lay trigger or a huge bet and run the bet trigger it will not activate.

[Dallas]

Thank you Dallas, but can anyone answer my original question.

Will bet and lay in automation using a netstake percentage logic always protect you, in that if you already have a huge lay and run the lay trigger or a huge bet and run the bet trigger it will not activate.

That was answered in the first line of my reply above
In short - yes

[thelearner]

Cheers, so my method is fine, I could not load your trigger into 1.60.

[Dallas]

Cheers, so my method is fine, I could not load your trigger into 1.60.

Assuming it contains a back and lay rule always armed and will trigger once (ie, as soon as you start the servant)

You'll need to use the latest V1.61 to use the file I uploaded above, although it was made in an earlier version it's one of my own files so I removed parts and re-saved it to give you just what you asked for
viewtopic.php?f=46&t=27763

[thelearner]

Just updated to the beta version of betangel and downloaded the trigger and yep exactly the same as what i do.

Thanks again