WarLoGhE

Hello Peter

How do you approach the issue with the fact that the solver will produce solutions with different accuracies?

First of all the solution will be more accurate if we save it as a 'full tree' as opposed to 'very small tree'. The difference is very small and probably negligible, so we can just skip this point. Also, I can only speak for myself but I certainly have not got the disk space for full trees. The last one I saved was 1.8 GB.

But the thing that is slightly annoying is the difference in accuracy we get if we choose a turn card and solve for the turn itself by using Tree --> Create subtree configuration.

We can see this by comparing the first picture (very small tree) with the second picture (solved on flop) below.

To me this difference seems significant.

Well... when I look at it now I'm not so sure if it matters. But fuck it, I spent 15 mins writing this post, I might as well just post it... xD xD xD

In 4bet pot BTNvsSB at 13 min mark PIO really likes to shove...? What do you think about this?

I might have gotten the ranges wrong. Picking a 4bet range isnt that hard but the calling range for SB is not that easy.

ffs why do you say this.. :P do you want to pay more?

Thank you!!! I will have to spend some more time trying to understand it... but, thank you.

I might just try and write a short script (loop) in Python.. :P could be fun

Surely, you are not a BIG fish? i dont get it

So lots of nice discussions, nicenice :D
but; can someone explain how the solver works?

so when people are throwing around the phrase "the equilibrium play here is to..." or similar they are saying "the perfect/unexploitable play here is to..."?

I like many things about this video, e.g. when you explain how the field will underraise flop and therefore the bet is more profitable than PIO suggests - or how they will reach the flop with a stronger range than PIO.

I would love to look at the ranges you use - they differ quite a lot from mine, which is a bit worrying :P Would posting them somewhere here on RIO be a possibility?

And may I ask how you create your ranges? (both for yourself and villain).

Realistically...

and potentially...

you're bang on with your videos! ;-)

good job, keep them coming.

I don't understand what the number behind a flop means (e.g. 3d9sQs:1.08) :-(

When I generated I saw it sometimes said the number 2 behind and I just thought that this meant that the generator had generated the exact same flop twice.

Thank you 🤗🙏

First of all - thank you for putting out great content.

43s around 25 mins:

You say something a long the lines of
"when the opposition doesn't 3bet enough we can raise profitably here".

How have you determined this? Do you compare your data to PIO? What kind of bet sizes, what kind of textures and against what kind of players is this the most true for in a situation like this with SB vs BB?

furthermore (after you jam the river) you say something like
"pio wouldnt shove here with 43s but regulars really struggle to defend correctly when they face a jam here, so expanding your bluff range here is profitable against he right regulars".

Again,how do you determine this?

I find this very interesting but in all honesty it doesn't really help me at all as a player. I understand that you can't go into full depth in each hand while playing, so I guess what I am really saying is that I would like to see an analysis of these hands so that we can fully understand why you do what you do because at the moment I am not getting any smarter :P

Maybe you could pause the play and do the analysis in between playing? Or you could do at the end of the video.

Great stuff here, keep it going :-)

this

The PIO-analysis is awesome.

Lovely stuff :)

Thank you for your answer.

I have both pdfs that you mention from Peter Clarke.

But as far as I know they dont have the ranges that I am looking for.

I'll check out the videos :-)

Great video :)

Love your videos, keep them coming.

If I could change one thing I would like to see 2-3 tables instead of 4, because at times it's a bit chaotic :)