a few questions

[daiquiri]

first of all, congratulations for making this awesome program, it has some sick potential, I have been doing this kind of stuff by manually counting hands in my database after running various filters, lol. this is gonna make these researches so much easier and way more accurate because of the larger sample sizes.
ok a few questions for which I didn't want to start separate threads:
1. Any info about how to interpret the line explorer? something similar to the thread about preflop and postflop ranges? (edit: ok I'm figuring it out now, i think I get it. holy shit, this is sick! )
2. any chance you could introduce a progress bar for the queries? it would be an extremely useful addition imo
3. I noticed some weird bug or whatever it is: I ran a simple query on full tilt 3/6 lhe hands, I got all the nice fancy graph, then I ran the same query on my stars hands, and it was completely empty.. I did it a few times, same result.. It was a very broad one and I have a ton of hands so it's certainly not caused by not finding such hands on stars... any idea what could have caused this? (edit: absolutely no queries seem to run on my stars hands,all return empty sheets - on my fulltilt hands everything works fine)
4. if my db is full of datamined hands, will it not skew the results? eg if I run a query about a certain player type's c/c c/c c/c range, in the datamined hands, I won't have their holecards unless they win, which results in stronger than average c/c c/c c/c ranges in the query, or am I overlooking something?

and a suggestion: as an LHE player I'd love to see an option where the bet size related info can be disabled, eg. in the post flop ranges I won't see what percentage of the pot the bet was, I don't really need that info for lhe, it would be more useful to see the whole thing on one bar instead. I assume it would also speed up the queries somewhat.

[daiquiri]

re: my suggestion about disabling bet size related info - I just realized the pie chart accomplish just that, so nvm too bad the hand replay option doesn't work on the pie chart
wow I'm loving this and I've just started to play around with it. If only my pokerstars issue was solved.. I still can't retrieve any data from stars hands, not even from my own hands with my sn in "include only"

[VisionSupport]

I'm glad you like the program...

On question 2, the database server doesn't provide any indication of how long a query will take, so I don't have information to populate a progress bar. The number of queries remaining to complete gives you a high level view of progress for most tabs.

It's strange that the Stars filter doesn't work. I will PM you with a database query to help figure out what is going wrong. On my database I am able to filter Stars hands fine.

Hold'em Vision's results all have some degree of bias given that you only have complete information for hands that went to showdown. You do, however, have mucked hole cards regardless of whether a player wins or loses (at least on FT and Stars, probably most others), so the bias isn't extreme in either direction.

It's important on most tabs to enter your screen name in the Exclude Only box. Since your hole cards are known for every hand, including them will bias results strongly towards your playing style.

I'll put replaying hands from pie charts on my todo list.

[daiquiri]

Originally Posted by VisionSupport

It's strange that the Stars filter doesn't work. I will PM you with a database query to help figure out what is going wrong. On my database I am able to filter Stars hands fine.

Problem solved, here's what happened: in the drop down list, there are multiple 3/6 LIM, 5/T LIM options, and if I selected one of them it only worked for fulltilt, if I selected the other one it only worked for stars.. needs some bugfixing imo also, any chance to have the possibility of grouping stakes together, like in HEM's filters?

Originally Posted by VisionSupport

Hold'em Vision's results all have some degree of bias given that you only have complete information for hands that went to showdown. You do, however, have mucked hole cards regardless of whether a player wins or loses (at least on FT and Stars, probably most others), so the bias isn't extreme in either direction.

the problem is, you only see the mucked card if you have been involved in the hand. there are no mucked cards for observed hands -> datamined hands. So if someone has a large amount of mined hands, that should have a huge bias on the passively played ranges (calling hands are only shown if they win. If they call and lose, and the mucked hand is not shown, they are put into the "unknown - folded" category).

Originally Posted by VisionSupport

I'll put replaying hands from pie charts on my todo list.

cool, thanks!

[daiquiri]

some more suggestions (I hope you don't mind, I'm just pretty excited about this program atm, I'm blown away by it's potential tbh)
it would be nice to see some more complex board texture filtering.
For example, in the high cards field, would it be very difficult to introduce stuff like "lower than" or "higher than"? Like, the flop is made up of cards lower than an Ace, then the turn comes an Ace, I'd like to know how often various player types raise me with less than an Ace (or particular players, if I'm analyzing their game). So I'd like to set the flop highcards for anything lower than a particular card.
Similarly, it would be very useful to specify in some way when the flush comes in - eg, turn was only 2 flushcards, river was 3 flushcards, and I got raised - you get the idea.

+1 question: as I see, these queries don't seem very cpu intensive, my processor is hardly working during them, but my hdd is working like crazy. Do you think it would speed them up drastically if I had a solid state drive?

[VisionSupport]

Keep the questions coming... I'm happy to answer them all.

On board texture, have you tried the Detailed flop texture filters on the Post Flop Ranges and Flop C-Bet Ranges tabs? With the detailed filter, you can specify ranges for each board card. For example, you could specify that one card is an A while other cards are 8 or lower.

Flush cards can be specified for the current street only, but I'll add the previous street to my todo list. It makes sense to be able to filter by changes in flush draws.

You are correct that HV queries are data intensive vs. CPU intensive, so an SSD disk makes a big difference. I picked one up a couple of weeks ago and love it.