analyzing database

[pat3392]

I want to go through my database and see what hands certain stereotypical players show up with in certain situations vs. players that fit my stereotypical identify. For example, what hands a player with a vpip between 25/40 with a pfr of half his vpip and with a sample of at least 20 hands show up with when attempting to steal and are faced with a normal sized 3bet from either of of the blinds when normal stacked. Can PT3 do this?

[WhiteRider]

That sort of filtering isn't really possible with the current system but I will remind the development team about this kind of request as they are currently working on the filtering system for PT4. It's a pretty complex interaction of different sections of the database, so I'm not sure what will be possible, but I'll make sure it is considered.
EDIT: it may be possible to do something with a custom report filter using the Auto Rate icons if you have the players classified that way. We may be able to apply a filter based on the icon value to find players with certain stat value combinations, and then the hand situations can be filtered for mostly using normal filters.

[pat3392]

Could you please confirm if this can be done and if so, write instructions for me please?

[WhiteRider]

Kraada has done more of this kind of filtering so let's see if he has a filter for this when he comes on later.
Do you use Auto Rate?

[kraada]

The following set of filters can be used in the blue Filters section and will match your request. Make sure you uncheck filter on active player. And you'll want to be doing this in the Player Statistics section with the Hole Cards stat added (as well as Times at least).

This gets you VPIP between 25 and 40:

player.id_player in (SELECT player.id_player from player, holdem_hand_player_statistics where player.id_player = holdem_hand_player_statistics.id_player GROUP BY player.id_player HAVING (((( (CASE WHEN ( (sum((case when(holdem_hand_player_statistics.id_hand > 0) then 1 else 0 end)))) <> 0 THEN (((sum((case when(holdem_hand_player_statistics.flg_vpip) then 1 else 0 end))) * 1.0 )/( (sum((case when(holdem_hand_player_statistics.id_hand > 0) then 1 else 0 end))))) ELSE 0 END) ) * 100) BETWEEN 25 AND 40)))

This gets you PFR * 2 > VPIP:

player.id_player in (SELECT player.id_player from player, holdem_hand_player_statistics where player.id_player = holdem_hand_player_statistics.id_player GROUP BY player.id_player HAVING (((( (CASE WHEN ( (sum((case when(holdem_hand_player_statistics.id_hand > 0) then 1 else 0 end)))) <> 0 THEN (((sum((case when(holdem_hand_player_statistics.flg_vpip) then 1 else 0 end))) * 1.0 )/( (sum((case when(holdem_hand_player_statistics.id_hand > 0) then 1 else 0 end))))) ELSE 0 END) ) * 100) < 2 *(CASE WHEN ( (sum((case when(holdem_hand_player_statistics.id_hand > 0) then 1 else 0 end)))) <> 0 THEN (((sum((case when(holdem_hand_player_statistics.cnt_p_raise > 0) then 1 else 0 end))) * 1.0 )/( (sum((case when(holdem_hand_player_statistics.id_hand > 0) then 1 else 0 end))))) ELSE 0 END) ) * 100))))

Hands >= 20 is:

player.id_player in (SELECT player.id_player from player, holdem_hand_player_statistics where player.id_player = holdem_hand_player_statistics.id_player GROUP BY player.id_player HAVING (sum((case when(holdem_hand_player_statistics.id_hand > 0) then 1 else 0 end))) >= 20)

Attempt to steal is just:

holdem_hand_player_statistics.flg_steal_att

And facing a 3bet is just:

holdem_hand_player_statistics.flg_3bet_def_opp

Checking the size for that is done like the above filters but I don't have one handy for you to paste - hopefully that'll give you a good start.

[pat3392]

tyvm

I don't use autorate as I've never found a use for it, but if I did, would this process be a lot quicker for going over a lot of situations?

[WhiteRider]

If you don't already use auto rate (and neither Kraada or I do either) then there is no need if you're building the reports like this in the Holdem Cash Player Statistics section, and you'll probably find it takes longer to set up the rules you want and rate the players than to change the filters once you get used to working with them. The idea with auto rate would be once you had the rules set up and the players rated you could just filter for the icon value of the player type you're interested in, which would make the filters simpler.

[pat3392]

Facing 3bet/ PFR wasn't valid

Surely there's a simpler way to do it than this? How was it intended for users to find the definitions? Ask you guys every time? Or use the incomplete simple filters? I mean is their a list somewhere with all the definitions?

[WhiteRider]

The facing 3-bet filter is missing the "_p" street specifier:

holdem_hand_player_statistics.flg_p_3bet_def_opp

The database fields are listed in the Database Schema, and the queries are in SQL, which you can find more information about at www.PostgreSQL.org if you're interested.

The filters are being overhauled for PT4, but this manual mechanism will remain as it just isn't possible to build in every possible option that anyone may ever want - that's why we have the custom stat and report options.

[pat3392]

The PFR was also invalid

Fairly long guide, makes one appreciate the complexity of PT3.

I'd suggest to try and make PT4 more user friendly; custom stats/reports is what gives PT it's main edge, but it's rather complicated for the average user, adding buttons for us dummies would be great :D