btw the Pokerhand.org format works for cardrunnersEV. Thanks for that!

in the hand reviewer when you click calculate, the equity calculator comes automatically loaded with inferred hands. are those inferred hands specific to THAT opponent?

also I just like to say that the more I play around with your soft the more I like it...

After you click "Edit statistics", on the left is a list of all of the stats that will be in that stat block. Add as many stats as you want to display in the stat block. They will all be "VPIP" initially.

Click on one of the "VPIP"s on the left. Then, on the right hand side look for where it says "VPIP" in bold. That's a drop-down box that you can click to change it to another stat.

wow ! yes the drop down box appears when you click on it! ok got it now!
thanks for your patience.

Yes.

It pulls the information from the Player Analyzer tool, based on the player's first action in the hand.

Thanks! I'm glad you like it.

hud layout doesn't seem to be compatible with the "preferred seat" setting in pokerstars. is it necessary to manually rotate the hud stats every time?

I played around with this a lot yesterday and like the way you have implemented statistics and inferences. the ability to have weighted ranges auto input into the equity calc is a great thing. i imagine for a lot of people the question will be "can i trust what this is suggesting about his likely range?". Here are my questions with that in mind:

Does your "inference engine" discriminate based on relative stakes or between full ring and 6 max? If not, how about some filters?

Will it pick up on things like polarized 3 betting ranges, for example, or will it make incorrect inferences by assuming the tweener hands are in villains range bacause they are in some worse players range? If not, have you noticed any snagging points where it doesn't represent a range very well, even with a large db? Looking at my "hero" inferences chart, it seems most error prone with regard to how i play small pockets.

Do more recent hands in the db have more influence on range weighting?

Here are some other issues I wanted to raise:

I do like the overall simplicity and small footprint of the app but i feel the hand reviewer might be a little limited by the lack of any search function or hand filters. I wanted to bring up an unmarked QQ flopped set hand i played a few days ago Vs a nit and load it into the calculator...

Although the HUD has a lot going for it, its hard to arrange stuff so that it fits on smallish (tiled) tables. I have played around with this. Removed the stat headers, changed the arrangement etc. I tried an "L" shape and found that it filled in the rest of the square with the background colour even though i had set all background colours to transparent. I also caused at least two crashes playing around. I read that you want to support multiple panels to better use space. This + user friendliness = awesome.

Stats do not appear in the hand reviewer for me.

Thanks for letting me know. I'll try to fix that sometime this week, so you don't have to manually rotate the HUD every time.

I am confused. Does this work with HEM or PT? Or is it an alternative for those programs? Is it parsing all the HH files itself and storing the info in its own DB?

It's an alternative, although even HEM and PT users would benefit from the free equity calculator (which is similar to Poker Stove, but faster and with more features).

Yes.

It's designed to be a good first-order approximation that will save you time in most cases. Putting a player on a range is often subjective, and it's conclusions might not be the same as yours. That said, it's much more accurate than just plugging their VPIP or PFR in.

With regards to the number of players at the table, I carefully designed the inference engine to avoid using statistics or inferences that vary wildly depending on how many players are present.

By "relative stakes" are you referring to the stakes relative to the total amount of money in the tournament (i.e., is it early, close to getting a payout, or fighting for a better payout?), or are you referring to the relative stack sizes of the players involved?

There is always a trade off here. The more you filter and split up the data, the less data you have about a particular combination of circumstances.

By a polarized range, do you mean a range with a hole in the middle of it?

You have a sharp eye. Yes, small pocket pairs are the most difficult hands for it to draw inferences about.

The problem is that it's hard to write a reliable inference rule of the form: "I have observed the player raise hand X in this pre-flop situation, therefore he probably raises with 22 as well".

Not at this time.

Yes, that's a good suggestion. The hand reviewer would benefit from a search feature. I've added it to my to-do list.

D'oh. Yeah, that won't work. I had not realized that you could set the BackColor to "Transparent" (which is not actually transparent, as you have discovered). I will have to remove that as an option. In the meantime, please don't set the BackColor to "Transparent". ;-)

However! The good news is that transparency is supported. Please follow the instructions at Setting up HUD Transparency.

Assuming you are the user who sent me two crash reports, I believe those are fixed in 2.1.1.27. Thanks for the crash reports by the way; they really make it a lot easier for me to locate and fix the problem!

Multiple panels are already supported. :-) Panels are called "Stat Groups" in Poker Sleuth.

In the Stat Groups tab, click "New" and set up your second Stat Group however you'd like.

Next, in the Table Layouts, find the layout to which you would like to add the second Stat Group. Click "Edit", which will open the Table Layout Editor.

In the left pane, locate and click on the name of your second Stat Group. Then, click anywhere on the table in the middle pane. You will see a copy of the Stat Group appear for each seat at the table.

Position each copy of the Stat Group as you see fit. Also, check the Seat property in the right pane, to make sure that (for example) the stats for the player in seat 5 are actually shown near seat 5.

