Custom Stat: Fold vs RFI for MTT Tournament

[Gae80]

Hi everyone,

I wanted to create a simple, clean statistic for my tournament HUD to track how often a player folds specifically when facing an open raise (RFI) across all positions.

Since I wanted to make sure it is completely accurate, I built this custom stat and would love to get your confirmation or feedback on it.

Here's the screenshot:

Stat Fold to RFI.png

(86.39 KiB) Downloaded 724 times

[Flag_Hippo]

To check that I would need to know the expressions used in your custom columns. Please copy/paste the expressions from those columns into a reply.

[Gae80]

To check that I would need to know the expressions used in your custom columns. Please copy/paste the expressions from those columns into a reply.

Hi Flag_Hippo,

Thank you for your reply!

Here are the expressions used in the columns for this stat:
sum(if[tourney_hand_player_statistics.flg_p_3bet_opp and tourney_hand_player_statistics.flg_p_fold, 1, 0])
sum(if[tourney_hand_player_statistics.flg_p_3bet_opp, 1, 0])

Here's below the screenshot of the columns section: I would like to ask you: is it normal that when I look at the Columns tab, I see the formula sum(tourney_summary.amt_addon * tourney_results.cnt_addon) in the Expression box, rather than seeing both columns combined there?

Columns.png

(61.94 KiB) Downloaded 704 times

[Flag_Hippo]

Here are the expressions used in the columns for this stat:
sum(if[tourney_hand_player_statistics.flg_p_3bet_opp and tourney_hand_player_statistics.flg_p_fold, 1, 0])
sum(if[tourney_hand_player_statistics.flg_p_3bet_opp, 1, 0])

There is nothing in these expressions that's specific to the player facing a raise first in. Also tourney_hand_player_statistics.flg_p_fold isn't suitable as the player could 3bet and fold to further action. I would recommend starting by duplicating the following columns instead:

cnt_p_2bet_def_action_fold
cnt_p_2bet_def_opp

That will give you a statistic for how often a player folded to a 2Bet (first raise) preflop. You can edit those columns for folding vs a raise first in by specifying that there were no limpers:

Code: Select all

char_length(tourney_hand_summary.str_aggressors_p) >= 2 and char_length(tourney_hand_summary.str_actors_p) >= 2 and substring(tourney_hand_summary.str_aggressors_p from 2 for 1) ::int = substring(tourney_hand_summary.str_actors_p from 1 for 1) ::int

and if you do not want callers in-between you'll also need to test for not having a squeeze opportunity:

Code: Select all

NOT tourney_hand_player_statistics.flg_p_squeeze_opp

Here's below the screenshot of the columns section: I would like to ask you: is it normal that when I look at the Columns tab, I see the formula sum(tourney_summary.amt_addon * tourney_results.cnt_addon) in the Expression box, rather than seeing both columns combined there?

I am not sure what you are asking but amt_addon is the column. Columns cannot be referenced in column expressions. tourney_summary.amt_addon and tourney_results.cnt_addon are a part of the database schema and are not columns.

[Gae80]

Hi Flag_Hippo,

Here are the expressions used in the columns:

cnt_p_rfi_def_action_fold_copy:

sum(if[tourney_hand_player_statistics.amt_p_2bet_facing > 0 AND ((tourney_hand_player_statistics.flg_p_limp and lookup_actions_p.action = 'CF') or (NOT(tourney_hand_player_statistics.flg_p_limp) and lookup_actions_p.action SIMILAR TO '(XF|F)')) AND char_length(tourney_hand_summary.str_aggressors_p) >= 2 and char_length(tourney_hand_summary.str_actors_p) >= 2 and substring(tourney_hand_summary.str_aggressors_p from 2 for 1) ::int = substring(tourney_hand_summary.str_actors_p from 1 for 1) ::int and NOT tourney_hand_player_statistics.flg_p_squeeze_opp , 1, 0])

cnt_p_rfi_def_opp_copy:

sum(if[tourney_hand_player_statistics.amt_p_2bet_facing > 0 AND char_length(tourney_hand_summary.str_aggressors_p) >= 2 and char_length(tourney_hand_summary.str_actors_p) >= 2 and substring(tourney_hand_summary.str_aggressors_p from 2 for 1) ::int = substring(tourney_hand_summary.str_actors_p from 1 for 1) ::int and NOT tourney_hand_player_statistics.flg_p_squeeze_opp , 1, 0])

Here's below the screenshots:

cnt_p_rfi_def_action_fold_copy.png

(97.54 KiB) Downloaded 668 times

