Planning: PFA OOP NOT CBet XF Stat

Forum for users that want to write their own custom queries against the PT database either via the Structured Query Language (SQL) or using the PT3 custom stats/reports interface.

Moderator: Moderators

Planning: PFA OOP NOT CBet XF Stat

Postby js2002 » Sun Oct 18, 2009 1:00 pm

Hi,

a NL buddy of mine asked me to build a stat that show what villians plan/strategy is when he misses his own CBet oop and this means giving up -> XF

(position > pfa position) AND
<psydocode: line>preflop "%R" AND
NOT(CBet Flop) AND
<psydocode: line>flop "XF"

1.
I miss sth here: f.e. The IP guy doenst float the flop and so it comes to the TURN. XF would catch that.
What is the easiest way to catch all that?
Maybe sth like: ...OR (face turn bet AND fold turn) OR (face river bet and fold river) ?

2. NOT(Cbet flop) could be redundant here, correct?

EDIT: a true OR exp would make the whole exp true but this I did not want. I I have to repeat the 4 lines frome above into the brackes?

like this:

(position > pfa position) AND
<psydocode: line>preflop "%R" AND
NOT(CBet Flop) AND
<psydocode: line>flop "XF"

OR (
(position > pfa position) AND
<psydocode: line>preflop "%R" AND
NOT(CBet Flop) AND
<psydocode: line>flop "XF"

face turn bet AND fold turn)
OR (
(position > pfa position) AND
<psydocode: line>preflop "%R" AND
NOT(CBet Flop) AND
<psydocode: line>flop "XF"

face river bet AND fold river)

Do I really need such a big exp?

I see, THIS should be smaller and correct
(position > pfa position) AND
<psydocode: line>preflop "%R" AND
NOT(CBet Flop) AND (

<psydocode: line>flop "XF"
OR
(face turn bet AND fold turn)
OR
(face river bet AND fold river)
)
js2002
 
Posts: 1502
Joined: Fri Feb 15, 2008 5:44 am
Location: Germany

Re: Planning: PFA OOP NOT CBet XF Stat

Postby WhiteRider » Sun Oct 18, 2009 1:25 pm

Your pseudo code looks pretty good, but you may include some cases where the player faces a donk bet on the flop. "NOT CBet" just says the player didn't CBet, it doesn't mean they had a chance to CBet. Flop 'XF' would imply that, but since you OR that with the other cases then the player could be facing a flop bet and call or raise, then face a turn bet and fold.
You probably want to include a test for flop CBbet opp or 'check flop'.
WhiteRider
Moderator
 
Posts: 54025
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Planning: PFA OOP NOT CBet XF Stat

Postby js2002 » Sun Oct 18, 2009 1:33 pm

(position > pfa position) AND
<psydocode: line>preflop "%R" AND
NOT(CBet Flop) AND
<psydocode: line>flop "X%" AND (

<psydocode: line>flop "XF"
OR
(face turn bet AND fold turn)
OR
(face river bet AND fold river)

I added the bold part.
But if (position > pfa position) == true the Player always had the chance to Cbet flop because he is oop. (or do i miss anything?!?!?!)
js2002
 
Posts: 1502
Joined: Fri Feb 15, 2008 5:44 am
Location: Germany

Re: Planning: PFA OOP NOT CBet XF Stat

Postby WhiteRider » Sun Oct 18, 2009 2:23 pm

js2002 wrote:(position > pfa position) AND
<psydocode: line>preflop "%R" AND
NOT(CBet Flop) AND
<psydocode: line>flop "X%" AND (

<psydocode: line>flop "XF"
OR
(face turn bet AND fold turn)
OR
(face river bet AND fold river)

I added the bold part.
But if (position > pfa position) == true the Player always had the chance to Cbet flop because he is oop. (or do i miss anything?!?!?!)

If the player is the preflop raiser then the pfa position is no relevant (PFA pos will either be -1 if the player was the only raiser, or will be the position of the last other player to raise).

Using LIKE 'X%' should be fine because that means that they had chance to bet (but chose to check).
WhiteRider
Moderator
 
Posts: 54025
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Planning: PFA OOP NOT CBet XF Stat

Postby js2002 » Sun Oct 18, 2009 9:37 pm

so tell me then: How do i check for "was he OOP?" ?

I thought the check "(position > pfa position) " gives me TRUE when the PFA is OOP.
f.e. Hero raise, Idiotdonk reraise
posi = 1 idiot posi = 0
so it is true and the %R filteres the rest, so only situations where Hero is PFA OOP.

U wierd me now, plz clear up what u did mean.

does "not has position" flag fill my needs? (the OOP check problem?)
js2002
 
Posts: 1502
Joined: Fri Feb 15, 2008 5:44 am
Location: Germany

Re: Planning: PFA OOP NOT CBet XF Stat

Postby kraada » Sun Oct 18, 2009 10:05 pm

If we are the preflop raiser, and we are never 3bet, the only thing we can check is holdem_hand_player_detail.flg_f_has_position which is true when we have absolute position on the flop (that is, we are last to act) and false if there is anybody (no matter how many people there are) to act after us.
kraada
Moderator
 
Posts: 54430
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: Planning: PFA OOP NOT CBet XF Stat

Postby js2002 » Mon Oct 19, 2009 3:11 am

why never 3bet? I dont check that.
Do u mean we never FACE a 3bet? That I filter out by %R.
js2002
 
Posts: 1502
Joined: Fri Feb 15, 2008 5:44 am
Location: Germany

Re: Planning: PFA OOP NOT CBet XF Stat

Postby WhiteRider » Mon Oct 19, 2009 4:26 am

You are building the stat from the preflop aggressor's position, yes?
Therefore the preflop aggressor is the active player, and the PFA position will either be -1 (if this player was the only one to raise) or the position of the last other player to raise.

You can either use 'NOT holdem_hand_player_detail.flg_f_has_position' as kraada suggested, or if the player checks and faces a bet then he must have been out of position (although you don't always face a flop bet, so that won't work for all your cases).
holdem_hand_player_detail.flg_f_has_position will do the trick, though - this means that there is at least one player behind.

For any street where the player faces a bet you can use "holdem_hand_player_detail.val_f_bet_aggressor_pos" and see if that is less than the current player's position, which would mean the bet came from someone who has position on them.
WhiteRider
Moderator
 
Posts: 54025
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Planning: PFA OOP NOT CBet XF Stat

Postby marvin » Fri Oct 23, 2009 1:18 pm

whiterider says:
For any street where the player faces a bet you can use "holdem_hand_player_detail.val_f_bet_aggressor_pos" and see if that is less than the current player's position, which would mean the bet came from someone who has position on them.

YES BUT MUST BE "AND holdem_hand_player_detail.val_f_bet_aggressor_pos >0 " WHY IF NOT MAY BE THE BETTOR IS THE HERO.
marvin
 
Posts: 327
Joined: Tue Jul 08, 2008 10:17 am

Re: Planning: PFA OOP NOT CBet XF Stat

Postby kraada » Fri Oct 23, 2009 1:47 pm

Yes but in this stat you're checking for times you've checked and faced a bet on the flop - val_f_bet_aggressor_pos will never be you in that case.
kraada
Moderator
 
Posts: 54430
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Next

Return to Custom Stats, Reports, and SQL [Read Only]

Who is online

Users browsing this forum: No registered users and 0 guests