Suggestions : Time since bet placed

Help improve Bet Angel.
Post Reply
User avatar
gazuty
Posts: 1559
Joined: Sun Jun 26, 2011 11:03 am

Mon Jun 01, 2020 12:36 am

Looking in Gaurdian to apply a condition such as "time since bet placed in market" condition.

There is a condition based on time since market contained a fill or kill bet. I guess I could increment a stored value etc at the time of bet placement and then use a condition based of time since stored value changed - but was hoping for a direct cut through.

User avatar
rik
Posts: 905
Joined: Sat Jan 25, 2014 5:16 am
Location: London

Mon Jun 01, 2020 12:43 am

+1

User avatar
ShaunWhite
Posts: 5969
Joined: Sat Sep 03, 2016 3:42 am

Mon Jun 01, 2020 2:57 am

gazuty wrote:
Mon Jun 01, 2020 12:36 am
Looking in Gaurdian to apply a condition such as "time since bet placed in market" condition.

There is a condition based on time since market contained a fill or kill bet. I guess I could increment a stored value etc at the time of bet placement and then use a condition based of time since stored value changed - but was hoping for a direct cut through.
How about setting an SV to 1 when the bet is placed, and then have a rule that increments that SV every second if it's >0.
Basically having a timer that only increments once it's been nudged up from 0 to 1 by an action.

User avatar
gazuty
Posts: 1559
Joined: Sun Jun 26, 2011 11:03 am

Mon Jun 01, 2020 4:52 am

ShaunWhite wrote:
Mon Jun 01, 2020 2:57 am
gazuty wrote:
Mon Jun 01, 2020 12:36 am
Looking in Gaurdian to apply a condition such as "time since bet placed in market" condition.

There is a condition based on time since market contained a fill or kill bet. I guess I could increment a stored value etc at the time of bet placement and then use a condition based of time since stored value changed - but was hoping for a direct cut through.
How about setting an SV to 1 when the bet is placed, and then have a rule that increments that SV every second if it's >0.
Basically having a timer that only increments once it's been nudged up from 0 to 1 by an action.
Thanks good suggestion, and I think that can work for sure.

Editing.

So thinking about it further, I guess I would use signals. I would increment the signal each time a rule that places a bet is triggered. I would then use the "Signal Changed Condition" and use my time in the seconds between part of that condition.

But I am still hoping for Guardian to be developed in the future to have a condition for "time since bet placed in market" as this is a much simpler way rather than incrementing signals and having another rule based of the changed signal.

User avatar
ShaunWhite
Posts: 5969
Joined: Sat Sep 03, 2016 3:42 am

Mon Jun 01, 2020 6:09 am

gazuty wrote:
Mon Jun 01, 2020 4:52 am
Editing.

So thinking about it further, I guess I would use signals. I would increment the signal each time a rule that places a bet is triggered. I would then use the "Signal Changed Condition" and use my time in the seconds between part of that condition.

But I am still hoping for Guardian to be developed in the future to have a condition for "time since bet placed in market" as this is a much simpler way rather than incrementing signals and having another rule based of the changed signal.
I'll take you word for it, I don't use Guardian. It was just a hunch based on when I've read.

sa7med
Posts: 768
Joined: Thu May 18, 2017 8:01 am

Mon Jun 01, 2020 6:25 am

gazuty wrote:
Mon Jun 01, 2020 12:36 am
Looking in Gaurdian to apply a condition such as "time since bet placed in market" condition.

There is a condition based on time since market contained a fill or kill bet. I guess I could increment a stored value etc at the time of bet placement and then use a condition based of time since stored value changed - but was hoping for a direct cut through.
Not sure if this works for you but you could look into unmatched time condition as well

sniffer66
Posts: 347
Joined: Thu May 02, 2019 8:37 am

Mon Jun 01, 2020 7:12 am

I've found the simplest way to do any time based conditions are to use a Signal Changed Condition

Set a signal when you place the bet, then in your following condition use the above with a time between x and y when signal changed.

It also ties it to a specific action, so you can have multiple signals with different time conditions if required. As opposed to time since a bet was placed, when that could be any bet

Edit: just seen you've come to that conclusion. I shouldnt post before my first coffee :)

Post Reply

Return to “Suggestions”

  • Information
  • Who is online

    Users browsing this forum: No registered users and 1 guest