Author Topic: Form string parsing  (Read 2874 times)

Tags:
  • All members
  • Posts: 154
  • Gender: Male
Form string parsing
« on: 30 Nov 2014, 16:33 »
Hi Oxa,

I have 2 trigger conditions that (should) stop a bet being placed if either of the last 2 form string characters are 1 or 2.  I am using:

Selection's form does not contain [12]$ and
Selection's form does not contain [12]%$.

For a horse with form PF321 a bet has just been placed!  I would have expected both the above conditions to have returned FALSE but in this case it clearly didn't.

I will replace them meanwhile with 4 separate conditions (i.e. not using the [ ] syntax)

So am I doing something wrong?  8.0.0.10 is the version in use in live mode on horse racing.

thanks

Wez

  • Élite
  • Posts: 3698
  • Gender: Male
*
Re: Form string parsing
« Reply #1 on: 01 Dec 2014, 08:03 »
hi
your condition is looking for a seqence of 12,NOT 1 or 2.
you need this condition
and selections trigger expression silf_form_1 is not in list 1,2
and selections trigger expression silf_form_2 is not in list 1,2


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: 154
  • Gender: Male
Re: Form string parsing
« Reply #2 on: 01 Dec 2014, 10:20 »
Thanks McBee,

got it!

regards

Wez

  • Administrator
  • Posts: 8821
  • Gender: Female
*
Re: Form string parsing
« Reply #3 on: 01 Dec 2014, 11:17 »
Hi Wez,

You can do what mcbee suggested, but your notation is correct too. The [12] does really mean "either 1 or 2", not "12" (i.e. twelve).

I have just checked your trigger conditions against selections whose form I made equal to PF321. And in my case the conditions prevented the trigger from being executed.

Please check if it was "and" between the conditions and not "or". Please attach trigger logs if you'd like to investigate into it.
Always try your triggers in Test Mode before switching to real money!

Follow us on Twitter.

Join our WhatsApp chat!

Присоединяйтесь к официальному Telegram-каналу!

  • All members
  • Posts: 154
  • Gender: Male
Re: Form string parsing
« Reply #4 on: 01 Dec 2014, 15:01 »
Hi Oxa,

Okay I'll dig them out.  I'm pleased to read my original syntax was correct  ;D but it doesn't help explain what's going on.  I will send the trigger file and trigger logs via a PM.

Meanwhile, I did update the triggers as per McBee's suggestion and I've just caught that not working either - screenshot attached.  Clearly the end of the form string is a "1" and silk_form_1 not being in list 1,2 didn't stop the bet being placed either!

regards

Wez


  • All members
  • Posts: 154
  • Gender: Male
Re: Form string parsing
« Reply #5 on: 01 Dec 2014, 15:01 »
Sorry, missed off an attachment

  • All members
  • Posts: 154
  • Gender: Male
Re: Form string parsing
« Reply #6 on: 01 Dec 2014, 15:52 »
Hi Oxa,

triggers and logs attached as per PM just sent.

regards

Wez

  • Administrator
  • Posts: 8821
  • Gender: Female
*
Re: Form string parsing
« Reply #7 on: 02 Dec 2014, 14:13 »
Hi Wez,

In the particular market that you referred to above (the 14:40 Plump on the 1st of December), the trigger placed a bet correctly. What is indeed incorrect is the form variable displayed in the Engineer view. You covered this issue in another topic, so I won't comment it here. The important thing is that the Form of Maccabees was 4986-65, therefore it was not ending with either 1 or 2.

Please see the attached screenshot where that selection's form is displayed in a separate window. I used Time Machine to recreate this race.
Always try your triggers in Test Mode before switching to real money!

Follow us on Twitter.

Join our WhatsApp chat!

Присоединяйтесь к официальному Telegram-каналу!

  • All members
  • Posts: 154
  • Gender: Male
Re: Form string parsing
« Reply #8 on: 03 Dec 2014, 18:25 »
Hi Oxa.

I completely agree now I understand the display format issue of silk_form in Engineer mode and the User Variables viewer.

I've updated the Engineer Mode default field value to silk_form_4,silk_form_3,silk_form_2,silk_form_1 which does the job of showing the last 4 form characters.

Thanks for looking into what I initally thought was a trigger problem.  I'm now happy that my triggers are doing what I want.

regards

Wez

  • All members
  • Posts: 47
Re: Form string parsing
« Reply #9 on: 04 Dec 2014, 20:13 »
Overall a nice ending to you Wez. Glad to see this worked out for you.
Bots are lifesavers.

  • Administrator
  • Posts: 8821
  • Gender: Female
*
Re: Form string parsing
« Reply #10 on: 05 Dec 2014, 09:41 »
Hi Wez,

The new update should also resolve the variable viewing problem as well.
Always try your triggers in Test Mode before switching to real money!

Follow us on Twitter.

Join our WhatsApp chat!

Присоединяйтесь к официальному Telegram-каналу!

 

Please note, BetFair is seems to be currently OFFLINE