PokerDaVinci January BETA: semi-public release
 

http://www.pokerdavinci.com/images/logo-small.gifThe January BETA release of PokerDaVinci is now available for download/testing. This is the first semi-public release. Up until this point, all testing has been private.

The short release notes and instructions are located at http://www.pokerdavinci.com/sw/rel-Jan06.php .

PokerDaVinci is designed with the same goals as PokerTracker but intended to be much more powerful and flexible. It imports histories into a database and lets you analyze your play and the play of your opponents. Note that the current beta doesn't contain any live advisor aspect (although it eventually will and I also hope to work with 3rd party developers who currently have products that support PT).

Take a look at the screen shot page: http://www.pokerdavinci.com/sw/screenshots.php?dir=2 for a feel...

A quick comparison to PT is here: http://www.pokerdavinci.com/sw/compe...ysis.php?dir=2 .

You can also take a look at our website: http://www.pokerdavinci.com/sw/overview.php?dir=2 for an idea of what PokerDaVinci is. However, since we are just leaving "stealth" mode, there are not too many real details there yet. As I find time to update it, I will...The blog has day by day details of what is being worked on.

A couple of notes about the beta release:<ul type="square">
[*]It is a BETA- not a finished product. There are many known bugs and incomplete features. I actually believe it to be a fairly stable beta or I wouldn't be opening it up to the public in general but you still need to have the right attitude. I am looking for people who will try out various aspects of the program and provide me feedback and suggestions!
[*]PokerDaVinci has higher system requirements that an app like PokerTracker. We use a real database system (Microsoft SQL Server) and .NET 1.1 as a platform. Don't expect to run it on a 7 year old laptop and be happy with the results. You are going to probably want a screen of at least 1024x768, a decent processor and 256MB+ of RAM. It requires Windows 2000, XP or Vista.
[*]The download is approx. 35MB which doesn't include .NET 1.1. If you don't already have this installed (most of you probably do), it will also need to download. You are going to need to be very patient if you don't have a broadband connection.
[*]The most tested/stable parsers are for PokerStars and PartyPoker. Ideally, you should have a number of histories from one of those sites just to be sure to have something that imports succesfully. We also have early versions of parsers for Paradise, FullTilt, Pacific, UltimateBet, Cryptologic, Ladbrokes, PokerRoom and TruePoker. [/list]
Thanks for all the interest and feel free to post questions here, or send me a PM/email...

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

I went ahead and guinea pigged this. Very ambitious project!

My first impression is of course that I don't know what the heck I'm doing. Despite the less technical look than most of the other poker software out there, it definitely looks like it's for people that really know what they're doing and are willing to spend some time getting the program to do what you want it to (even more so than PT and PAHUD, etc.)

It definitely has a lot of fun potential, like you've highlighted with a couple of the pre-programmed filters-- you can easily find things like bad beats and (good beats?), etc.

One of the things that really caught my eye-- it may already exist in other programs but not that i've used or know how to access-- is identifying what kind of hand you had after the flop-- overcards, flush draw, top pair, etc. I have no idea whether this is finished or how to use it yet, but I like the idea of easily identifying hands and perhaps comparing performance of each.

runs pretty slow on my VM (i'm not 100% convinced you're not playerlogin!), and either a tutorial or plenty of time invested in learning what's going on is in order, but looks pretty neat!

Re: PokerDaVinci January BETA: semi-public release
 

VERY nice!

the program looks professional-looking, the website is awesome, LOTS of info on the website... i'm gonna give this a try.


EDIT: minor correction on the comparison page - PokerTracker DOES have auto-updating. whenever you start it up, it checks for a newer version.

Re: PokerDaVinci January BETA: semi-public release
 

[ QUOTE ]
PokerDaVinci has higher system requirements that an app like PokerTracker. We use a real database system (Microsoft SQL Server) and .NET 1.1 as a platform. Don't expect to run it on a 7 year old laptop and be happy with the results. You are going to probably want a screen of at least 1024x768, a decent processor and 256MB+ of RAM. It requires Windows 2000, XP or Vista.

[/ QUOTE ]

