Spadeit forums

I may be doing something wrong but it seems SpadeEye is reporting incorrect/incomplete stats.

I am using PT3 with a dual database configuration. I have my main DB called PT3 and a datamining DB called PTDataMining I use for imported hands. PT3 is configured to not store HH text for observed hands.

I configured SpadeEye to use both databases by adding them both and acivating them. The I ran a datamining session of about 1500 hands and stopped it. The updated the PT3 cache and also the Aggregator.

I scanned on the tables that were being datamined and was surprised to see that all the players in that table had very few hands, all under 10.

I checked my PT3 for these players and they have over 100 hands each. I compared the stats in SpadeEye to the stats in PT3 and they are not even close. A player with 9 hands in SpadeEye has a VPIP of 90 while in PT he has 120 hands with VPIP of 20.

I also tried to deactivate one of the databases in SpadeEye and use only one. Same exact results, it doesn't even change when I switch them which is very surprising since the player has a different number of hands in each database.

What's goin on here?

Running v3.05 on Full Tilt

Update:
Imported all observed hands into my PT2 database and lo and behold, it works.

Something is very wrong with the PT3 integration.

Hmm, now that I think of it, it might be because I'm using Beta 19 rather than the official Build 3.

can someone confirm this?

SpadeEye saves "old" scanresults for up to 20 minutes.
(See "main->options->tablescanning")
So if you switch between the aggregator/playercache or import some hands you will need to restart SpadeEye to get the new statistics "on the fly"...

Hmm, this isn't very good for Semi Smart Datamining. Does SE refresh the aggregator before rescanning tables?

No, it doesn't, and "yes", this is not ideal for semi smart datamining, but if it would be perfect it would be called "very smart datamining"