lookup_realminutes_day bugs

[ethanrox]

Hello,
PT4 v4.14.23 (Microgaming...)
recently discovered the Results>Group By Date>Date Report. Really nice

However, I think there is something wrong with the Real_Hours_Date stat.
I have 3 hours of hands that count for 0.88 hours.

Reporting Options: Day starts at Midnight.

From the log:
...AND ctss.date_start >= '2019/06/30 21:00:00' AND ctss.date_start < '2019/07/31 21:00:00'...

Curiously enough I am living in a UTC+3 country.

Any ideas?

[Flag_Hippo]

Presumably you are using such an old version to import Microgaming cash game hands? If so please note the following:

1) It's a very old version PokerTracker 4 and we don't support it anymore.

2) Microgaming cash hand histories saved by the old client are not complete where you didn't contribute to the pot and these missing hands would reduce the amount of minutes available for the calculation of 'Real Hours' statistics in PokerTracker 4.

3) We re-enabled the import of Microgaming cash hand histories after their policy change.

[ethanrox]

Good news. Will upgrade immediately and update the post if it's still an issue.

[ethanrox]

Same issue unfortunately.
It has definitely something to do with the way UTC dates are handled back and forth in PT4.
I tried creating slighgly modified variables to be used in duplicates for the Real Hours Day/Month.
https://imgur.com/a/EKwRX20

It does work but there are double rows.
https://imgur.com/a/KYIUkPM
This happens because one row is hands from 00:00 til 02:59 and one row is from 03:00 to 23:59.

Is there some workaround possible?

[Flag_Hippo]

Please report this to us in a Support Ticket along with your compressed GameHistory.dat file.

[ethanrox]

It's not a Microgaming issue.

Tested on a database with only Pokerstars hands with newest PT4 version - still have similar results.

Based on the logs which helped me see the queries executed to generate the reports I found that
1. The query that gets the number of hands works correctly always.
2. The query that gets the table sessions in a time period to calculate the "Real Hours" is flawed. There is some offset for time zone I guess like this: ctss.date_start >= '2019/09/29 21:00:00' (should be just 2019/09/30 00:00:00).

I checked my postgres config file and time zone is set up properly.

[Flag_Hippo]

Please report this to us in a Support Ticket and one of technicians will investigate. Thank you.