Just one question:

If you were to benchmark your product on say importing and using 1 million hands or more, then how does your product compare to Poker Tracker, Poker Office and Poker Manager.

So far I found Poker Manager wins hands down in respect to this question: it is about 3-4 times faster for import than either Poker Tracker or Poker Office <u>AND</u> DB performance does not seem to degrade badly as more hands get imported [as in other products]). Extra functionality is not helpful to me, if speed issues make a product totally unusable... [img]/images/graemlins/smile.gif[/img]

The only reason I ask this is because I don't want to waste yet another 2/3 days importing hands only to find it is not what I am looking for. For me personally the DB speed is the main factor and some kind of standard benchmark would help me most in judging which product is best [img]/images/graemlins/smile.gif[/img]

Juk [img]/images/graemlins/smile.gif[/img]

Re: PokerDaVinci January BETA: semi-public release
 

Thanks for checking it out. Yes, it is fairly advanced and designed for serious players. It targets the same set of players as PokerTracker. Like you said, it could really use a tutorial, help files, etc. But it is only in beta and I don't want to spend too much time documenting what might still change...

In terms of the comparision...By my terminology, that isn't "auto updating", it is simply version checking. PT simply notifies you that a new version is available but you still need to download and install it by hand.

PokerDaVinci has built in support for auto-updating (although it isn't turned on in the beta) so that if a bug is found in a plugin (or another plugin is released), it will automatically be downloaded and installed with no user interaction necessary. It will, of course, be able to be disabled.

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

[ QUOTE ]
One of the things that really caught my eye-- it may already exist in other programs but not that i've used or know how to access-- is identifying what kind of hand you had after the flop-- overcards, flush draw, top pair, etc. I have no idea whether this is finished or how to use it yet, but I like the idea of easily identifying hands and perhaps comparing performance of each.

[/ QUOTE ]
PokerOffice 2 has this feature

Re: PokerDaVinci January BETA: semi-public release
 

[ QUOTE ]

Just one question:

If you were to benchmark your product on say importing and using 1 million hands or more, then how does your product compare to Poker Tracker, Poker Office and Poker Manager.

So far I found Poker Manager wins hands down in respect to this question: it is about 3-4 times faster for import than either Poker Tracker or Poker Office <u>AND</u> DB performance does not seem to degrade badly as more hands get imported [as in other products]). Extra functionality is not helpful to me, if speed issues make a product totally unusable... [img]/images/graemlins/smile.gif[/img]

The only reason I ask this is because I don't want to waste yet another 2/3 days importing hands only to find it is not what I am looking for. For me personally the DB speed is the main factor and some kind of standard benchmark would help me most in judging which product is best [img]/images/graemlins/smile.gif[/img]

Juk [img]/images/graemlins/smile.gif[/img]

[/ QUOTE ]

Juk,

I hear you. I can't give you concrete answers because I haven't taken the time to run the comps on the beta since it keeps changing. I wouldn't suggest spending 2-3 days importing a million hands into the beta since you may need to do it again w/ the February beta, etc. until the DB format is finalized for release.

Having said that, I can tell you some general "truths"...

1) The performance will be independent of the size of the file you are importing. I have no idea what the heck PT does to make it so bad when you import a large file (it seems to get exponentially worse as the file gets larger). We actually save each hand to the DB as it gets parsed so the performance is linear "O(N)" if that means anything to you. There are some bugs in the current beta which makes this statement (slightly) untrue but the next beta will resolve them. Specifically, while parsing is linear, we do things like count the number of hands in a file before we start (to provide a status bar) and this takes a *long* time if the file gets big. I need to add a method to estimate rather than count if the size of the file is big (e.g. hundreds of thousands of hands).

2) The app is entriely multi-threaded and the DB import (e.g. parsing) is separate from the viewing of the data. In other words, unlike PT which locks up the whole app (and often the whole machine with a 95% processor usage), you can simply start to import your hands and then put it into the background while you start to view your data (or do other things). This also means that it will take advantage of things like a dual processor machine.

