Author Topic: delay bet  (Read 16098 times)

Tags:
  • All members
  • Posts: 829
delay bet
« on: 02 Oct 2014, 12:25 »
Hi,
I would like to prevent a trigger firing at the same time as another one.
In fact I'd prefer it to fire a few seconds later to enable a greenup trigger to fire
if conditions are right. Is a 'condition' required ?
I am using Time Machine and I am aware there is a bet placing delay option in settings/test bets, however I prefer not to use that function.
Thanks
R
My grandma taught me not to run downstairs and never back odds on.

  • All members
  • Posts: 405
Re: delay bet
« Reply #1 on: 02 Oct 2014, 15:03 »
How about adding a condition that says:
"Trigger xxxxx number of runs is greater than 0"
It should give a small delay, or at least stop the other trigger firing until the other has already executed.

  • Moderator
  • Posts: 3597
*
Re: delay bet
« Reply #2 on: 02 Oct 2014, 17:57 »
Hi
If you want to delay a specific amount of time:

Add a constant to your trigger file and call it dts (delay time in seconds) and set the value to the number of seconds delay you want.

Add a second action to your betting trigger:
set user variable
name: timer
value: now_time
individually for each market

Then add the following conditions to the trigger you want to delay:
and trigger <betting trigger name> number of runs per selection is greater than 0
and selections trigger expression (now_time - timer)/mf_second is equal or greater than dts

Please read the following disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

  • All members
  • Posts: 829
Re: delay bet
« Reply #3 on: 02 Oct 2014, 21:09 »
hi armarni,
Thanks for your suggestion, I am looking at this along with Mark's input.
Cheers
R
My grandma taught me not to run downstairs and never back odds on.

  • All members
  • Posts: 829
Re: delay bet
« Reply #4 on: 02 Oct 2014, 21:26 »
Hi Mark,

Thanks for the conditions, I'll test them the next couple of days and come back to you
Cheers
R
My grandma taught me not to run downstairs and never back odds on.

  • All members
  • Posts: 829
Re: delay bet
« Reply #5 on: 03 Oct 2014, 09:34 »
Hi Mark,

Not having any luck with the trigger firing.
Just to confirm here are the settings:
set user variable
name  timer  value  time_now  individually for each market
conditions:
and selection's trigger expression (now_time-timer)/mf_second is equal or greater than dts
(dts setting in constant tried at  8  2  and .1)
The log report.
Condition is: FALSE.
10:05:35       Checking condition and Selection's Trigger Expression (now_time-timer)/mf_second is equal or greater than dts.

One thing I don't understand is putting the condition
and trigger xxxx number of runs is greater than 0
If I place that condition in the same trigger it won't fire. Have I misunderstood?
I want to delay the bets as the triggers fire altogether.
I have 3 back triggers and for easier explanation let's call them Back1 Back2 and Back3
The log time show firing times as follows
7.0.2  Back1
7.0.2  Back2
7.0.2  Back3
Thanks
R
My grandma taught me not to run downstairs and never back odds on.

  • All members
  • Posts: 405
Re: delay bet
« Reply #6 on: 03 Oct 2014, 11:50 »
marks approach is a far more sophisticated approach than my suggestion.  Mine would require each trigger to be in its own block, but it would only ensure that a trigger would fire after another one had executed already in that market, where as Marks more elegant solution allows you to specify a time delay.

  • All members
  • Posts: 829
Re: delay bet
« Reply #7 on: 03 Oct 2014, 13:14 »
hi armarni,
I am testing both out today. Yours is one that I have used before and a timely reminder (no pun intended!) and thanks for that.
will get back to you soon
Cheers
R
My grandma taught me not to run downstairs and never back odds on.

  • Moderator
  • Posts: 3597
*
Re: delay bet
« Reply #8 on: 03 Oct 2014, 17:35 »
Just to confirm here are the settings:
set user variable
name  timer  value  time_now  individually for each market
Hi
value should be: now_time

The idea is the same as in this example trigger.
http://marketfeeder.co.uk/solutions/miscelaneous-betting/waiting-after-trigger/
Please read the following disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

  • All members
  • Posts: 829
