Quote:
Originally Posted by reverie
i imagine for a lot of people the question
will be "can i trust what this is suggesting about his likely range?"
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.
Quote:
Originally Posted by reverie
Does your "inference engine" discriminate based on relative stakes or
between full ring and 6 max? If not, how about some filters?
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.
Quote:
Originally Posted by reverie
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?
By a polarized range, do you mean a range with a hole in the middle of it?
Quote:
Originally Posted by reverie
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.
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".
Quote:
Originally Posted by reverie
Do more recent hands in the db have more influence on range weighting?
Not at this time.
Quote:
Originally Posted by reverie
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...
Yes, that's a good suggestion. The hand reviewer would benefit from a search feature. I've added it to my to-do list.
Quote:
Originally Posted by reverie
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.
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.
Quote:
Originally Posted by reverie
I also caused at least two crashes playing
around.
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!
Quote:
Originally Posted by reverie
I read that you want to support multiple
panels to better use space. This + user friendliness = awesome.
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.
Quote:
Originally Posted by reverie
Stats do not appear in the hand reviewer for
me.
Thanks. Fixed in 2.1.1.27. :-)