3) Last time I checked, PokerDaVinci was about 2-3 times faster than PT for small files. There is no real comparison on larger files since (as you mention), PT just goes completely to hell. I have not tested against PokerManager. Again, this isn't an "official" comparision. That will need to wait until we get closer to release but I wanted to give you an idea.

4) Finally, the beta database is not optimized for performance so it will only get better. Although this is mostly true for the queries as we build more complex indexes. The actual parsing performance probably won't change that fundamentally since it is bound by the speed of the regular expression matching.

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

Thanks for the detailed answer! [img]/images/graemlins/smile.gif[/img]

I think I better wait until the Feb beta to try importing my hands (I done this for PG SQL and PM now, and it eats a few days each time... [img]/images/graemlins/smile.gif[/img] ).

[ QUOTE ]
I have no idea what the heck PT does to make it so bad when you import a large file (it seems to get exponentially worse as the file gets larger). We actually save each hand to the DB as it gets parsed so the performance is linear "O(N)" if that means anything to you.

[/ QUOTE ]

Yep, O(n) means something to me [img]/images/graemlins/smile.gif[/img] I too have no idea what the heck PT does, but it drove me crazy in the end... [img]/images/graemlins/smile.gif[/img]

[ QUOTE ]
The app is entriely multi-threaded and the DB import (e.g. parsing) is separate from the viewing of the data. In other words, unlike PT which locks up the whole app (and often the whole machine with a 95% processor usage), you can simply start to import your hands and then put it into the background while you start to view your data (or do other things). This also means that it will take advantage of things like a dual processor machine.

[/ QUOTE ]

I too have suffered from the 'lockups'. I originally re-imported all my hands into PT/PGSQL on a separate dual processor machine (it just crashed on my machine... [img]/images/graemlins/frown.gif[/img] ). It locked the whole PC for nearly 3 days for about 900k hands, used huge amount of page-file (GBs), and used just 1 processor (PG SQL barely used 5% of 2nd processor...).

I will look forward to seeing how PokerDaVinci turns out - Juk [img]/images/graemlins/smile.gif[/img]

Re: PokerDaVinci January BETA: semi-public release
 

Juk,

Just a quick update (both good and bad). The good first...

I have spent a fair amount of time working on the performance of PokerDaVinci after your question (profilers are your friend!). In terms of parsing performance, I have been able to speed up the base performance and fix the issues to ensure that it is basically O(n) now. I just ran a test where I imported 250k PokerStars hand histories. In round numbers, it takes around a minute/1000 hands of history. This was true at the start and at the end (the last 120k took 2h10min). My memory use also remains fairly constant (although the DB memory footprint grows agressively depending upon your settings).

The bad? First off, I have spent so much time on performance testing (which is slow) that I have neglected the core code and I am needing to push the next release back. My new release target is March 15th.

Second, I store a LOT more data about each hand than something like PT does. This means that the DB gets larger. Now that I am doing more extensive performance testing, I have a better feel for it. My 250k hands means a 1GB database file. The current DB I install (MS SQL 2000 Desktop edition) limits you to 2GB which would mean ~500k hands. There are a lot of solutions to this but they will all take some work (for either me or the user)...One option is to just upgrade to SQL Express 2005 which raises the limit to 4GB which would give approx a million hands of history. Another option is to support PostgreSQL in addition (or instead) of MSSQL since it has no limit. Obviously if the user has access to a full licensed version of MSSQL, they can use that instead with no limitations.

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

I installed it and I am currently importing 40kish hands. I've been importing for roughly 15 minutes and im 25% of the way done. Not sure how this compares to PT, as I've never imported a large amount of hands to PT.

Re: PokerDaVinci January BETA: semi-public release
 

i wish you luck but this is going to be a tough market to get into. not only does poker tracker have its name out there, but due to his incredible support and his generous nature (not charging us for the postgre version), poker tracker pat has a loyal following and will continue to get good reviews. not like i'm telling you anything you don't know, but it seems like quite an ambitious undertaking

i wodner if pat would be willing to either hire you or buy your ideas/software. that way you avoid the barriers of entry and he can get a good second guy to take some of the load off his shoulders and maintain his market share. seems like it could be mutually beneficial. even though it seems like your goal is to blow pokertracker away, from a marketing standpoint your product is going to have to be significantly better to compete

