coldcall vs position

Discuss how to create custom stats, reports and HUD profiles and share your creations.

Moderators: WhiteRider, kraada, Flag_Hippo, morny, Moderators

Re: coldcall vs position

Postby madsquare » Sat Apr 12, 2014 10:45 am

nevermind the 0s, its working now. Even though it takes very long to load the popup.




The percentages for fold, 3bet and call still dont match up. 2 days into this and a lot of explaining, there is no progress on it. We have to make some.
madsquare
 
Posts: 26
Joined: Thu Dec 29, 2011 12:12 pm

Re: coldcall vs position

Postby WhiteRider » Sat Apr 12, 2014 11:50 am

Can you explain exactly what is still wrong?
Kraada explained that the fold, call and raise stats will not add up to 100% because the opportunities are different for fold/call and raise. Is that what you're referring to?
WhiteRider
Moderator
 
Posts: 54017
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: coldcall vs position

Postby madsquare » Sat Apr 12, 2014 12:32 pm

theres one post of kraada talking about skewing and why 'expected' coldcalling frequencies are likely different than actual ones.
I understand all of this, consider it solved.

The question still open:
madsquare wrote:this custom cc v pos stat and the corrosponding PT-default 3b v pos stat dont add up to the PT-default fold v pos stat [cc + 3b < (1-fold)]; it should be equal.


to be 100% clear:
stats for this example villain, who is real
fold vs bu (pos=BB): 27.7 ---- its the default stat, you can find it one page 1 too
3bet vs bu open (pos=BB): 17.81 ---- default stat
coldcall vs bu 48.78 ---- custom, latest version on page 2 (see p1 also)

>>> wheres the missing 5.71%?

fold vs co (pos=BB): 58 ---- its the default stat, you can find it one page 1 too
3bet vs co open (pos=BB): 9.79 ---- default stat
coldcall vs co 23.5 ---- custom, latest version on page 2 (see p1 also)

>>> wheres the missing 8.71% ?
madsquare
 
Posts: 26
Joined: Thu Dec 29, 2011 12:12 pm

Re: coldcall vs position

Postby WhiteRider » Sat Apr 12, 2014 2:34 pm

You have less opportunities to 3bet than you do to call or fold, so these percentages will not necessarily add up to 100.

Imagine you face three 2Bets and one of them is for more than your stack. You fold to the one which is for more than your stack and you call one of the others and raise the other.
Your fold and call percentages are both 33%, but your 3bet percentage is 50%. These do not add up to 100%.

If you have a specific example where you think one of the stats is wrong please send us the hand history and we'll check it out for you.
WhiteRider
Moderator
 
Posts: 54017
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: coldcall vs position

Postby potamito » Tue Jul 07, 2015 3:42 pm

I have a question rearding Call PF 2Bet stat which its define as "(cnt_p_2bet_def_action_call / cnt_p_2bet_def_opp) * 100", does the...

cnt_p_2bet_def_action_call
Code: Select all
sum(if[tourney_hand_player_statistics.amt_p_2bet_facing > 0 AND ((NOT(tourney_hand_player_statistics.flg_p_limp) AND lookup_actions_p.action LIKE 'C%') OR lookup_actions_p.action SIMILAR TO '(C|X)C%'), 1, 0])


Excludes the potential limping action? I want the stat to show how often a player calls a open raise
potamito
 
Posts: 802
Joined: Wed Apr 21, 2010 4:20 pm

Re: coldcall vs position

Postby kraada » Tue Jul 07, 2015 3:48 pm

That is how often someone calls an open raise -- but limping is included. If you want to know how often someone calls cold in position you can just use the built in stat Cold Call 2Bet PF.
kraada
Moderator
 
Posts: 54431
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: coldcall vs position

Postby potamito » Mon Jan 04, 2016 3:04 pm

Custom columns:

note: i used the "cash_hand_player_statistics.flg_p_ccall" originally, but it resultet in zeros for all positions where the coldcaller is oop. Now it works for BBvBU and SvBU.

