Hey Guys,

I have a quick question ; Is FPDB calculating the rake and rakeback on Seals With Clubs ?

I saw in the Cashier of the room that you can ask for your "Rakeback history". Do I have to add these numbers on the results I have from FPDB ??

I want to be accurate and obvously not count twice the rakeback

Am I doing it well by adding the rakeback history to my results on FPDB ???
I guess that the rakeback is directely added to your account by SWC. They don't explain it in their web.

As far as I know FPDB has no mechanism for calculating rakeback. Even if it did, you would need to enter your rakeback % before it could. But it doesn't. So you can't.

So what you are currently doing seems to be correct.

Thanks Phil

Thx for the answer phil. New problem now..: In betonline, the tables are 10 handed, but one seat has no stats (only xxxx ). I searched HH, is called seat 0 and maybe thats why is not recognized? Any solution?

Thanks for all the help, Phil.

I was just thinking it would be nice to be able to double click on hands in the RingPlayerStats (e.g AKo) and have all your plays of that hand show up in the HandViewer.

I opened an issue in github for tracking.

https://github.com/philroberts/FPDB-for-OSX/issues/4

I'll do some testing in a minute. Does this problem happen every time? Is it always seat 0?

Update: I tested. It would happen all the time. Temporary solution: search in your config file for the betonline_default layout:

Add in the highlighted bit in the 10-max layout. If anyone is playing on other size tables a similar solution should work there too.

I think I should fix this in the parser, really, and I might in a future release. But then you will need to remove this fix from your config file. The whole situation makes me want to vomit. Maybe I will just make the default config have this in it. It's so gross though!

How to clean hand history data base from fpdb on Max OS?
Thnx.

Option 1: Maintenance->Create or Recreate tables

Option 2 (if using sqlite, which is the default): rm -r ~/.fpdb/database

That works for me, thnx.

freepokerdb worked for me. Thanks for a program. Suggestions:
1) hud to auto-position correctly onto table and multiple tables (especially for first timers).
2) hud main window pop-out could be incorporated into hud tab
3) creation of hud preview window and customisable window
4) save graph settings and stats layout on exit
5) set default tabs to open at start-up (in my case: hud, graphs, ring player stats, session stats, hand viewer) - remember these settings.
6) tabs movable at top
7) stats moveable around and editable (add to, remove).
8) auto importing of hands running at startup and able to detect poker client/s running.
8) date parameters (today, yesterday, this month, last month, this year etc).
9) candlestick chart (very cool), add volume (volume spread analysis indicators - I know I'm going to go on a downswing).

Is there a bug where FPDB won't import properly? It seems when I try to import certain tables it doesn't really "freeze" per se, but does just sit on the same file for what seems like eternity. I'm literally trying to import 1 file that is 140.9kb big....

I am using SQLite that came with FPDB. I've tried installing/using Postgres to no avail...it's just beyond me apparently lol.

Also wanted to add that I imported what I could. HUD worked pretty well for the most part. Another problem I ran into was during a semi-decent session (over 1.5 hours) the auto-importer started to get stuck on reading a table and then stopped working on all other tables. Not entirely sure why.

What operating system/poker site/FPDB version? Anything pertinent in log messages?

I'm running Windows 7, playing on BetOnline, FPDB: 0.40.5

Error Log:

Traceback (most recent call last):
File "GuiBulkImport.pyc", line 89, in load_clicked
File "Importer.pyc", line 255, in runImport
File "Importer.pyc", line 294, in importFiles
File "Importer.pyc", line 319, in _import_despatch
File "Importer.pyc", line 538, in _import_hh_file
IndexError: list index out of range

fpdb-log:

This file has a ton of lines, a lot of errors as well.

2nd to last line of log file:

2015-02-07 00:34:50,882 - importer ERROR Importer._import_hh_file: '<type 'file'>' Fatal error: ''Traceback (most recent call last): File "Importer.pyc", line 467, in _import_hh_file File "Hand.pyc", line 305, in getHandId File "Database.pyc", line 3238, in isDuplicateOperationalError: near "%": syntax error''

^^ This is repeated a ton

Can you search your config file for "publicDB" and tell me what you find?

publicDB="False"

Hmm, that's not the problem then. Can you try my latest release? I don't expect it to fix the problem but at least I'll be looking at the same code as you are running.

https://github.com/philroberts/FPDB-for-OSX/releases

If that doesn't help (it probably won't), can you email the hand history file to me? philip.roberts@gmail.com

Cheers.

HH sent. Quickly got 0.41.0-rc5 running and bulk import hung up at about 22%.

Little update phil...

I got a config_example from the new 0.41.0-rc5. I saved it as an xml file, replaced the old config I had and now the import works. Loaded all hands fairly quickly.

Great news! I love it when problems solve themselves.

Yeah, thank you so much for your prompt and quick responses Phil. Means a lot here.

Ugh.

Should be fixed in the parser for sure. Is it only 10 handed tables that have a seat=0 or do all tables?

Hi Sorrow! I have not seen a HH from anything other than 10-max.

Edit: belay that, one of the HHs kedwards sent me is 6-max, and oh boy is it fun. They have a similar weird seating thing to ipoker so hist_seat is probably the way to go, and leave the parser as is. Hopefully having a 0 seat doesn't break things elsewhere...

I'm an old dev and haven't looked at FPDB and poker in a while but...

1) We relied on users to send us better config defaults for positions, the main FPDB devs were only playing on Stars/FTP only so couldn't provide better defaults (when adding a new site I used to copy another sites layout, just about guaranteed to be wrong)

3) We agree, the HUD code was pretty closely tied to the parser tick and window detection making it tough to do.

4) Again agree, any specific defaults you'd like to see?

5) Sounds useful

6) I think thats a limitation of the toolkit, but I suspect that might be a one liner

8) That was removed. It caused a _lot_ of new user problems. You start FPDB and it becomes unresponsive for possibly hours as it found your last 5 years of hh's and started importing. We got a lot better at handling it, but it is surprisingly tough to get 'auto detect' logic to work consistently across operating systems.

8.2) For what reports?

9) Sounds interesting can you provide an example of what you'd like to see?

Looks like BetOnline has always had the 0 seat.

If the calculations in DerivedStats are ok then its probably a hud/query issue.