Forum Replies Created
- MortenMarch 10, 2016 at 11:04 am
This is not possible with the current version 2.28 of Odds Oracle, but luckily as we speak ProPokerTools is working on a version 2.29 with exactly this feature So hopefully before long we can add hand samples given a specific range to PJMortenMarch 3, 2016 at 10:54 am
Thank you for the feature request. I understand what you mean. We will do our best to come up with a solution.
MortenMortenFebruary 24, 2016 at 12:59 pm
Good idea, we will implement a warning within one of the next releases.
MortenMortenFebruary 15, 2016 at 9:53 am
Great question! What happens is this:
When you run modules that are designed for HU (SH, BC, PS) then PJ pretends the other players never existed and therefore their bets are not taken into account.
So, in this situation UTg is wiped off the table and on the dead money remain (the blinds). UTG’s bets are not counted as dead money.
As you can see SOEQ_EQ is 26.48% and this is really the key number. It is calculated like this:
After we call the raise we will have 27.45 left. The HU Pot on the flop will be 2 * 24.25 + 0.25 + 0.50 = 49.25 (remember UTG does not exist). On the flop 27.45 / (49.25 + 2 * 27.45) = 26.36%.
From PJ just calculates the EV based on stack-off frequency on the flop and equity when stacking off.
In general PJ is not designed for these 3way spots (yet) but in some scenario our 3way tool can be beneficial: http://pokerjuice.com/3way/
So, check it out if you haven’t already done so 🙂MortenAugust 6, 2015 at 1:08 pm
At the moment, no…but the suggestion is good – and noted! 🙂MortenHi James, Very nice suggestion! I totally see this being an annoyance. Will see what we can do 🙂 MortenJuly 22, 2015 at 12:48 amMortenHi Alexey, Yes, this is clearly a bug. PJ is using dead cards when it should not. Will have that fixed immediately. Thanks for submitting! MortenJuly 21, 2015 at 1:44 pmMortenJames, could you email me the original PKJ (HH is not enough if you have ranges assigned). Then I will fix it right away! My email is firstname.lastname@example.org. Thanks.June 27, 2015 at 6:08 pmMortenOk, problems with upload should be fixed. Please upgrade to latest version of PokerJuice (v. 2.0.14). I have put the release notes in the PokerJuice Support group. If you have a post where PKJ/thumbnail is broken please do the following: 1. Send me email with link to the post in the community 2. Attach original PKJ (I cannot fix them without the original PKJ). My email is email@example.com. Then I will fix the posts right away so we can make PJC look pretty again 🙂 Thanks!June 27, 2015 at 6:05 pmMortenHi Viktor! Great video! And thanks for doing this 🙂 I agree with Sune that it would be interesting to see how we defend against check-raises, especially on the dry board (on the wet we should have no problems), but also against turn leads. I know that I keep the weakest of my top pairs in my check-back range to be able to defend against turn leads. Can we defend properly on turn if we cbet all our top-pairs? Looking forward to the next video!May 25, 2015 at 3:54 pmMorten@Ratatuj Very good point! Something to think about in close spots. I am not familiar with the rake structure at PLO10.May 15, 2015 at 9:41 pmMortenUps…sorry about that. It totally slipped my mind. I have finished my comment (and my dinner!) 🙂 “The flop raising range assigned by Morten seems to be very wide. He is definitively not raising bare 88, 99.” Well, I agree that optimal play is to flat bare 88,99 but this is PLO10. Also, preflop raiser checked reducing the risk of top-set significantly. But I totally agree that you should not bet this flop. That doesn’t mean you are giving up the hand, it just means that checking is better.May 15, 2015 at 11:11 amMortenWhat you should do is to try to narrow Villain’s range here street by street. Let’s go through that process while keeping it simple: Preflop Here Villain calls a bet from the button. He did not squeeze. You are correct to exclude a squeezing range from his calling range. However, I would probably widen both his calling range and his excluded squeezing range. Let’s use some thing like: Flop On the flop he calls. He does raise. What does that tell us? Well, we should start by assigning him the hands that he is not folding and then exclude the hands he is definitely raising (we still keep ranges simple): We think that he continues when he has Q high flush draw or better, the nut open ended, top pair with either spades or a decent straight draw and all made hands A8+. We also think given SPR and the fact that preflop opener checked that he raises: Top pair with nut flush draw, top two pair with either nut open ended or any flush draw and we think he plays all sets like the nuts and raises them. Turn We have defined Villain’s flop continuation range and we are now heads up with Villain on the turn: As you can see we have 40% against his range. If we look at Table Stats we can see that we need 37.69% to stack off with no fold equity. Let’s take a look at his range in Range Distribution: A = 76+ B = 88+,A8+:(dd,ss,J8+) C = * Sub range A are the hands that you were really worried about. He has a hand in this range 34.81% of the time. Range B are hands that we think his is not folding either. Range C are the hands that we think he folds. We now have a better understanding of how his range is composed and how often we can expect to be up against a straight. The advantage of shoving here is that we can make some better hands (naked A9/AT) fold and we also protect against the spade flush draw. Let’s combine sub ranges A+B and enter these in the SHOVE module: I set SOR = #B+. EV = $1.37. This is almost 14 big blinds which is not bad. So, I think best play on turn is just to get it in. You can download my PKJ here.May 11, 2015 at 6:43 pmMortenYes, great article Jonna! Decision trees are a great way to think about and calculate EV and something that a lot of people forget. When we play poker we (should) try maximize the EV of our entire tree and not just one sub branch. For instance a player who 3bets 20% preflop from BB and does it very profitably is not required to yield the same EV defending the flops when flatting as the player who never 3bets. Same with leading out on rivers. It weakens our check-calling range, but the important part is the total EV of our leading + check/deciding. The key is to maximize the combination of our options. Anyway, great initiative with this series of articles! Looking forward to the next one 🙂May 8, 2015 at 1:22 pm