Tournament stack sizes

[K1K0]

Hi,

I'm making reports for analyzing short-stacked SnG bubbles. What I want to know is if it is possible to make a column that shows all the different stack sizes before the hand started and the positions of the players. It would look something like this...

CO: 5000, BTN: 3500, SB: 2500, BB: 9000

I already made a stat that shows the position of the selected player and amount of players in the hand, but I don't know where to look for the stack sizes of the other players and their positions.

If I had the stack sizes and positions of the other players at the table, I would be able to make the above column.

[WhiteRider]

No, you can't yet get information about specific other players in a hand.
I think the closest you can get to that at the moment is to get the effective (shortest) stack:
tourney_holdem_hand_summary.amt_p_effective_stack

[K1K0]

Hi White,

I was just wondering if there are plans to add the stacksizes and positions of the other players in the hands to the db anytime soon. This would be so helpfull.

Thanx

[kraada]

Their stack sizes are already in the database, it's not that the data isn't there, it's that there isn't, currently, an easy way to get at it. I hope as well that access to Villian's information becomes easier to access, but I'm not sure how soon that will become available.

[K1K0]

You say that there is no EASY way to get it. Does this imply that there IS a way to get it? If so, could you explain how?

[kraada]

Not from PT3, but if you know PostgreSQL yes.

The holdem_hand_player_detail table holds all of the starting stack sizes.

Let's say you want to know all of the stack sizes in hand # 2.

select player, amt_before from holdem_hand_player_detail, holdem_hand_summary where holdem_hand_summary.id_hand = holdem_hand_player_detail.id_hand and holdem_hand_summary.hand_no = 2.

This will print out all of the different stack sizes. Then to figure out whose is whose you need to also join to the player table and get the player names. It adds up to a complicated query and there's no way to get that information at this point in time directly from the PT3 interface.

I do hope it becomes available at some point, though.

[K1K0]

Ok, thanx, I'll take a look at it.