Re: PokerDaVinci January BETA: semi-public release
 

[ QUOTE ]
I installed it and I am currently importing 40kish hands. I've been importing for roughly 15 minutes and im 25% of the way done. Not sure how this compares to PT, as I've never imported a large amount of hands to PT.

[/ QUOTE ]


i think that's comparable, though maybe a little slower (for my computer at least)

Re: PokerDaVinci January BETA: semi-public release
 

[ QUOTE ]
[ QUOTE ]
I installed it and I am currently importing 40kish hands. I've been importing for roughly 15 minutes and im 25% of the way done. Not sure how this compares to PT, as I've never imported a large amount of hands to PT.

[/ QUOTE ]


i think that's comparable, though maybe a little slower (for my computer at least)

[/ QUOTE ]

For refrence my computer is a 3 ghz P4C with 512 ram. I did forget to mention something that may be very important, I am importing from an external drive (USB 2.0). This may (or may not?) greatly affect the speed.

Re: PokerDaVinci January BETA: semi-public release
 

This is great and seems very promising. I've been looking for something that incorporates the graphs and polished feeling of Poker Office and hand analysis similar to what Poker Academy does.

Also, very impressive, sir [img]/images/graemlins/smile.gif[/img]:

[ QUOTE ]
Jon Mittelhauser, President: Jon is considered one of the founding fathers of the World Wide Web. He was the co-author of the first widely used browser (NCSA Mosaic for Windows) and was a founder of Netscape Communications. He is now a poker addict (aren't we all?). Jon uses his experience in developing software and building successful startups as our President and chief software architect.


[/ QUOTE ]

Re: PokerDaVinci January BETA: semi-public release
 

I attempted to import some hand histories, and it took about 30 minutes to do, but nothing is showing up in the program. Maybe it is because I'm trying to important hand historys that PT has already proccessed? These are party hand historys.

Re: PokerDaVinci January BETA: semi-public release
 

It was the exponential decay in performance that stopped me using PT in the end. Also the 'lock-ups' didn't help either as I had no idea when (or if) it was ever going to finish importing.

Look forward to seeing it in action.

Juk [img]/images/graemlins/smile.gif[/img]

Re: PokerDaVinci January BETA: semi-public release
 

Juk - If you end up importing 900k hands into davinci, could you tell us how long it took / if there were lockups / memory &amp; cpu use? (Even if you import only 500k due to database limits, this would be useful too). Also, could you give us a general feel for how the program deals with databases of that magnitude (queries, lookups, etc.)

PT pisses me off in how long it takes to access the database and look for stuff. I've abandoned (more or less) using it for anything but PAhud, graphing, and the occasional stat check on myself. If davinci can boost performance so it becomes a usable database, I think I would be able to boost play a lot. (note - i'm on an amd 3200+ with a gig of ram, so pt should run decently well on my computer, but doesn't really)

I'll postpone downloading it until more people leave feedback, but it looks tempting from the screenshots - very tempting indeed.

-eric

Re: PokerDaVinci January BETA: semi-public release
 

I am will give it a try, but just waiting as the developer said something about possibly having to re-import all my hands as the DB schema may change before it goes final and I done this too many times already trying to find a solution to HH problems.

I am currently using PokerManager which does seem to handle large number of hand histories quite gracefully (so far just under 800k 6max hands imported and still running smoothly). I would say overall it is about 3-4 times quicker than PT for the imports and doesn't have the exponential slowdown problems of PT. Also I was getting problems from PT look-ups for displaying stats on HUDs and PokerManager look-ups seem quite acceptable even with so many hands in the DB.

When PokerDaVinci goes final then I will try reimporting my hands and give some feedback here.

Juk [img]/images/graemlins/smile.gif[/img]

Re: PokerDaVinci January BETA: semi-public release
 

[ QUOTE ]

Second, I store a LOT more data about each hand than something like PT does. This means that the DB gets larger. Now that I am doing more extensive performance testing, I have a better feel for it. My 250k hands means a 1GB database file.

[/ QUOTE ]

That seems like a lot of space for 250,000 hands. I think with datamining that would be too much, but since datamining will be non-existent for most users you may get lucky. 1 gb still seems like a ton of space for that many hands. I haven't looked at the database, but are you duplicating the data in different tables? When I look at the HH half of it is just the names of the players. I would have thought with a good data model, once you get the names of the players in the DB the amount of space used would be rather small for each HH. But, I haven't dug into it like you have so I'm probably wrong.

Re: PokerDaVinci January BETA: semi-public release
 

Guys,

A few comments...

1) The performance issues that Juk and I were discussing is in the NEXT beta. The January beta has some bugs that slow it down as the files get larger. Please feel free to try out the January beta (with smaller numbers of hands) and give me your feedback but these are only betas. The database schema is still changing, the product is still improving...

