Hi,
I have a green up rule that greens out if the profit is >0 and then another one that kicks in later without this condition.
I am getting the two running - Is there a way I can not get the second one to run if that first has? I'm seeing occasions where I'm actually up a fair bit and then the second rule causes the amount to reduce.
I always assumed green up was a once-only affair - how do I ensure if successive green ups happen it's only if they give a higher return or lower loss?
thanks
Repeated Green-Ups
Just set the time of the green with profit one to expire a second or two before your second is armed -
Or you can set a signal with your profit > green up
Then on your timed green up add a 'Signal Set Condition' and specify its NOT set with a value
Or you can set a signal with your profit > green up
Then on your timed green up add a 'Signal Set Condition' and specify its NOT set with a value
-
- Posts: 46
- Joined: Sat Aug 05, 2017 11:33 am
Thanks Dallas
What about the second query about forcing green up to occur if there's a higher profit / reduced loss available?
Cheers
What about the second query about forcing green up to occur if there's a higher profit / reduced loss available?
Cheers
Once one of them has green up the amount wont change unless you trigger further betsjaipal2004 wrote: ↑Fri Sep 15, 2017 8:01 pmThanks Dallas
What about the second query about forcing green up to occur if there's a higher profit / reduced loss available?
Cheers
-
- Posts: 46
- Joined: Sat Aug 05, 2017 11:33 am
@Dallas - one thing I'm struggling with is I've seen some instances where my losses are not being greened up - the logs are sometimes next to useless
With the following bot:
I'm also getting instances where I get the error message about being unable to cancel bets..... doesn't seem clear why:
17/09/2017 15:45:45: Guardian has detected that the market is suspended
17/09/2017 15:45:46: Guardian has detected that the market is in-play
17/09/2017 15:45:46: Guardian has detected that the market is now unsuspended
17/09/2017 15:45:48: [G_Auto] : £ 2.00 Lay bet placed on Jim Rockford at 4.6. Fully matched at 4.3. Ref: 102855326037 ( Offsetting by 20 ticks with greening. )
17/09/2017 15:45:51: [G_Auto] : £ 1.30 Back bet placed on Jim Rockford at 6.6. Entirely unmatched when it initially reached the market. Ref: 102855332729
17/09/2017 15:46:06: [G_Auto] : Automation Signal for market: Greened1 = 1
17/09/2017 15:46:06: [G_Auto] : Cancelling bets 102855332729
17/09/2017 15:46:07: [G_Auto] : Automation Signal for market: Greened1 = 1
17/09/2017 15:46:08: [G_Auto] : Automation Signal for market: Greened1 = 1
17/09/2017 15:46:08: [G_Auto] : Placed closure bet with greening on Jim Rockford by Backing 1.72 at 5
17/09/2017 15:46:09: [G_Auto] : Automation Signal for market: Greened1 = 1
17/09/2017 15:46:09: [G_Auto] : Cancelling bets 102855377224
17/09/2017 15:46:09: [G_Auto] : Placed closure bet with greening on Jim Rockford by Backing 1.76 at 4.9
17/09/2017 15:46:10: [G_Auto] : Automation Signal for market: Greened1 = 1
17/09/2017 15:46:10: [G_Auto] : An error occurred while cancelling bets: The entire order has been rejected.
17/09/2017 15:46:10: [G_Auto] : Cancelling bets 102855379719
17/09/2017 15:46:10: [G_Auto] : Placed closure bet with greening on Jim Rockford by Backing 1.91 at 4.5
17/09/2017 15:46:11: [G_Auto] : Placed closure bet with greening on Jim Rockford by Backing 1.91 at 4.5
17/09/2017 15:46:12: [G_Auto] : Placed closure bet with greening on Jim Rockford by Backing 1.91 at 4.5
17/09/2017 15:46:52: Guardian has detected that the market is suspended
With the following bot:
I'm also getting instances where I get the error message about being unable to cancel bets..... doesn't seem clear why:
17/09/2017 15:45:45: Guardian has detected that the market is suspended
17/09/2017 15:45:46: Guardian has detected that the market is in-play
17/09/2017 15:45:46: Guardian has detected that the market is now unsuspended
17/09/2017 15:45:48: [G_Auto] : £ 2.00 Lay bet placed on Jim Rockford at 4.6. Fully matched at 4.3. Ref: 102855326037 ( Offsetting by 20 ticks with greening. )
17/09/2017 15:45:51: [G_Auto] : £ 1.30 Back bet placed on Jim Rockford at 6.6. Entirely unmatched when it initially reached the market. Ref: 102855332729
17/09/2017 15:46:06: [G_Auto] : Automation Signal for market: Greened1 = 1
17/09/2017 15:46:06: [G_Auto] : Cancelling bets 102855332729
17/09/2017 15:46:07: [G_Auto] : Automation Signal for market: Greened1 = 1
17/09/2017 15:46:08: [G_Auto] : Automation Signal for market: Greened1 = 1
17/09/2017 15:46:08: [G_Auto] : Placed closure bet with greening on Jim Rockford by Backing 1.72 at 5
17/09/2017 15:46:09: [G_Auto] : Automation Signal for market: Greened1 = 1
17/09/2017 15:46:09: [G_Auto] : Cancelling bets 102855377224
17/09/2017 15:46:09: [G_Auto] : Placed closure bet with greening on Jim Rockford by Backing 1.76 at 4.9
17/09/2017 15:46:10: [G_Auto] : Automation Signal for market: Greened1 = 1
17/09/2017 15:46:10: [G_Auto] : An error occurred while cancelling bets: The entire order has been rejected.
17/09/2017 15:46:10: [G_Auto] : Cancelling bets 102855379719
17/09/2017 15:46:10: [G_Auto] : Placed closure bet with greening on Jim Rockford by Backing 1.91 at 4.5
17/09/2017 15:46:11: [G_Auto] : Placed closure bet with greening on Jim Rockford by Backing 1.91 at 4.5
17/09/2017 15:46:12: [G_Auto] : Placed closure bet with greening on Jim Rockford by Backing 1.91 at 4.5
17/09/2017 15:46:52: Guardian has detected that the market is suspended
You do not have the required permissions to view the files attached to this post.
-
- Posts: 46
- Joined: Sat Aug 05, 2017 11:33 am
Thanks Dallas - what is the 'recommended' setting based on your experience?
With amounts below £2 you should be using at least a 3sec re-armjaipal2004 wrote: ↑Mon Sep 18, 2017 1:46 pmThanks Dallas - what is the 'recommended' setting based on your experience?
-
- Posts: 46
- Joined: Sat Aug 05, 2017 11:33 am
Why would stake size make a difference to re-arm?Dallas wrote: ↑Mon Sep 18, 2017 1:51 pmWith amounts below £2 you should be using at least a 3sec re-armjaipal2004 wrote: ↑Mon Sep 18, 2017 1:46 pmThanks Dallas - what is the 'recommended' setting based on your experience?
Thanks!
Submitting bets below the BF min £2 requires it to be done using two bets, so the in-play delay increases the time it takes for these bets to reach the marketjaipal2004 wrote: ↑Mon Sep 18, 2017 6:16 pmWhy would stake size make a difference to re-arm?Dallas wrote: ↑Mon Sep 18, 2017 1:51 pmWith amounts below £2 you should be using at least a 3sec re-armjaipal2004 wrote: ↑Mon Sep 18, 2017 1:46 pmThanks Dallas - what is the 'recommended' setting based on your experience?
Thanks!
-
- Posts: 46
- Joined: Sat Aug 05, 2017 11:33 am
Hi Dallas,
still can't make sense of logs on today's race below:
19/09/2017 14:25:18: Guardian has detected that the market is suspended
19/09/2017 14:25:18: Guardian has detected that the market is in-play
19/09/2017 14:25:18: Guardian has detected that the market is now unsuspended
19/09/2017 14:25:21: [G_Auto] : £ 2.00 Lay bet placed on Hazapour at 3.8. Fully matched at 3.8. Ref: 103011913924 ( Offsetting by 20 ticks with greening. )
19/09/2017 14:25:23: [G_Auto] : £ 1.36 Back bet placed on Hazapour at 5.6. Entirely unmatched when it initially reached the market. Ref: 103011918042
19/09/2017 14:27:11: Guardian has detected that the market is suspended
The rules all show as triggering at the same time (when they clearly shouldn't) and my loss didn't green up. I have also selected my signals are written to logs yet that's not happening either. I think the logs are flawed potentially because they should show everything going on.
My key worry is the lack of loss greening in this scenario - can't make sense of why
still can't make sense of logs on today's race below:
19/09/2017 14:25:18: Guardian has detected that the market is suspended
19/09/2017 14:25:18: Guardian has detected that the market is in-play
19/09/2017 14:25:18: Guardian has detected that the market is now unsuspended
19/09/2017 14:25:21: [G_Auto] : £ 2.00 Lay bet placed on Hazapour at 3.8. Fully matched at 3.8. Ref: 103011913924 ( Offsetting by 20 ticks with greening. )
19/09/2017 14:25:23: [G_Auto] : £ 1.36 Back bet placed on Hazapour at 5.6. Entirely unmatched when it initially reached the market. Ref: 103011918042
19/09/2017 14:27:11: Guardian has detected that the market is suspended
The rules all show as triggering at the same time (when they clearly shouldn't) and my loss didn't green up. I have also selected my signals are written to logs yet that's not happening either. I think the logs are flawed potentially because they should show everything going on.
My key worry is the lack of loss greening in this scenario - can't make sense of why
You do not have the required permissions to view the files attached to this post.
-
- Posts: 46
- Joined: Sat Aug 05, 2017 11:33 am
Puzzled why logs no longer show what they did - signal setting and cancelling / greening of bets
Also - is the race length condition robust? Could that be 'failing' ?
Look forward to your help
Also - is the race length condition robust? Could that be 'failing' ?
Look forward to your help
All the conditions and options within automation work perfectly fine, as i have said to you before when a market suspends all rules that have not triggered will show as 'triggered' at the time of suspension, therefore everything in your automation showing as last triggered 14:28:12 did not trigger.
-
- Posts: 46
- Joined: Sat Aug 05, 2017 11:33 am
Hi,
thanks for responding.
What would be causing this loss not to green-up:
19/09/2017 15:25:55: Guardian has detected that the market is suspended
19/09/2017 15:25:56: Guardian has detected that the market is in-play
19/09/2017 15:25:56: Guardian has detected that the market is now unsuspended
19/09/2017 15:25:58: [G_Auto] : £ 2.00 Lay bet placed on Kynren at 3.1. Entirely unmatched when it initially reached the market. Ref: 103018952932 ( Offsetting by 30 ticks with greening. )
19/09/2017 15:26:00: [G_Auto] : £ 1.19 Back bet placed on Kynren at 5.2. Entirely unmatched when it initially reached the market. Ref: 103018957256
19/09/2017 15:27:34: Guardian has detected that the market is suspended
15:25:56 the race went in-in play (1m) and that would've caused the 6 - 16f stop rule to trigger assuming that the previous (non-stop) didn't at about 15:27:02 - therefore plenty of time for the loss to be greened up. However, it didn't trigger and I'm at a loss as to why - it has the following conditions:
The previous rule sets the signal Greened2 to '1' and that didn't run so this should've.
Might just be me
Thanks agian
thanks for responding.
What would be causing this loss not to green-up:
19/09/2017 15:25:55: Guardian has detected that the market is suspended
19/09/2017 15:25:56: Guardian has detected that the market is in-play
19/09/2017 15:25:56: Guardian has detected that the market is now unsuspended
19/09/2017 15:25:58: [G_Auto] : £ 2.00 Lay bet placed on Kynren at 3.1. Entirely unmatched when it initially reached the market. Ref: 103018952932 ( Offsetting by 30 ticks with greening. )
19/09/2017 15:26:00: [G_Auto] : £ 1.19 Back bet placed on Kynren at 5.2. Entirely unmatched when it initially reached the market. Ref: 103018957256
19/09/2017 15:27:34: Guardian has detected that the market is suspended
15:25:56 the race went in-in play (1m) and that would've caused the 6 - 16f stop rule to trigger assuming that the previous (non-stop) didn't at about 15:27:02 - therefore plenty of time for the loss to be greened up. However, it didn't trigger and I'm at a loss as to why - it has the following conditions:
The previous rule sets the signal Greened2 to '1' and that didn't run so this should've.
Might just be me
Thanks agian
You do not have the required permissions to view the files attached to this post.
-
- Posts: 46
- Joined: Sat Aug 05, 2017 11:33 am
Hi again....
same thing happened on the 17:10 (1m4f handicap):
19/09/2017 17:11:02: Guardian has detected that the market is suspended
19/09/2017 17:11:03: Guardian has detected that the market is in-play
19/09/2017 17:11:03: Guardian has detected that the market is now unsuspended
19/09/2017 17:11:05: [G_Auto] : £ 2.00 Lay bet placed on Get Out of Jail at 8. £ 1 matched at 8 £ 1 unmatched when it initially reached the market. Ref: 103030297274 ( Offsetting by 30 ticks with greening. )
19/09/2017 17:11:06: [G_Auto] : £ 0.80 Back bet placed on Get Out of Jail at 20. Entirely unmatched when it initially reached the market. Ref: 103030298981
19/09/2017 17:13:56: Guardian has detected that the market is suspended
Had a loss of £14.00 and no greening - same bot with rules as above .... why isn't the greening triggering?
The rule that should kick in is obviously for 12f:
Help (hopefully for the final time) would be appreciated!
thanks all
same thing happened on the 17:10 (1m4f handicap):
19/09/2017 17:11:02: Guardian has detected that the market is suspended
19/09/2017 17:11:03: Guardian has detected that the market is in-play
19/09/2017 17:11:03: Guardian has detected that the market is now unsuspended
19/09/2017 17:11:05: [G_Auto] : £ 2.00 Lay bet placed on Get Out of Jail at 8. £ 1 matched at 8 £ 1 unmatched when it initially reached the market. Ref: 103030297274 ( Offsetting by 30 ticks with greening. )
19/09/2017 17:11:06: [G_Auto] : £ 0.80 Back bet placed on Get Out of Jail at 20. Entirely unmatched when it initially reached the market. Ref: 103030298981
19/09/2017 17:13:56: Guardian has detected that the market is suspended
Had a loss of £14.00 and no greening - same bot with rules as above .... why isn't the greening triggering?
The rule that should kick in is obviously for 12f:
Help (hopefully for the final time) would be appreciated!
thanks all
You do not have the required permissions to view the files attached to this post.