Facing a Raise OTT

[wangtangkiki]

I can't find out how to add my opponent raising the turn after I bet to the filters.. I've going to "Actions and Opportunities" > "Turn" > "Turn Actions Encountered With Sizes" and I typed in the sizes for "Facing Turn 2Bet" and it just doesn't filter at all.. I'm probably doing something wrong.. I selected a 2bet between 2 and 50.. then 20 and 50.. and both times, they eliminated 0 of the hands I am currently looking for.. (Hands where I had TPTK and Cbet flop and turn)


How do you put in "Facing 3bet" or "Facing Raise on the Turn" ?

[WhiteRider]

It doesn't look like those filters are working correctly - I will report this to the development team to be fixed.
Thanks for bringing this to our attention.

[COKE_MAN]

Has this been looked into? I came here to ask basically the same question, but for flop, turn, or river with an exception...

I am looking for NOT facing a raise. When I enter the filter for facing a F,T,orR 2bet, I get correct hands. When I "NOT" it, I get nothing. Basically looking for hands where I bet 3 streets and never get raised. I know they are there, I can see them if I manually go through the hands without putting in the "not face raise" filters.

[kraada]

These filters should have been fixed. You should be able to use NOT() on them, just remember to make sure to add that you saw the street in question otherwise you'll get hands where you didn't see the street (because it's true if you don't see the river that you don't face a raise there).

[COKE_MAN]

Still not working unless maybe I am selecting the wrong filter.

I want hands where I bet flop, turn, and river but never face a raise on any of those streets.

The filter that I select for each street is: Actions and Opportunities->Facing Flop Bet->"Flop 2bet(First Flop Raise) Between...." then I Not() that for each street (replacing Flop for Turn etc).

Is the 2bet not what I am looking for here? I assume when I bet and they raise is the 2bet. Or is PT4 counting my bet as "the first flop raise?"

[WhiteRider]

You're right - the first "raise" is the 2Bet.

However, if you want to rule out all 2Bets faced then you shouldn't use the "between" option.
In Actions and Opportunities - Flop, go to Flop Opportunities and select 'any raise opportunity', and then NOT that.

(If you specify that you "bet" then that should work fine - if you don't specify that you bet then you'd need to select just 3Bet, 4Bet and 5Bet+ so as to rule out facing a "bet" rather than a raise.)

[COKE_MAN]

I think I see what you are saying WR. Since I bet the flop, if I have no opportunity to then raise, that would mean my initial bet was not raised.

But why won't the between options work? Seems like Not Facing a 2bet between .01 and 200bb should be the same as not facing a 2bet

[kraada]

You could still face a raise if you bet, one player raises and a third player 3bets.

[COKE_MAN]

Ok, WR's method worked just fine. Thanks

@Kraada: Are you saying that's why the in between filters won't work here? I think I see what you mean in that if I bet, one player 2bets, and another player 3bets, then I would face a 3bet and not a 2bet so the filter would not catch it. However, throwing out the cases like that, why would it not work when there is only one raise (2bet)? Is it just a semantics thing? To me, "NOT facing a 2bet between .01 and 200bb" means that I faced a 2bet of 0bb (ignoring the upper bound) and since a 2bet of 0bb is not possible, that equates to no 2bet. I can, however, see that the action filter probably looks for actions flagged as a 2bet and then applies the between filter. So, in that case, it will look for 2bets and then for the amounts and since there are no 0bb 2bets in the database, it returns no records. If that is the case then I would say it is working as expected. Now that I type all that out, if this is in fact how it works, then I will say that my original thinking was incorrect and the current implementation makes more sense.

[kraada]

Since the field is numeric in the database it is set to 0 by default - so 0 should in fact be times where you don't face a 2bet.

I tested on my database and that's exactly how this filter does appear to be working for me.