cnt_p_coldcall_vs_btn_open
Code: Select all
 sum(if[cash_hand_summary.str_aggressors_p LIKE '80%' and
    cash_hand_summary.str_actors_p LIKE '0%' and
    cash_hand_player_statistics.flg_vpip and
    not(cash_hand_player_statistics.flg_p_3bet or cash_hand_player_statistics.flg_p_squeeze_opp), 1, 0])



cnt_p_coldcall_vs_co_open
Code: Select all
  sum(if[cash_hand_summary.str_aggressors_p LIKE '81%' and
    cash_hand_summary.str_actors_p LIKE '1%' and
    cash_hand_player_statistics.flg_vpip and
    not(cash_hand_player_statistics.flg_p_3bet or cash_hand_player_statistics.flg_p_squeeze_opp), 1, 0])



cnt_p_coldcall_vs_mp_open
Code: Select all
 sum(if[cash_hand_summary.str_aggressors_p LIKE '82%' and
    cash_hand_summary.str_actors_p LIKE '2%' and
    cash_hand_player_statistics.flg_vpip and
    not(cash_hand_player_statistics.flg_p_3bet or cash_hand_player_statistics.flg_p_squeeze_opp), 1, 0])



cnt_p_coldcall_vs_utg_open
Code: Select all
   sum(if[cash_hand_summary.str_aggressors_p LIKE '83%' and
    cash_hand_summary.str_actors_p LIKE '3%' and
    cash_hand_player_statistics.flg_vpip and
    not(cash_hand_player_statistics.flg_p_3bet or cash_hand_player_statistics.flg_p_squeeze_opp), 1, 0])


Can someone point it out the oportunity columns for these?
potamito
 
Posts: 802
Joined: Wed Apr 21, 2010 4:20 pm

Re: coldcall vs position

Postby kraada » Mon Jan 04, 2016 5:06 pm

I don't think you want flg_vpip in these cases - as the way you've written it, the times you make the 2bet would count (as an open raise is a vpip situation). Instead I think you want: lookup_actions_p.action LIKE 'C%' - that guarantees the player's first action was to call.

Instead of that clause for your opportunities use cash_hand_player_statistics.amt_p_2bet_facing > 0.
kraada
Moderator
 
Posts: 54431
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: coldcall vs position

Postby potamito » Mon Jan 04, 2016 5:33 pm

kraada wrote:I don't think you want flg_vpip in these cases - as the way you've written it, the times you make the 2bet would count (as an open raise is a vpip situation). Instead I think you want: lookup_actions_p.action LIKE 'C%' - that guarantees the player's first action was to call.

Instead of that clause for your opportunities use cash_hand_player_statistics.amt_p_2bet_facing > 0.


Like this?

BB CC vs BU RFI is define as ( cnt_p_coldcall_vs_bu_rfi / cnt_p_coldcall_vs_bu_rfi_opp )*100

Where..
cnt_p_coldcall_vs_bu_rfi
Code: Select all
sum(if[cash_hand_summary.str_aggressors_p LIKE '80%' and
cash_hand_summary.str_actors_p LIKE '0%'
and lookup_actions_p.action LIKE 'C%'
and not(cash_hand_player_statistics.flg_p_squeeze_opp), 1, 0])


cnt_p_coldcall_vs_bu_rfi_opp
Code: Select all
sum(if[cash_hand_summary.str_aggressors_p LIKE '80%' and
cash_hand_summary.str_actors_p LIKE '0%'
and cash_hand_player_statistics.amt_p_2bet_facing > 0
and not(cash_hand_player_statistics.flg_p_squeeze_opp), 1, 0])
potamito
 
Posts: 802
Joined: Wed Apr 21, 2010 4:20 pm

Re: coldcall vs position

Postby kraada » Mon Jan 04, 2016 6:10 pm

That looks good but keep in mind that you would need to specify the big blind position in Item Properties - either the SB or BB could qualify based on the definition you have.
kraada
Moderator
 
Posts: 54431
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

PreviousNext

Return to Custom Stats, Reports and HUD Profiles

Who is online

Users browsing this forum: No registered users and 14 guests

cron