by pat3392 » Fri Jun 15, 2012 9:54 pm
Colour coding by stat was one of the coolest features that PT offered over HM, and still does. imo, colour coding by range makes the HUD look "cheap" and un-professional. However, doing this via custom stats is a slow process, and sometimes I want my coding to only apply to one HUD(for example, on one HUD I may have the stats limp % and limp-fold %, with limp% colour coded by limp-raise% and limp-fold% by fold to cbet when limped and called iso, whereas in another HUD I may just have limp% colour coded by limp-fold%)
By adding this feature, PT4 will be easier and quicker to use, and also more versatile.
This idea is something that I've wanted to do myself for some time now, and would probably be hard for PT4 to implement but if it does, it will be mind blowing and give PT4 a pretty big edge over HM2. Set up a means of automatic colour coding based on the stat falling within a certain confidence interval. So let's say PT4 does some complex calculations to figure out what the mean and standard deviation is for that particular playertype(have it all customizable of course) within some user defined range that was pulled from their database, and than colour code it for the nearest confidence interval to 100 that it lies within; so perhaps for every 5% closer to 100% it goes a lighter and lighter shade of colour.
And for some quick technical support; I'm trying to make a total continuation bet stat, that is, the average of flop/turn/river cbet, but I'm not typing it right, I got this:
(((cnt_f_cbet / cnt_f_cbet_opp) + (cnt_t_cbet / cnt_t_cbet_opp) + (cnt_r_cbet / cnt_r_cbet_opp))/3) * 100
Where did I go wrong? And what would it have to be to make a total fold to cbet stat?