Changing Default Colums Value (Fold 3bet) ¡TST PROBLEM!

[parraka]

Hi people, a lot of time without making a question.
I have tried with Zandry adapt Turbo Scan Table to work with Fold to PF 3bet after raise for making the filter more accurate. These are the current default stats in PT3.

Fold to PF 3bet is (cnt_p_3bet_def_action_fold / cnt_p_3bet_def_opp) * 100

-1 sum(if[holdem_hand_player_statistics.enum_p_3bet_action='F', 1, 0])

-2 sum(if[holdem_hand_player_statistics.flg_p_3bet_def_opp, 1, 0])

Fold to PF 3bet When Raised is (cnt_p_3bet_def_action_fold_when_open_raised / cnt_p_3bet_def_opp_when_open_raised) * 100

-1 sum(if[holdem_hand_player_statistics.enum_p_3bet_action='F' and holdem_hand_player_statistics.flg_p_first_raise and not(holdem_hand_player_statistics.flg_steal_att), 1, 0])

-2 sum(if[holdem_hand_player_statistics.flg_p_3bet_def_opp and holdem_hand_player_statistics.flg_p_first_raise and not(holdem_hand_player_statistics.flg_steal_att), 1, 0])

In the first one we have Player 1 raises, Player 2 3bets, Player 3 folds. Player3 sums a Fold 3bet case, i dont want this.
In the second one we have Player 1 raises at button, Player 2 3bets, Player 1 folds. Player 1 doesnt sum a Fold 3bet case, I dont want this.

So, i need these second columns but without the condition and not(holdem_hand_player_statistics.flg_steal_att)
The problem is that this stat doesnt exist by default and if Zandry adds it to his software all of the users would have to have this new stat Fold 3bet After Raise (With or without steal) and it would be a total mess.

So, it would be easier if i can replace my default columns into:

cnt_p_3bet_def_action_fold = sum(if[holdem_hand_player_statistics.enum_p_3bet_action='F' and holdem_hand_player_statistics.flg_p_first_raise), 1, 0])

cnt_p_3bet_def_opp = sum(if[holdem_hand_player_statistics.flg_p_3bet_def_opp and holdem_hand_player_statistics.flg_p_first_raise), 1, 0])

Is this possible? Any alternative suggestion?

[WhiteRider]

No, you can't change the definition of built-in stats - these are protected to avoid complications.

[parraka]

I ll have to move to Holdem Manager, im tired of trying to fix developers fails.
I dont understad how doesnt exist Fold 3bet After Raise, you create one similar, but you include if its not a steal? Why?
This is not useful.

[kraada]

That's why we have the custom statistics! We do have Fold to 3Bet Preflop When Raised built in, and in PT4 we have Fold to Preflop 3Bet After Raise built in by default (and used in our default HUD layouts). We don't disagree that these versions of folding to 3bets is useful, it's just disingenuous of us to call a stat "fold to 3bet" that doesn't count when someone actually folds to a 3bet because of other unnamed (in the stat name) circumstances.

[parraka]

Cani have installed at the same time PT4 and PT3? I feel so comfortable playing with PT3 but i would like to take a look into PT4. I have read that importing hands is slow, is this real? For me this is so important.

[parraka]

Would i be able to play with my current database? Would i be able to use my actual customized stats?

[parraka]

We do have Fold to 3Bet Preflop When Raised built in

Yes, but it doesnt include Attempts to Steal, it doesnt have sense :oops:

[kraada]

You can use PT3 and PT4 at the same time. When you take into account housekeeping time we have found PT4 to be faster overall, but housekeeping is included in the import so the numbers appear slower as h/sec goes down but you end up having to spend less time with import + housekeeping.

There is a built in database conversion tool and PT3 HUDs do import into PT4 so you can convert your setup over with a minimal amount of interruption.

[parraka]

I only do update cache, i dont need anything else, i have a database huge (more than 10 millions) and it works perfect, with the cache updated obvious. The question is, is faster PT4 (importing + housekeeping (i dont know what is included in this housekeeping)) or PT3 (importing + update cache)?

[kraada]

By Housekeeping in PT4 I meant the cache - PT4's Import includes the equivalent of the PT3 cache update - whereas PT3 has them separate. With a 10M hand database you well know how long cache updates can take in PT3. In PT4 it's all done at import time so there is nothing else to do afterwards. This means you get lower raw hands per second (since all of the cache update time is included when it isn't included in the h/sec of PT3) but PT4's total time should be smaller than a full PT3 reimport + cache rebuild.