Save up to 50% during The A-Game Plan Week
×

getting a ballpark estimate of the EV of a call (new and improved proper title)

Posted by

Posted by posted in High Stakes

getting a ballpark estimate of the EV of a call (new and improved proper title)

Posted this in HS as I figured this would be where people (might) have the biggest sample/largest experience. So, here goes. We're regularly put in spots where we know raising is +EV and can even estimate fairly decently what the EV should be. To simplify, let's say we're looking at a preflop 3b or 4b. But we also have an alternative which should also be +EV given odds and our hand strength vs villain's range, which is to just call (with or without position). Obviously in this case position and stack depth will play a big part as an advantage or disadvantage depending on spots. But how do you estimate how much you're making with a call?

CG players like Tyler Forrester have huge databases to work on which is awesome but in MTTs stack depths and opponent types vary so wildly it's kind of difficult to accumulate very significant samples for both options and compare them. When I study, I try to give myself some realistic value of R given position/lack thereof etc and go from there, then play based on what "seems" about right while at the table. Do you guys do something similar? Is this as problematic for you? Be it as a CG or tournament player, we always want to get it right. As tournament players, do you factor in stack utility? How often do you find yourself saying "you know what, shoving now and getting this pot here fairly often is good, I don't really want to commit this much more of my stack and fold most flops with this particular holding"?

Any tips on approaching the issue are appreciated as well as the usual constructive discussion :)

Loading 3 Comments...

Be the first to add a comment

You must upgrade your account to leave a comment.

This thread has been locked. No further comments can be added.

Runitonce.com uses cookies to give you the best experience. Learn more about our Cookie Policy