Q9s on button

[Irieguy]

[ QUOTE ]
Yeah it is pretty boring, I just want to know exactly what to do. Against the following call ranges (that are wayyy too loose IMO, 55+,ATo+,A8s+,KQs, pushing is almost breakeven). If they get to the following range (66+,ATs+,AJo+), which is Still tighter than some may be, it becomes +.2%.

In any case I feel that the evidence suggests that it's appropriate to make some kind of raise, and that raising to 400 or so is the right play. Whenever simply opening allin has such a good chance of being +EV, it pains me to simply fold my hand.

In any matter, I don't believe it's of the utmost importance to not fold here. It's hard to prove mathematically because its not just some push/fold situation, but I suspect that it's correct to raise something. Can anyone prove me wrong?



[/ QUOTE ]

I don't know if I can prove you wrong, but I see a potential flaw in the logic "if there's a good chance pushing would be +EV, folding can't be right."

The difference between pushing and raising when you know you'll have to fold to a re-raise is quite large.

All of the math behind the value of pushing incorporates the expectation you gain from sometimes being ahead, and sometimes winning even when you are behind. Obviously you lose all of this when you fold after VPIP.

If your opponents would only re-raise you with hands that beat you, the argument for making a raise would be stronger. But there are probably at least a few hands your opponent could hold which would fold to a push, but push against a small raise by you. (TJs comes to mind, or maybe a very small pair.)

You also have the problem of seeing a flop and being made to fold a better hand, or being trapped by a better hand that wouldn't have extracted all of your chips with a different preflop action.

In other words, by making a small raise you introduce into the EV equation a lot of possibilities that don't exist when you push. You become much more likely to lose a "small" amount, but still susceptible to losing everything. You are also allowing your opponents an opportunity to outplay you... even if they do it by accident.

So, I think that in order for a raise to be correct here, your opponents would have to be very unlikely to push with a worse hand, very unlikely to stop-n-go you, very unlikely to bluff at the pot after the flop, and willing to fold often to a small preflop raise. These circumstances sometimes exist, and I would sometimes raise with this hand here.

But, I think folding preflop would be more correct than raising more often than not. If I'm wrong about this, I don't think it's because of anything that push/fold ICM calculations can prove.

Irieguy

[Roman]

yup, thanks for saying what I was way too lazy to type out.

[curtains]

Well my point when I say that "folding" can't be right because pushing seems +EV, implies that pushing is superior to folding. However as much as I love to grab the +.2% or +.3% situatons, this is a spot where my large stack can seriously allow me to expect greater +EV spots in the future. This combined with the fact that I don't know just how tight they are going to be, makes this a spot where I'm willing to not just move allin for 225 chips. It MAY be very slightly +EV against the right opponents to just push, but it's really pushing it in this spot.

My next logical thoguht was to figure out a reason for why making a normal raise would be appropriate. I'm sure its ok and I would definitely do so against some opponents, but it's probably a situation where you can just go either way depending on your feel of the opponents.

[tigerite]

For sure, if the BB is quite loose, and quite aggressive on the flop or unlikely to fold bottom pair type, then I'm folding here. But against a thinking, good player, who won't push pf with ~15bb or stop and go on a flop containing ~6bb for ~12bb (and especially with hands like JTs).. which I think is a lot (I certainly wouldn't do it) then the raise is absolutely fine and the right play.

But no, this isn't a carte blanche to raise every time or something. I certainly wouldn't and it is read-dependent. But so are many, many moves I make.. as it should be.