Open Opportunity and Behind Limpers filters

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

Re: Open Opportunity and Behind Limpers filters

Postby BigBangTheory » Mon Mar 19, 2012 7:31 pm

Ok, so if I want to apply the filter on the stat "Cbet Flop" :

(cnt_f_cbet / cnt_f_cbet_opp) * 100

and taking in consideration elements composing the numerator of RWPC filter :

cnt_p_raise_limpers = sum( if[ holdem_hand_player_statistics.flg_p_first_raise AND NOT holdem_hand_player_statistics.flg_p_open_opp, 1 , 0 ])

cnt_p_raise_first_in = sum( if[holdem_hand_player_statistics.flg_p_first_raise AND holdem_hand_player_statistics.flg_p_open_opp, 1, 0])



I guess I have to apply the following filter on Cbet Flop (members of cnt_p_raise_limpers + cnt_p_raise_first_in) :

(holdem_hand_player_statistics.flg_p_first_raise AND NOT holdem_hand_player_statistics.flg_p_open_opp) OR (holdem_hand_player_statistics.flg_p_first_raise AND holdem_hand_player_statistics.flg_p_open_opp)


Which is theoretically the same as applying only "holdem_hand_player_statistics.flg_p_first_raise" ...?


So, finally I will have :

cnt_f_cbet filtered :

sum(if[holdem_hand_player_statistics.flg_f_cbet AND holdem_hand_player_statistics.flg_p_first_raise, 1, 0])

cnt_f_cbet_opp filtered :

sum(if[holdem_hand_player_statistics.flg_f_cbet_opp AND holdem_hand_player_statistics.flg_p_first_raise, 1, 0])

Is that right ?

PS : I tried to be as clear as possible :-/
BigBangTheory
 
Posts: 30
Joined: Tue Aug 23, 2011 3:31 pm

Re: Open Opportunity and Behind Limpers filters

Postby WhiteRider » Tue Mar 20, 2012 4:59 am

Yes, they look fine.
WhiteRider
Moderator
 
Posts: 54025
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Open Opportunity and Behind Limpers filters

Postby BigBangTheory » Tue Mar 20, 2012 8:51 am

Ok, so it means that the "Raise first In" filter in PT3 and the field flg_p_first_raise in the database have different behaviors ?
BigBangTheory
 
Posts: 30
Joined: Tue Aug 23, 2011 3:31 pm

Re: Open Opportunity and Behind Limpers filters

Postby Mr Tiger » Tue Mar 20, 2012 10:35 am

BigBangTheory wrote:Ok, so it means that the "Raise first In" filter in PT3 and the field flg_p_first_raise in the database have different behaviors ?

Raise first in = flg_p_first_raise AND flg_p_open_opp
Mr Tiger
 
Posts: 143
Joined: Tue Sep 09, 2008 5:14 am

Re: Open Opportunity and Behind Limpers filters

Postby BigBangTheory » Tue Mar 20, 2012 3:45 pm

Yes, you are right ; in a first approach the name "flg_p_first_raise" was confusing.
BigBangTheory
 
Posts: 30
Joined: Tue Aug 23, 2011 3:31 pm

Re: Open Opportunity and Behind Limpers filters

Postby kraada » Tue Mar 20, 2012 5:11 pm

Yes, it just means that the player in question made the first raise (ie the 2Bet).
kraada
Moderator
 
Posts: 54430
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: Open Opportunity and Behind Limpers filters

Postby BigBangTheory » Wed Mar 21, 2012 9:53 am

I would like to add two filters in my custom stats :

- Add the filter "PF raise all-in" in addition of the filter "flg_p_first_raise"
- Add the filter "Facing all-in PF" in addition to the filter "flg_p_3bet_opp"

For "PF raise all-in" it seems that I need to use the field "enum_allin" and for "Facing all-in PF" the field "enum_face_allin".

But when I read the database definitions of this two fields, it seems that :

enum_allin : indicates if a all-in occured in the WHOLE PF session of a given hand. There is visibly no way to tell if the all-in was made for a raise or a 3bet, a 4bet...

enum_face_allin : indicates if the player faced a all-in in the whole hand (PF, F, T, R).

So, finally I can't see how to reproduce "PF raise all-in" and "Facing all-in PF" filters, in my custom stats...

Again, thank your for your help...
BigBangTheory
 
Posts: 30
Joined: Tue Aug 23, 2011 3:31 pm

Re: Open Opportunity and Behind Limpers filters

Postby kraada » Wed Mar 21, 2012 2:56 pm

holdem_hand_player_statistics.enum_allin = 'P' means that, at some point, the player made an all-in raise preflop.

Now, if you want that to be on the first raise add: AND NOT(holdem_hand_player_statistics.flg_p_3bet OR holdem_hand_player_statistics.flg_p_4bet)

If they made an all-in raise and it wasn't a 3bet or 4bet or higher it had to be the first raise. Similarly you can use (flg_p_3bet and NOT(flg_p_4bet)) to make sure that the raise was exactly a 3bet. The PT3 schema cannot distinguish between any bet that is higher than a 4bet and the 4bet itself.

Similarly you can use the defense opportunity flags (flg_p_3bet_def_opp and flg_p_4bet_def_opp) to see if the all-in faced was of a given raise level. If you faced an all-in 3bet and called and a 4bet was later made you won't be considered to have faced it as you had no money left to call with.
kraada
Moderator
 
Posts: 54430
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: Open Opportunity and Behind Limpers filters

Postby BigBangTheory » Wed Mar 21, 2012 4:42 pm

I forget to mention in my question that I do NOT want situation with "PF raise all-in" or "Facing all-in PF"...

I should have write this :

- Add the filter NOT "PF raise all-in" in addition of the filter "flg_p_first_raise"
- Add the filter NOT "Facing all-in PF" in addition to the filter "flg_p_3bet_opp"

For instance, if I take the case with NOT "PF raise all-in", I can make this :

flg_p_first_raise AND enum_allin NOT LIKE 'P'

But the player could have also made his all-in in a 3bet or a 4bet+... So here, I will lost in my stat cases where the player made a non-allin 2bet and made a all-in later...

And it will be the same thing with NOT "Facing all-in PF".

Sorry to don't be clear enough in my last post.
BigBangTheory
 
Posts: 30
Joined: Tue Aug 23, 2011 3:31 pm

Re: Open Opportunity and Behind Limpers filters

Postby kraada » Wed Mar 21, 2012 4:56 pm

flg_p_first_raise AND enum_allin NOT LIKE 'P' will not pick out hands where you 3bet or 4bet all-in. It will limit it to hands where you made the first raise, and did not - at any point - go all-in preflop.
kraada
Moderator
 
Posts: 54430
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

PreviousNext

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

Who is online

Users browsing this forum: No registered users and 4 guests