Re: delay bet
« Reply #9 on: 03 Oct 2014, 23:22 »
Hi Mark,
Thanks for the example trigger.
I am assuming we are talking about only one trigger.
The sample trigger appears confusing with the and/or option. It doesn't make sense that if the condition 'and trigger xxxx number of runs is greater than 0' is met then the trigger will fire and take no notice of the 'or' option being the waiting condition.
Your example makes more sense in that there are two 'and' conditions that means they both must be met.
However I still get the false log and trigger won't fire.
I must be missing something or maybe two triggers are involved
Please advise Thanks
R
My grandma taught me not to run downstairs and never back odds on.

  • Moderator
  • Posts: 3597
*
Re: delay bet
« Reply #10 on: 04 Oct 2014, 06:50 »
Hi
In the example trigger, it is the block named "Executing one trigger after another" which is the one I am suggesting for you. This block is disabled when you download it.

Regarding your question about the second block (enabled as you download it and not the trigger I had in mind for you):
The trigger repeats every 0.3 secs
however, on the first run the timer is not set, therefore:
trigger cancel then lay number of runs is equal to 0 lets the trigger execute first run because the timer variable is not set.
or selections trigger expression (now_time-timer).... the timer variable is set and therefore the timer works correctly on this condition on all subsequent repetitions.

In order to see why what was suggested is not working in your trigger, I need to see your trigger file, or just the basic mechanics of it.     
Please read the following disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

  • All members
  • Posts: 829
Re: delay bet
« Reply #11 on: 04 Oct 2014, 07:27 »


Hi Mark,
Still a bit confusing if I may say so. I read the above as you are suggesting the first block but have the second block in mind for me ??

Maybe I'll just outline my triggers.
The basic triggers are as follows
Trigger names, Back, Fav, 2Fav
Back
It has simple conditions like gap etc.
2Fav
similar conditions
Fav
similar conditions
I want the Fav trigger to fire x seconds after the 2Fav fires.
OR the Back trigger fires
Thanks for your continued patience Mark
R
ps.... How can I copy and paste comments to make them appear the proper way?
My grandma taught me not to run downstairs and never back odds on.

  • All members
  • Posts: 829
Re: delay bet
« Reply #12 on: 04 Oct 2014, 07:50 »
In the example trigger, it is the block named "Executing one trigger after another" which is the one I am suggesting for you. This block is disabled when you download it.

Regarding your question about the second block (enabled as you download it and not the trigger I had in mind for you):

Hi Mark,
Still a bit confusing if I may say so. I read the above as you are suggesting the first block but have the second block in mind for me ??

Maybe I'll just outline my triggers.
The basic triggers are as follows
Trigger names, Back, Fav, 2Fav
Back
It has simple conditions like gap etc.
2Fav
similar conditions
Fav
similar conditions
I want the Fav trigger to fire x seconds after the 2Fav fires.
OR      the Fav trigger to fire x seconds after the Back fires.
Thanks for your continued patience Mark
R
ps.... How can I copy and paste comments to make them appear the proper way?

My grandma taught me not to run downstairs and never back odds on.

  • Moderator
  • Posts: 3597
*
Re: delay bet
« Reply #13 on: 04 Oct 2014, 14:01 »
Hi
Either use the Quote link to repy, or Reply and use the Insert Quote button.

The attached trigger file will fire the Fav trigger 5 seconds after either the Back trigger fired, or the 2Fav trigger fired. Screenshot shows the bets, timing, and trigger sequence.

Basically you set the variable "timer" when the first bet is made, and the two conditions in the second trigger ensure the timer has been set (first trigger has run), and the delay is for the required amount of time. "timer2" is required for the OR condition block where you specify:
(Insert Quote button)
Quote
I want the Fav trigger to fire x seconds after the 2Fav fires.
OR      the Fav trigger to fire x seconds after the Back fires.
Please read the following disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

  • All members
  • Posts: 829
Re: delay bet
« Reply #14 on: 04 Oct 2014, 15:50 »
Hi Mark,

A BIG THANK YOU as it seems to be working quite well.
One small problem though is I had to set 'dts' to 120 to get 8 seconds wait time.
I'm not sure how that happens but most of the logs show 8 seconds which is about what I require.
Perhaps a possible explanation is that the Time Machine runs at 15 times that of real time
and 120 divided by 15 = 8  wala !!  Could that be the answer ?
I'll keep testing and report back
thanks
R
My grandma taught me not to run downstairs and never back odds on.

 

Please note, BetFair is seems to be currently OFFLINE