Author Topic: Previous "event_off" [TCKT08062013OF]  (Read 6258 times)

Tags:
  • Élite
  • Posts: 110
*
Previous "event_off" [TCKT08062013OF]
« on: 08 Jun 2013, 15:12 »
Hi,

The following scenario:

1.) I want to place bets on UK Horse Racing markets as close to the actual off as possible

2.) I want to integrate information about previous "event_off" (at same racetrack) into trigger.

If for example last race at Southwell was delayed for 8 minutes, I would assume a 8 minutes delay for next race as well.

What is the best way to access this information? The best would be if there was a variable pw_event_off_[racetrack]

But I assume I can get same functionality by using an user variable??

Cheers,
bamthwok


  • Moderator
  • Posts: 3597
*
Re: Previous "event_off"
« Reply #1 on: 08 Jun 2013, 17:43 »
Hi
Here is the first half:
(event_off-event_start)/mf_second
or
(event_off-event_start)/mf_minute

I think you will need a second variable to hold the course name
but a separate trigger for each course to set it
e.g.
trigger: set user variable
name: course
value: Catt
condition: markets name contains Catt

trigger: set user variable
name: course
value: Donc
condition: markets name contains Donc

etc.
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.

  • Élite
  • Posts: 110
*
Re: Previous "event_off" [TCKT08062013OF]
« Reply #2 on: 08 Jun 2013, 19:24 »
Hi Mark,

Thanks for your reply.

However, this part is clear to me. But the problem is that I need the variable value of the  previous market not of the current market.

How can I achieve that?

Cheers,
bamthwok

  • Élite
  • Posts: 3698
  • Gender: Male
*
Re: Previous "event_off" [TCKT08062013OF]
« Reply #3 on: 08 Jun 2013, 19:27 »
hi
you would need recording triggers for every racecourse about 87 uk and ire.
also do you realise that if this race is delayed for 5 mins due to a horse playing up, it means that the next race would have a recorded delay of 5 mins and most likely you would miss the start.
even though races are delayed, they always try and get the times back in line, so i think that this idea would miss more race starts than it is worth.
the idea sounds good, it would be perfect if we could get betfair to give a line up/entering stalls message.
for a variable to carry from one market to the next, you just use global

mcbee
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.

  • Élite
  • Posts: 110
*
Re: Previous "event_off" [TCKT08062013OF]
« Reply #4 on: 08 Jun 2013, 19:56 »
Hi,

Thanks McBee for your input.

I'm aware about the potential problem of using such kind of variable.

However, for certain strategies it might be better to miss a race race then to place a bet premature.

Anyway, just now I'm just trying to learn how to use user variables. I think I have the right idea now. Settings "global" will do the trick.

Cheers,
bamthwok

  • Moderator
  • Posts: 3597
*
Re: Previous "event_off" [TCKT08062013OF]
« Reply #5 on: 08 Jun 2013, 20:58 »
I need the variable value of the  previous market not of the current market.
At the end of your trigger, or once your betting triggers have executed you have a trigger action that will activate the block of triggers which will update the user variables for the current market.

At the start of the next market, you use the stored value of the previous market.
then activate the block of update triggers again to store the updated delay time ready for the next race.
etc...

but as mcbee points out, you will need a block of about 87 triggers - one for each course.
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.

  • Élite
  • Posts: 3698
  • Gender: Male
*
Re: Previous "event_off" [TCKT08062013OF]
« Reply #6 on: 08 Jun 2013, 21:13 »
hi
i have thought of another way.
each course is given a market id
and each new race is market id plus 2
so you could have the maximum number of courses on any day, maybe 15.
so you would only need 15 triggers, using mi with the market_id and another variable  td   to record the time.
then in your betting trigger you would have and market id is equal to mi
and trigger expression now_time is equal or greater than event start+td
but you would also need a betting trigger with 15 blocks or 15 betting triggers.


mcbee
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: 905
Re: Previous "event_off" [TCKT08062013OF]
« Reply #7 on: 09 Jun 2013, 10:41 »
Hi,

The following scenario:

1.) I want to place bets on UK Horse Racing markets as close to the actual off as possible


Why don't you just use SP, can't get closer to the start than that?

  • All members
  • Posts: 163
Re: Previous "event_off" [TCKT08062013OF]
« Reply #8 on: 09 Jun 2013, 12:14 »
I was about to suggest the same Rubold, that is what I ended up doing when the start time was causing me problems...

And as Mcbee pointed out, the first race in a metting might be delayed by 27minutes, the next race by 21, the next by 15 etc. as they attempt to claw the late start back. Also the delay might not occur until the 4th race anyway...

  • Élite
  • Posts: 110
*
Re: Previous "event_off" [TCKT08062013OF]
« Reply #9 on: 10 Jun 2013, 23:42 »
Hi Rubold, Demon,

Thanks for your comments.

I'm aware about potential problems and SP option, however, I just want to achieve to have previous "event off" (at same race course) stored in a variable.

Cheers,
bamthwok

  • Élite
  • Posts: 3698
  • Gender: Male
*
Re: Previous "event_off" [TCKT08062013OF]
« Reply #10 on: 11 Jun 2013, 11:11 »
hi bamthwok
i have put a set of triggers together for you to test and learn how to record and use the information in a betting trigger.
you can set the time before the start to bet in the constants, DO NOT ALTER ANY OTHER CONSTANT.
it is for 3 courses/meetings, so once you have learned what is what, then you can add extra constants and triggers to the amount of courses/meetings the you want to record each day.
there is one betting trigger with condition blocks that check for each course/meeting id and time delays, so again when you are ready, you can add new blocks for each extra course/meeting that you want.

please use test mode until you are happy with your settings 


mcbee

download the trigger below
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.

  • Élite
  • Posts: 110
*
Re: Previous "event_off" [TCKT08062013OF]
« Reply #11 on: 11 Jun 2013, 14:46 »
Hi McBee,

Thanks, that's very cool of you.

I will test your trigger examples as soon as I can and will comment about it.

Many thanks,

bamthwok

 

Please note, BetFair is seems to be currently OFFLINE