2) Josh, I acknowledge everything you say. Pat has done a great job with PT and provides very good support which has given him a loyal following. Having said that, it is a very big (potential) market and I believe that I will be able to compete. There is plenty of space for more than one piece of software. As Xiphoid dug up, this isn't my first software venture. [img]/images/graemlins/smile.gif[/img] If I produce something substantially better and do a good job marketing it, it will succeed. If not, PT will continue to dominate and he may adopt some of the features that I have that he is missing. Either way, you (the consumer) wins.

3) Juk, I haven't had a chance to play with PokerManager much yet. How big is your firebird DB with 800k hands? Does it store info about *every* player or just players that match a certain criteria (e.g. X hands known).

4) Nibster, no there is no duplicate data in the database. However, there is a lot of calculated data. I'm at home right now so can't give you the exact stats on the various table sizes but...With 250k hands, we have:

*250k rows in the Game table (datetime, name of game, etc)
*250k rows in the GameCalc table (number of players, number of players seeing flop, total pot, rake, etc),
*I'd think somewhere between 5k and 20k rows in the Player table (this one is small and just stores their name)
* Approximately 1.5million rows in the Seat table (6 players ave * 250k hands) which stores the seat #, pos relative to button, etc.
* Approx. 1.5 million rows in the SeatCalc table. This is the BIG one where I store a lot more data than PT does. All the basic info you expect (net for the hand, player VP$IP yes/no, player went to showdown, etc). In addition to the info that they store, I keep track of more specific poker info like the rank of the hand you have at the flop, turn and river; how many overcards you have to the board at the flop and turn; how many outs you had to a straight, flush or straight flush; your EV (if more than one set of hole cards is know) at each stage, etc.

I have some ideas on how to optimize this latter data down but it becomes a tradeoff between space and performance. I can easily shrink the DB size but then the query performance may suffer to much. I am still trying to find the right balance.

One easy way to shrink the DB may be to purge out players who we don't have enough info about to be useful on a semi-regular basis. On my current test, I have 250k hands of data on one player but there are a TON of players in the DB with less than 100 hands of data on. That data could be purged, archived to a separate db (in case I get more data later), etc, etc.

Anyway, I'm still working on it...keep tuned if you are interested. Although my blog and PDV forums will be updated more than 2+2...

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

Hey, I like the modern interface. It looks very nice. Two questions:

Can I use the express edition of SQL Server 2005 for this beta?

The "poker knowledge" sounds intriguing. Does it mean that I can query for stuff like: "any hand that I raised pre-flop, was check-raised on the turn and showed down" and "any hand where I was heads-up on flop and check-raised with less than two overcards"?

Re: PokerDaVinci January BETA: semi-public release
 

Fiddler,

I haven't tested it against SQL Express 2005 yet (keep meaning to) but it *should* work. You'll just need to modify some settings in shared.config which I can walk you through if they aren't self-explanatory.

Yes, those are the exact type of queries that the data in the database is designed to support. The front end GUI doesn't make all the queries possible yet but the data is there and the GUI gets more powerful each iteration. You can also create custom queries by modifying the query XML files if you are that sophisticated (and avoid the GUI query builder)...

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

