I get a lot of the same questions from users on how the syntax works, and usually I just refer them to ProPokerTools documentation on the generic syntax that can. In depth video covering everything you ever wanted to know about constructing ranges of hands with. Pro Poker Tools Question. No matter how many times I read the description of. Hand vs Range graphing compared to Hand vs Hand. Incorporation into HUDs It will be legal only if villain info is collected only from the user's hands, which will slow convergence down, but still it could be useful in the long run. Strategien und Hände diskutieren 5. I've removed it to avoid this happening again in the future. I noticed in the Advanced Range Constructor it shows all the possible wraps for a given board. Thread Tools Show Printable Version Email this Page. After looking at your message I think maybe I am asking the wrong questions. Syntax macros are a useful way to avoid typing in the same string of characters over and over again. Incorporation into HUDs It will be legal only if villain info is collected only from the user's hands, which will slow convergence down, but still it could be useful in the long run. Switch to Threaded Mode. I've run both for 5 minutes each with 8 GB RAM and a 2. This shows the satisfactory extent of imprecision of the desktop Odds Oracle Pro PQL interpreter. I think that is a good baseline assumption? On top of that it's quite a simple piece of software. Recall that the Evolution program generating them doesn't take positions, betting structures, stack depths, postflop play into account: Here are a few quick notes for those of you who have made extensive use of the classic ProPokerTools range of hands syntax:. In my example, the board is rainbow and unpaired, so minOutsToHandType hero,flop,straight,9 misses no wraps at all and the exact answers to the queries would be equal. The error is in the syntax and the input, not ppt imo. Basically the risk of getting raised if we cbet. RxRyOxOy — A double-suited hand with two pairs in it.