PFR doubts!

[andrenalina]

You said

cnt_p_sr_first_action_ip_def_opp: Number of times the player faces a single raise as first action in position.
sum( if[ holdem_hand_player_statistics.flg_p_3bet_opp AND NOT(holdem_hand_player_statistics.flg_p_limp OR lookup_positions.flg_blinds), 1, 0])

This says

- You must have the opportunity to 3bet
- Or you didnt limp or you arent at the blinds

I this case will be counted the cases where you are at the blinds, and the case where you are not at the blinds and limped, because the first OR will be check and is not needed to check de second, and if the first is not checked and the second is it will be counted. OR one OR another, right? This is because if the player limped it will be counted in another stat and if the player is at the blinds because that situation we have the player out of position, and this is stats if for the player in position.

I think we should change this OR to AND because we want the cases where

- You must have the opportunity to 3bet
- You didnt limp
- You arent at the blinds

We dont want the cases where the players limped AND the player is at the blinds.

The same is for

cnt_p_sr_first_action_ip_def_action_raise: Number of times the player 3bets a single raise as first action in position.
sum( if[ holdem_hand_player_statistics.flg_p_3bet AND NOT(holdem_hand_player_statistics.flg_p_limp OR lookup_positions.flg_blinds), 1, 0])

Neither limped players nor blinds.

I know its saturday and you will probabily be answering from monday on, but Im tryng here to construct the other stats and I will wait for your answer to confirm that stats to follow asking for more doubs in the future stats. I think as we are correcting theese the future stas will be easier, because they're similar.

[WhiteRider]

holdem_hand_player_statistics.flg_p_3bet_opp AND NOT(holdem_hand_player_statistics.flg_p_limp OR lookup_positions.flg_blinds)


..is

3-bet-opp AND NOT ( limp or blinds )

If the player limped or is in the blinds then the bit in the brackets will be true, and NOT of that will be false, so it won't count either case, when the player limps or is in the blinds.

This is equivalent to:

3-bet-opp AND NOT limp AND NOT blinds

FWIW, I'm not sure that using "lookup_positions.flg_blinds" like that will work - it's not something I've tried, but you might find that checking for "holdem_hand_player_statistics.position < 8" is safer.
(Blind positions are always 8 and 9, regardless of the number of players at the table.)

sum( if[ holdem_hand_player_statistics.flg_p_3bet_opp AND NOT holdem_hand_player_statistics.flg_p_limp AND holdem_hand_player_statistics.position < 8, 1, 0])

..counts times the player had opportunity to 3-bet when they hadn't limped and weren't in the blinds.

[WhiteRider]

FWIW, I'm not sure that using "lookup_positions.flg_blinds" like that will work - it's not something I've tried, but you might find that checking for "holdem_hand_player_statistics.position < 8" is safer.

..although having said that, this may be something that Kraada has used before as he has built some sets of positional stats, in which case I'm sure he's tested it.

[andrenalina]

Thanks guys! Man, Im liking to much the attetion of you at PT, the best support I've ever seen! None of my post spent more than one day to be answered, I thought because of the weekend you'd have a break, but not, good work guys!!!

So is it ok the lookup_positions.flg_blinds? Is that the same of holdem_hand_player_statistics.position < 8, ok?

But I still have a doubt

A AND NOT(B OR C) = A AND NOT B AND NOT C? (the 3 must be checked)

And what about

A AND NOT (B AND C) is the same thing? If not whats the diference?

And more. How do I make the condition for the case you want A and not (or B or C), that is, A AND NOT B or A AND NOT C, how do I define that, because I thought It was the case A AND NOT(B OR C)?

[kraada]

NOT(B AND C) is logically equivalent to NOT(B) OR NOT(C). NOT(B OR C) is logically equivalent to NOT(B) AND NOT(C). See Demorgan's Law.

