GOD must be expecting to get a flop c/r in quite often here?

the fact that he didnt stab his middle pair makes his attempted CR quite bad

yeah i doubt anyone would stab much here tbh. It looks insanely suspicious to not cbet an 8 high board in this spot, any nl2k reg would know pio cbets 100% so every reg should cbet 100% here given it's so easy to replicate gto in this spot.

well perhaps godofhu is one of the few that hasn't touched a solver. I wouldn't be suprised going off this hand...

On October 03 2018 08:09 Stroggoz wrote: yeah i doubt anyone would stab much here tbh. It looks insanely suspicious to not cbet an 8 high board in this spot, any nl2k reg would know pio cbets 100% so every reg should cbet 100% here given it's so easy to replicate gto in this spot. well perhaps godofhu is one of the few that hasn't touched a solver. I wouldn't be suprised going off this hand...

I must be massively out of touch (I don't really even play anymore), but would have thought solvers would actually cbet fairly infrequently on 864 as 3bettor there. What preflop ranges are you assigning both players or what solver ranges are there for this spot if you have any? What postflop sizings are you assigning both players?

Edit: By fairly infrequently I just mean a lot less than 100%, like maybe 50-70% ish

low flops do not hit IP that much, but OOP has 6 overpairs. 6x6=36 combos. looking at IP the only low hands are suited, like A8s, 87s, and pp's. suited combos are only 4 combos each, those broadway hands like KQ, AJo being 12 combos each, it's really connected broadway flops that OOP has more trouble cbetting.

It's common knowledge among solver uses that basically any 9 high flops or less in this particular spot is a 100% cbet spot because OOP's range is that much stronger. (apart from a few flops like 987).

Furthermore JJ is one of the best cbetting hands because it needs protection more than QQ-AA. if you put lots of sizes for cbetting, 99-JJ pick big sizes. (overbet as a cbet size sometimes).

Midian's right
It's a deep-ish spot
TT and say 50% JJ should flat pre

definitely not 100% cbet here
various sizes
+ Show Spoiler +

IP bets 50% or checks

50%
+ Show Spoiler +

50% locked, ip bets 50%, raises 3x and bet 75% jams river sizings

And these are tightish ranges
If I add more sooted hands like 96s 86s K7s + more offsuit broadways it goes down to 27%

In practice I think people add more suited hands as opposed to call QJo and shit deeper, but for the sake of the argument let's add them also
+ Show Spoiler +

JJ is mostly a check in all scenarios here

These are with basic turn+river sizes
it's possible you I gave it a lot more options there like 25% +pot it will change
by that it'd change from 30-50% to 100% cbet? seems unlikely

Perhaps the ranges in my Simple Postflop pack are massively off what people are actually doing, or even what they should be doing. Although, there isn't an SB v BTN pack so maybe this explains the difference. I just have the BB v Button ranges and I guess BB is a bit more "polar" if SB is still playing mostly 3bet or fold these days (Unsure if this is true these days either).

But against BB 3bet IP has basically 100% of 88,66,44,86s,75s,64s. Still has a good percentage of the JJ-99 region and doesn't have the missed offsuit broadways at 100% as they are choosing to 4bet a good percentage. IP also simply has a lot of hands that connect with pair or gutshot.

I'll try running the sim with these ranges and see what happens, be interested to see the ranges you're assigning for this spot

you can see mine
on the very left

Top one is OOp bottom one IP

solvers should have similar results btw
it will differ on the settings for next streets tho

Using the Simple postflop BB v BTN pack (Although this is based on 100bb stacks, 2.25x open and 3bet sizing is a bit smaller than used in actual hand). Gave 25%/50%/75% and 150% options to both players postflop

ill try messing around with ranges a bit. My sims have been using solver preflop ranges and all cbet 90%+ on low flops, but i was looking at BB as well. SB has a wider 3bet range and less overpairs %wise as a result, so it can be different for sure. slight changes in preflop range here can have drastic differences. even a slightly higher equity 3bet range can make it go from 50% to 100% cbet on flop

this is 2million hands of 5/10+ population frequencies in SB 3bet BU https://gyazo.com/f475a3eb5495467b042a584bc2b63034

On October 06 2018 09:47 LemOn[5thF] wrote: Midian's right It's a deep-ish spot TT and say 50% JJ should flat pre definitely not 100% cbet here various sizes + Show Spoiler + IP bets 50% or checks 50% + Show Spoiler + 50% locked, ip bets 50%, raises 3x and bet 75% jams river sizings And these are tightish ranges If I add more sooted hands like 96s 86s K7s + more offsuit broadways it goes down to 27% In practice I think people add more suited hands as opposed to call QJo and shit deeper, but for the sake of the argument let's add them also + Show Spoiler + JJ is mostly a check in all scenarios here

Is that the new GTO solver? the UI looks prettier than SP and PIO

On October 06 2018 23:04 Baalim wrote: Show nested quote + On October 06 2018 09:47 LemOn[5thF] wrote: Midian's right It's a deep-ish spot TT and say 50% JJ should flat pre definitely not 100% cbet here various sizes + Show Spoiler + IP bets 50% or checks 50% + Show Spoiler + 50% locked, ip bets 50%, raises 3x and bet 75% jams river sizings And these are tightish ranges If I add more sooted hands like 96s 86s K7s + more offsuit broadways it goes down to 27% In practice I think people add more suited hands as opposed to call QJo and shit deeper, but for the sake of the argument let's add them also + Show Spoiler + JJ is mostly a check in all scenarios here Is that the new GTO solver? the UI looks prettier than SP and PIO

Yeah nicer and simpler
Drawback is that it is simple, you need to get around the quirks

Like for 3 sizes you just put in "25,50,100" in one box
And it builds a tree with all of em
And why some results differ is that it has a default one size for turn+river
And you need to specify multiple ones to get more realistic flop results
And no preflop, but you're better off buying solutions for that anyways if you dont want to bother with the cliud server thing
It has everything the others do - nodelock, multiple sizes, database and I find it really snappy
And results are more or less the same

And costs $75 lifetime licence no restrictions on cores or anything


I got a group on Skype of some micro guys running sims, pm if you'll use it and wanna go in

On October 07 2018 08:57 LemOn[5thF] wrote: Show nested quote + On October 06 2018 23:04 Baalim wrote:   On October 06 2018 09:47 LemOn[5thF] wrote: Midian's right It's a deep-ish spot TT and say 50% JJ should flat pre definitely not 100% cbet here various sizes + Show Spoiler + IP bets 50% or checks 50% + Show Spoiler + 50% locked, ip bets 50%, raises 3x and bet 75% jams river sizings And these are tightish ranges If I add more sooted hands like 96s 86s K7s + more offsuit broadways it goes down to 27% In practice I think people add more suited hands as opposed to call QJo and shit deeper, but for the sake of the argument let's add them also + Show Spoiler + JJ is mostly a check in all scenarios here Is that the new GTO solver? the UI looks prettier than SP and PIO Yeah nicer and simpler Drawback is that it is simple, you need to get around the quirks Like for 3 sizes you just put in "25,50,100" in one box And it builds a tree with all of em And why some results differ is that it has a default one size for turn+river And you need to specify multiple ones to get more realistic flop results And no preflop, but you're better off buying solutions for that anyways if you dont want to bother with the cliud server thing It has everything the others do - nodelock, multiple sizes, database and I find it really snappy And results are more or less the same And costs $75 lifetime licence no restrictions on cores or anything I got a group on Skype of some micro guys running sims, pm if you'll use it and wanna go in

PIO works the same with sizes you write them down in that exact format, SP is slightly different.

the inputs for turn and river (cars, sizes, etc) should not affect the result on the flop since they are independant events afaik

can it run aggregate reports?

On October 07 2018 23:58 Baalim wrote: Show nested quote + On October 07 2018 08:57 LemOn[5thF] wrote:   On October 06 2018 23:04 Baalim wrote:   On October 06 2018 09:47 LemOn[5thF] wrote: Midian's right It's a deep-ish spot TT and say 50% JJ should flat pre definitely not 100% cbet here various sizes + Show Spoiler + IP bets 50% or checks 50% + Show Spoiler + 50% locked, ip bets 50%, raises 3x and bet 75% jams river sizings And these are tightish ranges If I add more sooted hands like 96s 86s K7s + more offsuit broadways it goes down to 27% In practice I think people add more suited hands as opposed to call QJo and shit deeper, but for the sake of the argument let's add them also + Show Spoiler + JJ is mostly a check in all scenarios here Is that the new GTO solver? the UI looks prettier than SP and PIO Yeah nicer and simpler Drawback is that it is simple, you need to get around the quirks Like for 3 sizes you just put in "25,50,100" in one box And it builds a tree with all of em And why some results differ is that it has a default one size for turn+river And you need to specify multiple ones to get more realistic flop results And no preflop, but you're better off buying solutions for that anyways if you dont want to bother with the cliud server thing It has everything the others do - nodelock, multiple sizes, database and I find it really snappy And results are more or less the same And costs $75 lifetime licence no restrictions on cores or anything I got a group on Skype of some micro guys running sims, pm if you'll use it and wanna go in PIO works the same with sizes you write them down in that exact format, SP is slightly different. the inputs for turn and river (cars, sizes, etc) should not affect the result on the flop since they are independant events afaik

I'll preface this by saying I've never used a solver, but from what I've seen in the posts here they work by creating a tree based on the allowed bet sizes, so it seems that allowing different sizes on the turn and river will give different results on the flop. It is essentially solving two different games when the bet sizes are different. I understand the way the solvers work is by creating a 'limit' game with the fixed sizings you input, and then solving that game.

On October 07 2018 23:58 Baalim wrote: Show nested quote + On October 07 2018 08:57 LemOn[5thF] wrote:   On October 06 2018 23:04 Baalim wrote:   On October 06 2018 09:47 LemOn[5thF] wrote: Midian's right It's a deep-ish spot TT and say 50% JJ should flat pre definitely not 100% cbet here various sizes + Show Spoiler + IP bets 50% or checks 50% + Show Spoiler + 50% locked, ip bets 50%, raises 3x and bet 75% jams river sizings And these are tightish ranges If I add more sooted hands like 96s 86s K7s + more offsuit broadways it goes down to 27% In practice I think people add more suited hands as opposed to call QJo and shit deeper, but for the sake of the argument let's add them also + Show Spoiler + JJ is mostly a check in all scenarios here Is that the new GTO solver? the UI looks prettier than SP and PIO Yeah nicer and simpler Drawback is that it is simple, you need to get around the quirks Like for 3 sizes you just put in "25,50,100" in one box And it builds a tree with all of em And why some results differ is that it has a default one size for turn+river And you need to specify multiple ones to get more realistic flop results And no preflop, but you're better off buying solutions for that anyways if you dont want to bother with the cliud server thing It has everything the others do - nodelock, multiple sizes, database and I find it really snappy And results are more or less the same And costs $75 lifetime licence no restrictions on cores or anything I got a group on Skype of some micro guys running sims, pm if you'll use it and wanna go in PIO works the same with sizes you write them down in that exact format, SP is slightly different. the inputs for turn and river (cars, sizes, etc) should not affect the result on the flop since they are independant events afaik

That's wrong afaik
When you solve flop it solves the remainder of the tree as well, including the options you give it
They aren't independent

none of the solvers are actual NL GTO nowhere near it
You are solving a simplified game, but a game that runs over multiple streets nonetheless

On October 07 2018 23:58 Baalim wrote: can it run aggregate reports?

yeah for postflop
not sure how these work yet