Stat for Effective Stacks (HUSNGs)

[Late Ariba]

I have only just started working with pt4 so shout this is already built-in

There doens't seem to be a stat to report results by effective stacks.
Ideally there should be an Effective Preflop Stack Size stat that offers the same reporting behavior as the Preflop Stack Size stat.

This would help with the analysis of hands or results for HUSNGs regardless whether we are the:
- overstack (e.g. HTs at PS with starting stacks of 500 each where we have 735 @10/20) or the
- understack (e.g. 235 @10/20)

but in both isntances at the same effective stack depth i.e. 13.25bb (and in this particular format never above 25bb)

Using the Preflop Stack Size stat is producing misleading results as it distributes the data into two different bb reporting ranges. In the above example results achieved @13.25 effective will reported into two differnt bands:
- 30-40bbs, and
- 10-15bbs



Although filters could be setup it means we have to run seperate reports and cannot report side side results similary to the Preflop Stack size stat.

In the same topic is it possible to manually set the granularity of the stack ranges? For example the image shows that I get a range of 2-5bb for the lowest stack range and it increases in steps of 5 or 10. Again this hinders analysis as it prevents any reporting at 0-8bb where the game moves to a push-fold mode. Different SNG formats required reporting at different bb ranges and most likely each player will have their own range preferences they to track results.

PS awesome software! definitively converting form hem

[Parket]

You can easily create it yourself :
min(live_amt_stack,2*live_amt_avg_stack-live_amt_stack) / live_amt_bb

'live_amt_avg_stack' however is currently missing as a built-in column, so you have to define it yourself : live_tourney_table.amt_avg_stack

I doubt though that you can use it to further group your results based on that stat.

[WhiteRider]

You can do this with custom stats. Parket has a nice idea, but for reports the "live" stats won't work as they are based on information from the previous hand (which doesn't fit with reports as there is no current or last hand).

To change the ranges that the preflop stack size is grouped into you will need to duplicate the "Preflop Stack Size" stat and the "val_p_stack_size" column which it uses and change the defined ranges within the expressions.
To make an effective stack version make another copy and in the column expression replace "tourney_hand_player_detail.amt_before" with "tourney_hand_summary.amt_p_effective_stack".

[Late Ariba]

You can easily create it yourself :
min(live_amt_stack,2*live_amt_avg_stack-live_amt_stack) / live_amt_bb

'live_amt_avg_stack' however is currently missing as a built-in column, so you have to define it yourself : live_tourney_table.amt_avg_stack

I doubt though that you can use it to further group your results based on that stat.

Thanks Parket this will be very useful to me anyway to track effective stacks during live play.

[tosr]

I've read this thread but am a bit unclear. As hyper players it would be great to be able to access stats from certain effective stacks during the game. A similar feature to "show stats for current blind level only" but for effective stats. for example 20-25bb 16-20bb 10-15bb 5-10bb 0-5 bb.
Will this be possible, and if not, can someone start working on it please

[WhiteRider]

You could build those as custom stats, but you'd need to build each stat for each range - we can't add range options like that to the HUD at the moment as it would mean splitting the cache down so far it would no longer be effective. This may be possible at some time in the future, but I doubt it will be in PT4.

[tosr]

OK thanks, it would be very useful, so hopefully one day!

[husngforfood]

You can easily create it yourself :
min(live_amt_stack,2*live_amt_avg_stack-live_amt_stack) / live_amt_bb

'live_amt_avg_stack' however is currently missing as a built-in column, so you have to define it yourself : live_tourney_table.amt_avg_stack

I doubt though that you can use it to further group your results based on that stat.

I want to create a statistic that shows effective stack in big blinds. Is there a reason I should use this complicated formula instead of "tourney_hand_summary.amt_p_effective_stack / tourney_blinds.amt_bb"? What about when creating statistics for certain stack depths? Can I just use "tourney_hand_summary.amt_p_effective_stack < X AND tourney_hand_summary.amt_p_effective_stack > Y" or should I replace "tourney_hand_summary.amt_p_effective_stack" with "min(live_amt_stack,2*live_amt_avg_stack-live_amt_stack) / live_amt_bb"?

[WhiteRider]

Your simple version is fine for reports - Parket's expressions are needed for use in the HUD if you want information about the current hand, but for reports your expressions are fine.

[husngforfood]

Yeah, should have mentioned that I'm creating statistics for a hud.

Using "live" stats makes sense for the effective stack statistic in big blinds. And if I understand correctly, the statistic will show misleading information during the first hand of every blind level.

What I don't understand is why can't I use the simplified formula in case of creating a column that, for example, counts times player raised at certain stack depth?