Actors & aggressor strings

[josephlabarbara121]

Hi, just want to make sure my understanding of preflop implementation is correct:

str_actors_p: begins with whatever position is the first to VPIP regardless of whether its a bet or a raise; player position numbers are appended whenever they VPIP regardless if a call or raise.
Ex: Player in positions 2 and 4 limps, BTN raises, SB 3bs, player 4 calls, everyone else folds: str_actors_p is %42094

str_aggressors_p: only tracks players who make raises or 3b+; from the example, str_aggressors_p would be %809

Can you help me understand how the postflop versions work (str_actors_t, str_aggressors_r, etc.)?

Thanks so much!

[josephlabarbara121]

Had a few more questions pop up. Apologies!

1. Can you describe how the "actions" field within the lookup_actions tables are populated? What are the possible values? If you could kindly provide an example or two for how the actions field would be populated it be super helpful.

2. In the tourney_hand_summary table, are the fields "card_1" through "card_5" the flop, turn and river cards respectively?

3. Hole card information will come from the lookup_hole_cards table? I see there are flags in there like "flag_h connector", enum_pair_type. They don't appear to be used in any off-the-shelf columns but sound like they could be really handy. Can I ask for an explanation (or just documentation if it's available) about the values these fields take, what information is contained in them etc?

4. Field amt_pot_p (table tourney_hand_summary) is that the sum of blinds and antes ("preflop pot size")

Again, really appreciate the help! Thanks!

[Flag_Hippo]

Hi, just want to make sure my understanding of preflop implementation is correct:

str_actors_p: begins with whatever position is the first to VPIP regardless of whether its a bet or a raise; player position numbers are appended whenever they VPIP regardless if a call or raise.
Ex: Player in positions 2 and 4 limps, BTN raises, SB 3bs, player 4 calls, everyone else folds: str_actors_p is %42094

str_aggressors_p: only tracks players who make raises or 3b+; from the example, str_aggressors_p would be %809

That's correct although the '%' isn't used in the strings themselves - that is only used for pattern matching when using custom filters and/or statistics.

Can you help me understand how the postflop versions work (str_actors_t, str_aggressors_r, etc.)?

It works the same postflop as it does for preflop except that the aggressors string postflop does not start with the BB - it starts with the player who makes the first bet on that street. Checks are not recorded in the strings - only bets, raises and calls.

1. Can you describe how the "actions" field within the lookup_actions tables are populated? What are the possible values? If you could kindly provide an example or two for how the actions field would be populated it be super helpful.

This stores the actions a player took on each street where 'B' is bet, 'C' is call, 'R' is raise, 'X' is check and 'F' is fold. For example:

lookup_actions_p.action = 'RC' (the player raised as their first action preflop and called as their second action).

lookup_actions_r.action = 'XRF' (The player checked as their first action on the river, raised as their second action and folded with their third action).

2. In the tourney_hand_summary table, are the fields "card_1" through "card_5" the flop, turn and river cards respectively?

Yes.

3. Hole card information will come from the lookup_hole_cards table? I see there are flags in there like "flag_h connector", enum_pair_type. They don't appear to be used in any off-the-shelf columns but sound like they could be really handy. Can I ask for an explanation (or just documentation if it's available) about the values these fields take, what information is contained in them etc?

We have not published the schema like we did for PokerTracker 3 however the meaning of database fields with the same names haven't changed in any significant way from PokerTracker 3.

PokerTracker 3 Database Schema Documentation

Hole card lookup values are detailed here and there is more information on hand strengths in this post.

4. Field amt_pot_p (table tourney_hand_summary) is that the sum of blinds and antes ("preflop pot size")

Yes.