Changing the default positions

[mager]

Nice mechanism.

OK so if I want to change "cnt_p_3bet_vs_mp_2bet" to "cnt_p_3bet_vs_mp_open" in 6max only, it will look like this:
sum(if[char_length(cash_hand_summary.str_aggressors_p) >= 2 AND cash_hand_summary.str_actors_p LIKE '2%' and cash_hand_player_statistics.flg_p_3bet AND ((cash_hand_summary.cnt_players BETWEEN 3 and 6 and substring(cash_hand_summary.str_aggressors_p from 2 for 1) = '2')), 1, 0])

I do not understand the "char_length(cash_hand_summary.str_aggressors_p) >= 2" part. Shouldn't it be JUST equals 2? If it is more than 2 - it is no longer a 3bet(it's 4bet+).
Also, I still don't fully understand substring. I understand it's function, but not how it is being used. Why is it " from 2 for 1" in this situation?

*I know I can remove the "cash_hand_summary.cnt_players BETWEEN 3 and 6" if it's purely for 6max but if it cause no harm I prefer to leave it there for future reference.

in 6max EP 2bet equals EP open(since it's just position 3), so I do not need to create new columns right?
(Though it is ((cash_hand_summary.cnt_players BETWEEN 4 and 6 and substring(cash_hand_summary.str_aggressors_p from 2 for 1)::int BETWEEN 3 and 5) and I think it can be "='3'" instead. There is no positions 4 and 5 in 6max )

[kraada]

Yes actors like '2%' will do what you want. The reason you want the length of the string to be greater than or equal to 2 is that you can face a 2bet and fold and then afterwards there are 3 and 4 bets made but that doesn't matter as far as you are concerned - you folded to the open and everything else that happened later was irrelevant. We need to make sure the string is at least length 2 because otherwise the SQL will error when the string is too small.

[mager]

OK I understand why it will be important to be greater than or equal to 2 when we are talking about the opportunity column of this stat. But when we talk about the actual 3bet, it can be equal to 2(i.e. no greater than) right?
Also, if you can address my two more small questions about substring and 6max EP 2bet it will be great. I know these are very specific but i'm trying to really understand and not just copy-past.

Thanks a lot :)

[kraada]

No, because if you 3bet then the string becomes length 3.

Regarding EP in 6max you are correct - a 2bet must be an open from that position. Technically there could be a position 4 in a 6 handed game if you were playing full ring and a player left resulting in a hand with no small blind - but playing in a devoted 6 max game that can never happen.

[mager]

Ah, yea I forgot the BB.
When you have time, if you can explain the substring this it will be helpful.

Anyway, I keep creating stats and I just found a mistake you made:
"cnt_f_cbet_def_action_fold_in_pos" and "cnt_f_cbet_def_action_raise_in_pos" are are missing the "not" before "cash_hand_player_statistics.flg_f_check". Check it out.

[kraada]

That's a known issue that should be fixed in the next beta.

[Mr Tiger]

Just want to specify. You haven't created all separate positions for fullring, because you think EP and MP grouped is usually more useful, or it's much more complex to make all separate or something? Looks weird for me, because I think, it's much more useful to have all positions separated and in case of some grouped columns get much more complex:

3bet vs CO 2bet:

Code: Select all

sum(if[cash_hand_player_statistics.flg_p_3bet and cash_hand_summary.str_aggressors_p LIKE '81%', 1, 0])

3bet vs MP 2bet:

Code: Select all

sum(if[char_length(cash_hand_summary.str_aggressors_p) >= 2 and cash_hand_player_statistics.flg_p_3bet AND ((cash_hand_summary.cnt_players BETWEEN 3 and 6 and substring(cash_hand_summary.str_aggressors_p from 2 for 1) = '2') OR (cash_hand_summary.cnt_players BETWEEN 7 and 8 and substring(cash_hand_summary.str_aggressors_p from 2 for 1)::int BETWEEN 2 and 3) OR (cash_hand_summary.cnt_players BETWEEN 9 and 10 and substring(cash_hand_summary.str_aggressors_p from 2 for 1)::int BETWEEN 2 and 4)), 1, 0])

[WhiteRider]

As I understand it in the investigations which were done there was very little difference in behaviour between the different "EP" and different "MP" positions, so being able to combine data from those positions gives you more useful data than having to look at each position separately (which gives you a smaller sample size for each data point, and more complex data on screen).

[Mr Tiger]

I'd like to change the default positions, so for fullring table MP and UTG will match the same positions as for shorthanded one (MP - one position after the CO; UTG - next one position; so CO - #1; MP - #2; UTG - #3). I play 6max, 9max, 10max and sometimes 8,7,5,4-max tables simultaneously, and it would be much more comfortable to have the same position meanings for all table types. For earlier positions (#4-7) I will create custom stats. I can also create custom stats for positions #2-3 for fullring, but more custom stats mean slower HUD and more columns used (by the way, does number of custom columns influence HUD performance even with not all these columns used in the HUD?). But there is one important issue. Do I have to make the changes in pgAdmin to every DB? Can I do this once, so when I create a new DB by PT4, it would have positions meaning I set before?

[kraada]

Yes you'd need to make changes for every database.

For what it's worth, I did very detailed analyses on this very subject in the past, and found that positions earlier than the HJ played substantially similar. It was a little while ago but I would be surprised if there was a big shift in EP play given how much you're at the mercy of the large number of players behind you.