Thanks. Fixed in 2.1.1.27. :-)

ok just got the new version but i can't find the fold to donk bet stat to add to my hud display. I thought it would be under afq but it i can't find it.

ok from what i understand donk bet is a stat group of it's own. I still can't find it though.

The stat added in the newest version is "Donk Bet Fold vs Raise", which is how frequently a player folders their donk bet when confronted with a raise. It doesn't show up under any of the default Stat Groups, but you can add it wherever you would like using the Stat Groups tab.

If you'd like more detailed instructions, just let me know where you'd like to add it.

Thanks for the detailed answers.

Ah. I was making it more complicated.

The inference engine doesn't distinguish between stakes, so if the same player plays at multiple stakes and employs very different strategies at different stakes, that will indeed introduce some error.

In theory the inference engine can detect polarized ranges, but you'd need an absurdly large number of hands on an opponent for it to show up clearly. I don't think there's much that can be done about that; polarized ranges are by their nature hard to spot. Of course, if in a certain situation a player raises with only AA, KK, or 43s, that will be a lot easier to spot than if they raise with AA, KK, and JJ, but not QQ.

The inference engine explicitly models uncertainty. When it sees that a player has raised with AA and JJ, it will put a strong weight on that action being likely. It will also deduce, with slightly less weight, that the player would also raise with KK and QQ. As more hands accumulate, it will eventually start to find it a little odd if it never sees the player raise with KK or QQ and will very gradually reduce the weight on those inferences. Does that make sense?

(The above examples are chosen to be illustrative and not necessarily realistic)

Yes that makes sense.

If I see someone 3 bet AA, KK, 78s and 65s in a range comprised of roughly 6% of hands over a few hundred hands I can make a reasonable guess that they won't be 3 betting 99 or KQo all that much. If I had a 500k hand database there are going to be players 3 betting a similar range. If poker sleuth looks at our example villain, the rest of the database, and infers that he raises hands close to AA and KK and hands close to 78s but not much stuff in between those ranges then imo it is doing the job right.

it would be better if sleuth used holdem managers/pt3 database instead of making a new one, it would reach more people. I like the hands in the tray and you could make it mark hands in the database easily using that.

I got it figured out but can't promise that i will remember the next time i want to add a stat. Anyway any chance of you adding a stat for floating.?

Also how do i back up my sleuth db onto a storage device like a memory stick?

In the Poker Sleuth Options Window, go to the Database tab. It will tell you where the database is stored. You can click the "Filename to Clipboard" button to copy the full path to the clipboard.

You can copy the database like any other file, but be sure to exit Poker Sleuth before you do so. While you're at it, I recommend backing up the whole folder that contains the database.

when i downloaded this i by malwarebytes thingy quarantined a file or something. anyone else get anything similar?

Could you email the exact message and filename to me at support@pokersleuth.com, so I can report the false positive to malwarebytes?

i like the software-i don't understand what the +/- means for every stat. Can someone explain it? Thanks

Hey,

came across your software via this forum and wanted to give it a try, but I get an error message from your server when I click on Download, see below (pretty chatty, also!)

Tom




MOD_PYTHON ERROR

ProcessId: 15671
Interpreter: 'pokersleuth.com'

ServerName: 'pokersleuth.com'
DocumentRoot: '/home/agthorr/pokersleuth.com/html'

URI: '/dist/PokerSleuthInstaller-2.1.1.28.exe'
Location: None
Directory: '/home/agthorr/pokersleuth.com/html/dist/'
Filename: '/home/agthorr/pokersleuth.com/html/dist/PokerSleuthInstaller-2.1.1.28.exe'
PathInfo: ''

Phase: 'PythonHandler'
Handler: 'dist'

Traceback (most recent call last):

File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1537, in HandlerDispatch
default=default_handler, arg=req, silent=hlist.silent)

File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1229, in _process_target
result = _execute_target(config, req, object, arg)

File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1128, in _execute_target
result = object(arg)

File "/home/agthorr/pokersleuth.com/html/dist/dist.py", line 110, in handler
'-out', tmp_file_name])

File "/home/agthorr/pokersleuth.com/html/dist/dist.py", line 49, in check_output
process = subprocess.Popen(stdout=subprocess.PIPE, *popenargs, **kwargs)

File "/usr/lib/python2.5/subprocess.py", line 594, in __init__
errread, errwrite)

File "/usr/lib/python2.5/subprocess.py", line 1149, in _execute_child
raise child_exception

OSError: [Errno 13] Permission denied


MODULE CACHE DETAILS

Accessed: Mon Dec 27 22:25:28 2010
Generation: 0

_mp_301a2456cc26ca3bd2d87ee41f87bece {
FileName: '/home/agthorr/pokersleuth.com/html/dist/dist.py'
Instance: 1 [IMPORT]
Generation: 1
Modified: Fri Jul 2 20:43:45 2010
Imported: Mon Dec 27 22:25:28 2010
}