blonde poker forum
Welcome, Guest. Please login or register.
June 04, 2024, 06:06:26 PM

Login with username, password and session length
Search:     Advanced search
2272886 Posts in 66759 Topics by 16723 Members
Latest Member: callpri
* Home Help Arcade Search Calendar Guidelines Login Register
+  blonde poker forum
|-+  Poker Forums
| |-+  Poker Hand Analysis
| | |-+  Sunday Million BvB
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: 1 [2] Go Down Print
Author Topic: Sunday Million BvB  (Read 2437 times)
MC
Super
Hero Member
*****
Offline Offline

Posts: 6304



View Profile WWW
« Reply #15 on: October 23, 2012, 07:58:03 AM »

open jamming here is pretty horrible. r/f slightly > fold >>>>>>>>>>>>> jam

this
Logged

"Success is not final, failure is not fatal"
http://www.atkinator.net ..... @epitomised
Pinchop73
Hero Member
*****
Offline Offline

Posts: 1438


View Profile
« Reply #16 on: October 23, 2012, 08:58:56 AM »

Think the given calling range is too wide, something more like 66+ A8o+ A6s+ KJs+ KQo. Either way open jamming here is pretty horrible. r/f slightly > fold >>>>>>>>>>>>> jam

For what reason is it horrible?

It's +2bb cEV (10% of stack), with a 6.6% chance of being called by a range were 27% against?

What is the non mathematical theory that makes this horrible in 2012? (Not pointing this question squarely at Thigh btw, its open to the floor.)
Logged

First they came for the nits, and I did not speak out because I was not a nit
MC
Super
Hero Member
*****
Offline Offline

Posts: 6304



View Profile WWW
« Reply #17 on: October 23, 2012, 10:52:23 AM »

Because it's a terrible line.

Do you think the Heads Up Hyper Turbo heroes jam K high every hand 17bbs deep because it's borderline profitable?
Logged

"Success is not final, failure is not fatal"
http://www.atkinator.net ..... @epitomised
Dubai
Hero Member
*****
Offline Offline

Posts: 6040


View Profile
« Reply #18 on: October 23, 2012, 11:39:13 AM »

Think the given calling range is too wide, something more like 66+ A8o+ A6s+ KJs+ KQo. Either way open jamming here is pretty horrible. r/f slightly > fold >>>>>>>>>>>>> jam

For what reason is it horrible?

It's +2bb cEV (10% of stack), with a 6.6% chance of being called by a range were 27% against?

What is the non mathematical theory that makes this horrible in 2012? (Not pointing this question squarely at Thigh btw, its open to the floor.)

Already shown the 6.6% is way way higher and being +ev doesnt always mean optimal. Obviously whenever we get dealt an above average hand bvb its +Ev to shove any amount, doesnt make it optimal.

Noone mentions card removal either which does have a decent effect on calling ranges- some "interesting" reads here about how significant the effect is

http://forumserver.twoplustwo.com/87/high-stakes-mtt/q6-sb-11-12bb-effective-arguments-folding-1255043/index2.html
http://forumserver.twoplustwo.com/87/high-stakes-mtt/simple-bounty-spot-brawl-858658/index6.html
http://forumserver.twoplustwo.com/36/stt-strategy/lt-card-removal-bunching-effect-simulation-321075/
« Last Edit: October 23, 2012, 11:44:03 AM by Dubai » Logged
buffyslayer1
Full Member
***
Offline Offline

Posts: 195


View Profile
« Reply #19 on: October 23, 2012, 12:45:44 PM »

Having chips (even 20bb stack) deep in the sunday million is so vaulable. People are so bad they gift you chips, this is not the 100r where you need to take every edge.

r/f is optimal anyway, give the risk of busting and BvB people dont give you credit even for a big shove. Even a fish knows you dont jam AA here for example
Logged

cambridgealex
Hero Member
*****
Offline Offline

Posts: 14876


#lovethegame


View Profile
« Reply #20 on: October 23, 2012, 02:51:23 PM »

Its not even 17bbs, it's 70k at 1500/3000 which is 23bbs! It's a ridiculous amount to jam with K5o. So so spewy.
Logged

Poker goals:
[ ] 7 figure score
[X] 8 figure score
Pinchop73
Hero Member
*****
Offline Offline

