Questions about R stats

[kilipo]

Hi,

I have noticed thanks to a PT3 report that the fold to R float bet of my opponents is significantly higher than their fold to R Cbet (60% vs 38%). I find it reaaally surprising (especially the 60%), so could you please tell me if the folowing definitions of these two stats are ok?

fold to R float bet: the player cbet flop & turn, checks on the river and folds if the opponent bets on the river.

fold to R Cbet: the player check-call or call prefop, on flop & turn, then check-fold or fold on river.

Thank you for reading (and replying )

[WhiteRider]

I'm not aware of any problems with those stats.
It could be related to the number of opportunities - if 60% is 3/5 then it would only take one different action to make that 40% (2/5) for example.

However, it could be because of the type of actions involved. If a player CBets the flop and turn and then checks the river I guess they'll fold fairly often, especially if the opponent only bets when the board is scary. If a player has called both flop and turn CBets then I guess they will fold the river less often.

[kilipo]

Thank you for your answer. The number of opportunities is high (hundreds of opportunities for each stat) so it is probably because of "the type of actions involved"

[kilipo]

Hi,

I had a look at these two stats:
- Fold to R Float Bet
- Fold to Flop Float Bet

I have noticed that the expressions for "cnt_r_float_def_action_fold" and "cnt_f_float_def_opp_action_fold" are significantly different. Is that normal?

[WhiteRider]

I don't see "cnt_f_float_def_opp_action_fold" - is that a custom column?

[kilipo]

No. It is the numerator in the value expression of "Fold to Flop Float Bet"
((cnt_f_float_def_opp_action_fold / cnt_f_float_def_opp) * 100).

[WhiteRider]

Ah - I see what you mean.
Strictly speaking you can only make a "float" bet after calling a continuation bet on the previous street. Since this isn't possible for the flop (because there was no previous street to face a continuation bet) the database doesn't store a field for flop float bets. Therefore we need to define the situation in other ways, which is why the flop expression is more complex.