New Tracking Software: Poker Maven

[VisualCSharp]

[ QUOTE ]
I'd like to see Ipoker added. How big is a massive hand history database?

[/ QUOTE ]

I coded support for PokerStars and Full Tilt Poker on databases of a little over 2000 hand histories. I guess huge and massive aren't the right terms. [img]/images/graemlins/smile.gif[/img] I would still like a larger sample than 2000, although I think 2000 is the minimum.

Here's some technical detail on the subject. There are a lot of strange situations that can happen in poker (as you all know) that don't happen very often. Things like side pots, split side pots, canceled hands, partial hand histories, uncalled bets, etc. all make the process of parsing hand histories a challenge because I have to be sure some of the hand histories cover these bases. PokerStars' hand histories led me to fix some things I didn't think about when coding Full Tilt Poker support, so I am pretty sure I have all the kinks worked out at this point. Excluding the HUD, implementing PokerStars support took less than a day.

[VisualCSharp]

[ QUOTE ]
i assume its texas holdem only atm? any plans on adding support for omaha/etc?

[/ QUOTE ]

Correct. The supported hand history formats are listed (and updated) at Features. I think implementing support for Omaha is definitely doable, but the differences in the game make it a challenging prospect. If I use the same database schema for all game types, it would mean tracking four hole cards instead of two, which would increase the disk space required by each record in the database. There's also the question of multiple pots (hi/lo) and hand history differences. It's definitely more doable than stud or razz but still a challenge. It is absolutely near the top of my future features list though.

[elklonko]

Prima support would be nice. Someone pls send him hand histories.

[VisualCSharp]

Eventually I would like to support at least as many sites as Poker Tracker does, starting with the bigger sites. The heads-up display is actually where most of the work comes in (images, database changes, default layouts, etc.) The parsing of the hand histories is not that difficult.

[VisualCSharp]

I have completed documenting the entire statistics database schema. You can download and read the documentation at http://poker-analytics.com/Documentation/Poker Maven Statistics Database Technical Documentation.doc

If you use Microsoft Word to view the document I recommend turning on the document map feature. Document map will make it easier to navigate around the different tables.

[rjacobs003]

[ QUOTE ]
[ QUOTE ]
Integrity check. What does PT do that you DON"T currently have built into the software (but I would assume you're focusing on for future versions?)

[/ QUOTE ]

I'm not sure what you mean by "integrity" but I'll definitely answer your question truthfully. Usually it is not in a company's best interest to list edges their competitors have over your own product, but I believe by me providing an honest comparison you can make better choices. It will also, of course, drive me to improve Poker Maven to go beyond what Poker Tracker can offer.

As a side note to this, Poker Maven has been in development for only a month and already supports many of the critical features the majority of users look for when considering a poker hand tracking application. I am estimating that implementing support for each poker room, including the HUD, takes 1-2 days per poker room (assuming I have hand histories to work from).

Poker Tracker edges:

- 18 hand history formats
- Tournaments
- Non Hold'em game types (I can't be sure but I think these are stored as separate databases?)
- Importing/exporting player notes
- Player auto-ratings
- Hand replayer
- Help system
- Other minor features

I'm not trying to design an application that functions exactly like Poker Tracker. Poker Tracker definitely has some great features, but also some features many people may not use. My focus at this point is providing the community with the features most people really need. I've been seeing a lot of interest in "fish lists," for example. When you boil it down, a "fish list" is nothing more than another report being run over statistical data. If I can gauge the types of statistics most people want to see used in a fish list I can create a fish report.

I am constantly reviewing 2+2's forums for new feature ideas. Poker Maven's default reports are very similar to Poker Tracker's own reports, with some additions. In the very near term I will be focusing on adding more reports, including a fish report. Adding support for some of the other major poker rooms is a top priority as well.

Again, if anyone can donate hand histories I would greatly appreciate it. I would like to focus on Party and Ultimate Bet next. Additionally, if there are hand histories out there that use currency other than USD I would love some of those so I can support different currencies.

I am also in the process of documenting the schema for the statistic databases used by Poker Maven. I should have a Word document prepared and available on my site within the next day or so.

[/ QUOTE ]

Thanks for this sir. You've definitely got my interest. I will be visiting your site and doing a beta download this evening.

[VisualCSharp]

For those interested, I am currently working on iPoker and Ultimate Bet support (hand histories + HUD) for the next release, which will occur sometime before September 15 (the current beta expiration date).

Let me also make a quick point. I spent a lot of time up front creating a good installation experience for the user. If I am going to offer software for beta testing by the community, at the very least the software should install without hitches or manual steps. Even though Poker Maven requires SQL Server 2005 I have made sure that the installation of the database server as well as all the configuration tweaking that is actually required to get Poker Maven working happens in the installer. Here's a list of tasks the installer performs that I didn't have to do myself, but chose to do to give the the user a better experience:

- Including SQL Server 2005 Express Service Pack 2 as a prerequisite.
- Performing an "NGEN" or native image generation, on the Poker Maven binaries to speed their execution.
- Making the MSDTC service (Microsoft Distributed Transaction Coordinator) start automatically at Windows startup. This Windows service is critical to Poker Maven operation because it allows me to use database transactions. This ensures the integrity of all data imported into a Poker Maven database.
- Change the authentication mode of SQL Server 2005 Express from just Windows Authentication to Mixed Mode. This means Poker Maven can use its own database logins and users, pokerMavenReader and pokerMavenWriter rather than relying on Windows accounts.
- Setting Windows ACL permissions on the Databases folder where you installed Poker Maven to give SQL Server access. SQL Server 2005's Windows service runs as the local Network Service account that has very restricted permissions. By default, folders are not created granting permissions to this user.
- Automatically creating or updating your hand histories database.
- When uninstalling, giving the user the option to delete all statistics databases, the hand history database, the application configuration settings and the HUD configuration settings.

[Toasta]

how about postgres support?

[Bogglor]

No reason for postgres support if it has SQL 2005 Express integrated.

[VisualCSharp]

[ QUOTE ]
how about postgres support?

[/ QUOTE ]

As a previous poster stated, there is no reason for me to support PostgreSQL at this time. Poker Maven requires Windows, and a lot of the features in SQL Server 2005 make it the most worthwhile database engine choice in my opinion, including its integration with C# and .NET. I also use stored procedures for all my SQL queries and these stored procedures take full advantage of all SQL Server 2005 features, such as Common Table Expressions (CTE). After you install Poker Maven, install SQL Server Management Studio Express and open one of the statistics databases. Take a look at some of the more complicated Report_ stored procedures.