I have not tested lookup_positions.flg_blinds extensively so WhiteRider is correct that checking for position < 8 may be safer (though the lookup table may work, I just haven't tested it in a while).

[andrenalina]

I understood the last post, and I will read the content of the site you said. Please check if its correct now, I think it is:

Stats

Preflop Fold to Single Raise First Action In Position: Player's percentage of preflop fold to single raise as first action in position.
( cnt_p_sr_first_action_ip_def_action_fold / cnt_p_sr_first_action_ip_def_opp ) * 100

Preflop 3bet First Action In Position: Player's percentage of preflop 3bet as first action in position.
( cnt_p_sr_first_action_ip_def_action_raise / cnt_p_sr_first_action_ip_def_opp ) * 100

Columns

cnt_p_sr_first_action_ip_def_opp: Number of times the player faces a preflop single raise as first action in position.
sum( if[ holdem_hand_player_statistics.flg_p_3bet_opp AND NOT(holdem_hand_player_statistics.flg_p_limp OR holdem_hand_player_statistics.position < 8), 1, 0])

cnt_p_sr_first_action_ip_def_action_fold: Number of times the player folds to a preflop single raise as first action in position.
sum( if[ holdem_hand_player_statistics.flg_p_3bet_opp AND lookup_actions_p.action LIKE 'F' AND NOT(holdem_hand_player_statistics.position < 8), 1, 0])

cnt_p_sr_first_action_ip_def_action_raise: Number of times the player 3bets preflop as first action in position.
sum( if[ holdem_hand_player_statistics.flg_p_3bet AND NOT(holdem_hand_player_statistics.flg_p_limp OR holdem_hand_player_statistics.position < 8), 1, 0])

[kraada]

That looks good to me.

[WhiteRider]

Not quite - you're not checking the position right.
In your expression, if the player is on the button (position 0) then "holdem_hand_player_statistics.position < 8" is TRUE, and "NOT ( anything OR TRUE)" is FALSE, and "anything AND FALSE" is false, so your expression will be false.

If you want to use that structure of A AND NOT (B OR C) then you need the position check to check for being in the blinds (because you are then NOTing it), so you could do this:

sum( if[ holdem_hand_player_statistics.flg_p_3bet AND NOT(holdem_hand_player_statistics.flg_p_limp OR holdem_hand_player_statistics.position > 7), 1, 0])

..or you could do it as I suggested originally:

sum( if[ holdem_hand_player_statistics.flg_p_3bet AND (NOT holdem_hand_player_statistics.flg_p_limp) AND holdem_hand_player_statistics.position < 8, 1, 0])

[andrenalina]

Sure man, It was my mistake, kraada was right and I did a mistake when rewrote the columns. I'll post again to make it definitive, so the stat will be

Stats

Preflop Fold to Single Raise First Action In Position: Player's percentage of preflop fold to single raise as first action in position.
( cnt_p_sr_first_action_ip_def_action_fold / cnt_p_sr_first_action_ip_def_opp ) * 100

Preflop 3bet First Action In Position: Player's percentage of preflop 3bet as first action in position.
( cnt_p_sr_first_action_ip_def_action_raise / cnt_p_sr_first_action_ip_def_opp ) * 100

Columns

cnt_p_sr_first_action_ip_def_opp: Number of times the player faces a preflop single raise as first action in position.
sum( if[ holdem_hand_player_statistics.flg_p_3bet_opp AND (NOT holdem_hand_player_statistics.flg_p_limp) AND holdem_hand_player_statistics.position < 8, 1, 0])

cnt_p_sr_first_action_ip_def_action_fold: Number of times the player folds to a preflop single raise as first action in position.
sum( if[ holdem_hand_player_statistics.flg_p_3bet_opp AND lookup_actions_p.action LIKE 'F' AND holdem_hand_player_statistics.position < 8, 1, 0])

cnt_p_sr_first_action_ip_def_action_raise: Number of times the player 3bets preflop as first action in position.
sum( if[ holdem_hand_player_statistics.flg_p_3bet AND NOT(holdem_hand_player_statistics.flg_p_limp) AND holdem_hand_player_statistics.position < 8, 1, 0])

Now its right! Thanks guys!

[WhiteRider]

Yes, that looks good!

----

Just for reference, because you aren't using any wildcards in the LIKE statement:

lookup_actions_p.action LIKE 'F'

..is equivalent to:

lookup_actions_p.action = 'F'

This is only because you're comparing an exact string - if you wanted to check for the first action being a call (followed by any other actions), for instance, you'd need to use LIKE as you'd use the % wildcard character too.
lookup_actions_p.action LIKE 'C%'

You don't need to change anything, but I think that = is probably slightly more efficient than LIKE for this case.