I started installing it and got about 20 errors..I'm not trying to post a report, good or bad, or about anything..this was two days ago or so so I don't remember the exact error...anyways I have been working with computers(web-site designer and programmer for 4 years) for atleast 8 years and am quite computer savvy. If I screw around with something for more than 20 minutes and can't figure it out, then you probably need to work on making it "easier" for the regular customer..this could've just been caused by my computer, but i just un-installed the program after 20 mins or so(I got the launcher etc up, and then tried importing hands and it didn't even start to import)

I might try it when it is out of beta though

Re: PokerDaVinci January BETA: semi-public release
 

*grin* I'd be happy to try to help you with the install errors but that report is a bit vague. [img]/images/graemlins/smile.gif[/img] Seriously, it is a beta so I am not that surprised that some people have problems but I can't fix them unless I am given a hint...

The only known bugs related to install have been on systems which don't have administrator privilage or already have MSSQL installed but I am sure that there could be more. Do either of those describe your setup? Did the install fail during the setup of MSSQL? If you still have a file c:\MSDE2klog.txt it might provide me/you a clue.

For the record, I have had about 500 downloads and only 3 people who have _reported_ installation problems.

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

Jon,

Great product. I've been posting here hoping other people would make up my mind on whether to use it, but I finally chose to just do it myself. My database is at 250k hands and it took a night to import (~12 hours... but at least 4 hours of those I had other things running, including pokertracker). All in all it wasn't too bad, I've got about a dozen suggestions for you in terms of ways to improve the layout, system performance, and a few other things that kinda irked me that I would like to see fixed. I'll post those eventually on your forums to make life easier.

I'm posting, though, because I encountered a pretty big error. I imported all of the hands and then started up the player analyzer function. It came up, flashed "loading" for a while at the top, then gave me a timeout error. The exact error was something along the lines that the timeout period expired before it could complete the process.

I'm not sure what the error is about, but hopefully you could get back to me. I really think this software could be a huge success given its speed and versatility, so please get back to me about a possible fix.

-eric

Re: PokerDaVinci January BETA: semi-public release
 

Eric,

Yeah one of the things I figured out when I started doing the stress testing was that the default SQL timeout was set too low when you got a decent (100k+) quantity of hands in the DB. This is fixed in the next release but I realize that doesn't do you any good. I'll see if I can pull the January code from version control and do a quick fix and issue an update for you today. None of the other performances fixes would be part of it but at least the queries wouldn't timeout. I'll post here if I am able to (or not, either way)...

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

Sounds very very promising, I'll check it out.

Hopefully, you are doing more for NL and SnG players than PT.

For example, PT has a database field to indicate if a player went all-in but it is not used currently. I'd like to see this fact imported. Also, the ability to filter raises by x * buy-ins would be nice. Finally, the analyzer should have the ICM built in.

Re: PokerDaVinci January BETA: semi-public release
 

Eric,

Ok…I think I have a patch for your timeout issue. This hasn't been extensively tested (either the patch itself or the autoupdate mechansim) but I figure you are busted right now so...if we fail with this, you may need to wait for the next update or we may need to take the discussion to email...

I am assuming that you haven’t done any UI customization yourself by modifying the DataViewTree.xml file. If you have, ignore this and let me know (since this would overwrite your changes)…

Try this…

Run the Launcher app and then go to the menu at the top: Help-&gt;Check for Updates

Follow the process and when you run the PlayerAnalyzer again, it will hopefully allow your queries to complete. I upped the SQL timeout to 120 seconds. Even without the more optimized DB, this should be enough.

In addition, I threw in some more queries/tables for you.

1) You should now see By Flop-&gt;Hole Cards which groups Hole card stats by the flop (e.g. what cards you played that flopped a fullhouse).

2) You’ll also get By Hole-&gt;By Position and By Position-&gt;Hole Cards…which allow you to see what cards were played in what position (grouped either by card or by position).

Of course, these queries may take a while with 250k hands. [img]/images/graemlins/smile.gif[/img]

Let me know if it works!

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

HesseJam,