Posts: 1438


View Profile
« Reply #21 on: October 23, 2012, 03:49:08 PM »

Thanks for the links Dave, really interesting. I remember reading a similar thread by HU_15 regarding a jam by DJK123 into him. That thread was very interesting too, although now quite old.

After reading peoples opinions, I'm beginning to think that my jam might have been an incorrect decision. :p :p  #understatement

Seriously though, 'knowing' other peoples opinions is all well and good, but I would far prefer to understand the 'why' I shouldn't be taking these +ev spots.

Risk vs Ruin game theory I guess
« Last Edit: October 23, 2012, 04:15:22 PM by Pinchop73 » Logged

First they came for the nits, and I did not speak out because I was not a nit
youthnkzR
Hero Member
*****
Offline Offline

Posts: 2406


View Profile
« Reply #22 on: October 23, 2012, 06:08:29 PM »

raise / fold > fold > call >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> jam
Logged
discomonkey
Sr. Member
****
Offline Offline

Posts: 316



View Profile
« Reply #23 on: October 24, 2012, 05:52:55 PM »

Your calling ranges for villain are miles off imo. You have put in him folding AJos, id say he is 1000-1 to fold that

4 s+, A2s+ A7os+ K9s+ KTos+ QTs QJs- is probably a more realistic range

i def disagree that random snug villains will be calling off the bottom 20% of that range vs a 23bb shove... i would remove qts, qjs, qjo k9s, kts, kto and some other other hands he might fold like the low axs and kjo/kqo

a more realistic range imo for described player is 44/a7s/a9o/kjs/kqo

ps dont shove just raise/fold vs this knid of opponent
Logged
skolsuper
Hero Member
*****
Offline Offline

Posts: 1510



View Profile
« Reply #24 on: October 24, 2012, 06:18:38 PM »

Think the given calling range is too wide, something more like 66+ A8o+ A6s+ KJs+ KQo. Either way open jamming here is pretty horrible. r/f slightly > fold >>>>>>>>>>>>> jam

For what reason is it horrible?

It's +2bb cEV (10% of stack), with a 6.6% chance of being called by a range were 27% against?

What is the non mathematical theory that makes this horrible in 2012? (Not pointing this question squarely at Thigh btw, its open to the floor.)

Already shown the 6.6% is way way higher and being +ev doesnt always mean optimal. Obviously whenever we get dealt an above average hand bvb its +Ev to shove any amount, doesnt make it optimal.

Noone mentions card removal either which does have a decent effect on calling ranges- some "interesting" reads here about how significant the effect is

http://forumserver.twoplustwo.com/87/high-stakes-mtt/q6-sb-11-12bb-effective-arguments-folding-1255043/index2.html
http://forumserver.twoplustwo.com/87/high-stakes-mtt/simple-bounty-spot-brawl-858658/index6.html
http://forumserver.twoplustwo.com/36/stt-strategy/lt-card-removal-bunching-effect-simulation-321075/

Wrong.
Logged
strak33
Sr. Member
****
Offline Offline

Posts: 830


View Profile
« Reply #25 on: October 24, 2012, 06:39:31 PM »

Its not even 17bbs, it's 70k at 1500/3000 which is 23bbs! It's a ridiculous amount to jam with K5o. So so spewy.

In the money in the sunday million aswell!
Logged
matfrankland
Newbie
*
Offline Offline

Posts: 15


View Profile
« Reply #26 on: October 25, 2012, 09:07:33 PM »

i'd also r/f pre, you keep using the term "mathematically correct" it is mathematically unexploitable but can't be either mathematically in/or correct as there are other factors to consider. For instance with this logic open jamming aces from the button with 100 bigs would be "mathematically correct" but you'd never do it. It's a mathematically unexploitable play but that doesn't mean we can't find a more optimal line to take in order to increase long term expected chip profit. Hope this helps and isn't too rambley, seems very rambley
Logged
Rupert
:)
Hero Member
*****
Offline Offline

Posts: 2134



View Profile WWW
« Reply #27 on: October 27, 2012, 01:32:43 AM »

You guys know the Sunday Million is really soft right? and you don't want to bust it so you get to play with lots of fish?
Logged

Pages: 1 [2] Go Up Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.179 seconds with 20 queries.