Two Plus Two Older Archives  

Go Back   Two Plus Two Older Archives > Limit Texas Hold'em > Micro-Limits
FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Display Modes
  #1  
Old 02-22-2005, 09:24 PM
parappa parappa is offline
Senior Member
 
Join Date: Jul 2004
Posts: 441
Default Calling the flop with middle pair.

Upon reflection, the flop call seems obviously atrocious, but I want to talk about an error in my thinking. This is what happens when I can't decide on the flop whether I think my hand is good or not. I end up just calling. Yes, I arguably have 2.5 outs instead of 2, but I'm really calling here because I think my hand might be good.

Should I:

a) realize that when I'm wondering, it's automatically a marginal situation and fold?
b) commit myself to raising or folding? (Here I would've folded)
c) just call like I did?

This is almost certainly a leak for me. I do this once or twice a session.


Party Poker 0.5/1 Hold'em (10 handed) converter

Preflop: Hero is SB with 8[img]/images/graemlins/spade.gif[/img], 8[img]/images/graemlins/diamond.gif[/img].
UTG calls, UTG+1 calls, <font color="#666666">1 fold</font>, MP1 calls, <font color="#666666">2 folds</font>, CO calls, <font color="#CC3333">Button raises</font>, Hero calls, <font color="#666666">1 fold</font>, UTG calls, UTG+1 calls, MP1 calls, CO calls.

Flop: (13 SB) 7[img]/images/graemlins/club.gif[/img], 5[img]/images/graemlins/spade.gif[/img], Q[img]/images/graemlins/heart.gif[/img] <font color="#0000FF">(6 players)</font>
Hero checks, UTG checks, UTG+1 checks, MP1 checks, CO checks, <font color="#CC3333">Button bets</font>, Hero calls, UTG calls, UTG+1 folds, MP1 calls, CO calls.

Turn: (9 BB) 8[img]/images/graemlins/heart.gif[/img] <font color="#0000FF">(5 players)</font>
<font color="#CC3333">Hero bets</font>, UTG folds, MP1 calls, CO folds, <font color="#CC3333">Button raises</font>, <font color="#CC3333">Hero 3-bets</font>, MP1 calls, <font color="#CC3333">Button caps</font>, Hero calls, MP1 calls.

River: (21 BB) K[img]/images/graemlins/heart.gif[/img] <font color="#0000FF">(3 players)</font>
Hero checks, MP1 checks, <font color="#CC3333">Button bets</font>, Hero calls, MP1 calls.

Final Pot: 24 BB
Reply With Quote
  #2  
Old 02-22-2005, 09:28 PM
toss toss is offline
Senior Member
 
Join Date: Sep 2004
Location: 2+2 Archives Digging up Gold
Posts: 1,327
Default Re: Calling the flop with middle pair.

I think calling the flop was the worse option. Raising is better. Folding would be best.
Reply With Quote
  #3  
Old 02-22-2005, 09:30 PM
Entity Entity is offline
Senior Member
 
Join Date: Jul 2004
Location: joining the U.S.S smallstakes
Posts: 3,786
Default Re: Calling the flop with middle pair.

I would checkraise this flop frequently.

Turn is fine, and river I'd bet and call a raise.

Rob
Reply With Quote
  #4  
Old 02-22-2005, 09:40 PM
Shillx Shillx is offline
Senior Member
 
Join Date: Oct 2004
Location: Frog and Peach Pub, Downtown SLO
Posts: 4,478
Default Re: Calling the flop with middle pair.

Heh the schooling effect worked for you fairly well on this flop, but making this call is really bad because you don't know what will happen behind you. If someone raises, you can't fold for another bet but your EV on the street as a whole will go into the tank.

Getting 22.5:1 you are looking at:

18(.0426) - 1 = - .23 SB with no raise
23(.0426) - 2 = - 1.02 SB with a raise

So if you knew that it would never get raised, this call isn't the worst thing ever (you would have to make up about 5.2 SB on the turn/river to make this call +EV) but with the chance that it will get raised, you would have to make back 23 SB (assuming it would get raised everytime)! No way this is going to happen on the turn/river.

Brad
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 05:48 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.