Call vs minraise stat

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

Moderators: WhiteRider, kraada, Flag_Hippo, morny, Moderators

Call vs minraise stat

Postby supaflyer » Mon Feb 24, 2014 2:43 pm

Hi Guys,

I'm trying to write a HU stat, which shows in how many percentages calls the enemy call our minraises.

I've tried it with the following definition:

(cnt_p_mr_call / cnt_p_mr_call_opp) * 100

cnt_p_mr_call
sum(if[(tourney_hand_player_statistics.amt_p_raise_facing / tourney_blinds.amt_bb) <= 2.25 AND lookup_actions_p.action LIKE 'C', 1, 0])

cnt_p_mr_call_opp
sum(if[(tourney_hand_player_statistics.amt_p_raise_facing / tourney_blinds.amt_bb) <= 2.25 AND lookup_actions_p.action LIKE '_', 1, 0])

My stat is not working properly, could you please tell me where is the problem? :S It also counts the SB limp as an opportunity to call a min raise.

Where is the problem in my stat?

Thanks,
supaflyer
supaflyer
 
Posts: 32
Joined: Mon Feb 24, 2014 7:24 am

Re: Call vs minraise stat

Postby kraada » Mon Feb 24, 2014 3:11 pm

Because 0 is less than 2.25 -- if you always want this to be heads up and you always want it to be from the big blind's perspective, you can set that fraction to exactly 1 -- because the big blind when facing a minraise has 1bb to call.

Once you do that it should work properly I think.
kraada
Moderator
 
Posts: 54431
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: Call vs minraise stat

Postby supaflyer » Mon Feb 24, 2014 3:51 pm

I've modified it in the following way:

cnt_p_mr_call
sum(if[(tourney_hand_player_statistics.amt_p_raise_facing / tourney_blinds.amt_bb) <= 1 AND lookup_actions_p.action LIKE 'C', 1, 0])

cnt_p_mr_call_opp
sum(if[(tourney_hand_player_statistics.amt_p_raise_facing / tourney_blinds.amt_bb) <= 1 AND lookup_actions_p.action LIKE '_', 1, 0])

Now, after the BB limped the stat did show (100 %) 1/1, however he didn't face a min raise... I'm really confused... :)
supaflyer
 
Posts: 32
Joined: Mon Feb 24, 2014 7:24 am

Re: Call vs minraise stat

Postby kraada » Mon Feb 24, 2014 6:01 pm

= 1, not <= 1. When you have it as <= 1, 0 matches. It's 0 when he doesn't face a raise and you don't want that.
kraada
Moderator
 
Posts: 54431
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: Call vs minraise stat

Postby supaflyer » Mon Feb 24, 2014 7:05 pm

Thanks, it works now.

One more question. I've tried to adjust it to a non-HU version. How should I redefine the columns in that case? I would like to get a stat, which shows in how many percentage does the enemy call a raise between 2 and 2.25 bb.

Thank you in advance!
supaflyer
 
Posts: 32
Joined: Mon Feb 24, 2014 7:24 am

Re: Call vs minraise stat

Postby kraada » Tue Feb 25, 2014 9:32 am

You need it to be = 1 when the player is in the BB, = 1.5 when the player is in the SB and = 2 otherwise.
kraada
Moderator
 
Posts: 54431
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: Call vs minraise stat

Postby supaflyer » Sat Mar 01, 2014 7:40 am

Hi,

I know what you mean, but I would like to have a generic stat, which shows how many % calls the enemy vs min raises, regardless his position.

Now I've setted up the following:

(cnt_p_mr_call_generic / cnt_p_mr_call_opp_generic) * 100

cnt_p_mr_call_generic
sum(if[(tourney_hand_player_statistics.amt_p_raise_facing / tourney_blinds.amt_bb) <= 2.25 AND lookup_actions_p.action LIKE 'C', 1, 0])

cnt_p_mr_call_opp_generic
sum(if[(tourney_hand_player_statistics.amt_p_raise_facing / tourney_blinds.amt_bb) <= 2.25 AND lookup_actions_p.action LIKE '_', 1, 0])

I've defined the minraise as a raise between 2 and 2.25bbs. However this doesn't work for me. It shows as an opportunity, when somebody makes a 3x raise, and the player is on the bb, and he has 2 bb to call. Could you please help me how to create a generic stat?

thanks,
supaflyer
supaflyer
 
Posts: 32
Joined: Mon Feb 24, 2014 7:24 am

Re: Call vs minraise stat

Postby WhiteRider » Sat Mar 01, 2014 9:12 am

You can add the amount of blind posted to make it more general. For example:

((tourney_hand_player_statistics.amt_p_raise_facing + tourney_hand_player_statistics.amt_blind) / tourney_blinds.amt_bb) <= 2.25

However, if the player doesn't face a raise then amt_p_raise_facing is zero, so will be less than 2.25, so you should probably use "between", like:

((tourney_hand_player_statistics.amt_p_raise_facing + tourney_hand_player_statistics.amt_blind) / tourney_blinds.amt_bb) BETWEEN 1.5 AND 2.25
WhiteRider
Moderator
 
Posts: 54017
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Call vs minraise stat

Postby supaflyer » Sat Mar 01, 2014 9:42 am

Thanks,

It looks ok now.

Cheers,
supaflyer
supaflyer
 
Posts: 32
Joined: Mon Feb 24, 2014 7:24 am

Re: Call vs minraise stat

Postby LosingPlayer » Thu Jan 26, 2017 6:42 pm

Hey,

i copied the aforementioned definitions for the columns and the custom stat, but i get the "invalid" expression notification when i try to implement the statistic.
The columns :

cnt_p_mr_call :=
sum(if[(tourney_hand_player_statistics.amt_p_raise_facing / tourney_blinds.amt_bb) = 1 AND lookup_actions_p.action LIKE 'C', 1, 0])

cnt_p_mr_call_opp :=

sum(if[(tourney_hand_player_statistics.amt_p_raise_facing / tourney_blinds.amt_bb) = 1 AND lookup_actions_p.action LIKE '_', 1, 0])

seem to work, but when i try to tell PT4 to compute:

(cnt_p_mr_call / cnt_p_mr_call_opp) * 100,

it doesnt validate the expression.

I have imported the column names both by copy and paste and the built in selection function to ensure that there is no font/ spelling errors in the reference.

I just recently switched to PT and have not used SQL in quite a while so please bear with me if my question turns out rather redundant.
LosingPlayer
 
Posts: 1
Joined: Thu Jan 26, 2017 6:15 pm

Next

Return to Custom Stats, Reports and HUD Profiles

Who is online

Users browsing this forum: No registered users and 16 guests

cron
highfalutin