cnt_p_rfi_def_opp_copy.png

(93.29 KiB) Downloaded 665 times

Fold vs RFI Custom.png

(86.9 KiB) Downloaded 664 times

[Flag_Hippo]

That will work but you could shorten one column by changing this:

Code: Select all

((tourney_hand_player_statistics.flg_p_limp and lookup_actions_p.action = 'CF') or (NOT(tourney_hand_player_statistics.flg_p_limp) and lookup_actions_p.action SIMILAR TO '(XF|F)'))

to just this:

Code: Select all

lookup_actions_p.action SIMILAR TO '(XF|F)'

since the aggressors and actors strings are already testing for no limpers.

[Gae80]

Hi Flag_Hippo,

I tried to play some expressos on Winamax and it seems to be working with the following formulas, I also created the Call to Rfi stat:

cnt_p_rfi_def_opp_copy:

sum(if[tourney_hand_player_statistics.amt_p_2bet_facing > 0 AND tourney_hand_summary.str_aggressors_p LIKE '8%' AND (substring(tourney_hand_summary.str_aggressors_p from 2 for 1) = substring(tourney_hand_summary.str_actors_p from 1 for 1) OR (substring(tourney_hand_summary.str_aggressors_p from 2 for 1) = '9' AND tourney_hand_summary.str_actors_p LIKE '09%')), 1, 0])

cnt_p_rfi_def_action_fold_copy:

sum(if[tourney_hand_player_statistics.amt_p_2bet_facing > 0 AND tourney_hand_player_statistics.flg_p_fold AND tourney_hand_summary.str_aggressors_p LIKE '8%' AND (substring(tourney_hand_summary.str_aggressors_p from 2 for 1) = substring(tourney_hand_summary.str_actors_p from 1 for 1) OR (substring(tourney_hand_summary.str_aggressors_p from 2 for 1) = '9' AND tourney_hand_summary.str_actors_p LIKE '09%')), 1, 0])

cnt_p_rfi_def_action_call_copy:

sum(if[tourney_hand_player_statistics.amt_p_2bet_facing > 0 AND tourney_hand_player_statistics.cnt_p_call > 0 AND tourney_hand_summary.str_aggressors_p LIKE '8%' AND (substring(tourney_hand_summary.str_aggressors_p from 2 for 1) = substring(tourney_hand_summary.str_actors_p from 1 for 1) OR (substring(tourney_hand_summary.str_aggressors_p from 2 for 1) = '9' AND tourney_hand_summary.str_actors_p LIKE '09%')), 1, 0])

Here's below the screenshots:

Column cnt_p_rfi_def_opp_copy.png

(90.92 KiB) Downloaded 614 times

Column cnt_p_rfi_def_action_fold_copy.png

(95.68 KiB) Downloaded 611 times

Column cnt_p_rfi_def_action_call_copy.png

(97.59 KiB) Downloaded 611 times

[Flag_Hippo]

You haven't made the changes I recommended to the fold column and you have instead introduced other things for some reason:

Code: Select all

tourney_hand_summary.str_aggressors_p LIKE '8%'

Code: Select all

(substring(tourney_hand_summary.str_aggressors_p from 2 for 1) = '9' AND tourney_hand_summary.str_actors_p LIKE '09%')

The latter is testing for the button limping and SB raising which contradicts the statistic you said you wanted.

You have also removed this from the column:

Code: Select all

NOT tourney_hand_player_statistics.flg_p_squeeze_opp

[Gae80]

You haven't made the changes I recommended to the fold column and you have instead introduced other things for some reason:

Code: Select all

tourney_hand_summary.str_aggressors_p LIKE '8%'

Code: Select all

(substring(tourney_hand_summary.str_aggressors_p from 2 for 1) = '9' AND tourney_hand_summary.str_actors_p LIKE '09%')

The latter is testing for the button limping and SB raising which contradicts the statistic you said you wanted.

You have also removed this from the column:

Code: Select all

NOT tourney_hand_player_statistics.flg_p_squeeze_opp

Hi Flag_Hippo,

You are totally right, I am making a lot of confusion with these custom expressions! :D

The reason I tried to tweak the formula is that when I applied the exact changes you previously recommended, the statistic completely stopped showing up in my HUD (it just displayed as dashes). I must have broken something else while trying to fix that visibility issue.

I will wipe out my edits and try again using strictly your formulas. If it turns out to be too difficult to get it working, I'll just stick to the native stats, which are already doing a great job.

Thank you for catching those contradictions, I really appreciate your patience with my database mess!