"stat" which just shows colour rather than value

[pt4pt4pt4]

You can improve upon the scheme i set up on my blog with colors only, if need be.

[pasita]

That's a clean looking interface, especially good if you don't wish to work with custom stats.

[pasita]

extranotes.png

(39.36 KiB) Downloaded 4557 times

Kind of happy how this is turning out. Displaying a pretty value oriented bet range on river, this guy has it when he bets. Getting the data from the notes to HUD would be pretty easy now but not sure if there's any reason to do that since the notes box is so versatile nowadays 8-) The colors are hard coded though.

[oracle3001]

How did you get that into the notes window? And is it put there automatically?

And are you willing to share the custom stat underpinning this i.e the bet river "strength"?

[pasita]

The stat is done outside of PT4 in a program I'm writing. I read all the river bets* from a player and the board from the DB (with an SQL query). Next, for each river bet, I compare the bettors equity to random cards** on that board, using the 2+2 hand evaluator under the hood. So if I have 100 riverbets from a player, I get 100 equities. Those are ordered and arranged to 10 bins (like 0-10%, 10-20%....90-100%). The more bets in a bin, the bigger value I give to the bin.These 10 values are normalized and arranged into a string (using digits 0-9), so in the pic you see the underlying string is something like 000111597. He basically never bluffs with missed stuff, maybe makes some merged range type value bets / bluffs but not enough to try to raise him off those.

Once the string is done, the program inserts (via SQL) the tags and the string to the players's notes. If a note does not exist it is created, if there's already a note, I insert to the top. For the actual data string I use a font I designed where digits 0..9 are represented by the different height bars. The colors are handled during the same process (and are mainly for fun).

Repeat for all the players in the db.
(To do: repeat for river raise, river 3!, maybe look at turn stuff...***)

* all the bets where I know his holecards. This may introduce a small bias, but since it's river and I mainly play FL, most bets get called anyway so I believe this should be fine-ish.
** random because I can't construct a range for the villain(s) in hand. Random should be fine to get this distribution, though... it's used to figure out his betting polarization, not exact value.
*** I can see some biasing problems here as there's one more street where the player can muck his weaker cards. Ideas appreciated.

I can publish the sql queries I used to put data into the notes if there's public interest and the officials here don't mind it... they seem to be a bit wary about using the db in unconventional ways :? Using the notes for stuff like this was more simple in PT3, although the rich text formatting does give some liberties (once you figure out how it's used). The only side effect I've noticed so far (doing all this so far in a backup db obviously) is that the notes tooltip doesn't synchronize with the data I insert before I actually click save in the notes box or restart the replayer window... PT4 seems to do some caching there. This doesn't really matter as the tool is run "offline" anyway.

As for my C source code,that would take serious cleaning before publishing... it was built on the go, starting from fooling around with the hand evaluator.

Was this worth it to get a few river stats? From the game perspective, most certainly not. For academic purposes, certainly yes... had to relearn a lot of C and learn a lot of SQL to get here.

Also, if anyone knows how to change the expression below to return 'asomas', not 'as', i.e. finding the first occurrence of 'om', I'd appreciate the help.
select substring('Thomasomas' from '%om#"%#"%' for '#')

[oracle3001]

Have PM'ed you pasita.

[pasita]

Also, if anyone knows how to change the expression below to return 'asomas', not 'as', i.e. finding the first occurrence of 'om', I'd appreciate the help.
select substring('Thomasomas' from '%om#"%#"%' for '#')

Note to self: have to use the non-greedy version.
select substring('Thomasomas' from '%?om#"%#"%' for '#')

[COKE_MAN]

For either of you brainiacs... does the 'lower opacity until mouseover' feature work with your blobs/dominoes?

Yes, that's how I have mine set.

[COKE_MAN]

Considering my skills of visualizing stuff (that's low) I'd love to see how you set up your dominoes :)

Top Row, Left side: Flop Cbet, Turn Cbet, River Cbet (green = high, Yellow = middle, red = low)
Bottom Row, Left Side: Flop fold to Float bet, Turn fold to Float or Probe, River fold to Float or Probe (green = high, Yellow = middle, red = low)
Top Row, Right side: Fold to Cbet flop, F2 Cbet turn, F2 cbet river (green = high, Yellow = middle, red = low)
Bottom row, right side: Float bet flop, float or probe turn, float or probe river (green = high, Yellow = middle, red = low)
A popup gives the values and times for each stat if I need more in depth info.

So for this player I see that he is about middle of the road on cbets F, T, and R. However, he is very high on folding to floats or probes. So that is a green light for me to float him more often. With in reason of course, since he is not blindly 2/3 barrelling. I think your ideal guy here would be green on flop and turn cbets, red on the river cbet, and a green for folding the river to floats. Rare though. On the flip side, if the guy was green all the way across the top for cbets and has a high-ish PFR stat, he is betting way too often and you can call him down more lightly.

His fold to cbet on flop and turn are middle of the road (not enough info for river yet), so I should use some caution in cbetting and not just blindly cbet air. He's middle of the road on floating flop, so it's not an auto fold when he does it, but I should use caution when continuing. He floats or probes turn fairly high so I can check some made hands to him and let him bluff. On the river, though, he rarely floats/probes so if he does it there, I am not buff catching.

I mainly did this to get a quick visual against the guys in my games that are constantly float betting or probing when the pre-flop raiser checks any street. It is an experiment to see if I can quickly assess those situations using visual indicators.

[pasita]

That is sweetness to eyes.