Are people misapplying final table icm in certain spots?
Posted by timetopop87
Posted by timetopop87 posted in Mid Stakes
Are people misapplying final table icm in certain spots?
I was talking to friend and winning player the other day and about icm on fts in particular. His thoughts on the subject are that we should completely disregard chip ev and adjust to a stict $icm way of approaching things. We debated a spot i had the other day and would love some extra insight. Im afraid i cant post the hand history as im away from my db for the next week but i can explain the hand and ranges as i have already studied the spot.
Ft of a $20 bounty hunter on party. 6 players left, 5 players between 14 and 23bb, we have 22bb and massive chip leader with 120bb.
The chip leader has been very aggresive, mixing in 2.5x raises and open shoves from all positions. (on the last orbit he open shoved from the co with K8s vs 3 20bb stacks).
Payouts are as follows:
- $1900
2.$1350
3.$870
4.$600
5.$430
6.$300
So we come to the hand in question. Folds to Big stack in the HJ and he open shoves. We have AJo in the co with 22bb. Given the previous information i guessed he was open shoving the middle 20-25% of his range, raise- calling the top 7% and raise-folding a fair bunch of raggy hands.
I ran the spot in icmizer in $ giving him the mid strength shoving range i assumed and as i thought the spot was -$68. I then changed it to how many bb we would win given the same ranges and we win +4.72bb.
This is where i find it hard to interpret the data and how to proceed. My friend says stick to icm however in my mind im thinking sacrifing $68 seems fine to accumulate on average 4.7bb when i only have 22bb. Is my thought process flawed? Another thing to consider which is not quantifiable on icmizer, is how willing to take risks in bounty builders we should be as the payout structure is so top heavy?
Would be great to hear peoples thoughts, thanks.
Loading 4 Comments...
Be the first to add a comment
You must upgrade your account to leave a comment.
This thread has been locked. No further comments can be added.