Fold to 3Bet positional

[js2002]

Hi experts,

I made the standard orginal "fold to pf 3bet" stat for each position:

http://rapidshare.com/files/206894486/f ... l.rar.html

After that, I though a little bit:

1. @ orginal "fold to pf 3bet": Are there Squeezes into it? f.e. Mr. HUD raises firstin (2bet), Mr. A coldcalls, Mr. B 3bets (squezzes). Mr HUD folds. Is this a "fold to pf 3bet" ?

2. Are the known fold to 3bet positional stats in this forum that handle the positional fold to 3bet topic and maybe there are even finished stats?

3. What else do I have to consider @my 20 new stats? Are they ok like this or did I forgot special cases? (f.e. how much sense does it make to build in sth like: "was the guy who folded to a 3bet in position x (Mr. HUD) the initial 2Better?!)

[js2002]

found a stat in the rep. "4bet when was initial raiser", thats what i need I think.
but i have to modify it for fold to 3bet.

@WhiteRider: was the things with "initial raiser aka 2better" the reason to request 2Bet column?! Do they exist?!

[kraada]

The squeeze columns are currently known to have some issues, so I would be careful about using them (I'm not certain off the top of my head exactly what the issues with it are, if you want me to check I'd be glad to dot hat for you).

If you want to make your fold to 3-bet fold to 3-bet when you were the initial raiser add this to both columns (the raise and the opportunity column):
"and holdem_hand_player_statistics.flg_p_first_raise"

and then it'll be for only times you raise first in.

If you're looking to do it for fold to 4bet when you were the 3better make it "and holdem_hand_player_statistics.flg_p_3bet" instead.

[js2002]

nominator:
sum(if[holdem_hand_player_statistics.enum_p_3bet_action='F' AND holdem_hand_player_statistics.position = 0 AND holdem_hand_player_statistics.flg_p_first_raise, 1, 0])
denominator:
sum(if[holdem_hand_player_statistics.flg_p_3bet_def_opp AND holdem_hand_player_statistics.position = 0 AND holdem_hand_player_statistics.flg_p_first_raise, 1, 0])

1. Is this correct (for the Button)?
2. So flg_p_first_raise includes all cases? like isolation of a limpers etc?!

[kraada]

(1) Yes.

(2) I think it should, if you want to be absolutely certain that your first action is raise though you could instead use:
lookup_actions_p.action LIKE 'R%'

as that says that your action string starts off with an R (raise), and if your raise was a 3bet, you can't then face a 3bet later so it should work that way too.

[js2002]

(1) Yes.

(2) I think it should, if you want to be absolutely certain that your first action is raise though you could instead use:
lookup_actions_p.action LIKE 'R%'

as that says that your action string starts off with an R (raise), and if your raise was a 3bet, you can't then face a 3bet later so it should work that way too.

1. Explain in simple english again plz, why should I use that "R" way? Why is it better? (sry did not understand all) What in the field when it was a 3bet? a '3%' ?!?!?!?

2. what happens if somebody behind the 3better 4bets, does the firstin raiser still "face a 3bet" ?! Im wierd now...

[kraada]

(1) The action string is the list of things you do in the hand, and contains only the following letters: B, C, F, R, X for bet, call, fold, raise and check. So if your actions on the flop were, say, check, raise fold the string for the flop is XRF. In this case we're looking for the preflop string to start with an R (that's what R% means; R then anything after), meaning you raised on your first action.

(2) If the action is:
Player A raises UTG, Player B raises UTG+1 and Player C is in the CO, he is facing a 3bet. If he raises, player D in the BB doesn't face a 3-bet ever, he faces a 4bet.

[js2002]

nearly perfect answers thx!
one last thing: Why is the "string" way better? Is this a new standard. I think it came later into PT3 right?

[kraada]

They should be functionally identical assuming that the flag is set properly. The string method is only slightly better in that it's easier to say for sure there's no problem with the strings in the database (we'd have found out about that by now) but a very small case being improperly set up in the flag might be very hard to miss and thus leave your data slightly (though not much) askew.

[WhiteRider]

holdem_hand_player_statistics.flg_p_first_raise is true if and only if you were the first person to make a raise preflop, regardless of any other action you made, or anyone else made before you. This will always be a 2-bet on all streets so I think it good enough for what you want.
Preflop, if you make the first raise then that has to be your first action, but on later streets you could check then someone else could bet and you could then still make the first raise when the action gets back to you, so using the action string method would tell you whether the raise you made was your first action (lookup_actions_f.action LIKE 'R%') or whether you checked and then raised (lookup_actions_f.action LIKE 'XR%'). In both cases flg_f_first_raise would be true if you made the 2-bet.