Can stack sizes be recognized somehow w/ the HUD?

[rowhousepd]

Is it possible for PT3's HUD to somehow recognize a villain's stack size at the table? I believe w/ HEM, the abbreviated name ("Abb Name") can be color coded to his current stack size -- which is a nice little feature. Is PT3 "aware" of stack sizes as it imports hands? Thanks.

[kraada]

PT3 knows nothing about a hand until it is imported. The way the current caching mechanism works, it is not easily possible to get 100% accurate stack size statistics.

[zubs1aa]

PT3 knows nothing about a hand until it is imported. The way the current caching mechanism works, it is not easily possible to get 100% accurate stack size statistics.

I think we can safely assume that OP is making a feature request here and that I and others +1 it since there is no capability now....

[kraada]

And as you are well aware zubs, it is a feature request the development team is aware of. I just wanted to make it clear that nothing is known about a hand until it imports in response to the OP's question.

[zubs1aa]

And as you are well aware zubs, it is a feature request the development team is aware of. I just wanted to make it clear that nothing is known about a hand until it imports in response to the OP's question.

yes i'm aware of how it currently works. That does not prevent figuring out how to do it via a different method though....

[dj11]

Seems relatively straightforward for most of the players at the table.
Last hand imported will show starting stacks for each player.
That hand was played and the stack sizes will be changed via simple addition/subtraction of the antes/blinds/action and an expected stack size determined for the beginning of the current hand for all but a new player at the table. So the HUD could fairly easily have that info as a stat to chose from....IMO

What might not be so easy is to determine any tourney implications of a stack size as the tourney average is generally not easily found. But for ring play, it seems doable, easily.

[kraada]

The problem is that the statistics are built based on the history of all hands for a given player. My M workaround was to use a condition to check when the hand was imported - but now the cache updates on import, so when the cache is updated, the hand is recent and the data is retained in the cache for the future, thus leading to the numbers getting further and further from reality. There is currently no way to tell a stat to just look at the last hand, and adding this to the custom stats configuration methodology is not simple.

There was another workaround post but the comments in the thread lead me to believe that using it causes extremely long cache update times.

We've been investigating this issue as it is a highly requested feature and we are very much aware of people's desires to see these features implemented.

[zubs1aa]

What about building a hand number index for each tourney? As hands are imported index them 1 to X.

Or better yet index them based on the tourney number and the time/date of th ehand.

Concatenate tny number to the date/time codetime stamp. that would order them correctly>

[kraada]

There's already an id_hand and id_tourney - the problem is the way the custom stats and the associated query is formulated, it's not built for trying to grab data from just one hand, it grabs from groups of hands.

[zubs1aa]

There's already an id_hand and id_tourney - the problem is the way the custom stats and the associated query is formulated, it's not built for trying to grab data from just one hand, it grabs from groups of hands.

I always thought the ID hand was not useful other than to find a hand via the SQL joins etc.... It's not indexed sequentially or in any other way that has an intrinsically meaningful value.

regardless, i get why it wouldn't work today. But does that mean that other methods cant be used to solve this or other issues in the future? Or perhaps multiple methods at the same time?

Sometimes the innards need to be re-examined or re-done to meet future needs..and people need to look at whether the current guts are really functional for the long haul. I don' t know the answer to that analysis, but "it wont do it now"- while truthful - seems to leave out the possibility that it might be changed in teh future...