---

Poker Video: Pot-Limit Omaha by n0whereman (Micro/Small Stakes)

Just finished the video with notes. Some good information in there, particularly with regards to the 4-bet calling example. I had read about calculating the area under the graphs in Donkr's PLO From Scratch article (Bugs was the forum member who wrote it), but he didn't delve into the details.

So...I pretty much could make a big exel calculator to do that for me quicker, but I'd just have to punch in lots of numbers like the bounds for each area, change stack sizes if need be and what not? Is that plausible?

yeah you could do that - there's definitely a formula that can be made out of the stuff I wrote.

Thoughts on this as a 7.17% 3b range say btn v co (it is simple and there are some double ups but I figured it would do)... also what would be the best way to add hand types such as AxKx*x*y and KxQy9x7y?

4%!RRRR!RRR, A[9+][9+][9+]!RRRR!RRR, [99-QQ][99-QQ]!RRRR!RRR, $0g: xx!5, $1g: xx!3!4!5, $2g: xx!3!4!5!6

had to put a space in every : xx due to

Thoughts on this as a 7.17% 3b range say btn v co (it is simple and there are some double ups but I figured it would do)... also what would be the best way to add hand types such as AxKx*x*y and KxQy9x7y?

4%!RRRR!RRR, A[9+][9+][9+]!RRRR!RRR, [99-QQ][99-QQ]!RRRR!RRR, $0g: xx!5, $1g: xx!3!4!5, $2g: xx!3!4!5!6

had to put a space in every : xx due to

It's a good start, for sure. There's lots of not-as-well connected ss/ds hands (eg qt86) you could definitely throw in there too. If the CO is fairly loose, 7% is on the low side for a BTN 3b% imo.

It's a good start, for sure. There's lots of not-as-well connected ss/ds hands (eg qt86) you could definitely throw in there too. If the CO is fairly loose, 7% is on the low side for a BTN 3b% imo.

Agreed this is from a micro/small stakes perspective... there aren't too many people 3b'ing 10% but I am sure I will just work through various ranges. Thank you.

Agreed this is from a micro/small stakes perspective... there aren't too many people 3b'ing 10% but I am sure I will just work through various ranges. Thank you.

Oh I was thinking that this was you talking about what you would 3-b in that spot as the BTN. I do think that the range you have is pretty decent for a rando micro stakes guy 3-betting 7% otb.

I'm sure you'll be getting into discussions about this on future videos, but the key question here, unanswered, is "How do I determine if I have enough equity, 32%, on THIS flop, to call?"

It's really about counting outs, and I've been surprised at how weak I can be on the flop to get it all-in against an overpair. If I put my opponent exactly on AA** and I only flop a pair of 6s with 9876, then I have 11 outs(!), any 9876 to hit 2 pair or better. 11 outs already puts me at well over 40% equity, without include straight or flush draws I might have. I might hit my 2 pair and lose to an A on the river, but I am still waaaayy behind on the flop (pair of 6s vs As) , but with more than enough equity to get it all-in. (not like AA versus 66 on the flop in NLHE).

a pair is a nobrainer. if you have the rundown, a gutter some backdoor wrap potential and two backdoor flushdraws are normally enough.
for example 6789 w/ 2 bdfd on K35 has 32 % against bare aces

Hm... can't we just make the EV calc:
Frequency of call * (Potsize * AVG Equity - Flop call) = X
Then compare it to how much we had to call preflop.

IE...
.69*(201.5*.55-64.5)=31.9~
31.9-24.5=7.4~~~~~ bb

Also, accounting for rake is just a question of removing it from whenever we won the pot right?

Also, accounting for rake is just a question of removing it from whenever we won the pot right?

usually this is the approach

Just finished the video with notes. Some good information in there, particularly with regards to the 4-bet calling example. I had read about calculating the area under the graphs in Donkr's PLO From Scratch article (Bugs was the forum member who wrote it), but he didn't delve into the details.

So...I pretty much could make a big exel calculator to do that for me quicker, but I'd just have to punch in lots of numbers like the bounds for each area, change stack sizes if need be and what not? Is that plausible?

Is there an easier way of calculating this with the oracle? It is so clever, it should be able to do it for us, right?