My intention is to do more for SNG and NL but you won't see *that* much additional yet. I believe that my biggest advantage is that my architecture/framework is very flexible which makes it easier to add new features like the ones you want. However, I need to get the core stuff rock solid first (as you can see from some of these posts...) [img]/images/graemlins/smile.gif[/img]

I'd love to start a discussion with you about what you'd find most useful. ICM is already on my list but is a bit of a ways down. 2+2 isn't the best place to do that though. Can you either email me or start a *wanted features* post on poker davinci that I can track easier.

BTW, I have promised my earlier beta testers that the ones that contribute the most (bugs, ideas, etc) would get free licenses. The same offer would apply to you...

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

Integrate a Pacific Poker hand grabber and all you have to do is show me where I need to line up to buy this. [img]/images/graemlins/smile.gif[/img]

T

Re: PokerDaVinci January BETA: semi-public release
 

does this show stats on players like V$PIP, etc, etc. ? im at work and just saw this...sounds very cool

Re: PokerDaVinci January BETA: semi-public release
 

oh and yes a pacific hand grabber integrated would be awesome. maybe even integrated hand grabbers for a variety of poker rooms.

Re: PokerDaVinci January BETA: semi-public release
 

Jon,

Both of the things you added showed up in the GUI tree. However, it still timed out after 120 seconds. Anything else I can try? I'm tempted to reimport like 1/4 of my hand histories and try it out with a smaller database to help with the beta, but either way this will be an issue for your program eventually.

Thanks for the help.

-eric

Re: PokerDaVinci January BETA: semi-public release
 

Eric,

Hmm. Can you select a different player (with less hands) from the player selector and get it to show up? Unless you have a really weak machine, I can't imagine 120 seconds not being enough so something else may be going wrong.

On my machine, queries on the player with 225k hands take about 30 seconds but the other players all come up in under 10 seconds.

The next beta will do a better job with larger databases but it is still something I am working on getting better.

If you want, I can also give you instructions on how to create a new DB to try importing a smaller set of hands also...

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

gswarriorfan,

Yes, it shows all of the common PT stats plus a bunch of things that PT can't show.

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

I know you still have a lot to do just to get Holdem running but do you have any plans to add Omaha and Omaha Hi/Lo in the future?

Re: PokerDaVinci January BETA: semi-public release
 

Any word on Absolute support. That site isn't listed anywhere on your site and just wanted to throw it out there...

A huge chunk of my play is at Absolute and it probably wouldn't be worth my coin to get your program when it won't cover at least half my hands...

Re: PokerDaVinci January BETA: semi-public release
 

jon for some reason when i load up my hand histories it only sees 5 hands played. im not sure whats goin on. i tried loading them again and same problem.

Re: PokerDaVinci January BETA: semi-public release
 

[ QUOTE ]
I know you still have a lot to do just to get Holdem running but do you have any plans to add Omaha and Omaha Hi/Lo in the future?

[/ QUOTE ]

Yes, the DB support is in there to tag different games. Unlike PT, the intention is to support all poker games through a single interface (and for a single price!).

However, this is only the first public beta of the hold'em part and that still needs a fair amount of work. The hope is to have the 1.0 version done in time for a launch at (or before) the WSOP. The Omaha code will follow that...

-Jon

Re: PokerDaVinci January BETA: semi-public release
 

[ QUOTE ]
Any word on Absolute support. That site isn't listed anywhere on your site and just wanted to throw it out there...

A huge chunk of my play is at Absolute and it probably wouldn't be worth my coin to get your program when it won't cover at least half my hands...

[/ QUOTE ]

Well when I started, they were covered by other plugins but since they have changed their format, I haven't updated anything. Yes, I'll add support. Plugins are fairly quick/easy to write. The hard part is getting the format specification since the sites don't publish anything. Basically, I need a bunch of sample histories to reverse-engineer. The problem with this (of course) being that sites keep changing their formats and the format/lines are slightly different for each game type.

I have some older histories but if you (or other interested parties) send me some histories ideally from a variety of limit types (fixed, pot, NL), game types (ring, tournament, SNGs, etc)), I'll add support to the list. The nice thing about the plugins is that they are easy to add/update independently of the rest of the code.

-Jon