Page 1 of 1
delayed XR stat
Posted:
Sat Oct 12, 2024 11:01 am
by caribbean93
Hi, I'm trying to create a stat for my HUD of tournaments Spins.
I want to know the percentage of check raise of my rival vs my delayed bet BTN vs BB. I open raise as BTN, BB called, I don't Cbet Flop, BB don't probe turn, I bet turn and BB raise.
Thanks for you help
Re: delayed XR stat
Posted:
Sun Oct 13, 2024 7:51 am
by Ventilatorrr
Hello,
Here are updated columns (and the stat) for the BB vs BTN Raise vs Turn Delayed Cbet stat:
1. Column #1: cnt_bb_vs_btn_raise_vs_turn_delayed_cbet_srp
- Code: Select all
sum(if[tourney_hand_player_statistics.position = 8 and tourney_hand_summary.str_aggressors_p = '80' and tourney_hand_summary.str_actors_p = '08' and lookup_actions_f.action = 'X' and lookup_actions_t.action LIKE 'XR%', 1, 0])
2. Column #2: cnt_bb_vs_btn_raise_vs_turn_delayed_cbet_srp_opp
- Code: Select all
sum(if[tourney_hand_player_statistics.position = 8 and tourney_hand_summary.str_aggressors_p = '80' and tourney_hand_summary.str_actors_p = '08' and lookup_actions_f.action = 'X' and lookup_actions_t.action LIKE 'X_%', 1, 0])
3. Stat: BB vs BTN Raise vs Turn Delayed Cbet
- Code: Select all
(cnt_bb_vs_btn_raise_vs_turn_delayed_cbet_srp / cnt_bb_vs_btn_raise_vs_turn_delayed_cbet_srp_opp) * 100
Re: delayed XR stat
Posted:
Mon Oct 14, 2024 9:24 am
by Ventilatorrr
An expert has looked over my columns and has noticed an issue with the lookup_actions_t.action = 'XR' part, which doesn't include hands with any further actions after check/raising on the turn to count towards the stat. Also, "=" has been used instead of "LIKE" in str_aggressors_p and str_actors_p parts. I've edited my previous post with these changes.
Re: delayed XR stat
Posted:
Tue Oct 15, 2024 4:28 am
by caribbean93
Thank you, I'll give it a try right now
Re: delayed XR stat
Posted:
Wed Oct 16, 2024 4:54 am
by caribbean93
Great,it works.
How could I make two different stats, one for Limped pots and the other for Raised pots?
Cheers
Re: delayed XR stat
Posted:
Wed Oct 16, 2024 6:32 am
by Flag_Hippo
That depends on if you mean generally or for what's been posted above. You can normally test for a limped pot with:
- Code: Select all
char_length(cash_hand_summary.str_aggressors_p) = 1
and raised pots with:
- Code: Select all
char_length(cash_hand_summary.str_aggressors_p) >= 2
but that will not work for what's been posted above since the aggressors string in those columns is set at being two characters long since you wanted hands where BTN raised and BB called so just adding
char_length(cash_hand_summary.str_aggressors_p) = 1 to those columns would mean not getting any data without further adjustments.