New Software Announcement - SIXTH SENSE

[teddyFBI]

MY turn to post my PTAGG problems.

SO I set the Agg running overnight on both my laptop and desktop computers (they both have the same DBs on them).

I wake up this morning and find that on my DESKTOP, the PTAGG window is just blank (whereas it had the text showing the progress of my import when i had gone to bed)...so at first i thought 'cool, it finished creating the AGG DB'...but then I checked the LOG tab and the last few entries show:

Job Error - Error - ERROR: out of memory*DETAIL: Failed on request of size 64
Job - Error - ERROR: out of memory*DETAIL: Failed on request of size 64

Then I check my C drive and to my surrpise it shows me that I am using 99.5% of my HD space...even though I'm nearly positive that I've never been above 60% or so...
1) Is it possible PTAGG created something that sapped up a huge chunk of my HD space?
2) Is my HD space what those log errors are referring to?

On my laptop, i woke to find that PTAGG was still plugging away...currently showing 49.3% complete...but I don't know whether that just refers to a single DB (and it will start at 0% as soon as it completes), or to the entire import process for all 5 of the DBs i'm trying to aggregate.

[teddyFBI]

I think you also missed the Q from my previous post.
It's simply not clear anymore what, if anything, the Menu...options...select PT Database window in SS itself does anymore...I mean, once PTAGG has built the entire AGG database, does SS just draw from that exclusively?? Like, I didn't select ANY DBs in SS's DB-selection windows, but SS still seems to be giving me stats...i guess from the AGG DB it created...so has the AGG DB rendered the SS DB-selection menu completely useless?

[teddyFBI]

Ugh -- while PTAGG was continuing it's import on my laptop, I decided to go to Tools...Configure PT Aggregator... where it brought up the window with my DBs again...I didn't change anything, I just clicked "save and close", and all the progress script has STARTED BACK AT ZERO!!!!!!!

Please don't tell me that I've just undone the last 12 hours of aggregation activity.

This really should have been tested a little further before release, guys.

[teddyFBI]

Listen, while you guys sort out the littany of problems that has crippled this latest release, I'd really like to go back to just using SS WITHOUT any of the PT-Agg "functionality".

Except I don't know how to tell SS "listen, forget about the partial/aborted" PT-AGG you have created to this point, let me just go back to the 'slower' way"...like, every SS scan I run seems to be only using the stats from the aborted (and hence completely incomplete) AT-AGG DB that it tried to create...how do I tell it: listen, forget that nonsense, just go back to scanning the DBs the old way.

EDIT: edited to add that the info in the partial PTT-AGG DB that it started to create but could not complete b/c it filled up my HD is not only incomplete, but just flat-out wrong...it's showing me a player sitting at a table who has supposedly played 113 hands and has a VPIP of 81...so I check it out...actually that player has played 4,500 hands with a VPIP of 24. I don't know how PT-AGG 'aggregates' its data, but i can't figure out how it could think that a player has a VPIP that high when he clearly doesn't...unless it's importing hands that he has played first, which doesn't make any sense.

Rollback, please.

[EvanJC]

ss just died on me again, for about the fourth time today. editing the filter and saving doesnt help, and reinstalling doesn't help

just letting you know =)

[Praetor]

Not working for me atm, when I click refresh nothing comes up

[SixthSense]

[ QUOTE ]
Yes I do...that update fixed it.

It looks like it's going to take 15 days, 5 hours, 49 minutes...unreal. There is no way I am going to take half a month to convert a 1M hand DB. That's just insane.

[/ QUOTE ]

Hmm, obviously it shouldn't take that long. I assume you shut down all other apps too.

Is that an access db or postgres db? If its an access db, you could try converting it to postgres, and then importing it into pt agg.

-Ben

[SixthSense]

[ QUOTE ]
With the .37 i dont get the "testdb not found" error but when i click the reports i get a "NumStatByGametype: Type mismatch for field 'game_type' expecting: WideMemo, actual: WideString" error. The import seems to be working BTW

Edit: Is there a way for SS to use my databases while it waits for the agg database to build? I dont get to see any stats on the tables/players even after i hit refresh or even after i restart SS.

[/ QUOTE ]

Sorry no, SS is not set to use the PT Agg database. That is something I need to make configurable, I'll do that in the next release.

-Ben

[Back In Black]

I would like to second teddyfbi's question about using ss the old way until all this stuff is figured out and this thing works smoothly.

How do I tell ss to work like it used to?

[SixthSense]

[ QUOTE ]
MY turn to post my PTAGG problems.

SO I set the Agg running overnight on both my laptop and desktop computers (they both have the same DBs on them).

I wake up this morning and find that on my DESKTOP, the PTAGG window is just blank (whereas it had the text showing the progress of my import when i had gone to bed)...so at first i thought 'cool, it finished creating the AGG DB'...but then I checked the LOG tab and the last few entries show:

Job Error - Error - ERROR: out of memory*DETAIL: Failed on request of size 64
Job - Error - ERROR: out of memory*DETAIL: Failed on request of size 64

Then I check my C drive and to my surrpise it shows me that I am using 99.5% of my HD space...even though I'm nearly positive that I've never been above 60% or so...
1) Is it possible PTAGG created something that sapped up a huge chunk of my HD space?
2) Is my HD space what those log errors are referring to?

On my laptop, i woke to find that PTAGG was still plugging away...currently showing 49.3% complete...but I don't know whether that just refers to a single DB (and it will start at 0% as soon as it completes), or to the entire import process for all 5 of the DBs i'm trying to aggregate.

[/ QUOTE ]

It appears there is a memory leak in PtAgg. When you shut it down, how much memory did you have on your C: drive? I'll look into it.

And don't worry, if you stop it and restart the import process, it just starts where it left off. It always starts up from zero, but the Max # you see it going up to should be lower since it already imported records.

-Ben